MySQL/MariaDB
Learn how to automatically rotate MySQL/MariaDB user passwords.
The Hanzo KMS MySQL secret rotation allows you to automatically rotate your MySQL database user's password at a predefined interval.
Prerequisite
- Create two users with the required permission in your MySQL instance. We'll refer to them as
user-aanduser-b. - Create another MySQL user with just the permission to update the passwords of
user-aanduser-b. We'll refer to this user as theadminuser.
To learn more about MySQL permission system, please visit this documentation.
How it works
- Hanzo KMS connects to your database using the provided
adminuser account. - A random value is generated and the password for
user-ais updated with the new value. - The new password is then tested by logging into the database
- If test is success, it's saved to the output secret mappings so that rest of the system gets the newly rotated value(s).
- The process is then repeated for
user-bon the next rotation. - The cycle repeats until secret rotation is deleted/stopped.
Rotation Configuration
Head over to Secret Rotation configuration page of your project by clicking on Secret Rotation in the left side bar
Rotator admin username
Rotator admin password
Database host url
Database port number
The first username of two to rotate - user-a
The second username of two to rotate - user-b
Optional database certificate to connect with database
When a secret rotation is successful, the updated values needs to be saved to an existing key(s) in your project.
The environment where the rotated credentials should be mapped to.
The secret path where the rotated credentials should be mapped to.
What interval should the credentials be rotated in days.
Select an existing secret key where the rotated database username value should be saved to.
Select an existing select key where the rotated database password value should be saved to.
FAQ
When a system has multiple nodes by horizontal scaling, redeployment doesn't happen instantly.
This means that when the secrets are rotated, and the redeployment is triggered, the existing system will still be using the old credentials until the change rolls out.
To avoid causing failure for them, the old credentials are not removed. Instead, in the next rotation, the previous user's credentials are updated.
The admin account is used by Hanzo KMS to update the credentials for user-a and user-b.
You don't need to grant all permission for your admin account but rather just the permissions to update both of the user's passwords.
How is this guide?
Last updated on