Manage Your Environment


This article describes the user interface (UI) for managing an environment in Engine Yard Cloud.


Refer to a callout number and then find the matching number and description below, explaining that part of the UI.

Manage environment


  1. [Your_Application_Name] - the name of your application. In this example, it is the "todo" sample application.

    Click to view or manage the todo application.

  2. [Your_Environment_Name] - the name of your environment. In this example, we've deployed the "todo" application into the "production" environment.

    Click to view or manage the production environment. [Does nothing: you are already on the page.]

  3. Apply - click to apply configuration changes to this environment.

    Note: the Apply button appears blue when configuration changes are pending.

  4. Upgrade - click to apply stack (cookbook) changes to this environment. Refer to Upgrade an Environment for more information. 

    Note: the Upgrade button appears only when stack (cookbook) changes are pending.

  5. Snapshot - click to initiate a snapshot of your application instances. Refer to Take Snapshots for more information. 

    Note: app users might experience a slowdown during the snapshot process.

  6. Add - click to add application resources (application, database slave, and utility instances) to your environment (cluster).
  7. Stop - click to shut down instances for this environment.

    Note: stopping the environment saves a snapshot, stops your application(s), and shuts down your instances. You can later re-provision the instances using the snapshot.

  8. Environment - information about the environment follows.
  9. [Your_Environment_Name] - the name of your environment. In this example, the "production" environment includes 3 server instances: app, app master, and a master database.

  10. Visit Your Application - click to visit your running application on your instances.

  11. [Your_App_Region] - the Amazon Web Services (AWS) region identifier for your production environment. This is the specific geographic area where the app instances are located. In this example, "Eastern United States" is the region.
  12. [Your_Framework_Environment_Type] - the Rails * framework environment type for this Engine Yard Cloud environment. In this example, "production" is the framework environment type.
  13. Migrate? - select (check) to enter a Rails * migration command in the text box.
  14. Ref - type in the git reference you want to deploy. The default is HEAD (meaning the current directory, with the most recent commit).
  15. Deploy - click to deploy your application in Engine Yard Cloud.
  16. Status message - displays the most recent activity on this application/environment. Click View Log to display the latest deployment log. Click Deployment history to view a historical list of deployment logs.

* For this example, we are using the Rails framework.

Scroll down to see more environment page options.

Manage instances


  1. Instances - information about environment instances follows.
  2. Label - each instance type is described. In this example, the first is an app instance, configured on the Amazon High CPU Medium (32-bit) instance type.
  3. SSH - click to start an SSH connection.
  4. HTTP - click to view your running application.
  5. Base Log - click to view your base Chef log for this instance.
  6. Custom Log - click to view your custom Chef log for this instance.
  7. Performance Graphs - click to view cluster performance graphs for this instance.
  8. Terminate - click to shut down this instance.

Scroll down to see more environment page options.

Manage alerts


  1. Alerts - information about environment alerts follows.
  2. Message - in this example, alerts are disabled for the environment.
  3. Send email - you can send important server alerts to an email address, which you type into the text field.
  4. Send Email Alerts - click to set up email alerts.

Scroll down to see more environment page options.

Manage options


  1. More Options - information about other environment options follows.
  2. Edit Environment - click to review the current configuration and make stack changes. For example you can change the version of Ruby or the RubyGems. In some cases, you cannot make changes unless all instances have been stopped first.
  3. Clone environment: Make a clone of this environment. This option will be disabled if no instance snapshots have been created yet. Refer to Clone an Environment for more information. 
  4. Copy environment: Make a copy of this environment (no data). Refer to Copy an Environment for more information. 
  5. Crontabs: Add or edit scheduled (cron) jobs for the environment. Refer to  Add Cron Jobs for more information. 
  6. Deployment Tuning: Select instances to hide from the deployment process. This will make the deployment process faster. 
  7. Database backups: Download database backups. Refer to View and Download Database Backups for more information. 
  8. HAProxy stats: View load balancer statistics for your application cluster. Refer to View Your HAProxy Stats for more information. 
  9. HTTP monitoring: Set up HTTP monitoring on specific URLs for your application. External service that pings the application every 2 minutes. 
  10. Logs: View log files from previous configuration runs. 
  11. Promotions: View previous database promotions.
  12. Snapshots: View and manage snapshots. Refer to Manage Snapshots for more information. 
  13. Takeovers: View previous application takeovers. Refer to Application Master Takeover for more information. 
  14. Maintenance: Enable or disable maintenance mode in this environment. Cron jobs will not be affected in this mode (they will still run). Refer to Use Application Maintenance Pages for more information. 
  15. Environment Variables: View and manage environment variables. Refer to Environment Variables and How to Use Them for more information.
  16. Target Groups: Create and manage application load balancer target groups for this environment
  17. Auto Scaling: Create and manage auto-scaling for this environment

Add-ons - if you have enabled any add-on services, then they appear in a table below this title. In this example, there are no add-ons enabled.

If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.


Article is closed for comments.