Menu
Deploys Serverless OpenClaw CDK stacks to AWS. Handles SecretsStack parameter injection, full/individual stack deployment, and Docker image push.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | deploy |
| description | Deploys Serverless OpenClaw CDK stacks to AWS. Handles SecretsStack parameter injection, full/individual stack deployment, and Docker image push. |
| argument-hint | [target: secrets|all|<StackName>|image] |
| allowed-tools | Read, Bash, Glob, Grep |
Deploy target: $ARGUMENTS
export $(cat .env | xargs)packages/web/dist/ exists: cd packages/web && npx vite buildnpm run buildsecrets — Deploy SecretsStack (first-time setup)SecretsStack uses AwsCustomResource to create SSM SecureString parameters. On first deploy, all 5 values must be provided.
cd packages/cdk
export $(cat .env | xargs)
npx cdk deploy SecretsStack \
--parameters "BridgeAuthToken=$(openssl rand -hex 32)" \
--parameters "OpenclawGatewayToken=$OPENCLAW_GATEWAY_TOKEN" \
--parameters "AnthropicApiKey=$ANTHROPIC_API_KEY" \
--parameters "TelegramBotToken=$TELEGRAM_BOT_TOKEN" \
--parameters "TelegramWebhookSecret=$(openssl rand -hex 32)" \
--profile $AWS_PROFILE --region $AWS_REGION --require-approval never
BridgeAuthToken and TelegramWebhookSecret can be randomly generatedOpenclawGatewayToken, AnthropicApiKey, TelegramBotToken must come from .envUsePreviousValue)all — Deploy All Stackscd packages/cdk
npx cdk deploy --all --profile $AWS_PROFILE --region $AWS_REGION --require-approval broadening
Stack order (automatic): SecretsStack + NetworkStack -> StorageStack -> {AuthStack, ComputeStack} -> ApiStack -> WebStack + MonitoringStack
<StackName> — Deploy Individual Stackcd packages/cdk
npx cdk deploy <StackName> --profile $AWS_PROFILE --region $AWS_REGION --require-approval never
Use --exclusively flag to skip dependency resolution when needed.
image — Push Docker Image to ECR./scripts/deploy-image.sh # standard push
./scripts/deploy-image.sh --soci # with SOCI lazy loading (Linux only)
lambda-image — Build + Push Lambda Container Image./scripts/deploy-lambda-image.sh # build + push Lambda container image to ECR
lambda-stack — Deploy LambdaAgentStackcd packages/cdk
npx cdk deploy LambdaAgentStack --profile $AWS_PROFILE --region $AWS_REGION --require-approval never
lambda-update — Update Lambda Function Code (after image rebuild)aws lambda update-function-code \
--function-name serverless-openclaw-agent \
--image-uri $ECR_REPO:latest \
--profile $AWS_PROFILE --region $AWS_REGION
See Deployment Guide §9 for full Lambda deployment walkthrough.
./scripts/setup-telegram-webhook.shmake task-statusaws cloudformation delete-stack --stack-name SecretsStack --deletion-mode FORCE_DELETE_STACK, then redeploy.env has non-empty values for ANTHROPIC_API_KEY, TELEGRAM_BOT_TOKEN, OPENCLAW_GATEWAY_TOKENcd packages/web && npx vite build firstReferences Serverless OpenClaw architecture. Covers network design, CDK stack structure, DynamoDB data model, API protocols, and container design.
References cold start optimization history and techniques. Covers Docker image optimization, Fargate CPU tuning, SOCI lazy loading, and Lambda Bedrock discovery fix. Use when optimizing startup performance.
Loads Serverless OpenClaw project context. Provides background knowledge needed for development including project overview, tech stack, architecture decisions, and data models.
References Serverless OpenClaw cost optimization guidelines. Validates that no resources exceeding the cost target ($1/month) are created during implementation. Use when writing CDK stacks or making infrastructure changes.
Development workflow guide. Covers build, test, lint, format commands, package structure, Git hooks, TDD methodology, and coding conventions. Use when setting up dev environment, running tests, or following project conventions.
Guides Phase 1 MVP implementation steps. Pass a specific step number as an argument to get the goals, deliverables, validation criteria, and detailed design for that step.