Ensure Managed IAM Policies are used instead of Inline Policies

AWS remediation

Console

1. Locate identities with inline policies.
2. Create equivalent customer-managed policies.
3. Attach managed policies.
4. Remove inline policies.

AWS CLI

aws iam create-policy --policy-name <policy-name> --policy-document file://policy.json
aws iam attach-role-policy --role-name <role-name> --policy-arn arn:aws:iam::<account-id>:policy/<policy-name>
aws iam delete-role-policy --role-name <role-name> --policy-name <inline-policy-name>

References

• https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html
• https://docs.aws.amazon.com/cli/latest/reference/iam/

Service-wide remediation

Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.

AWS

Use AWS Organizations guardrails, AWS Config rules or conformance packs where they fit, approved account baselines, and IaC modules so new resources inherit the secure setting.

Operational rollout

1. Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
2. Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
3. Re-scan and track approved exceptions with an owner and expiry date.