About SRGTechnical ArticlesRecruitment Information
About SRGTechnical ArticlesRecruitment Information
HOME/Technical Articles/[Additional Note] Regarding the issue where parameters other than binlog_format are required for Aurora Blue/Green deployment

[Additional Note] Regarding the issue where parameters other than binlog_format are required for Aurora Blue/Green deployment

This is Onkai Yuta (@fat47) from the Service Reliability Group (SRG) of the Media Headquarters.
#SRG(Service Reliability Group) is a group that mainly provides cross-sectional support for the infrastructure of our media services, improving existing services, launching new ones, and contributing to OSS.

[Additional Notes] Introduction

Amazon Aurora Blue/Green deployments are a convenient feature that allows you to safely test database changes (such as version upgrades or schema changes) without affecting your production environment, and then push them into production with minimal downtime.
ROW
However, as of April 2025, it has been confirmed that other parameter settings are also required.
💡
[Additional Note] As of May 2025, there has been a fix on the AWS side, and the error no longer occurs even if you do not change the additional parameters.

Current issues (resolved in May 2025)

ON
  • enforce_gtid_consistency
  • gtid_mode
If these parameters are not set properly, you will see the following error when creating a blue/green deployment:
Even if the UI is set to Japanese, the error message will be displayed in English.
 
If you check the checkbox and select "Next", you will be prompted to enable the two parameters mentioned above on the Blue cluster.

Current situation

There is no guidance in the official user guide.

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

Support has been contacted

A support case has been opened and is currently being investigated.
💡
[Additional Note] As of May 2025, there has been a fix on the AWS side, so the error no longer occurs even if you do not change this parameter.

Countermeasures

The Blue cluster parameters enable two additional parameters:

ON
Note that these parameters are not dynamic and require a cluster reboot for changes to take effect.

Pattern for creating B/G from AWS CLI

Currently, if you create a B/G from the CLI, you can create the B/G without enabling these two parameters.
The following command creates the Green cluster with the same parameter group as Blue.
 
Please note that some people have pointed out that leaving these parameters enabled is safer in terms of replication.
Starting with Aurora MySQL v3.04, the default value for replica_parallel_workers is 4.

Conclusion

Please note that the current behavior of Aurora Blue/Green is not described in the documentation.
We will update this article as soon as we hear back from support regarding the status of the investigation.。
💡
[Additional Note] As of May 2025, there has been a fix on the AWS side, so the error no longer occurs even if you do not change this parameter.
SRG is looking for people to work with us. If you're interested, please contact us here.