AWS Blue Green Deployment for Databases - Mydbops
0 likes37 views
Mastering AWS Blue/Green Deployment for Databases - Mydbops MyWebinar 37 What You Will Learn * Key Principles of Blue/Green Deployment: Understand the fundamental concepts that drive this deployment strategy. * Step-by-Step Implementation: A detailed walkthrough of the processes involved in setting up Blue/Green deployments using AWS services. * Best Practices: Discover industry best practices to minimize risks and avoid common pitfalls during deployments. * Database Management with AWS: Learn how to effectively use AWS services like RDS and Aurora for safe database upgrades, including rollback options in the event of deployment issues. This webinar is ideal for database administrators, DevOps engineers, cloud architects, and anyone interested in mastering AWS deployment strategies. Whether you are new to AWS or looking to enhance your skills, this session will provide valuable insights and practical knowledge. Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL. Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability. Contact us: [email protected] Visit: https://www.mydbops.com/
AWS Blue Green Deployment for Databases - Mydbops
- 1. Mastering AWS Blue/Green Deployment for Databases Mydbops MyWebinar Edition 37 Praveen GR Mydbops
- 2. Problem statement ā Amplified effort on DB setup ā Data Migration ā Manual Ratification ā Data Synchronization ā Manual Traffic Routing ā DNS/Load balancer Amend ā Rollback Strategy
- 3. Agenda ā About AWS BLUE-GREEN ā Internal Workflow ā Benefits ā Prerequisites ā Deployments ā Use cases ā Best practices ā Limitation
- 4. Use cases
- 5. Use cases ā Version upgrade ā Pre-production deployment ā Testing with live data ā Database Parameter validation ā Performance testing with prod data
- 6. AWS BLUE - GREEN
- 7. Recipes BLUE-GREEN ā Supported engine: ā MySQL ā MariaDB ā PostgreSQL ā Supported service: ā RDS ā Aurora
- 8. Recipes BLUE-GREEN ā Full data migration ā Clone of current server ā Same architecture ā Automatic process ā Incremental data
- 9. Recipes BLUE-GREEN ā Live data sync ā Async replication ā Easy switchover ā Independent ā Customisation on GREEN
- 11. Internal Workļ¬ow ā BLUE environment ā Topology Analysis ā Data clone from BLUE to GREEN ā GREEN Identifier ā <Instance name>-green-<Random character> ā Configure Async replication ā Switch over
- 12. Internal Workļ¬ow ā Instance identifier and Endpoint rename ā <Instance name>-green-<Random character> to <Instance name> ā <Instance name> to <Instance name>-old ā BLUE - Old server ā GREEN - Live production
- 14. Beneļ¬ts
- 15. Beneļ¬ts ā Easy creation of environment ā AWS makes it simple to set up a new environment that's identical to the live one. ā Saves time and ensures both environments are perfectly matched. ā Automated process ā The entire deployment can be automated, so you don't have to manually move things around. ā Makes it faster and less prone to mistakes.
- 16. Beneļ¬ts ā Live replication sync between prod and staging server ā Changes made in the live environment are automatically synced with the testing environment. ā Ensures both have the same data, so tests are accurate. ā Easy testing on the GREEN Environment ā we can test updates in the green environment without disrupting the live one. ā Allows us to catch any issues before users see them.
- 17. Beneļ¬ts ā No impact on BLUE environment ā The live environment stays untouched while updates are being tested. ā Users wonāt notice any downtime or issues while you're working. ā Easy switchover process ā Once everything looks good in the green environment, you can switch live traffic to it quickly. ā The process is smooth, keeping disruptions to a minimum.
- 18. Beneļ¬ts ā No manual intervention ā The whole system can switch automatically, without any manual work. ā Ensures the transition happens exactly as planned. ā Avoid human errors ā Automation reduces the chance of mistakes that can happen with manual deployments. ā Makes the process more reliable and stress-free.
- 19. Beneļ¬ts ā Ensure data consistency ā Your data is always kept in sync between the live and testing environments. ā Ensures youāre testing the latest, most accurate data. ā Auto rollback during timeout ā If something goes wrong or takes too long during the switch, the system can automatically roll back to the old version. ā Keeps everything running smoothly even if thereās a problem.
- 20. Prerequisites
- 21. Prerequisites ā PostgreSQL ā Version (Aurora & RDS) ā >= 11.21 , >= 12.16 , >= 13.12 , >= 14.9, >= 15.4 ā MySQL ā Version (Aurora MySQL) ā >= 5.6 ā Version (RDS MySQL) ā >= 5.7 ā Version (RDS MariaDB) ā >= 10.3
- 22. Prerequisites ā PostgreSQL ā Variable configuration ā max_replication_slots ā max_wal_senders ā max_logical_replication_workers ā Max_worker_processes ā MySQL ā Binlog ā Binlog format as ROW (Optional)
- 23. Deployment
- 24. Deployment ā Select the target cluster for the BLUE/GREEN deployment, then click Actions and choose āCreate Blue/Green Deployment - newā
- 25. Deployment ā Enter a unique and appropriate identifier for this BLUE/GREEN Deployment.
- 26. Deployment ā We can modify the engine version or parameter group for the GREEN environment if needed.
- 27. Deployment ā Once confirmed, the system will begin provisioning the GREEN environment.
- 28. Deployment ā Once all GREEN nodes are created, they will transition to an available state.
- 29. Deployment ā To switch between BLUE and GREEN, select the BLUE/GREEN job, click Actions, and choose āSwitch Overā.
- 30. Deployment ā After clicking the switchover, a summary is displayed along with the option to set the switchover timeout.
- 31. Deployment ā After confirmation, the switchover process will begin.
- 32. Deployment ā Once the switchover is completed, the current production (BLUE) becomes the old environment, and the GREEN environment is promoted to production, becoming the new BLUE.
- 33. Best practices
- 34. Best practices ā Validate replication lag before the cutover ā Ensure the data in the green environment is fully up-to-date with the blue environment. ā Prevents missing or inconsistent data during the cutover. ā Parameter group are in sync ā Verify that the parameter settings in both environments are identical. ā Misaligned settings can cause unexpected behavior after the switch.
- 35. Best practices ā Same configuration ā Both the blue and green environments should have the same infrastructure and application configurations. ā Ensures a seamless transition with no surprises. ā Additional binlog retention - BLUE environment ā Keep additional binlog (binary log) data on the blue environment for a longer period. ā Avoid cluster break between BLUE and GREEN due to binlog purge.
- 36. Best practices ā Lesser switchover timeout ā Reduce the timeout for switching traffic to the green environment to minimize downtime. ā Ensures a faster transition with minimal user impact. ā Maintain consistency between BLUE-GREEN ā Ensure data and configurations between the blue and green environments are consistent throughout the deployment. ā Inconsistencies can cause failures during or after the cutover.
- 37. Best practices ā Manual reverse replication for rollback ā In case of rollback, set up manual reverse replication to sync changes back to the blue environment. ā Prevents data loss and ensures the live environment stays current.
- 39. Notable Limitation ā Canāt stop or start the cluster ā Auto-scaling policies are not copied ā Doesnāt support AWS Secrets Manager instances ā Not supported ā RDS proxy ā Cross-Region read replicas ā Global database
- 40. Demo
- 41. Reference ā https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html ā https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-considerations.h tml ā https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Concepts.Aurora_Fea_Regions_DB-eng.F eature.BlueGreenDeployments.html ā https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-creating.html#cr eate-blue-green-settings
- 42. Any Queries?
- 43. Thank you ā +91 99622 88131 ā [email protected] ā www.mydbops.com