Aurora MySQL
Britive integrates with Amazon Aurora MySQL through the Britive Access Broker. The broker uses the mysql client to create temporary database users at checkout and drop them at checkin. Admin credentials are retrieved from AWS Secrets Manager — never stored on the broker host.
Access Patterns
Two patterns are available:
- Role access — creates a temporary MySQL user and grants a specific table-level privilege (e.g.
SELECT). Use for scoped, least-privilege access. - Temporary user — creates a temporary MySQL user with
ALLprivileges on the target database. Use for admin or DBA sessions.
The broker must have network access to the Aurora cluster endpoint on port 3306. AWS Secrets Manager must be reachable from the broker host for credential retrieval.
In This Section
- Getting Started
Set up the Britive Access Broker for JIT access to Amazon Aurora MySQL — install dependencies, create a service account, store credentials in AWS Secrets Manager, and register the cluster as a resource.
- Role-Based Access
Create a temporary MySQL user and grant a table-level privilege at checkout — revoke and drop the user at checkin. Uses AWS Secrets Manager for admin credentials.
- Temporary User Access
Create a temporary MySQL user with ALL privileges on the target database at checkout — drop the user at checkin. Uses AWS Secrets Manager for admin credentials.