Q: 7
A company has a VPC that has no internet access and has the private DNS hostnames option
enabled. An Amazon Aurora database is running inside the VPC. A security engineer wants to use
AWS Secrets Manager to automatically rotate the credentials for the Aurora database. The security
engineer configures the Secrets Manager default AWS Lambda rotation function to run inside the
same VPC that the Aurora database uses. However, the security engineer determines that the
password cannot be rotated properly because the Lambda function cannot communicate with the
Secrets Manager endpoint.
What is the MOST secure way that the security engineer can give the Lambda function the ability to
communicate with the Secrets Manager endpoint?
Options
Discussion
C. saw a similar question on a practice test and interface endpoints were the right fit for Secrets Manager access inside a private VPC. Not 100% if it's always the case for every service, but makes sense here.
C
B . Both gateway and interface endpoints come up a lot, but I recall gateway VPC endpoints being used for S3 and DynamoDB, so figured B should work for Secrets Manager too. Seems secure since it keeps things internal to AWS. Not totally confident though, maybe someone else can clarify if Secrets Manager needs interface instead.
D imo, a lot of people pick A by mistake but IGW would expose the VPC way more than needed. Interface endpoint (C) is the private/internal solution for Secrets Manager, not NAT or gateway.
C
C for sure. Interface VPC endpoint (AWS PrivateLink) lets Lambda hit Secrets Manager over private IPs, no internet or NAT needed. Pretty sure that's the AWS recommended way.
A is wrong, C. Interface endpoints (PrivateLink) are the secure method for Lambda in a private VPC to reach AWS services like Secrets Manager without exposing anything to the public internet. NAT or IGW would add unnecessary risk imo.
Option C
B or C? Had something like this in a mock and picked B because gateway endpoint is often used for private AWS service connections, especially S3. But now not as sure, maybe Secrets Manager needs interface type instead. Anyone else recall details?
Probably C. is the only type of endpoint that works for Secrets Manager, since it's not a gateway service.
Be respectful. No spam.