I'm not super well versed frankly but my attempt: They're both control planes for envoy proxy. App Mesh is a managed proprietary solution, Istio is open source

I'm not super well versed frankly but my attempt: They're both control planes for envoy proxy. App Mesh is a managed proprietary solution, Istio is open source and self-hosted but there are managed options available. Istio explicitly supports k8s and consul; app mesh doesn't care where the envoy proxies run (great for migrating). I _think_ Istio is a full knowledge model where everyone knows about everyone else in the mesh, App Mesh is explicit. The configuration pushed to the proxies only have the targets that have been modeled as such in the app mesh model (great for larger organizations). App Mesh roadmap: https://github.com/aws/aws-app-mesh-roadmap https://github.com/aws/aws-app-mesh-roadmap Istio's: https://istio.io/about/feature-stages/ https://istio.io/about/feature-stages/