This is documentation for AWS M2 instances. M2 instances provide sustained memory bandwidth, superior I/O performance, support for EBS optimization, as well as support for lower latency, low jitter, and very high packet per second performance. M2 instances are recommended for applications that require high memory performance at the best price point per GB of RAM.
M2 instances must be launched into an Amazon Virtual Private Cloud (VPC); they are not supported on the EC2-Cloud platform. Amazon VPC enables you to launch AWS resources into a virtual network that you've defined.
Note: You cannot change the instance type of an existing EC2-Cloud instance to a M2 instance type.
Memory Optimized (M2)
The HVM instance types, available in all AWS regions, are:
- Extra Large*
- 2x Extra Large* Hidden behind feature flag
- 4x Extra Large* Hidden behind feature flag
* Extra large, double extra large, and quadruple extra large instances are also available as EBS optimized instances.
Get started with M2 instances on Engine Yard
This document describes how to use M2 instances with Engine Yard.
- Configure M2 instances
- Verify M2 instances
- More information
- This article assumes you already have an Engine Yard account. If not, see Sign up for an Engine Yard Account.
- You must be on at least the September 24th, 2014 Engine Yard Gentoo 12.11 stack release to gain M2 instances support.
- You must add a new instance to use this feature. You cannot modify an existing instance / volume.
Configure M2 instances
You can configure M2 instances when you add new instances to a new or existing environment.
Note: We recommend testing in a staging environment before applying changes in a production environment.
To add a new M2 instance
Ensure that you meet all the prerequisites above.
Add an instance in the usual way.
See the database docs for more information about adding a database instance to an environment.
Select the appropriate General Purpose M2 instance size of your choosing.
Click Add to Cluster (or Boot This Configuration, if you are re-booting an existing environment).
See the related documentation for more information on adding instances to your environment.
Note: If you are adding a M2 database instance, you also need to click Apply to update the database.yml file.
Verify M2 instances
Note: When you are testing in staging, consider the differences between your test and production loads.
To verify M2 instances
Ensure that instance provisioning worked and the instance is running.
In general, that is enough of an indication that the M2 instance is working fine.
- Review the Troubleshooting tips below for more information.
- If this is a staging environment and you are finished with testing, be sure and stop any M2 instances to avoid unnecessary charges.
- Stop any unneeded M2 instances to avoid unnecessary charges.
You might have these questions about M2 instances.
How can I use the SSDs on these instances?
You can leverage the SSDs as needed via custom Chef; be aware that there is no ability to create snapshots of SSDs.
How much does it cost?
See the pricing page for details.
This table contains troubleshooting tips related to M2 instances.
|The M2 instances do not appear in the drop-down list.||If you have had an Engine Yard account for a while, you might need to create a new Engine Yard account in order to have VPC and use M2 instances. Older Engine Yard accounts did not have VPC.|
|When I clicked HTTP on the app server, I received a 500 Internal Server Error.||If this is the first time provisioning, wait a few minutes and try again.|
This table provides other resources related to M2 instances.
|For more information about...||See...|
|Adding an instance to an environment||Add Instances to an Environment|
|Amazon Virtual Private Cloud (VPC)||VPC on Engine Yard|
|Hardware-assisted virtual machine (HVM)||HVM vs. PV|
|Supported AWS instances on Engine Yard||AWS Instance Type Support|
|Upgrading your environment||Upgrade Guide|
|Adding a database instance to an environment||Add a database replica (slave) to an existing environment|
|EBS optimized instances||EBS optimized instances|