Source AMI Has Password Already Baked

[t3e...@gmail.com]

Currently building AMIs from within EC2 using EC2Launch. 

This seems to be causing me an issue when trying to use this AMI as my Source AMI because the password is unobtainable from Packer or AWS because Ec2SetPassword"="Disabled is in play. Has anyone else come up agains this and is so how do I get around this issue? Because the password is unobtainable I am stuck at the dreaded "Waiting for WinRM to become available..."

Any help or suggestions welcome

[Rickard von Essen]

Can't you just use a user-script to re-enable password creation / fetching? 

--
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 packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/2effc8dd-34a0-472a-8f3c-e822cf317827%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[t3e...@gmail.com]

Thanks Rickard, 

I actually have a powershelgl function on the AMI that will do this and called that function via the user-script however that had no effect and didn't seem to run. 

I have since realised that my custom (test) AMI was miss configured and I had incorrectly not set the password to random in EC2-Config (not EC2Lunch as I statued in my OP). SO now I have my AMI correctly confirmed it's now working a treat. 

Thanks again.