Community Note
- 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
AWS Health update to migrate to new component
This component "arn:aws:imagebuilder:eu-west-1:aws:component/stig-build-linux-medium/2025.1.0" is deprecated and the recommendation is to migrate to "arn:aws:imagebuilder:eu-west-1:aws:component/stig-build-linux/1.0.x"
We recommend using the arn:aws:imagebuilder:eu-west-1:aws:component/stig-build-linux/1.0.x component as an alternative.
This component requires additional permissions that are not included in the AWS Managed ImageBuilder policies.
"This component requires s3:GetObject IAM permissions attached to the instance profile for the aws-windows-downloads-eu-west-1 S3 bucket resource. For more information, see https://docs.aws.amazon.com/imagebuilder/latest/userguide/ib-stig.html."
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
This is not a major issue but feels like updating the existing policies that have specific 's3' perms already would prevent any issues with migrating to new components. Our pipelines failed when we switched to the new component.
Are you currently working around this issue?
Created a new policy and attached to existing role
Community Note
Tell us about your request
AWS Health update to migrate to new component
This component "arn:aws:imagebuilder:eu-west-1:aws:component/stig-build-linux-medium/2025.1.0" is deprecated and the recommendation is to migrate to "arn:aws:imagebuilder:eu-west-1:aws:component/stig-build-linux/1.0.x"
We recommend using the arn:aws:imagebuilder:eu-west-1:aws:component/stig-build-linux/1.0.x component as an alternative.
This component requires additional permissions that are not included in the AWS Managed ImageBuilder policies.
"This component requires s3:GetObject IAM permissions attached to the instance profile for the aws-windows-downloads-eu-west-1 S3 bucket resource. For more information, see https://docs.aws.amazon.com/imagebuilder/latest/userguide/ib-stig.html."
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
This is not a major issue but feels like updating the existing policies that have specific 's3' perms already would prevent any issues with migrating to new components. Our pipelines failed when we switched to the new component.
Are you currently working around this issue?
Created a new policy and attached to existing role