Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by WrtCdEvrydy on Tuesday December 01, 2020 @02:10PM
(#25268637)
To be honest, if it's a static site and you just need a little bit of compute... Cloudfront in front of S3 and lambda is probably the cheapest way to give someone a basic website (just a contact form and nothing else)
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by Pfhreak on Tuesday December 01, 2020 @02:30PM
(#25268850)
This is my go to stack these days for personal projects. (That said, I'm a former AWS dev, so I'm super familiar with these moving parts.)
It's easy to develop for, it's easy to automate deployments, I don't have to worry about keeping anything up to date, and I can just focus on the small amount of code I want to write.
The most expensive thing is the Route 53 configuration at $0.50/month/domain.
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by madoublet on Tuesday December 01, 2020 @02:48PM
(#25269051)
I love this stack. I recently added AWS SAM to the mix as well so that I can automate deployments. I have always wondered why Route 53 was so expensive relative to the other services. I have a collection of low traffic sites that I run for local businesses and this is always the most expensive part. I guess it's hard to complain about $0.50. But, given I could probably run them all on $5 DO droplet, it ends up costing a little more.
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by vagab0nd on Tuesday December 01, 2020 @04:01PM
(#25269850)
It's my goto stack as well. However, I haven't been able to get both www->root redirect and http->https redirect working. Do you happen to know if it's possible?
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by klohto on Tuesday December 01, 2020 @07:34PM
(#25271955)
www->root should be handled on DNS, therefore Route53.
http->https can be done using CloudFront and Lambda@Edge
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by munns on Tuesday December 01, 2020 @02:06PM
(#25268594)
Yes, you are still limited to 15 minute maximum duration.
- Chris Munns - Lead of Dev Advocacy - Serverless@AWS
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by danpalmer on Tuesday December 01, 2020 @02:09PM
(#25268619)
Ok that's not too bad a cap. I can see that working for quite a lot of use cases that aren't serving websites.
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by rainforest on Tuesday December 01, 2020 @02:45PM
(#25269016)
Is there any potential for extending that limit? I work on a product that uses Fargate Spot as a kind-of lambda substitute to run longer-duration tasks consumed from SQS and being able to use lambda to do that would make life easier :)
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by JoshTriplett on Tuesday December 01, 2020 @03:10PM
(#25269287)
Likewise. Doesn't have to be indefinite; 1-2 hours would be wonderful.
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by remify on Wednesday December 02, 2020 @05:08AM
(#25275043)
For a 1 hour process why not just launch an instance ? You can also probably use a spot instance to be even cheaper.
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by JoshTriplett on Wednesday December 02, 2020 @04:40PM
(#25282007)
Instances take longer to start up; Lambda processes requests in milliseconds or less. Lambda automatically manages a pool for you.
If you're running a predictable process and you know how long it'll take in advance, an instance may make sense. If you're running an unpredictable process, where you won't know how long it'll take until it's done, and it might be quite fast, the low startup time and fine-granularity billing helps.
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by spullara on Tuesday December 01, 2020 @02:28PM
(#25268824)
GPUs please.
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by panabee on Tuesday December 01, 2020 @03:13PM
(#25269319)
oracle plans to ship serverless GPUs in Q12021, according to our oracle rep. hope this means amazon and google are close as well.
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by ignoramous on Tuesday December 01, 2020 @02:43PM
(#25268985)
fly.io (upto 8CPUs + 8GiB) and stackpath.com (upto 8CPUs + 32GB) both can run such workloads at the Edge. That said, AWS Fargate and AWS Batch (minus the Edge) are probably comparable services to those than AWS Lambda.
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by austinpena on Tuesday December 01, 2020 @11:02PM
(#25273112)
Are you familiar with stackpath? Does anyone have words to share about them?
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by ignoramous on Friday December 04, 2020 @04:20AM
(#25300481)
StackPath is kind of edge-essential services from Cloudflare and AWS rolled into one.
I used StackPath's Serverless functions once before and they worked as advertised (but since moved to Cloudflare Workers).
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by austinpena on Friday December 04, 2020 @03:31PM
(#25307426)
Thanks for the response. I’m currently using them and liking them. Not as sexy as CF workers but I can have 100 delivery domains per site so my customers can point at me for essentially free.
Re:AWS Lambda – Functions with Up to 10 GB of Memory and 6 V...
by bpodgursky on Tuesday December 01, 2020 @02:10PM
(#25268635)
ECS (potentially on Fargate) would be a reasonable stack for those tasks, given the 15 minute limit on Lambdas.
However, I've seen many things that run a couple of times a day, or in response to a deployment, or things like that, which often need some compute behind them, but for which setting up a little server and hosting it somewhere just to call it once a day feels like so much unnecessary ceremony.
Does this have a maximum function duration? If so this could still rule out this approach.