Which solution will meet these requirements?

By:
On:
In: SAA-C02
Tagged:
With: 0 Comments
An application running on an Amazon EC2 instance in VPC-A needs to access files in another EC2 instance in VPC-B.Both are in separate AWS accounts.The network administrator needs to design a solution to configure secure access to EC2 instance in VPC-B from VPC-A.The connectivity should not have a single point of failure or bandwidth concerns.

Which solution will meet these requirements?

Set up a VPC peering connection between VPC-A and VPC-B.

Set up VPC gateway endpoints for the EC2 instance running in VPC-B.

Attach a virtual private gateway to VPC-B and set up routing from VPC-A.

Create a private virtual interface (VIF) for the EC2 instance running in VPC-B and add appropriate routes from VPC-A.

Explanations:

VPC peering allows private, secure, and high-bandwidth connections between VPCs across different AWS accounts. It avoids single points of failure and supports full traffic.

VPC gateway endpoints are only for accessing AWS services within the same VPC, not for inter-VPC communication between instances in separate VPCs.

Virtual private gateways are used for VPN connections to on-premises networks, not for inter-VPC communication between instances in different VPCs.

Private VIFs are used for Direct Connect to connect AWS to on-premises networks, not for direct inter-VPC communication between AWS instances.

Leave a Reply

Your email address will not be published. Required fields are marked *

10 − seven =