Deleting a read replica for Redis OSS (Cluster Mode Disabled) - Amazon ElastiCache (Redis OSS)
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).

Deleting a read replica for Redis OSS (Cluster Mode Disabled)

Information in the following topic applies to Redis OSS (cluster mode disabled) replication groups only.

As read traffic on your Redis OSS replication group changes, you might want to add or remove read replicas. Removing a node from a Redis OSS (cluster mode disabled) replication group is the same as just deleting a cluster, though there are restrictions:

  • You cannot remove the primary from a replication group. If you want to delete the primary, do the following:

    1. Promote a read replica to primary. For more information on promoting a read replica to primary, see Promoting a read replica to primary, for Redis OSS (cluster mode disabled) replication groups.

    2. Delete the old primary. For a restriction on this method, see the next point.

  • If Multi-AZ is enabled on a replication group, you can't remove the last read replica from the replication group. In this case, do the following:

    1. Modify the replication group by disabling Multi-AZ. For more information, see Modifying a replication group.

    2. Delete the read replica.

You can remove a read replica from a Redis OSS (cluster mode disabled) replication group using the ElastiCache console, the Amazon CLI for ElastiCache, or the ElastiCache API.

For directions on deleting a cluster from a Redis OSS replication group, see the following: