About SRGTechnical articleRecruitment Information
About SRGTechnical articleRecruitment Information
HOME/Technical article/[Update Added] Regarding the issue where parameters other than binlog_format are now required in the Aurora Blue/Green deployment feature.

[Update Added] Regarding the issue where parameters other than binlog_format are now required in the Aurora Blue/Green deployment feature.

This is Yuta Kikai (@fat47) from the Service Reliability Group (SRG) of the Media Management Division.
#SRGThe Service Reliability Group primarily provides comprehensive support for the infrastructure surrounding our media services, focusing on improving existing services, launching new ones, and contributing to open-source software (OSS).

[Update added] Introduction

Amazon Aurora Blue/Green deployments are a convenient feature that allows you to safely test database changes (such as version upgrades and schema changes) without impacting your production environment, and then deploy them to production with minimal downtime.
ROW
However, as of April 2025, it has been confirmed that other parameter settings are also required in addition to the above.
💡
[Update] As of May 2025, AWS has made a fix, and the error no longer occurs without changing any additional parameters.

Issues that occurred (resolved in May 2025)

ON
  • enforce_gtid_consistency
  • gtid_mode
If these parameters are not set correctly, you will see an error like the one below when creating a Blue/Green deployment.
Even when the UI is set to Japanese, these error messages are displayed in English.
 
Checking the checkbox and selecting "Next" will display a message indicating that the two parameters mentioned above will be enabled in the Blue cluster.

Current situation

There is no information about this in the official user guide.

gtid_mode
Reference:Creating a blue/green deployment - Prerequisites for Aurora MySQL

Support inquiry submitted

I have filed a support case, and the investigation is currently ongoing.
💡
[Update] As of May 2025, AWS has made a fix, and the error no longer occurs even without changing these parameters.

Countermeasures

A pattern for enabling two additional parameters in the Blue cluster parameters.

ON
However, please note that these parameters are not dynamic, so a cluster restart will be required for the changes to take effect.

Pattern for creating a B/G from AWS CLI

Currently, when creating a background group (B/G) from the CLI, it is possible to create a B/G without enabling these two parameters.
The following command will create a Green cluster with the same parameter group selected as the Blue cluster.
 
Please note that some sources suggest that enabling these parameters is safer for replication purposes.
In Aurora MySQL v3.04 and later, the default value for replica_parallel_workers is 4.

In conclusion

Please note that the current Aurora Blue/Green versions exhibit behavior not documented.
We will update this article as soon as we receive a response from support regarding the status of their investigation.。
💡
[Update] As of May 2025, AWS has made a fix, and the error no longer occurs even without changing these parameters.
SRG is looking for new team members. If you are interested, please contact us here.