Every time you configure a queue as an event source for a Lambda function, we create pollers to read from the queue and invoke the function when there are messages. If you configure two queues with the same function, we will create two sets of pollers to read from these queues and invoke the function. Each one of these pollers will scale independently so you will need to have enough Lambda concurrency in your account to accommodate for the higher concurrency.
The Behavior is described in the "Scaling and Processing" Section.
It describes that you have at a max 1k processes reading from a Queue and hand over the Batches to your function. With more than one Queue feeding the function you will have more parallel Lambda executions, so take care of your Lambda Limits.
SQS Not Sending Message to Queueasked 5 months ago
Config for lambda internal queue batch sizeasked 6 months ago
How can I prevent an Amazon SQS message from invoking my Lambda function more than once?EXPERTasked a year ago
boto3 sqs receive_message MaxNumberOfMessagesasked 6 days ago
Multiple SQS queue to same Lambdaasked 8 months ago
SNS to Lambda vs SNS to SQS to LambdaAccepted Answerasked a year ago
At what point is an AWS SQS queue overkill as a Lambda function's source?asked 9 months ago
Large number of unaccounted for SQS requestsAccepted Answerasked 3 years ago
Can't Create SQS Queue From Docker-based LambdaAccepted Answerasked 4 months ago
SQS batching S3 events issueasked 10 months ago