Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
What do you want us to build?
We deploying all EC2 Image Builder resources using AWS CloudFormation templates. Once we like to deploy a subsequent stack-update we must check the drift status for this stack before doing such change (e.g. to avoid issues by changes outside of CloudFormation).
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
As per AWS CloudFormation docs, mostly all of the EC2 Image Builder resources are not supported resource for drift detection. Hence, we are currently not able to run CloudFormation drift detection and check for drifts via AWS Console or via AWS API.
Are you currently working around this issue?
There is no known workaround at the moment available.
Community Note
Tell us about your request What do you want us to build? We deploying all EC2 Image Builder resources using AWS CloudFormation templates. Once we like to deploy a subsequent stack-update we must check the drift status for this stack before doing such change (e.g. to avoid issues by changes outside of CloudFormation).
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? As per AWS CloudFormation docs, mostly all of the EC2 Image Builder resources are not supported resource for drift detection. Hence, we are currently not able to run CloudFormation drift detection and check for drifts via AWS Console or via AWS API.
Are you currently working around this issue? There is no known workaround at the moment available.
Additional context We opened a github issue with CloudFormation Team/Roadmap-Repo: https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/1548