AWS

Amazon Web Services

Autobase will automatically set up the following in Amazon Web Services (AWS):

1. AWS EC2 Instances - a virtual machine (with a dedicated data disk), with all cluster components installed and configured.
2. AWS Network Load Balancer (NLB) to serve as the entry point for database connections.
3. AWS S3 Bucket, and configured backups using pgBackRest.

info

All components are installed within your cloud account.

Prerequisites

You will need the access key (AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY) to deploy the PostgreSQL cluster to your AWS account. See the official documentation for instructions on creating an access key.

note

You can either add these credentials in advance on the Settings page under the Secrets tab, or you will be prompted to enter them during the cluster creation process.

Console (UI)

Basic

Select AWS as the destination and choose the deployment region.

Select the type of server with the required amount of CPU and RAM.

Select the number of servers to be created for the PostgreSQL cluster.

warning

Please note that at least 3 servers are required to ensure high availability.

Specify the desired disk size for the database.

Specify your SSH public key to be able to access the database servers via SSH after deployment.

Choose which environment your database cluster belongs to.

Specify a name for your cluster.

Optionally, specify a description.

Select the PostgreSQL version to install.

Review the summary and click the "Create Cluster" button.

Expert Mode

This mode unlocks advanced settings for fine-tuning clusters, including options hidden in standard mode.
Designed for experienced users.

info

To use Expert Mode, go to the Settings page and turn on “Enable expert mode”.
(available since Autobase 2.5.1)

Select AWS as the destination and choose the deployment region.

Select the type of server with the required amount of CPU and RAM.

tip

If the required instance type is not listed, you can specify it in the CUSTOM tab.
Make sure it follows the format supported by the AWS API (e.g., r8g.xlarge).

Select the number of servers to be created for the PostgreSQL cluster.

warning

Please note that at least 3 servers are required to ensure high availability.

info

Spot instances can be used if needed.

not permanent

Spot instances are 60–90% cheaper than standard ones, making them great for testing.
However, they are not suitable for production because the cloud provider can terminate them at any time to reclaim capacity.

Specify the desired disk size for the database, along with the volume type (st1, gp3, io2) and file system type (ext4, xfs, zfs).

If needed, specify the subnet ID to which the database servers will be added. If not specified, the default VPC subnet is used.

Specify your SSH public key to be able to access the database servers via SSH after deployment.

Choose which environment your database cluster belongs to.

Specify a name for your cluster.

Optionally, specify a description.

Select the PostgreSQL version to install.

Specify the desired database name, username, and user password.

Optionally, specify connection pools for your databases, its size and mode.

Available pool modes

• session - Server is released back to pool after client disconnects.
• transaction - Server is released back to pool after transaction finishes. Recomended.
• statement - Server is released back to pool after query finishes. Transactions spanning multiple statements are disallowed in this mode.

Enable the necessary extensions for your databases.

tip

This list includes all contrib extensions and some popular third-party ones. However, more than 400 extensions are available.
To install others, specify the installation parameters manually on the YAML tab.

Configure backup settings such as the start time and retention period.

info

By default, Autobase automatically configures the settings for the selected backup tool.
If you prefer to set the parameters manually, click Configure button and specify them in the usual key=value format.

note

For pgBackRest, you can specify the global section options — the stanza section will be populated automatically.

Optionally, specify the Postgres and kernel parameters.

info

By default, Autobase automatically configures these parameters. See the default settings for Postgres and the kernel.
If you prefer to set the parameters manually, click Configure button and specify them in the usual key=value format.

Example for Postgres parameters:

Example for Kernel parameters:

Optionally, specify the Additional settings.

tip

Use the hint (?) icon for a more detailed description of each option.

Review the summary and click the "Create Cluster" button.

YAML tab

The YAML editor allows you to specify any parameters that were previously available only in command-line mode.
Designed for experienced users.

info

To use the YAML tab, go to the Settings page and turn on “Enable expert mode” and “Enable YAML tab”.
(available since Autobase 2.5.1)

Autobase offers a wide range of functionality, and not all options can be fully represented in UI forms. That’s why we added a YAML editor — it allows you to set any parameters supported by Autobase. You can see available parameters here (for cloud resources) and here (for cluster settings).

Make the necessary changes and click the "Create Cluster" button.

Wait until deployment is complete. This process takes about 10 to 15 minutes.

info

You can see the deployment log in the "Operations" page.
Select the relevant event with the "deploy" type and click "Show details" under the Actions tab.

tip

After a successful deployment, you can obtain the connection info on the cluster page.
Click on the name of your cluster on the "Clusters" page.

Example of a cluster page:

Command line

tip

📩 Contact us at [email protected], and our team will provide you with deployment instructions tailored specifically to your infrastructure, including the most suitable parameters for optimal performance and reliability.

1. Set AWS credentials

Export your AWS access key to environment variables:

export AWS_ACCESS_KEY_ID=<value>
export AWS_SECRET_ACCESS_KEY=<value>

2. Run the Deployment Command

Execute the following command to deploy a PostgreSQL cluster (example):

docker run --rm -it \
  --env AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID} \
  --env AWS_SECRET_ACCESS_KEY=${AWS_SECRET_ACCESS_KEY} \
  autobase/automation:2.5.1 \
    ansible-playbook deploy_pgcluster.yml --extra-vars \
      "ansible_user=ubuntu \
       cloud_provider='aws' \
       cloud_load_balancer=true \
       server_count=3 \
       server_type='m7i.xlarge' \
       server_image='ami-034568121cfdea9c3' \
       server_location='us-east-1' \
       volume_size=100 \
       postgresql_version=18 \
       patroni_cluster_name='postgres-cluster-01' \
       ssh_public_keys='ssh-rsa AAAAB3NzaC1yc2EAAAA******whzcMINzKKCc7AVGbk='"

Key parameters:

• cloud_provider: Specifies Amazon Web Services (AWS) as the provider.
• cloud_load_balancer: Adds an AWS Network Load Balancer (NLB) to the cluster.
• server_count: Number of servers in the cluster (at least 3 servers are needed for high availability).
• server_type: Type of servers (e.g., 'm7i.xlarge' for 4 vCPU 16 GB RAM).
• server_image: Operating system image for the servers (e.g., 'ami-034568121cfdea9c3' for Ubuntu 24.04).
• server_location: Server location (e.g., 'us-east-1' for US East N. Virginia).
• volume_size: Disk size (in GB) for the database.
• postgresql_version: PostgreSQL version.
• patroni_cluster_name: PostgreSQL cluster name.
• ssh_public_keys: Your SSH public key to access the database servers after deployment.

note

See the default automation variables for more details, including the list of available variables for cloud resources.

3. Wait until deployment is complete

This process takes about 10 to 15 minutes.

info

After a successful deployment, the connection information can be found in the Ansible log.