API Gateway HTTP API
HTTP API with routes, Lambda/ALB integrations, custom domain, JWT authorizers, and access logs.
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-11 · 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 aws-apigateway-http-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/aws-apigateway-http/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle aws-apigateway-http-1.0.0.sigstore.json \
aws-apigateway-http-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "e4af8581fc75d04976c6efea6494b552baae0a4a8f052270f9f3658af4f41449 aws-apigateway-http-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "apigateway_http" {
source = "www.iac-bazaar.com/iac-bazaar/aws-apigateway-http/aws"
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/aws-apigateway-http?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [API Gateway HTTP API](https://www.iac-bazaar.com/catalog/aws-apigateway-http?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "apigateway_http" {
source = "www.iac-bazaar.com/iac-bazaar/aws-apigateway-http/aws"
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
aws-apigateway-http — API Gateway HTTP API
An HTTP API (API Gateway v2) wired end to end: typed integrations
(Lambda-proxy or any HTTP/ALB backend, including private VPC-Link upstreams),
JWT and Lambda authorizers, routes that bind methods/paths to those backends,
a stage with throttling and structured JSON access logs, and an optional
regional custom domain (ACM-backed, TLS 1.2 floor, optional mutual TLS).
Works with Terraform and OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0.
Secure / sane defaults
- Deny-by-default authorization. Routes that name no authorizer inherit
default_authorization_type, which isAWS_IAM— unauthenticated callers are rejected unless a route is explicitly opened withauthorization_type = NONE. Flip the default toNONEonly for a genuinely public API. - CORS off by default. No CORS headers are emitted (same-origin only)
until you opt in; the module refuses the
allow_credentials+"*"origin combination that AWS rejects. - Access logs on by default, streamed as a structured JSON record (request id, source IP, route, status, latency, integration error) to a module-managed CloudWatch log group with 30-day retention (KMS optional).
- TLS 1.2 floor on the custom domain, regional endpoint type, optional mutual-TLS client authentication via an S3 truststore.
- Throttling on by default (burst/rate caps in
default_route_settings) so a single client cannot exhaust the account-wide soft limits. integration_methodis dropped automatically forAWS_PROXY, andconnection_idonly applies toVPC_LINKintegrations — invalid AWS combos are pruned for you.
Requirements
- Terraform or OpenTofu
>= 1.6 hashicorp/aws>= 6.0, < 7.0
License
Commercial — LicenseRef-IaCBazaar-Commercial. © 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 (key)
- Outputs
- Notes
Related modules
aws-appsync
introspection_config defaults to ENABLED, handing any caller a complete map of every type, field and argument, and query_depth_limit defaults to 0, which means no limit - so one nested query multiplies into thousands of resolver calls. Both closed here, with request bodies kept out of CloudWatch and a WAF association for the rate nothing else bounds.
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.
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.
gcp-api-gateway
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.
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.