Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

Update aws-properties-apitgateway-stage-methodsetting.md #781

Closed
wants to merge 1 commit into from

Conversation

takanabe
Copy link

@takanabe takanabe commented Sep 9, 2020

According to https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html, ThrottlingBurstLimit is defined as follows:

In API Gateway, the burst limit corresponds to the maximum number of concurrent request submissions that API Gateway can fulfill at any moment without returning 429 Too Many Requests error responses.

the burst limit does not define the maximum number of requests per second but at any moment . This means API Gateway returns 429 when it receives more requests during a millisecond time-window than the value of ThrottlingBurstLimit. So, the current explanation of ThrottlingBurstLimit is not accurate and a replacement with accurate documents make sense.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

According to https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html, `ThrottlingBurstLimit` is defined as follows:

>In API Gateway, the burst limit corresponds to the maximum number of concurrent request submissions that API Gateway can fulfill at any moment without returning 429 Too Many Requests error responses.

the burst limit does not define the maximum number of requests **per second** but **at any moment** .  This means API Gateway returns 429 when it receives more requests during a millisecond time-window than the value of `ThrottlingBurstLimit`.  So, the current explanation of `ThrottlingBurstLimit` is not accurate and a replacement with accurate documents make sense.
@rachfop rachfop changed the base branch from master to main October 15, 2020 22:44
@takanabe
Copy link
Author

Let me close this issue since I don't think this PR will be merged... Please open this PR if necessary.

@takanabe takanabe closed this Jan 21, 2021
@takanabe takanabe deleted the patch-1 branch January 21, 2021 07:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants