Lambda functions have a publicly accessible URL-based invocation. While I’ve put some restrictions on access through HTTP headers, I worry still that a malicious actor could drive up my request counts so that I get charged lots of $$$. What’s to prevent this? I don’t want to jump to the next plan level automatically.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| How to prevent background-function spamming | 2 | 1585 | January 7, 2022 | |
| Functions abuse prevention | 3 | 4146 | July 20, 2020 | |
| Locking down netlify function | 3 | 521 | March 2, 2020 | |
| [Support Guide]: How to apply Access Control for Netlify Functions? | 2 | 6690 | February 17, 2024 | |
| Is there a Rate Limiter for serverless functions? | 28 | 1052 | April 11, 2024 |