Success story of migrating entire infrastructure from AWS Singapore to AWS Mumbai
0 likes298 views
The document outlines the successful migration of Medlife.com's infrastructure from AWS Singapore to AWS Mumbai, highlighting the motivations such as cost-effectiveness, user proximity, and marketing strategies. It details the planning and execution phases, emphasizing the necessity of clear communication, risk management, and the importance of a well-prepared team. Key execution strategies included the use of blue-green deployments and careful handling of service migrations.
Success story of migrating entire infrastructure from AWS Singapore to AWS Mumbai
- 1. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. BENGALURU
- 2. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Success story of migrating entire infrastructure from AWS Singapore to AWS Mumbai Pranesh Vittal CG, Database Architect, Medlife.com | 6th Oct 2018.
- 3. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. What is Medlife.com?
- 4. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. When did we come into existence? First Order Delivered – May 2015 First Production Deployment – May 2015
- 5. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Growth Story
- 6. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Growth Story:
- 7. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Growth Story:
- 8. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Migration Story
- 9. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Migration Story: Stringent Laws
- 10. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Migration Story: AWS Mumbai is cheaper than AWS Singapore.
- 11. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Migration Story: Stay closer to the users.
- 12. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Migration Story: Aggressive Marketing in the form of TVC, Online Marketing, Social Media Marketing.
- 13. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Migration Story: • Availability of the required services in the target region. • An opportunity to implement best practices. • Expiry of Reserved Instances.
- 14. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Planning Story
- 15. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Technology stack at Medlife.com
- 16. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Planning Story: • Program Duration : 2 Months. • VPC Peering between the two regions. • Segregating Automated & Manual tasks. • Scarce documentation available on this topic.
- 17. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Planning Story (Continued): • See yourself transition from unknown-unknowns to known-knowns. • No half-hearted attempts. • Keep the stake holders informed about what to expect, the risks, the timelines, the additional costs etc… • Nurture a good team with mix of DevOps, Development, QA Teams. • Plan well in advance for any time-critical tasks like data sync.
- 18. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Planning Story (Continued): • Prefer DNS names over IP values. • Review AWS limits of the target region to avoid last minute surprises. • Practice with smaller instance type during automation tests. • Always have a good rollback plan in place in case of unforeseen errors. • Make best use of Business or Enterprise support.
- 19. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Execution Story
- 20. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Execution Story on the D-Day: • No major release before the migration. • Enough rest time for the core migration team. • Don’t engage the whole team for the migration. • Have a positive mindset.
- 21. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Execution Story on the D-Day (Continued): • Blue-Green deployment using Terraform, Jenkins, Chef • Once all the required infrastructure was ready. Switch the Primary MongoDB replica set member from Singapore to Mumbai region. Change the Route53 rules from Singapore to Mumbai region. Migrate the services that required manual intervention.
- 22. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
- 23. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.