Remote Access with Acquia CLI
Use when:
- Opening an SSH shell on a Cloud environment
- Running a Drush command on a remote environment
- Downloading or listing Drush aliases
- Tailing live logs from an environment
SSH into a Cloud Environment
Open an interactive shell in a Cloud Platform environment:
acli remote:ssh <alias>Alias: acli ssh
The alias format is app-name.env (e.g. myapp.prod, myapp.dev).
# Open interactive shell
acli remote:ssh myapp.prod
# Run a single command without opening a shell
acli remote:ssh myapp.prod -- ls -la /var/www/html
# Run multiple commands
acli remote:ssh myapp.prod -- "cd /var/www/html && git log --oneline -5"Run Drush Remotely
Run any Drush command on a Cloud environment without SSHing in manually:
acli remote:drush <drush_command>Aliases: acli drush, acli dr
# Check Drupal status
acli remote:drush status
# Clear caches
acli remote:drush cr
# Run database updates
acli remote:drush updatedb
# Export configuration
acli remote:drush cexTail Logs Live
Stream live logs from an environment:
acli app:log:tailAliases: acli tail, acli log:tail
Prompts you to select the application, environment, and log type.
List Drush Aliases
List all Drush site aliases for your Cloud environments:
acli remote:aliases:listAliases: acli aliases, acli sa
Download Drush Aliases
Download Drush aliases for use with local Drush:
acli remote:aliases:downloadOptions:
acli remote:aliases:download \
--destination-dir=/path/to/aliases \
--all # download aliases for all applicationsBest Practices
- Use
remote:drushover SSH for Drush commands — It handles authentication and environment selection automatically. - Use aliases — Download aliases with
remote:aliases:downloadso local Drush can target Cloud environments directly. - Tail logs during deploys — Run
acli app:log:tailwhile deploying to catch errors in real time.
Related Topics
- Pull & Push — Sync code, files, and databases
- SSH Key Management — Secure access setup
- Environment Management — Manage environments