Stable pack. Claude Code is production-quality. Anthropic releases updates frequently, and the pack is configured to pick them up automatically.
What makes Claude Code different
- Native Bedrock — no proxy. Claude Code talks to Bedrock directly using the
CLAUDE_CODE_USE_BEDROCK=1environment variable. There is no bedrockify proxy layer between the CLI and the model. - Auto-updates. The pack uses Anthropic’s official installer. When Anthropic releases a new version of Claude Code, your instance can update itself.
- Full tool permissions. The pack writes
~/.claude/settings.jsonwithBash(*),Read(*),Write(*), andEdit(*)pre-approved — no permission prompts during agent runs. - No data volume needed. Claude Code is stateless on disk. The data volume is set to 0 GB, which lowers your storage cost.
Compatible profiles
Prerequisites
- AWS CLI configured with admin access in a dedicated sandbox account
- Amazon Bedrock model access enabled in your target region (default:
us-east-1) - No API keys, Docker, or interactive login needed
Install
- Builder
- Account assistant
- Personal assistant
~/.claude/bedrock-env.sh) that sets CLAUDE_CODE_USE_BEDROCK=1, AWS_REGION, ANTHROPIC_MODEL, and ANTHROPIC_DEFAULT_HAIKU_MODEL. These variables are sourced automatically in every new shell session.
Connect and use
After the stack deploys, SSM into the instance and runclaude directly — no login step required:
Configuration options
To use a custom Bedrock model ID (for example, a provisioned-throughput ARN), run the installer in advanced mode:
Resource requirements
Notes and limitations
- Claude Code is a pure CLI pack — there is no background gateway service. The agent runs only when you actively SSM into the instance and invoke
claude. - Auto-updates mean the version running on your instance may differ from the version documented here. Pin with caution — Anthropic’s updates often include important bug fixes.
- There is no persistent memory between sessions by default. Each
claudeinvocation starts with the context you provide in that session. - Tearing down the CloudFormation or Terraform stack leaves no lingering state to clean up.