A company is moving an on-premises application to Amazon EC2. The application needs to retrieve a sensitive API credential for an external payment service and a non-sensitive API endpoint URL for a weather forecasting service. A solutions architect needs to design a configuration storage strategy that is secure, cost-effective, and minimizes administrative overhead.
Which combination of steps should the solutions architect take to meet these requirements? (Select TWO.)
- Store the payment service API credential as a SecureString parameter in AWS Systems Manager Parameter Store.Cevap
- Store the weather forecasting service API endpoint URL as a String parameter in AWS Systems Manager Parameter Store.Cevap
- CStore the payment service API credential as a String parameter in AWS Systems Manager Parameter Store.
- DStore the weather forecasting service API endpoint URL as a SecureString parameter and configure AWS KMS to automatically rotate the parameter value every 24 hours.
- EStore the payment service API credential as a String parameter in AWS Systems Manager Parameter Store and enable KMS automatic key rotation to automatically update the credential value.
Cevap
Store the payment service API credential as a SecureString parameter in AWS Systems Manager Parameter Store, and store the weather forecasting service API endpoint URL as a String parameter in AWS Systems Manager Parameter Store.
Storing the sensitive payment service API credential as a SecureString parameter in Systems Manager Parameter Store provides automatic encryption at rest using AWS KMS. Storing the non-sensitive weather forecasting service API endpoint URL as a standard String parameter in Parameter Store is the most secure and cost-effective approach, avoiding unnecessary KMS costs while utilizing a centralized parameter management solution.
Adım Adım Çözüm
Anahtar Kavram
AWS Systems Manager Parameter Store supports String parameters for plaintext configurations and SecureString parameters for sensitive configuration data encrypted by AWS KMS.