A developer is deploying a containerized application to Amazon Elastic Kubernetes Service (Amazon EKS). The application requires access to a database password for an Amazon RDS DB instance and an API key for a third-party service. The database password must be rotated every 30 days. The third-party API key changes infrequently, and the developer wants to access it with minimum latency and cost. Which combination of steps should the developer take to retrieve these configurations securely and cost-effectively? (Select TWO.)
- Store the database password in AWS Secrets Manager and configure automatic rotation using an AWS Lambda function.Cevap
- Store the third-party API key as a SecureString parameter in AWS Systems Manager Parameter Store and retrieve it via the application.Cevap
- CStore the database password in Systems Manager Parameter Store and enable native Parameter Store automatic rotation.
- DStore the third-party API key in AWS Secrets Manager to leverage its built-in rotation and access rate capabilities.
- EHardcode the database password and the API key directly into the Kubernetes deployment manifest file as environment variables.
Cevap
Store the database password in AWS Secrets Manager with Lambda rotation, and store the third-party API key as a SecureString parameter in AWS Systems Manager Parameter Store.
The correct combination involves storing the database password in AWS Secrets Manager because it natively supports automatic rotation via Lambda, and storing the third-party API key in AWS Systems Manager Parameter Store as a SecureString parameter because standard parameters are free and ideal for infrequently changing secrets.
Adım Adım Çözüm
Anahtar Kavram
Selecting between AWS Secrets Manager and Systems Manager Parameter Store based on rotation, cost, and lifecycle requirements.