Sending SQS message timeout

Question 1

I wrote an AWS lambda function in NodeJs that pulls id’s off a database and queues them onto a AWS SQS queue. I had it working fine until I deployed a function to receive the messages and now the original function is not working. Here is the relevant code:

    async function sendHelper(rows)
    {
        let i;
        let params;
        let res;
        let sqs = new AWS.SQS({apiVersion: '2012-11-05'});
        for (i = 0; i < rows.length; i++) { 
            params = {
                MessageBody: rows[i].ID.toString(),
                QueueUrl: 'https://sqs.' + process.env.AWS_REGION_NAME + '.amazonaws.com/' + process.env.AWS_ID_SHORT + '/' + process.env.SQS_VENDPERSON_QUEUE_NAME
            };

            res = await sqs.sendMessage(params).promise().catch(err => errorHandler(err));

            console.log(res);
        }

        return null;
    }

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

async function sendHelper(rows)

{

let i;

let params;

let res;

let sqs = new AWS.SQS({apiVersion: '2012-11-05'});

for (i = 0; i < rows.length; i++) {

params = {

MessageBody: rows[i].ID.toString(),

QueueUrl: 'https://sqs.' + process.env.AWS_REGION_NAME + '.amazonaws.com/' + process.env.AWS_ID_SHORT + '/' + process.env.SQS_VENDPERSON_QUEUE_NAME

};

res = await sqs.sendMessage(params).promise().catch(err => errorHandler(err));

console.log(res);

}

return null;

}

The issue is that it isn’t throwing an error anywhere. It just times out on the first sendMessage no matter how long you give it. I have since removed the message receiving function and the issues persists. Some additional info that might help is I have been using serverless to deploy.

Question 2

You didn’t include the rest of your lambda function but I assume your database instance is in a VPC. If so, you need to:

Place your lambda inside your VPC
Set up a VPC endpoint for SQS or NAT gateway (depending on whether you just need to access SQS only or also need to access the internet).

Key note (that I learned the hard way): When you add your lambda function to a subnet, make sure you ONLY add it to the private subnets, otherwise nothing will work.

It is going to take quite a bit of tinkering to get right, but it is doable. Here are some relevant docs:

https://docs.aws.amazon.com/lambda/latest/dg/vpc.html

and

https://aws.amazon.com/premiumsupport/knowledge-center/internet-access-lambda-function/

Sending SQS message timeout

Question:

Answer:

Leave a Reply Cancel reply