Unlike other PaaS providers, we give you full control over your instances. When you request an environment, we:
You can see the status of your application, add and remove capacity and deploy new application versions.
You control everything from where your application is deployed to configuring the software stack.
With Engine Yard Cloud, horizontal and vertical scaling is easy. Add additional instances easily to your application tier and that instance will automatically deploy with the correct application configuration and join your load-balanced group.
You can create database slaves with smaller or larger instance sizes. For guidance on database replication in basic and custom clusters, visit our documentation.
With a single click, you can clone your full production environment even if your application is running across many different instances with multiple volumes and databases.
This includes storage, CPU and memory utilization levels, and we proactively alert you when you need additional capacity, or when your application may be behaving poorly. Through our Premium and Managed support plans, you have the ability to define your custom call escalation path, where you can determine the best path for members of your team to get notified.
We automatically mount these volumes and create backups. Both the /data mount on the application master instance and the /db mount on the database master instance(s) are persistent.
This is delivered at two levels:
In the case of AWS, all Engine Yard supporting infrastructure is located in multiple AWS availability zones (datatext-centers within an AWS region).
Within the dashboard, you can select from a variety of regions to establish your computing clusters. Our provisioning system then distributes the instances across the availability zones so that applications can continue to run even during infrastructure outages.
“Takeover” is the Engine Yard failover process for recovering an application master instance from failure. It occurs automatically when our system detects an application master is unable to reliably respond to requests. For example, this can happen because of an infrastructure issue or because the instance froze. If the instance does not recover within a short time, our platform does the following:
We are committed to protecting the confidentiality and integrity of your data. Our information security team consistently evaluates risk, defines policy, designs and operates technical controls and monitors program effectiveness through a combination of tools, internal audits and quarterly third-party security assessments.
Our hosted applications, operating systems, databases, and networking infrastructure are designed and configured to mitigate known external security threats. With our investment in SOC 2 audits, you can be assured of the rigor and discipline in our systems, policies and change management processes. You can also run HIPAA compliant applications on our platform. If you're interested in reading more about our commitment to security, click here.