Erik
Reputation: 898
Accessing ECS instances from AWS Lambda running in VPC
I am running a Lambda function in a VPS and have been able to connect to my S3 and RDS resources. However I cannot connect to containers I have running in the VPC through ECS (These containers are exposed to the internet via ELB).
I am aware that accessing the internet via a Lambda function in a VPC requires a managed NAT Gateway (https://aws.amazon.com/blogs/aws/new-access-resources-in-a-vpc-from-your-lambda-functions/) but is it possible to connect to EC2/ECS resources in a VPC without the NAT gateway?
Upvotes: 2
Views: 1362
Answers (1)
Andreas
Reputation: 984
Two options:
- use an internal ELB instead of a internet-facing ELB (http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-internal-load-balancers.html)
- use a NAT Gateway to access the internet-facing ELB
Upvotes: 2
Related Questions
- Why can't an AWS lambda function inside a public subnet in a VPC connect to the internet?
- AWS call Lambda inside VPC to another Lambda in another VPC
- What is the downside of NOT running AWS Lambda functions in a VPC?
- Why can my lambda function not access S3 and SQS when an EC2 instance in the same VPC can?
- AWS Lambda in VPC with RDS and Internet Connection
- AWS VPC with both internet gateway and NAT
- Accessing ECS container from AWS Lambda running in VPC
- Connect to ElastiCache cluster from AWS Lambda function
- AWS Lambda: How to set up a NAT gateway for a lambda function with VPC access