Ensure AMIs Are Private

AWS remediation

Console

1. Open the AMI in EC2.
2. Select Actions -> Edit AMI permissions.
3. Remove public launch permission (All).
4. Keep sharing only with specific AWS accounts if needed.

AWS CLI

aws ec2 modify-image-attribute \
  --image-id <ami-id> \
  --launch-permission "Remove=[{Group=all}]"

aws ec2 modify-image-attribute \
  --image-id <ami-id> \
  --launch-permission "Add=[{UserId=<account-id>}]"

References

• https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sharingamis-explicit.html
• https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-image-attribute.html

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.