a6-plugin-limit-req

Configure Apache APISIX limit-req plugin for leaky bucket rate limiting.

1|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/moonming/a6 --skill a6-plugin-limit-req
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a6-plugin-limit-req
Source: https://github.com/moonming/a6/tree/main/skills/a6-plugin-limit-req
Command: npx skills add https://github.com/moonming/a6 --skill a6-plugin-limit-req

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps manage and control the rate of incoming requests to your Apache APISIX services, preventing overload and ensuring smooth traffic flow using the limit-req plugin.

Core Features & Use Cases

  • Leaky Bucket Rate Limiting: Apply sustained request rates with configurable burst capacity.
  • Traffic Smoothing: Delay excess requests instead of rejecting them immediately to protect upstream services.
  • Distributed Limiting: Utilize Redis for shared rate limiting across multiple APISIX nodes.
  • Use Case: Configure a route to allow a maximum of 100 requests per second per IP address, with a burst capacity of 50, ensuring that sudden traffic spikes are handled gracefully without overwhelming your backend.

Quick Start

Use the a6-plugin-limit-req skill to create a route with a rate limit of 10 requests per second and a burst of 5.

Frequently Asked Questions about a6-plugin-limit-req

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

FAQPage Schema
How do I configure rate limiting in Apache APISIX?

You can configure rate limiting in Apache APISIX by applying the limit-req plugin to a route, setting a per-second rate, and defining a burst capacity to control incoming request flow.

How does leaky bucket rate limiting handle traffic spikes?

Leaky bucket rate limiting smooths traffic by delaying excess requests rather than rejecting them immediately, allowing configurable burst capacity to handle sudden spikes without overwhelming upstream services.

Can I apply distributed rate limiting across multiple APISIX nodes?

Yes, you can apply distributed rate limiting across multiple APISIX nodes by configuring the limit-req plugin to use Redis, which shares rate limit state across your deployment.

What is the difference between rate and burst in APISIX limit-req?

The rate parameter sets the sustained allowed requests per second, while burst defines the maximum capacity for excess requests that can be delayed or queued before being rejected.

Do I need Redis to use the limit-req plugin for traffic shaping?

You do not need Redis for single-node traffic shaping, but Redis is required for distributed rate limiting to synchronize request counters and burst capacity across multiple APISIX instances.