Choosing regions and availability zones - Amazon ElastiCache
Availability Zone considerationsSupported regions & endpointsLocating your nodes
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Choosing regions and availability zones

Amazon Cloud computing resources are housed in highly available data center facilities. To provide additional scalability and reliability, these data center facilities are located in different physical locations. These locations are categorized by regions and Availability Zones.

Amazon Regions are large and widely dispersed into separate geographic locations. Availability Zones are distinct locations within an Amazon Region that are engineered to be isolated from failures in other Availability Zones. They provide inexpensive, low-latency network connectivity to other Availability Zones in the same Amazon Region.

Important

Each region is completely independent. Any ElastiCache activity you initiate (for example, creating clusters) runs only in your current default region.

To create or work with a cluster in a specific region, use the corresponding regional service endpoint. For service endpoints, see Supported regions & endpoints.

Image: Regions and Availability Zones

Regions and Availability Zones

Topics

Availability Zone considerations

Distributing your Memcached nodes over multiple Availability Zones within a region helps protect you from the impact of a catastrophic failure, such as a power loss within an Availability Zone.

Serverless Caching

ElastiCache serverless caching creates a highly available cache that spans multiple Availability Zones. You can specify subnets from different availability zones and same VPC as you create your cache or ElastiCache will choose subnets automatically from your default VPC.

Designing your own ElastiCache for Memcached cluster

A Memcached cluster can have up to 300 nodes. When you create or add nodes to your Memcached cluster, you can specify a single Availability Zone for all your nodes, allow ElastiCache to choose a single Availability Zone for all your nodes, specify the Availability Zones for each node, or allow ElastiCache to choose an Availability Zone for each node. New nodes can be created in different Availability Zones as you add them to an existing Memcached cluster. Once a cache node is created, its Availability Zone cannot be modified.

If you want a cluster in a single Availability Zone cluster to have its nodes distributed across multiple Availability Zones, ElastiCache can create new nodes in the various Availability Zones. You can then delete some or all of the original cache nodes. We recommend this approach.

To migrate Memcached nodes from a single Availability Zone to multiple availability zones

  1. Modify your cluster by creating new cache nodes in the Availability Zones where you want them. In your request, do the following:

    • Set AZMode (CLI: --az-mode) to cross-az.

    • Set NumCacheNodes (CLI: --num-cache-nodes) to the number of currently active cache nodes plus the number of new cache nodes you want to create.

    • Set NewAvailabilityZones (CLI: --new-availability-zones) to a list of the zones you want the new cache nodes created in. To let ElastiCache determine the Availability Zone for each new node, don't specify a list.

    • Set ApplyImmediately (CLI: --apply-immediately) to true.

    Note

    If you are not using auto discovery, be sure to update your client application with the new cache node endpoints.

    Before moving on to the next step, be sure the Memcached nodes are fully created and available.

  2. Modify your cluster by removing the nodes you no longer want in the original Availability Zone. In your request, do the following:

    • Set NumCacheNodes (CLI: --num-cache-nodes) to the number of active cache nodes you want after this modification is applied.

    • Set CacheNodeIdsToRemove (CLI: --nodes-to-remove) to a list of the cache nodes you want to remove from the cluster.

      The number of cache node IDs listed must equal the number of currently active nodes minus the value in NumCacheNodes.

    • (Optional) Set ApplyImmediately (CLI: --apply-immediately) to true.

      If you don't set ApplyImmediately (CLI: --apply-immediately) to true, the node deletions will take place at your next maintenance window.

Supported regions & endpoints

Amazon ElastiCache is available in multiple Amazon Regions. This means that you can launch ElastiCache clusters in locations that meet your requirements. For example, you can launch in the Amazon Region closest to your customers, or launch in a particular Amazon Region to meet certain legal requirements.

Each Region is designed to be completely isolated from the other Regions. Within each Region are multiple Availability Zones (AZ). ElastiCache Serverless caches automatically replicate data across multiple availability zones (except us-west-1, where data is replicated in two availability zones) for high availability. When designing your own ElastiCache cluster, you can choose to launch your nodes in different AZs to achieve fault tolerance. For more information on Regions and Availability Zones, see Choosing regions and availability zones at the top of this topic.

Regions where ElastiCache is supported
Region Name/Region Endpoint Protocol

US East (Ohio) Region

us-east-2

elasticache.us-east-2.amazonaws.com

 HTTPS

US East (N. Virginia) Region

us-east-1

elasticache.us-east-1.amazonaws.com

 HTTPS

US West (N. California) Region

us-west-1

elasticache.us-west-1.amazonaws.com

 HTTPS

US West (Oregon) Region

us-west-2

elasticache.us-west-2.amazonaws.com

 HTTPS

Canada (Central) Region

ca-central-1

elasticache.ca-central-1.amazonaws.com

 HTTPS

Canada (West) Region

ca-west-1

elasticache.ca-west-1.amazonaws.com

 HTTPS

Asia Pacific (Jakarta)

ap-southeast-3

elasticache.ap-southeast-3.amazonaws.com

 HTTPS

Asia Pacific (Mumbai) Region

ap-south-1

elasticache.ap-south-1.amazonaws.com

 HTTPS

Asia Pacific (Hyderabad) Region

ap-south-2

elasticache.ap-south-2.amazonaws.com

 HTTPS

Asia Pacific (Tokyo) Region

ap-northeast-1

elasticache.ap-northeast-1.amazonaws.com

 HTTPS

Asia Pacific (Seoul) Region

ap-northeast-2

elasticache.ap-northeast-2.amazonaws.com

 HTTPS

Asia Pacific (Osaka) Region

ap-northeast-3

elasticache.ap-northeast-3.amazonaws.com

 HTTPS

Asia Pacific (Singapore) Region

ap-southeast-1

elasticache.ap-southeast-1.amazonaws.com

 HTTPS

Asia Pacific (Sydney) Region

ap-southeast-2

elasticache.ap-southeast-2.amazonaws.com

 HTTPS

Europe (Frankfurt) Region

eu-central-1

elasticache.eu-central-1.amazonaws.com

 HTTPS

Europe (Zurich) Region

eu-central-2

elasticache.eu-central-2.amazonaws.com

 HTTPS

Europe (Stockholm) Region

eu-north-1

elasticache.eu-north-1.amazonaws.com

 HTTPS

Middle East (Bahrain) Region

me-south-1

elasticache.me-south-1.amazonaws.com

 HTTPS

Middle East (UAE) Region

me-central-1

elasticache.me-central-1.amazonaws.com

 HTTPS

Europe (Ireland) Region

eu-west-1

elasticache.eu-west-1.amazonaws.com

 HTTPS

Europe (London) Region

eu-west-2

elasticache.eu-west-2.amazonaws.com

 HTTPS

EU (Paris) Region

eu-west-3

elasticache.eu-west-3.amazonaws.com

 HTTPS

Europe (Milan) Region

eu-south-1

elasticache.eu-south-1.amazonaws.com

 HTTPS

Europe (Spain) Region

eu-south-2

elasticache.eu-south-2.amazonaws.com

 HTTPS

South America (São Paulo) Region

sa-east-1

elasticache.sa-east-1.amazonaws.com

 HTTPS

China (Beijing) Region

cn-north-1

elasticache.cn-north-1.amazonaws.com.cn

 HTTPS

China (Ningxia) Region

cn-northwest-1

elasticache.cn-northwest-1.amazonaws.com.cn

 HTTPS

Asia Pacific (Hong Kong) Region

ap-east-1

elasticache.ap-east-1.amazonaws.com

 HTTPS

Africa (Cape Town) Region

af-south-1

elasticache.af-south-1.amazonaws.com

 HTTPS

Israel (Tel Aviv) Region

il-central-1

elasticache.il-central-1.amazonaws.com

 HTTPS

Amazon GovCloud (US-West)

us-gov-west-1

 elasticache.us-gov-west-1.amazonaws.com HTTPS

Amazon GovCloud (US-East)

us-gov-east-1

 elasticache.us-gov-east-1.amazonaws.com HTTPS

For information on using the Amazon GovCloud (US) with ElastiCache, see Services in the Amazon GovCloud (US) region: ElastiCache.

Some regions support a subset of node types. For a table of supported node types by Amazon Region, see Supported node types by Amazon Region.

For a table of Amazon products and services by region, see Products and Services by Region.

Locating your nodes

Amazon ElastiCache supports locating all of a cluster's nodes in a single or multiple Availability Zones (AZs). Further, if you elect to locate your nodes in multiple AZs (recommended), ElastiCache enables you to either choose the AZ for each node, or allow ElastiCache to choose them for you.

By locating the nodes in different AZs, you eliminate the chance that a failure, such as a power outage, in one AZ will cause your entire system to fail.

You can specify an AZ for each node when you create a cluster or by adding nodes when you modify an existing cluster. For more information, see the following: