Technology1 min read

Stop Deploying to ECS Just to See If Your Code Works

By · Published by Everything Blog

In short

The new ECS support connects local machines straight to staging environments without modifying base application images or exposing open inbound ports. A one-time setup container loads the tool into the target task, while an intermediary sessions-manager bridges the environments using outbound HTTPS connections. This configuration routes outgoing requests directly through the ECS task, granting local code seamless access to private cloud databases. It ensures engineers and automation agents can validate complex microservice interactions safely before triggering actual production rollouts.

Key points

  • Teams can eliminate full deployment cycles by executing local code inside cloud task cont…: Teams can eliminate full deployment cycles by executing local code inside cloud task contexts.
  • Local environments safely access private cloud databases because outgoing calls originate…: Local environments safely access private cloud databases because outgoing calls originate from inside the ECS container.
  • Base container images remain completely untouched thanks to an initial one-time sidecar s…: Base container images remain completely untouched thanks to an initial one-time sidecar setup.

Sources checked by our analysis pipeline: 1

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 to learn whether it worked, and it rarely gets there on the first try. Most of the speed you got from the agent ends up spent on waiting for rollouts.

Today we’re launching mirrord for ECS. Your code can now run on your laptop, in your CI runner or in your coding agent’s sandbox as if it were a live task in your staging environment, with the task’s network, environment variables and IAM task role. It reaches the same databases, queues, and internal and external APIs as the deployed service. Only the requests that carry your session header come to it, so you, your teammates and your agents can each…

Technology