A developer is designing a serverless data ingestion application on AWS Lambda. The application requires access to a third-party service API key that must be rotated automatically every 30 days, as well as a non-sensitive database port number that does not change. To minimize cost and operational overhead, which two actions should the developer take to store and manage these parameters? (Select TWO.)
- Store the API key in AWS Secrets Manager and configure a Lambda function to handle the rotation.Answer
- Store the database port number in AWS Systems Manager Parameter Store as a Standard parameter.Answer
- CStore both the API key and the database port number in AWS Secrets Manager to centralize credential storage.
- DStore the API key in Systems Manager Parameter Store as a SecureString parameter and configure the native Parameter Store auto-rotation policy.
- EHardcode the API key directly in the Lambda function's source code to avoid external service calls.
Answer
Store the API key in AWS Secrets Manager with a Lambda rotation function, and store the database port number in AWS Systems Manager Parameter Store as a Standard parameter.
The correct options are to store the API key in AWS Secrets Manager with a Lambda rotation function, and to store the database port in AWS Systems Manager Parameter Store as a Standard parameter. AWS Secrets Manager is appropriate because it supports automatic rotation out-of-the-box. Systems Manager Parameter Store Standard parameters are the correct choice for non-sensitive data because they do not incur a monthly configuration cost.
Step-by-Step Solution
Key Concept
Selecting between AWS Secrets Manager and Systems Manager Parameter Store based on cost, sensitivity, and automatic rotation requirements.