3
Simple rate limiting for almost all services needed ?!
Source: supabase/supabase#36512 · opened by @mrtncode
Hello, I am surprised that there is no real rate limiting for almost all services? As far as I know, there are no real rate limits for DB operations. But the much bigger problem is that there is no rate limit for either Supabase storage or Supabase edge functions. If I understand this correctly, it is therefore easy for a hacker to completely use up the free bandwidth of Supabase storage in a short time. And the free invocations can also be gone very quickly. Or am I mistaken? As far as I understand it, you can rate limit the edge functions with redis itself but the invocations are still charged, right?
I see this as a huge problem. Maybe I'm wrong and I'm worrying unnecessarily, but at the moment the whole thing seems really unsafe to me and leads to high bills. Of course, you can restrict it with a pay limit, but then my customers will no longer have access to the services afterwards. 🙁
I see this as a huge problem. Maybe I'm wrong and I'm worrying unnecessarily, but at the moment the whole thing seems really unsafe to me and leads to high bills. Of course, you can restrict it with a pay limit, but then my customers will no longer have access to the services afterwards. 🙁
No pledges yet. Be the first to back this.
Comments
Similar requests
SMS rate limiting requests/feedback
2 votes · 0 comments
Auth Rate Limits by email address (or Supabase user ID) instead of by IP address
4 votes · 0 comments
Add rate-limiter at project level for client side requests like 120 request/min
1 vote · 0 comments
Rate limits on postRest or graphql
31 votes · 0 comments
supabase Storage: custom rate limits
1 vote · 0 comments
No comments yet.