Basic Deployment using c4
This section explains how to use the Exasol Deployment Tool (c4) for a basic deployment of Exasol 8 on Amazon Web Services (AWS).
Prerequisites
- AWS account with an active Exasol subscription
- Exasol deployment tool (c4) installed and configured on a Ubuntu 20.04 LTS AMI. For more information, see Install c4
- Server access to official Ubuntu package repositories for updates
- Relevant permissions for the AWS user creating the database. For more information, see Configure c4 for AWS.
Create a Deployment
To create a deployment, use the c4 aws play
command.
The following example creates a database with 3 active nodes running Exasol 8.15.0 using the default CloudFormation template.
-N
= the number of database nodes to deploy. For example,-N3
will deploy 3 database nodes.-T
= use CloudFormation template@exasol-8.18.1
= pointer to the Exasol release version on AWS
For information about the latest available Exasol version, see Release Notes.
The deployment can take up to 20 minutes to complete depending on various factors such as the number of node instances.
Additional Deployment Options
The deployment is based on c4 configuration parameters that are defined in the configuration files and (optionally) on the command line. For more information about specifying additional parameters for more advanced deployments, see Parameters in c4 and Advanced Deployment. The help system in c4 also provides information about the 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
.
Monitoring Deployment
You can monitor the status of your deployment using c4 ps
. For more information about the deployment stages and states, see Monitor Deployments.
For more details about the deployment, for example to see the CloudFormation logs, connect to the deployment using c4 connect -t 1
after it is created or specify the -C
option when creating the deployment. The progress of the deployment will then be shown in real time in the terminal window.
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 EXTERNAL_IP INTERNAL_IP STAGE STATE UPTIME TTL
┌─ 1 3a4a7d8d 10 awscf c5d.large 203.0.113.10 10.0.0.10 c running 04:35:15 +∞
│ 1 3a4a7d8d 11 awscf c5d.2xlarge 203.0.113.11 10.0.0.11 d running 04:35:16 +∞
│ 1 3a4a7d8d 12 awscf c5d.2xlarge 203.0.113.12 10.0.0.11 d running 04:35:16 +∞
└─ 1 3a4a7d8d 13 awscf c5d.2xlarge 203.0.113.13 10.0.0.13 d running 04:35:15 +∞
In the example above, node 10 is the access node, which is used to interact with the cluster nodes using the Administration API. The database does not run on the access node, and you cannot connect to the database using the IP address of this node.
Connect to the Database
Once the database is running you can connect to it using SQL Clients, or using c4 with the command c4 connect -t1/db
.
The built-in SQL client in c4 always runs in autocommit mode.
When connecting using a SQL Client the following attributes are used:
Attribute | Value |
---|---|
Hostname | Comma-separated list of IP addresses in the IP column of c4 ps . |
Port | Value of the CCC_PLAY_DB_PORT parameter. Default is 8563. |
Username | sys |
Password | Value of the CCC_PLAY_DB_PASSWORD parameter. The default password if the parameter is not set is aX1234567 . |
Change the default password of the sys user to a secure password using the ALTER USER command.
Next Steps
To learn more about how to administer your Exasol database and which tools are used, see Administration Tools.