Multiple API keys and the flow rate limit in the usage plan

Question

I associate an API with a usage plan and multiple API keys with the usage plan.  
In addition, I set the flow rate limit in the usage plan.  
When the API is executed using an API key and the request exceeded error (429 error) occurs, if the API is executed using another API key, does the request exceeded error (429 error) occur?

Accepted Answer

> According to this answer, if multiple clients execute the same API using different API keys, the flow rate can't be limited by the total number of requests to the API, right?  
  
Not with usage plans, no.  
  
> I want to realize a per-API flow rate limit instead of a per-client flow rate limit.  
  
Unfortunately we do not support API level throttling rates today. We do support method level throttling rates that would be global to all callers. These can be used in addition to usage plan throttling.  
  
Regards,  
Bob

Answer

Thanks for answering.  
  
According to this answer, if multiple clients execute the same API using different API keys, the flow rate can't be limited by the total number of requests to the API, right?  
I want to realize a per-API flow rate limit instead of a per-client flow rate limit.

Answer

Hello:  
  
Usage plan limits are applied per key. Keys within the same plan do not share the limit.  
  
Hope this clarifies.  
  
Regards,  
Bob

Answer

It seems now we can throttle by endpoint: https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-throttling.html

> Route-level throttling
You can set route-level throttling to override the account-level request throttling limits for a specific stage or for individual routes in your API. The default route throttling limits can't exceed account-level rate limits.

Multiple API keys and the flow rate limit in the usage plan

Relevanter Inhalt