API Gateway (OpenAPI 2.0)
A serverless API Gateway fronting an OpenAPI 2.0 spec - API, immutable config and managed gateway - with a dedicated least-privilege backend service account and a built-in default spec.
Verification
Live-testedReally deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan test superseded by live test
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-30 · how we verify
Verify this download
cosign · sha-256Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.
# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub
# 2. This module's Sigstore bundle
curl -o gcp-api-gateway-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/gcp-api-gateway/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle gcp-api-gateway-1.0.0.sigstore.json \
gcp-api-gateway-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "5d501a818fb33c0da6d8936b60cac40c6a0d747d3d28a217c1db1e39e665ff13 gcp-api-gateway-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "api_gateway" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-api-gateway/gcp"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/gcp-api-gateway?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [API Gateway (OpenAPI 2.0)](https://www.iac-bazaar.com/catalog/gcp-api-gateway?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "api_gateway" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-api-gateway/gcp"
version = "1.0.0"
}
```Preview:
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
gcp-api-gateway
A serverless API Gateway fronting an OpenAPI 2.0 (Swagger) spec: the API,
an immutable API config that carries the spec, and a managed gateway. A
dedicated gateway service account is created and set as the backend identity
(instead of the default compute SA), so calls to authenticated backends are made
as a least-privilege principal. The OpenAPI document is embedded inline
(base64-encoded) and the module ships a minimal valid default — a single
GET /hello — so it deploys standalone with no real backend. Works with
Terraform and OpenTofu (>= 1.6).
Provider note: API Gateway resources (
google_api_gateway_*) are only available in the google-beta provider. The module requiresgoogle-betaand setsproject/regionexplicitly on every resource, so it works with an implicit/default google-beta provider configuration (ADC credentials) — you do not need a separate provider block when the gateway is the only beta resource.
What you get per module call:
- An API Gateway API + immutable API config + deployed gateway
- An inline, base64-encoded OpenAPI 2.0 document (built-in default or your own)
- A dedicated gateway backend service account (least privilege)
create_before_destroyon the immutable config so spec changes roll forward
Requirements
| Requirement | Version |
|---|---|
| Terraform / OpenTofu | >= 1.6 |
hashicorp/google | >= 7.0, < 8.0 |
hashicorp/google-beta | >= 7.0, < 8.0 |
The API Gateway (apigateway.googleapis.com), Service Management
(servicemanagement.googleapis.com) and Service Control
(servicecontrol.googleapis.com) APIs must be enabled on the project.
License
Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
- Inputs
- Outputs
Related modules
tencent-api-gateway
An API Gateway service with net_type INNER rather than OUTER, https rather than the http that stays plaintext to the gateway, and QPS ceilings required - without a limit one caller can spend the whole backend's capacity. auth_type NONE and CORS are both named per API, since either turns an endpoint into an open one.
oci-api-gateway
Managed API gateway with route deployments, JWT/auth policies, rate limiting, CORS and custom-domain TLS.
aws-apigateway-http
HTTP API with routes, Lambda/ALB integrations, custom domain, JWT authorizers, and access logs.
aws-apigateway-rest
A REST API wired end to end - resource tree built from route paths, deny-by-default IAM authorization, MOCK/Lambda/HTTP integrations, deployment + stage with throttling and JSON access logs.
azure-api-management
An API Management gateway tuned for the serverless Consumption tier - scale-to-zero, billed per call - with a system-assigned managed identity, TLS hardening, and HTTP/2 enabled.
huawei-api-gateway
A Huawei Cloud APIG dedicated instance, group, environment and published APIs. The provider defaults an API to no authentication; this module defaults to signed app requests and takes open or plaintext APIs one at a time. Every published API gets the required rate limit, the gateway stays off the internet unless asked, and the debug hostname stays off.