A company has five VPCs in us-east-1. An internal web app runs in us-east-1. VPC-A must connect to an external partner's AWS environment in the same Region; the partner's VPC is VPC-B. Both VPC-A and VPC-B use the same IP range, so the company's EC2 instances in VPC-A cannot directly reach the partner's application. The solution must not disrupt either party's existing environment. Which two actions should the network engineer take? (Choose two.)

The correct actions leverage AWS PrivateLink to establish private connectivity without overlapping IP address concerns. The partner creates a VPC endpoint service in VPC-B, fronted by a Network Load Balancer (NLB), which exposes their application. The company then creates a VPC endpoint in VPC-A, connecting to this shared service. This allows instances in VPC-A to access the partner's application in VPC-B using private IP addresses, bypassing the overlapping CIDR blocks. VPC peering is not suitable because it requires non-overlapping CIDR blocks. Adding a secondary CIDR block to both VPCs and using a NAT gateway would be complex and disruptive, requiring re-IPing resources or complex routing. A Site-to-Site VPN is designed for connecting on-premises networks to AWS VPCs, not for VPC-to-VPC communication within the same region, and would also face routing challenges with overlapping CIDRs.