api-gateway

Manage north-south microservices traffic with edge routing and security features.

Updated Jun 5, 2026

Search Tags:#security #microservices #rate-limiting #traffic-management #api-gateway

Ready to run

npx skills add https://github.com/hung-phan/system-skills --skill api-gateway-hung-phan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: api-gateway
Source: https://github.com/hung-phan/system-skills/tree/main/skills/system-review/references/communication/api-gateway
Command: npx skills add https://github.com/hung-phan/system-skills --skill api-gateway-hung-phan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires envoy, kong, nginx, aws-api-gateway, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing north-south traffic for microservices, providing a single entry point for authentication, authorization, rate limiting, and observability.

Core Features & Use Cases

Edge Layer for Traffic: Handles routing, authentication, authorization, rate limiting, and security for external clients.
Use Case: When you need a stable public URL for your microservices while ensuring consistent security and traffic management.
Features: TLS termination, JWT verification, rate limiting, request/response shaping, and observability.

Quick Start

Use the api-gateway skill to route requests to your services and enforce security policies.

Frequently Asked Questions about api-gateway

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage north-south traffic for microservices with an API gateway?▼

An API gateway manages north-south traffic for microservices by routing external client requests through a single entry point that enforces security and traffic policies. It provides edge routing, TLS termination, and request shaping.

What is the best way to enforce JWT verification and rate limiting across microservices?▼

The best way to enforce JWT verification and rate limiting is handling them at the API gateway edge layer. This centralizes authentication and authorization policies before traffic reaches internal services.

Does this API gateway support Envoy, Kong, and Nginx for edge routing?▼

Yes, this API gateway supports Envoy, Kong, Nginx, and AWS API Gateway. These dependencies provide the underlying infrastructure for edge routing, TLS termination, and request response shaping.

When do I need TLS termination and request shaping for external client interactions?▼

You need TLS termination and request shaping when exposing microservices to external clients. An API gateway secures these interactions by offloading SSL decryption and standardizing request formats before internal routing.

How do I set up a stable public URL for microservices while ensuring consistent security?▼

To set up a stable public URL for microservices, route external traffic through an API gateway. This centralizes security policies like JWT verification and rate limiting while providing a single entry point for external clients.

What are the limitations of using an API gateway for microservices traffic management?▼

An API gateway is optimized for north-south traffic and external client interactions, meaning it may not address east-west service-to-service communication within the internal microservices mesh.