API Gateway
Regional managed gateway fronting Cloud Run, functions and App Engine backends.
- Provider
- gcp
- Kind
- API gateway
- Category
- Edge
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| apiKeys | boolean | — | no | true | inherited |
| auth | enum | none | api-key | jwt | oauth2 | mtls | no | none | inherited |
| concurrencyLimit | boolean | — | no | false | inherited |
| configFormat | enum | openapi | grpc | no | openapi | inherited |
| idempotencyKeys | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| keyTtlHours | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| protocol | enum | http | grpc | websocket | fix | ouch | no | http | inherited |
| rateLimiting | boolean | — | no | false | ▸ false |
| regional | boolean | — | no | true | inherited |
| tls | boolean | — | no | true | ▸ true |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
sync-chain-too-deep
Every consecutive synchronous hop from this entry point spends part of the stated p95 latency budget, and the chain's failures multiply. More than three hops is a budget nobody is tracking.
- — all of these hold:
- — the design requirement `latency.p95Ms` has a value
- — the longest chain of synchronous calls starting at the node is more than 3 hops long
nodes:
- { id: "api-gateway", component: "google-api-gateway" }API Gatewayalibaba-api-gatewayAmazon API Gatewayaws-api-gatewayAWS AppSync GraphQL APIaws-appsyncAzure API Managementazure-api-managementAI Gatewaycloudflare-ai-gatewayCloudflare API Shieldcloudflare-api-shieldMCP Server Portalcloudflare-mcp-portalCloudflare Privacy Gatewaycloudflare-privacy-gatewayGeneric API gatewayapi-gatewayApache APISIXapisixApollo GraphOSapollo-graphosEasegresseasegressEmissary-ingressemissaryEnvoy Gatewayenvoy-gatewayGloo GatewayglooHasurahasuraHelicone AI Gatewayhelicone-gatewayHigresshigressKong GatewaykongKong AI Gatewaykong-ai-gatewayKong Konnectkong-konnectKrakenDkrakendLiteLLM ProxylitellmMartian GatewaymartianNot Diamondnot-diamondPortkey AI GatewayportkeyRequestyrequestySpring Cloud Gatewayspring-cloud-gatewayTyk GatewaytykUnifyunify-aiVercel AI Gatewayvercel-ai-gatewayWSO2 API Managerwso2-api-managerZuulzuulApigeeapigeeAgent Gatewaygoogle-agent-gatewayApigee hybridgoogle-apigee-hybridCloud Endpointsgoogle-cloud-endpointsFirebase Data Connectgoogle-firebase-data-connectIBM API Connectibm-api-connectOCI API Gatewayoci-api-gateway
# yaml-language-server: $schema=../../schema/component.schema.json # Google Cloud API Gateway: managed gateway in front of Cloud Run, Cloud Run functions, App Engine and # other backends. Per "About API Gateway" an API config is an OpenAPI or gRPC description, API keys and # Google ID tokens are the supported authentication mechanisms, and per the quickstart a gateway is # deployed to a region and served on a Google-managed hostname. schemaVersion: "1" type: "component" id: "google-api-gateway" kind: "api-gateway" provider: "gcp" docs: "https://cloud.google.com/api-gateway/docs/about-api-gateway" defaults: managed: true tls: true rateLimiting: false properties: regional: type: "boolean" default: true apiKeys: type: "boolean" default: true configFormat: type: "enum" values: ["openapi", "grpc"] default: "openapi"