product updateAnthropic

AWS Publishes Reference Architecture for Deploying Anthropic's Claude Apps Gateway at Enterprise Scale

TL;DR

AWS published a production reference architecture for deploying Anthropic's Claude apps gateway, a self-hosted governance layer that sits between Claude Code, Claude Desktop, and Amazon Bedrock or Claude Platform on AWS. The deployment pattern centralizes SSO authentication, model access policy, and spend controls for enterprise rollouts.

3 min read
0

AWS has published a production reference deployment for Anthropic's Claude apps gateway, a self-hosted governance layer designed to sit between Claude Code, Claude Desktop, and either Amazon Bedrock or Claude Platform on AWS. The post extends an earlier launch announcement with concrete architecture, deployment patterns, and configuration guidance for enterprise administrators.

The gateway ships inside the same Claude Code CLI binary developers already use and starts in server mode via claude gateway --config gateway.yaml. In AWS's reference architecture, it runs as a stateless container on AWS Fargate within a customer VPC, though AWS notes the same image also runs on Amazon EKS or Amazon EC2.

Architecture details. Session state — including device codes, sign-in sessions, per-user spend counters, and audit records — lives in Amazon RDS for PostgreSQL rather than in the gateway task itself. Because auth state is externalized, any Fargate task can serve any request without sticky sessions on the load balancer. An internal Application Load Balancer terminates TLS via AWS Certificate Manager, with Amazon Route 53 private hosted zones resolving the gateway over VPN or AWS Direct Connect. The gateway authenticates to Bedrock using its assigned IAM role, while Claude Platform API keys and other static credentials stay in AWS Secrets Manager — no upstream credentials are distributed to developer machines.

Governance controls. The gateway addresses five stated governance needs, with the post detailing two in depth:

  • Identity/SSO: Authentication delegates entirely to a customer's OIDC provider (Okta, Microsoft Entra ID, Auth0, Keycloak, or Amazon Cognito). Developers sign in once via browser-based OAuth 2.0 device authorization grant; the gateway issues a bearer token with a one-hour default time-to-live and refreshes it silently. The gateway maintains no user directory of its own — group membership comes directly from the identity provider, and offboarding is accomplished simply by removing a user from that provider.

  • Policy/model access: Administrators define model access and tool permissions in a single YAML policy block, matched by identity provider group and evaluated in declaration order with a required catch-all (match: {}) entry. Example policies shown restrict contractor groups to Claude Haiku models with web access denied, while engineering groups get access to Claude Opus, Sonnet, and Haiku models with file-access guardrails. Policy changes propagate to connected clients within one hour with no developer action required.

Usage metrics are attributed to authenticated identities and forwarded via the OpenTelemetry Protocol (OTLP) to a customer-configured collector, enabling per-user or per-group cost attribution and spend-cap enforcement.

AWS did not disclose pricing for running the gateway infrastructure itself (Fargate, RDS, ALB, and NAT gateway costs apply per standard AWS billing), nor pricing changes to underlying Bedrock or Claude Platform inference. Deployment scripts, configuration templates, and an operational guide are available through AWS's accompanying repository and documentation.

What this means: This is an infrastructure and governance release, not a new model. It targets a specific enterprise pain point — IT and security teams need centralized SSO, model-access policy, and cost attribution before they'll approve broad rollout of Claude Code and Claude Desktop across a workforce. By keeping credentials off developer machines and externalizing session state to RDS, AWS and Anthropic are positioning the gateway as infrastructure that satisfies enterprise compliance and audit requirements rather than adding new model capability. Organizations already standardized on AWS and an OIDC identity provider get a relatively low-friction path to deploy Claude tooling at scale; the more interesting signal is that AI coding tools are now mature enough to need this kind of governance tooling in the first place.

Related Articles

product update

Aderant Cuts Ticket Triage Time 8-14 Hours Weekly Using Amazon Nova Lite

Aderant built a serverless ticket triage system on Amazon Nova Lite that reviewed 109 tickets in its first 2.5 weeks with roughly 96% routing accuracy. The company estimates the system recovers 8-14 engineering hours per week at under $30 in total monthly operating cost.

product update

AWS Brings Alibaba's Qwen3-TTS Voice Cloning Model to SageMaker Real-Time Endpoints

AWS published a deployment guide for running Alibaba's Qwen3-TTS-12Hz-1.7B-Base voice cloning model as a real-time SageMaker inference endpoint. The model clones a speaker's voice from a short audio clip and generates speech in 10 languages, including cross-lingual cloning, without retraining.

product update

Microsoft Merges Coding and Productivity Copilot Into Single App to Counter Anthropic

Microsoft launched an updated Copilot app that merges coding, productivity tasks, and custom agent creation into three tabs — Cowork, Code, and Autopilot. The company is shifting to usage-based pricing as it tries to close the gap with Anthropic's Claude in enterprise AI adoption.

product update

GitHub Copilot App Adds Canvases for Custom, Natural-Language-Built Workflows

GitHub has published a beginner's guide to canvases in the Copilot app, a feature that lets users describe an interface in natural language and have the agent build a live, interactive surface. The feature targets users who want custom workflow tools without writing code.

Comments

Loading...