Using your guidance Ive managed to get mine working thanks :) FYI the Ref from the SQS resource holds the URI for the queue so you can just export that by itself and dont have to wrangle the string in the handler or library. Thanks again
I do. Ive got an internal wiki article that I'm going to turn into a gist and publish in the next 24 hours. I'll link it back here. Ive upgraded 14 services to use SQS this way in the last day so am fairly comfortable with it
Thanks for the video, does the SQS message get automatically deleted from the SQS queue once processed by the lambda? What happens if the processing fails for any reason (run time exception for example), I would the expect the message to be invisible for the visibilityTimeOut period and then becomes visible again and trigger another instance of the lambda
Great explanation! Thank you very much. Could we take some information such as the queue name you have imported in the handler from the environment variables?
Hi, i have a query. I have a single lambda function which is triggered by sqs standard queue and the event source is cloudwatch. I am sending message to sqs through cloudwatch which is then triggering lambda and my lambda is getting failed so i m retrying it for 3 times and send it to DLQ. Now my question is if the message id will be same for that single message or with every retry message id will change because message body is same but i am getting 2 message id's with same message.
My queues and functions are not showing up in my console, but I'm also not getting any errors and everything works as expected in the CLI and postman. I can create queues through the console, but my queues created via CLI are not showing up in the console. Are their permissions I should double check? I'm using a federation account if that makes a difference.
Have a issue stranger, I follow all steps but when exexute the resource of API gateway always response me: 502 Bad Gateway { "message": "Internal server error" } On CloudWatchLog aren't print none message using console.log.
interesting sqs pronunciation "es coo es", later you pronounce queue properly... ES cue ES is correct... sqs === ES CUE ES or s queue s... good lesson thanks for the content!!
Hello World :D This video helps me a lot! Thank you so much. Can you please make a video of something like this but using a post method? I just wonder how to pass the request body of my api to the next lambda that i will be triggering. Hoping for your response :D
Using your guidance Ive managed to get mine working thanks :) FYI the Ref from the SQS resource holds the URI for the queue so you can just export that by itself and dont have to wrangle the string in the handler or library. Thanks again
good point! have you an example?
Auto-response:
functions:
test-sqs:
handler: handler.testSqs
events:
- http:
path: test-sqs
method: get
cors: true
environment:
AWS_QUEUE_URL:
Ref: TestSqsHello
I do. Ive got an internal wiki article that I'm going to turn into a gist and publish in the next 24 hours. I'll link it back here. Ive upgraded 14 services to use SQS this way in the last day so am fairly comfortable with it
medium.com/@brunowatt/implementing-sqs-in-serverless-the-right-way-a416f73e94da
Bruno Watt awesome!
I will check it now. thanks! 👍🏿👍🏿
I was just reseaching this and you posted !!!!
Thanks for the video, does the SQS message get automatically deleted from the SQS queue once processed by the lambda?
What happens if the processing fails for any reason (run time exception for example), I would the expect the message to be invisible for the visibilityTimeOut period and then becomes visible again and trigger another instance of the lambda
Awesome! Thanks!
Our pleasure!
Great! thank you very much!
That was a nice explanation!
Great explanation! Thank you very much. Could we take some information such as the queue name you have imported in the handler from the environment variables?
Ow! I could see the tips in the video. Yes, it's pretty cleaner having that info in environment variables.
Hi, i have a query. I have a single lambda function which is triggered by sqs standard queue and the event source is cloudwatch. I am sending message to sqs through cloudwatch which is then triggering lambda and my lambda is getting failed so i m retrying it for 3 times and send it to DLQ. Now my question is if the message id will be same for that single message or with every retry message id will change because message body is same but i am getting 2 message id's with same message.
Great video, thanks for sharing, are you able to provide a link to the code?
github.com/mavi888/sls-sqs-test
My queues and functions are not showing up in my console, but I'm also not getting any errors and everything works as expected in the CLI and postman. I can create queues through the console, but my queues created via CLI are not showing up in the console. Are their permissions I should double check? I'm using a federation account if that makes a difference.
are u checking the right region in your console?
🔥 Hello, I was wondering maybe you could make a firebase storage for videos, like a course video app, I see no tutorials online
Can I use Python to write it?
python is supported by lambda so yes
@@foobar_codes Thank you.
Awesome
Do someone know if we can use a DynamoDB Stream to SQS without passing from a Lambda function?
Have a issue stranger, I follow all steps but when exexute the resource of API gateway always response me:
502 Bad Gateway
{
"message": "Internal server error"
}
On CloudWatchLog aren't print none message using console.log.
i have same problem
Omg thank you so much, you just save my arse on this 😂😂
interesting sqs pronunciation "es coo es", later you pronounce queue properly... ES cue ES is correct... sqs === ES CUE ES or s queue s... good lesson thanks for the content!!
hahaha english is hard :P
Hello World :D
This video helps me a lot! Thank you so much.
Can you please make a video of something like this but using a post method? I just wonder how to pass the request body of my api to the next lambda that i will be triggering.
Hoping for your response :D
You can check my free course on serverless there is some examples on how to use post www.udemy.com/introduction-to-serverless-aws/
TY u help me get a job hahaha
Code like a girl =)
You are cute. Love u