Rate limiting controls how many requests a client or source can make during a defined interval. It is a server-side defense: it protects an API from aggressive retries, abusive traffic, and requests that could overwhelm the system. section 10.2 section 11.3.1
Enforce limits at the API Gateway, the entry point between external clients and backend services. The gateway can reject excessive requests before they reach services such as authentication, keeping this defense out of core business logic. section 11.3.1
Rate limiting supports perimeter defense in several ways:
- Drop malicious traffic before it reaches internal services and adds load. section 11.6
- Combine with other layers, such as a web application firewall and account lockouts, rather than relying on a single defense. section 11.2.2
A login burst
If one IP address attempts to log in 500 times in a minute, the API Gateway can drop those requests before they reach the authentication service. section 11.3.1


















