A developer needs to configure an AWS Lambda function to make HTTP POST requests to an internal application. The application is in the same AWS account that hosts the function. The internal application runs on Amazon EC2 instances in a private subnet within a VPC. Which solution will meet these requirements?
Select an option, then click Submit answer.
Reference / correct answer:
Attach the Lambda function to the VPC and to the private subnet.
Most accepted answer: B. Attach the Lambda function to the VPC and to the private subnet.
Community votes: B=2, D=1
Selected Answer: B When your Lambda function needs to access resources within a VPC, such as Amazon EC2 instances in a private subnet, you need to configure the Lambda function to run within that VPC. This is done by specifying the VPC, subnet(s), and security group(s) in the Lambda configuration. Once attached to the VPC and subnet, the Lambda function can make HTTP requests to the internal application running on the EC2 instances in the private subnet. upvoted 5 times
Selected Answer: B Lambda functions do not have fixed IP addresses, making it impractical to add them to a route table upvoted 1 times
Selected Answer: D Lambda Function logs request information (e.g., timestamp, processing time, status) using the default logging mechanism. Create custom CloudWatch metrics in a specific namespace based on these logs. upvoted 1 times YUICH 1 year, 7 months ago Sorry I changed my opinion. The answer is B. Lambda functions do not have fixed IP addresses, making it impractical to add them to a route table. Instead, attaching the Lambda function to the VPC and configuring security groups appropriately is the recommended approach. upvoted 3 times ...
Sorry I changed my opinion. The answer is B. Lambda functions do not have fixed IP addresses, making it impractical to add them to a route table. Instead, attaching the Lambda function to the VPC and configuring security groups appropriately is the recommended approach. upvoted 3 times