This section explains how to use Exasol Deployment Tool (c4) to create a basic deployment of Exasol 8 on Amazon Web Services (AWS).
AMI running Ubuntu 20.04 LTS/22.04 LTS or with jq JSON processor installed
Server access to official Ubuntu package repositories (required for automatic installation of any missing dependencies).
Exasol Deployment Tool (c4) is a command-line application that is used for deploying Exasol on cloud platforms as well as for on-premises installation.
If you download c4 from the Download Portal you must use
chmod +x c4to make c4 executable for all users, otherwise the application will not be able to run the installation. For more information, see Install c4.
Configure c4 for AWS deployment. For more information, see Configure c4 for AWS.
Step 2: Create a Deployment
To create a deployment on AWS, use
c4 aws play -N <nodes> -T <package>.
-N= The number of database nodes to deploy. For example,
-N3will deploy 3 database nodes.
-T= Use CloudFormation template. The default template is used unless a template is defined in the c4 configuration.
package= The Exasol package to install, using the format
For information about the latest available Exasol version, see Release Notes.
For example: to create a deployment with 3 active nodes running Exasol 8.23.4 using the default CloudFormation template:
The deployment can take up to 20 minutes to complete depending on various factors such as the number of node instances.
Additional Deployment Options
For information about additional options for more advanced deployment scenarios, see Advanced Deployment.
The help system in c4 also provides information about all available commands and configuration parameters.
For information about additional AWS specific deployment options, use
c4 aws --help.
For information about generic cloud deployment options, use
c4 play --help.
Monitor Deployment Status
To monitor the status of your deployment, use
The deployment is finished when the database nodes in
c4 ps have reached stage d and are in the running state. For example:
$ c4 ps
N PLAY_ID NODE MEDIUM INSTANCE IP CORED COS XMLRPC STAGE STATE UPTIME TTL
┌─ 1 a016a6ae 10 awscf c5d.large 203.0.113.242 325 20002 20003 c running 00:09:31 +∞
│ 1 a016a6ae 11 awscf c5d.2xlarge 203.0.113.160 325 20002 20003 d running 00:09:30 +∞
│ 1 a016a6ae 12 awscf c5d.2xlarge 203.0.113.2 325 20002 20003 d running 00:09:30 +∞
└─ 1 a016a6ae 13 awscf c5d.2xlarge 203.0.113.166 325 20002 20003 d running 00:09:31 +∞
Node 10 is the database access node, which is required for using the Administration API. The database does not run on the access node, which means that you cannot connect to the database using the IP address of this node.
To view the progress of the deployment process you can add the
-C option to the
c4 play command, or connect to the deployment using
c4 connect -t <NODE> when the process has started. The progress of the deployment will then be presented on the terminal screen.
For more information about the deployment stages and states, see How to use c4.
For more details about the c4 ps command, use
c4 ps --help.
Connect to the Database
Once the database is running you can connect to it using your preferred SQL client.
You can also connect to the database using the built-in SQL client in c4 by using the command
c4 connect -t1/db. For more information, see How to use c4.
The built-in SQL client in c4 always runs in autocommit mode.
When connecting using a SQL Client, use the following attribute values in the connection:
|Comma-separated list of the IP addresses in the
IP column of
|Value of the
CCC_PLAY_DB_PORT parameter. Default is 8563.
|Value of the
CCC_PLAY_DB_PASSWORD parameter. The default password if the parameter is not set is
Change the default password of the sys user to a secure password as soon as possible using the ALTER USER command.