This website uses cookies to ensure you get the best experience.
Learn more.
A long-lived IAM access key is exposed in a public repository. Which sequence best limits risk while supporting investigation?
Published
- Rename the IAM user while retaining the same active key.
- Disable the exposed credential, assess its activity and permissions, and replace dependent access safely.
- Delete CloudTrail logs to avoid retaining the exposed key identifier.
- Rotate only the repository password while leaving the AWS key active.
Comments — 0
Sign in to comment