You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Description
AWS recommends creating AMIs via a snapshot of a root EBS volume as a faster way of creating images. (This would be using the RegisterImage API rather than the CreateImage API.) Despite this potentially offering large speed improvements, this feature seems to be missing from the Amazon Packer plugin.
The amazon-ebssurrogate builder exists, but as far as I can tell, that's designed to create an AMI based on a snapshot of a volume that is not the root volume of the Packer builder instance.
Use Case(s)
Creating AMIs more quickly
Potential configuration
This could be implemented using a use_create_image option on the amazon-ebs builder, similar to the option that already exists on the amazon-ebssurrogate builder. The main difference is that use_create_image would need to default to true on the amazon-ebs builder to preserve existing behavior.
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.
Description
AWS recommends creating AMIs via a snapshot of a root EBS volume as a faster way of creating images. (This would be using the RegisterImage API rather than the CreateImage API.) Despite this potentially offering large speed improvements, this feature seems to be missing from the Amazon Packer plugin.
The
amazon-ebssurrogate
builder exists, but as far as I can tell, that's designed to create an AMI based on a snapshot of a volume that is not the root volume of the Packer builder instance.Use Case(s)
Potential configuration
This could be implemented using a
use_create_image
option on theamazon-ebs
builder, similar to the option that already exists on theamazon-ebssurrogate
builder. The main difference is thatuse_create_image
would need to default totrue
on theamazon-ebs
builder to preserve existing behavior.The text was updated successfully, but these errors were encountered: