feat(misconf): Add support for aws_ami

[simar7]

Description

Adds support for parsing AWS AMIs.

Related issues

• feat(checks): Add check for checking owners of AMI #8480

Checklist

• I've read the guidelines for contributing to this repository.
• I've followed the conventions in the PR title.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).

[nikpivkin]

@simar7 There is no AWS::EC2::Image resource in CloudFormation, so I removed the adaptation for CF.

[simar7]

Also of interest hashicorp/terraform-provider-aws#40375

[simar7]

@simar7 There is no AWS::EC2::Image resource in CloudFormation, so I removed the adaptation for CF.

Interesting, since there isn't one, CloudFormation users are also at a loss preventing the run of malicious AMIs.

AWS recommends to set the allowed AMIs on an account basis https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-allowed-amis.html

But I do wonder if we will see an equivalent of hashicorp/terraform-provider-aws#40375 in cloudformation.

[nikpivkin]

Interesting, since there isn't one, CloudFormation users are also at a loss preventing the run of malicious AMIs.

Isn't it the other way around? Usually in CloudFormation AMI ID is passed through a parameter, which forces the user to search for the image themselves and prevents using an image with a similar name from an untrusted vendor?

[simar7]

Interesting, since there isn't one, CloudFormation users are also at a loss preventing the run of malicious AMIs.

Isn't it the other way around? Usually in CloudFormation AMI ID is passed through a parameter, which forces the user to search for the image themselves and prevents using an image with a similar name from an untrusted vendor?

Yeah I guess that would be fine then.