Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add API rate limiting to our events API #23

Open
glitchedmob opened this issue Nov 29, 2023 · 2 comments
Open

Add API rate limiting to our events API #23

glitchedmob opened this issue Nov 29, 2023 · 2 comments

Comments

@glitchedmob
Copy link
Member

glitchedmob commented Nov 29, 2023

It's possible that our API gateway has an option for this that we can change in our CDK configuration

@KalonOhm
Copy link

KalonOhm commented Nov 29, 2023

Is this even in the ballpark?

-https://stackoverflow.com/questions/71998170/how-do-you-implement-rate-limiting-on-a-serverless-lambda-application

"AWS API gateway is more suited for client credentials oAuth authentication flow for point to point connectivity. It don't provide much features such as rate limiting based on users. You can use lambda authoriser with dynamodb to store user limits and current value and provide rate limiting based on user. There is no feature provided by AWS API gateway for user based limiting."

@glitchedmob
Copy link
Member Author

@KalonOhm sort of. User based rate limiting would be awesome, but I think we could get away with just ip address based rate limiting.

Some followup searches related to what you found is telling me that API Gateway does not support this :(. However AWS WAF (Web Application Firewall) does. It's probably worth some time diving into that service and understanding

  • How much it costs
  • How do we create one using the CDK
  • How do we connect it to our API gateway using the CDK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants