Introduction
The Service Gateway feature is designed to allow services running on Virtual Machines (VMs) to be exposed using the IP address of the hypervisor. This is useful in scenarios where only a single public IP is available for both the host and guest VMs such as bare metal hosting providers.
Early Access Feature
This feature currently has a number of caveats and is likely to rapidly change. Please contact support if you have a use case for this feature and require additional assistance. The current limitations include:
Only ports 1 to 1024 can be used on the Service Gateway
Editing a Gateway is not possible, it must be recreated
Usage and Limitations
Use Cases:
Single Public IP Environments: Especially useful in hosting environments where only a single public IP is available, enabling services on VMs to be accessible externally using the hypervisor's IP address.
Network Separation: Scenarios where you have a Virtual Machine that should only expose very specific services to the local network. Most commonly used for hardened backup repositories where the data transfer port is open whilst maintaining management traffic separation.
Recommendations and Limitations:
Port Limitations: Only TCP ports from 1 to 1024 can be exposed on the Service Gateway. Although the mapped VM port can be above 1024.
NAT Network Requirement: VMs must be connected to a NAT network to be compatible with the Service Gateway feature.
No Limit on Gateways: There is no restriction on the number of Service Gateways that can be created. We recommend using one per application.
Deployment
Step 1: Navigate to the Service Gateways Page
Go to the Service Gateways Page and select "New Service Gateway."
Step 2: Select the Hypervisor
Choose the hypervisor on which you want to create the new Service Gateway.
Step 3: Create Port to VM Mappings
Map each TCP port that you wish to expose to the respective VM.
Note: Only VMs with a network interface on the NAT network will be available for configuration in the Service Gateway.