This document describes the cluster topologies supported by Segura, focusing on multi-region and hybrid scenarios. These topologies address business continuity, global scalability, and compliance with regional security and governance requirements.
Supported scenarios
Segura supports cluster operation in different topologies to meet specific needs:
- Multi-region: Cluster distributed across multiple data centers or geographic regions, whether on-premises, cloud, or hybrid.
- Hybrid environment: Cluster combining on-premises data centers with public cloud infrastructure such as AWS, Azure, or GCP.
Benefits
- Global high availability: Minimizes the impact of localized failures, natural disasters, or regional outages.
- Low latency for global users: Sessions and proxies provisioned close to users and resources.
- Compliance: Meets regulatory requirements for data residency, segmentation, and governance.
How to expand clusters to multi-region
Prerequisites
- Stable and secure network interconnectivity between regions.
- Time synchronization (NTP) among all nodes.
- Firewall rules allowing required ports between nodes.
- Licensing covering multiple regions or data centers.
Step-by-step – expansion example
-
Planning
- Define the regions or data centers to compose the cluster.
- Validate network, latency, throughput, and security requirements.
-
Node provisioning
- Install and configure the operating system and recommended dependencies at each location.
- Ensure all nodes are accessible via internal network (preferably VPN/MPLS).
-
Adding nodes to the cluster
- Access the Segura central console, navigate to “Cluster Management”.
- Select “Add Node” and provide connection/identification parameters for the new remote node.
- The system will perform connectivity and replication tests.
-
Load balancing and regional affinity configuration
- Optionally configure rules to route sessions based on user location or workload.
- Adjust failover policies between regions.
-
Synchronization and monitoring
- Check the dashboard to confirm nodes are “Healthy” and synchronized.
- Configure alerts for latency, connection loss, or remote node degradation.
Important considerations
- Latency: Cross-region communication can increase replication time; adjust thresholds and monitoring accordingly.
- Firewall and security: VPN/IPsec between regions is recommended.
- Cross-region failover: Assess if each region has sufficient resources to absorb load during total site unavailability.
Limitations and recommendations
- The number of supported regions varies depending on infrastructure, connectivity, and licensing.
- Perform periodic failover tests between regions.
- Always validate data residency compliance when distributing nodes across countries in regulated environments.