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
Column
Panel

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)   (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

HTML
</div>


In case you need full control over all parameters (e.g. setting the AMI-ID manually or configuring the number and size of the attached data disks) you might use our advanced templates:

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

Column
Panel

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)   (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

HTML
</div>


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




...