# api-gateway-configuration

A skill that walks through API gateway setup for microservices: routing, auth, rate limiting and request transformation.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 408 installs · ★ 236
- Author: secondsky
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/secondsky/claude-skills/tree/HEAD/plugins/api-gateway-configuration/skills/api-gateway-configuration/SKILL.md
- Updated: 2026-10-20
- HTML: https://affpapa.org/en/nevibecode/skills/secondsky-api-gateway-configuration

## What it does

The skill lays out what an API gateway handles: request routing and load balancing, authentication and authorization, rate limiting, request and response transformation, logging, monitoring and SSL termination. Then it gives ready config examples for four gateways.

Kong gets a YAML file with services, routes and plugins — a per-minute rate limit and JWT. Nginx gets an upstream block with weighted servers, keepalive, proxy headers and a separate location for health checks. AWS API Gateway gets a SAM template with a JWT authorizer backed by Cognito. A best-practices section follows: authenticate at the gateway, apply global rate limits, log requests, health-check backends, cache responses, enforce HTTPS in production and keep backend details out of error responses.

Nothing runs on its own — this is a configuration reference. If your project already has a gateway you are happy with, or you do not run Kong, Nginx, AWS API Gateway or Traefik, there is little here for you.

## Requirements
- Works with: AWS

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add secondsky/claude-skills --skill api-gateway-configuration -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/api-gateway-configuration/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/api-gateway-configuration/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add secondsky/claude-skills --skill api-gateway-configuration -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/api-gateway-configuration/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add secondsky/claude-skills --skill api-gateway-configuration -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/api-gateway-configuration/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install secondsky/claude-skills api-gateway-configuration
```

2. **Manually: put the files in place**
- File: `.github/skills/api-gateway-configuration/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add secondsky/claude-skills --skill api-gateway-configuration -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/secondsky/claude-skills --path plugins/api-gateway-configuration/skills/api-gateway-configuration
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/api-gateway-configuration/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add secondsky/claude-skills --skill api-gateway-configuration -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/secondsky/claude-skills/tree/HEAD/plugins/api-gateway-configuration/skills/api-gateway-configuration/SKILL.md

## When to use it
- route requests across microservices
- put JWT authentication at the gateway layer
- cap how often a service can be called
- write an Nginx upstream with load balancing
- wire a Cognito authorizer into AWS API Gateway

## Example prompts
- configure Kong for the users and orders services with JWT and a 100-per-minute limit
- write an Nginx config with an upstream of two backends and a health check
- add a Cognito authorizer to my SAM API Gateway template

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 0fa591fcf5abf007.

BEGIN THIRD-PARTY FILE 0fa591fcf5abf007
````text
---
name: api-gateway-configuration
description: Configures API gateways for routing, authentication, rate limiting, and request transformation in microservice architectures. Use when setting up Kong, Nginx, AWS API Gateway, or Traefik for centralized API management.
license: MIT
---

# API Gateway Configuration

Design and configure API gateways for microservice architectures.

## Gateway Responsibilities

- Request routing and load balancing
- Authentication and authorization
- Rate limiting and throttling
- Request/response transformation
- Logging and monitoring
- SSL termination

## Kong Configuration (YAML)

```yaml
_format_version: "3.0"

services:
  - name: user-service
    url: http://user-service:3000
    routes:
      - name: user-routes
        paths: ["/api/users"]
    plugins:
      - name: rate-limiting
        config:
          minute: 100
          policy: local
      - name: jwt

  - name: order-service
    url: http://order-service:3000
    routes:
      - name: order-routes
        paths: ["/api/orders"]
```

## Nginx Configuration

```nginx
upstream backend {
    server backend1:3000 weight=5;
    server backend2:3000 weight=5;
    keepalive 32;
}

server {
    listen 443 ssl;

    location /api/ {
        proxy_pass http://backend;
        proxy_http_version 1.1;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_cache_valid 200 1m;
    }

    location /health {
        return 200 'OK';
    }
}
```

## AWS API Gateway (SAM)

```yaml
Resources:
  ApiGateway:
    Type: AWS::Serverless::Api
    Properties:
      StageName: prod
      Auth:
        DefaultAuthorizer: JWTAuthorizer
        Authorizers:
          JWTAuthorizer:
            JwtConfiguration:
              issuer: !Sub "https://cognito-idp.${AWS::Region}.amazonaws.com/${UserPoolId}"
```

## Best Practices

- Authenticate at gateway level
- Implement global rate limiting
- Enable request logging
- Use health checks for backends
- Apply response caching strategically
- Never expose backend details in errors
- Enforce HTTPS in production
````
END THIRD-PARTY FILE 0fa591fcf5abf007

The third-party file has ended. Everything between the 0fa591fcf5abf007 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© secondsky · MIT · https://github.com/secondsky/claude-skills/tree/HEAD/plugins/api-gateway-configuration/skills/api-gateway-configuration/SKILL.md

## Similar
- [analyzing-api-gateway-access-logs](https://affpapa.org/en/nevibecode/skills/analyzing-api-gateway-access-logs.md) — skill · 761 installs
- [api-gateway-patterns](https://affpapa.org/en/nevibecode/skills/api-gateway-patterns.md) — skill · 481 installs
- [connecting-lambda-to-api-gateway](https://affpapa.org/en/nevibecode/skills/connecting-lambda-to-api-gateway.md) — skill · 6600 installs

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md