MENU
Jarrad is an AWS engineer and has provisioned a new EC2 instance running MySQL since his application requires a specific MySQL version. He wants to integrate Vault into his workflow but is new to Vault. What secrets engine should Jarrad use to integrate this new database running in AWS?
Comprehensive and Detailed In-Depth
For integrating a MySQL database on an EC2 instance with Vault, the database secrets engine is the appropriate choice:
B . database: 'The 'database' secrets engine in Vault is specifically designed for integrating with databases like MySQL.' It generates dynamic credentials, manages rotations, and supports MySQL plugins, ideal for Jarrad's use case. 'To manage the database resource, the database secrets engine should be used, specifically with the MySQL plugin.'
Incorrect Options:
A . azure: For Azure-specific credential management, not databases. 'Used for generating Azure service principal credentials.'
C . kv: Stores static secrets, not dynamic database credentials. 'Used for storing arbitrary secrets in a key-value pair format.'
D . aws: Manages AWS credentials, not database integration. 'Used for generating AWS access keys.'
The database engine's MySQL support is agnostic to the hosting platform (EC2 vs. RDS), focusing on the database itself.