Gateway
Gateway
Deploy a single communication point between your private and public networks.
Gateway
A central communication point between your private network and the public network.
The Gateway service is the easiest way to ensure a secure and scalable connection between vRack infrastructure and an internet-connected network. It enables secure internet access to all your instances, without requiring separate public IP addresses. There are several plans available, each with different bandwidth capabilities to match your specific needs.
Gateway: a secure connection between networks
Help ensure a secure, stable connection between your internal network and an internet-connected external network. Meet specific security and performance requirements by combining Gateway with Floating IP, Load Balancer, or vRack Private Network services.
Benefits
Robust single-entry point for your infrastructure
Have all incoming internet traffic arrive at a single point - built with a 99.99% SLA-backed availability - that can then be forwarded to relevant resources. Thanks to Gateway, you can split your architecture on multiple networks, and configure routes on-demand, depending on your business logic.
Simple, pay-as-you-go pricing
Gateway is billed upon usage, on an hourly basis. The service is available in three plans, depending on your traffic profile: Small, Medium, and Large. With its simple pricing, you can easily anticipate your monthly costs.
Enhanced security
With its NAT functionality, Gateway for public cloud ensures individual instances, do not need to be directly attached to the public network and remain private. Any resources behind Gateway can still reach internet sources.
Key features
Cloud-native automation
Deploy and manage the Gateway service directly from your Public Cloud environment via OpenStack API support, or other compatible tools (Terraform, Ansible, Salt, etc.)
SNAT capabilities
Leverage Source Network Address Translation (SNAT) protocol to enable internet connectivity for private network. The instances behind your Gateway can access the internet while remaining isolated from the public network.
Network security
Combine Floating IP with Gateway to enable external access to instances within a private network.
With Gateway’s SNAT mode (without Floating IP), you can get fully private instances that are only accessible within the private network.
Discover Gateway service plans
| Gateway | S | M | L | XL |
| Bandwidth capacity | 200 Mbps | 500 Mbps | 2Gbps | 4Gbps |
| Outbound internet connectivity (through SNAT) | Yes | |||
| Inbound internet connectivity (through Floating IP) | Yes | |||
Flexible service exposure with Floating IPs
Leverage Floating IP and Gateway in combination to manage service exposure. Keep your service IP and if needed, reassign it to other instances and services. Or ensure no services are exposed outside with private instances remaining only accessible within the private network while having internet access by leveraging the Gateway SNAT capability.
Combine Load Balancer and Floating IPs
Use our Gateway in conjunction with Load Balancer and Floating IPs to help ensure, your application services are exposed according to your security needs. This architecture allows customers to choose from different operating modes of Load Balancer (public and private). Allowing you to benefit from the flexibility to update your Load Balancer transparently.
Outbound Gateway to Internet
Create instances that only use private ports rather than public ports, while keeping access to the internet through the Gateway. This is useful when you need your instance to query the outside world and access external 3rd party services while staying directly unreachable from the internet.
Gateway scenarios
Combine Floating IP, Gateway, and Load Balancer in your architecture and achieve the appropriate rules for network accessibility, and achieve the level of security that you require.
Enable internet access to private instances
Instances running within a private network can leverage Gateway to send traffic to the public internet, while not being accessible from the outside. This enables you to update any software running on your private instances while making sure that only services within the private network can connect to your private instances.
Exposing a service on an instance
A service running on an instance within a private network can only be reached from the public internet through a Floating IP. This lets you update or replace the instance, transparently as the Floating IP remains the same.
For outgoing traffic to the public internet, the service can leverage Gateway. A typical use case is when a service needs to download an update.
Exposing services behind Load Balancer
A Load Balancer can be reached via a Floating IP and distribute incoming traffic into several instances. The instances behind Load Balancer have no public IP, ensuring they remain completely private and not directly accessible from outside. Load Balancer brings a higher level of security while supporting SSL encryption and can be updated transparently as the floating IP is hosted at the Gateway level.
Related Products
Guides
Concepts - Public Cloud Networking
Understand networking concepts in the Public Cloud.
Creating a Private Network with Gateway
Learn how to create a Private Network with Gateway.
FAQ
What is a gateway?
A gateway is a secure link between an organization’s internal network and the internet. Since local networks and the internet use different protocols, a gateway serves as a protocol converter to enable communication between them.
Using a gateway provides a secure environment for your internal cloud services and applications, while also using the internet when needed. It functions as a scalable and dependable central communication point between the two networks, helping to ensure inbound and outbound internet traffic remains secure to enhance your organization’s infrastructure efficiency.
What is the Gateway service?
By itself, the Gateway service functions as a standard gateway, allowing instances in one of your private networks to communicate with another network that is connected to the internet. It ensures security for local networks connected to internet-based networks, enabling a stable and resilient connection. The Floating IP, Load Balancer, and vRack services can be used together with the Gateway service. One way to use Gateway is by combining it with Floating IP to make private network instances accessible from outside. Another way is to combine Gateway with the Load Balancer service for more efficient traffic distribution.
Why use the Gateway service?
Gateway acts as the single entry point for your applications. By combining Gateway with Floating IP, you can ensure instances within a private network are accessible from outside or that a private Load Balancer can distribute traffic.
Can Gateway be integrated into a Public Cloud project?
Yes, our service can be integrated into a Public Cloud project. You can manage it from your customer control panel or the OVHcloud API, or even via the OpenStack API.
What is the pricing model for the Gateway service?
For greater flexibility, the Gateway service operates on a pay-as-you-go model, where you’re billed hourly and receive a monthly invoice. There are five Gateway service plans available for you to pick from, each designed to match your specific needs, and you can easily upgrade or downgrade whenever necessary.