Local AWS development / Beta

Build your AWS app.
Test it locally.

Run functions, route events and move data between services on your machine. A native Linux emulator, with the AWS tools you already use.

Get started on Linux See what you can build

Open sourceLinuxApache 2.0

S3 Lambda DynamoDB
127.0.0.1:4566Your architecture, running locally.

S3 → Lambda → DynamoDB

Connected services. One local endpoint.

AWS CLI & SDKs Native Rust execution No Docker daemon

Built for your development loop

Build the connections.
Test the outcome.

An event triggers a function. A workflow writes to a table. See what happens across your application, locally.

01 / Connected services

Follow the
whole flow.

Exercise documented integrations between events, functions, queues and storage. Inspect the result, from input to output.

02 / Native by design

A Linux binary.
Your local cloud.

Install a system package and run as your regular user. No Docker daemon to manage. Compute uses compatible host runtimes.

03 / Your tools

Keep the tools
you know.

Connect AWS CLI and SDKs to localhost. Try tested workflows with Terraform, AWS SAM, Serverless Framework v3 and osls v4.

Start with a real use case

From a file upload
to the next action.

Explore three connected architectures, then find more workflows and services for your application.

Amazon S3AWS LambdaAmazon SQS

Upload a file. Trigger a function. Queue the next task.

Storage → function → queue

Explore all architecture examples →

These examples cover specific implemented integrations. Explore requirements and limits in the repository.

Your toolchain, closer to your code

Change the endpoint.
Keep building.

Use AWS CLI and SDKs for implemented operations. Specific Terraform, AWS SAM, Serverless Framework v3 and osls v4 deployments are tested in the project.

AWS CLIAWS SDKsTerraformAWS SAMServerless Framework v3osls v4 · Open Serverless

Your first local run

Install. Start.
Make your first request.

Choose a Debian/Ubuntu or Arch package. Configure your master key, start the server and connect your AWS tools.

Read the installation guide
locallycloud / terminal 
# After installing and configuring your master key
locallycloud

# In another terminal, check the endpoint
curl -fsS http://127.0.0.1:4566/_locallycloud/health
One endpoint. Your local environment.

Platforms and runtime requirements

Packages are available for Debian/Ubuntu and Arch, with x86_64 and ARM support depending on the platform. Source builds are also documented.

Compute workflows need additional host tools. Use WSL 2 on Windows, or connect from macOS through a Linux VM. Keep the same master key when restarting.

A few answers

Before taking
the first step.

Do I need Docker?

LocallyCloud runs without a Docker daemon. Compute workflows require compatible host tools, such as crun or youki on Linux.

Can I use my AWS tools?

Connect AWS CLI and SDKs on port 4566. Specific Terraform, AWS SAM, Serverless Framework v3 and osls v4 workflows are tested. See the repository for configuration and coverage.

What happens after restarting?

Persistent resources use local state. Reuse the same master key after restarting and check service-specific limits in the repository.

Can I use it commercially?

Yes. Apache 2.0 allows commercial use.

Zento Studio Labs ↗

An idea from
Zento Studio Labs.

LocallyCloud is a Zento Studio Labs experiment for exploring AWS workflows locally. Open source, built to make development simpler.

Zento Studio Labs

Ideas, experiments and open source.

Explore the project on GitHub ↗

Feedback and contributions help this lab experiment evolve.

The next step is yours

Your next architecture.
Start it locally.

Start locally