A company is migrating a new application from an on-premises data center to a new VPC in the AWS Cloud. The company has multiple AWS accounts and VPCs that share many subnets and applications. The…

Question

Options

• ASet up a VPC peering connection for each VPC that needs access to the new application VPC.
• BDeploy a transit gateway in the account that hosts the new application. Share the transit gateway
• CUse an AWS PrivateLink endpoint service to make the new application accessible to other VPCs.
• DUse an Application Load Balancer (ALB) to expose the new application to the internet. Configure

• A
  3% (1)
• B
  12% (4)
• C
  82% (28)
• D
  3% (1)

Explanation

AWS PrivateLinkis the most suitable solution for providing fine-grained access control while allowing multiple VPCs, potentially across multiple accounts, to access the new application. This approach offers the following advantages: Fine-grained control: Endpoint policies can restrict access to specific services or principals. No need for route table updates: Unlike VPC peering or transit gateways, AWS PrivateLink does not require complex route table management. Scalable architecture: PrivateLink scales to support traffic from multiple VPCs. Secure connectivity: Ensures private connectivity over the AWS network, without exposing resources to Why Other Options Are Not Ideal: VPC peering is not scalable when connecting multiple VPCs or accounts. Route table management becomes complex as the number of VPCs increases.Not scalable. While transit gateways provide scalable VPC connectivity, they are not ideal for fine-grained Transit gateways allow connectivity but do not inherently restrict access to specific applications.Not ideal for fine-grained access control. Exposing the application through an ALB over the internet is not secure and does not align with the requirement to use private network resources.Security risk.

No community discussion yet for this question.