Restoring from a snapshot - Amazon MemoryDB for Redis
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).

Restoring from a snapshot

You can restore the data from a MemoryDB or ElastiCache for Redis .rdb snapshot file to a new cluster at any time.

The MemoryDB for Redis restore process supports the following:

  • Migrating from one or more .rdb snapshot files you created from ElastiCache for Redis to a MemoryDB cluster.

    The .rdb files must be put in S3 to perform the restore.

  • Specifying a number of shards in the new cluster that is different from the number of shards in the cluster that was used to create the snapshot file.

  • Specifying a different node type for the new cluster—larger or smaller. If scaling to a smaller node type, be sure that the new node type has sufficient memory for your data and Redis overhead.

  • Configuring the slots of the new MemoryDB cluster differently than in the cluster that was used to create the snapshot file.

  • MemoryDB clusters do not support multiple databases. Therefore, when restoring to MemoryDB your restore fails if the .rdb file references more than one database.

  • You cannot restore a snapshot from a cluster that uses data tiering (for example, r6gd node type) into a cluster that does not use data tiering (for example, r6g node type).

Whether you make any changes when restoring a cluster from a snapshot is governed by choices that you make. You make these choices in the Restore Cluster page when using the MemoryDB console to restore. You make these choices by setting parameter values when using the Amazon CLI or MemoryDB API to restore.

During the restore operation, MemoryDB creates the new cluster, and then populates it with data from the snapshot file. When this process is complete, the cluster is warmed up and ready to accept requests.


Before you proceed, be sure you have created a snapshot of the cluster you want to restore from. For more information, see Making manual snapshots.

If you want to restore from an externally created snapshot, see Seeding a new cluster with an externally created snapshot.

The following procedures show you how to restore a snapshot to a new cluster using the MemoryDB console, the Amazon CLI, or the MemoryDB API.

To restore a snapshot to a new cluster (console)
  1. Sign in to the Amazon Web Services Management Console and open the MemoryDB for Redis console at

  2. On the navigation pane, choose Snapshots.

  3. In the list of snapshots, choose button next to the name of the snapshot name you want to restore from.

  4. Choose Actions and then choose Restore

  5. Under Cluster configuration, enter the following:

    1. Cluster name – Required. The name of the new cluster.

    2. Description – Optional. The description of the new cluster.

  6. Complete the Subnet groups section:

    1. For Subnet groups, create a new subnet group or choose an existing one from the available list that you want to apply to this cluster. If you are creating a new one:

      • Enter a Name

      • Enter a Description

      • 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.

      • If you are creating a new subnet group and do not have an existing VPC, you will be asked to create a VPC. For more information, see What is Amazon VPC? in the Amazon VPC User Guide.

  7. Complete the Cluster settings section:

    1. For Redis version compatibility, accept the default 6.0.

    2. For Port, accept the default Redis port of 6379 or, if you have a reason to use a different port, enter the port number..

    3. For Parameter group, accept the default.memorydb-redis6 parameter group.

      Parameter groups control the runtime parameters of your cluster. For more information on parameter groups, see Redis specific parameters.

    4. For Node type, choose a value for the node type (along with its associated memory size) that you want.

      If you choose a member of the r6gd node type family, you will automatically enable data-tiering in your cluster. For more information, see Data tiering.

    5. For Number of shards, choose the number of shards that you want for this cluster.

      You can change the number of shards in your cluster dynamically. For more information, see Scaling MemoryDB clusters.

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

      The following restrictions exist;.

      • 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.

    7. Choose Next

    8. Complete the Advanced settings section:

      1. 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.

      2. Data is encrypted in the following ways:

        • 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 choosing Customer Managed Amazon KMS key and choosing the key.

        • Encryption in-transit – Enables encryption of data on the wire. This is enabled by default. For more information, see encryption in transit.

        If you select no encryption, then an open Access control list called “open access” will be created with a default user. For more information, see Authenticating users with Access Control Lists (ACLs).

      3. For Snapshot optionally specify a snapshot retention period and a snapshot window. By default, the Enable automatic snapshots is selected.

      4. For Maintenance window optionally specify a maintenance window. The maintenance window is the time, generally an hour in length, each week when MemoryDB schedules system maintenance for your cluster. You can allow MemoryDB 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.

      5. 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

    9. For Tags, you can optionally apply tags to search and filter your clusters or track your Amazon costs.

    10. 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.

    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 Step 2: Authorize access to the cluster and Step 3: Connect to the cluster.


    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 Step 4: Deleting a cluster.

When using either the create-cluster operation, be sure to include the parameter --snapshot-name or --snapshot-arns to seed the new cluster with the data from the snapshot.

For more information, see the following:

You can restore a MemoryDB snapshot using the MemoryDB API operation CreateCluster.

When using the CreateCluster operation, be sure to include the parameter SnapshotName or SnapshotArns to seed the new cluster with the data from the snapshot.

For more information, see the following: