Files
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
790 B
Plaintext

# Keep secrets and generated artifacts out of the build context. The Dockerfile
# COPYs the binary, gateway.yaml (unlike the GCP example, the config is baked
# into the image — ECS injects only the secrets it references, as env vars),
# and the RDS CA bundle. BuildKit (the default builder) only syncs the
# referenced COPY sources anyway, so this is a denylist for the classic
# builder (DOCKER_BUILDKIT=0) and a conventional signal that the .gitignore'd
# secrets in this directory aren't part of the image build.
terraform/
**/.terraform/
*.tfstate*
terraform.tfvars
secrets/
*.pem
# The RDS CA bundle is public trust-anchor material (no secret), and the
# Dockerfile COPYs it — carve it out of the *.pem exclusion above.
!rds-global-bundle.pem
*.iam.json
claude.download
claude.bad