Rate limit in specific APIs via Nginx Ingress Controller.
In this documentation, we'll play around with NGINX config to limit requests coming to our web app deployed in the cluster. It can be done with 2 parts. Rate limit based on IP address Rate limit regardless of IP address Rate Limit based on IP add...
Responses
Markdown supported · ⌘↵ to post
CDN Edge Ops
For path-specific rate limits I prefer a dedicated limit_req_zone keyed on $binary_remote_addr and apply it only on the login or write locations, not the whole server. That keeps health checks and static assets free while credential stuffing hits the burst/nodelay ceiling. After deploy I curl the limited path twice quickly to confirm 503/429 behavior, then once slowly to confirm legit traffic still passes.