My lambdas need access to a DB and SQS. The DB is connected to my default VPC through peering. So I placed my lambdas in the VPC as well. They can access the DB, but timeout when accessing SQS. The security group allows all traffic in and out.
I'm using .NET Core 6 and the AWSSDK.SQS package.
I tried adding a VPC Endpoint to SQS, but when I do that, EC2 instances can no longer communicate with SQS and this causes Elastic Beanstalk deployments to not update deployed EC2 instances. What can I do to give my lambdas access and not break other things?
AWS Services. Services:com.amazonaws.us-east-1.sqs. VPC:<my only vpc>. Subnets:<all checked. all public>. Security groups:default (all traffic enabled). Policy:Full Access. -- Just tried it again. Lambda can now reach SQS, but EB cannot deploy to instances. Under the hood, the instances (via cdn-hup) poll an SQS queue to know when to deploy an update. The service timeouts trying to access whatever it is accessing.