A software developer is configuring a deployment pipeline on AWS and needs to store database connection details. The database hostname is public information, but the database password must be encrypted at rest to comply with company security policies. The password is static and does not need automatic rotation. Which configuration should the developer use to meet these requirements securely and with the lowest cost?
- Store the database hostname as a String parameter and the database password as a SecureString parameter in AWS Systems Manager Parameter Store.Cevap
- BStore both the database hostname and the database password as String parameters in AWS Systems Manager Parameter Store.
- CStore the database password as a SecureString parameter in AWS Systems Manager Parameter Store, and enable AWS KMS automatic key rotation to rotate the database password value annually.
- DStore the database password in the AWS account root user credentials to ensure maximum security and access control.
Cevap
Store the database hostname as a String parameter and the database password as a SecureString parameter in AWS Systems Manager Parameter Store.
The correct option proposes storing the hostname as a String parameter and the password as a SecureString parameter in AWS Systems Manager Parameter Store. This configuration is secure because the password is encrypted at rest using AWS KMS, and it is cost-effective because standard parameters in Systems Manager Parameter Store are free of charge, unlike AWS Secrets Manager which incurs a monthly hosting fee.
Adım Adım Çözüm
Anahtar Kavram
Distinguishing between sensitive and non-sensitive configuration data and using appropriate Parameter Store parameter types (String vs. SecureString) to optimize cost and security.