• Terraform Cloud
    • HCP Vault
    • HCP Consul
    • HCP Packer
    • HCP Boundary
  • Pricing
  • Documentation
  • Tutorials
  • Community
Sign InTry cloud for free
    • What is HCP?
    • HCP Account
      • AWS
      • Azure
      • Overview
        • Create and Manage HVN
        • Peering Connections
        • Transit Gateway Attachments
        • Routes
        • Security Groups
        • Create and Manage HVN
        • Peering Connections
        • Routes
        • Security Groups
      • Organizations
      • Users
      • Service Principals
        • Overview
        • Okta
        • Azure Active Directory
      • Multi-Factor Authentication
        • Overview
        • Payment
        • Flex Billing
      • Support
    • Overview
    • How HCP Boundary Works
    • Public Beta Limitations
    • Get Started
    • Boundary Documentation
    • What is HCP Consul?
    • Specifications
    • Constraints and Known Issues
      • Overview
      • Clusters
      • Clients
      • Federation
      • Upgrades
      • Audit Logs
      • Snapshots
      • Tutorials
      • Consul Documentation
      • Forums
    • Overview
    • Security Overview
    • Get Started
    • Login MFA
    • High Availability and Disaster Recovery
    • Performance Replication
    • Version Management
    • RBAC Permissions
    • Administrative Capabilities
    • Audit Log Management
      • Overview
      • FAQ
    • Metrics
    • Constraints and Known Issues
    • Migrate to HCP Vault
    • What is HCP Packer?
    • Get Started
      • Template Configuration
      • Image Metadata
      • Image Buckets
      • Image Channels and Revocation
      • Terraform Cloud Run Tasks
    • Reference Image Metadata
    • Manage Registry
    • API Reference
    • Packer Documentation
  • Glossary
  • Changelog
Type '/' to Search

»HashiCorp Virtual Network

The HashiCorp Virtual Network (HVN) makes HashiCorp Cloud Platform (HCP) networking possible. An HVN delegates an IPv4 CIDR range that HCP uses to automatically create resources in your cloud network.

All HCP resources must be located in a single HVN. You cannot use a single product deployment across two HVNs, and product deployments cannot be moved from one HVN to another. You also cannot make changes to HVNs after you create them.

You can manually configure your HVN or use HCP to provision an HVN with default configurations. To learn more, follow the tutorial for your supported infrastructure environment:

»Amazon Web Services (AWS)

»HCP Consul

  • Consul getting started tutorial
  • Consul cluster deployment tutorial

»HCP Vault

  • Vault getting started tutorial
  • Vault deployment tutorial

»Microsoft Azure

»HCP Consul

  • Get started with end-to-end deployment configuration tutorial
  • Learn about HCP

    • Blog
    • Press Release
  • Resources

    • Tutorials
    • Documentation
  • Help

    • Community
    • Support
    • Contact Us
  • Terms of Service
  • SLA
  • Shared Responsibility Model
  • Privacy
  • Security
  • Press Kit
©2022 HashiCorp, Inc. All rights reserved