You are writing a Lambda function that fetches messages from an SQS queue, processes the messages and writes the results to a database. The SQS queue and the Lambda function are deployed in the same AWS region. However, when the Lambda function is configured in a VPC, it cannot read messages from the queue. There is no such problem when the Lambda function is not within VPC. How would you quickly resolve the issue?

Answer options:

A.Configure the SQS queue in the same VPC subnet.
B.Modify the SQS security group to allow the incoming traffic from the Lambda function.
C.Create the VPC endpoint for Amazon SQS and modify the Lambda function to use the endpoint.
D.Configure a direct connect link between the Lambda function and the SQS queue.

Correct Answer – C
Option A is incorrect: Because the SQS queue cannot be put in a VPC subnet.
Option B is incorrect: Because Amazon SQS does not have a security group.
Option C is CORRECT: Because with the VPC endpoint of Amazon SQS, the Lambda function can communicate with the SQS queue from the VPC, and the connection is not within the public internet.
Option D is incorrect: Because there is no such network configuration between the Lambda function and SQS queue. The VPC endpoint should be used in this case.
Reference:
https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-sending-messages-from-vpc.html