About Subscriptions

The subscription is the service your solution is associated with, and from which data is passed to and from. Users can subscribe to a service that has been defined and is active by way of a service profile.. The name is typically aligned with a cloud, software, security, network or other recognizable service with whom the user has a relationship.

When users request a subscription from a Routing Instance (RI) to a profile, the ECX FabricECX Fabric is an advanced interconnection solution that improves performance by providing a direct, private network connection orchestrator executes a set of import and export statements between all eligible RIs in the transaction:

On the subscriber side, this is typically a single RI. On the provider side, it could be more than one RI. A subscription automatically interjects import-export route statements, and users on either side don't get to customize this option. However, users can add other services to limit or filter these routes.

Example: An easy way to create basic sell-side redundancy in a service profile is to have redundant RIs in a single metro both be part of the profile:

You might see subscriptions to your RIs that don't belong to your account. These are users who have subscribed to your service. Although you can't make edits to these instances as you would to your own, the component is exactly the same. You will see many elements of the subscription, including the subscriber’s account name.

A subscription requires the following parameters:

  • Routing Instance - select an eligible RI where the subscription terminates

  • Service - choose a service from the list of eligible names

    • A single RI might not have more than one subscription to the same service provider

    • The list of eligible services might include that are reachable remotely, and the user indicates which metro or region they wish to subscribe to in the Location field, when relevant

  • Subscription name - this defaults to [RI name] to [service name] but the user can enter any desired value as long as it's unique to their account and that metro

  • Conditional - if the provider of the service requires a unique identifier of some type, it will be labeled and require you to enter the ID you received from them

  • Notifications - the email address where we send notifications about this component

Optional Services

The following optional services are available on the Subscription component:

  • Dedicated connector - This allows a user to select a connector from any that are associated to the RI, and that connector will be dedicated to only passing the routes for this subscription back and forth. It allows for better isolation and additional settings that will only apply to the services on this specific subscription

    • A connector is available if it's not already dedicated to another subscription, and if it's not the only connector remaining to pass traffic for other existing subscriptions

    • There must be an available connector on the same RI this subscription is associated with, in order to select the service

Tip: If you already have other subscriptions on the RI and you dedicate the last or only connector to a new subscription, you will inadvertently isolate that traffic, because there will no longer be a connector available for all other non-dedicated subscriptions.

Here's an example of when a user decides to (or is mandated to) dedicate a connector to the Green service that they've subscribed to. The remaining connector is for Yellow and any other non-dedicated subscriptions.

  • Perform network address translation (NAT) - This service allows the user to define traffic that will be NATted before it's advertised to the specified provider associated with this subscription. This is an optional service, but might be required to subscribe to some providers, is useful when using private addressing on your RI, and can streamline other functions

    • A network can advertise addresses outside the NAT block, but they might be denied or treated differently by some providers that are subscribed

    • Some applications might not function properly with NAT, and the user is responsible for ensuring proper operations with that provider’s specification.

    • This feature NATs all traffic bound for a provider; the user might not define specific blocks from the provider

Limitations