Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have bought some reserved EC2 instances in different availability zones in eu-west-1 region. When launching a new instance, via API or AWS control panel, we do usually set "No preference" as the availability zone.

In case of we have an "unused" reserved instance in an availability zone, does AWS still prefer that very zone even "No preference" is selected when launching the instance? Or, should we explicitly define the availability zone to match the inactive instance reservation?

I tried to look for the answer from the AWS documentation, but without luck yet:

share|improve this question
up vote 2 down vote accepted

Yes, if you have reserved instances purchased in us-east-1b, for example, then you explicitly want to specify us-east-1b at launch. RI's are purely a backend billing thing that function like an invoice credit. The EC2 instances themselves have no awareness of whether they're an RI or not.

The way RI's are handled is actually one of my top five complaints about AWS. I'm hoping that they improve on this soon.

share|improve this answer
Thank you for your answer! Just wondering, do you have any references that would confirm this behavior? – Ville Mattila Mar 14 '13 at 23:35

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.