A developer is designing a microservice application deployed on Amazon Elastic Kubernetes Service (Amazon EKS). The microservice requires access to two types of data: database credentials for an Amazon RDS for PostgreSQL instance that must be automatically rotated every 30 days, and non-sensitive API endpoints for external integration that vary by environment. Which combination of actions should the developer take to store and manage this data securely and cost-effectively? (Select TWO.)
- Store the database credentials in AWS Secrets Manager and configure automatic rotation using the built-in RDS rotation template.Cevap
- Store the non-sensitive API endpoints in AWS Systems Manager Parameter Store as String parameters.Cevap
- CStore the database credentials in AWS Systems Manager Parameter Store as SecureString parameters, and configure an Amazon EventBridge rule to trigger a custom Lambda function to rotate the credentials.
- DStore the non-sensitive API endpoints in AWS Secrets Manager to centralize all application configuration and enable automatic rotation.
- EHardcode the database credentials in the application's source code and use the AWS SDK to decrypt them at runtime using a customer managed key in AWS KMS.
Cevap
Store the database credentials in AWS Secrets Manager with built-in automatic rotation, and store the non-sensitive API endpoints in AWS Systems Manager Parameter Store as String parameters.
Storing database credentials in AWS Secrets Manager takes advantage of native automatic rotation with Amazon RDS, removing the need to manage custom rotation code. Storing non-sensitive configuration parameters like API endpoints in AWS Systems Manager Parameter Store as String parameters is cost-effective because Parameter Store standard parameters are free, whereas Secrets Manager charges per secret.
Adım Adım Çözüm
Anahtar Kavram
Differentiating between AWS Secrets Manager and Systems Manager Parameter Store based on security, rotation, and cost requirements.
Tahmini Süre:2m 0s