Thank you both for the suggestions. "-on-error" was new to me. Alvaro's suggested script is essentially the same as what I've been working with. I started with Hashicorp's "best-practices" repo. And I have also read the post that you suggested, Rickard.
As I only need to build two windows machines at the moment, I think I'll just cave and do this manually for now. I'll come back and give it another go once I have all my other tasks finished. Cheers On Wednesday, 2 November 2016 20:42:58 UTC, Rickard von Essen wrote: > > Without knowing much about Windows, especially on AWS. But if I would try > the same I would follow the following pattern. > > Manually setup an EC2 with windows and enable WinRM. These things must go > into a user-script. Verify that I can connect with WinRM from the host that > will run Packer. Use a static security group allowing this. > > Code the settings that was manually verified into a Packer template. Run > that with PACKER_LOG=1 and -on-error=ask to allow you to manually try to > connect if Packer fails and see a lot of details of what Packer actually > do. If you get stuck, post a template.json and additional scripts that you > have tried here and ask for help. > > I assume you have found > http://engineering.daptiv.com/provisioning-windows-instances-with-packer-vagrant-and-chef-in-aws/ > > On 2 November 2016 at 18:11, Chris Forbes <[email protected] <javascript:> > > wrote: > >> Hello everyone, >> >> I've only been using Packer for a few weeks now for setting up our >> infrastructure in AWS. We are using it in conjunction with Terraform and >> it's going great... for Linux. I've started looking into creating the >> Windows machines that we unfortunately still need, and I'm having a lot of >> trouble. I've followed along with numerous different blog posts on how to >> actually get WinRM to work properly with no luck. I'm still stuck on the >> WinRM timeout issue. >> >> Is there a definitive guide out there for creating a simple Windows AMI >> on AWS with Packer? Or does anyone have a Git repo that I can simply change >> the source AMI and run without any hitches? >> >> Any help would be appreciated! >> >> Chris >> >> -- >> 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/mitchellh/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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/packer-tool/afa18d28-a0bc-41d3-8c9f-9f1e6279121d%40googlegroups.com >> >> <https://groups.google.com/d/msgid/packer-tool/afa18d28-a0bc-41d3-8c9f-9f1e6279121d%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/mitchellh/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/8fba76a9-55aa-43ed-b427-ead78e1c4fc3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
