Stop Deploying to ECS Just to See If Your Code Works
Liriel
29 points
6 comments
November 18, 2026
Related Discussions
Found 5 related stories in 562.1ms across 13,334 title embeddings via pgvector HNSW
- Ephemeral Testing ibobev · 46 pts · October 05, 2026 · 51% similar
- AWS Emulator and the engineer's job when agents write the code drbm · 111 pts · November 11, 2026 · 49% similar
- Show HN: I built self-hosted deployment automation tool for Windows and IIS dt3ft · 28 pts · August 25, 2026 · 48% similar
- Show HN: OneDeploy – Managed open-source apps with nightly backups and TLS relatedcode · 26 pts · October 16, 2026 · 45% similar
- Testcontainers and Reuse sarumake · 13 pts · October 06, 2026 · 45% similar
Discussion Highlights (4 comments)
eyalbukchin
Hi HN, Eyal from MetalBear here, thanks Liriel for posting. Indeed, with the new mirrord for ECS you add a setup container to the task definition in staging once, and from then on your local code can run as if it were the live task, with its network, environment and IAM role. Only requests with your session header reach it, and everyone else on staging keeps hitting the deployed task. Bottom line is much faster development cycle against ECS, obviously much more important now with agents. Happy to take questions!
tptacek
Style nit: I kind of hate these kinds of titles. "Stop deploying to ECS", OK, I'm interested in reading a take here... but then the take is "... because we have a new product offering that avoids the need". If it's a strong product offering, a more forthcoming title shouldn't hurt your clicks.
on_the_train
This sadly doesn't seem to be about entity component systems
ozlikethewizard
Did I miss something and local dev environments have stopped existing?