---
title: "API Gateway"
description: "3 posts about API Gateway, summarised, each linking to the original."
---

# API Gateway
> 3 posts about API Gateway, summarised, each linking to the original.

## Articles

### [Multi-region disaster recovery for Amazon API Gateway WebSocket APIs](https://yomu.fyi/post/multi-region-disaster-recovery-for-amazon-api-gateway-websocket-apis.md)
- Company: [AWS](https://yomu.fyi/company/aws.md)
- Author: Shubham Dhoka
- Published: Oct 14, 2026
- Type: Tutorial

WebSocket connections for real-time applications like live auctions and collaborative editors are vulnerable to regional outages because each connection is tied to a single AWS Region. A regional failure severs all active connections and loses session state. This post presents an active-passive multi-region disaster recovery pattern that uses Amazon API Gateway WebSocket APIs, Route 53 failover routing, DynamoDB Global Tables for cross-Region state replication, a canary health probe, and client-side reconnection logic. The canary Lambda function tests the endpoint every minute and drives a CloudWatch alarm that triggers a Route 53 health check to mark the primary Region unhealthy. Clients detect connection drops via application-level heartbeat messages and reconnect with exponential backoff and full jitter to avoid thundering herd. After reconnection, clients retrieve the latest application state from the secondary Region’s DynamoDB replica and resume their session automatically.


### [Architecting Secure Identity: Extending Auth0 PrivateLink with Intelligent Gateways](https://yomu.fyi/post/architecting-secure-identity-extending-auth0-privatelink-with-intellig.md)
- Company: [Auth0](https://yomu.fyi/company/auth0.md)
- Author: Daryl Martis
- Published: Oct 2, 2026
- Type: Problem & solution

Enterprises centralize authentication into a single Auth0 environment but must comply with frameworks like PCI-DSS, HIPAA, and SOC 2 that restrict data to private channels. Auth0 Outbound PrivateLink provides a secure unidirectional connection between Auth0 and AWS infrastructure, avoiding the public internet. However, a single PrivateLink connection per environment cannot directly reach multiple isolated VPCs for staging and production. The Intelligent Gateway Pattern solves this by deploying an API gateway or reverse proxy at the PrivateLink termination point to fan out traffic. Auth0 Actions append context such as custom headers like X-Target-Env or specific paths, and the gateway inspects these to route requests to the appropriate isolated VPC, decoupling secure transport from internal routing. This pattern unblocks identity consolidation by allowing a single Auth0 tenant to serve both staging and production workloads while maintaining strict VPC isolation.


### [Turn your REST APIs into MCP tools with Google Cloud API Gateway](https://yomu.fyi/post/turn-your-rest-apis-into-mcp-tools-with-google-cloud-api-gateway.md)
- Company: [Google](https://yomu.fyi/company/google.md)
- Author: Sanjay Pujare, Paul Howell
- Published: Sep 24, 2026
- Type: Announcement

Most enterprise REST APIs are invisible to AI agents, forcing teams to run separate MCP servers that duplicate their existing gateway logic. Google Cloud API Gateway in Public Preview solves this by acting as a remote MCP server — annotate the OpenAPI 3.0.x/3.1.x spec with x-google-api-management.mcp and deploy it with no extra infrastructure. The gateway accepts MCP JSON-RPC requests on a single /mcp endpoint, transcodes tools/call into the corresponding REST call, runs it through existing policies, and returns the response as an MCP result. Authentication via JWT or API key works unchanged for REST operations; tools/list is unauthenticated by default and requires JWT in production for security. With no separate server to operate, teams in Public Preview can expose up to 1,000 tools per gateway that support existing authentication and quota, and the MCP server is automatically discoverable via API hub and Agent Registry.