Basic Workflow Overview
There are three basic workflows that will involve most users:
- Creating/Ordering Ports
- Creating Connections (buying a service from another)
- Creating Service Profiles (selling a service to others)
For most activities on the ECX FabricECX Fabric is an advanced interconnection solution that improves performance by providing a direct, private network connection, users usually start by ordering one or more ports. This process follows the same structure, regardless of how the port will be used. Buying or selling services, locations (metro, region, etc.), or configuration.
The port is the only component that is currently requested, configured and activated outside of the ECX Fabric portal or APIs.
- The information entered for any profile includes:
- A basic marketing description and name that will appear to potential buyersA buyer is a user who connects to an available service through ECX. A buyer can be an enterprise end customer of the seller service or an aggregator, managed service provider, network service provider or system integrator company that bundles its service offerings with ECX.
- Any technical parameters needed as a pre-requisite or as data entry
- Some metadata that the provider requires from buyers
- Where it will be available on the ECX Fabric using either a list of ports or Routing Instances (depending on the type of service)
For more information on creating profiles specific to the type of interconnection desired, see the sections later in this document.
We also track several other workflows later in this document, such as:
- Approving connection requests as a provider
- Editing Connections and components
- Managing/Viewing components and other ECX Fabric assets
AggregatorsOn Enterprise Cloud Exchange (ECX), aggregators are Network Service Providers (NSPs) and Managed Service Providers (MSPs) who provide multi-tenant services. Aggregators are both buyers of ECX service from Equinix and sellers of value-added services over ECX to their end customers. can choose from one of the two options for managing connections on ECX Fabric.
- Option 1: Resellers manage connections in the ECX Fabric on behalf of their customers. Resellers must have the customer’s Authorization keyThe authorization key typically contains alpha-numeric characters and is a unique identifier authorizing Equinix to provision a connection towards the CSPNote: To Equinix, authorization key is a generic term and is NOT encrypted on ECX. CSPs might use a different name to refer to the same key. For example: Azure ExpressRoute calls the authorization key the “service key” while AWS calls it the “account ID” and other technical information to be able to order connections for their customers.
- Option 2: Resellers enable some or all of their end customers for self-service on ECX Fabric. Resellers must follow steps in the Portal User Guide section about sub-account setup to designate their end customers as sub-accounts, assign ports and set up user access for them to be able to manage their own connections on CXP. The sub-account user’s experience is the same as described in this document and elsewhere, with visibility and activities restricted to those that the reseller allows.