Cloud Development

Command Reference

Complete reference for all cloud-dev CLI commands.

Cloud Dev Command Reference

All commands are run from the DevStride repository root:

./ds cloud-dev <command> [options]

Getting Started

CommandDescription
initConfigure local environment (run this first!)
createCreate and fully configure a cloud dev environment

init

Configure your local environment for cloud-dev. Run this once before using other commands.

./ds cloud-dev init

This will:

  • Set DEVSTRIDE_STAGE (your developer name)
  • Set AWS_PROFILE (your AWS SSO profile)
  • Update your shell configuration

create

Deploy a new cloud development environment.

./ds cloud-dev create [options]

Options:

OptionDescription
-n, --name <name>Developer name (defaults to DEVSTRIDE_STAGE)
-i, --instance <id>Instance identifier for multiple instances
--skip-setupDeploy infrastructure only (skip auto-setup)

Example:

./ds cloud-dev create              # Standard create
./ds cloud-dev create -i 2         # Create second instance
./ds cloud-dev create --skip-setup # Infrastructure only

Instance Management

CommandDescription
listList all your dev instances
startStart a stopped instance
stopStop a running instance (preserves data)
infoShow connection information
destroyRemove instance and all AWS resources

destroy

Completely remove a cloud environment. This deletes all data.

./ds cloud-dev destroy [options]

Options:

OptionDescription
-n, --name <name>Developer name
-i, --instance <id>Instance identifier
-f, --forceSkip confirmation prompt

This removes:

  • EC2 instance and EBS volume (all data lost)
  • VPC and networking resources
  • Local SSH keys and config

Connectivity

CommandDescription
sshSSH into your instance
ssmConnect via AWS SSM (no SSH key needed)
claudeRun Claude Code on your instance
setupConfigure SSH keys and GitHub access manually

ssh

Connect to your instance via SSH.

./ds cloud-dev ssh
./ds cloud-dev ssh -i 2  # Connect to instance 2

If SSH keys aren't configured, you'll be prompted to run setup.

ssm

Connect via AWS Systems Manager (useful if SSH is blocked):

./ds cloud-dev ssm

claude

Launch Claude Code directly on your cloud instance:

./ds cloud-dev claude
./ds cloud-dev claude -i 2  # On instance 2

This SSHs into your instance and starts Claude Code in the ~/dev/devstride directory. Claude runs with --dangerously-skip-permissions to enable autonomous operation.


Remote Development

Run commands on your cloud instance from your local terminal:

CommandDescription
start-backendStart backend (./ds run backend)
stop-backendStop backend process
start-frontendStart frontend (./ds run ui)
stop-frontendStop frontend process
run-migrationsRun database migrations
reset-databaseReset database from source

Example:

./ds cloud-dev start-backend  # Runs in your terminal with live output
# Press Ctrl+C to stop

Secrets Management

CommandDescription
init-secretsPush local .env to AWS Secrets Manager (admin)
setup-secretsFetch secrets from AWS to local .env file
list-secretsList stored secret keys (not values)

setup-secrets

Download shared secrets to create your .env file:

./ds cloud-dev setup-secrets
./ds cloud-dev setup-secrets -o .env.local  # Custom output path

init-secrets (Admin)

Upload local .env to AWS Secrets Manager for team sharing:

./ds cloud-dev init-secrets
./ds cloud-dev init-secrets -f  # Force overwrite

Global Options

These options work with most commands:

OptionDescription
-n, --name <name>Developer name (defaults to DEVSTRIDE_STAGE)
-i, --instance <id>Instance identifier (for multiple instances)
-f, --forceSkip confirmation prompts

Interactive Menu

Run without arguments for an interactive menu:

./ds cloud-dev

Or show help:

./ds cloud-dev help