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%

Image Removed

66%

Exasol on AWS

...

Two different Exasol offerings are available via the AWS Marketplace.

HTML
<div style="margin-left:30px">

...

width50%

...

bgColor#009e91
titleBGColor#f7f6f6
borderStyledouble
HTML
<div style="color: #FFFFFF">
HTML
<div style="font-size: 20px">

Pay-As-You-Go (PAYG)

HTML
</div>
  • Simply pay for what you use
  • Charged on an hourly basis
  • Billed through the cloud Marketplace
  • This offering includes enterprise support with 24/7 incident management

Please note: The former PAYG offering with community support has been discontinued and been superseded by this offering

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.

HTML
<p>
(Link to the marketplace offering <a class="external-link" style="color: white" href="https://aws.amazon.com/marketplace/pp/B07M718TBR" rel="nofollow">https://aws.amazon.com/marketplace/pp/B01FXIPXV4</a>
)</p>
HTML
</div>

...

width50%

...

bgColor#fcfcfc
HTML
<div style="font-size: 20px">

Bring-Your-Own-License (BYOL)

HTML
</div>
  • 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

...

For more information please contact the Exasol sales team (Contact Form)

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

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

HTML
</div>

Getting started

We recommend setting up Exasol as cluster. This offers the following advantages:

    • Scalability: easily scale out a cluster by adding additional nodes to process more data and to serve more concurrent users
    • High availability: When a nodes failes the system automatically tries to repair this node or includes a standby node into the system (if a standby node was configured).

However, for small data sizes or evaluation purposes a single-node system might be be sufficient and appropriate.

HTML
<div style="margin-left:30px">

...

bgColor#fcfcfc
borderStylenone

...

width50%

Status
colourGreen
titleNEW

Configure and deploy an Exasol cluster or single node system using our Cloud Deployment Wizard for public clouds. This tool will guide you through the sizing, configuration and deployment process. Internally it uses and parameterizes our standard CloudFormation templates (see below). After having configured your cluster you can either download the preconfigured CF template or directly open it with the AWS CloudFormation UI to proceed with the deployment proces. In the CloudFormation UI you can once more review and customize all settings.   

...

Column
width50%

Image Removed

Setting up a cluster using our CloudFormation templates is as easy as setting up a single node system.  Instruction for both setups using CloudFormation templates can be found below (You might also have a look a our Cloud Deployment wizard that guides you through the sizing and configuration process)

...

width50%

...

Cluster Installation

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

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

HTML
<div style="margin-left:30px">
Info
titleCluster Quick Launch

If you just want to start a preconfigured database 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) Image Removed  (using an existing VPC)  Image Removed    (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

HTML
</div>

...

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

...

width50%

...

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 system using an AWS CloudFormation template: 

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

HTML
<div style="margin-left:30px">
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) Image Removed  (use existing VPC)   Image Removed  (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

HTML
</div>

...

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

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

HTML
<div style="margin-left:30px">
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) Image Removed  (use existing VPC)   Image Removed  (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

...

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

HTML
<div style="margin-left:30px">
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) Image Removed  (using an existing VPC)  Image Removed    (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

HTML
</div>
HTML
-->

Support, Troubleshooting & Software Updates

...

is available through the AWS Marketplace in two variants, depending on how you want to license it.

  • Exasol Analytic Database (Single Node and Cluster, Enterprise Support)

...

The Pay-as-you-go version of Exasol 6.1 Exasol Analytic Database (Single Node and Cluster, Enterprise Support) that can be purchased via the AWS Marketplace includes 24/7 incident management.

After registration the following services are available:

...

HTML
<div style="margin-left:50px">
Info
titlePlease note
This support offering is only valid for Exasol instances launched using the AWS Marketplace offering Exasol
  • : You simply pay for what you use. You are billed through the AWS Marketplace on an hourly basis.
  • Exasol Analytic Database (Single Node and Cluster,
Enterprise Support)
  • In order to be fully eligible for support you have to register (see below). The registration process may take some days. 
  • SLAs only apply after successfully completing the onboarding process.
  • In case you need support before the registration process has been completed you may already use the "send support request" from below.
  • HTML
    </div>

    Register for Exasol PAYG support for AWS*

    ...

    Open Support Request*

    ...

    * Please note that this support offering is only valid for Exasol instances started using the AWS Marketplace offering "Exasol Analytic Database (Single Node and Cluster, Enterprise Support)"

    Exasol Analytic Database (Single Node and Cluster, Community Support)

    Note
    titleDiscontinued product

    This version has been discontinued and is no longer available to new customers.

    Users of this product should migrate to the current product including support

    HTML
    </div>

    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.

    Cluster Administration

    HTML
    <div style="margin-left:30px">
    Section
    Panel
    borderStylenone
    Column
    width50%

    Status
    colourGreen
    titleNEW

    Our new Web-based Cloud-Management UI is available now.

    If you would like to perform one of the following tasks please refer to the Cloud-plugin documentation 

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

      • Scale-Out (Add nodes): Add one or more nodes to the database cluster and database
      • Scale-Up/Down (Change instance type): Change the instance type/model of all data nodes in order to increase or decrease the overall processing power
      • Increasing disk storage capacity: Increase the overall storage capacity by enlarging the data volumes of all database nodes.

    You might have to update the plugin first. For instructions on how to update or install the plugin please refer to 

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

    Column
    width50%

    Image Removed

    Info
    titleEnhanced Failover Capabilities

    Before Exasol 6.1 for AWS a spare node had to be running all the time to provide automatic fail-safety capabilities in case of a node failure.

    Starting with 6.1 on AWS failover capabilities are also available if:

    • no spare/standby node is configured
    • a spare node was configured but suspended (not running)

    For Details please refer to

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

    HTML
    </div>

    Database System Documentation and Further Reading

    Loading Data

    If you just want to quickly find out how to load data from S3 and other sources into Exasol or how to connect Exasol to the most popular BI tools you should take a look the following guide: Getting Started

    Backup/Restore

    Jira
    serverIssue Tracker
    serverIdccda1d1d-5892-3e94-8a35-365616366603
    keySOL-354
     describes how to perform backup and restore operations using S3 ( Additional information on enhanced S3 support can be found in 
    Jira
    serverIssue Tracker
    serverIdccda1d1d-5892-3e94-8a35-365616366603
    keyEXASOL-1752
     and 
    Jira
    serverIssue Tracker
    serverIdccda1d1d-5892-3e94-8a35-365616366603
    keyEXASOL-1958
    )

    Full Documentation

    You can find the full documentation on using and administrating Exasol in the Exasol User Portal

    Furthermore the Solution Center that can also be found in the Exasol User Portal provides all kinds of problem specific guides and HowTos for using, integrating and optimizing Exasol.

    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) are supported for test and evaluation purposes only, as data in the instance store is lost when the instance is stopped.

    For production environments we recommend using high-available EBS drives, as these provide maximum reliability and durability.

    As EBS volume type we recommend using at least General Purpose SSD (gp2) volumes.

    For data backup & restore (

    Jira
    serverIssue Tracker
    serverIdccda1d1d-5892-3e94-8a35-365616366603
    keySOL-354
    as well as data import & export (
    Jira
    serverIssue Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdccda1d1d-5892-3e94-8a35-365616366603
    keyEXASOL-1774
    ) 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:

    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)

    Select "Continue"

    Select "Manual Launch"

    Select "Accept Software Terms" ( (warning) Otherwise you will not be able to succesfully launch the AMI)

    The AMI-ID can be found on the "Manual Launch" tab

    Upgrade Information

    Upgrade/migrate from discontinued PAYG offering with community support to current PAYG offering with enterprise support - Unfortunately it is generally not possible to migrate systems from one AWS Marketplace offering to another one. Please backup the data, install a new cluster, and import data in this case

    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

    ...

    Jira
    serverIssue Tracker
    serverIdccda1d1d-5892-3e94-8a35-365616366603
    keyDOWNLOAD-564

    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

    Please note 

    • BYOL): You already have a valid Exasol license for the selected configuration or if you plan to purchase an Exasol license separately.


    For details on how to use and configure Exasol on AWS please refer to the documentation portal at Getting Started with Exasol on AWS

    Column
    width34%

    Image Added