AWS

Deploy OpenClaw on AWS (EC2 + Ubuntu LTS)

Run OpenClaw 24/7 on a stable cloud instance.

Is this setup right for you?

Good fit

  • You need 24/7 uptime
  • You want a stable, shared runtime

Not recommended

  • You only need occasional runs
  • You want zero infrastructure management

Before You Start

  • AWS account
  • Region selected
  • EC2 access and SSH key
  • Supported Node.js version

Installation Steps

To ensure correctness and avoid outdated commands, we guide you through the official installation path and highlight what actually matters for this setup.

Step 1 - Follow the Official Installation Guide

OpenClaw's installation commands may change between versions. To avoid copy-paste errors or outdated instructions, we link directly to the official guide for this setup.

This ensures you always use the latest and supported installation commands.

Step 2 - Platform-Specific Notes (Read Before Running Commands)

Before running the official commands, review these notes to avoid common setup issues on this platform.

  • Open only the required ports in your security group
  • Use an Ubuntu LTS image for stability
  • Plan for backups and log retention

Step 3 - Verify Your Installation

After completing the official steps, confirm that OpenClaw is running correctly.

What you should see: a startup or 'listening' message without immediate errors.

What should work: a reachable endpoint or CLI response indicating the service is active.

If something doesn't look right, see: Troubleshooting Guide

This guide intentionally links to official installation instructions to ensure accuracy. Platform-specific notes and verification steps are curated and validated to improve success rates.

Verify Your Installation

Service status

The OpenClaw service should be running on the instance.

Public access

Your endpoint responds from outside the VPC as expected.

First run

A basic workflow completes without network or permission errors.

Common Issues on AWS

Security group blocks

No response from public endpoint.

Open only the required inbound ports and verify routing.

See troubleshooting

Instance stops

OpenClaw stops after a reboot or idle period.

Use a process manager or system service to keep it running.

See troubleshooting

Unexpected cost

Costs spike after a few days.

Set budget alerts and choose the right instance size.

See troubleshooting
Deploy OpenClaw on AWS – Cloud Deployment Guide | openclawskill