Amazon Relational Database Service on AWS Outposts

Ensure a secure connection between AWS Outposts and the parent Region by using https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html or a virtual private network (VPN). If the network connection between the AWS Region and AWS Outposts is disconnected, Amazon RDS for Outposts continues to run. API calls and management tasks are unavailable until the connection is restored.

Create a database (DB) subnet group that includes one subnet associated with your Outpost by using the AWS Management Console, the , or APIs. Customer Owned IP is also available for Amazon RDS on Outposts.

Create a supported Amazon RDS on Outposts instance by using the AWS Management Console, , or APIs. Amazon RDS creates an Elastic Network Interface (ENI) in the DB subnet group specified earlier. Amazon RDS currently supports MySQL and PostgreSQL database engines and db.m5 and db.r5 instances.

For Amazon RDS on AWS Outposts backups, you can use automated backups or manual snapshots. All snapshots and transaction logs are stored in the AWS Region. By default, automatic backups are enabled for 7 days. Retention can be set to a minimum of 1 day and maximum of 35 days.

Applications in the same VPC within the same Region or on Outposts can connect to the database by using the Amazon RDS endpoint. On-premises applications can connect to the Amazon RDS database through the Outposts Local gateway Direct VPC connect.

For disaster recovery, you can restore the Amazon RDS database in the parent Region. Use a snapshot taken from the Amazon RDS instance running on AWS Outposts.

AWS Outposts supports Amazon CloudWatch metrics. For a list of supported metrics, see CloudWatch metrics for AWS Outposts.