AWS Resources

This article explains which resources are created in your AWS account when you deploy Exasol.

When you create a native cloud deployment of Exasol in AWS, the deployment process will create a number of resources in the AWS account. Which resources are created depends on the configuration. For more details about how different configuration options will affect the billing for your deployment, you can use the AWS Pricing Calculator.

The following resources are created in a typical deployment scenario:

Resource type Description
EC2 instances

One instance is created for each node. For example, in a deployment with 4 data nodes, one reserve node, and an access node, 6 instances are created. For guidelines on which instance type to choose, see Sizing Considerations.
EC2 security group

A security group for describing firewall rules for your deployment.

For more information about security groups, see Control traffic to your AWS resources using security groups.

If you define an existing security group in the CCC_AWS_SECURITY_GROUP_ID configuration parameter, a security group is not created. For more information, see Advanced Deployment.
Virtual Private Cloud (VPC)

A VPC is a a logically isolated virtual network where your Exasol instances run. The deployment process creates a new VPC including all necessary related resources in the account by default.

If you set the configuration parameter CCC_AWS_NEW_VPC=false, a VPC is not created. You must then define an existing VPC where the deployment will run. For more information, see Advanced Deployment.
VPC endpoints

VPC endpoints allow instances to connect to selected AWS services without having internet access. The following endpoints are created:

  • SSM Messages

  • SSM

  • CloudFormation

  • EC2

  • S3

  • KMS

For more information about Amazon VPC endpoints, see What are VPC endpoints?.
EC2 internet gateway

A gateway that enables internet access to the VPC.

If you set the configuration parameter CCC_AWS_NEW_VPC=false, this resource is not created.
Elastic IP (EIP)

A public IP address is created for each instance. For more information, see Elastic IP addresses.

If you set the configuration parameter CCC_AWS_USE_EIP=false the instances will not get EIP addresses. For more information, see Advanced Deployment.
Authentication tokens The deployment process generates tokens that COS uses to authenticate nodes to each other. A random token is also generated to force CloudFormation template updates in certain scenarios.