# Send OpenClaw AWS Deploy to your agent
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
## Fast path
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
## Suggested prompts
### New install

```text
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
```
### Upgrade existing

```text
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
```
## Machine-readable fields
```json
{
  "schemaVersion": "1.0",
  "item": {
    "slug": "openclaw-aws-deploy",
    "name": "OpenClaw AWS Deploy",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/godwinbabu/openclaw-aws-deploy",
    "canonicalUrl": "https://clawhub.ai/godwinbabu/openclaw-aws-deploy",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadUrl": "/downloads/openclaw-aws-deploy",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=openclaw-aws-deploy",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "packageFormat": "ZIP package",
    "primaryDoc": "SKILL.md",
    "includedAssets": [
      "CHANGELOG.md",
      "README.md",
      "ROADMAP.md",
      "SKILL.md",
      "assets/agent-defaults/AGENTS.md",
      "assets/agent-defaults/HEARTBEAT.md"
    ],
    "downloadMode": "redirect",
    "sourceHealth": {
      "source": "tencent",
      "slug": "openclaw-aws-deploy",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-05-06T11:03:30.572Z",
      "expiresAt": "2026-05-13T11:03:30.572Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=openclaw-aws-deploy",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=openclaw-aws-deploy",
        "contentDisposition": "attachment; filename=\"openclaw-aws-deploy-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null,
        "slug": "openclaw-aws-deploy"
      },
      "scope": "item",
      "summary": "Item download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this item.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/openclaw-aws-deploy"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    }
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/openclaw-aws-deploy",
    "downloadUrl": "https://openagent3.xyz/downloads/openclaw-aws-deploy",
    "agentUrl": "https://openagent3.xyz/skills/openclaw-aws-deploy/agent",
    "manifestUrl": "https://openagent3.xyz/skills/openclaw-aws-deploy/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/openclaw-aws-deploy/agent.md"
  }
}
```
## Documentation

### Prerequisites

AWS credentials — any of these methods:

--profile <name> flag (named AWS CLI profile)
.env.aws file in workspace root or skill directory (optional):
AWS_ACCESS_KEY_ID=...
AWS_SECRET_ACCESS_KEY=...
AWS_DEFAULT_REGION=us-east-1


Existing environment variables, AWS SSO session, or IAM role


.env.starfish in workspace root (recommended) or skill directory:
TELEGRAM_BOT_TOKEN=...     # from @BotFather (required)
TELEGRAM_USER_ID=...       # your Telegram user ID (optional, enables auto-approve pairing)
GEMINI_API_KEY=...         # from aistudio.google.com (optional, for Gemini models)


aws CLI installed OR Docker for sandboxed access
jq, openssl available

### One-Shot Deploy

# From the skill directory:
./scripts/deploy_minimal.sh --name starfish --region us-east-1 \\
  --env-dir /path/to/workspace

# Or with cleanup of previous deployment first:
./scripts/deploy_minimal.sh --name starfish --region us-east-1 \\
  --env-dir /path/to/workspace --cleanup-first

This single command:

Creates VPC + subnet + IGW + route table
Creates security group (NO inbound ports — SSM only)
Creates IAM role with minimal permissions (SSM + Parameter Store + Bedrock)
Stores secrets in SSM Parameter Store (fetched at each service start — rewritten on each start, never stored in repo or static images)
Launches t4g.medium ARM64 instance with user-data bootstrap
User-data installs Node.js 22 + OpenClaw + configures everything
Runs smoke test via SSM
Saves all resource IDs to deploy-output.json

### After Deploy

Message the Telegram bot — you'll get a pairing code
Approve pairing via SSM:
aws ssm start-session --target <INSTANCE_ID> --region us-east-1
sudo -u openclaw bash
export HOME=/home/openclaw
openclaw pairing approve telegram <CODE>


Bot is live! ✅

### Teardown

# Using saved output:
./scripts/teardown.sh --from-output ./deploy-output.json --env-dir /path/to/workspace --yes

# Or by name (discovers via tags):
./scripts/teardown.sh --name starfish --region us-east-1 --env-dir /path/to/workspace --yes

### --model flag

Pass any model string — it goes directly into openclaw.json as model.primary:

# Default (MiniMax M2.1 on Bedrock — no API key needed, uses IAM role)
./scripts/deploy_minimal.sh --name starfish --region us-east-1

# Gemini Flash (needs GEMINI_API_KEY in .env.starfish)
./scripts/deploy_minimal.sh --name starfish --region us-east-1 \\
  --model google/gemini-2.0-flash

### AWS Bedrock

Bedrock IAM permissions (bedrock:InvokeModel, bedrock:InvokeModelWithResponseStream) are always added to the instance role — regardless of which model you choose. This means any deployed instance can use Bedrock models out of the box via IAM role credentials (no API key needed).

Known Bedrock model IDs:

Model flagDescriptionamazon-bedrock/minimax.minimax-m2.1MiniMax M2.1amazon-bedrock/minimax.minimax-m2MiniMax M2amazon-bedrock/deepseek.deepseek-r1DeepSeek R1amazon-bedrock/moonshotai.kimi-k2.5Kimi K2.5

Note: Bedrock models must be enabled in your AWS account via the Bedrock console before use.

### Gemini

If GEMINI_API_KEY is present in .env.starfish, it's stored in SSM and written to auth-profiles.json. If absent, it's simply skipped — no error.

### .env.starfish

TELEGRAM_BOT_TOKEN=...     # Required — from @BotFather
GEMINI_API_KEY=...         # Optional — from aistudio.google.com (needed for Gemini models)

### Architecture (Minimal)

┌─────────────────────────────────────────────────────┐
│                      VPC (10.50.0.0/16)             │
│  ┌───────────────────────────────────────────────┐  │
│  │           Public Subnet (10.50.0.0/24)        │  │
│  │  ┌─────────────────────────────────────────┐  │  │
│  │  │      EC2 t4g.medium (ARM64, 4GB)        │  │  │
│  │  │  ┌───────────────────────────────────┐  │  │  │
│  │  │  │       OpenClaw Gateway             │  │  │  │
│  │  │  │  • Node.js 22.14.0                 │  │  │  │
│  │  │  │  • Any model (Bedrock/Gemini/etc)   │  │  │  │
│  │  │  │  • Telegram channel                │  │  │  │
│  │  │  │  • Encrypted EBS (gp3, 20GB)       │  │  │  │
│  │  │  └───────────────────────────────────┘  │  │  │
│  │  └─────────────────────────────────────────┘  │  │
│  └───────────────────────────────────────────────┘  │
└─────────────────────────────────────────────────────┘
         ↑                              ↓
    SSM (no SSH/inbound)      Outbound HTTPS only

### Critical Lessons Learned (22 Issues)

These are baked into the deploy script. See references/TROUBLESHOOTING.md for full details.

### Instance Sizing

t4g.medium (4GB) required — t4g.small (2GB) OOMs during npm install + gateway startup
ARM64 — better price/performance than x86

### Node.js

Node 22+ required — OpenClaw 2026.x requires Node ≥22.12.0
Official tarball install — NodeSource setup_22.x unreliable on AL2023 ARM64
git required — OpenClaw npm install has git-based dependencies

### npm

Use openclaw@latest — bare openclaw may resolve to placeholder package (0.0.1)

### Gateway Startup

Use openclaw gateway run --allow-unconfigured — NOT gateway start (which tries systemctl --user and fails)
Config file must be openclaw.json — not config.yaml
gateway.mode: "local" — required or you get "Missing config" error
gateway.auth.mode: "token" — "none" is invalid

### Telegram

plugins.entries.telegram.enabled: true — must be explicit
dmPolicy: "pairing" — not "allowlist" (blocks everyone without user list)
streamMode: "partial" — some models don't support streaming tools, use "off" as fallback

### Model

Gemini 2.0 Flash — recommended (free tier: 15 RPM, 1M tokens/day, supports tools)
Auth profiles required — create auth-profiles.json in agent dir
Bedrock format — amazon-bedrock/MODEL_ID (not bedrock/)
Bedrock models need console enablement — Anthropic requires use case form

### Systemd Service

Simplified service file — removed ProtectHome, ReadWritePaths=/tmp/openclaw, PrivateTmp due to namespace issues
Use NODE_OPTIONS="--max-old-space-size=1024" — helps prevent OOM

### Security

No inbound ports — SSM Session Manager only
Secrets fetched from SSM at runtime — startup script fetches secrets each time the service starts; config files are ephemeral (rewritten on each start, never stored in repo or static images)
Encrypted EBS — enabled by default in deploy script
IMDSv2 required — HttpTokens=required

### File Layout

scripts/
  deploy_minimal.sh        # One-shot deploy (VPC + EC2 + OpenClaw)
  teardown.sh              # Clean teardown of all resources
  setup_deployer_role.sh   # Create IAM role/user with minimum permissions
  preflight.sh             # Pre-deploy validation checks
  smoke_test.sh            # Post-deploy health verification

references/
  TROUBLESHOOTING.md   # All 22 issues + solutions
  config-templates/    # Ready-to-use config files
    gemini-flash.json  # OpenClaw config for Gemini Flash
    auth-profiles-gemini.json  # Auth profile template
    openclaw.service.txt  # Systemd unit file template
    startup.sh         # Startup script template

### OpenClaw Config (gemini-flash.json)

See references/config-templates/gemini-flash.json — includes all required fields.

### Auth Profiles (auth-profiles-gemini.json)

Create at ~/.openclaw/agents/main/agent/auth-profiles.json

### Systemd Service (openclaw.service)

Simplified for reliability — security hardening removed due to namespace issues.

### Cost Breakdown (~$30/mo)

ResourceCostt4g.medium (4GB ARM64)~$24.53/moEBS gp3 20GB~$1.60/moPublic IP~$3.65/moGemini FlashFree tier / ~$0.30/1M tokensTotal~$29.78/mo

### "No API key found for amazon-bedrock"

Cause: OpenClaw needs models.providers config in openclaw.json with "auth": "aws-sdk". An auth-profiles.json entry alone is NOT sufficient.

Fix: Add to openclaw.json on the instance:

sudo -u openclaw bash
cd /home/openclaw/.openclaw
jq '.models = {
  "providers": {"amazon-bedrock": {"baseUrl": "https://bedrock-runtime.us-east-1.amazonaws.com", "api": "bedrock-converse-stream", "auth": "aws-sdk", "models": [{"id": "minimax.minimax-m2.1", "name": "MiniMax M2.1", "input": ["text"], "contextWindow": 128000, "maxTokens": 4096}]}},
  "bedrockDiscovery": {"enabled": true, "region": "us-east-1"}
}' openclaw.json > /tmp/oc.json && mv /tmp/oc.json openclaw.json
chown openclaw:openclaw openclaw.json
systemctl restart openclaw

### "API rate limit reached" (Gemini)

Fix: Switch to Bedrock (default in current version) or redeploy with --model amazon-bedrock/minimax.minimax-m2.1.

### Bedrock model returns errors

Cause: Model must be enabled in AWS Console → Bedrock → Model access. MiniMax models are auto-authorized; Anthropic/Meta models require use-case approval.

### Bot doesn't respond after deploy

Fix: Add TELEGRAM_USER_ID to .env.starfish for auto-pairing, or use --pair-user <id>. Manual: openclaw pairing approve telegram <CODE> via SSM.

### Safety Rules

Never print secrets in logs
Never open SSH/inbound ports; use SSM Session Manager only
Use least-privilege IAM policies
All resources tagged with Project=<name> and DeployId=<unique-id> for deterministic cleanup
Encrypted EBS volumes always
## Trust
- Source: tencent
- Verification: Indexed source record
- Publisher: godwinbabu
- Version: 1.0.0
## Source health
- Status: healthy
- Item download looks usable.
- Yavira can redirect you to the upstream package for this item.
- Health scope: item
- Reason: direct_download_ok
- Checked at: 2026-05-06T11:03:30.572Z
- Expires at: 2026-05-13T11:03:30.572Z
- Recommended action: Download for OpenClaw
## Links
- [Detail page](https://openagent3.xyz/skills/openclaw-aws-deploy)
- [Send to Agent page](https://openagent3.xyz/skills/openclaw-aws-deploy/agent)
- [JSON manifest](https://openagent3.xyz/skills/openclaw-aws-deploy/agent.json)
- [Markdown brief](https://openagent3.xyz/skills/openclaw-aws-deploy/agent.md)
- [Download page](https://openagent3.xyz/downloads/openclaw-aws-deploy)