AWS App Mesh Shut Down September 30, 2026 — What Happens and Where to Move
Most end-of-life dates are soft. Support stops, the software keeps running, and the risk accumulates quietly. AWS App Mesh was not one of those. AWS's notice at the top of the App Mesh user guide said that after September 30, 2026 you would no longer be able to access the App Mesh console or App Mesh resources. The meshes, virtual services, virtual routers and virtual nodes that carried traffic between your services stopped being reachable. That was a switch-off with a date, not a slow decay.
Key Dates at a Glance
- AWS App Mesh: generally available 2019-03-27; new-customer onboarding closed September 2024; support discontinued and resources inaccessible 2026-09-30
What actually changed on the date
AWS's own words are precise, so it is worth reading them precisely. "On September 30, 2026, AWS will discontinue support for AWS App Mesh. After September 30, 2026, you will no longer be able to access the AWS App Mesh console or AWS App Mesh resources." Two things follow.
First, this was not a support ending you could ride out. When RHEL 7 or Windows Server 2012 left support, the servers kept booting. Here the control plane went away. The Envoy proxies deployed beside your containers read their configuration from App Mesh; with the mesh resources inaccessible, the routing, retries, traffic shifting and observability those proxies provided are no longer managed by anything.
Second, the date was the same for every account and every region. There was no extension to buy, no long-term option, and no partner who can operate the service on AWS's behalf. The equivalent of "extended support" for a managed service does not exist, which is the honest reason this page contains no vendor recommendation.
appmesh, an envoy sidecar image from AWS, or virtual node names, those services lost their managed routing on September 30, 2026.The timeline AWS has published
| Date | What AWS said | Source |
|---|---|---|
| March 27, 2019 | App Mesh generally available and supported for production use | AWS What's New |
| September 2024 | End-of-support announced; new customers can no longer onboard from the announcement day; existing customers continue, with critical security and availability updates | AWS Containers blog |
| September 30, 2026 | Support discontinued; console and App Mesh resources no longer accessible | App Mesh user guide |
Two years of notice is generous by cloud standards, and it is exactly the kind of notice that gets filed and forgotten. The September 2024 announcement landed the same day the onboarding door closed, so anyone who read it then had a working mesh and no urgency. The urgency arrived on September 30, 2026.
Where AWS says to move
On Amazon ECS: Amazon ECS Service Connect
Service Connect is the ECS-native replacement and the one AWS's migration guide is written for. It gives service discovery, retries, outlier detection and health-aware routing without a separately managed mesh, configured on the ECS service itself rather than through virtual nodes and routers. Traffic shifting between task-set versions, which was a common reason to adopt App Mesh on ECS, is handled by ECS deployment configuration instead. The migration guide walks through mapping virtual services to Service Connect namespaces and removing the Envoy sidecar from the task definition.
On Amazon EKS: Amazon VPC Lattice
For Kubernetes workloads AWS points to VPC Lattice through the Gateway API controller, rather than to a drop-in mesh. Lattice operates at the VPC level, so it also covers service-to-service traffic across clusters and accounts, which App Mesh handled only within a mesh. Teams that used App Mesh on EKS mainly for mutual TLS and fine-grained routing should expect a design conversation, not a find-and-replace: the Gateway API resources are a different model from virtual routers and routes.
A third option AWS does not name
Some EKS teams will choose an open-source mesh such as Istio or Linkerd instead. That is a reasonable choice for a Kubernetes-only estate with the operations capacity to run a control plane, and it trades AWS's managed operation for portability. It is not the path AWS documents, and it means owning the mesh's own lifecycle from now on.
What to do now
- Find every mesh. In each account and region:
aws appmesh list-meshes, thenlist-virtual-servicesandlist-virtual-nodesper mesh. Search infrastructure code forAWS::AppMesh,appmeshannotations on Kubernetes resources, and the AWS Envoy image reference in task definitions. - Classify by platform. ECS services go to the Service Connect guide; EKS workloads go to the VPC Lattice guide. Mixed estates are two projects, not one.
- Migrate the traffic-shaping first. Canary and weighted routing are the features whose loss is felt on day one. Plain service discovery can move last.
- Remove the sidecars. A container still configured to read from a mesh that no longer answers is a container that fails its own health checks. Take the Envoy sidecar and the proxy configuration out of the task definition or pod spec as each service moves.
- Clean up what is left. The switch-off removed access to the service, not the references to it in your own code: delete leftover mesh resources from infrastructure code, task definitions and manifests so nothing still depends on it.
Frequently Asked Questions
Was AWS App Mesh deprecated or shut down?
Shut down. AWS's notice said that after September 30, 2026 you would no longer be able to access the App Mesh console or App Mesh resources. That was a switch-off, not a support ending: the meshes, virtual services, routers and nodes stopped being reachable.
Could existing customers keep using App Mesh until the date?
Yes, and AWS said it would continue to provide critical security and availability updates until the switch-off. New customers had been unable to sign up since September 2024, so a new account could not adopt it even for a transition. Since September 30, 2026 the service is gone for everyone.
Where does AWS say to move?
Amazon ECS Service Connect for workloads on Amazon ECS, and Amazon VPC Lattice for workloads on Amazon EKS. Both are AWS-managed, and AWS publishes a migration guide for each path.
Is there third-party extended support for App Mesh?
No. App Mesh is a managed service that only AWS operates, so there is nothing a third party can patch or keep running. The only path past the date is migration, which is why this page recommends no vendor.
Where is the authoritative notice?
The "End of support notice" at the top of the App Mesh user guide (docs.aws.amazon.com/app-mesh/latest/userguide/what-is-app-mesh.html), and the AWS Containers blog post "Migrating from AWS App Mesh to Amazon ECS Service Connect", which carries the onboarding cut-off and the security-update commitment. Both dates on this page are re-checked against that notice at every build.