As posted on its blog, AWS is also tripling the number of IOPS:
You can now create DB instances (MySQL or Oracle) with up to 3 TB of storage (the previous limit was 1 TB) and 30,000 IOPS (previously, 10,000). DB instances running SQL Server can scale to 1 TB of storage and 7,000 IOPS. For a workload with 50% reads and 50% writes running on an m2.4xlarge instance, you can realize up to 25,000 IOPS for Oracle and 12,500 IOPS for MySQL. However, by provisioning up to 30,000 IOPS, you may be able to achieve lower latency and higher throughput. Your actual realized IOPS may vary from what you have provisioned based on your database workload, instance type, and choice of database engine. Refer to the Factors That Affect Realized IOPS section of the Amazon RDS User Guide to learn more.
AWS is also adding the capability to convert database instances with “Standard Storage” to “Provisioned IOPS.” The intent is to offer the benefits of fast and predictable performance.
Lastly, AWS is offering the ability to scale “Provisioned IOPS” and storage independently.
RDS is designed to handle all of the “messy low-level aspects of setting up, managing, and scaling MySQL, Oracle Database, and SQL Server databases.”
All three of these features can be used now. They are available in every AWS Region where Provisioned IOPS are supported.
The tripling of storage and IOPs follows a trend with AWS to optimize customer’s infrastructure according to the data it is storing and processing. It’s this concept of “cost aware,” architecture that AWS is espousing that is evident in this latest update.