Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
CIS Amazon Web Services Foundations v7.0.0 · 2.15

A dedicated IAM role should exist for working with AWS Support

  • Level 1

This check looks at whether your AWS account has an IAM role that carries the AWSSupportAccess managed policy and can be assumed by the people who handle incidents. The safe setting is one such role, so support access does not depend on a root or full-admin login.

Why it matters

AWS Support cases are opened and read through IAM permissions. Without a purpose-made role, teams tend to fall back on the root user or hand out broad administrator rights just so someone can contact support during an incident. A named role with only the support permissions keeps that access small, easy to audit and easy to remove.

AWS provides the managed policy AWSSupportAccess for exactly this purpose, and its documentation describes granting Support access through IAM users, groups or roles. See the sources below.

How to check it yourself

In the IAM console open Policies, search for AWSSupportAccess, open it and look at the Entity attached tab. At least one role should be listed.

The same check with the AWS CLI is read-only:

aws iam list-entities-for-policy \
  --policy-arn arn:aws:iam::aws:policy/AWSSupportAccess

An empty PolicyRoles list means no role carries the policy. Run it with a read-only IAM profile.

How to fix it

In the IAM console choose Roles → Create role, pick the trusted entity (usually your own account, or your identity provider), attach AWSSupportAccess, name the role and create it. Then allow your incident responders to assume it, ideally only with MFA.

With the AWS CLI (the account ID below is a placeholder):

cat > trust.json <<'EOF'
{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Principal": {"AWS": "arn:aws:iam::111122223333:root"},
    "Action": "sts:AssumeRole",
    "Condition": {"Bool": {"aws:MultiFactorAuthPresent": "true"}}
  }]
}
EOF
aws iam create-role --role-name aws-support-incident-role \
  --assume-role-policy-document file://trust.json
aws iam attach-role-policy --role-name aws-support-incident-role \
  --policy-arn arn:aws:iam::aws:policy/AWSSupportAccess

You run this yourself. ConfigCobra reads your account through a read-only role and never creates or changes IAM resources; it reports the finding and suggests these steps.

What changes when you fix it

Creating the role does not touch any running workload. The effect is on people: whoever is allowed to assume it can open, view and update Support cases for the account, so decide who that should be and require MFA for the assume-role step. Which kinds of cases you can open still depends on the AWS Support plan on the account.

Tell the incident team the role name and how to switch to it, and write it into your incident runbook. If you currently rely on the root user for Support, you can stop doing that once the role works. Review the role's trust policy now and then to keep the list of people who can assume it current.

Included in

BenchmarkCIS IDProfile
CIS Amazon Web Services Foundations v7.0.02.15Level 1

Check this on your AWS

ConfigCobra runs this check with every other control of the CIS Amazon Web Services Benchmarks, read-only.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial