Review Set 1 Question 42

[Sue]

The solution explanation for option “Create AWS PrivateLink interface VPC
endpoints to route training data and model checkpoints to S3 and
internal services” states that “interface VPC endpoints are not used to connect to Amazon S3. S3 typically requires gateway VPC endpoints for private access”.

However, you can provision interface VPCs via PrivateLink: https://docs.aws.amazon.com/AmazonS3/latest/userguide/privatelink-interface-endpoints.html

I think options 1 and 5 overlap.

[Lois-TutorialsDojo]

Hello Sue,

Thank you for bringing this up.

Upon reviewing the official AWS documentation, you are correct that interface VPC endpoints (via AWS PrivateLink) can be used for accessing Amazon S3. However, the preferred method for accessing S3 privately is by using a gateway VPC endpoint (Option 1). Gateway endpoints are designed specifically for services like Amazon S3 and DynamoDB, providing a simple, efficient, and cost-effective solution. They are integrated with your VPC’s route tables, ensuring private access to S3 without the need for an internet gateway or NAT device.

While interface VPC endpoints are valid and can be used for certain use cases (e.g., cross-region access or connecting on-premises networks), they are generally not the first choice for standard S3 access due to higher complexity and cost.

Thank you for raising this. We’ve flagged the question for review and will update it based on the official AWS documentation. We appreciate your feedback, as it helps improve our materials!

Regards,

Lois @ Tutorials Dojo