Check ID:
Provider: AWS
Service:
Severity: LOW
Categories:
Resource type:
iam_support_role_createdProvider: AWS
Service:
iamSeverity: LOW
Categories:
identity-accessResource type:
AwsIamRoleWhat this check verifies
Presence of an IAM role that has the AWS managedAWSSupportAccess policy attached, designating a support role for interacting with AWS Support Center and related tooling.
Risk
Without a dedicated support role:- Case creation and escalation can be delayed, prolonging outages (availability)
- Teams may use admin/root, increasing blast radius (confidentiality/integrity)
- Audit trails of support actions are weaker, hindering investigations
Recommendation
Create a dedicated IAM role for AWS Support withAWSSupportAccess and:
- Restrict who can assume it; require MFA and time-bound access
- Enforce least privilege and separation of duties
- Monitor usage via audit logs and review assignments regularly
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/awssupport/latest/user/using-service-linked-roles-sup.html
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/IAM/support-role.html
- https://icompaas.freshdesk.com/support/solutions/articles/62000081064-ensure-a-support-role-has-been-created-to-manage-incidents-with-aws-support
- https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSSupportAccess.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = iam_support_role_created. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks