A Lambda function must read an Aurora database that is reachable only on private subnets inside the city's VPC. What must the developer configure?
Select an answer to reveal the explanation.
Short Explanation
If the database lives behind the city's locked fence, Lambda has to join that VPC neighborhood—right subnets and security groups—to knock on Aurora's door. Opening Aurora to the public internet, stuffing passwords in the zip, or pretending S3 is Aurora won't give a private DB path.
Full Explanation
To reach private VPC resources such as Aurora on private subnets, attach the Lambda function to appropriate subnets and security groups (accepting ENI and cold-start tradeoffs). Making the database public increases exposure. Packaging credentials without VPC access still cannot reach private endpoints. S3 website hosting is not a substitute for a relational Aurora data plane.