1 Answer
- Newest
- Most votes
- Most comments
0
A list of prechecks for moving from Aurora SQL 5.7 to 8.x
To minimize downtime during a major version upgrade, use blue-green upgrade Please note, using blue-green upgrade, source cluster should be binary log enabled. To do this, perform engine restart to enable binary log and may cause some performance impact due to additional resource consumption by writing and shipping binary log.
Another option is in-place upgrade You can estimate upgrade time by create cloned cluster and upgrade it for measuring upgrade time.
Please accept this answer if it is helpful so re:Post community will benefit. Thank you!
answered 8 months ago
Relevant content
- Accepted Answerasked 2 years ago
- Accepted Answerasked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 months ago
I understand Blue-green is an option, however, the concern here is that the Clusters are fronted by an RDS Proxy which currently doesn't support Blue-Green Deployment. So with a cluster that is fronted with RDS Proxy, how would a blue-green implementation work?