Platform teams running large-scale service mesh deployments need two things above all: reliability and the ability to quickly diagnose issues when they arise. At the same time, many teams are navigating the transition away from the upcoming AWS App Mesh deprecation, exploring Ambient mesh, and looking for more control over how services are structured across clusters. With Solo Enterprise for Istio 1.29, we focused on strong production debugging tools and GA-ready ECS support ahead of the AWS App Mesh sunset.
Key Highlights
- AWS ECS Integration reaches General Availability, with multi-region and multi-account support, comprehensive Day 2 operations documentation, and a clear migration path for AWS App Mesh users.
- Major debuggability and multi-cluster observability improvements, including a new peering Helm chart, enhanced istioctl multi-cluster checks, and new istiod and ztunnel metrics.
- Global Service Aliasing gives teams the ability to define any custom naming pattern for their global services, extending the Segments feature introduced in 1.28.
ECS Integration: Now Generally Available
AWS ECS support reaches General Availability in this release, reflecting extensive testing, real-world validation, and direct customer demand. With AWS App Mesh planned for deprecation in 2026, Solo Enterprise for Istio 1.29 is the clear next step. ECS tasks and services plug into an Istio control plane running on EKS, with the mesh automatically discovering ECS workloads and securing traffic across the fleet, between ECS and EKS clusters, and across multiple AWS accounts.
What changed for GA: multi-region service discovery with a single AWS IAM role; multi-account support for enterprises with complex AWS footprints and comprehensive Day 2 ops docs covering upgrades, rollbacks, and certificate rotation.
Debuggability and Observability
A core release goal was giving operators the right instrumentation to understand their environment and diagnose issues quickly.
- New peering Helm chart lets teams declaratively configure east-west gateway and Istio Remote Gateway resources, with pod disruption budgets, HPA, and anti-affinity rules built in.
- Enhanced istioctl multi-cluster check now walks through the entire peering setup step by step, with a verbose mode surfacing per-peer XDS connection state and license status.
- New istiod peering metrics expose connected and disconnected peer counts and XDS failures by peer, with a pre-built Grafana dashboard.
- New ztunnel health metrics (total endpoints, unhealthy endpoints, TCP connection failures by reason) support outlier detection at L4 and significantly reduce time-to-resolution.
Global Service Aliasing
Global Service Aliasing, introduced as alpha in Istio 1.29, adds a templating mechanism built on the Segments feature from 1.28, letting teams generate hostnames using any combination of service name, namespace, and label values.
- Flexible pattern templating with multiple active patterns simultaneously.
- Selector-based targeting applies patterns only to services matching specific label criteria.
- Safe conflict handling blocks and flags alias collisions rather than silently overwriting services, with conflict counts surfaced in segment status.
Practical use case: Consider a scenario where you need to establish a service, such as app.accounting.example.com. This service should be accessible both externally through an ingress gateway and internally as a global service within your mesh, thereby avoiding ingress expenses for internal traffic. Furthermore, you may want to apply distinct policies to this single host depending on whether the traffic is arriving via ingress (north-south) or moving within the mesh (east-west).
Learn More
For full technical details and upgrade guidance, see the Solo Enterprise for Istio 1.29 release notes. Hands-on labs are available at solo.io. For migrations from AWS App Mesh, reach out to the Solo team.
Also available: Gloo Mesh Enterprise 2.12 was released and adds support for Istio 1.29.
%20a%20Bad%20Idea.png)
%20For%20More%20Dependable%20Humans.png)
