Other Articles
- IAM - Enable User MFA
- IAM - Enforce Key Rotation
- IAM - Enforce Active Key Limit
- IAM - Disable Unused User Credentials
- IAM - Enforce Group Permission
- IAM - Enforce Password Length
- IAM - Prohibit Password Reuse
- IAM - Check Root Access Keys Existence
- IAM - Enable Root MFA
- IAM - Enable Key Rotation
- Purge Expired Certificates
- EC2 Volume – Enable EBS Volume Backup
- EC2 Volume – Enable EBS Encryption
- EFS – Enable EFS Storage Backup
- S3 Bucket – Enable S3 Bucket Versioning
- S3 Bucket – Enable S3 Bucket Encryption
- S3 Bucket – Block S3 Bucket Public Access
- RDS DB Instance – Encryption of Storage
- RDS DB Instance – Enable Deletion Protection
- RDS DB Instance – Enable Auto Minor Version Upgrade
- DynamoDB Table – Enable Table Encryption
- DynamoDB Table – Enable Table Point In Time Recovery
- DynamoDB Table – Enable Table Deletion Protection
- EC2 Instance – Monitor CPU Utilization
- ECS Service – Monitor CPU Utilization
- ECS Service – Monitor Memory Utilization
- RDS DB Instance – Monitor Free Storage Space
- RDS DB Instance – Monitor CPU Utilization
- SQS Queue – Monitor Message Age
- SQS Queue – Monitor Message Visibility
- DynamoDB Table – Monitor Table Read Capacity
- DynamoDB Table – Monitor Table Write Capacity
- DynamoDB Table – Monitor Table Latency
- Enable CloudTrail
- Encrypt CloudTrail Logs
- EC2 VPC – Ensure Flow Logs are Enabled
- RDS DB Instance – Block Public Access
- EC2 Instance – Enable Deletion Protection
- ECS Service – Enable Auto Scaling
- Enable AWS Security Hub
- Enable GuardDuty
IAM - Establish Support Role
Secure Configuration Checks > AWS
This check ensures that an IAM role with AWS Support permissions is established. A dedicated support role allows authorized users to manage AWS support cases securely without granting excessive permissions.
Check Details
- Resource: General
- Check: Establish support role
- Risk: Inability to manage AWS support incidents securely
Remediation via AWS Console
-
Log in to the AWS Management Console and open the IAM service.
-
Under Access management, click Policies.
-
In the policy search field, search for AWSSupportAccess.
- Click the policy name AWSSupportAccess.
-
Open the Entities attached tab and click Attach.
-
Select the appropriate IAM role or roles and click Attach policy.
Remediation via AWS CLI
-
Log in to the AWS Management Console and click the CloudShell icon (
>_) in the top-right corner.
-
Create a trust policy file:
nano /tmp/TrustPolicy.json
Replace
<iam_user>with the IAM user ARN and paste:{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": "<iam_user>" }, "Action": "sts:AssumeRole" } ] }Press CTRL + O → Enter → CTRL + X.
-
Create the IAM role:
aws iam create-role \ --role-name <aws_support_iam_role> \ --assume-role-policy-document file:///tmp/TrustPolicy.json
-
Attach AWS Support permissions to the role:
aws iam attach-role-policy \ --policy-arn arn:aws:iam::aws:policy/AWSSupportAccess \ --role-name <aws_support_iam_role>
-
Verify the role has the required policy attached:
aws iam list-attached-role-policies \ --role-name <aws_support_iam_role>
Updated on 06 March, 2026