This rule ensures creation of a support role for managing incidents with AWS Support.
Rule | Ensure a support role has been created to manage incidents with AWS Support |
Framework | cis_v140 |
Severity | ✔ Medium |
Ensure a Support Role Has Been Created to Manage Incidents with AWS Support for CIS v1.4.0
Creating a dedicated support role within your AWS account allows you to manage incidents with AWS Support more effectively. It adheres to the Center for Internet Security (CIS) Amazon Web Services Foundations Benchmark v1.4.0.
Description of the Rule
This rule requires an AWS Identity and Access Management (IAM) role specifically designed for managing incidents and support cases with AWS Support. This role is assumed by authorized AWS personnel when they need to access your AWS environment to assist with support-related tasks.
The role must have permissions that are narrowly scoped to enable AWS Support to perform necessary actions while adhering to the principle of least privilege. AWS provides an AWS-managed policy called
AWSSupportAccess
to facilitate this. Compliance with this rule ensures that you are prepared to handle incidents promptly with minimal disruption to your services.Troubleshooting Steps
If you confirm that a support role has not been created or has been misconfigured, follow these steps to address the issue:
Necessary Policies and Permissions
The support role must have the
AWSSupportAccess
managed policy attached. This policy contains the necessary permissions for AWS Support to assist you.Step by Step Guide for Remediation
Step 1: Create the Support Role
Roles
on the left sidebar and then Create role
.Another AWS account
for the role type, and provide the AWS account ID as per AWS Support's instructions.Require external ID
and Require MFA
for this role.Next: Permissions
.AWSSupportAccess
managed policy.Next: Tags
(optional step to add any metadata tags).Next: Review
.AWS_Support_Role
) and provide a description.Create role
.Step 2: Verify Role Configuration
Roles
.AWS_Support_Role
to check its details.AWSSupportAccess
is listed under Attached Policies.Step 3: Test the Role (Optional)
AssumeRole
API to test the role assumption process.CLI Commands Required
To create the support role via AWS CLI, you can use the following command:
aws iam create-role \ --role-name AWS_Support_Role \ --assume-role-policy-document file://support-role-trust-policy.json
Replace
support-role-trust-policy.json
with the path to your trust policy file. Once the role is created, run the following command to attach the AWSSupportAccess
policy:aws iam attach-role-policy \ --role-name AWS_Support_Role \ --policy-arn arn:aws:iam::aws:policy/AWSSupportAccess
Note: Be sure to have the AWS CLI installed and configured with the necessary permissions to perform these operations.
Conclusion
By following this detailed guide, you can ensure a support role has been created to align with the CIS Amazon Web Services Foundation Benchmark v1.4.0 standards. Proper configuration and testing of this role will facilitate efficient incident management with AWS Support.
For additional assurance of compliance and optimization for SEO, regularly review the role and attached policy to ensure that it's configured according to the latest AWS best practices and CIS benchmarks.