<p>I'm looking to use annotations like below for rate limiting for DDOS protection</p>
<pre><code>nginx.ingress.kubernetes.io/limit-connections: &quot;50&quot;
nginx.ingress.kubernetes.io/limit-rps: &quot;10&quot;
nginx.ingress.kubernetes.io/limit-rpm: &quot;100&quot;
nginx.ingress.kubernetes.io/limit-burst-multiplier: &quot;20&quot;
</code></pre>
<p>My question:
These solutions rate limit by IP Address.</p>
<p>Could there be situations where many users (proxy) under one IP address and therefore many users get the one set of rates and thus it affects there usage?</p>
<p>Or is it really one user per IP address?</p>
<p>thanks</p>

Adam
<p>Nginx ingress uses the <code>A leaky bucket, FIFO queue</code> for the rate-limiting.</p>
<p>Nginx ingress has some limitations like :</p>
<ul>
<li>Requests are counted by <strong>client IP</strong>, which is not accurate. Not much useful when you want rate-limiting by user identity.</li>
<li>It is not easy to monitor rejected requests</li>
</ul>
<p>By using this you can stop a certain amount of requests it's not accurate you can try with POC.</p>
<p>There is one nice article on rate limiting with Nginx : <a href="https://medium.com/titansoft-engineering/rate-limiting-for-your-kubernetes-applications-with-nginx-ingress-2e32721f7f57#:%7E:text=When%20we%20use%20NGINX%20ingress,configure%20rate%20limits%20with%20annotations.&amp;text=As%20an%20example%20above%2C%20the,qps" rel="nofollow noreferrer">https://medium.com/titansoft-engineering/rate-limiting-for-your-kubernetes-applications-with-nginx-ingress-2e32721f7f57#:~:text=When%20we%20use%20NGINX%20ingress,configure%20rate%20limits%20with%20annotations.&amp;text=As%20an%20example%20above%2C%20the,qps</a>)%20on%20the%20Hello%20service.</p>
