An application deployed on AWS needs to query a third-party weather forecasting service. The application requires access to two configuration settings: a sensitive API access token that must be rotated automatically every 30 days, and a non-sensitive API endpoint URL that does not change. To minimize costs while maintaining a secure architecture, which of the following configurations should a solutions architect recommend?
- Store the API access token in AWS Secrets Manager and configure a custom AWS Lambda function to rotate the token every 30 days. Store the API endpoint URL in AWS Systems Manager Parameter Store as a String parameter.Answer
- BStore both the API access token and the API endpoint URL as String parameters in AWS Systems Manager Parameter Store, and configure Parameter Store to rotate the token parameter automatically every 30 days.
- CStore the API access token as a SecureString parameter in AWS Systems Manager Parameter Store, and enable automatic rotation of the associated KMS Customer Managed Key (CMK) every 30 days to rotate the token value.
- DStore the API access token in AWS Systems Manager Parameter Store as a String parameter, and use a custom AWS Lambda function to encrypt the parameter and rotate the backing KMS key every 30 days.
Answer
Store the API access token in AWS Secrets Manager and configure a custom AWS Lambda function to rotate the token every 30 days. Store the API endpoint URL in AWS Systems Manager Parameter Store as a String parameter.
The correct configuration uses AWS Secrets Manager for the sensitive API access token because it provides secure encryption and supports automated rotation through custom AWS Lambda functions. To minimize costs, the non-sensitive, static API endpoint URL is stored in AWS Systems Manager Parameter Store as a standard String parameter, which is free of charge.
Step-by-Step Solution
Key Concept
Selecting between AWS Secrets Manager and Systems Manager Parameter Store based on security, rotation requirements, and cost.