Cloud Endpoints
Self-deployed ESPv2 Envoy proxy with Google-managed API keys, auth and quotas.
- 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 |
| hostingPlatform | enum | cloud-run | gke | compute-engine | app-engine-standard | no | — | inherited |
| idempotencyKeys | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| keyTtlHours | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ false |
| protocol | enum | http | grpc | websocket | fix | ouch | no | http | inherited |
| proxy | string | — | no | espv2 | inherited |
| rateLimiting | boolean | — | no | false | ▸ false |
| tls | boolean | — | no | true | inherited |
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: "cloud-endpoints", component: "google-cloud-endpoints" }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-gatewayAPI Gatewaygoogle-api-gatewayApigee hybridgoogle-apigee-hybridFirebase Data Connectgoogle-firebase-data-connectIBM API Connectibm-api-connectOCI API Gatewayoci-api-gateway
# yaml-language-server: $schema=../../schema/component.schema.json # Google Cloud Endpoints: the Envoy-based ESPv2 proxy that you deploy in front of your own API. Per "About # Cloud Endpoints" you run ESPv2 on Cloud Run, GKE, Compute Engine or App Engine yourself while Google # provides the service management backend, and authentication and quotas come from the OpenAPI config. schemaVersion: "1" type: "component" id: "google-cloud-endpoints" kind: "api-gateway" provider: "gcp" docs: "https://cloud.google.com/endpoints/docs/openapi/about-cloud-endpoints" defaults: managed: false rateLimiting: false properties: proxy: type: "string" default: "espv2" hostingPlatform: type: "enum" values: ["cloud-run", "gke", "compute-engine", "app-engine-standard"] apiKeys: type: "boolean" default: true