Build VPC virtual server instance configurations with profiles, networking, volumes, and placement targets.
Last verified: May 2026
Build VPC virtual server instance configurations with profiles, networking, boot/data volumes, and placement targets.
Required Fields
namevpcIdzoneprofileimageprimaryNetworkInterfaceOutput will appear here...A new database workload needs four instances with identical configuration: bx2-8x32 profile, 100 GB boot, 500 GB data volume, in a private subnet without floating IP. You define the spec once in the builder, copy the Terraform into a `count`-based block, and apply. Four instances come up in three minutes with consistent configuration. Changes (resize, add disk) apply to all four with a one-line edit.
IBM Cloud VPC virtual server instances are the equivalent of EC2 instances or Azure VMs — sized by profile, networked by subnet, attached to volumes, and placed by zone. The Virtual Server Config Builder generates a complete instance spec including profile, image, networking (VPC, subnet, security groups, floating IP), block storage, and placement target. Output is `ibm_is_instance` Terraform-ready and supports both standalone instances and template-based instance groups.
The builder collects instance name, zone, profile, image, VPC and subnet, security groups, optional floating IP, boot volume size, attached block storage volumes, and placement target (default scheduler or dedicated host/group). Output is an `ibm_is_instance` Terraform resource with nested `volume_attachments` and `network_interfaces` blocks, plus separate `ibm_is_floating_ip` and `ibm_is_volume` resources as needed.
Pick the profile family based on the bottleneck, not the gut feel. Most workloads are memory-bound or network-bound long before they're CPU-bound, and the balanced profiles are usually the most cost-effective default.
Use a dedicated host or reservation for compliance-sensitive workloads where the underlying hardware must be exclusive. Compliance auditors increasingly ask for this and it's much cheaper to plan for it than to retrofit.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.