AWS Regions and Endpoints

To reduce data latency in your applications, most Amazon Web Services offer a regional endpoint to
make your requests. An endpoint is a URL that is the entry point for a web service. For example,
https://dynamodb.us-west-2.amazonaws.com is an entry point for the Amazon DynamoDB
service.

Some services, such as IAM, do not support regions; therefore, their endpoints do not
include a region. Some services, such as Amazon EC2, let you specify an endpoint that does not
include a specific region, for example, https://ec2.amazonaws.com. In that case,
AWS routes the endpoint to us-east-1.

If a service supports regions, the resources in each region are independent. For example, if
you create an Amazon EC2 instance or an Amazon SQS queue in one region, the instance or queue is
independent from instances or queues in another region.

To see the supported services per region in a tabbed format, see the Region
Table. This page does not include endpoint information.

For information about which regions and endpoints are supported for each service, see the
following tables.

Amazon CloudFront

Amazon CloudFront distributions have a single endpoint: cloudfront.amazonaws.com and only supports HTTPS requests.
When you submit requests to CloudFront programmatically, specify us-east-1 for the US East (N. Virginia) Region.

If you specify the general endpoint (elasticmapreduce.amazonaws.com), Amazon EMR directs your
request to an endpoint in the default region. For accounts created on or after March 8,
2013, the default region is us-west-2; for older accounts, the default region is
us-east-1.

Amazon Mobile Analytics

Region Name

Region

Endpoint

Protocol

US East (N. Virginia)

us-east-1

mobileanalytics.us-east-1.amazonaws.com

HTTPS

AWS OpsWorks

AWS OpsWorks uses the following regional endpoints.

AWS OpsWorks for Chef Automate

You can create and manage AWS OpsWorks for Chef Automate servers in the following regions. Resources can be
managed only in the region in which they are created. Resources that are created in one
regional endpoint are not available, nor can they be cloned to, another regional
endpoint.

Region Name

Region

Endpoint

Protocol

US East (N. Virginia) Region

us-east-1

opsworks-cm.us-east-1.amazonaws.com

HTTPS

US West (N. California) Region

us-west-1

opsworks-cm.us-west-1.amazonaws.com

HTTPS

EU (Ireland) Region

eu-west-1

opsworks-cm.eu-west-1.amazonaws.com

HTTPS

AWS OpsWorks Stacks

You can create and manage AWS OpsWorks resources in all regions except AWS GovCloud (US)
and the China (Beijing) Region. Resources can be managed only in the region in which they are
created. Resources that are created in one regional endpoint are not available, nor can
they be cloned to, another regional endpoint.

Amazon Route 53

Amazon Route 53 uses two endpoints. The endpoint that you use depends on the operation that you want to perform.

Requests for hosted zones, resource record sets, health checks, and cost allocation tags use the following endpoint.

Region Name

Region

Endpoint

Protocol

US East (N. Virginia)

us-east-1

route53.amazonaws.com

HTTPS

Requests for domain registration use the following endpoint.

Region Name

Region

Endpoint

Protocol

US East (N. Virginia)

us-east-1

route53domains.us-east-1.amazonaws.com

HTTPS

AWS Security Token Service (AWS STS)

The default endpoint for AWS Security Token Service is https://sts.amazonaws.com, which serves all global
requests. You can also make calls to other regional endpoints that are activated for your AWS
account. All regions are activated by default, but you can deactivate regions that you do not
intend to use. If you deactivate a region, you must reactivate it for your account in the
AWS Management Console before you can use that region’s endpoint.

Amazon SQS Legacy Endpoints

If you use the AWS CLI or SDK for Python, you can use the following legacy endpoints.

Region Name

Region

Endpoint

Protocol

US East (N. Virginia)

us-east-1

queue.amazonaws.com

HTTP and HTTPS

US East (Ohio)

us-east-2

us-east-2.queue.amazonaws.com

HTTP and HTTPS

US West (N. California)

us-west-1

us-west-1.queue.amazonaws.com

HTTP and HTTPS

US West (Oregon)

us-west-2

us-west-2.queue.amazonaws.com

HTTP and HTTPS

Canada (Central)

ca-central-1

ca-central-1.queue.amazonaws.com

HTTP and HTTPS

Asia Pacific (Mumbai)

ap-south-1

ap-south-1.queue.amazonaws.com

HTTP and HTTPS

Asia Pacific (Seoul)

ap-northeast-2

ap-northeast-2.queue.amazonaws.com

HTTP and HTTPS

Asia Pacific (Singapore)

ap-southeast-1

ap-southeast-1.queue.amazonaws.com

HTTP and HTTPS

Asia Pacific (Sydney)

ap-southeast-2

ap-southeast-2.queue.amazonaws.com

HTTP and HTTPS

Asia Pacific (Tokyo)

ap-northeast-1

ap-northeast-1.queue.amazonaws.com

HTTP and HTTPS

EU (Frankfurt)

eu-central-1

eu-central-1.queue.amazonaws.com

HTTP and HTTPS

EU (Ireland)

eu-west-1

eu-west-1.queue.amazonaws.com

HTTP and HTTPS

South America (São Paulo)

sa-east-1

sa-east-1.queue.amazonaws.com

HTTP and HTTPS

Amazon Simple Storage Service (Amazon S3)

When sending requests to these endpoints using the REST API, you can use the
virtual-hosted style and path-style methods. For more information, see Virtual Hosting of Buckets.

Note

Amazon S3 renamed the US Standard Region to the US East (N. Virginia) Region to be consistent with AWS
regional naming conventions. There is no change to the endpoint and you do not need to
make any changes to your application.

Region Name

Region

Endpoint

Location Constraint

Protocol

Signature Version(s)

Support

US East (N. Virginia)

us-east-1

Valid endpoint names for this region:

s3.amazonaws.com

s3-external-1.amazonaws.com

s3.dualstack.us-east-1.amazonaws.com**

(none required)

HTTP and HTTPS

Versions 2 and 4

US East (Ohio)

us-east-2

Valid endpoint names for this region:

s3.us-east-2.amazonaws.com

s3-us-east-2.amazonaws.com

s3.dualstack.us-east-2.amazonaws.com

us-east-2

HTTP and HTTPS

Versions 4 only

US West (N. California)

us-west-1

Valid endpoint names for this region:

s3-us-west-1.amazonaws.com

s3.dualstack.us-west-1.amazonaws.com**

us-west-1

HTTP and HTTPS

Versions 2 and 4

US West (Oregon)

us-west-2

Valid endpoint names for this region:

s3-us-west-2.amazonaws.com

s3.dualstack.us-west-2.amazonaws.com**

us-west-2

HTTP and HTTPS

Versions 2 and 4

Canada (Central)

ca-central-1

Valid endpoint names for this region:

s3.ca-central-1.amazonaws.com

s3-ca-central-1.amazonaws.com

s3.dualstack.ca-central-1.amazonaws.com**

ca-central-1

HTTP and HTTPS

Version 4 only

Asia Pacific (Mumbai)

ap-south-1

Valid endpoint names for this region:

s3.ap-south-1.amazonaws.com

s3-ap-south-1.amazonaws.com

s3.dualstack.ap-south-1.amazonaws.com**

ap-south-1

HTTP and HTTPS

Version 4 only

Asia Pacific (Seoul)

ap-northeast-2

Valid endpoint names for this region:

s3.ap-northeast-2.amazonaws.com

s3-ap-northeast-2.amazonaws.com

s3.dualstack.ap-northeast-2.amazonaws.com**

ap-northeast-2

HTTP and HTTPS

Version 4 only

Asia Pacific (Singapore)

ap-southeast-1

Valid endpoint names for this region

s3-ap-southeast-1.amazonaws.com

s3.dualstack.ap-southeast-1.amazonaws.com**

ap-southeast-1

HTTP and HTTPS

Versions 2 and 4

Asia Pacific (Sydney)

ap-southeast-2

Valid endpoint names for this region:

s3-ap-southeast-2.amazonaws.com

s3.dualstack.ap-southeast-2.amazonaws.com**

ap-southeast-2

HTTP and HTTPS

Versions 2 and 4

Asia Pacific (Tokyo)

ap-northeast-1

Valid endpoint names for this region:

s3-ap-northeast-1.amazonaws.com

s3.dualstack.ap-northeast-1.amazonaws.com**

ap-northeast-1

HTTP and HTTPS

Versions 2 and 4

EU (Frankfurt)

eu-central-1

Valid endpoint names for this region:

s3.eu-central-1.amazonaws.com

s3-eu-central-1.amazonaws.com

s3.dualstack.eu-central-1.amazonaws.com**

eu-central-1

HTTP and HTTPS

Version 4 only

EU (Ireland)

eu-west-1

Valid endpoint names for this region:

s3-eu-west-1.amazonaws.com

s3.dualstack.eu-west-1.amazonaws.com**

EU or eu-west-1

HTTP and HTTPS

Versions 2 and 4

South America (São Paulo)

sa-east-1

Valid endpoint names for this region:

s3-sa-east-1.amazonaws.com

s3.dualstack.sa-east-1.amazonaws.com**

sa-east-1

HTTP and HTTPS

Versions 2 and 4

Note

**Amazon S3 dual-stack endpoints support requests to S3 buckets over IPv6 and IPv4. For
more information, see Using
Dual-Stack Endpoints.

Important

If you use a region other than the US East (N. Virginia) endpoint to create a bucket, you
must set the LocationConstraint bucket parameter to the same
region. Both the AWS SDK for Java and AWS SDK for .NET use an enumeration for setting location
constraints (Region for Java, S3Region for .NET). For more
information, see PUT Bucket in the
Amazon Simple Storage Service API Reference.

Amazon Simple Storage Service Website Endpoints

When you configure your bucket as a website, the website is available using the following
region-specific website endpoints. Note that the website endpoints are different than
the REST API endpoints listed in the preceding table. For more information about hosting
websites on Amazon S3, see Hosting Websites on
Amazon S3 in the Amazon Simple Storage Service Developer Guide. You need the hosted zone
IDs when using the Amazon Route 53 API to add an alias record to your hosted zone.