Deleting access keys for the root user - Amazon Identity and Access Management
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Deleting access keys for the root user

You can use the Amazon Web Services Management Console, the Amazon CLI or the Amazon API to delete the root user access keys.

Amazon Web Services Management Console
To delete an access key for the root user
Minimum permissions

To perform the following steps, you must have at least the following IAM permissions:

  • You must sign in as the Amazon Web Services account root user, which requires no additional Amazon Identity and Access Management (IAM) permissions. You can't perform these steps as an IAM user or role.

  1. Use your Amazon Web Services account's email address and password to sign in to the Getting Started with the Amazon Web Services Management Console as your Amazon Web Services account root user.

  2. In the upper right corner of the console, choose your account name or number and then choose Security Credentials.

  3. In the Access keys section, select the access key that you want to delete, and then, under Actions, choose Delete.

    Note

    Alternatively, you can Deactivate an access key, instead of permanently deleting it. This way you can resume using it in the future without having to change either the key ID or secret key. While the key is inactive, any attempts to use it in requests to the Amazon API fail with the error access denied.

  4. On the Delete <access key ID> dialog box, choose Deactivate, enter the access key ID to confirm you want to delete it, and then choose Delete.

Amazon CLI & SDKs
To delete an access key for the root user
Minimum permissions

To perform the following steps, you must have at least the following IAM permissions:

  • You must sign in as the Amazon Web Services account root user, which requires no additional Amazon Identity and Access Management (IAM) permissions. You can't perform these steps as an IAM user or role.