Why organizations use Ambassador
Map services to arbitrary URLs in a single, declarative YAML file.
Easily integrate your own authentication service with Ambassador for per-request authentication.
Ambassador uses the high performance Envoy Proxy, which processes over 2M requests/second at Lyft. Ambassador runs as a sidecar to Envoy, insuring that you get raw Envoy performance.
Ambassador uses the proven resilience capabilities of Kubernetes to insure high availability. For example, Kubernetes is responsible for auto-restarting, auto-scaling, and updating (via a RollingUpdate) Ambassador. Unlike many other API gateways, Ambassador has no database -- it relies on ConfigMap to store state.
Easily and safely configure Ambassador without going through operations -- Ambassador is configured using Kubernetes annotations.
How it works
Ambassador sits between your microservices and anything that is trying to access those services. By routing all requests through Ambassador, Ambassador provides centralized functionality for authentication, authorization, routing, and health checking. Ambassador is Kubernetes-native, and is designed to deploy on Kubernetes.