2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Lambda functions do not accept inbound connections. When you configure a VPC and security group for a Lambda function, this is for the purposes of allowing the Lambda function to execute within your VPC, allowing the function to access other services within the same VPC (e.g. RDS or Aurora instances, EC2 instances, load balancers, etc).
Lambda functions access SQS using the SQS API. You only need to ensure that the security group provides (at a minimum) outbound access on port 443 so that it can connect to SQS.
0
Please take a look at my answer to a similar question recently - https://repost.aws/questions/QUA-ke4GYcQx6-YNvmHxsfUA/can-lambdas-inside-a-private-subnet-still-receive-data-from-sqs#ANzEFlBd5wQ02DlAOAuszeoA
Contenus pertinents
- demandé il y a 6 mois
- demandé il y a 6 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
Is there a way to find the SQS service IP address? Or any way to limit the SG to confirm that it only can send outbond access to port 443 on SQS?
Thay way I do not have to allow the access to 0.0.0.0/0?