Skip to content

docs(deploy): document first-party AWS & GCP Terraform stacks#275

Draft
yassin-berriai wants to merge 3 commits into
mainfrom
claude/laughing-dijkstra-Fq5ic
Draft

docs(deploy): document first-party AWS & GCP Terraform stacks#275
yassin-berriai wants to merge 3 commits into
mainfrom
claude/laughing-dijkstra-Fq5ic

Conversation

@yassin-berriai

@yassin-berriai yassin-berriai commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds a Terraform infrastructure-stacks section to docs/proxy/deploy.md, documenting the first-party AWS (ECS Fargate) and GCP (Cloud Run) Terraform stacks introduced in BerriAI/litellm#28103.

Covers:

  • The reusable-module + examples/default/ one-command deploy path for both clouds
  • Calling the module directly with for_each for multi-tenant deployments
  • A side-by-side input mapping covering tags/labels, TLS posture, proxy_config, extra env / secrets, gateway_num_workers, and OpenTelemetry v2; spelling out what works the same on each cloud after the AWS/GCP consistency pass in the code PR
  • A pointer to the GCP-only DeployStack one-click Cloud Shell installer for trial flows

The existing User Management Terraform link is preserved under a #### User management subheading.

Related

Add a Terraform infrastructure-stacks section to the deploy guide covering
the reusable module + examples/default one-command deploy, the for_each
multi-tenant pattern, and a state-migration warning for existing deployments.
@vercel

vercel Bot commented Jun 1, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
litellm Ready Ready Preview, Comment Jun 6, 2026 6:38pm

Request Review

The AWS/GCP stacks have never been published, so there are no existing
deployments to migrate; remove the upgrade/migration admonition.
The first-party Terraform stacks now expose the same conceptual surface;
add a side-by-side input mapping (tags/labels, TLS posture,
proxy_config, extra env/secrets, gateway_num_workers, OTel v2) and a
brief opt-in OTel summary so readers don't have to dig through both
READMEs to confirm what works the same on each cloud. Also point at the
GCP-only DeployStack one-click installer for the Cloud Shell trial
path.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants