Basic Deployment

This section explains how to create a basic deployment of Exasol 8 on AWS using Exasol Deployment Tool (c4).


  • AMI running Ubuntu 20.04 LTS/22.04 LTS with jq JSON processor installed

  • Server access to official Ubuntu package repositories (required for automatic installation of any missing dependencies)

  • Exasol Deployment Tool (c4) must be installed on your system. For more information, see Install c4.

  • EC2 security group rules in AWS must be configured to allow traffic on the necessary ports. For more information, see Network Settings.

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, -N3 will 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 @exasol-<version>.

    For information about the latest available Exasol version, see Release Notes.

For example: to create a deployment with 3 active nodes running Exasol 8.27.0 using the default CloudFormation template:

$ c4 aws play -N 3 -T @exasol-8.27.0

The deployment can take up to 20 minutes to complete depending on various factors such as the number of node instances.

  • For more information about the available options with the c4 play command, use c4 play --help .

  • For information about AWS specific deployment options, use c4 aws --help.

Monitor deployments

To monitor the status of your deployments, use c4 ps.

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
  ┌─  1  3a4a7d8d  10    awscf   c5d.large    c      running    04:35:15  +∞
  │   1  3a4a7d8d  11    awscf   c5d.2xlarge    d      running    04:35:16  +∞
  │   1  3a4a7d8d  12    awscf   c5d.2xlarge    d      running    04:35:16  +∞
  └─  1  3a4a7d8d  13    awscf   c5d.2xlarge    d      running    04:35:15  +∞

Node 10 in this example is the database access node. Since the database does not run on the access node, its final stage is stage c.

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 log output of the deployment process will then be presented on the terminal screen.

Troubleshooting c4 ps

In some cases c4 ps may time out while waiting for an instance to respond during the deployment process. This can for example be the case if there is a large geographical distance between the system running c4 ps and the instances. If the instance does not respond within the timeout period, c4 ps will consider the instance to be unreachable and report it as being in deployment stage a, even if the instance has booted up and services are running on the node.

You can increase the time limit for c4 ps to wait for instances to respond by setting a higher value in the CCC_USER_PS_REMOTE_TIMEOUT parameter in the c4 configuration. The default value is 3000 ms. For example, to set the timeout to 10 seconds:


For more information on how to configure c4 and about the different 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 a database client. Use the following attribute values in the connection:


Comma-separated list of the external IP addresses of the database nodes.

For example:,,,

The external IP addresses of the nodes are shown in the EXTERNAL_IP column in c4 ps.


Value of the CCC_PLAY_DB_PORT parameter.

The default port if this parameter is not set is 8563.

Username sys

Value of the CCC_PLAY_DB_PASSWORD parameter.

The default password if this parameter is not set is aX1234567.

For more information about how to connect to your Exasol database using database clients and other tools, see Connect to Exasol .

When you are connected to the database, change the default password of the sys user as soon as possible to a secure password using the ALTER USER command.

You can also connect to the database using the built-in SQL client in c4. For more information, see How to use c4.

Next steps

Upload a License

All Exasol deployments start with a license that allows you to load 10 GB of raw data for testing purposes. For larger data sizes, you must upload a license to the database.

Connect to Exasol

This section describes how to connect to your Exasol database using various database clients and other tools that are compatible with the Exasol drivers and programming languages.

Load Data

Once you are connected to your Exasol database, you can start loading data from various sources. This section describes different methods, tools, and best practices for loading and processing your data.

Advanced Deployment

This section describes how to configure more advanced deployment options, such as using existing VPCs and security groups, disabling the use of Elastic IP addresses, and setting up AWS availability zones.