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

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section

Table of Contents

Column
width50%


Table of Contents

Column
width50%

Exasol on AWS versions in the AWS Marketplace

Section
Column
width40%
Panel
titleBGColor#f7f6f6
borderStyledouble
titlePay-As-You-Go (PAYG)
  • Simply pay for what you use
  • Charged on an hourly basis
  • Billed through the cloud Marketplace
  • This offering includes community support


Info

This is the default version used in the deployment templates.

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

(Link to marketplace offering https://aws.amazon.com/marketplace/pp/B01FXIPXV4)

Column
width40%
Panel
titleBring-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





(Link to marketplace offering: https://aws.amazon.com/marketplace/pp/B01IVOPPN8)


Info
titleRecommendations

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


Getting started

Single node installation

The recommended single-node installation method is AWS CloudFormation. The following guide explains step-by-step how to conveniently deploy an Exasol single node database system using an AWS CloudFormation template: 

Jira
serverIssue Tracker
serverIdccda1d1d-5892-3e94-8a35-365616366603
keySOL-633


Info
titleSingle Node Quick Launch

In case just want to start a preconfigured single node system as quickly as possible just follow the instruction below:

Expand
titleQuick Launch Instructions (Click to Expand)

Click one of the buttons below (the left one if you want to deploy the node to an existing VPC, the right button if you want to create a new VPC) to iniate a preconfigured CloudFormation based deployment of a sinlge-node system (good for approx. 500GB of uncompressed raw data).

1)   (use existing VPC)     (generate new VPC) 

2) Just press "Next" to proceed to the configuration options, then define passwords for the administrative users, select the target spress 2 times "Next".

3) Acknowledge the statement (checkbox) at the bottom of the screen and start the deployment by pressing the create button.

Please note that the deployment may take approximately 15-25 minutes before you can connect to the system.

For more information on the configuration parameters, how to change the configuration and how to connect to the database please refer to the full guide:

Jira
serverIssue Tracker
serverIdccda1d1d-5892-3e94-8a35-365616366603
keySOL-633

In case the installation via CloudFormation is not possible (e.g. due to missing user privileges) you can install Exasol using the AWS console or the markeplace page as well. The following guide explains how: 

Jira
serverIssue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdccda1d1d-5892-3e94-8a35-365616366603
keySOL-377

Cluster Installation

The recommended cluster installation method is AWS CloudFormation. The following guide explains step-by-step how to conveniently deploy an Exasol cluster using an AWS CloudFormation template::  

Jira
serverIssue Tracker
serverIdccda1d1d-5892-3e94-8a35-365616366603
keySOL-605

Info
titleCluster Quick Launch

If you just want to start a preconfigured cluster as quickly as possible just follow the instruction below:

Expand
titleQuick Launch Instructions (Click to Expand)

Click one of the buttons below (the left on if you want to use an existing VPC, the right button otherwise) to iniate a preconfigured CloudFormation based deployment of a 5-node cluster (good for approx. 2 TB of uncompressed raw data).

1)   (using an existing VPC)      (generating a new VPC)

2) Just press "Next" to proceed to the configuration options, then define passwords for the administrative users, select the target spress 2 times "Next".

3) Acknowledge the statement (checkbox) at the bottom of the screen and start the deployment by pressing the create button.

Please note that the deployment may take approximately 20-30 minutes before you can connect to the system.

For more information on the configuration parameters, how to change the configuration and how to connect to the database please refer to the full guide:

Jira
serverIssue Tracker
serverIdccda1d1d-5892-3e94-8a35-365616366603
keySOL-605


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 

Jira
serverIssue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdccda1d1d-5892-3e94-8a35-365616366603
keySOL-382
 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 (
    Jira
    serverIssue Tracker
    serverIdccda1d1d-5892-3e94-8a35-365616366603
    keySOL-354
    as well as data import & export (
    Jira
    serverIssue Tracker
    serverIdccda1d1d-5892-3e94-8a35-365616366603
    keyEXASOL-1678
    ) 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 https://aws.amazon.com/marketplace/pp/B01FXIPXV4 (Pay-As-You-Go, community support only) or https://aws.amazon.com/marketplace/pp/B01IVOPPN8 (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

Jira
serverIssue Tracker
serverIdccda1d1d-5892-3e94-8a35-365616366603
keyEXASOL-2161

Jira
serverIssue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdccda1d1d-5892-3e94-8a35-365616366603
keyEXASOL-2032

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:
    Jira
    serverIssue Tracker
    serverIdccda1d1d-5892-3e94-8a35-365616366603
    keyDOWNLOAD-564

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.


Jira
serverIssue Tracker
columnskey,content type,summary,versions
maximumIssues20
jqlQueryproject = SOL AND ("Category 1" in ("EXASOL on AWS") OR "Category 2" in ("EXASOL on AWS")) and status=Published ORDER BY resolved DESC
serverIdccda1d1d-5892-3e94-8a35-365616366603