MySQL Single User with Retain Password #152
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Kind of #108
Description of changes:
Added a new template named
SecretsManagerRDSMySQLRotationSingleUserRetainPassword.This template uses superuser secret to login to the MySQL (RDS) server and rotates a single user's password, while retaining its previous password, so that there is no time window where the secret's current version does not work for connecting to the database, hence no downtime without the need to clone users.
MySQL Dual Passwords documentation can be seen here: https://dev.mysql.com/doc/refman/8.0/en/password-management.html#dual-passwords
Since APPLICATION_PASSWORD_ADMIN permission is required to be able to use the
RETAIN CURRENT PASSWORDclause (even when it is for the user's own password), using superuser secret sounded better for this flow. So this template is kind of a mix of MultiUser and SingleUser templates.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.