Deploy Moltbot on AWS-- A Decision Worth Making
The original Moltbot was designed for developers to run locally—install it on your Mac Mini or PC, configure API keys, and let it run 24/7. But in practice, we discovered that deploying Moltbot to the cloud isn't just "convenient"—it delivers fundamental improvements in security, flexibility, cost, and capability.
Deploy Moltbot on AWS- A Decision Worth Making
What is Moltbot and Why Deploy to the Cloud?
If you haven't heard of Moltbot (formerly Clawdbot), here's the quick version: it's the hottest open-source AI assistant project of early 2026, hitting 30K GitHub stars in just weeks. It's not your typical chatbot—it's a 24/7 online assistant that proactively messages you, remembers all conversations, and executes tasks. Connect it to WhatsApp, Telegram, or Slack, and it handles emails, manages schedules, and even controls smart home devices.
The original Moltbot was designed for developers to run locally—install it on your Mac Mini or PC, configure API keys, and let it run 24/7. But in practice, we discovered that deploying Moltbot to the cloud isn't just "convenient"—it delivers fundamental improvements in security, flexibility, cost, and capability.
This post explains the four key advantages of cloud deployment, then provides a detailed guide for one-click deployment using CloudFormation. You'll have your own cloud-based AI assistant up and running in under 10 minutes.
Four Key Advantages of Cloud Deployment
Advantage 1: Security and Reliability at a Different Level
Local deployment requires storing Anthropic API keys in configuration files. These keys are like your bank card PIN—if leaked, attackers can rack up bills or access your data. And local computers typically have weaker security—home networks, personal firewalls, other software running alongside.
Cloud deployment uses IAM role authentication—no keys needed. The EC2 instance authenticates automatically through its identity, like badge access to an office building. Even if someone gains instance access, they can't steal any reusable credentials. According to AWS security best practices, IAM roles are far more secure than long-term credentials (API keys) because they're temporary and auto-rotated.
CloudTrail audit logs are another critical advantage. Every Bedrock API call is logged: who made it, when, which model, what was processed. AWS documentation emphasizes that CloudTrail provides an "immutable and verifiable history of all API interactions." This is essential for regulated industries (finance, healthcare, government). Local deployment? No such audit capability.
VPC Endpoints keep traffic on private networks. Moltbot-to-Bedrock communication never touches the public internet, reducing man-in-the-middle attack risks. Combined with SSM Session Manager, administrators can securely access instances without opening any public ports.
For availability, cloud instances run in enterprise data centers with redundant power and networking. Per AWS SLA, single-instance availability is 99.5%, multi-AZ deployment reaches 99.99%. Local Mac Mini? Power outages, network failures, crashes can all take your AI assistant offline.
Advantage 2: Multi-Model Ecosystem with Graviton Cost Efficiency
Available Models via Bedrock Unified API:
| Model | Input Cost | Output Cost | vs Claude | Best For |
|---|---|---|---|---|
| Nova 2 Lite (default) | $0.30/1M | $2.50/1M | 90% cheaper | Everyday tasks, FAQs |
| Nova Pro | $0.80/1M | $3.20/1M | 73% cheaper | Balanced performance, multimodal |
| Claude Sonnet 4.5 | $3/1M | $15/1M | Baseline | Complex reasoning, coding |
| DeepSeek R1 | $0.55/1M | $2.19/1M | 82% cheaper | Open-source reasoning |
Switch models by changing one parameter—no code changes or redeployment needed.
Real example: An e-commerce customer uses hybrid routing—80% simple FAQs with Nova 2 Lite ($0.30/M tokens), 20% complex complaints with Claude Sonnet 4.5 ($3/M tokens). Result: 60% AI cost reduction while maintaining quality.
Graviton ARM Processor Advantage:
| Instance Type | Architecture | Monthly Cost | vs x86 Savings |
|---|---|---|---|
| t4g.medium | Graviton ARM | $24 | 20% cheaper than t3.medium ($30) |
| c7g.xlarge | Graviton3 ARM | $108 | 11% cheaper than c5.xlarge ($122) |
Graviton processors deliver 20-40% better price-performance with 70% lower power consumption.
Global Cross-Region Inference (CRIS) enhances multi-model strategy:
- ✅ Auto-failover when region lacks capacity (zero downtime)
- ✅ Distributed requests across regions (higher throughput)
- ✅ New models available immediately (continuous innovation)
Advantage 3: Elastic Compute and Storage
Local Moltbot is limited by hardware. Mac Mini with 8GB RAM handles 3-5 concurrent conversations. Want Moltbot to remember more context? Serve 10 people simultaneously? Process large files? Hardware insufficient—either it crashes or you buy new equipment ($599-999).
Cloud deployment offers elastic choices:
- t4g.small (Graviton, 2GB RAM, $12/mo): Personal use, email and calendar
- t4g.medium (Graviton, 4GB RAM, $24/mo): Small teams, multi-channel concurrency
- c7g.xlarge (Graviton3, 8GB RAM, $108/mo): Large teams, AI-intensive tasks
The key is dynamic switching. Use t4g.small normally to save money, upgrade to c7g.xlarge when needed, downgrade after. Hourly billing means you pay only for what you use.
Real example: A startup uses t4g.small ($12/mo) normally, upgrades to c7g.xlarge ($108/mo) during promotional campaigns to handle customer inquiry spikes. 3-day promotion, $10 extra cost, but 10x processing capacity prevented customer loss.
Storage is flexible too. Conversation history in S3 ($0.023/GB/mo), frequently accessed data in EBS. Local disk fills up? Delete old data. Cloud? Unlimited expansion.
Advantage 4: Cloud Elasticity Enables Large-Scale Task Orchestration
Local Moltbot only works on your computer, limited by single-machine performance. But cloud Moltbot can orchestrate cloud resources.
Scenario: Batch Video Processing
User command: "Add subtitles and transcode 100 videos."
Local Moltbot: Process one by one, Mac Mini runs all day, might overheat and crash.
Cloud Moltbot:
- Auto-launch 100 Spot instances ($0.01/hour each)
- Parallel processing, complete in 20 minutes
- Upload results to S3, generate download links
- Release all instances
Cost $3.3, time 20 minutes. Local needs 8+ hours.
Scenario: Data Analysis Workflow
A consulting firm's Moltbot receives data and:
- Launches AWS Glue job to clean data
- Invokes SageMaker endpoint for predictions
- Uses Bedrock to generate analysis report
- Stores results in S3, triggers Lambda to send email
This "on-demand cloud resource orchestration" capability upgrades Moltbot from assistant to automation platform. Resources spin up when needed, release when done—cost precisely matches value.
Cost Reality: Cloud is Actually Cheaper
| Deployment Type | Hardware | Monthly Costs | First Year Total |
|---|---|---|---|
| Local (Mac Mini M2) | $599 one-time | Electricity: $8-21Anthropic API: $20-50 | $695-911 |
| Cloud (AWS) | $0 | EC2 (t4g.medium): $24Storage: $10Bedrock (Nova 2 Lite): $5-10 | $468-528 |
Cloud advantages:
- ✅ No hardware investment or depreciation
- ✅ Graviton 20% cheaper than x86
- ✅ Nova 2 Lite 90% cheaper than Claude
- ✅ Scale up/down anytime
- ✅ Enterprise security and audit
Team economics: One cloud instance ($39/mo) serves 10 people = $3.9/person. Individual ChatGPT Plus subscriptions? $20/person ($200/mo total).
One-Click Deployment: CloudFormation in Detail
What is CloudFormation?
CloudFormation is AWS's Infrastructure as Code (IaC) service. Instead of manually clicking through the console to create VPCs, security groups, EC2 instances, and IAM roles, you define everything in a template file. CloudFormation then automatically creates all resources in the correct order, with proper dependencies.
Why this matters:
- Reproducible: Deploy identical environments every time
- Version controlled: Track changes in Git
- Automated: No manual steps, no human error
- Documented: The template itself is documentation
What Gets Created
When you click "Launch Stack," CloudFormation automatically provisions:
| Resource Category | Components | Time | Purpose |
|---|---|---|---|
| VPC & Networking | VPC, subnets, Internet Gateway, route tables, security groups | ~2 min | Network isolation and connectivity |
| VPC Endpoints (optional) | Bedrock Runtime, SSM, EC2 Messages endpoints | ~2 min | Private API access, no public internet |
| IAM Roles | Instance role with Bedrock + SSM permissions | ~1 min | Secure authentication, no API keys |
| EC2 Instance | Ubuntu 24.04 (ARM64/AMD64), chosen instance type, 30GB EBS | ~3 min | Compute platform for Moltbot |
| Auto-Configuration | Node.js, Docker, Moltbot installation, Bedrock setup | ~2 min | Ready-to-use environment |
Total deployment time: ~8 minutes
What happens automatically:
- ✅ Installs Node.js 22 via NVM
- ✅ Installs Docker for sandbox execution
- ✅ Installs Moltbot globally via npm
- ✅ Generates secure gateway token (48-character random hex)
- ✅ Configures Bedrock integration with Nova 2 Lite
- ✅ Sets up systemd service for auto-restart
- ✅ Saves access URL to CloudFormation Outputs
Step-by-Step Deployment
Step 1: Choose Your Region
Visit the GitHub repository: aws-samples/sample-Moltbot-on-AWS-with-Bedrock
Click the "Launch Stack" button for your preferred region:
| Region | Why Choose This Region |
|---|---|
| US West (Oregon) | Low latency for West Coast, stable Bedrock availability |
| US East (N. Virginia) | Largest AWS region, most services available |
| EU (Ireland) | GDPR compliance, serves European users |
| Asia Pacific (Tokyo) | Low latency for Asian users, Japanese data residency |
Step 2: Configure Parameters
| Parameter | Default | Options | Recommendation |
|---|---|---|---|
| Stack name | moltbot-bedrock | Any valid name | Keep default or use your naming convention |
| ClawdbotModel | global.amazon.nova-2-lite-v1:0 | 8 models available | Keep default for lowest cost, switch to Claude for max capability |
| InstanceType | t4g.medium | t4g/c7g (Graviton), t3/c5 (x86) | Keep default for best value, upgrade to c7g.xlarge for high performance |
| KeyPairName | (required) | Your EC2 key pairs | Select existing or create new in EC2 console |
| CreateVPCEndpoints | true | true/false | Keep true for production (secure), set false to save $22/mo |
| AllowedSSHCIDR | 0.0.0.0/0 | Any CIDR | Change to your IP or 127.0.0.1/32 to disable SSH |
Quick decision guide:
- Personal use: Keep all defaults, costs ~$39/month
- Team use: Upgrade to t4g.large or c7g.xlarge
- Cost-sensitive: Disable VPC endpoints, use t4g.small
- Maximum security: Enable VPC endpoints, disable SSH (
127.0.0.1/32)
Step 3: Acknowledge IAM Resources
Check the box: "I acknowledge that AWS CloudFormation might create IAM resources"
This is required because the template creates an IAM role for the EC2 instance.
Step 4: Create Stack
Click "Create stack" and wait ~8 minutes. You can watch progress in the "Events" tab.
What's happening behind the scenes:
- Minute 0-2: Creating VPC, subnets, security groups
- Minute 2-4: Creating VPC endpoints (if enabled)
- Minute 4-5: Creating IAM roles
- Minute 5-8: Launching EC2, installing software, configuring Moltbot
- Minute 8: Signaling completion, outputting access URL
Step 5: Get Access Information
When status shows "CREATE_COMPLETE," go to the "Outputs" tab:
| Output Key | Description | Action Required |
|---|---|---|
| Step1InstallSSMPlugin | SSM Session Manager Plugin installation guide | One-time setup (5 minutes) |
| Step2PortForwarding | Command to run on local computer | Copy and run in terminal, keep open |
| Step3AccessURL | Complete URL with embedded token | Copy and open in browser |
| InstanceId | EC2 instance ID | Save for future SSM commands |
| BedrockModel | Current model in use | Reference for configuration |
| MonthlyCost | Estimated monthly cost | Budget planning |
Using Your Moltbot
First Access
- Install SSM Plugin (one-time)
- Start Port Forwarding:
- Copy command from CloudFormation Output 2
- Run in terminal, keep it open
- You should see: "Port 18789 opened for sessionId..."
- Open Web UI:
- Copy URL from CloudFormation Output 3
- Paste into browser
- You should see Moltbot Control UI
Connect Messaging Platforms
For detailed configuration guides, visit Moltbot Official Documentation.
WhatsApp (Recommended):
- In Web UI: Channels → Add Channel → WhatsApp
- Scan QR code with your phone (WhatsApp → Settings → Linked Devices)
- Send test message
Telegram:
- Create bot via @BotFather :
/newbot - Get bot token (format:
123456:ABC-DEF...) - In Web UI: Configure Telegram channel with token
- Send
/startto your bot
Discord:
- Create bot at Discord Developer Portal
- Get bot token and enable Message Content intent
- Generate invite
- In Web UI: Configure Discord channel
- Invite bot to your server
Slack:
- Create app at Slack API
- Configure bot token scopes (chat:write, channels:history)
- Install app to workspace
- In Web UI: Configure Slack channel
- Invite bot to channels
Microsoft Teams:
- Install plugin:
npm install -g moltbot-msteams - Create Azure Bot with App ID and secret
- Configure in Web UI with credentials
- Expose
/api/messagesendpoint (port 3978)
Lark / Feishu (飞书) - Community Plugin
- Install plugin
- Runs on EC2, forwards messages via WebSocket
- No public IP or domain required
Customizing Your Deployment
Change Model (Cost Optimization)
Want to switch from Nova 2 Lite to a more capable model?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
# 1. Connect to instance
aws ssm start-session --target <INSTANCE_ID> --region <REGION>
sudo su - ubuntu
# 2. Edit configuration
nano ~/.clawdbot/clawdbot.json
# 3. Change model ID under models.providers.amazon-bedrock.models[0].id
# Options:
# - global.amazon.nova-2-lite-v1:0 (default, cheapest)
# - us.amazon.nova-pro-v1:0 (balanced, 73% cheaper than Claude)
# - global.anthropic.claude-sonnet-4-5-20250929-v1:0 (most capable)
# 4. Also update agents.defaults.model.primary
# Example: "amazon-bedrock/us.amazon.nova-pro-v1:0"
# 5. Restart service
XDG_RUNTIME_DIR=/run/user/1000 systemctl --user restart clawdbot-gateway
Upgrade Instance (Performance Boost)
Need more power for your team?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
# Update CloudFormation stack
aws cloudformation update-stack \
--stack-name moltbot-bedrock \
--use-previous-template \
--parameters \
ParameterKey=InstanceType,ParameterValue=c7g.xlarge \
ParameterKey=KeyPairName,UsePreviousValue=true \
ParameterKey=ClawdbotModel,UsePreviousValue=true \
--capabilities CAPABILITY_IAM \
--region us-west-2
# Wait for update (~5 minutes)
aws cloudformation wait stack-update-complete \
--stack-name moltbot-bedrock \
--region us-west-2
Instance options:
| Instance Type | Specs | Monthly Cost | Best For |
|---|---|---|---|
| t4g.small | 2 vCPU, 2GB RAM | $12 | Personal use |
| t4g.medium | 2 vCPU, 4GB RAM | $24 | Small teams (default) |
| t4g.large | 2 vCPU, 8GB RAM | $48 | Medium teams |
| c7g.xlarge | 4 vCPU, 8GB RAM | $108 | Large teams, high performance |
All Graviton instances offer 20-40% better price-performance than equivalent x86 instances.
The Real Value of One-Click Deployment
Many think one-click deployment is just about "convenience." But the real value is reproducibility and standardization.
Manual deployment can fail differently each time. Forgot an environment variable? Security group rule wrong? Moltbot won't start, and you spend time debugging. Plus, everyone's environment is slightly different, making troubleshooting harder.
CloudFormation templates are Infrastructure as Code. Every deployment is identical, configurations are validated. You can fork the template, add custom logic (connect internal databases, integrate enterprise SSO), then deploy across multiple accounts and regions. All instances have consistent configuration, making management easy.
One enterprise customer forked our template, added internal compliance checks and monitoring alerts, then deployed across 8 global regions. Every region's Moltbot has identical configuration, making troubleshooting efficient.
Real-World Scenarios
Scenario 1: Startup AI Customer Service
A cross-border e-commerce company uses Moltbot connected to WhatsApp Business for customer inquiries. Their smart strategy:
- 80% simple questions ("order status", "return policy") use Nova 2 Lite at $0.30/M tokens
- 20% complex complaints use Claude Sonnet 4.5 at $3/M tokens
Average cost per conversation: $0.001. Processing 100K inquiries/month costs just $100 in AI fees. If using only Claude: $300. If local deployment: couldn't handle 100K concurrent requests.
During promotions, inquiry volume surges 10x. They temporarily upgrade from t4g.medium to c7g.xlarge, handle the traffic spike, then downgrade. Extra cost: $50 for the promotion period, but prevented customer churn.
Scenario 2: DevOps Automation for Development Teams
A tech team connects Moltbot to Slack to monitor CloudWatch alarms. When an alert fires, Moltbot automatically analyzes logs and determines if it's a known issue. If yes, executes fix scripts (restart service, clear cache). If no, creates Jira ticket and mentions relevant engineers.
Result: 80% of alerts auto-resolved, on-call engineers' midnight pages reduced by half.
This automation is hard to achieve with local deployment because your Mac Mini can't directly access CloudWatch, Jira, or production environments. Cloud Moltbot, through IAM roles, can securely invoke any AWS service.
Scenario 3: Large-Scale Task Orchestration
A content team needs to batch-process videos: add subtitles, edit, transcode 100 videos.
Local Moltbot: Process sequentially, Mac Mini runs all day, might overheat.
Cloud Moltbot:
- Receives task, auto-launches 100 Spot instances ($0.01/hour)
- Parallel processing, completes in 20 minutes
- Uploads results to S3, generates pre-signed URLs
- Sends links via Telegram
- Releases all instances
Cost $3.3, time 20 minutes. Local: 8+ hours minimum.
This "on-demand cloud resource orchestration" transforms Moltbot from personal assistant to enterprise automation platform. Cloud elasticity means: resources spin up when needed, release when done, cost precisely matches value.
Summary: Why Cloud Deployment is the Better Choice
| Criteria | Local Deployment | Cloud Deployment | Winner |
|---|---|---|---|
| Setup | Manual install, 1-2 hours | One-click, 8 minutes | ☁️ Cloud |
| Cost | $695-911/year | $468-528/year | ☁️ Cloud |
| Security | API keys in files, no audit | IAM roles, CloudTrail logs | ☁️ Cloud |
| Models | Single provider, manual switch | 8 models, one-parameter switch | ☁️ Cloud |
| Availability | ~95% (home internet) | 99.99% (multi-AZ) | ☁️ Cloud |
| Scalability | Fixed hardware | Elastic (t4g.small to c7g.xlarge) | ☁️ Cloud |
| Task Orchestration | Single machine | Orchestrate AWS services | ☁️ Cloud |
Local deployment suits:
- Hobbyists who enjoy tinkering
- Extreme data privacy requirements
- Light personal use only
Cloud deployment suits:
- 24/7 stable operation needed
- Team collaboration or enterprise use
- Elastic scaling and cost optimization
- Enterprise security and compliance
- Large-scale task orchestration
If you're in the latter category, cloud deployment is essential—not optional.
The AI assistant era has arrived. The real innovation isn't the technology itself, but how quickly you can turn technology into value. Moltbot provides the capability, AWS provides the infrastructure, and you—the builder—have the opportunity to combine them.
Don't wait. Visit the aws-samples repository, click "Launch Stack," and your AI assistant will be online in 8 minutes. Try having it handle emails, generate reports, monitor systems. You'll discover this isn't the future—it's now.
In this era where AI is reshaping everything, the fastest movers win. Cloud Moltbot is ready. Are you?
Built by builder + Kiro
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article