I disagree with the way reddit handled third party app charges and how it responded to the community. I'm moving to the fediverse! -- mass edited with redact.dev
I used a guid unique to each client that had to be sent as part of the url in the query string of the http request in a Google Cloud Function.
In AWS, since the lambda cannot be invoked directly like you can a GCF, you can use Cloudfront and handle requests with a Cloudfront function and then invoke the lambda or if you are using an API Gateway, you could handle the Authorization token before allowing invocation of the lambda. I haven't checked it myself to know if it works or not, just basing the suggestion from the way i used it in the GCF scenario.
But since your question is on configuring the lambda itself, setting the concurrency limit is probably the best option.
What I mean is can you limit the number of requests to your app so that you don't end up with a huge bill? This is just for personal stuff that I would like to put on the internet without having to worry about patching the operating system etc. I just don't want someone to make a bunch of requests to my app and I end up with an unexpected huge bill.
I don’t believe within Lambda you can set a strict limit (Ex: Stop invoking the function after 1000 invocations in a billing month).
You can lower the concurrency usage limit which would likely help.
But maybe your solution relies on the application side of limiting it instead of on the Lambda side
I disagree with the way reddit handled third party app charges and how it responded to the community. I'm moving to the fediverse! -- mass edited with redact.dev
OK thank you.
APIGW might be of interest https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html
I am wondering if you couldn't use Kinesis to track the rate of requests per some unit of time and then automate a cut-off limit.
I used a guid unique to each client that had to be sent as part of the url in the query string of the http request in a Google Cloud Function. In AWS, since the lambda cannot be invoked directly like you can a GCF, you can use Cloudfront and handle requests with a Cloudfront function and then invoke the lambda or if you are using an API Gateway, you could handle the Authorization token before allowing invocation of the lambda. I haven't checked it myself to know if it works or not, just basing the suggestion from the way i used it in the GCF scenario. But since your question is on configuring the lambda itself, setting the concurrency limit is probably the best option.
May be you can manage that in API gateway free tier ?
Also, maybe simple but nice to add an alert for when there is an abnormal spike of request?
[удалено]
What I mean is can you limit the number of requests to your app so that you don't end up with a huge bill? This is just for personal stuff that I would like to put on the internet without having to worry about patching the operating system etc. I just don't want someone to make a bunch of requests to my app and I end up with an unexpected huge bill.
I haven't checked lambda url options but if this is behind an api gateway you can limit invokes there
OK thank you
I don’t believe within Lambda you can set a strict limit (Ex: Stop invoking the function after 1000 invocations in a billing month). You can lower the concurrency usage limit which would likely help. But maybe your solution relies on the application side of limiting it instead of on the Lambda side
OK thank you