1 Answer
- Newest
- Most votes
- Most comments
1
Hi,
You are right, http api does not have usage plans out of box, while as rest api type does instead.
You would need a handle it yourself. I would take inspiration from the built-in usage model and build it for your api. You could store the limits for your customers in a database(dynamo).
Then each time an api is called, you would check whether the rate limit is passed for a customer, if so the api would throw a 4xx error.
If limit is still below threshold, increment the limit counter.
You could implement those check in different flavors such as Lambda@edge, or api gateway backed by a step function with lambda steps performing the check and counter increments.
Hope this ideas can inspire you
Relevant content
- asked 2 years ago
- asked 7 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago