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.
- Update Vertex AI prose references to Agent Platform across the example
(READMEs, script/terraform comments, config template). Functional
identifiers are unchanged: the 'provider: vertex' config key,
roles/aiplatform.user, aiplatform.googleapis.com, and the terraform
resource label (renaming it would recreate the IAM binding in existing
states). First mentions keep '(formerly Vertex AI)' for searchability.
- Drop the README's self-referential public-mirror link.
Reference artifacts accompanying the Gateway-on-GCP walkthrough
(https://code.claude.com/docs/en/claude-apps-gateway-on-gcp), including
its Terraform reference section:
- setup.sh: scripts the walkthrough end to end via gcloud (APIs, service
account, image build/push, private-IP Cloud SQL, secrets, Cloud Run)
- Dockerfile: runtime image for the gateway; setup.sh downloads the
public release binary and verifies it against the release manifest
- gateway.yaml.example: config template (Vertex upstream, Google
Workspace IdP)
- terraform/: module provisioning the same architecture (Cloud Run track)
Provided as a working example to adapt, not a supported production
deployment.
The workflow has been failing daily since 2026-04-27 with HTTP 422
"Pagination with the page parameter is not supported for large
datasets" at page=100. The repo now has ~58k closed issues and the
script was paging past ~10k already-locked ones every run before
reaching any candidates.
Replace listForRepo + page=N with the search API
(is:issue is:closed is:unlocked updated:<cutoff), which returns only
the issues that actually need locking. Cap at 250/run with a 1s sleep
between locks to stay under secondary rate limits.
Claude-Session: https://claude.ai/code/session_016EWY3FKCJyfUdCAZkXfi7i
