Information for: DEVELOPERS   PARTNERS

Additional environments for Acquia Cloud Enterprise

You may want more environments than the development, staging, and production environments that you get initially. For example, you might want additional environments to support:

  • Testing integration with other systems
  • Providing separate environments for different developers or development teams, where your developers want to work on the server instead of locally
  • Performing load testing on a copy of your production hardware

Note for Acquia Cloud Enterprise users

Additional environments, including Acquia Cloud CD environments, can be created for Acquia Cloud Enterprise applications. If you are an Acquia Cloud Enterprise customer and you want to set up additional environments for an application, contact Acquia Support. Ensure that you note the following:

  • If your application uses shared staging servers, you will need to pay an additional fee for each environment added.
  • If your application uses dedicated staging servers, you will not be charged for additional environments, but your servers may need to be upsized to accommodate the increased load or reduced resources per environment caused by the additional environments.

Aliases for additional environments

By default, Acquia Cloud applications have three environments with the aliases dev, test, and prod. If you have an Acquia Cloud Enterprise application with more than three environments and you need to determine what your environment names and aliases are, you can do one of the following:

  • Look at the $HOME/.drush folder on your server. Files in that folder list the aliases for the environments.

  • Use the Drush Cloud ac-environment-list command. For example:

    drush @site.env ac-environment-list
    
  • Use the GET /sites/:site/envs Cloud API command. For example:

    curl -s -u user:pass https://cloudapi.acquia.com/v1/sites/mysite/envs.json