Amazon Aurora with MySQL and PostgreSQL compatibility - AWS GovCloud (US)

Amazon Aurora with MySQL and PostgreSQL compatibility

Amazon Aurora (Aurora) is a fully managed relational database engine that's compatible with MySQL and PostgreSQL. You already know how MySQL and PostgreSQL combine the speed and reliability of high-end commercial databases with the simplicity and cost-effectiveness of open-source databases. The code, tools, and applications you use today with your existing MySQL and PostgreSQL databases can be used with Aurora. With some workloads, Aurora can deliver up to five times the throughput of MySQL and up to three times the throughput of PostgreSQL without requiring changes to most of your existing applications.

How Amazon Aurora Differs for AWS GovCloud (US)

  • Backtracking is not available.

  • Publishing Amazon Aurora MySQL Logs to Amazon CloudWatch Logs is not supported.

  • Creation of cross-Region read replicas from other AWS Regions to the AWS GovCloud (US) Regions or from AWS GovCloud (US) Regions to other AWS Regions isn't supported.

  • Copying of DB Snapshots from other AWS Regions to the AWS GovCloud (US) Regions or from AWS GovCloud (US) Regions to other AWS Regions isn't supported.

  • Amazon RDS Performance Insights isn't available in the AWS GovCloud (US) Regions.

  • Instance types and engine versions might vary in the AWS GovCloud (US) Regions. To determine instance and engine availability, see the RDS Management Console or CLI tools.

  • Database activity streams are not supported in AWS GovCloud (US).

  • Intermediate SSL certificates must be used to connect to the AWS GovCloud (US) Regions using SSL. For more information related to Intermediate certificates, see Using SSL/TLS to Encrypt a Connection.

The following Amazon Aurora editions are supported in AWS GovCloud (US) Regions:

  • Amazon Aurora MySQL-compatible edition

  • Amazon Aurora PostgreSQL-compatible edition

Documentation for Amazon Aurora

For more information about Amazon Aurora, see the Amazon Aurora documentation.

ITAR Boundary

AWS GovCloud (US) has an ITAR boundary, which defines where customers are allowed to store ITAR-controlled data for this service in AWS GovCloud (US) Regions. To maintain ITAR compliance, you must place ITAR-controlled data on the applicable part of the ITAR boundary. If you do not have any ITAR-controlled data in AWS GovCloud (US) Regions, this section does not apply to you. The following information identifies the ITAR boundary for this service:

ITAR-Regulated Data Permitted ITAR-Regulated Data Not Permitted
  • Amazon RDS master passwords are protected as ITAR-regulated data.

  • All data stored and processed in Amazon RDS database tables can contain ITAR-regulated data. You cannot transfer ITAR-regulated data in and out of your Amazon RDS instance using the API or CLI. You must use database tools for data transfer of ITAR-regulated data.

Amazon RDS metadata is not permitted to contain ITAR-regulated data. This metadata includes all configuration data that you enter when creating and maintaining your Amazon RDS instances except the master password.

Do not enter ITAR-regulated data in the following fields:

  • Database Cluster Identifier

  • Database instance identifier

  • Master user name

  • Database name

  • Database snapshot name

  • Database security group name

  • Database security group description

  • Database cluster parameter group name

  • Database cluster parameter group description

  • Database subnet group name

  • Database subnet group description

  • Event subscription name

  • Resource tags

If you are processing ITAR-regulated data with Amazon RDS, follow these guidelines in order to maintain ITAR compliance:

  • When you use the console or the AWS APIs, the only data field that is protected as ITAR-regulated data is the Amazon RDS Master Password.

  • After you create your database, change the master password of your Amazon RDS instance by directly using the database client.

  • You can enter ITAR-regulated data into any data fields by using your database client-side tools. Do not pass ITAR-regulated data by using the web service APIs that are provided by Amazon RDS.

  • To secure ITAR-regulated data in your VPC, set up access control lists (ACLs) to control traffic entering and exiting your VPC. If you have multiple databases configured with different ports, set up ACLs on all the ports.

    • For example, if you're running an application server on an Amazon EC2 instance that connects to an Amazon RDS database instance, a non-U.S. person could reconfigure the DNS to redirect ITAR-regulated data out of the VPC and into any server that might be outside of the AWS GovCloud (US-West) Region.

      To prevent this type of attack and to maintain ITAR compliance, use network ACLs to prevent network traffic from exiting the VPC on the database port. For more information, see Network ACLs in the Amazon VPC User Guide.

    • For each database instance that contains ITAR-regulated data, ensure that only specific CIDR ranges and Amazon EC2 security groups can access the database instance, especially when an Internet gateway is attached to the VPC. Only allow connections that are from the AWS GovCloud (US-West) Region or other ITAR-controlled environments to ITAR-controlled database instances.

If you are processing ITAR-regulated data with this service, use the SSL (HTTPS) endpoint to maintain ITAR compliance. For a list of endpoints, see Service Endpoints.