For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

Run agentgateway on AWS, Google Cloud, or Azure, and authenticate to each provider’s managed model services.

Agentgateway runs the same proxy and reads the same configuration file on every cloud provider, so none of the installation methods change when you move to a cloud. What changes is the surrounding environment: which container runtime starts the process, how the process gets an identity, and where its configuration file comes from.

The guides in this section cover those provider-specific parts. Each guide shows the agentgateway configuration that uses the provider’s own identity system, so that agentgateway reaches the provider’s managed model service without an API key in your configuration file.

Kubernetes on a cloud provider

Amazon EKS, GKE, and AKS are ordinary Kubernetes distributions as far as agentgateway is concerned. Two options are available on all three.

• Run standalone agentgateway as a Kubernetes Deployment with the Helm chart. Your configuration file is the source of truth, rendered into a ConfigMap.
• Run the Kubernetes control plane instead, which manages agentgateway proxies from Kubernetes custom resources and the Kubernetes Gateway API.

The identity configuration in each cloud provider guide applies to both options.