Ravion runs infrastructure in your own AWS account, and your coding agent drives it. Setup is two commands: teach the agent, then ask.
1
2
What the agent needs from you
The agent handles the terminal work. Three things need you, because only you can do them:
- Approve the sign-in.
ravion loginprints a URL and a short code for you to confirm in the browser. No account yet? Sign up first — Ravion is free for individuals, and teams start with a free trial. - Confirm the AWS account. The agent runs
aws sts get-caller-identityand asks whether that is the account Ravion should manage. It then connects it by deploying Ravion’s CloudFormation stack, which creates a cross-account IAM role. Without AWS CLI credentials, connect it in AWS accounts instead. - Connect your Git repository.
ravion git connectprints a URL that needs your Git permissions. Skip it if Ravion only deploys images from a registry.
The agent also asks for the decisions it should not guess, such as region, instance sizes, and domains, and it pauses for your approval before any change that modifies, replaces, or removes existing infrastructure.
Working without the skill
Agents that fetch URLs but do not support skills read the hosted copy:
To search the docs from the agent’s context window, add the Ravion Docs MCP server — the skill installs it on its own, so this is only for doing it up front:
Set up the CLI yourself
Nothing here is required when an agent does the setup for you.Install the CLI with Homebrew on macOS:
Or with the install script:
Sign in, then select your active organization if you belong to more than one:
See Install the Ravion CLI and Authentication.
Connect AWS from the AWS CLI yourself
Confirm which account your credentials belong to:
Create the Ravion AWS account record and get the CloudFormation template for it:
Deploy the template in us-east-1, where the template’s authenticator runs. The role it creates lets Ravion provision in any region:
The template carries your account id and a single-use token, so pass no --parameters and keep the URL private. CAPABILITY_NAMED_IAM is required because the stack creates a named role and named managed policies.Confirm the connection:
The status field reads CONNECTED once the stack finishes. When Ravion later ships new permissions, review them with ravion aws account policy-diff <aws-account-id>, then apply them with aws cloudformation update-stack and a freshly fetched template URL.