In the RDS console, select your Aurora MySQL cluster and choose 'Create Blue/Green Deployment' — AWS provisions a green cluster as a replicated copy of the blue cluster.
Apply the desired changes (engine version upgrade, parameter group changes) to the green cluster while it replicates from blue with low lag.
Test your application against the green cluster endpoint; verify query behavior and performance before switching over.
Initiate switchover from the RDS console or CLI (`aws rds switchover-blue-green-deployment`); Aurora atomically redirects connections — typical switchover takes under a minute.
After switchover confirm the green cluster is now serving production traffic, then delete the old blue cluster after a validation period.
Known gotchas
Blue/green switchover requires replication lag to be near zero; if lag is high at switchover time, the operation waits or times out — monitor `ReplicaLag` before initiating.
Application connection strings that hardcode the cluster endpoint (not the CNAME DNS) may not automatically follow the switchover; use the cluster DNS endpoint, not a static IP.
DDL changes made on the green cluster that are not replication-safe (e.g., some `ALTER TABLE` operations) can break the replication link from blue — apply schema changes carefully during the validation window.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp