Your requested instance type (m1.medium) is not supported in your requested Availability Zone

[cer]

Got this error running bosh-bootstrap deploy

Stemcell info
 -------------
Name:    micro-bosh-stemcell
Version: 0.8.1

Deploy Micro BOSH
  unpacking stemcell (00:00:15)                                                 
  uploading stemcell (00:14:29)                                                 
  delete stemcell (00:00:00)                                                    
                             |ooooo              | 3/11 00:14:45  ETA: 00:39:19/usr/local/lib/ruby/gems/1.9.1/gems/aws-sdk-1.6.9/lib/aws/core/client.rb:318:in `return_or_raise': Your requested instance type (m1.medium) is not supported in your requested Availability Zone (us-west-1b). Please retry your request by not specifying an Availability Zone or choosing us-west-1c, us-west-1a. (AWS::EC2::Errors::Unsupported)
    from /usr/local/lib/ruby/gems/1.9.1/gems/aws-sdk-1.6.9/lib/aws/core/client.rb:419:in `client_request'

Running bosh-bootstrap deploy again resulted in 

Performing update deploy to micro BOSH microbosh-aws-us-west-1
No existing instance to update
       error  deploy micro bosh
Failed to complete Stage 5: Deploying micro BOSH

[drnic]

reformatted issue

[drnic]

Can you please also include all the terminal output from the start?

Also, can you please try the tool again in another region so that you can enjoy it working?

Looks like m1.medium might not be available in all AZs https://forums.aws.amazon.com/thread.jspa?threadID=110067

[cer]

This happened three times in a row including with a newly created AWS account. The third time, @drnic edited a config file to explicitly specify us-east1a and microbosh was deployed successfully.

Either:

• The user should be able to specify an AZ
• Better yet, the tools should let EC2 pick the AZ

[drnic]

Thanks for reminding me of this bug Chris

On Fri, Mar 1, 2013 at 10:54 AM, Chris Richardson notifications@github.com wrote:

This happened three times in a row including with a newly created AWS account. The third time, @drnic edited a config file to explicitly specify us-east1a and microbosh was deployed successfully. Either:

• The user should be able to specify an AZ

* Better yet, the tools should let EC2 pick the AZ

Reply to this email directly or view it on GitHub: https://github.com/StarkAndWayne/bosh-cloudfoundry/issues/103#issuecomment-14304949

[mkb]

Which config file? I am getting this same error for us-east-1e and it's not clear how to point to another AZ.

[drnic]

@mkb if I recall (its been a long time) there'll be a settings.yml file that's created and where all your prompt answers are stored; plus other generated information.

[drnic]

BTW, we're working on a new set of tools (using terraform) for bootstrapping BOSH & CF. They will reuse the spiff templates from cf-release; so they won't go out of date as quickly. They will replace this project. Coming in 2015! (bold claim I know)

[drnic]

For anyone interested, the starting point is https://github.com/cloudfoundry-community/terraform-aws-cf-install

Currently this is for AWS only due to terraform not yet supporting OpenStack/vSphere.

[mkb]

Aha. I'm looking to use BOSH directly on AWS with no CF layer. Am I making a tragic mistake that will plague my family for generations?

[drnic]

Go straight to bosh-bootstrap project to get bosh running. Your family will prosper and rejoice your name on your name sake holiday day :)

On Mon, Dec 29, 2014 at 8:30 AM, mkb notifications@github.com wrote:

Aha. I'm looking to use BOSH directly on AWS with no CF layer. Am I making a tragic mistake that will plague my family for generations?

Reply to this email directly or view it on GitHub: https://github.com/cloudfoundry-community/bosh-cloudfoundry/issues/103#issuecomment-68272286