reference deployment

Amazon RDS for PostgreSQL

Operate, manage, and scale your PostgreSQL database in the cloud

This solution deploys Amazon Relational Database Service (Amazon RDS) for PostgreSQL in the Amazon Web Services (AWS) Cloud. With the default settings, an Amazon RDS for PostgreSQL cluster is deployed to a private subnet in a new virtual private cloud (VPC) with an Amazon RDS read replica in one Availability Zone and a write replica in another zone. Native replication mechanisms available with PostgreSQL ensure that the read replica stays in sync with the source database. The deployment also includes access to Amazon CloudWatch metrics and logs, event notifications, and data encryption.
AWS logo

This solution was developed by AWS solutions architects.

  •  What you'll build
  • This solution sets up the following:

    • A highly available architecture that spans two Availability Zones.*
    • A VPC configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.*
    • In the public subnets:
      • Managed NAT gateways to allow outbound internet access for resources in the private subnets.*
      • An optional Linux bastion host in an Auto Scaling group to allow inbound SSH (Secure Shell) access to Amazon Elastic Compute Cloud (Amazon EC2) instances in public and private subnets.*
    • In the private subnets:
      • An Amazon RDS for PostgreSQL cluster that includes a write replica in one Availability Zone and a read replica in the other.
    • Amazon CloudWatch metrics for monitoring the database instance and CloudWatch logs for storing database logs.
    • An Amazon Simple Notification Service (Amazon SNS) topic for sending CloudWatch alarm and Amazon RDS event notifications.
    • AWS Key Management Service (AWS KMS) for encrypting the data stored in the database instance.

    *  The template that deploys the solution into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.

  •  How to deploy
  • To deploy this solution, follow the instructions in the deployment guide, which includes these steps.

    1. Identify an email distribution list to use for notifications.
    2. Identify which PostgreSQL versions that your application(s) support, and select the optimal choice.
    3. Sign in to your AWS account. If you don’t have an AWS account, sign up at
    4. Launch the solution. The stack takes about 30 minutes to deploy. Before you create the stack, choose the AWS Region from the top toolbar. Choose one of the following options:
    5. Test the solution.
  •  Cost and licenses
  • You are responsible for the cost of the AWS services and any third-party licenses used while running this solution. There is no additional cost for using the solution.

    This solution includes configuration parameters that you can customize. Some of these settings, such as instance type, affect the cost of deployment. For cost estimates, refer to the pricing pages for each AWS service you use. Prices are subject to change.

    Tip: After you deploy a solution, create AWS Cost and Usage Reports to track associated costs. These reports deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. They provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information, refer to What are AWS Cost and Usage Reports?