Overview The 'Individual Instance Update' feature in Engine Yard is a good solution for you if you have multiple app servers and periodically, due to instance timeout errors, the Chef run completes o...
Instances on Engine Yard Cloud comprise of the compute resources that are dedicated to running your Ruby application in the cloud. Instances can be configured to serve your application tier, database ...
Engine Yard Cloud supports the Amazon Web Services (AWS) instance types listed below. Choose the instance type you need based upon your application requirements. For your convenience, the available in...
This document is new but should be mostly complete at this time. If you do encounter something not covered please reach out to support so we are aware and can assist you further. Engine Yard gets noti...
Background With the introduction of Elastic EBS volumes, it is now possible to expand the size of EBS volumes, change the volume type between General Purpose SSD (gp2) and Provisioned IOPS SSD (io1), ...
Access to customer instances operates on multiple layers, starting with the booting of an instance. When a new instance is booted, a key unique to that instance is generated with the KeyMaster service...
Engine Yard supports a wide variety of instance sizes and categories. This document discusses the instance types available to use with Engine Yard and provides some guidance on choosing the appropriat...
Memcached is a high-performance, in-memory key-value store that can be used to speed up your Rails applications by caching the results of database calls, API calls or page rendering. Using memcached i...
Overview Customers may wish to create an environment in Engine Yard that consists solely of a database instance. However, this is not possible as every environment in Engine Yard requires the presence...