Files
claude-code/examples/gateway/aws/terraform/.gitignore
T
Roy Arsan 843297f6b1 Add Claude apps gateway on AWS example deployment assets
Reference artifacts accompanying the Gateway-on-AWS walkthrough
(https://code.claude.com/docs/en/claude-apps-gateway-on-aws), sibling
to the existing examples/gateway/gcp assets:

- setup.sh: scripts the walkthrough end to end via the aws CLI
  (security groups, IAM roles, ECR image build/push with gateway.yaml
  baked in, private-subnet RDS for PostgreSQL, Secrets Manager secrets,
  ECS Fargate service behind an internal ALB)
- Dockerfile: distroless runtime image for the gateway; the Claude Code
  release binary is verified against an operator-supplied sha256
- gateway.yaml.example: config template (Bedrock upstream, Okta IdP)
- terraform/: module provisioning the same architecture (ECS track)

Provided as a working example to adapt, not a supported production
deployment.
2026-07-21 19:22:25 +00:00

20 lines
860 B
Plaintext

# Never commit state (contains secrets) or local var files
*.tfstate
*.tfstate.*
.terraform/
terraform.tfvars
*.auto.tfvars
crash.log
# The lock file holds no secrets. It's ignored here so consumers who copy this
# example into their own repo generate (and commit) their own platform-complete
# lock at first init — committing one from this repo would carry only one
# platform's provider hashes. In your copy, drop this line and commit the lock
# produced by:
# terraform providers lock -platform=linux_amd64 -platform=linux_arm64 \
# -platform=darwin_amd64 -platform=darwin_arm64 -platform=windows_amd64
# versions.tf pins by range only, so without a committed lock the registry
# serves the newest in-range build; a platform-complete lock gives hash
# continuity across machines/CI and makes provider upgrades reviewable diffs.
.terraform.lock.hcl