April 15, 2026
Cloud cosplay, comment wars
Show HN: Hiraeth – AWS Emulator
Fake AWS at home: devs cheer, skeptics say “just use the real thing”
TLDR: Hiraeth lets developers imitate parts of Amazon’s cloud on a laptop, starting with message queues, to test faster and cheaper. Commenters split between fans excited to dodge costs and delays, skeptics who insist you should test on real AWS, and shout-outs to alternatives like smoothmq.
Developers just dropped Hiraeth, a “fake AWS at home” tool that lets you practice using Amazon’s cloud without touching the real thing. It starts with SQS (Simple Queue Service), the mailbox where apps swap messages, and runs locally with a web page to peek inside. The crowd loved the idea of faster, cheaper tests—no flaky internet, no surprise bills—while memeing the pain of AWS pricing. One top quip begged, “Now add simulated billing,” and the thread erupted with chuckles. Supporters say this keeps their build‑and‑test loop quick and sane; nobody wants to wait on a data center to move one message.
Then the reality checkers arrived. The big worry: why not just test against a real, small AWS account to be sure nothing breaks later? Skeptics fear “emulator drift,” those tiny differences that cause 2 a.m. outages. The launch post admits it’s early and not a replacement for production; some SQS features are partial, which poured a little cold water on the hype. Meanwhile, tool spotters pointed at rivals like smoothmq. Verdict from the peanut gallery: exciting for local dev, risky if you treat it like the real thing. The vibe is equal parts hope, caution, and billing jokes—cloud discourse.
Key Points
- •Hiraeth is a local AWS emulator focused on fast integration testing, with initial support for Amazon SQS.
- •It processes signed AWS SDK requests via a local HTTP endpoint and stores state in SQLite, with an optional web UI for debugging.
- •Docker/Compose quickstart is provided; the AWS-compatible endpoint runs on localhost:4566 and the admin UI on localhost:4567 with test credentials.
- •Release images are hosted on GitHub Container Registry; maintainers can publish multi-arch images using Docker Buildx and a publish script.
- •The web UI lacks SigV4 auth and should remain bound to a trusted interface; several SQS APIs are supported, while some (e.g., CreateQueue) are partial.