An operations team is setting up a deployment pipeline and needs to store a sensitive API token that Amazon ECS tasks will use to access a third-party service. The solutions architect decides to store the token in AWS Systems Manager Parameter Store. Which configuration should the solutions architect choose to store and protect the token?
- ACreate a Parameter Store parameter using the String type, storing the token directly in the parameter value to reduce API latency.
- BCreate a Parameter Store parameter using the String type, and rely on AWS KMS automatic key rotation to secure the plaintext value.
- Create a Parameter Store parameter using the SecureString type, which encrypts the token using an AWS Key Management Service (AWS KMS) key.Cevap
- DCreate a Parameter Store parameter using the SecureString type, expecting that rotating the underlying KMS key will immediately re-encrypt all historical parameter versions.
Cevap
Create a Parameter Store parameter using the SecureString type, which encrypts the token using an AWS Key Management Service (AWS KMS) key.
The correct option is to use a SecureString parameter in Systems Manager Parameter Store. This configuration automatically encrypts the sensitive API token at rest using an AWS KMS key. This prevents unauthorized users from viewing the credentials in plaintext and adheres to AWS security best practices.
Adım Adım Çözüm
Anahtar Kavram
Using Systems Manager Parameter Store SecureString parameters encrypted with AWS KMS to securely store sensitive configuration data.