You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our current user guide, it mentioned that if users are using replica db, they will need to upgrade the replica major version after upgrading the primary DB.
If you have a read replica of your database, you will also need to update the db_engine_version and rds_family attributes to your new major version after the upgrade of your primary database has finished
However, from AWS doc, it seems AWS changed the approach compared to when the user guide was written.
For Major version upgrades,
If you upgrade a DB instance that has in-Region read replicas, Amazon RDS upgrades the replicas along with the primary DB instance.
For Minor version upgrades,
If your database has read replicas, you must first upgrade all of the read replicas before you upgrade the source instance or cluster.
Verify and Update the user guide for the correct approach.
Remarks:
There are 2 DB deployments for RDS.
Multi-AZ DB instance- resource "aws_db_instance" "default"
Multi-AZ DB cluster- resource "aws_rds_cluster" "default"
Background
In our current user guide, it mentioned that if users are using replica db, they will need to upgrade the replica major version after upgrading the primary DB.
However, from AWS doc, it seems AWS changed the approach compared to when the user guide was written.
For Major version upgrades,
For Minor version upgrades,
Verify and Update the user guide for the correct approach.
Remarks:
There are 2 DB deployments for RDS.
resource "aws_db_instance" "default"
resource "aws_rds_cluster" "default"
Our RDS module is using DB instance.
Approach
Which part of the user docs does this impact
Communicate changes
Questions / Assumptions
Definition of done
Reference
How to write good user stories
The text was updated successfully, but these errors were encountered: