A public API must limit requests per second for each consumer.
Throttle requests above the limit and manage usage without permanently overprovisioning the backend.
Which architecture is most appropriate?
Configure an API Gateway usage plan and stage or method throttling to control consumer request rates at the API entry point.
Detailed explanation
S3 object lifecycle rules do not control HTTP API request rates.
S3 object lifecycle rules do not control HTTP API request rates.
Usage plans associate quotas and throttling with API keys, allowing API Gateway to limit excess requests before they reach the backend.
Usage plans associate quotas and throttling with API keys, allowing API Gateway to limit excess requests before they reach the backend.
DNS caching does not manage per-consumer API usage or backend throttling.
DNS caching does not manage per-consumer API usage or backend throttling.
Changing permissions is too coarse for safe, continuous request-rate control.
Changing permissions is too coarse for safe, continuous request-rate control.
Check official documentation
Compare the following points with the official documentation.
Amazon API Gateway usage plans and throttlingの公式説明を確認する。
What to confirm
認可と要求レート制御を分離し、スロットリングの適用箇所を説明できる。
Key points
- API Gateway usage plan
- Throttling
- API key
Notes
- Environment:
- Confirm current behavior in the official SAA-C03 guide and AWS service documentation.
Foundation review
Authorization versus traffic control
IAM permission evaluation and request-rate throttling are separate responsibilities.
Capacity and cost
Traffic limits can reduce the need to keep excess backend capacity running.