An organization's software application requires access to two configurations: a static partner API token that does not change, and a backend database password that must rotate automatically every 45 days. The organization wants a cost-effective solution that keeps both secrets encrypted at rest. Which two actions should a solutions architect take to meet these requirements? (Select TWO.)
- Store the database password in AWS Secrets Manager and configure automatic rotation.Cevap
- Store the static partner API token as a SecureString parameter in AWS Systems Manager Parameter Store.Cevap
- CStore the database password as a String parameter in AWS Systems Manager Parameter Store.
- DStore the database password as a SecureString parameter in AWS Systems Manager Parameter Store and enable automatic rotation on the default aws/ssm KMS key.
- EStore the static partner API token as a String parameter in AWS Systems Manager Parameter Store and restrict access using a custom IAM policy.
Cevap
Store the database password in AWS Secrets Manager and configure automatic rotation, and store the static partner API token as a SecureString parameter in AWS Systems Manager Parameter Store.
AWS Secrets Manager is ideal for credentials that require lifecycle management and automatic rotation. Storing the static partner API token as a SecureString parameter in AWS Systems Manager Parameter Store is the most cost-effective and secure method for static secrets that do not require rotation.
Adım Adım Çözüm
Anahtar Kavram
Choosing between AWS Secrets Manager and AWS Systems Manager Parameter Store based on rotation requirements and cost.