This is documentation for AWS M3 instances. This new generation of EC2 instances provides high frequency processors and offer SSD-based instance storage for fast instance store I/O performance.
General Purpose (M3)
- Extra Large*
- 2x Extra Large* Hidden behind feature flag
* Extra large and double extra large instances are also available as EBS optimized instances.
Get started with M3 instances on Engine Yard
This document describes how to use M3 instances with Engine Yard.
- This article assumes you already have an Engine Yard account. If not, see Sign up for an Engine Yard Account.
- You must add a new instance to use this feature. You cannot modify an existing instance / volume.
- You must use 64-bit instances (32-bit instances are not supported).
- If you are using the Engine Yard Gentoo 2009 stack, you must click Update for the April 3, 2014 stable-v2 stack upgrade to gain M3 instances support.
- If you are using the Engine Yard Gentoo 12.11 stack, you must click Update for the April 3, 2014 stable-v4 stack upgrade to gain M3 instances support.
Configure M3 instances
You can configure M3 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 M3 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 M3 instance size in the list.
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 M3 database instance, you also need to click Apply to update the database.yml file.
Verify M3 instances
Note: When you are testing in staging, consider the differences between your test and production loads.
To verify M3 instances
Ensure that instance provisioning worked and the instance is running.
In general, that is enough of an indication that the M3 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 M3 instances to avoid unnecessary charges.
- Stop any unneeded M3 instances to avoid unnecessary charges.
You might have these questions about M3 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 M3 instances.
|The M3 dedicated 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 use the dedicated instances feature in your region. This is because it is part of the AWS default VPC feature set. Check the AWS "default VPC" region release dates or contact Engine Yard Support if you need help. See the dedicated instances doc and this note for more information.|
|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 M3 instances.
|For more information about...||See...|
|Adding an instance to an environment||Add Instances to an Environment|
|Adding a database instance to an environment||Add a database replica (slave) to an existing environment|
|EBS optimized instances||EBS optimized instances|
|Dedicated instances||Dedicated instances|
If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.