This is documentation for AWS R3 instances. R3 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. R3 instances are recommended for applications that require high memory performance at the best price point per GB of RAM.
Note: You cannot change the instance type of an existing EC2-Cloud instance to a R3 instance type.
Memory Optimized (R3)
- Extra Large*
- 2x Extra Large* Hidden behind feature flag
- 4x Extra Large* Hidden behind feature flag
- 8x 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 R3 instances on Engine Yard
This document describes how to use R3 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 be on at least the September 24th, 2014 Engine Yard Gentoo 12.11 stack release to gain R3 instances support.
- You must add a new instance to use this feature. You cannot modify an existing instance / volume.
Configure R3 instances
You can configure R3 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 R3 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 Memory Optimized R3 instance size in the list.
Note: Some instance sizes may not be available by default. Please contact Engine Yard Support if you do not see the necessary instance sizes.
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 R3 database instance, you also need to click Apply to update the database.yml file.
Verify R3 instances
Note: When you are testing in staging, consider the differences between your test and production loads.
To verify R3 instances
Ensure that instance provisioning worked and the instance is running.
In general, that is enough of an indication that the R3 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 R3 instances to avoid unnecessary charges.
- Stop any unneeded R3 instances to avoid unnecessary charges.
You might have these questions about R3 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 R3 instances.
|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 R3 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|
If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.