A SysOps administrator has configured automatic rotation for a database credential stored in AWS Secrets Manager. During the first scheduled rotation, the administrator notices that the rotation status changes to failed, and the database credentials are not updated. Which of the following is the most likely cause of this rotation failure?
- AThe database instance is missing an IAM service role that grants access to decrypt the secret using the customer managed KMS key.
- BThe administrator's IAM policy is missing the iam:PassRole permission required to associate the rotation role with the database.
- The AWS Lambda rotation function cannot network-communicate with the database endpoint to update the credentials.Answer
- DThe Systems Manager Automation document lacks an EventBridge trigger to schedule the secret rotation.
Answer
The AWS Lambda rotation function cannot network-communicate with the database endpoint to update the credentials.
For AWS Secrets Manager to rotate a database credential, it runs an AWS Lambda rotation function that connects to the database to update the password. If the Lambda function cannot establish a network connection to the database (e.g., due to VPC security groups, network access control lists, or routing rules), the rotation process fails.
Step-by-Step Solution
Key Concept
Secrets Manager automatic rotation requires a Lambda rotation function that has both the correct database access permissions and direct network connectivity to the target database endpoint.
Estimated Time:1m 0s