It looks like the Multi-AZ setup is using block level replication such as DRBD instead of the built-in replication:
> Database updates are made concurrently on the primary and standby resources to prevent replication lag.
Makes me feels better for setting up my own pg cluster on EC2 a week ago, which does allow reads from the replication slave. Plus, I can provision <1000 IOPS (provisioned IOPS is damn expensive with AWS), and get to use ZFS.
The time spent researching and building that cluster was time not spent building product. If you are low on capital then it was potentially a good tradeoff, but I'd much rather just scale up my read capacity by adding horsepower until they get around to adding read replicas. My goal is to spend as little time as possible administering my infrastructure, and running my own database cluster is the last thing on my mind.
Administering databases is a full-time type of responsibility. Yes, you can get pretty sane defaults, and up and running without much difficulty with MS-SQL, and mySQL has been a defacto standard in the LAMP stack. That said PostreSQL has been a rock solid RDBMS. The commercial extensions for replication have been cumbersome and expensive. Here's hoping that AWS will grow/expand the replications options/features, and that they'll grow to include JS procs as that feature stabilizes.