This document describes how to use the EBS (Elastic Block Store) optimized instances with Engine Yard Cloud.
EBS optimized instances provide persistent, high-performance, high-availability block-level storage which you can attach to a running instance. EBS optimized instances provide a dedicated and faster network path between your app and data storage for reliable volume performance.
You can use EBS optimized instances with provisioned IOPS volumes to increase performance levels as well as reliability. EBS optimized instances are also supported using standard EBS volumes.
EBS optimized instances support is available on these 64-bit instance types:
- Standard Large (m1.large)
- Standard Extra Large (m1.xlarge)
- High Memory Quadruple Extra Large (m2.4xlarge)
- High Memory Double Extra Large (m2.2xlarge)
- High CPU Extra Large (c1.xlarge)
Note: Some instance sizes may not be available by default. Please contact Engine Yard Support if you do not see the necessary instance sizes.
Get started with EBS optimized instances on Engine Yard Cloud
- Configure EBS optimized instances
- Verify EBS optimized instances
- More information
- This article assumes you already have an Engine Yard account. If not, see Sign up for an Engine Yard Account.
- Add a new instance to use this feature. You cannot modify an existing instance / volume.
- Use 64-bit instances (32-bit instances are not supported).
Configure EBS optimized instances
Important: We recommend testing in a staging environment before applying changes in a production environment.
You can configure EBS optimized instances when you add new instances to a new or existing environment.
To add a new EBS optimized instance
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 EBS optimized instance size, which appears with the added "[VO]" in the instance size description.
If you are also using provisioned IOPS volumes, specify the values you need for the volume and IOPS.
- The ratio of IOPS to GB should be 10:1. For example, 1000 IOPS needs a volume size of at least 100 GB.
- When you create a new environment, you cannot set the provisioned IOPS value for a database replica, its value automatically matches the database master.
Click Add to Cluster.
See the related documentation for more information on adding instances to your environment.
Note: You also need to click Apply to update the database.yml file.
Verify EBS optimized instances
Note: When you are testing in staging, consider the differences between your test and production loads.
To verify EBS optimized instances
Ensure that instance provisioning worked and the instance is running.
In general, that is enough of an indication that provisioned EBS optimized instances are working fine.
- You can use I/O benchmarking utilities to verify that the performance levels are what you need.
- Review the Troubleshooting tips below for more information.
This table contains troubleshooting tips related to EBS optimized instances.
|The new instance appears to be stuck in Chef provisioning.||This can happen when the EBS instance has been provisioned yet the PIOPS volume provisioning did not succeed. Try terminating and reprovisioning the instance. See the known issue for more information.|
This table provides other resources related to EBS optimized instances.
|For more information about...||See...|
|Using provisioned IOPS||Use Provisioned IOPS with Engine Yard Cloud|
|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|
If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.