- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
To access SQS from a Lambda in a VPC, you must either create a VPC endpoint, create a NAT gateway, or manually set a public IP address in the Lambda's ENI.
If you are on a public subnet, it would be easy to set up a VPC endpoint.
https://docs.aws.amazon.com/ja_jp/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-sending-messages-from-vpc.html#create-vpc-endpoint-for-sqs
The answer from Riku_Kobayashi is correct but I'd like to comment on something else in the question:
The endpoint name is sqs.ap-south-1.amazonaws.com
but the error you're getting shows that it is resolving to private IP addresses (10.0.0.69, 10.0.0.39, 10.0.0.53) and that's curious. Do you have anything in your VPC which is acting as a DNS server that is trying to send your traffic to some other endpoint?
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- In che modo posso risolvere i problemi relativi a ReportBatchItemFailures della funzione Lambda SQS?AWS UFFICIALEAggiornata 2 anni fa
But even in Public subnet with IGW and Private With NAT still getting the error
Lambda does not have a public IP address when placed on a public subnet.
So please set up a VPC endpoint for SQS