Official announcement just been released.
http://aws.amazon.com/blogs/aws/new-ssd-backed-elastic-block...
Interesting. I can create a gp2 volume through the console, but not through CloudFormation.
UPDATE_FAILED - gp2 is invalid. Valid volume types are standard and io1.It'll be interesting to see how much CloudCorset will be able to impact/improve performance by reducing the number of IOPS that goes to the EBS storage backend. http://www.cloudcorset.com/?ref=Tie98
Is it supposed to be all smooth sailing launching gp2 instances from standard snapshots and vice versa ?
It may be just me but I've had really weird and serious new errors today in us-east-1 launching new instances, or even starting previously stopped ones with no changes to the instance whatsoever ! General slowness, "reachability" health check failing, with the system log showing that the kernel couldn't be uncompressed, maybe because the bootloader couldn't find the root device in the first place ? I'm not using custom kernels at all.
The timing is too strange for it to be a coincidence, but nothing on the AWS status page.