Did you know? T2 instances on Engine Yard

This is the second in a series of short blog posts, intended to let you in on a little bit of knowledge about the Engine Yard platform that you might not have known. Engine Yard has a number of features and functions that many of our clients don’t know about, many of which can provide vast benefit.

Read More

Did you know? HIPAA on Engine Yard

This is the first in a series of blog posts, intended to shed some light on features of the Engine Yard Platform. Engine Yard has a number of features and functions that many of our clients don’t know about, many of which can provide vast benefits.

Read More
Learn about Engine Yard
Try Engine Yard for your Ruby or PHP Apps

Cloudwatch Metrics on Engine Yard

Since the introduction of T2 instance types from AWS, our customers have wanted a solution to see their compute credits. Monitoring this continuously changing metric, outside of our own platform, presented a lot of challenges to us. Luckily, AWS handles the brunt of this load for us through their CloudWatch service.

Read More

Disaster Recovery on Engine Yard Cloud, the Cold Standby Edition

We get a lot of requests for disaster recovery, but what exactly is D/R? D/R can mean different things depending on your business needs. Most people think of D/R as a hot standby, but it can also be a cold standby if that meets your business requirements. The process starts with asking yourself a few questions about business needs. How much downtime can we tolerate? How much data can we stand to lose? How much money are we willing to spend? If the answers to the first two questions are minutes and none, then you’ll need a hot standby which we’ll cover in a follow up blog post. If the answers are several hours and some data, then a cold standby may be the most cost effective option for your business. The following is an introduction to setting up a cold standby on Engine Yard Cloud. For the purpose of this post, we are just going to focus on a simple application with a relational database.

Read More

Connect with your Customers in Seoul

Here at Engine Yard, we recognize the importance of data accessibility and the importance of Region availability. The ability to provision instances through the Engine Yard platform around the globe allows clients to target specific users in geographic regions. In today’s fast-paced digital landscape, latency becomes a huge issue, especially with target markets in non-US territories. With this in mind, we’re happy to announce the Seoul, South Korea AWS region is generally available to all our customers starting today.

This region opens up huge opportunities to companies and applications that have direct target market in the Southeast Asia and Korean peninsula. Now you can be as close as possible to your end users, lowering latency and avoiding data transfer woes that might come with datacenters much further away. The Seoul region has two availability zones, allowing applications to be redundant across the AWS region, as well as allowing for auto-heal between availability zones. The region will function similarly to how Engine Yard offers other regions, with built in database backups and snapshots taken and held for you automatically. The Seoul datacenter will also have access to a majority of the newest instance sizes available from AWS as well as VPC enabling for all clients. Pairing this with Engine Yard’s twenty-four by seven support, you can accurately reach your end users like you’re in their backyard, even if you’re on the other side of the world.

You can read more about the AWS Korea region here: http://www.businesswire.com/news/home/20160106006789/en/Amazon-Web-Services-Launches-Korean-Datacenters-Cloud

To access the new region, simply create a new environment in any standard accounts with VPC-enabled by default.. If you’re interested in creating a new account with Engine Yard, please send an email to customersuccess@engineyard.com.


Look through our specially curated posts to get focused, in-depth information on a single topic.