Due to some security policies, we can’t spin up instances that are not 
encrypted. When I run a packer build, it tries to first make an instance 
named “Packer Builder” that is not encrypted and fails. Is there a way to 
tell packer to encrypt the actual instance it’s running the provisioners on?

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/hashicorp/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/88d7e904-0f0c-492d-82a2-8c2f797f954en%40googlegroups.com.

Reply via email to