I've been building AMIs using Packer for a while. I'm basing these on Amazon Linux, and have been using the same base AMI version. I'm using Packer 10.1. Recently I have not been able to SSH in to instances built from these Packer base AMIs. I get a Connection Refused error. I'm using a Terraform configuration to manage my infrastructure, so have defined security groups, etc. with that. If I build my infrastructure with the hard-coded Amazon Linux base AMI, I'm able to SSH in. If I do the same with a Packer-built AMI, I can't log in. I've even tried removing the provisioner block from my Packerfile. It's as if Packer is doing something that prevents SSH (disables SSH agent? Messes with the firewall?)
Does this ring a bell for anyone? What could be happening? -- 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/9d70cf00-a2db-48ae-8a13-cb0ee8b26b9e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
