About virtual server instances for VPC
Virtual servers for VPC is an Infrastructure-as-a-Service (IaaS) offering that gives you access to all of the benefits of IBM Cloud VPC, including network isolation, security, and flexibility.
With virtual server instances for VPC, you can provision instances with high network performance. When you provision an instance, you select a profile that matches the amount of memory and compute power that you need for the application that you plan to run on the instance. Instances are available on the x86 architecture. After you provision an instance, you control and manage those infrastructure resources.
How are virtual server instances for VPC different from other IBM virtual server offerings?
In the IBM Cloud Virtual Server for Classic infrastructure offering, instances use native subnet and VLAN networking to communicate to each other within a data center (and single pod). Using subnet and VLAN networking in one pod works well until you must scale up or have large virtual resource demands that require resources to be created between pods. (Adding appliances for VLAN spanning can get expensive and complicated!)
IBM Cloud VPC adds a network orchestration layer that eliminates the pod boundary, creating increased capacity for scaling instances. The network orchestration layer handles all of the networking for all virtual server instances that are within a VPC across regions and zones. With the software defined networking capabilities that VPC provides, you've more options for multi-vNIC instances and larger subnet sizes.
To review and start deploying your typical x86 virtual server, see the following topics:
Deployment options Description Virtual Servers for VPC profiles IBM Cloud Virtual Servers for VPC provide the advanced security of a private cloud with the agility and ease of a public cloud. Virtual servers for VPC offer the best network performance (up to 80 Gbps), best security, and fastest provisioning times. Virtual Servers for Classic When you create an x86-based virtual server in classic infrastructure, you've a lot of options. We can choose between a public (multi-tenancy) environment or a dedicated (single-tenancy) environment. Then, depending on the chosen environment, you select hourly, monthly, or transient virtual servers. In the case of public virtual servers, you also choose to use either SAN-based storage or local storage. To compare all virtual compute options, see Compare Virtual Compute options.
Next steps
After you choose a profile, it's time to plan for and create an instance.