AWS App Mesh reached its discontinuation date on September 30, 2026. AWS points ECS users to Service Connect (no extra charge, now zone-aware) and offers VPC Lattice for cross-account traffic; EKS users often land on Istio. What each replaces, what each does not, and how to migrate.
AWS discontinued App Mesh effective September 30, 2026, after a notice period in which it kept providing security and availability updates. Anything still depending on it has no supported control plane, so it should move now.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
ECS-only, services in one account: Service Connect. It is AWS's stated path from App Mesh, and zone-aware routing cuts cross-AZ data transfer for chatty services.
Calls across accounts or between ECS, EKS and Lambda, or where you want IAM to decide which service may call which: VPC Lattice.
EKS with advanced traffic management or mTLS everywhere: Istio, ideally in ambient mode to avoid per-pod sidecars.
If you used App Mesh only for service discovery and retries, Service Connect covers it with far less configuration.
List which App Mesh features each service uses: routes, retries, timeouts, TLS, outlier detection. Not every Envoy feature exists in Service Connect yet.
Create a Service Connect namespace and enable it on one client and one server service in a test environment.
Move services one at a time, updating clients to the Service Connect names, and watch error rates and latency.
Remove the App Mesh Envoy sidecars and virtual nodes once nothing routes through them.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Moving From Jenkins to GitHub Actions: Audit, Forecast, Dry-Run, and the Plugins That Do Not Translate
The Jenkins server under someone's desk is a classic legacy system: plugins nobody updates, credentials in global config, builds only one person can fix. GitHub Actions Importer audits Jenkins, forecasts Actions usage and converts pipelines. What converts cleanly, what does not, and how to handle AWS credentials on the other side.
Read
From docker-compose on a VM (or Docker Swarm) to ECS: A Small-Team Migration
Many products still run as a docker-compose file on one server, or a small Swarm cluster. It works until the server needs patching, the disk fills or traffic doubles. How the pieces of a compose file map to ECS, where state should go, and how ECS Express Mode and ECS Gateway make the move small.
Read
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.