It’s a best practice to change your passwords on a regular basis to avoid unauthorized use of your account. For information about AWS security best practices, see the AWS Security Best Practices whitepaper.

Delete or rotate any potentially compromised AWS access keys

If you find AWS access keys that you no longer need or didn’t create, delete them. For more information about deleting access keys, see How do I delete an AWS access key?

If your application currently uses an exposed access key, replace the exposed key with a new one. To do this, create a second key and modify your application to use the new key, and then disable (but do not delete) the first key. If there are any problems with your application, reactivate the key temporarily. When your application is fully functional and the first key is in the disabled state, delete the first key.

If you received correspondence from AWS about potential issues with your account, sign in to the AWS Support Center and respond to the notification with any information AWS Support requested from you. If you have any additional questions or concerns, but didn’t receive a notification, create a new AWS support case in the AWS Support Center.

Note: Do not include potentially sensitive information in your correspondence, including full AWS access keys, passwords, or credit card information.

Use AWS Git projects to scan for evidence of compromise

AWS offers Git projects you can install that can help you protect your account:

Git Secrets can scan merges, commits, and commit messages for secret information (e.g. access keys). If it detects prohibited regular expressions, it can reject those commits from being posted to public repositories.