Q: What is RDS on Outposts?
Amazon RDS on AWS Outposts provides fully managed, scalable databases running on AWS Outposts in customers’ data centers. RDS automates time-consuming administrative tasks such as database setup, patching, and backups for databases that run on-premises on Outposts. RDS makes it easy for you to manage a hybrid-cloud database fleet via a single pane of glass using AWS RDS console, the same RDS APIs, and CLI, to manage the RDS databases running in the AWS region and on Outposts.
Q: What types of use cases are best suited to run on RDS on Outposts?
You can use Amazon RDS on Outposts for managing databases that need to run on-premises for applications that need local access to the databases. This includes applications such as manufacturing equipment, IoT devices, etc. You can create and manage RDS databases running on Outposts using the same AWS APIs, CLI, and console.
Q: Does RDS on Outposts support data residency use cases that require all data to remain on-premises?
RDS on Outposts stores database backups and logs in the AWS region today, it does not support use cases that require all data to remain in a customer’s data center.
Q: What type of database engines does RDS on Outposts support?
MySQL 8.0.17 and PostgreSQL 12.2 database engines will be supported at Outposts GA.
Q: Does RDS on Outposts support Amazon Aurora?
No, Aurora is not currently supported on Outposts.
Q: What regions is RDS on Outposts available in?
RDS on Outposts is available in all regions where Outposts is supported.
Q: How will RDS on Outposts be priced?
RDS on Outposts pricing is based on a per-instance hour management fee for each database managed. Refer to RDS on Outposts pricing page.
Q: What are the pre-requisites for using RDS on Outposts?
RDS on Outposts supports standard and memory-optimized instance classes, the underlying Outposts must support the same EC2 instances in order for the customer to create the corresponding DB instances. RDS on Outposts requires a reliable network connection to the AWS region from your Outposts.
Q: What type of on-demand DB instances are supported with RDS on Outposts?
The following DB instance types will be supported for RDS on Outposts based on instances supported by Outposts. You can choose general purpose (SSD) storage for the databases.
Memory Optimized class:
Q: How do I create RDS databases on Outposts?
Before you create an RDS on Outposts DB instance, you need to create a DB subnet group that includes one subnet that is associated with your Outpost. When you create an RDS on Outposts DB instance, specify this DB subnet group. An example is below:
aws rds create-db-subnet-group --db-subnet-group-name outposts-rds-sg --db-subnet-group-description poc --subnet-ids <outpost-subnet>
aws rds create-db-instance --db-instance-identifier outpost-instance --engine mysql --engine-version 8.0.17 --db-instance-class db.m5.large --master-username master --master-user-password password --allocated-storage 20 --db-subnet-group-name outpost-rds-sg --storage-type gp2 --storage-encrypted
Q: How do I scale my database up on Outposts?
You can use AWS CLI command modify-db-instance to scale up DB instances to scale your database instances. Based on the available capacity on Outpost, RDS on Outposts will support this operation.
Q: Does RDS on Outposts support backups and restore?
Yes. RDS provides two different methods for backing up and restoring your DB instance(s), automated backups, and database snapshots (DB Snapshots). You will need networking connectivity between your Outposts and the AWS region to back up or restore your database.
When automated backups are turned on for your DB instance, RDS 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). Amazon RDS 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 Console, via CreateDBSnapshot API, or create-db-snapshot command and are kept until you explicitly delete them.
All the 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 region and account or in the AWS region.
Q: Does RDS on Outposts support patching my databases?
Yes. RDS takes care of both OS and database engine patching with minimal downtime. Patching happens during a customer configurable maintenance window (30 min to 12 hours) or when you request an immediate patching action. When a patch becomes available, you may opt individual databases in 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 databases when I lose connectivity to my Outposts?
When network connectivity to the AWS region goes down, your database continues to run locally. You cannot create new databases or take new actions on existing the database, automatic backups will also not trigger at that particular interval while connectivity is not available. In the case of database failures, the database will not be automatically replaced until the connectivity is restored. 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 AWS Outposts stores the snapshots for your databases running on AWS Outposts in the AWS region. You can create a database in AWS by restoring from those snapshots.
Q: Is encryption at rest supported?
Yes. All database instances and snapshots are encrypted at rest on Outposts and in the AWS region using the KMS key you provide.