An online gaming studio uses AWS Organizations to manage its game development, testing, and production environments. The environment includes a parent organizational unit (OU) called Engineering, which contains a child OU named Game-Dev for individual game development teams. To maintain compliance, the security team has deployed a centralized auditing IAM role named SecurityAuditRole in all member accounts under the Game-Dev OU. The security team wants to ensure that local administrators in the Game-Dev accounts cannot delete, modify, or detach policies from the SecurityAuditRole, while still retaining full administrative control over other resources. Which solution should the solutions architect implement to meet these requirements with the least administrative effort?
- Attach a Service Control Policy (SCP) to the Game-Dev OU that denies iam:DeleteRole, iam:UpdateAssumeRolePolicy, iam:PutRolePolicy, iam:DeleteRolePolicy, iam:AttachRolePolicy, and iam:DetachRolePolicy actions when the resource is the SecurityAuditRole ARN.Answer
- BDefine an IAM Permission Boundary in the Game-Dev member accounts that denies modifications to the SecurityAuditRole, and require all developers to attach this boundary when creating new IAM users or roles.
- CConfigure a SAML 2.0 identity provider (IdP) in each member account and configure the trust policy of SecurityAuditRole to allow access only from the central security account's IdP entity.
- DEnable AWS KMS encryption using an AWS-managed key (aws/iam) in the management account to encrypt the configuration of the SecurityAuditRole, and restrict access to this key.