M6 DC and endpoint P1

Direct connect

Doesn't support multicast

Doesn't come with redundancy

Can order Active- active

or active passive

Type of interface

image

  1. virtual interface

to access servce in AWS

2 type

Public virtual interface

Private virtual interface

LAG

can aggregate 4 direct connect port into single connection

All conection are active active

/It is available as 1G/10G

for S3 access

Direct Connect GW

for VPC access

to connect multiple VPC in same or diff region

Global resource

can connect VPC from diff account

click to edit

requirement

click to edit

To use AWS Direct Connect in an AWS Direct Connect location, your network must meet one of the

following conditions:

• Your network is colocated with an existing AWS Direct Connect location. For more information about

available AWS Direct Connect locations, see AWS Direct Connect Product Details.

• You are working with an AWS Direct Connect partner who is a member of the AWS Partner Network

(APN). For information, see APN Partners Supporting AWS Direct Connect.

• You are working with an independent service provider to connect to AWS Direct Connect.

In addition, your network must meet the following conditions:

• Your network must use single-mode fiber with a 1000BASE-LX (1310 nm) transceiver for 1 gigabit

Ethernet or a 10GBASE-LR (1310 nm) transceiver for 10 gigabit Ethernet.

• Auto-negotiation for the port must be disabled. Port speed and full-duplex mode must be configured

manually.

• 802.1Q VLAN encapsulation must be supported across the entire connection, including intermediate

devices.

• Your device must support Border Gateway Protocol (BGP) and BGP MD5 authentication.

• (Optional) You can configure Bidirectional Forwarding Detection (BFD) on your network. Asynchronous

BFD is automatically enabled for AWS Direct Connect virtual interfaces, but does not take effect until

you configure it on your router.

Must create virtual interface

you need 1 one private virtual interface to connect to each VPC

direct connect gateay

image

to connect to multiple VPC

requirement

Must support BGP

single Mode1000LX

vpc endpoint

Interfacd endpoint

● For each interface endpoint, you can choose only one subnet per Availability
Zone. Endpoints are supported within the same region only.

GW endpoint

click to edit

A gateway that is a target for a specified route in your route table, used for traffic destined to a supported AWS service.

● You can create multiple endpoints in a single VPC, for example, to multiple services. You can also create multiple endpoints for a single service, and use different route tables to enforce different access policies from different subnets to the same service.

You can modify the endpoint policy that's attached to your endpoint, and add or remove the route tables that are used by the endpoint.