Working with Amazon RDS on Amazon Outposts - Amazon Relational Database Service
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Working with Amazon RDS on Amazon Outposts

Amazon RDS on Amazon Outposts extends RDS for SQL Server, RDS for MySQL, and RDS for PostgreSQL databases to Amazon Outposts environments. Amazon Outposts uses the same hardware as in public Amazon Web Services Regions to bring Amazon services, infrastructure, and operation models on-premises. With RDS on Outposts, you can provision managed DB instances close to the business applications that must run on-premises. For more information about Amazon Outposts, see Amazon Outposts.

You use the same Amazon Web Services Management Console, Amazon CLI, and RDS API to provision and manage on-premises RDS on Outposts DB instances as you do for RDS DB instances running in the Amazon Web Services Cloud. RDS on Outposts automates tasks, such as database provisioning, operating system and database patching, backup, and long-term archival in Amazon S3.

RDS on Outposts supports automated backups of DB instances. Network connectivity between your Outpost and your Amazon Web Services Region is required to back up and restore DB instances. All DB snapshots and transaction logs from an Outpost are stored in your Amazon Web Services Region. From your Amazon Region, you can restore a DB instance from a DB snapshot to a different Outpost. For more information, see Introduction to backups.

RDS on Outposts supports automated maintenance and upgrades of DB instances. For more information, see Maintaining a DB instance.

RDS on Outposts uses encryption at rest for DB instances and DB snapshots using your Amazon KMS key. For more information about encryption at rest, see Encrypting Amazon RDS resources.

By default, EC2 instances in Outposts subnets can use the Amazon Route 53 DNS Service to resolve domain names to IP addresses. You might encounter longer DNS resolution times with Route 53, depending on the path latency between your Outpost and the Amazon Web Services Region. In such cases, you can use the DNS servers installed locally in your on-premises environment. For more information, see DNS in the Amazon Outposts User Guide.

When network connectivity to the Amazon Web Services Region isn't available, your DB instance continues to run locally. You can continue to access DB instances using DNS name resolution by configuring a local DNS server as a secondary server. However, you can't create new DB instances or modify existing DB instances. Automatic backups don't occur when there is no connectivity. If there is a DB instance failure, the DB instance isn't automatically replaced until connectivity is restored. We recommend restoring network connectivity as soon as possible.

Prerequisites for Amazon RDS on Amazon Outposts

The following are prerequisites for using Amazon RDS on Amazon Outposts:

  • Install Amazon Outposts in your on-premises data center. For more information about Amazon Outposts, see Amazon Outposts.

  • Make sure that you have at least one subnet available for RDS on Outposts. You can use the same subnet for other workloads.

  • Make sure that you have a reliable network connection between your Outpost and an Amazon Region.