Maintenance Notification:
On next Monday August 5th 2019 starting at 7am CEST we will conduct some maintenance. You might encounter some issues using the Exasol User Portal and Issue Tracker! We will restore the Exasol User Portal and Issue Tracker before 9am CEST on Monday August 5th 2019.

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 56 Next »

Table of Contents

Where to get Exasol on AWS?

 Two different versions are available via the AWS marketplace:

Pay-As-You-Go (PAYG)

  • Simply pay for what you use
  • Charged on an hourly basis
  • Billed through the cloud Marketplace
  • This offerings contains community support

This is the default setting used in the deployment templates.

(Url to marketplace offering

Bring-Your-Own-License (BYOL)

  • Select this option if you already have a valid Exasol license for the selected configuration or if you plan to purchase a license.
  • The license file is required to operate this product

((Url to marketplace offering:


We recommend reading the getting started guides before launching a database system.

If you are not sure which version to choose, the PAYG version is most probably the version you should use

Getting started

Single node installation

If you just want to quickly start with a single-node database via AWS Marketplace or AWS Console please refer to refer to this guide  SOL-377 - Getting issue details... STATUS

Cluster Installation

An Exasol cluster can be conveniently installed using our CloudFormation template:   SOL-605 - Getting issue details... STATUS .2

Quick Launch

If you would like to start a preconfigured cluster as quickly as possible just press one of the buttons below to iniate a CloudFormation based deployment of a 5-node cluster (good for approx. 2 TB of raw data).

Just press "Next" to proceed to the configuration options, then define passwords for the administrative users, press 2 times next, acknowlege the checkbox at the bottom of the screen and start the setup via the create button.

 (uses an existing VPC)    (generates a new VPC)

Please note that the deployment may take approximately 15 minutes.

For more details on the parameters and how to change the configuration please refer to SOL-605 (please see above).

Support & Troubleshooting

This offer includes assistance from the Exasol Community (Community Support) and access to the Exasol Solution Center.

For troubleshooting & and information on how to register for community support please refer to  SOL-382 - Getting issue details... STATUS  and to the solution documents listed below.

More Information 

Recommendations for using Exasol on AWS

  • Recommended instance families: m4, m5, r4, r5, c5
  • Recommended storage: gp2 EBS storage
  • Backup storage: S3
  • Minimum size of main memory: 16 GB

Storage Configuration

  • Instance-integrated hard drives (ephemeral storage) and EBS volumes are supported for data storage.
  • In a production environment, we recommend using high-available EBS drives, as these provide maximum reliability and durability.
  • For EBS type we recommend using at least General Purpose SSD (gp2) volumes.For high IO requirements we recommend Provisioned IOPS SSD (io1).
  • For data backup & restore ( SOL-354 - Getting issue details... STATUS as well as data import & export ( EXASOL-1678 - Getting issue details... STATUS ) Exasol supports cost-efficient S3 storage.

Exasol AMI: Determine AMI ID and activate AMI for manual launch

    The AMI-ID can be found in the AWS Marketplace offering:

  1. Access (Pay-As-You-Go, community support only) or (Bring-Your-Own-License)
  2. Select "Continue"
  3. Select "Manual Launch"
  4. Select "Accept Software Terms" ( (warning) Otherwise you will not be able to succesfully launch the AMI)
  5. The AMI-ID can be found on the "Manual Launch" tab

Release Notes

EXASOL-2161 - Getting issue details... STATUS

EXASOL-2032 - Getting issue details... STATUS

Upgrade Information

  • 5.0.x   -  (warning) It is not possible to upgrade a 5.0.x AWS installation to a 6.0.x. Please backup the data, install a new cluster, and import data in this case
  • 6.0.1   -  (warning) if you consider upgrading AWS 6.0.1 to any later version, you need to apply the patch attached to this issue while the nodes are still running. Just upload it through EXAOperation in the Software tab: DOWNLOAD-564 - Getting issue details... STATUS

Further Documentation & Tools

For clients, drivers and the standard Exasol manual, please visit the Exasol User Portal

Please note that AWS specific information can be only found in this section and is not contained in the standard user manual.

Key content type Summary Affected Version/s