Node type missing in wizard when attempting to scale redis node

Hi,
Yes, if you only want to scale up with a single node, you can following the AWS guide to Replace the only node in any Redis cluster

To replace the only node using backup and restore

1. Create a snapshot of the node's cluster. For instructions, see Making Manual Backups.

2. Create a new cluster seeding it from the snapshot. For instructions, see Restoring From a Backup with Optional Cluster Resizing.

3. Delete the cluster with the node scheduled for replacement. For instructions, see Deleting a Cluster.

4. In your application, replace the old node's endpoint with the new node's endpoint.

Link: https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/CacheNodes.NodeReplacement.html#ReplaceStandalone

When you perform Step 2 (Restoring from a Backup using Console), you are presented with the Node Type option to specify the larger node type.
Link: https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/backups-restoring.html#backups-restoring-CON

Hope this helps!
-randy

Thanks Randy for confirming what I suspected. I will proceed as described in the article https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/CacheNodes.NodeReplacement.html#ReplaceStandalone .

Actually, one further question. Is there a way of avoiding the need to replace the old node's endpoint with the new node's endpoint in our applications? Can we keep the old one and map it to the new Redis node?

Edited by: ec-confounder on Aug 19, 2019 2:54 AM