7 days in, still can't get anything more than the infinitely seen tutorial GET / request working on a lambda function.

Oh, you've got something more complex, god forbid a POST handler? well, prepare yourself for days of suffering.

how far can you really go from standard software patterns?

Giving it about 20 more minutes and i'm going full self-managed, I don't have time for this shit

λ🤡

What's your deployment strategy(server less/sam/terraform/etc)?

What language are you using?

Are you using API gateway or the new lambda execution URL?

A container with lambda RIE/RIC can speed your development workflow by a far margin: https://docs.aws.amazon.com/lambda/...

@gcavalcante8808 Or he can just write a 10-line lambda function which starts a predefined fargate task by passing inputs from HTTP request as environment variables (or as something else if it better fits the input data, maybe lambda would store the data somewhere and just pass the URI as a variable for the task), and then all other code can be developed and shipped as a regular docker image. But he doesn't want to explain the details about what he's trying to achieve, so fuck do I know...

I've got an express app with a single POST handler that in turn does some stuff with ffmpeg. There are no docs for this (though as I mentioned, infinite "how to run an express GET endpoint that returns some text as a lambda function"). some say "add the whole thing as a zip and lambda just magically knows what to do!" Some say, "no use a whole ubuntu image or similar and go from there!" Sick of the whole thing, I don't have time to fight it.

Another problem is I need to pass form data (part of which includes binary data) to the lambda function and this is nontrivial, at least from all the garbage I've read.

Anyway, I stuck true to my word and I gave up. I had my self-managed server up and working as a backend in about 2 hours.

For me the whole thing should be this simple: if I have a container X exposed at port Y, and POSTing to port Y does Z, I should be able to put that container X as my lambda function image, and POSTing to that lambda function should do Z. Period. No exceptions, no "strange" things or modifications or gotchyas I need to consider for my dockerfile. Yet so far everywhere I have turned and everything I have tried you need to jump through what appear to me to be trivially set hoops that apply to the LaMdA eNvIoRmeNt. what a joke. I'm just disappointed lambda is not at all what i've thought it was. (go figure, shame on me)

The thing is: That’s not how a lambda works, it is much more simple than a microframework; in fact you going to receive an event/message containing all request stuff (method, path, uri, etc) organized in a message (called event).

I would recommend to create a simple lambda using AwS interface in your preferred language and then you explore it: see the signature expected, print the event and context and so on.

The example bellow is just like that:

https://github.com/awsdocs/...