WinRM Access to EC2 Forbidden

timo.lechner...@gmail.com

unread,

Mar 18, 2019, 5:03:16 AM3/18/19

to Packer

Hi guys,

I have the following problem already described on github:

https://github.com/hashicorp/packer/issues/7420#issue-422085957

Any suggestions or missing information ?

John Roh

unread,

Apr 10, 2019, 4:27:08 AM4/10/19

to Packer

I'm having the exact same problem described in your post.

Also, tried with winrm_no_proxy and my packer version v1.3.5.

* unknown configuration key: "winrm_no_proxy"

2019/04/10 08:23:10 Build 'aws-web-int' prepare failure: 1 error(s) occurred:

* unknown configuration key: "winrm_no_proxy"

2019/04/10 08:23:10 ui error: 1 error(s) occurred:

Please let me know anyone knows how to fix or if there is any work around.

John Roh

unread,

Apr 10, 2019, 4:40:29 AM4/10/19

to Packer

tried ssh_interface: private_ip or export no_proxy=localhost,169.254.169.254, us-west-1.compute.internal (described @ https://github.com/hashicorp/packer/issues/4857).

So far no luck...I even defined vpc_id, subnet_id, and security_group_id that 5986 is opened in our existing networks since there is additional firewall I need to go through.

On Monday, March 18, 2019 at 2:03:16 AM UTC-7, timo.lechne...@gmail.com wrote:

Sean Nolan

unread,

Sep 26, 2019, 7:50:56 PM9/26/19

to Packer

Did you ever find a reliable fix for this issue?

Thanks

Sean

Sean Nolan

unread,

Sep 26, 2019, 10:00:21 PM9/26/19

to Packer

In case it helps anyone else, for us the issue was addressed by this from the Packer docs:

"Where Packer is configured for an outbound proxy but WinRM traffic should be direct, ssh_interface must be set to private_dns and <region>.compute.internal included in the NO_PROXY environment variable."

So I had to put

"ssh_interface": "private_dns",

in the template, and I had to add .ec2.internal to the NO_PROXY environment variable.

Sean

Reply all

Reply to author

Forward