Providing AWS ReadOnlyAccess

If you are in a situation where you need to provide full AWS ReadOnlyAccess to your environment for a security audit, follow these simple instructions:

Login to AWS

Using the root account or an IAM privileged account login to AWS here: https://console.aws.amazon.com

Access IAM

Click on the Search box in the top-left hand corner and type in IAM. Select the IAM option in the menu.

Create an IAM User Group

  1. On the left hand menu, select User groups.

  2. On the top right hand part of the screen click on the blue Create group button.

  3. For User group name type in SecurityAuditReadOnlyAccess

  4. Under Attach permissions policies select ReadOnlyAccess

    Tip: There are 800+ policies to sift through. Filter by "ReadOnlyAccess" and then sort the Policy Name column in descending order. "ReadOnlyAccess" should be close to the top.

    Screenshot-2023-02-02-121845

  5. Click on the blue Create group button on the bottom when finished.

Create a User

  1. Back on the IAM screen, on the left hand menu, select Users.

  2. On the top right hand part of the screen click on the blue Add users button.

  3. For the User name, type in the organization's name that is providing the security audit.

  4. Check the box for Enable console access

  5. Choose autogenerated password for the console password.

  6. Check the box for Users must create a new password at next sign-in.

    Screenshot-2023-02-02-123100

  7. Click on the Next button on the bottom.

Set Permissions

  1. Select Add user to group from the Permissions Options area.

  2. Check the box next to the group that was previously completed SecurityAuditReadOnlyAccess.

    Screenshot-2023-02-02-123509

  3. Click on the Next button on the bottom.

Review and Create

  1. Your screen should look like this:

    Screenshot-2023-02-02-123728

  2. Click on the Create user button.

  3. On the next screen, the credentials will be displayed.

  4. Click on the Show link next to Console password.

  5. Provide the information below to whomever requires the access.

    Screenshot-2023-02-02-124403

Cleanup Afterwards

Once the security audit engagement is over, remember to delete the user that was created during this process.