Regions, Availability Zones, and Local Zones - Amazon Relational Database Service

Regions, Availability Zones, and Local Zones

Amazon cloud computing resources are hosted in multiple locations world-wide. These locations are composed of AWS Regions, Availability Zones, and Local Zones. Each AWS Region is a separate geographic area. Each AWS Region has multiple, isolated locations known as Availability Zones.

Note

For information about finding the Availability Zones for an AWS Region, see Describing your Regions, Availability Zones, and Local Zones in the Amazon EC2 documentation.

By using Local Zones, you can place resources, such as compute and storage, in multiple locations closer to your users. Amazon RDS enables you to place resources, such as DB instances, and data in multiple locations. Resources aren't replicated across AWS Regions unless you do so specifically.

Amazon operates state-of-the-art, highly-available data centers. Although rare, failures can occur that affect the availability of instances that are in the same location. If you host all your instances in a single location that is affected by such a failure, none of your instances is available.


			AWS Region

It is important to remember that each AWS Region is completely independent. Any Amazon RDS activity you initiate (for example, creating database instances or listing available database instances) runs only in your current default AWS Region. The default AWS Region can be changed in the console, by setting the EC2_REGION environment variable, or it can be overridden by using the --region parameter with the AWS Command Line Interface (AWS CLI). For more information, see Configuring the AWS Command Line Interface, specifically the sections about environment variables and command line options.

Amazon RDS supports a special AWS Region called AWS GovCloud (US-West) that is designed to allow US government agencies and customers to move more sensitive workloads into the cloud. AWS GovCloud (US-West) addresses the US government's specific regulatory and compliance requirements. For more information about AWS GovCloud (US-West), see What is AWS GovCloud (US-West)?

To create or work with an Amazon RDS DB instance in a specific AWS Region, use the corresponding regional service endpoint.

AWS Regions

Each AWS Region is designed to be isolated from the other AWS Regions. This design achieves the greatest possible fault tolerance and stability.

When you view your resources, you see only the resources that are tied to the AWS Region that you specified. This is because AWS Regions are isolated from each other, and we don't automatically replicate resources across AWS Regions.

Availability Zones

When you create a DB instance, you can choose an Availability Zone or have AWS choose one for you. An Availability Zone is represented by an AWS Region code followed by a letter identifier (for example, us-east-1a).

In some cases, you might distribute your DB instances across multiple Availability Zones in a Multi-AZ deployment. In such cases, if one DB instance fails, you can design your application so that a DB instance in another Availability Zone can handle requests. For more information about Multi-AZ deployments, see High availability (Multi-AZ) for Amazon RDS.

Local Zones

A Local Zone is an extension of an AWS Region that is geographically close to your users. You can extend any VPC from the parent AWS Region into Local Zones by creating a new subnet and assigning it to the AWS Local Zone. When you create a subnet in a Local Zone, your VPC is extended to that Local Zone. The subnet in the Local Zone operates the same as other subnets in your VPC.

When you create a DB instance, you can choose a subnet in a Local Zone. Local Zones have their own connections to the internet and support AWS Direct Connect. Thus, resources created in a Local Zone can serve local users with very low-latency communications. For more information, see AWS Local Zones.

A Local Zone is represented by an AWS Region code followed by an identifier that indicates the location, for example us-west-2-lax-1a.

Note

A Local Zone can't be included in a Multi-AZ deployment.

To use a Local Zone

  1. Enable the Local Zone in the Amazon EC2 console.

    For more information, see Enabling Local Zones in the Amazon EC2 User Guide for Linux Instances.

  2. Create a subnet in the Local Zone.

    For more information, see Creating a subnet in your VPC in the Amazon VPC User Guide.

  3. Create a DB subnet group in the Local Zone.

    When you create a DB subnet group, choose the Availability Zone group for the Local Zone.

    For more information, see Creating a DB instance in a VPC.

  4. Create a DB instance that uses the DB subnet group in the Local Zone.

    For more information, see Creating an Amazon RDS DB instance.

Important

Currently, Local Zones are only available in the US West (Oregon) Region. In this AWS Region, the Los Angeles AWS Local Zone is available.

Region availability

The following table shows the AWS Regions where Amazon RDS is currently available and the endpoint for each Region.

Region Name Region Endpoint Protocol
US East (Ohio) us-east-2

rds.us-east-2.amazonaws.com

rds-fips.us-east-2.amazonaws.com

HTTPS

HTTPS

US East (N. Virginia) us-east-1

rds.us-east-1.amazonaws.com

rds-fips.us-east-1.amazonaws.com

HTTPS

HTTPS

US West (N. California) us-west-1

rds.us-west-1.amazonaws.com

rds-fips.us-west-1.amazonaws.com

HTTPS

HTTPS

US West (Oregon) us-west-2

rds.us-west-2.amazonaws.com

rds-fips.us-west-2.amazonaws.com

HTTPS

HTTPS

Africa (Cape Town) af-south-1 rds.af-south-1.amazonaws.com HTTPS
Asia Pacific (Hong Kong) ap-east-1 rds.ap-east-1.amazonaws.com HTTPS
Asia Pacific (Mumbai) ap-south-1 rds.ap-south-1.amazonaws.com HTTPS
Asia Pacific (Osaka-Local) ap-northeast-3 rds.ap-northeast-3.amazonaws.com HTTPS
Asia Pacific (Seoul) ap-northeast-2 rds.ap-northeast-2.amazonaws.com HTTPS
Asia Pacific (Singapore) ap-southeast-1 rds.ap-southeast-1.amazonaws.com HTTPS
Asia Pacific (Sydney) ap-southeast-2 rds.ap-southeast-2.amazonaws.com HTTPS
Asia Pacific (Tokyo) ap-northeast-1 rds.ap-northeast-1.amazonaws.com HTTPS
Canada (Central) ca-central-1

rds.ca-central-1.amazonaws.com

rds-fips.ca-central-1.amazonaws.com

HTTPS

HTTPS

China (Beijing) cn-north-1 rds.cn-north-1.amazonaws.com.cn HTTPS
China (Ningxia) cn-northwest-1 rds.cn-northwest-1.amazonaws.com.cn HTTPS
Europe (Frankfurt) eu-central-1 rds.eu-central-1.amazonaws.com HTTPS
Europe (Ireland) eu-west-1 rds.eu-west-1.amazonaws.com HTTPS
Europe (London) eu-west-2 rds.eu-west-2.amazonaws.com HTTPS
Europe (Milan) eu-south-1 rds.eu-south-1.amazonaws.com HTTPS
Europe (Paris) eu-west-3 rds.eu-west-3.amazonaws.com HTTPS
Europe (Stockholm) eu-north-1 rds.eu-north-1.amazonaws.com HTTPS
Middle East (Bahrain) me-south-1 rds.me-south-1.amazonaws.com HTTPS
South America (São Paulo) sa-east-1 rds.sa-east-1.amazonaws.com HTTPS
AWS GovCloud (US-East) us-gov-east-1

rds.us-gov-east-1.amazonaws.com

rds.us-gov-east-1.amazonaws.com

HTTPS

HTTPS

AWS GovCloud (US) us-gov-west-1

rds.us-gov-west-1.amazonaws.com

rds.us-gov-west-1.amazonaws.com

HTTPS

HTTPS

If you do not explicitly specify an endpoint, the US West (Oregon) endpoint is the default.

When you work with a DB instance using the AWS CLI or API operations, make sure that you specify its regional endpoint.