Open ahawkins opened 11 years ago
What type of problem are you having? Note that if you supply -z
you will also need to override the AMI since the AMI being used is region specific.
I'm having issues even when I don't specify the zone:
$ bees up -s 1 -k key
# ...
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>InvalidParameterValue</Code><Message>Invalid availability zone: [us-east-1d]</Message></Error></Errors><RequestID>80b47c16-039d-48bf-8aa5-ddd3b6305bc6</RequestID></Response>
That looks odd, because us-east-1d
should definitely be a valid availability zone in us-east-1
. If you have the EC2
command line tools or the the new awscli
installed, can you list the availability zones available to you in us-east-1
?
According to the EC2 command line tools, I've only got us-east-1a
, us-east-1b
and us-east-1c
. Using one of those works.
But I really want to use something in us-west-1
, and that doesn't work for me, even though us-west-1b
and us-west-1c
are both available. Same error. beeswithmachineguns
seems to be using the option correctly, though. Doesn't seem like a bug on your end.
If you want to use another region, you will have to change the ec2 url endpoint (ex: for europe http://ec2.eu-west-1.amazonaws.com)
Thanks for this project. We are having problems operating in
eu-west-1
. It seems the-z
flag does not work with all EC2 queries. The only way for us to get bees to work was to create a new key pair, and security group in the default zone.