Remote Access with Acquia CLI

• 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

acli remote:ssh <alias>

acli ssh

app-name.env

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

acli remote:drush <drush_command>

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 cex

Tail Logs Live

acli app:log:tail

acli tail

acli log:tail

List Drush Aliases

acli remote:aliases:list

acli aliases

acli sa

Download Drush Aliases

acli remote:aliases:download

acli remote:aliases:download \
  --destination-dir=/path/to/aliases \
  --all                               # download aliases for all applications

Best Practices

1. Use

   remote:drush

   over SSH for Drush commands — It handles authentication and environment selection automatically.
2. Use aliases — Download aliases with

   remote:aliases:download

   so local Drush can target Cloud environments directly.
3. Tail logs during deploys — Run

   acli app:log:tail

   while 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