11–19 of 19 posts
Nice things scalability, not taking down the site if there is a segfault, and cost. Can run a smaller webserver and PAYG on the functions overall it costs less.
It is a lot cheaper than a "proxy as a service".
The functionality was so small and temporary it was great to be able to not need to provision anything and not even pay (our usage is under the free tier).
The regex to deal with error handling and API GW in general were pretty clunky. The Lambda was a self contained and unit/integration tested Java project.
I'm using it as a proxy with IP rotation. It is not a perfect solution, but solved my problem more than one time. It is a lot cheaper than a "proxy as a service".
I'm using it as a proxy with IP rotation. It is not a perfect solution, but solved my problem more than one time. It is a lot cheaper than a "proxy as a service".
I thought lambda was configured to use a single exit IP that rotates every 4 hours. How many IP's are you getting via this method, and are you using any tricks (multiple accounts, etc) to get a wider variety of IPs?
I have a toy service with ~200k requests/day to a public service and I was blocked all the time.
After I changed to use API Gateway + Lambda as a proxy, never had these problems again. I just monitor the 4xx and 5xx errors and they are almost zero now.
I've been using it for lots of things lately. The last thing was to process ebs volumes that get left behind when leostream deletes instances from it's pools. (we need fresh machines all the time, so that's why we delete these instead of re-using) We have it delete the machine from the pool, and the ami is set to not delete the volume. I use a cloudwatch event to detect this, spin up a new ec2 instance, attach the av…
I used AWS Lambda with API Gateway to provide a single API endpoint allowing other services to exchange authentication keys for new tokens. The functionality was so small and temporary it was great to be able to not need to provision anything and not even pay (our usage is under the free tier). The regex to deal with error handling and API GW in general were pretty clunky. The Lambda was a self contained and unit/int…