Packer: Feature Request: Temporary names for unencrypted AMIs when using encrypt_boot: true

Created on 12 Jul 2018  ยท  7Comments  ยท  Source: hashicorp/packer

Packer's amazon-ebs builder, when using encrypt_boot: true, currently uses the same name for the temporary unencrypted AMIs as it does for the resulting encrypted AMIs.

This results in a race condition where the unencrypted AMIs may be returned when searching for the "latest" AMI matching a naming convention.

Since there is clearly no intention to use the unencrypted AMIs and they are deregistered/deleted once the packer process finishes, it would seem better to create the unencrypted AMIs as temporary resources using a temporary naming scheme.

Alternatively, the simplest solution to prevent this type of race condition would be greatly appreciated

bug buildeamazon

Most helpful comment

I can work on this, would be good for me to understand packer in more details. If no one is working on it.

All 7 comments

Thanks for opening this issue!

So true, and now with GDPR - even more important..

I can work on this, would be good for me to understand packer in more details. If no one is working on it.

Hey there, I'll probably give a shot at this issue on Monday; if that's okay.

Any ETA on this being released? TIA

It's in master, so for the next release. Master is very soon going to be tested for a release.

I'm going to lock this issue because it has been closed for _30 days_ โณ. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sourav82 picture sourav82  ยท  3Comments

tleyden picture tleyden  ยท  3Comments

DanielBo picture DanielBo  ยท  3Comments

craigsimon picture craigsimon  ยท  3Comments

mwhooker picture mwhooker  ยท  3Comments