The subscription defines the service your solution will be associated with and pass data to and from. A user “subscribes” to a service that has been defined and is active by way of a service profile by choosing it by name. The name is typically aligned with a cloud, software, security, network or other recognizable service with whom the user has a relationship.
When a subscription is requested from an RI to a profile, the ECX 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; but on the provider side, it could be more than one. A subscription automatically interjects import/export route statements between all, and users on either side do not get to customize this option. However, users can add other services to limit or filter these routes.
Implementation 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:
When a user subscribes to your service, they will automatically get the routes from both RIs without having to take any further action.
If you have created a service profile, you may see subscriptions to your RIs that do not belong to your account—these are users who have subscribed to your service. Although you cannot make edits as you would to your own, the component is exactly the same. You will see many elements of the subscription (see below), including the subscriber’s account name.
A subscription requires the following parameters:
- RI: select an eligible RI where the subscription terminates
- Service: choose a service from the list of eligible names
- A single RI may not have more than one subscription to the same service provider
- The list of eligible services may 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 will default to “[RI name] to [service name]” but the user may enter any desired value as long as it is 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: user indicates any email addresses to receive notifications about this component
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 is not already dedicated to another subscription, and if it is 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, as there will no longer be a connector available for all other “non-dedicated” subscriptions.
Example in which user decides to (or is mandated to) dedicate a connector to the “Green” service 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 is advertised to the specified provider associated with this subscription. This is an optional service, but may be required to subscribe to some providers, is useful when using private addressing on your RI, and may streamline other functions
- A network can advertise addresses outside the NAT block, but they may be denied or treated differently by some providers that are subscribed
- Some applications may 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 may not define specific blocks from the provider
As of the current software release, a user must create a connector BEFORE using the “Dedicated Connector” service, whether it is optional or required.
If a provider mandates that its service be rate limited in its service profile, users will be required to dedicate a connector with a policer to the subscription, that may incur additional costs to the user.
If a provider has added certain services to the service profile, or the subscription is attached to a private RI, users may be required to have Perform NAT and the option must be filled out.