AWS SQS + Lambda | Setup | Integration | Trigger Lambda via SQS

I am going to demonstrate how we can integrate Lambda function with SQS and trigger lambda function using SQS.
Amazon Simple Queue Service (Amazon SQS) is a distributed message queuing service.
It supports programmatic sending of messages via web service applications as a way to communicate over the Internet.
SQS is intended to provide a highly scalable hosted message queue that resolves issues arising from the common producer-consumer problem or connectivity between producer and consumer.
Supports - Standard Queue and FIFO queue
Lambda function: • AWS Lambda function | ...
EC2 Tutorial: • AWS Cloud EC2 introduc...
AWS Complete tutorial - • AWS Cloud EC2 introduc...

[@sudhirdeshmukh3601]

Very good content and explained simply.

[@Jennielync]

Thank you, please make more videos!

[@maYYidtS]

well explained...
can I use SQS in my use case...like
I have a requirement to auto start an EC2 when a user got uploaded file in S3. for this I have created Lambd function and add a S3 event notification trigger in lambda...it is working fine, and auto starting as well and with a basic function I'm stoping EC2 when the instance process got finished.
But the problem is...before stoping EC2 if user upload other file in s3...I want notification sould hold till EC2 stop, once the EC2 stoped second notification will pass to lambda then EC2 starts again...

[@rashmikagawade9574]

Awesome and simple video :)

[@umabharati9911]

Thanks for the video, can u also explain how to do this cross account?

[@bhupathivarma9170]

I too have similar requirement please share if u find any relevant info pls

[@biggbosstelugu8252]

Good content

[@heenaahuja651]

I am facing issue with the api gateway integration with SQS. can you please help me with it. I want to write the serverless.yml mentioning the integration of api gateway with SQS. (in this case while creating the API GATEWAY THE CODE SHOULD BE SUCH WHICH SHOULD HAVE INTEGRATION TYPE AS SQS).
Please let me know how this can be done. ?????

[@ashishbansod2036]

Hey need clarity on visibility timeout, it is the time in which other consumers will not be able to see that message.

[@KashishPandey07]

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. Could you halp me in this?

[@manodavidson]

Hi, I have the similar requirement, could you please share your findings, it will be a of great help.

[@KashishPandey07]

@@manodavidson if the cloudwatch is the triggering event for lambda then check the rule and make it 5min, so you can disable the cloudwatch as soon as you get the logs in lamba. I don't remember exactly bt i think my trigger event was less than 5min that's why lambda was invoked multiple times before i could disable it. Try this once.

[@manodavidson]

@@KashishPandey07 Thanks a ton, can you help me with the second part of my question which is to move my messages back from dead-letter queue to source-queue, there is are 2 findings by me but I don't find them conventional, which is 1) to make your source queue as dead-letter-queue of the original dead-letter queue and 2) was using exponential algorithm using python which I'm not familiar with.
Thank you in advance.