QuestionQ50

VerifiedNetwork Security, Compliance, and Governance

A company is developing an API-based application on AWS with a microservices architecture. The company uses a multi-account AWS environment, with a separate AWS account for every microservice development team. Each team hosts its microservice in its own VPC, which contains Amazon EC2 instances behind a Network Load Balancer (NLB).

A network engineer must use Amazon API Gateway in a shared services account to create an HTTP API that exposes these microservices to external applications. The network engineer must ensure that access to the microservices occurs only across a private network. In addition, the company must be able to control which entities from its internal network can connect to the microservices. The company will create additional microservices in the future that it must be able to integrate with the application.

What is the MOST secure solution that satisfies these requirements?

Explanation

AWS PrivateLink lets each microservice account expose its NLB as an endpoint service and restrict which principals can create endpoint connections. The shared-services account consumes those services through interface endpoints, whose ENI private IP addresses can be registered as targets of an ALB. An API Gateway HTTP API can use a VPC link to privately integrate with that ALB, while the architecture remains extensible as new endpoint services are added. API Gateway HTTP API private integrations require the API, VPC link, and load balancer to be owned by the same account, so directly linking to the NLBs in the separate microservice accounts is not supported.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!