CloudBit Documentation
  • Overview
  • Platform
    • Release Notes
    • Pricing
      • Compute
      • Kubernetes
      • Object Storage
      • Volumes & Snapshots
      • Load Balancers
      • Elastic IPs
      • VPN & Peering
      • Licenses
      • Support
      • Billing FAQ
    • Account
      • Sign Up
      • Closing account
  • Products
    • ▫️Compute
      • Instances
        • How-to
          • Connect to instances
          • Destroy instances
      • Volumes
      • Keypairs
      • ▫️Networking
        • Private Networks
        • Routers
        • Security Groups
        • Elastic IPs
        • Load Balancers
          • Balancing Pools
        • Certificates
        • VPN & Peering
    • ▫️Kubernetes
      • Clusters
      • Resources
        • Volumes Features (CSI)
        • Cluster Autoscaler
    • ▫️Object Storage
      • Instances
      • How-to
        • Access Storage with AWS S3 SDKs
        • Access Storage with Cyberduck
        • Access Storage with Mountainduck
      • Ressources
        • Supported Amazon S3 features
        • Replication Management
          • GET service replication
          • PUT service replication
          • DELETE service replication
  • Developer Center
    • Overview
    • API
      • Product Entities
      • Location Entities
    • CLI
    • Terraform
Powered by GitBook
On this page
  • Default Networks
  • Quickstart
  • Pricing
  • Regional Availability
  • Limitations

Was this helpful?

  1. Products
  2. Compute
  3. Networking

Private Networks

PreviousNetworkingNextRouters

Last updated 2 years ago

Was this helpful?

A Private Network (also known as VPC) is a virtual version of a physical network (Layer 2) implemented inside of our production network using VXLAN encapsulation. Private Networks provide the following:

  • Internal connectivity for your Compute Instances, including Kubernetes Clusters.

  • Complete isolation of network traffic from other Private Networks.

  • Integrated DHCP, IP, and DNS management enable easy network configuration.

Default Networks

Each region comes with a Private Network by default. The default network is an auto-created Private Network with the following addressing scheme:

  • Region BIT1: 172.31.0.0/20

Quickstart

  1. Start by clicking the Wizard button in the . Click Create Private Network.

  2. Name your Private Network and compose a description.

  3. Under CIDR, specify the IP address allocation in CIDR notation for your Private Network (for example, 10.11.12.0/24).

  4. Under Gateway IP, specify the IP address that serves as an entrance to other networks, such as the internet (for example, 10.11.12.1).

  5. Under Allocation Pool Start, specify the IP address that will serve as the start of the DHCP allocation pool. (for example, 10.11.12.100).

  6. Under Allocation Pool End, specify the IP address that will serve as the end of the DHCP allocation pool. (for example, 10.11.12.200).

  7. Under Domain Name Servers, specify the IP addresses that will serve as the DNS for your Private Network. (for example, 1.1.1.1, 8.8.8.8).

  8. Under Region, choose a data center Region where your Private Network should be created and click on Save. Creating a new Private Network takes a few minutes.

Pricing

Private Networks are free of charge.

Regional Availability

Private Networks are available in all regions. They are region-specific resources and can only be assigned within the same region.

Limitations

Only one subnet per Private Network is supported.

▫️
▫️
Control Panel