Build SQS-based applications without the boilerplate. Just define a function that receives an SQS message and call a callback when the message has been processed.
npm install sqs-consumer --save
const Consumer = ;const app = Consumer;app;appstart;
done(err)with an error object will cause the message to be left on the queue. An SQS redrive policy can be used to move messages that cannot be processed to a dead letter queue.
batchSizeoption detailed below.
By default the consumer will look for AWS credentials in the places specified by the AWS SDK. The simplest option is to export your credentials as environment variables:
export AWS_SECRET_ACCESS_KEY=...export AWS_ACCESS_KEY_ID=...
If you need to specify your credentials manually, you can use a pre-configured instance of the AWS SQS client:
const Consumer = ;const AWS = ;AWSconfig;const app = Consumer;app;appstart;
Creates a new SQS consumer.
queueUrl- String - The SQS queue URL
region- String - The AWS region (default
handleMessage- Function - A function to be called whenever a message is received. Receives an SQS message object as its first argument and a function to call when the message has been handled as its second argument (i.e.
attributeNames- Array - List of queue attributes to retrieve (i.e.
['All', 'ApproximateFirstReceiveTimestamp', 'ApproximateReceiveCount']).
messageAttributeNames- Array - List of message attributes to retrieve (i.e.
batchSize- Number - The number of messages to request from SQS when polling (default
1). This cannot be higher than the AWS limit of 10.
visibilityTimeout- Number - The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request.
waitTimeSeconds- Number - The duration (in seconds) for which the call will wait for a message to arrive in the queue before returning.
authenticationErrorTimeout- Number - The duration (in milliseconds) to wait before retrying after an authentication error (defaults to
sqs- Object - An optional AWS SQS object to use if you need to configure the client manually
Start polling the queue for messages.
Stop polling the queue for messages.
Each consumer is an
EventEmitter and emits the following events:
||Fired when an error occurs interacting with the queue. If the error correlates to a message, that error is included in Params|
||Fired when an error occurs processing the message.|
||Fired when a message is received.|
||Fired when a message is successfully processed and removed from the queue.|
||None||Fired when the consumer finally stops its work.|
||None||Fired when the queue is empty (All messages have been consumed).|