VPC (Virtual Private Cloud)

Independent Virtual Network in Cloud Environment

VPC service offers logically separated private network space dedicated to customers in the cloud. Public and private subnets can be created according to the purpose as well as local subnets for inter-server communications. Various networks can be configured using NAT and Internet gateways. Multiple VPCs can be created and operated independently, and connected to one another using VPC peering.




Service Architecture

  • Internet → Internet Gateway → Private Subnet - VM, VM ... / Private Subnet → Virtual IP : VM, VM ... → Local Subnet → VPC1
  • Internet → Internet Gateway → VPC Peering → Direct Connect → Customer Network
  • Customer Network → Direct Connect → Private Subnet - VM, VM ... / Private Subnet → Virtual IP: VM, VM ... → Local Subnet → VPC2

Key Features

  • VPC and subnet creation

    - Regular subnets (public or private) and local subnets (between VMs) available according to purpose
    - Reserve private IP in the subnet using Virtual IP
    - Offer additional DNS setting feature on user definition domain (Note that DNS information on basic domain cannot be changed)

  • NAT Gateway

    - For internet connection of Virtual Server without a public IP, map to the outbound traffic of the subnet using the representative public IP

  • Internet Gateway

    - Uplink Internet connections to enable Internet communications of VPCs

  • VPC Peering

    - 1:1 private IP communications among VPCs


    • Billing
    • Outbound Internet traffic charge : Charge by GB of VPC Internet-oriented outbound traffic
    • Public IP charge : Hourly rate for Public IP usage
    • NAT Gateway charge : Hourly rate for NAT Gateway usage
    • VPC Peering charge : Charge by GB of VPC peering outbound traffic
      ※ Only outbound traffic among Regions to be charged
Let’s talk

Whether you’re looking for a specific business solution or just need some questions answered, we’re here to help