Just as a note in 7:51 the runtime handler is not the name of the function entry point, but the name of the executable generated by go build command. For example if you run "go build something" the runtime handler must be "something".
@fuexfollets5755 Жыл бұрын
Your series is easily the best guide for aws lambda dn cognito usage. You talk clearly and detailed. Your tutorials are also very fast which helps a lot.
@anhtramnguyen2469 Жыл бұрын
good video, quick to the point. Thanks!
@brianmmdev Жыл бұрын
Glad it was helpful!
@sergeyagronov96502 жыл бұрын
the handler name is the file name, not the function name like u mentioned in 8:00
@sherifhmdy Жыл бұрын
exactly it's the binary file name generated from the build command I believe. But anyway thanks a lot @Brian you helped me to create my first lambda function.
@jeanjacquesbarros Жыл бұрын
Thank you! I was trying to run my lambda but I gave some errors, this video helped me a lot!
@roberto_camp Жыл бұрын
Good stuff Brian!
@brianmmdev Жыл бұрын
Appreciate it!!!
@MrTixey4 ай бұрын
Great video! Thanks. Please, if it's possible update moment when you select GO1.x. AWS has changed list
@keerthanas1877 Жыл бұрын
While Test the file it shows calling the invoke Api action failed with signature expaired
@KevinArellano Жыл бұрын
I followed your tutorial except the AWS console part. I just used Terraform since I very much dislike point and click lol. Great video though!!!
@brianmmdev Жыл бұрын
Glad it helped
@VijayChintapandu9 ай бұрын
Hey I couldn't find the Go in supported languages list. How can I find go in that list. there are Java, Node.js and Python versions. Please help me
@VijayChintapandu9 ай бұрын
go it.. it's listed as OS-only runtimes
@sudarsan333 Жыл бұрын
Thanks bro..this video help me very much
@hanzladev2 жыл бұрын
Great video, keep up the good work ✨🎉
@brianmmdev2 жыл бұрын
Thank you so much!
@XfazXtudo Жыл бұрын
Such a great channel ! Thanks for the video Could you make one for AWS gateway proxy with gin ? Couldn't find an updated one
@DarshitGandhi-d4n Жыл бұрын
How can I pass parameters such as bucket name, path etc
@brianmmdev Жыл бұрын
If you're using an S3 event, you'd want to replace the event param with `s3Event events.S3Event`. I do this in my side project, you can see more here: github.com/GuardianForge/guardianforge.net/blob/0f6b41f1bcf28830557510496f8d3ea19939d06e/backend/stack/s3-handlers/create-og-image/main.go#L52C35-L52C57
@thisisreallyme3130 Жыл бұрын
@BrianMorrison Lambda "Test" returned "fork/exec /var/task/main: exec format error: PathError null" when I built with v1.17 or v1.20. Log Events said "INIT_START Runtime Version: go:1.v15". OK I understand that, but.. How are you using v1.17 under Lambda in 2022, when in 2023 the steps in the video cause AWS to look for v1.15? Did you also customize something in Lambda (allowing 1.17) which wasn't covered here?
@brianmmdev Жыл бұрын
Nothing funny going on that wasn't covered. Maybe it's a regional thing? What region are you trying to deploy to?
@sravyadamera9090 Жыл бұрын
same with me . Did u find any solution?
@sravyadamera9090 Жыл бұрын
Let me know if u know solution for this error
@diegorocha2186 Жыл бұрын
This problem is because in 7:51 he says that the handler name should be the name of the function entry point "main", but in reality it is the name of the executable generated after the go build process. For example if you create a go project named "lambda-something" and inside it you run "go build" the executable name is "lambda-something" so that is the name you should put in the runtime handler not main.
@adairhz2 жыл бұрын
Hey there! When I try to run my program locally, I get the following error: expected AWS Lambda environment variables [_LAMBDA_SERVER_PORT AWS_LAMBDA_RUNTIME_API] are not defined. I find this weird since the AWS Lambda documentation does not mention any env variables with these names, nor mentions this configuration step at any point. I already tried googling for it but I got no answers. Do you know if there's something I'm missing? Thanks in advance!
@brianmmdev2 жыл бұрын
That is strange... honestly to do local testing, I use AWS SAM which kinda takes care of that logic. You might find some answers here: docs.aws.amazon.com/toolkit-for-vscode/latest/userguide/welcome.html