Q: What is Amazon RDS on Outposts?

Amazon RDS on AWS Outposts provides fully managed, scalable databases running on AWS Outposts in your data center. With RDS on Outposts, AWS handles time-consuming administrative tasks such as database setup, patching, and backups for databases that run on premises in your Outposts. RDS on Outposts makes it easy for you to administer a hybrid cloud database fleet because RDS databases are managed using the same AWS APIs, Console, and CLI whether they are running on Outposts or in the cloud. You can also use Amazon CloudWatch to monitor database metrics, and RDS on Outposts will automatically store database backups and snapshots in the AWS Region.

Q: What types of use cases are best suited to run on RDS on Outposts?

You can use RDS on Outposts for managing databases that run on premises for applications that require local access to the database. These include latency sensitive applications like manufacturing systems, healthcare delivery solutions, real-time trading systems, multiplayer game streaming, and more.

Q: What database engines does RDS on Outposts support?

The RDS on Outposts preview supports MySQL 5.7.26 and PostgreSQL 10.9 database engines, with support for additional database engines coming soon.

Q: Is Amazon Aurora supported on Outposts?

No. Aurora databases are not currently supported on AWS Outposts.

Q: What are the pre-requisites for using RDS on Outposts?

RDS on Outposts supports standard and memory optimized instance classes. To use RDS on your AWS Outposts infrastructure, you will need to have M5 or R5 instances available on your Outpost. RDS requires EBS for database storage and will support databases with GP2 EBS volumes. Additionally, RDS on Outposts requires a reliable network connection to the AWS Region.

Q: When I use RDS on Outposts, which data stays on premises and which data is stored in the AWS Region?

Your database and its data remain on-premises, ensuring that data is locally available. Operational data including backup/restore, snapshots, and logs are stored in the AWS Region, and database metrics are stored in Amazon CloudWatch.

Q: How do I configure RDS on Outposts for an existing Outpost instance?

There is no additional step required to configure RDS on your existing Outposts. You can start creating RDS on Outposts databases immediately by using the AWS APIs, CLI, or console and specifying the relevant Outpost ID for a given account.

Q: How do I create and manage RDS on Outposts instances?

You can create, manage, and monitor your RDS on Outposts database using the AWS console, CLI, or APIs. You can use CLI commands such as the example below:

aws rds create-db-subnet-group \
--db-subnet-group-name myoutpostdbsubnetgr \
--db-subnet-group-description "DB subnet group for RDS on Outposts" \
--subnet-ids subnet-abc123

You can use the API as in the CreateDBInstance example below:


Note: To create an RDS database on Outposts, you first need to create a DB subnet group using the CreateDBSubnetGroup API. Please refer to the RDS on Outposts documentation for more information.

Q: How do I scale my database instance up on RDS on Outposts?

You can use the AWS console or the ModifyDBInstance API to scale up DB instances, based on the capacity of the Outposts.

Q: What types of on demand DB instances are available on RDS on Outposts?

The following DB instance types will be supported for RDS on Outposts:

Standard class:

  • db.m5.large
  • db.m5.xlarge
  • db.m5.2xlarge
  • db.m5.4xlarge
  • db.m5.12xlarge
  • db.m5.24xlarge

Memory optimized class:

  • db.r5.large
  • db.r5.xlarge
  • db.r5.2xlarge
  • db.r5.4xlarge
  • db.r5.12xlarge
  • db.r5.24xlarge

Q: Does RDS on Outposts support backup and restore?

Yes. RDS on Outposts provides two different methods for backing up and restoring your DB instance(s): automated backups and database snapshots. You will need networking connectivity between your Outposts and the AWS Region to back up or restore your database.

The automated backup feature of RDS on Outposts enables point-in-time recovery of your DB instance. When automated backups are turned on for your DB instance, RDS on Outposts automatically performs a full daily snapshot of your data (during your preferred backup window) and captures transaction logs as updates to your DB instance are made. When you initiate a point-in-time recovery, transaction logs are applied to the most appropriate daily backup in order to restore your DB instance to the specific time you requested. RDS on Outposts retains backups of a DB instance for a limited, user-specified period of time called the retention period, which by default is 7 days but can be set to up to 35 days.

DB snapshots are user-initiated and can be initiated at any time. DB snapshots can be created from the AWS Console via CreateDBSnapshot API or create-db-snapshot command and are kept until you explicitly delete them.

All snapshots and transaction logs are stored in the AWS region. You can restore a DB instance from a DB snapshot either on an existing Outpost, another Outpost in the same AWS Region and account, or in the AWS Region.

Q: How does patching support work with RDS on Outposts?

Just like with RDS in the cloud, RDS on Outposts takes care of both OS and database engine patching with minimal downtime. Patching happens during a customer configurable window or when you request an immediate patching action. When a patch becomes available, you may opt in individual databases for immediate, next-window, or specified-date patching. You can also configure individual databases to automatically receive minor version upgrades as they become available.

Q: What happens to my RDS on Outposts databases when I lose connectivity to the AWS Region?

When network connectivity to the AWS Region is lost, your RDS on Outposts databases continue to run and can be accessed locally. You cannot create new databases or take new actions on existing databases. Additionally, automatic backups will also not trigger if network connectivity is down at that particular backup interval. In case of database failures, the database will not be automatically replaced. Being disconnected beyond a few hours will result in the loss of metrics and logs, and IAM policies may expire. Once connectivity is restored, RDS on Outposts will replace any databases that are not available. We recommend you restore network connectivity as soon as possible.

Q: Can I restore a database in AWS from an RDS on Outposts database snapshot?

Yes. RDS on Outposts stores the snapshots for your databases running on Outposts in the AWS Region. You can create a database in Amazon RDS in the AWS Region by restoring from those snapshots.

Q: Is encryption at rest supported?

Yes. All RDS on Outposts database instances and snapshots are encrypted at rest on Outposts and in the AWS Region using the KMS key you provide.

Q: How is RDS on Outposts priced?

RDS on Outposts is priced based on a per vCPU basis, depending on the database engine and the instance type of your choice. Please refer to the pricing page for additional information.

Q: What regions will RDS on Outposts be available in?

In preview, RDS on Outposts is available in the US East (N. Virginia) and US West (Oregon) AWS Regions. In the general availability (GA) release, RDS on Outposts will be available in all regions where Outposts is generally available.

Learn more about Amazon RDS on Outposts pricing

Visit the pricing page.

Learn more 
Sign up for a free account

Instantly get access to the AWS Free Tier. 

Sign up 
Start building in the console

Get started building with Amazon RDS in the AWS Management Console.

Sign in