OpenClaw on AWS Lightsail: Cost Breakdown and Configuration Lessons
OpenClaw on AWS Lightsail Configuration and Costs
A developer attempted to build a personal assistant bot called "Belvedere" using OpenClaw on AWS Lightsail with Claude Sonnet 4.6 via Bedrock. The setup involved two Lightsail instances (medium_3_0, 4GB, $40/mo each) running the openclaw_ls_1_0 blueprint in us-east-1, aiming to manage family calendars, school logistics, travel booking, and morning briefings via Telegram.
What Worked
The system successfully pulled JetBlue fares via headless Chromium, cross-referenced work calendars against family commitments, and flagged scheduling conflicts. It connected to Google Calendar via gogcli, read Gmail via himalaya (read-only), and pulled credentials from 1Password.
What Didn't Work
- Sandbox Issues: The Lightsail blueprint ships with sandbox mode set to "all," which broke gog, himalaya, op CLI, and cron jobs. The undocumented fix was changing sandbox mode to "non-main" (valid values are "all", "non-main", and "off").
- Cron Problems: Morning briefing cron jobs ran inside sandbox containers without access to host binaries or the gateway websocket, causing failures and inconsistent execution times (sometimes firing on UTC instead of ET).
- Permission Issues: Basic commands like
npm install -g openclaw@latestfailed without sudo due to root-owned global npm directories. - Setup Hurdles: Bedrock First Time User form required submission both via webform and CLI, with 3-4 hour delays between attempts.
- Token Management: The gateway auth token embedded in systemd service files rotated frequently, requiring frequent
--accept-latestlogin checks.
Cost Breakdown
The AWS bill for one week totaled $98.31:
- Bedrock (Claude Sonnet 4.6): $69.61
- Lightsail: $8.17
- Other (WAF, Route53, EC2): $20.53
$64 of the Bedrock bill came from a single heavy setup day with 567 invocations, each carrying 10-15K tokens of context. The system prompt (AGENTS.md alone is 8KB, plus SOUL.md, USER.md, and memory files) gets sent on every API call. With 30-minute heartbeat polling, that's ~48 calls/day just for heartbeats.
Recommendations
- Skip Lightsail entirely in favor of a $5 VPS on Hetzner or DigitalOcean with the Anthropic API directly (~$20-35/month at this usage level).
- Change sandbox to "non-main" or "off" immediately instead of the default "all."
- Trim AGENTS.md from the default 8KB boilerplate that ships with every API call.
- Reduce heartbeat frequency from 30 minutes to 1-2 hours for personal bots.
- Set timezone explicitly everywhere since OpenClaw and cron don't always agree on "local time."
📖 Read the full source: r/openclaw
👀 See Also
Using Claude to Root a Trifo Lucy Vacuum and Build a Local Network Server
A developer used Claude to gain root access to a Trifo Lucy robot vacuum after manufacturer servers went down, involving soldering header pins and precise boot timing. Claude then helped create a server to provide basic control for unrooted devices on local networks.
Claude Sonnet 4.6 Grades Bug Reports from Four Qwen3.5 Local Models
A developer tested four Qwen3.5 variants by having them generate bug reports for an iOS game issue, then had Claude Sonnet 4.6 grade the reports. The models correctly identified a Swift bug where equipment border colors don't reset, but test code had compilation issues.
Developer Creates 3D GitHub City Visualization Using Claude Code in One Day
A developer built Git City, a 3D visualization where GitHub users appear as pixel art buildings with height based on commits and width on repositories, using Claude Code exclusively in one day. The project uses Next.js, Three.js, Supabase, and Vercel.
Enterprise OpenClaw Implementation: Lessons from a SaaS Company
A software company running enterprise SaaS for 1,100 companies with 60,000 concurrent users shares their OpenClaw implementation experience, including custom security wrappers, 1,400 API integrations, and CI/CD pipeline integration, while noting limitations in enterprise data handling.