AWS Lambda pricing now per ms

Re:AWS Lambda pricing now per ms by jthomerson on Tuesday December 01, 2020 @01:57PM (#25268503)

Chris, while I've seen the change in my accounts on regular Lambda, I don't yet see it on Lambda@Edge. I think Lambda@Edge is the place where we'd benefit from this change the most, because many L@E scenarios take single-digit milliseconds, and the cost of L@E is 3x regular Lambda.

Any word on whether we'll also see this change on L@E billing?

[ Parent | on HN ]

Re:AWS Lambda pricing now per ms by munns on Tuesday December 01, 2020 @02:00PM (#25268526)

Yes, to be clear this change was just for Lambda. L@E is honestly a completely different service run by a different part of AWS that just happens to share parts of our core worker platform. I am not 100% aware of when they might adjust their own pricing on this, but also couldn't share any roadmap here (sorry).

[ Parent | on HN ]

Re:AWS Lambda pricing now per ms by daxfohl on Tuesday December 01, 2020 @02:18PM (#25268722)

How does that even work? Lambda seems like a challenge even with the entirety of the datacenter resources to work with. Running it in constrained edge environments with a VM per function seems like black magic.

[ Parent | on HN ]

Re:AWS Lambda pricing now per ms by munns on Tuesday December 01, 2020 @02:53PM (#25269102)

The naming is a bit of a misnomer, today L@E doesn't run at the edge (in our PoPs) but when you deploy it copies to every region and then CloudFront routes you to the lowest latency region for your request.

[ Parent | on HN ]

Re:AWS Lambda pricing now per ms by austinpena on Tuesday December 01, 2020 @04:12PM (#25269952)

So is L@E multi region then? Like if I have two concurrent requests across the globe are they serviced from two locations?

[ Parent | on HN ]

Re:AWS Lambda pricing now per ms by munns on Tuesday December 01, 2020 @04:28PM (#25270162)

Yes, but you deploy it from one region.

[ Parent | on HN ]