The business-license renewal Lambda must obtain RDS credentials at runtime with managed rotation, not from a checked-in .env file in the repository. Which approach meets that requirement?
Select an answer to reveal the explanation.
Short Explanation
Checked-in .env files are yesterday's USB stick under the keyboard. Let the Lambda ask Secrets Manager for the current RDS password when it runs, with rotation doing the heavy lifting.
Full Explanation
AWS Secrets Manager is designed for runtime secret retrieval and rotation integrated with databases such as RDS. The Lambda execution role should allow secretsmanager:GetSecretValue (and related permissions) without embedding credentials in source or build artifacts. Git .env files, hard-coded passwords, and chat distribution fail confidentiality and rotation requirements.