Ultimate access to all questions.
Explanation:
Running the Lambda in the VPC using private subnets ensures traffic uses VPC ENIs in private subnets. Referencing the Lambda security group in the Aurora security group grants precise inbound access on the DB port without exposing the cluster. This provides private connectivity with least operational overhead. Interface VPC endpoint for RDS is for control-plane API, not data-plane. Private DNS does not establish routing or permissions. RDS Proxy adds overhead and is unnecessary for basic access.
No comments yet.
Which actions enable private, least-ops connectivity from an AWS Lambda function to an Aurora PostgreSQL cluster in the same VPC? (Choose 2)
A
Create an interface VPC endpoint for Amazon RDS
B
Run the Lambda in the VPC using private subnets
C
Enable private DNS on the Aurora endpoint
D
Reference the Lambda security group in the Aurora security group on the DB port
E
Use Amazon RDS Proxy and connect to the proxy endpoint