Topic lessonTopic: Connecting VPCs and investigating traffic
AWS PrivateLink service sharing: provider and consumer responsibilities
Choose the service you want consumers to reach. Trace an NLB-backed API and distinguish provider approval, consumer networking and application permissions.
Trace an NLB-backed API and distinguish provider approval, consumer networking and application permissions.
This fictional case requires no AWS account or live connection.
Choose the endpoints and the service they expose
With this type of endpoint service, the provider uses a Network Load Balancer and the consumer creates an interface endpoint.
- Consumer app → Consumer endpointResolve the name
- Consumer endpoint → Provider entryUse the approved connection
- Provider entry → Provider APIReach the selected target
- Consumer app
- Audit API name
- Consumer endpoint
- Interface endpoint
- Provider entry
- Endpoint service NLB
- Provider API
- Audit response
Evaluate connection and API permissions separately
| Item | Observation | Responsibility |
|---|---|---|
| Connection request | Pending acceptance | Provider checks approval conditions |
| Consumer DNS | Returns endpoint addresses | Consumer checks intended name |
| Synthetic API request | 200 with expected content | Confirm path and application permissions |
| Admin database | No endpoint service for it | Outside this service share |
PrivateLink provides connectivity to the endpoint service. Check who may connect and what the API permits separately.
Identify the right owner before changing scope
Record the two sides. Provider checks the NLB, service name, authorized principals and connection status. Consumer checks endpoint, subnets, DNS and network controls.
Validate more than name resolution. Include endpoint acceptance and optional private DNS, then verify a permitted synthetic operation reaches the intended API.
Keep the shared surface bounded. Treat management access as its own requirement and scope review.
Check the worked example
Choose an option to see the result and explanation.
Check, then explain in your own words
- Draw provider and consumer endpoints.
- Check connection status and DNS separately.
- Verify the synthetic API outcome.
Check your understanding: Does endpoint acceptance authorize API operations?
Check endpoint connectivity and API authorization separately.
The application still decides which operations the caller can perform.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsProvider endpoint services and consumer interface endpoints.
Used in this lessonChoose the endpoints and the service they expose Evaluate connection and API permissions separately Identify the right owner before changing scope