Amazon EC2 Allowed AMIs now integrates with AWS Config

[Allowed AMIs](https://aws.amazon.com/about-aws/whats-new/2024/12/amazon-ec2-allowed-amis-enhance-ami-governance/), an account-wide Amazon EC2 setting that enables you to limit the discovery and use of Amazon Machine Images (AMIs) within your AWS accounts, now integrates with AWS Config. You can now use AWS Config rules to automatically monitor, detect, and report instances launched using AMIs that have not been allowed by Allowed AMIs. Prior to today, you had to create custom scripts to monitor instance launches and assess the impact of enabling Allowed AMIs. Now with the integration of Allowed AMIs with AWS Config, you can track and detect non-compliant instances using the new [AWS Config rule](https://docs.aws.amazon.com/config/latest/developerguide/ec2-instance-launched-with-allowed-ami.html). By leveraging this rule in conjunction with the audit-mode functionality of Allowed AMIs, you can gain valuable insights into your instance launch patterns and identify any potential issues before enforcing stricter controls. This rule scans existing instances and monitors new instance launches, flagging instances launched with unapproved AMIs. This capability enables you to proactively identify and remediate violations before enabling Allowed AMIs in your accounts, simplifying governance across your AWS environment. By default, this rule is disabled for all AWS accounts. You can enable it by using the AWS CLI, SDKs, or Console. To learn more, please visit our [documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-allowed-amis.html#identify-instances-with-allowed-AMIs).