Deployed clawdbot in under 5 minutes on AWS free tier

Deployed @clawdbot in under 5 minutes on AWS free tier.

Open source personal AI. Full system access.
Interfaces through WhatsApp, Discord, Telegram.

People are rigging it to their Ray-Bans for real-time price comparisons.

One command. That's it. pic.twitter.com/2u07nLvY14
— Tech Friend AJ (@techfrenAJ) January 24, 2026

AWS (Amazon Web Services) provides a stable and highly available environment for running Clawdbot 24/7. Using the AWS Free Tier, you can deploy Clawdbot on an EC2 instance (t3.micro or similar) at no cost for the first year. This guide covers the rapid deployment process using a single command.

Quick Deployment Steps

Step 1: Launch an AWS EC2 Instance

Login to your AWS Management Console.
Navigate to **EC2 Dashboard** and click **Launch Instance**.
Choose **Ubuntu Server 24.04 LTS** as the Amazon Machine Image (AMI).
Select **t3.micro** (Free Tier Eligible).
Configure Security Group to allow inbound traffic on SSH (22) and the Clawdbot Gateway port (default 18789).
Launch with your SSH key pair.

Step 2: Connect via SSH

Open your terminal and connect to your instance:
```
ssh -i "your-key.pem" ubuntu@your-aws-public-ip
```

Step 3: One-Command Installation

Run the official deployment script which handles Node.js, dependencies, and Clawdbot CLI setup:
```
curl -sSL https://install.clawd.bot | bash
```
The script will automatically detect the AWS environment and optimize settings for cloud performance.

Step 4: Onboard and Configure

Complete the setup wizard:
```
clawdbot onboard --cloud
```
Enter your API keys (Claude/OpenAI) and link your messaging channels (WhatsApp, Telegram, etc.).
The `--cloud` flag ensures background services (systemd) are properly established for 24/7 operation.

Step 5: Verify Deployment

Check the status of the gateway: clawdbot gateway status
Access your remote dashboard via http://your-aws-public-ip:18789 (Ensure your security group allows this port).

Pro Tip: For production environments, it is highly recommended to use a reverse proxy like Nginx with SSL or a Cloudflare Tunnel to secure your remote access. The AWS deployment is the fastest way to get Clawdbot running for multi-user or high-availability scenarios.

Troubleshooting Cloud Connectivity

Problem	Detail	Solution
Unable to access Dashboard	Timeout when connecting to IP:18789.	Check AWS Security Groups. Ensure Inbound Rules allow your IP or 0.0.0.0/0 on port 18789 (TCP).
Memory Exhaustion (OOM)	Gateway crashes on t3.micro.	Enable Swap memory (2GB+) in Linux. See the Linux Guide for swap setup commands.
QR Code not rendering	Termianl size or font issues when scanning for WhatsApp.	Use the Web UI dashboard for QR code scanning, or use `clawdbot channels login --debug`.
Service stops after terminal close	Gateway not running in background.	Ensure you ran `clawdbot onboard --install-daemon` to set up the systemd service.