Skip to main content

Service Gateway

Introduction​

The Service Gateway feature enables services on Virtual Machines to be accessible through the hypervisor's IP address. This is particularly valuable in scenarios where only a single public IP is available for both the host and guest VMs, such as bare metal hosting providers.

:::caution Early Access This feature is in early access with notable limitations. Please contact support for assistance. :::

Use Cases​

Single Public IP Environments: Allows VM services to be externally accessible using the hypervisor's IP when limited to one public address.

Network Separation: Enables Virtual Machines to expose very specific services to the local network, commonly used for hardened backup repositories.

Key Requirements and Recommendations​

  • 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 connect to a NAT network for compatibility.
  • No Gateway Limit: Multiple Service Gateways can be created, with a recommendation to use one per application.
  • Gateway Editing: Gateway editing requires complete recreation.

Deployment Steps​

  1. Navigate to the Service Gateways page and select New Service Gateway.
  2. Choose the target hypervisor.
  3. Create TCP port-to-VM mappings (only NAT-connected VMs are available).