Fixes #29187 - using winrm on EC2 #29205
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ensures that use_winrm: True is respected when bootstrapping with salt-cloud on EC2. Adds the option to specify winrm port to use with 'winrm_port' option in cloud configuration. This is optional and defaults to WinRM 2.0 HTTP port tcp/5986. Only HTTPS (as before) is supported.
There is also a documentation update with a working example using default EC2 Windows images. The existing examples don't account for opening WinRM on the Windows firewall or ensuring auth type is basic.
Additionally the example uses the following Technet 'trick':
http://social.technet.microsoft.com/wiki/contents/articles/28753.powershell-trick-copy-certificates-from-one-store-to-another.aspx
This allows you to enable HTTPS as previously there was no store available on EC2 Windows images resulting in an error to enable HTTPS. This borrows from RDP.