Mandatory and optional network services when using the IaaS platforms.
The network design of the IaaS platform is based on L3 (IP) and hardware-based routing. Virtual routers or L2 overlay networks are not used. This ensures maximum network performance and operational simplicity at all scales. Security are based on sets of L3 IP address access control lists. If a customer requires overlay networks, they are free to deploy them – at less overhead and at higher performance than in competing provider solutions.
- Public IPv4 and IPv6 addresses directly assigned to network interface
- Private addresses for site-internal communication
- Ingress / Egress traffic controlled by API driven ACL
- Managed SLB (based on BGP and haproxy)
- Saferoute / IP-VPN
- Bring your own IP prefixes (for large customers)
- Reverse DNS names (for large customers, own prefixes)
| Product Code | Description |
|---|---|
| NET-publicv4 | Public IPv4 address |
| NET-publicv6 | Public IPv6 address |
| NET-byoip | Bring your own IP prefix |
| NET-ingress | Ingress traffic into an instance from outside the datacenter |
| NET-egress | Egress traffic from an instance to outside the datacenter |
| NET-mgn.slb | Managed Service Load Balancer |
| NET-saferoute | Saferoute MPLS based IP-VPN |
| NET-rdns | Reverse DNS records (PTR) |
Public IP addresses
Safespring provides public IPv4 and IPv6 addresses to your services. By default, each instance receives one of each.
Bring your own IP prefix(es)
Customers can allocate their own IPv4 prefixes to the platform for their own use in the platform (minimum size /24). Safespring configures these prefixes in the platform and announce them to its peers using BGP.
Ingress / Egress traffic
Safespring measures ingress and egress traffic for each customer instance at the network border of each datacenter.
Managed SLB
Safespring manages a Service Load Balancer for customers. It is hosted on a server instance in the customers environment. The load balancer is a subscription service and is charged monthly. Included in the cost is configuration and management. Additional IPv4 addresses are charged as an extra.
Saferoute
Safespring provides an MPLS based IP-VPN service with the local NREN allowing separate traffic from regular Internet traffic, such that customers can connect an environment in the Safespring datacenters to their own local infrastructure, e.g. behind firewalls, etc. This product depends on network integration with the local NREN its peers and is not generally available to any customer, but other VPN solutions can be delivered using standard Professional Services instead in those cases.
Reverse DNS names
Safespring can configure, on a case-by-case basis, reverse DNS names of its public IP addresses for customers hosting for example SMTP servers or other services where the reverse DNS name (PTR record) is important.
