Cloud Connections
OESS | User Documentation | Cloud Connections
OESS supports provisiong connections to AWS, Microsoft Azure, and Google Cloud Platform. As provisioning for each cloud is slightly different, use the videos in this section to setup your cloud enabled endpoints.
Amazon Web Services: Hosted Connections
Workflow Overview
- Create a new Connection in OESS.
- Create an Endpoint to AWS using your AWS Customer Id.
- Create an Endpoint to your network.
- Create a peer for each created Endpoint.
- Save the Connection.
- Under the Connections pane in the AWS Direct Connect console, select the newly created Hosted Connection and choose View details. Select the confirmation check box and choose Accept connection.
- Create a Virtual Interface to use on the Hosted Connection, and configure the Hosted Connection’s Endpoint in OESS to enabling peering between AWS and OESS.
Google Cloud Platform: Partner Interconnects
Workflow Overview
- Create a Partner Interconnect via the GCP web portal. Note the generated Pairing Keys; These are used to create Endpoints within OESS.
- Create a new Connection in OESS.
- Create an Endpoint to GCP using each Pairing Key mentioned in Step 1.
- Create an Endpoint to your network.
- Create a peer for each created Endpoint.
- Save the Connection.
- Return to the GCP web portal and approve the Interconnect.
Microsoft Azure: ExpressRoutes
Workflow Overview
- Create an ExpressRoute via the Azure web portal. Note the generated Service Key; This is ued to create Endpoints within OESS.
- Create a new Connection in OESS.
- Create two Endpoints to Azure using the Service Key mentioned in Step 1.
- Create an Endpoint to your network.
- Create a peer for each created Endpoint.
- Save the Connection.
Note: If manually configuring peer addresses, Azure expects a
/30
for both the primary and secondary Endpoints. The first address
will be used by the peer and the second will be used by Azure. For
example, if 192.168.100.248/30
is used, 192.168.100.249/30
will be
used by the peer and 192.168.100.250/30
will be used by Azure.