Guided architecture tour · 6–8 min
Reach a service through a private doorway — VPC and Interface endpoints
Plan a private path from an app to a supported AWS service.
This tour teaches architecture decisions. Its services are not provisioned in the emulator.
Your goal
Plan a private path from an app to a supported AWS service.
Why this matters
An app in a private network needs Secrets Manager. You will choose an interface endpoint, make its name reachable, and keep network access separate from permission to read secrets.
Words you will use
An endpoint is a connection point. An interface endpoint uses private network addresses. DNS turns a service name into an address. IAM controls allowed actions.
How to proceed
Read each situation and choose an answer. The lesson explains the result. Try again if needed, then continue through all three decisions and finish the tour.
1. Choose a private route
Your app needs a supported regional service without sending that connection through a public internet path. Choose the suitable VPC feature.
What can provide that service connection?
An interface VPC endpoint for the service.
An interface endpoint provides a private connection to a supported service through AWS PrivateLink. Confirm service and Region support and the endpoint type; not all VPC endpoints use the same design.
The app has a planned private service connection.
App → private endpoint address → supported service2. Make the path usable
The endpoint exists, but requests from the app still fail. Names, security groups, and the chosen subnets can all affect the path. Choose a useful review.
What should you check?
Private DNS and allowed traffic between app and endpoint.
Creating an endpoint is one part of the setup. Check name resolution, endpoint placement, and security group rules for the intended traffic. Test the request from the app’s actual network location.
The private path can be reached and tested.
Service name → endpoint address → permitted connection3. Keep permission separate
The app can connect to the endpoint but cannot read a secret. A reachable network path does not grant permission to retrieve protected data. Choose the next check.
What controls the allowed action?
IAM, resource policies, endpoint policies, and relevant key permissions.
Network access and authorization answer different questions. Review the policies involved in this request and allow only the needed secret actions. A private connection is not permission to read every secret.
The app gets only the access it needs.
Reachable service + authorized action → permitted requestPractice, then check your understanding
In the interactive tour, make each decision before seeing the outcome. Wrong answers receive coaching, and replay gives you a fresh attempt without duplicating earned XP.
Read the official AWS documentation for service behavior and production details.