Automates the deployment of CDK-based serverless infrastructure components to AWS.
Install
mkdir -p .claude/skills/deploy-serithemage && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9533" && unzip -o skill.zip -d .claude/skills/deploy-serithemage && rm skill.zipInstalls to .claude/skills/deploy-serithemage
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Deploys Serverless OpenClaw CDK stacks to AWS. Handles SecretsStack parameter injection, full/individual stack deployment, and Docker image push.Key capabilities
- →Deploy CDK stacks
- →Inject secrets
- →Push Docker images
- →Update Lambda code
How it works
It handles the deployment of CDK stacks, including secret injection and container image management.
Inputs & outputs
When to use deploy
- →Deploying secrets management
- →Updating specific service stacks
- →Pushing container images
- →Full infrastructure deployment
About this skill
Serverless OpenClaw Deployment
Deploy target: $ARGUMENTS
Prerequisites
- Load environment variables:
export $(cat .env | xargs) - Ensure
packages/web/dist/exists:cd packages/web && npx vite build - Ensure TypeScript build passes:
npm run build
Deployment Targets
secrets — 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
BridgeAuthTokenandTelegramWebhookSecretcan be randomly generatedOpenclawGatewayToken,AnthropicApiKey,TelegramBotTokenmust come from.env- On subsequent deploys, CloudFormation reuses previous values (
UsePreviousValue)
all — Deploy All Stacks
cd 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 Stack
cd 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 LambdaAgentStack
cd 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.
Post-Deployment
- Register Telegram webhook:
./scripts/setup-telegram-webhook.sh - Verify: send a message via Telegram or Web UI
- Check ECS tasks:
make task-status
Troubleshooting
- SecretsStack ROLLBACK_FAILED: Force delete with
aws cloudformation delete-stack --stack-name SecretsStack --deletion-mode FORCE_DELETE_STACK, then redeploy - Empty parameter values: Verify
.envhas non-empty values forANTHROPIC_API_KEY,TELEGRAM_BOT_TOKEN,OPENCLAW_GATEWAY_TOKEN - CDK synth fails on web dist: Run
cd packages/web && npx vite buildfirst
References
When not to use it
- →When the user wants to bypass infrastructure deployment
Prerequisites
Limitations
- →AWS CDK specific
- →Requires AWS credentials
How it compares
It provides a specific deployment workflow for Serverless OpenClaw, including secret management and stack ordering.
Compared to similar skills
deploy side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| deploy (this skill) | 0 | 4mo | Review | Advanced |
| sst | 0 | 4mo | No flags | Intermediate |
| cloudflare | 0 | 2mo | No flags | Beginner |
| deployment-pipeline-design | 6 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by serithemage
View all by serithemage →You might also like
sst
ComeOnOliver
SST (Serverless Stack) is a framework for building and deploying full-stack applications on AWS with high-level constructs for Lambda, API Gateway, DynamoDB, S3, and frontend frameworks. It features live local development connected to real AWS services, type-safe resource linking
cloudflare
bilal-chajia
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biase
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
terraform-module-library
wshobson
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
vercel-deployment
davila7
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.
azure-static-web-apps
github
Helps create, configure, and deploy Azure Static Web Apps using the SWA CLI. Use when deploying static sites to Azure, setting up SWA local development, configuring staticwebapp.config.json, adding Azure Functions APIs to SWA, or setting up GitHub Actions CI/CD for Static Web Apps.