Managed Istio-based service mesh that provides east-west traffic management, mTLS, fine-grained authorisation, and unified observability across GKE, GKE on AWS, Cloud Run, and VMs, delivered as a GCP-managed control plane (formerly Anthos Service Mesh)
FluffyStack toolsJurisdictional exposure
Attributes
- Managed Control Plane
- Yes
Sub-services (4)
Managed Istio
GCP-operated Istio control plane with automatic upgrades
Automatic mTLS
Mesh-wide mutual TLS with no app-side code changes
Unified Observability
Golden signals, service dependency graph, and per-request telemetry in Monitoring
Compliance & Certifications
This service is attested for the following frameworks. Always verify with the provider before relying on a specific compliance posture.
Where this runs
Sovereign regions (1)
- T-Systems Sovereign Cloud · FrankfurtT-Systems Sovereign Cloud powered by Google Cloud
Commercial regions (43)
Europe (13)
- Belgium
- Finland
- Paris
- Berlin
- Frankfurt
- Milan
- Turin
- Netherlands
- Warsaw
- Madrid
- Stockholm
- Zurich
- London
North America (12)
- Montréal
- Toronto
- Querétaro
- Northern Virginia
- Columbus
- Iowa
- Dallas
- Las Vegas
- Los Angeles
- South Carolina
- Salt Lake City
- Oregon
South America (2)
- São Paulo
- Santiago
Asia (10)
- Hong Kong
- Delhi
- Mumbai
- Jakarta
- Osaka
- Tokyo
- Singapore
- Seoul
- Taiwan
- Bangkok
Oceania (2)
- Melbourne
- Sydney
Middle East (3)
- Tel Aviv
- Doha
- Dammam
Africa (1)
- Johannesburg
Tags
Equivalent services on other platforms
Fully managed application networking service that connects, secures, and observes services across VPCs and AWS accounts without load balancers or service meshes — HTTP, HTTPS, and gRPC routing with IAM-based authorisation. AWS's replacement for App Mesh going forward
Istio-based service-to-service mTLS, traffic management and observability for OpenShift (Service Mesh 3.x), with an Operator-managed control plane, Kiali topology views and tracing via OpenTelemetry-based Red Hat OpenShift distributed tracing
Managed Istio-based mesh for service-to-service traffic on OKE — mTLS by default, traffic shaping, retries, circuit breakers, and observability without per-service sidecar configuration. Pairs with OCI API Gateway for north-south + east-west uniform policy.