Cloud Connect

The order and provisioning process for Microsoft Azure ExpressRoute contains the following steps:

1. The customer creates an ExpressRoute resource in their own Azure domain, which generates a service-key which is shared with NL-ix
2. NL-ix uses the service-key to 'accept' the ExpressRoute on our ports and state which VLAN is used for this connection
3. The VLAN information is configured on the relevant (customer) ports and the information is shared with the customer.
4. The customer sets up the correct BGP Peering in order to create a working connection.

For AWS, NL-ix serves as the Transport provider for the Direct Connect service. In short the process is like this:

1. The customer orders a Direct Connect at AWS, stating to which AWS locations they want to connect. For each Direct Connect, the customer gets a LOA.
2. The LOA is sent to NL-ix, which we sent through to the relevant datacenter to connect to our infrastructure.
3. NL-ix makes sure that a VLAN is configured over the created connection, from the demarcation with AWS towards the customer port.
4. The customer sets up the correct BGP Peering in order to create a working connection.

For AWS, NL-ix offers dedicated connections of 1 Gbps, 10 Gbps, and 100 Gbps ports.
Hosted connections are not supplied by NL-ix.

The main differences between a hosted and a dedicated connection lies in the Virtual Interfaces (VIFS). When you have a Direct Connect you must configure Virtual Interfaces to enable access to AWS services. A Hosted Direct Connect supports one (1) VIF. If you have more than one VPC’s in AWS you will need multiple Hosted Direct Connects to access these multiple VPC’s. A Dedicated Direct Connect supports 50 or 51 (in case of a VPC Transit Gateway) and therefore can be more efficient. Each VIF communicates with one VPC.

AWS Direct Connect supports Private VIF’s for communication with your private cloud environment(s) in AWS and Public VIF’s for access to public services such as Amazon S3.

The order and provisioning process for Oracle Cloud FastConnect contains the following steps:

1. The customer orders a FastConnect in the Oracle Cloud domain, which generates a OCID which is shared with NL-ix
2. NL-ix uses the OCID to 'accept' the FastConnect, state to which Oracle Ramp-up port this FastConnect is connected and determine the transport VLAN.
3. The VLAN is configured on the relevant (customer) ports and the information is shared with the customer.
4. The customer sets up the correct BGP Peering in order to create a working connection.

The order and provisioning process for Google Partner Interconnect follows the following steps:

1. The customer orders a Google Partner Interconnect (VLAN-attachment) in the Google Cloud domain, which generates a 'pairing-key' which is shared with NL-ix
2. NL-ix uses the 'pairing-key' to create a working VLAN-attachment, and determine the transport VLANs.
3. The VLAN is configured on the relevant (customer) ports and the information is shared with the customer (or can be found in the Google Cloud overview)
4. The customer sets up the correct BGP peering in order to create a working connection.