Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default AMIs for Windows not available #174

Closed
emiliogarcia opened this issue Jul 10, 2015 · 3 comments
Closed

Default AMIs for Windows not available #174

emiliogarcia opened this issue Jul 10, 2015 · 3 comments
Labels
Milestone

Comments

@emiliogarcia
Copy link

I can't find the default AMIs for Windows in us-east-1
https://github.com/test-kitchen/kitchen-ec2/blob/master/data/amis.json

I get:
No AMIs found matching your filter criteria
or not authorised to launch the AMI from the kitchen log.

Were those AMIs special? AFAIK WinRM is not enabled by default in the ones provided by Amazon. What does the Windows AMI needs to be able to work with Kitchen-ec2?

@zl4bv
Copy link
Contributor

zl4bv commented Jul 15, 2015

Amazon release new Windows AMIs around once per month. The AMIs are then available for about six weeks after which you can no longer start new instances with those AMIs (the expectation being that you start new instances with this month's AMIs). Based on your error, it is most likely that the AMIs listed in amis.json are out of date now - which makes sense given they were last updated on June 5.

By default kitchen-ec2 provides user-data that enables WinRM for Windows guests.

You'll need to make sure the security group of the test kitchen instance allows WinRM traffic on TCP port 5985. Also, either you need to provide a username and password for test-kitchen to connect to the instance with, or an SSH key and key ID so that kitchen-ec2 can decrypt the EC2 generated Windows password (with the default username Administrator).

@tjnicholas
Copy link

It'd be easier to avoid stale AMI IDs if #177 was merged.

@cheeseplus
Copy link
Contributor

#177 is merged so calling this closed.

@jkeiser jkeiser added this to the 1.0.0 milestone Jul 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants