Once you have created an AWS Direct Connect connection, how can you start working with connecting to resources in your VPC and other public resources? Choose 2 answers from the options given below.
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - B and D.
The AWS documentation mentions the following.
After you have placed an order for an AWS Direct Connect connection, you must create a virtual interface to begin using it.
You can create a private virtual interface to connect to your VPC, or you can create a public virtual interface to connect to AWS services that aren't in a VPC.For more information on AWS Direct Connect getting started, please refer to the below URL:
http://docs.aws.amazon.com/directconnect/latest/UserGuide/getting_started.htmlWhen you create an AWS Direct Connect connection, you can use it to connect to resources in your VPC and other public resources. To achieve this, you can create one or more virtual interfaces (VIFs), which are logical connections between your Direct Connect connection and your resources. VIFs can be either private or public, depending on whether they are connected to private or public resources.
To start working with connecting to resources in your VPC and other public resources, you can create a private virtual interface and a public virtual interface.
A. Create a VPC Peering Connection: VPC peering enables you to connect two VPCs together over a Direct Connect connection. With VPC peering, you can establish a private, low-latency connection between VPCs in different regions or different AWS accounts. However, this option is not relevant for connecting to public resources.
B. Create a Private Virtual Interface: A private virtual interface enables you to connect to private resources in your VPC over a Direct Connect connection. When you create a private virtual interface, you specify the VPC and the VPC's CIDR block that you want to connect to. Once the private virtual interface is created, you can associate it with a Direct Connect gateway or a Virtual Private Gateway to route traffic between the VPC and your on-premises network.
C. Create a PrivateLink Connection: AWS PrivateLink enables you to securely access services hosted on AWS over a Direct Connect connection, without using public IPs, NAT devices, VPN connections, or firewall rules. With PrivateLink, you can access services like Amazon S3, Amazon EC2, and Amazon Kinesis directly from your VPC over a private connection.
D. Create a Public Virtual Interface: A public virtual interface enables you to connect to public resources over a Direct Connect connection. When you create a public virtual interface, you specify the AWS public service that you want to connect to, such as Amazon S3 or Amazon EC2. Once the public virtual interface is created, you can use it to route traffic to the public service over the Direct Connect connection.
Therefore, the correct options to connect to resources in your VPC and other public resources are: B. Create a private virtual interface D. Create a public virtual interface.