OESS
IntroductionUser DocumentationOperations ManualAdministration
  • FAQ
  • Provisioning
  • Workgroups
  • Network Entities
  • Cloud Connections

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

  1. Create a new Connection in OESS.
  2. Create an Endpoint to AWS using your AWS Customer Id.
  3. Create an Endpoint to your network.
  4. Create a peer for each created Endpoint.
  5. Save the Connection.
  6. 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.
  7. 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

  1. Create a Partner Interconnect via the GCP web portal. Note the generated Pairing Keys; These are used to create Endpoints within OESS.
  2. Create a new Connection in OESS.
  3. Create an Endpoint to GCP using each Pairing Key mentioned in Step 1.
  4. Create an Endpoint to your network.
  5. Create a peer for each created Endpoint.
  6. Save the Connection.
  7. Return to the GCP web portal and approve the Interconnect.

Microsoft Azure: ExpressRoutes

Workflow Overview

  1. Create an ExpressRoute via the Azure web portal. Note the generated Service Key; This is ued to create Endpoints within OESS.
  2. Create a new Connection in OESS.
  3. Create two Endpoints to Azure using the Service Key mentioned in Step 1.
  4. Create an Endpoint to your network.
  5. Create a peer for each created Endpoint.
  6. 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.

OESS

  • OESS
  • oess-users@globalnoc.iu.edu
  • GlobalNOC
  • iuglobalnoc

The Network Development and Deployment Initiative (NDDI), a partnership between Internet2, Indiana University and others was formed to create a new network platform and complementary software, which together will support global scientific research in a revolutionary new way. The Open Exchange Software Suite (OESS) is the first software product to emerge from this partnership.