UseDocumentation Index
Fetch the complete documentation index at: https://docs.remotemux.com/llms.txt
Use this file to discover all available pages before exploring further.
backend=aws when you want the RemoteMux control plane to provision into your own AWS account.
What This Backend Does
- Authenticates to the RemoteMux control plane with
rmux login - Validates your AWS identity and network/storage settings
- Creates one EC2 devbox per environment
- Uses AWS SSM Session Manager for attach (no inbound port 22 needed)
Prerequisites
- AWS credentials (AWS CLI, environment variables, or access keys)
- AWS Session Manager plugin (bundled in RemoteMux releases)
- A default VPC in the target region, or explicit subnet and security group settings
Configure
The shortest path:Validate
Create and Use
Authentication Modes
| Mode | How it works |
|---|---|
aws-cli | Uses configured AWS CLI profile. Works with editors and standalone SSH. |
env | Uses AWS_* environment variables. RemoteMux injects credentials for editor commands. |
access-key | Uses explicit access key ID and secret. RemoteMux injects credentials for editor commands. |
Editor Access
Open workspaces in VS Code or Cursor over SSH:~/.ssh/rmux/config and tunnels through SSM. See Editor Access for details.
Port Exposure
AWS BYOC exposed ports currently return direct public-IP URLs such ashttp://PUBLIC_IP:3000.
Private previews and preview share links are currently available only on Managed and E2B environments. BYOC AWS ports stay public until RemoteMux ships a non-public ingress path for that runtime.