-
Hello Khadijah Senian,
Thank you for your question.
While the AWS blog you referenced does mention using Route 53 inbound resolvers for resolving private DNS queries from on-premises networks, this approach introduces additional infrastructure components. The original solution is Configuring an interface VPC endpoint for Amazon API Gateway with private DNS names activated—is the recommended approach because it allows the use of the standard public DNS name for the API, which automatically resolves to private IPs without needing extra infrastructure.
By enabling Private DNS on the interface VPC endpoint, the API endpoint remains private, and DNS resolution for the API will happen seamlessly within the VPC. This method is simpler, avoids unnecessary complexity, and meets the goal of securing private access to the API from on-premises.
For more details, you can refer to the official AWS documentation on private APIs.
I hope this clears up the confusion. Feel free to reach out if you have more questions!
Best,
Irene @ Tutorials Dojo
