A development team has deployed a microservice using AWS Lambda. The function is associated with private subnets in a custom VPC so it can securely access an internal Amazon Aurora MySQL database. Additionally, this function must send transaction logs to a public SaaS logging endpoint. While the database operations are performing correctly, all attempts to connect to the external SaaS endpoint result in timeout errors. How can this connectivity issue be resolved?
- Set up a NAT Gateway within a public subnet, and update the route table of the private subnets to forward traffic destined for 0.0.0.0/0 to the NAT Gateway.Cevap
- BAssociate the function with the public subnets of the VPC and enable the auto-assign public IP setting on those subnets.
- CAdd a route in the route table of the private subnets that routes all traffic destined for 0.0.0.0/0 directly to the VPC's Internet Gateway.
- DIncrease the function's execution timeout to the maximum limit and modify the code to initialize the database connection pool globally outside the handler function.
Cevap
Set up a NAT Gateway within a public subnet, and update the route table of the private subnets to forward traffic destined for 0.0.0.0/0 to the NAT Gateway.
For a Lambda function associated with a VPC to access the public internet, it must be placed in private subnets with a route to a NAT Gateway in a public subnet. The NAT Gateway then forwards the traffic to the Internet Gateway. This allows the Lambda function to maintain connectivity to both the internal database (via local VPC routing) and the external endpoint.
Adım Adım Çözüm
Anahtar Kavram
VPC networking for AWS Lambda functions requiring internet access