[chef] Re: Launching Windows instances with chef-provisioning-aws


Chronological Thread 
  • From: George Miranda < >
  • To: " " < >
  • Subject: [chef] Re: Launching Windows instances with chef-provisioning-aws
  • Date: Fri, 30 Jan 2015 15:56:59 -0800

It looks like you might be getting the default AMI for whatever region you're in.[1]  For... reasons?

Try setting image_id as a machine option rather than a bootstrap option.

with_machine_options({
:bootstrap_options => {
:foo => "bar"
},
:image_id => "ami-73717d36"
})




On Fri, Jan 30, 2015 at 12:31 PM, tayworm . < " target="_blank"> > wrote:
I'm attempting to launch a windows instance into vpc but for some reason it always picks ubuntu-trusty-14.04-amd64-server-20140816 (ami-73717d36) instead of the ami I specified with `:image_id => 'ami-xxxxxxxx'` in the bootstrap options. Any ideas on how to get my ami choice honored?






Archive powered by MHonArc 2.6.16.

§