Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RDS: Verify and Update User Guide for DB Upgrade with Replica #6759

Open
9 tasks
timckt opened this issue Jan 31, 2025 · 1 comment
Open
9 tasks

RDS: Verify and Update User Guide for DB Upgrade with Replica #6759

timckt opened this issue Jan 31, 2025 · 1 comment

Comments

@timckt
Copy link
Contributor

timckt commented Jan 31, 2025

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.

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"

Our RDS module is using DB instance.

Approach

Which part of the user docs does this impact

  • Create the primary and replica db in the testing namespace
  • Verify the correct approach with upgrading the primary and replica with no pipeline error
  • Update the user guide with correct verified approach

Communicate changes

  • post for #cloud-platform-update
  • Weeknotes item
  • Show the Thing/P&A All Hands/User CoP
  • Announcements channel

Questions / Assumptions

Definition of done

  • readme has been updated
  • user docs have been updated
  • another team member has reviewed
  • smoke tests are green
  • prepare demo for the team

Reference

How to write good user stories

@timckt
Copy link
Contributor Author

timckt commented Feb 12, 2025

This ticket shall be done asap and completed in next sprint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

2 participants