docs(readme): add Deploy on AWS/GCP with Terraform section

[yassin-berriai]

Summary

Adds a quickstart for the two published Terraform modules on the public registry, inside the existing Get Started section.

• AWS -- copy-paste `main.tf` for `BerriAI/litellm/aws`. ECS Fargate + Aurora + ElastiCache + ALB.
• GCP -- copy-paste `main.tf` for `BerriAI/litellm/google`, plus the one-time `gcloud artifacts repositories create ... --mode=remote-repository` command (Cloud Run can't pull from ghcr.io directly).
• Both snippets default to plaintext LB (`allow_plaintext_alb/lb = true`) with commented-out lines for prod TLS, since the README example is the "kick the tires" path.
• Closes the loop on the BerriAI/project-releaser workflow that publishes the modules to the registry on each stable/rc release.

Where it lands

Inside Get Started, between the gateway-vs-SDK table and "Run in Developer Mode" -- where someone scanning the README for "how do I deploy this" will look.

Test plan

• Skim the new section on the rendered README to confirm code blocks look right.
• Click both registry links and verify they resolve to the latest published version.
• Spot-check one `terraform init && terraform apply` end-to-end from the AWS snippet against a sandbox account.

🤖 Generated with Claude Code

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 4 committers have signed the CLA.

✅ yuneng-berri
❌ yassin-berriai
❌ shin-berri
❌ claude
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[codspeed-hq]

Merging this PR will not alter performance

✅ 16 untouched benchmarks

---

_{Comparing chore/readme-tf-deploy-snippets (2c56b4d) with main (8f41fdb)}

[greptile-apps]

Greptile Summary

This PR adds a new "Deploy on AWS or GCP with Terraform" section to the root README.md, providing copy-paste main.tf quickstarts for the published BerriAI/litellm/aws and BerriAI/litellm/google Terraform Registry modules.

• AWS snippet wires ECS Fargate + Aurora + ElastiCache + ALB with allow_plaintext_alb = true and a commented-out ACM cert line for production TLS.
• GCP snippet adds a prerequisite gcloud artifacts repositories create command to proxy GHCR through Artifact Registry (required because Cloud Run rejects ghcr.io directly), then deploys Cloud Run + Cloud SQL + Memorystore + HTTPS LB.

Confidence Score: 3/5

The change is README-only and cannot break runtime behaviour, but it adds documentation directly to this repository in a way the team has explicitly decided against.

A team rule explicitly requires new documentation to live in the litellm-docs repo rather than here; this PR deposits 124 lines of Terraform quickstart content into the root README instead. Beyond the policy issue, the GCP snippet silently requires users to replace my-gcp-project in three separate locations — the project_id input, the image_registry path, and the gcloud --project flag — with no hint that all three need to match, which could produce a confusing Artifact Registry resolution failure at apply time.

README.md — the only changed file; the GCP section needs the placeholder concern addressed and the content should be evaluated for placement in the litellm-docs repo.

Important Files Changed

Filename	Overview
README.md	Adds a 124-line "Deploy on AWS or GCP with Terraform" section with copy-paste HCL quickstarts; violates the policy requiring new documentation to live in the litellm-docs repo, and the GCP snippet has a repeated placeholder that users may only partially substitute.

Comments Outside Diff (1)

1. README.md, line 406-529 (link)

   Documentation added to README violates litellm-docs repo policy

   Per the team's custom instruction, documentation additions should live in the litellm-docs repository rather than being committed here. This entire "Deploy on AWS or GCP with Terraform" section (124 lines) was added to the root README.md, which will diverge from the canonical docs site and creates a maintenance burden when these snippets need to be updated with new module versions.

   Rule Used: Prevent documentation from being added - needs to ... (source)

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

_{Reviews (1): Last reviewed commit: "docs(readme): add Deploy on AWS/GCP with..." | Re-trigger Greptile}

[greptile-apps]

my-gcp-project placeholder must be updated in three separate locations

The GCP snippet requires users to substitute my-gcp-project in three distinct places: the project_id input, the image_registry path, and the --project flag in the preceding gcloud command. It's easy to update project_id and miss the others — the image_registry value in particular looks like a module default rather than a user-specific placeholder, so users who copy-paste may end up pointing Cloud Run at a non-existent Artifact Registry path and hit a confusing deploy failure. Adding an inline comment like # Replace my-gcp-project with your GCP project ID on the image_registry line would help.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[mateo-berri]

LGTM; thanks!