Urgent.News

What's breaking now, across thousands of outlets.

Tech

Stop Deploying to ECS Just to See If Your Code Works

Originally published on metalbear.com . On ECS, the usual way to find out whether a change works is to deploy it. You build the image, push it, register a new task definition revision, wait for the rollout and look at what happened, then do it all again if it's wrong. A loop like that might have been tenable for humans, but a coding agent writes a change in seconds, then waits for a full rollout…

A new tool called mirrord for ECS has been introduced to help developers test their code changes without having to deploy them to the production environment. This tool works by running the code on the developer's laptop, CI runner, or sandbox as if it were a live task in the staging environment, with the same network, environment variables, and IAM task role as the deployed service.

Developers can then use their usual development tools to run their code and see the results, without having to wait for a full rollout. This eliminates the need for the traditional process of building the image, pushing it, registering a new task definition revision, and monitoring the rollout. Mirrord for ECS works by adding a small setup container to each service's task definition, which stays in place after deployment.

When the task starts, the setup container loads mirrord into the app container, allowing the code to run with the app's network and environment. The code and the task both connect to a sessions-manager, which relays traffic between them. This allows the local code to reach the private databases, queues, and APIs that the deployed service can access, without opening any new ports.

Developers can choose where the sessions-manager runs, either in their own Kubernetes cluster or in MetalBear Cloud, and authenticate to it using their session key. Once mirrord is set up, developers can run their code locally with the mirrord up command, and send requests with their session header to the service's staging address.

This allows them to see the results of their changes in real-time, without having to wait for a rollout. If there are any issues, developers can simply change the code and run it again, without the need to build or roll out a new version. MetalBear Cloud provides a sample ECS app that demonstrates how to use mirrord with a small service and a private RDS database.

The tool is also available for other platforms such as Lambda, Cloud Run, Vercel, and Cloudflare, and users can request support for additional platforms on their website.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Every outlet that reported this, and when →

Read the original at dev.to →

More in Tech

Why has it become harder and harder to type one-handed on smartphones these days?

Phones keep getting bigger, but our hands stay the same size. I’m not sure when it started, but every product launch now seems to compete over who has the larger screen, and reviewers keep talking…

  • Larger smartphone screens make one-handed typing difficult.
  • Manufacturers prioritize bigger screens over ergonomics.
  • Phone3box website lists phone dimensions for comparison.

랩트 모네로 붕괴: 익숙한 신뢰 배신 이야기

지난 30년간 지켜본 암호화폐 시장은 참으로 가혹한 스승이다. 날카롭고 고통스러운 조정장을 통해 우리에게 뼈아픈 교훈을 안겨주곤 했다. 2026년 11월 20일 금요일, 우리는 랩트 모네로(wXMR)의 처참한 붕괴로 또 하나의 교훈을 목격했다. 발행자 연결 지갑이 1,350만 달러어치를 매도하면서 wXMR의 가치는 무려 99%나 증발해버렸다.

  • $1.35 million wXMR sold off in single transaction, shattering peg
  • Monero collateral held by custodian, 1:1 peg mechanism flawed
  • Incident raises concerns about trust in custodial lattice assets

npm ERESOLVE: --legacy-peer-deps vs --force (What Each Really Does)

npm has two messages with "ERESOLVE" in them, and they're easy to mix up. One is an error and the install stops. The other is a warning and the install carries on.

  • --legacy-peer-deps ignores peerDependencies while building package tree
  • --force overrides conflict, disables recommended protections
  • Upgrade package with strict peer range is most effective solution

More from Friday 20 November →