Use Cases

Cross Connect is a natural fit for sharing secure information between VDCs that belong to IONOS's Cloud ecosystem in a specific region. It acts as a backup and recovery tool, and ensures continued business connectivity and reduced latency, and a secure data transmission.

Scenario 1: Resource Sharing


The price and overhead of managing resources individually rises with the installation and administration of each data center.


Within the regional hub, you can provide access to centralized resources or functionality while concealing crucial information. For example, consider creating two VDCs— VDC1 for the sales team and VDC2 for the operations team. Add centralized functionalities, such as a firewall and a Virtual Private Network (VPN), network security, identity and access management to VDC2. Connect the isolated VDCs, VDC1 and VDC2, using Cross Connect. In such a scenario, the sales team (VDC1) can only access the centralized resources from the IT operations team data center (VDC2) without additional infrastructure and administration. Still, the critical data of the sales and operation teams remain hidden. Moreover, upon scaling, the centralized resources can be shared via all the new data centers without the need for extra infrastructure or management. Thus, Cross Connect is cost efficient.

Scenario 2: Organizing resources in different VDCs based on the organizational structure


Multiple organizational structures can exist within an organization. It becomes increasingly challenging to oversee several organizational structures as a business expands and to give roles and privileges in order to effectively manage resources.


Consider that your organization is handling multiple teams and each team works on separate projects. If you want a project (let's call it P1) to be accounted for separately, an ideal approach is to create a separate VDC for P1 and similarly have distinct VDCs for each team or project tightly coupled using Cross Connect over private LANs. This automatically creates a separate section on the IONOS bill each month for VDC P1 and all the associated VDCs. That way, you can have custom labels for resources, instances, cost centers, etc. Moreover, you can also:

  • achieve an organizational separation for organizational, financial (cost and billing), and user management purposes. For example, you can configure VDC-Core for core infrastructure, VDC1 for production servers, VDC2 for development resources, VDC3 for monitoring services, etc.

  • assign relevant permissions to limit external users or partners via the User Manager. With valid permissions, they can create or manage the services. Additionally, Cross Connect can be used to provide access to functionality provided by such managed VDCs.

  • allot specific privileges to a department. You may permit a project department to establish several data centers, for instance. After that, a distinct data center is established by the project department solely for project accountability.

Last updated