Redis to Elasticache Migration in AWS

Comparing Redis , AWS Elasticache giving multiple options to cache the data in cloud . Its enhanced with two ways of Access control options in PaaS Service 

Below are the few mission handling features we loved in elastic cache ,

• Detecting data failures and recovery the nodes automatically 
• Multi AZ features with automatic failover to replication nodes 
• Redis Cluster mode enabled supports data partitioning up to 500 shards in different zones
• Redis managed backups , automatic failure detection and log files transfer to Kinesis Firehouse and cloud watch 
• Easy online migration from any Redis source 
• Encryption at rest and Encryption in transit are supported 
• Data volume up to peta bytes with micro second response time  

Let start migrating data from Redis to Elasticache ,

Preparing our source and target Redis nodes for migration 

1. Launched two EC2 machines and installed redis 5.x version 
2. Configured replication between master and replica

        To avoid downtime , we are doing online migration from replication server . so we have modified below values in replica server . Its based on your source modify the below values

      3.Configured replication between master and replica

• protected-mode no
• bind datablogs.xcnphd.ng.0001.use1.cache.amazonaws.com 6379
• requirepass should be disabled

       Note : Transferring source master or replica should not have AUTH configured and protected mode disabled 

      4.Launch Elastic cache instance with below steps 

Cluster Mode Disabled ( Redis Engine 5.0.5 or Higher ) 

Multi-AZ Should be Enabled 

Encrypt at rest and in-transit should be disabled

If we have not followed above all steps , we will get below popup while we start the migration 

 

Starting Migration 

In Elastic console Click --> Action --> Migrate data from endpoint 

Once clicked , we can type the Source Redis Endpoint ( Private IP ) and Port ( Customized Port ) in below console ,

Then click Start Migration and follow the logs from Events in same console , 

If we get any error , It will be printed in the events log

Once its started , Restart the Master of Elasticache node one time , In our case we need to restart the replica server because its our source

Once restarted verify the info replication in Elasticache nodes 

Once started successfully , we can't perform any other operation in Elasticache nodes ,

Verifying the Data Migration Progress 

We have inserted sample record in the EC2 Master Node and verified the same in the replica and as well as in Elasticache 

Data looks good , once all the data transferred from IaaS to PaaS . Complete the migration in the Elasticache console and point the application endpoints to Elasticache node 

Authors : 👷 Krishna and 👷 Selvackp

Thanks for Reading !!!