Acquia Cloud defines Drush aliases for all of your application's environments. For example, the application named (Acquia Cloud username) example has the following Drush aliases for its Development, Staging, and Production environments:
Your environments might not all be on the same server, depending on your account and configuration. Using Drush's remote command capability, you can use any of the aliases to access any of your applications from your local computer or any Acquia Cloud server. The remote aliases work seamlessly if you have your SSH private key available on the source server. To use your SSH private key from Acquia Cloud without having to copy the private key to the Acquia Cloud server, use SSH key forwarding by using the
-A argument to SSH when connecting from your local computer.
For the following examples, the Staging environment is on server
staging-1 and your Production environment is on
Downloading Drush aliases
Use the following method to download your Drush aliases:
- Sign in to the Acquia Cloud interface using your email address and Acquia password.
- Click your user avatar in the upper right corner, and then click Edit profile.
- On the Profile page, click Credentials.
- Under Drush integration, click Download Drush aliases
Extract the downloaded archive file into
tar -C $HOME -xf $HOME/Downloads/example.tar.gz
Use the aliases on your local command line as though you were signed in to your Acquia Cloud server to view the Drush status. For example:
drush @example.test status
Example: Viewing site status with Drush
To view the status of your application on the Production environment from your local computer using Drush, enter the following command:
drush @example.prod status
Viewing site status using Drush and SSH forwarding
By signing in to an Acquia Cloud server with SSH forwarding, you can access all of your environments without copying your private key to Acquia Cloud. To view the Drush status for your Production website while being signed in to the server for your Staging environment, enter the following commands, replacing server names as appropriate:
ssh -A [email protected]
drush @example.prod status
Refreshing Drush aliases
From time to time, your Drush aliases may change. This can happen when your server infrastructure (and therefore the hostname of your Acquia Cloud) changes. That might happen if your server instance is resized or relaunched, for example, or if you upgrade your subscription from Acquia Cloud Free to Acquia Cloud Professional, or from Acquia Cloud Professional to Acquia Cloud Enterprise.
You can refresh your Drush aliases by downloading them again, and pasting the new version over the old one. As an alternative, you can use this Drush command: