A company is deploying a three-tier application on Amazon EC2. The database password must be stored securely and retrieved dynamically by the application. Additionally, the application's Amazon EBS volumes must be encrypted at rest using an AWS KMS customer managed key that undergoes automatic annual rotation, while ensuring that all existing snapshots remain readable. Which combination of actions will meet these requirements? (Select TWO.)
- AStore the database password in AWS Systems Manager Parameter Store as a parameter of type String.
- Store the database password in AWS Systems Manager Parameter Store as a parameter of type SecureString.Answer
- Enable automatic key rotation for the customer managed key in AWS KMS.Answer
- DManually create a new customer managed key each year, associate it with the EBS volumes, and re-encrypt all historical snapshots.
- EUse the default AWS managed key aws/ebs for volume encryption and enable automatic rotation on it.
Answer
Storing the database password as a SecureString parameter in Systems Manager Parameter Store, and enabling automatic key rotation on the KMS customer managed key used for EBS volume encryption.
Storing the database password as a SecureString parameter in Systems Manager Parameter Store ensures that the password is encrypted at rest using a KMS key. Enabling automatic key rotation for the customer managed key in AWS KMS automatically rotates the key material annually. AWS KMS retains all historical backing key versions, allowing the system to seamlessly decrypt older snapshots encrypted with previous key versions without any manual re-encryption or reconfiguration.
Step-by-Step Solution
Key Concept
AWS KMS Customer Managed Key rotation mechanics and secure parameter storage using Systems Manager Parameter Store