Create a Linode account to try this guide with a $ credit.
This credit will be applied to any valid services used during your first  days.
VPC Availability
VPCs are now publicly available to all customers in select data centers. For a list of supported regions, review the Availability section.

A VPC (Virtual Private Cloud) is an isolated network that enables private communication between Compute Instances within the same data center. Since Cloud environments often necessitate sharing infrastructure with other users, VPCs are a critical component of many application architectures and can further isolate your workloads from other Akamai users.

Protect Sensitive Data

Networking packets sent over a VPC are walled off from the public internet — as well as from other services within the same data center that don’t belong to the same VPC. When assigning a Compute Instance to a VPC, you can opt for it to be fully private or configure it with public internet access through either a 1:1 NAT on the VPC or a public internet interface.

Segment Traffic Into Separate Subnets

Instead of assigning a single IPv4 range for the entire VPC, Akamai’s VPC design allows users to configure multiple RFC1918 ranges through the use of subnets. This has the benefit of segmenting services into distinct networks and can be useful when migrating or combining existing networking environments so that there are no changes to routing or static IPs. These subnets can isolate various functionality of an application (such as separating public frontend services from private backend services) or separate out a production environment from staging or development.

Routing between subnets on a VPC is configured automatically. By default, all Compute Instances on a VPC can communicate with any other instance on that VPC, regardless of which subnet the other instance is assigned to use.

Compatible with Cloud Firewalls

If a Compute Instance is assigned to a Cloud Firewall, firewall rules that limit access and filter traffic will be applied to the public interface as well as the VPC interface. This means that private traffic between Compute Instances within a VPC will be filtered by the Cloud Firewall.


VPCs are available in: Amsterdam (Netherlands), Chennai (India), Chicago IL (USA), Jakarta (Indonesia), Los Angeles CA (USA), Miami FL (USA), Milan (Italy), Paris (France), Osaka (Japan), São Paulo (Brazil), Seattle WA (USA), Stockholm (Sweden), and Washington DC (USA).


VPCs are provided at no additional cost. Additionally, communication across your private VPC network does not count against your monthly network transfer usage.

Difference Between Private Network Options (VPCs, VLANs, and Private IPs)

Both VLANs and Private IP addresses are private networking services offered by Akamai cloud computing. VLANs operate on layer 2 of the OSI model whereas VPCs and Private IPs operate on layer 3. While this allows VLANs to use any layer 3 protocol, it also means that there are limitations to routing and other layer 3 features. Since VPC is on layer 3 and uses the IP (Internet Protocol), IP addressing and IP routing features are built-in.

  • Latency: All 3 services offer extremely low latency.

  • Cost: There is no charge for VPCs, VLANs, and private IP addresses. The only costs are related to the associated Compute Instance service and any outbound traffic over the public IP addresses.

  • Network Isolation: Both VPC and VLANs offer true network isolation from other tenants within the same data center. Private IP addresses are accessible by default from any other instance in the same region, provided that instance also has a private IP address. This is because they all use the same range.

  • Multiple Subnets: Each VPC can have multiple subnets. Each VLAN can only be configured with IP addresses from one specified range.

Technical Specifications

  • Users can create up to 10 VPCs per data center (by default).

  • Each VPC can have up to 10 subnets.

  • Compute Instances can join a VPC by specifying the VPC as a network interface. Other services, such as NodeBalancers, LKE clusters, and Managed Databases cannot join a VPC at this time.

  • VPCs can only be deployed to a single data center. As such, Compute Instances within different data centers cannot belong to the same VPC.

  • A VPC interface can be private or have public internet access through a 1:1 NAT.

Additional Limits and Considerations

  • VPCs peering is not supported (within the same data center or different data centers).

  • While VPC traffic is isolated from other cloud tenants, it is not encrypted.

  • IPv6 addresses are not available on a VPC interface.

  • VPC IP addresses cannot use IP Sharing or IP Transfer features.

  • To facilitate routing between different subnets on the same VPC, configure the VPC network interface as the primary interface.

  • Network traffic across a private VPC network does not count against your monthly network transfer usage. The network transfer allowance for Compute Instances configured on VPCs still counts towards the global network transfer pool on your account.

  • Using the Metadata service over a VPC is not yet supported.

This page was originally published on

Your Feedback Is Important

Let us know if this guide was helpful to you.