The new EBS-backed instances work with reserved instances, but there's a snag. Reserved instances are limited to a specific availability zone.

The Hub transparently routes activity to an availability zone with spare capacity. Initially, there is no guarantee when you launch a server that is going to land in any specific availability zone.

I say initially because after you use the Hub to create an asset (e.g., EBS block) in a given region, the Hub will "pin" your account down to a specific availability zone.

So here's a workaround for now: create an EBS volume asset such as an EBS device via the Hub. Log into the Amazon web console to find out in what availability zone it was created, then purchase a reserved instances in that availability zone. When you launch an EBS-backed instance, Amazon should apply the reserve pricing...

I admit this is kind of clunky. We'll think about how to streamline this...