HN Explorer

14 comments

[ 2.8 ms ] story [ 39.1 ms ] thread
markonen
The big deal here is that ALB doesn’t cost $3.50 per million requests like the API Gateway does.
avitzurel
I think what this is solving is that in case you already have an ALB, you can have a route rule that will direct traffic to lambda. That's pretty powerful.
nodesocket
Does this also means you can use a custom domain now to invoke a lambda function? Maybe this was possible before using API gateway, I may be confusing with Google Cloud Functions.
zedpm
You were always able to use a custom domain with Lambda, via API Gateway, just like you can now via ALB.
colmmacc
Yes! you can do this with ALB, or also with Lambda@Edge. You can also use ACM with both to create and renew a certificate for your custom domain.
davewritescode
Anyone know if ALB supports custom authentication lambdas? That's one of the big features that's keeping us on API Gateway.
xmly
Why not move the Auth to the code instead? Add one middleware just.
renke1
Good point, if you do authentication in your code manually (like verifying a JWT issued by Cognito) you could also directly invoke the Lambda from your client and completely forgo ALB saving even more money (at the cost of slightly increased complexity, that is).
luhn
AFAICT they don't.

I haven't looked at the details of Lambda Layers yet, but I wonder if they might help with this? Build an authentication layer that you can bundle with all your ALB Lambdas.

xmly
Great! I do not like API Gateway complex setting anyway

haha

cheeseburgerj
Can also do Private VPC invocation of Lambda through this without the stuffing around with private API gateway and VPC Endpoints

good stuff