reference deployment
Amazon RDS on AWS
Operate, manage, and scale your Amazon RDS databases in the cloud
This solution was developed by AWS solutions architects.
-
What you'll build
-
How to deploy
-
Cost and licenses
-
What you'll build
-
This solution sets up the following:
- A highly available architecture that spans two Availability Zones.*
- A virtual private cloud (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 cluster that includes a write replica in one Availability Zone and a read replica in the other.
- 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.
- Identify an email distribution list to use for notifications.
- Identify the database engine versions that your applications support and select the optimal choice to deploy.
- Sign in to your AWS account. If you don’t have an AWS account, sign up at https://aws.amazon.com.
- 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:
- Deploy Amazon RDS for PostgreSQL into a new VPC.
- Deploy Amazon RDS for PostgreSQL into an existing VPC.
- Deploy Amazon RDS for MySQL into a new VPC.
- Deploy Amazon RDS for MySQL into an existing VPC.
- Deploy Amazon RDS for Microsoft SQL Server into a new VPC.
- Deploy Amazon RDS for Microsoft SQL Server into an existing VPC.
- Deploy Amazon RDS for MariaDB into a new VPC.
- Deploy Amazon RDS for MariaDB into an existing VPC.
- Deploy Amazon RDS for Oracle into a new VPC.
- Deploy Amazon RDS for Oracle into an existing VPC.
- Deploy Amazon RDS for PostgreSQL into a new VPC.
- Test the solution.
- Identify an email distribution list to use for notifications.
-
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?
