Implement a rollback strategy after an Amazon Aurora MySQL blue/green deployment switchover
Database Blog
This article discusses implementing a rollback strategy after an Amazon Aurora MySQL blue/green deployment switchover.
Specifically, the article covers:
- Solution overview for setting up a rollback environment
- Prerequisites and limitations of the solution
- Preparing the green environment for rollback by enabling binary logging and configuring binary log retention
- Performing the Aurora MySQL blue/green deployment switchover
- Configuring logical replication from the new production environment to the rollback environment
- Steps to perform a rollback to the old environment if issues arise in the new production environment
- Cleanup of resources after rollback
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Jun 20
2025
2025
Implement a rollback strategy for Amazon Aurora PostgreSQL upgrades using Amazon RDS Blue/Green deployments
May 28
2024
2024
Create a fallback migration plan for your self-managed MySQL database to Amazon Aurora MySQL using native bi-directional binary log replication
Aug 5
2024
2024
Migrate an on-premises MySQL database to Amazon Aurora MySQL over a private network using AWS DMS homogeneous data migration and Network Load Balancer
Jul 2
2024
2024
Understanding Amazon Aurora MySQL storage space utilization
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.