Limit call rate by key in the Consumption tier
The rate-limit-by-key policy prevents API usage spikes on a per key basis by limiting the call rate to a specified number per a specified time period. This is really important feature of api managament and it's not available in Consumption tier.
Added to the backlog.
Alex Maiereanu commented
Last movement on this subject was in 2019. Any updates?
Need this one. What's it's ETA?
Totally agree, this should be able in the Consumption tier also!
Here we are left with only rate-limit, and then one IP is able to consume the whole limit.
This looks like DDOS by design!