It looks like Amazon has released a third EBS volume type, and renamed "Standard" volumes to "Magnetic". General Purpose is currently the default type when launching "Create Volume" in the EC2 Web UI (https://console.aws.amazon.com/ec2/v2/home), which provides the following documentation:<p>"General Purpose (SSD) volumes provide the ability to burst to 3,000 IOPS per volume, independent of volume size, to meet the performance needs of most applications and also deliver a consistent baseline of 3 IOPS/GiB. Provisioned IOPS (SSD) volumes can deliver up to 4000 IOPS and are best for EBS-optimized instances. Magnetic volumes, previously called 'standard volumes', deliver approximately 100 IOPS on average, with a best effort ability to burst to hundreds of IOPS."<p>The EBS Pricing page (http://aws.amazon.com/ebs/pricing/) currently makes no mention of General Purpose (SSD) volumes.
Is it supposed to be all smooth sailing launching gp2 instances from standard snapshots and vice versa ?<p>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.<p>The timing is too strange for it to be a coincidence, but nothing on the AWS status page.
Official announcement just been released.<p><a href="http://aws.amazon.com/blogs/aws/new-ssd-backed-elastic-block-storage/" rel="nofollow">http://aws.amazon.com/blogs/aws/new-ssd-backed-elastic-block...</a>
Interesting. I can create a gp2 volume through the console, but not through CloudFormation.<p><pre><code> UPDATE_FAILED - gp2 is invalid. Valid volume types are standard and io1.</code></pre>
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.
<a href="http://www.cloudcorset.com/?ref=Tie98" rel="nofollow">http://www.cloudcorset.com/?ref=Tie98</a>