Prerequisites and Limitations - Amazon ElastiCache for Redis

Prerequisites and Limitations

Before getting started with global datastores, be aware of the following:

  • Global datastores are supported in the following AWS Regions: Asia Pacific (Seoul) Region, Asia Pacific (Tokyo) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, Asia Pacific (Mumbai) Region, Europe (Frankfurt) Region, EU (Paris) Region, Europe (London) Region, Europe (Ireland) Region, US East (N. Virginia) Region, US East (Ohio) Region, US West (N. California) Region, US West (Oregon) Region, South America (São Paulo) Region, AWS GovCloud (US-West), AWS GovCloud (US-East), Canada (Central) Region, China (Beijing) Region and China (Ningxia) Region.

  • To use global datastores, use Redis engine version 5.0.6 or higher and R5 or M5 node types or higher.

  • All clusters—primary and secondary—in your global datastore should have the same number of primary nodes, node type, engine version, and number of shards (in case of cluster-mode enabled). Each cluster in your global datastore can have a different number of read replicas to accommodate the read traffic local to that cluster.

    Replication must be enabled if you plan to use an existing single-node cluster.

  • You can set up replication for a primary cluster from one AWS Region to a secondary cluster in up to two other AWS Regions.

    Note

    The exception to this are China (Beijing) Region and China (Ningxia) regions, where replication can only occur between the two regions.

  • You can work with global datastores only in VPC clusters. For more information, see Access Patterns for Accessing an ElastiCache Cluster in an Amazon VPC. Global datastores aren't supported when you use EC2-Classic. For more information, see EC2-Classic in the Amazon EC2 User Guide for Linux Instances.

    Note

    At this time, you can't use global datastores in Using Local Zones with ElastiCache .

  • ElastiCache doesn't support autofailover from one AWS Region to another. When needed, you can promote a secondary cluster manually. For an example, see Promoting the Secondary Cluster to Primary.

  • To bootstrap from existing data, use an existing cluster as primary to create a global datastore. We don't support adding an existing cluster as secondary. The process of adding the cluster as secondary wipes data, which may result in data loss.

  • Parameter updates are applied to all clusters when you modify a local parameter group of a cluster belonging to a global datastore.

  • You can scale regional clusters both vertically (scaling up and down) and horizontally (scaling in and out). You can scale the clusters by modifying the global datastore. All the regional clusters in the global datastore are then scaled without interruption.

  • Global datastores support encryption at rest, encryption in transit, and Redis AUTH.

  • Global datastores support AWS KMS customer master keys. For more information, see AWS Key Management Service concepts in the AWS Key Management Service Developer Guide.

  • Security for cross-Region communication is provided through VPC peering. For more information, see What is VPC peering? in the Amazon VPC Peering Guide.

Note

Global datastores support pub/sub messaging with the following stipulations:

  • For cluster-mode disabled, pub/sub is fully supported. Events published on the primary cluster of the primary AWS Region are propagated to secondary AWS Regions.

  • For cluster mode enabled, the following applies:

    • For published events that aren't in a keyspace, only subscribers in the same AWS Region receive the events.

    • For published keyspace events, subscribers in all AWS Regions receive the events.