agentleFS
acquiaacquia/acquia-skills/skills/acli/remote-access/SKILL.md

remote-access

Skill10 starsChanged 38 days agoMITView on GitHub

Use when SSHing into a Cloud environment, running Drush commands remotely, or tailing live application logs.

  • Reads credentials

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run any Drush command on a Cloud environment without SSHing in manually:

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Remote Access with Acquia CLI

Platform: This skill applies to ACE (Acquia Cloud Enterprise) subscriptions only. For MEO (Multi-site Enterprise Operations), see MEO Overview.

Trials: trial sites are stricter than ACE environments — SSH is Drush-only. Interactive ssh, rsync, scp and sftp are all rejected; a denial there is expected, not an error to retry. Use the SSH key for git clone against the trial's git remote instead. See Trial Management.

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 cex

Tail Logs Live

Stream live logs from an environment:

acli app:log:tail

Aliases: 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:list

Aliases: acli aliases, acli sa


Download Drush Aliases

Download Drush aliases for use with local Drush:

acli remote:aliases:download

Options:

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.