INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Trace an NLB-backed API and distinguish provider approval, consumer networking and application permissions.

Prerequisite

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.

From a consumer to the shared API
From a consumer to the shared API1: Consumer app — Resolve the name — Consumer endpoint. 2: Consumer endpoint — Use the approved connection — Provider entry. 3: Provider entry — Reach the selected target — Provider API123Consumer appConsumer endpointProvider entryProvider APIFrom a consumer to the shared API1: Consumer app — Resolve the name — Consumer endpoint. 2: Consumer endpoint — Use the approved connection — Provider entry. 3: Provider entry — Reach the selected target — Provider API123Consumer appConsumerendpointProvider entryProvider API
  1. Consumer app → Consumer endpointResolve the name
  2. Consumer endpoint → Provider entryUse the approved connection
  3. 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

A provider owns an audit API and an admin database. Only the audit API is shared.
ItemObservationResponsibility
Connection requestPending acceptanceProvider checks approval conditions
Consumer DNSReturns endpoint addressesConsumer checks intended name
Synthetic API request200 with expected contentConfirm path and application permissions
Admin databaseNo endpoint service for itOutside 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.

What does the consumer create in this setup?
Read the answer and reason

Answer: An interface endpoint · The consumer creates an endpoint to connect to the service.

The connection is pending acceptance. Where to look first?
Read the answer and reason

Answer: Provider connection status and authorized principal · Inspect the acceptance conditions for the endpoint service.

Does reaching the API prove that the admin database is reachable?
Read the answer and reason

Answer: Database reachability is unverified · The observed path ends at the shared API.

Check, then explain in your own words

  1. Draw provider and consumer endpoints.
  2. Check connection status and DNS separately.
  3. 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.