Explanation:
By default, Lambda functions run in a secure VPC managed by AWS but are not connected to your own VPCs. To enable a Lambda function to access resources inside a private VPC subnet (like the database in this scenario), you must configure the Lambda function to connect to the VPC. This is done by specifying the VPC subnet IDs and security groups when creating or updating the function.
Ultimate access to all questions.
Question 7
A SysOps administrator is re-architecting an application. The SysOps administrator has moved the database from a public subnet, where the database used a public endpoint, into a private subnet to restrict access from the public network. After this change, an AWS Lambda function that requires read access to the database cannot connect to the database. The SysOps administrator must resolve this issue without compromising security. Which solution meets these requirements?
A
Create an AWS PrivateLink interface endpoint for the Lambda function. Connect to the database using its private endpoint.
B
Connect the Lambda function to the database VPC. Connect to the database using its private endpoint.
C
Attach an IAM role to the Lambda function with read permissions to the database.
D
Move the database to a public subnet. Use security groups for secure access.
No comments yet.