SAA-C03 ยท Network security in the VPC
VPC endpoints and PrivateLink
Gateway endpoints (S3, DynamoDB) versus interface endpoints powered by PrivateLink, endpoint policies and exposing a service privately to other VPCs.
Key points
- VPC endpoints: private subnets reach AWS services without internet gateway or NAT.
- Gateway endpoint: only S3 and DynamoDB; prefix-list route in chosen route tables, no PrivateLink, no extra cost.
- Interface endpoint: AWS PrivateLink, network interface with private IP per subnet; many AWS services, partner or own services.
- Endpoint policy: resource-based, default full access.
- Your own service: Network Load Balancer + endpoint service.
Source: https://docs.aws.amazon.com/vpc/latest/privatelink/gateway-endpoints.html
Practice questions
Which AWS services can be reached through a gateway VPC endpoint?
- Amazon S3 and Amazon SQS
- Amazon S3 and Amazon DynamoDB
- Amazon DynamoDB and AWS KMS
- Every AWS service in the Region
Show answer
Answer: B. Amazon S3 and Amazon DynamoDB
Gateway endpoints are available only for Amazon S3 and Amazon DynamoDB. Other services, such as SQS or KMS, are reached privately through interface endpoints.
Which statements describe interface VPC endpoints?
- They are powered by AWS PrivateLink
- They create a network interface with a private IP in each chosen subnet
- Consumers use them to connect to a provider's endpoint service
- They work by adding a prefix-list route to your route tables
- They are available only for Amazon S3 and DynamoDB
Show answer
Answer: A. They are powered by AWS PrivateLink, B. They create a network interface with a private IP in each chosen subnet, C. Consumers use them to connect to a provider's endpoint service
Interface endpoints are powered by AWS PrivateLink, place a network interface with a private IP in each subnet you choose, and are what consumers create to reach someone else's endpoint service. Prefix-list routes in route tables belong to gateway endpoints, and interface endpoints cover many services, not just S3 and DynamoDB.
Gateway endpoints for Amazon S3 are built on AWS PrivateLink, just like interface endpoints.
Show answer
Answer: False
False. Gateway endpoints do not use PrivateLink; they work through route table entries that point the service's prefix list at the endpoint. Only interface endpoints (and the endpoint services behind them) are PrivateLink-based.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
