Creating a Redis (Cluster Mode Enabled) Cluster (Console) - Amazon ElastiCache for Redis

Creating a Redis (Cluster Mode Enabled) Cluster (Console)

If you are running Redis 3.2.4 or later, you can create a Redis (cluster mode enabled) cluster. Redis (cluster mode enabled) clusters support partitioning your data across 1 to 90 shards (API/CLI: node groups) but with some limitations. For a comparison of Redis (cluster mode disabled) and Redis (cluster mode enabled), see Supported ElastiCache for Redis Versions.

You can create a Redis (cluster mode enabled) cluster (API/CLI: replication group) using the ElastiCache management console, the AWS CLI for ElastiCache, and the ElastiCache API.

To create a Redis (cluster mode enabled) cluster using the ElastiCache console

  1. Sign in to the AWS Management Console and open the Amazon ElastiCache console at

  2. From the list in the upper-right corner, choose the AWS Region that you want to launch this cluster in.

  3. Choose Redis from the navigation pane.

  4. Choose Create.

  5. For Cluster engine, choose Redis, and then choose Cluster Mode enabled. These selections create a Redis (cluster mode enabled) cluster that looks something like the following.

    Image: Redis (cluster mode enabled) cluster created with replication and data partitioning

    Redis (cluster mode enabled) cluster created with replication and data partitioning

  6. Complete the Redis settings section.

    1. In Name, enter a name for your cluster.

    2. In the Description box, enter a description for this cluster.

    3. For Engine version compatibility, choose the ElastiCache for Redis engine version that you want to run on this cluster. Unless you have a specific reason to run an older version, we recommend that you choose the latest version.


      You can upgrade to newer engine versions. For more information on doing so, see Upgrading Engine Versions. However, you can't downgrade to older engine versions except by deleting the existing cluster and creating it again.

    4. In Port, use the default port, 6379. If you have a reason to use a different port, enter the port number.

    5. For Parameter group, choose a parameter group or create a new one. Parameter groups control the runtime parameters of your cluster. For more information on parameter groups, see Redis Specific Parameters and Creating a Parameter Group.

    6. For Node type, choose the down arrow ( ). In the Change node type dialog box, choose a value for Instance family for the node type that you want. Then choose the node type that you want to use for this cluster, and then choose Save.

      For more information, see Choosing Your Node Size.

    7. For Number of shards, choose the number of shards (partitions/node groups) that you want for this Redis (cluster mode enabled) cluster.

      For some versions of Redis (cluster mode enabled), you can change the number of shards in your cluster dynamically:

      • Redis 3.2.10 and later – If your cluster is running Redis 3.2.10 or later versions, you can change the number of shards in your cluster dynamically. For more information, see Scaling Clusters in Redis (Cluster Mode Enabled).

      • Other Redis versions – If your cluster is running a version of Redis before version 3.2.10, there's another approach. To change the number of shards in your cluster in this case, create a new cluster with the new number of shards. For more information, see Restoring From a Backup with Optional Cluster Resizing.

    8. For Replicas per shard, choose the number of read replica nodes that you want in each shard.

      The following restrictions exist for Redis (cluster mode enabled).

      • If you have Multi-AZ enabled, make sure that you have at least one replica per shard.

      • The number of replicas is the same for each shard when creating the cluster using the console.

      • The number of read replicas per shard is fixed and cannot be changed. If you find you need more or fewer replicas per shard (API/CLI: node group), you must create a new cluster with the new number of replicas. For more information, see Seeding a New Cluster with an Externally Created Backup.

    9. For Subnet group, create a new subnet group or choose an existing one that you want to apply to this cluster. If you enabled Multi-AZ, the subnet group must contain at least two subnets that reside in different availability zones.

      For more information, see Subnets and Subnet Groups.

  7. Click Advanced Redis settings and complete the section.

    1. For Slots and keyspaces, choose how you want your keys distributed over your shards (partitions). There are 16,384 keys to be distributed (numbered 0 through 16383).

      • Equal distribution – ElastiCache distributes your keyspace as equally as possible over your shards.


      • Custom distribution – You specify the range of keys for each shard in the table below Availability zone(s).

    2. For Availability zone(s), you have two options:

      • No preference – ElastiCache chooses the Availability Zone.


      • Specify availability zones – You specify the Availability Zone for each cluster.

        If you chose to specify the Availability Zones, for each cluster in each shard, choose the Availability Zone from the list.

      For more information, see Choosing Regions and Availability Zones.

      Image: Specifying Keyspaces and Availability Zones

      Specifying Keyspaces and Availability Zones

    3. For Security groups, choose the security groups that you want for this cluster. A security group acts as a firewall to control network access to your cluster. You can use the default security group for your VPC or create a new one.

      For more information on security groups, see Security groups for your VPC in the Amazon VPC User Guide.

    4. Encrypt your data, you have the following options:

      • Encryption at rest – Enables encryption of data stored on disk. For more information, see Encryption at Rest.


        You have the option to supply a different encryption key by selecting Customer Managed Customer Master Key and selecting the key. For more information, see Using Customer Managed CMKs from AWS KMS.

      • Encryption in-transit – Enables encryption of data on the wire. For more information, see encryption in transit.

      • Redis AUTH – An authentication mechanism for Redis server. For more information, see Redis AUTH.

    5. (Optional) If you are going to seed your cluster with data from a .rdb file, enter the S3 location of the .rdb file for Seed RDB file S3 location.

      For more information, see Seeding a New Cluster with an Externally Created Backup.

      For Redis (cluster mode enabled), make sure that you have a separate .rdb file for each node group.

    6. For regularly scheduled automatic backups, select Enable automatic backups and then enter the number of days that you want each automatic backup retained before it is automatically deleted. If you don't want regularly scheduled automatic backups, clear the Enable automatic backups check box. In either case, you always have the option to create manual backups.

      For more information on Redis backup and restore, see Backup and Restore for ElastiCache for Redis .

    7. (Optional_ Specify a maintenance window. The maintenance window is the time, generally an hour in length, each week when ElastiCache schedules system maintenance for your cluster. You can allow ElastiCache to choose the day and time for your maintenance window (No preference), or you can choose the day, time, and duration yourself (Specify maintenance window). If you choose Specify maintenance window from the lists, choose the Start day, Start time, and Duration (in hours) for your maintenance window. All times are UCT times.

      For more information, see Managing Maintenance.

    8. For Notifications, choose an existing Amazon Simple Notification Service (Amazon SNS) topic, or choose Manual ARN input and enter the topic's Amazon Resource Name (ARN). Amazon SNS allows you to push notifications to Internet-connected smart devices. The default is to disable notifications. For more information, see

  8. Review all your entries and choices, then make any needed corrections. When you're ready, choose Create cluster to launch your cluster, or Cancel to cancel the operation.

To create the equivalent using the ElastiCache API or AWS CLI instead of the ElastiCache console, see the following:

As soon as your cluster's status is available, you can grant EC2 access to it, connect to it, and begin using it. For more information, see Authorize Access and Connect to a Cluster's Node.


As soon as your cluster becomes available, you're billed for each hour or partial hour that the cluster is active, even if you're not actively using it. To stop incurring charges for this cluster, you must delete it. See Deleting a Cluster.