Build instance configuration templates for instance pools with shape, image, and block volumes.
Last verified: May 2026
Build instance configuration templates for instance pools with shape, image, networking, and block volumes.
Required Fields
compartmentIddisplayNameinstanceDetails.launchDetails.shapeinstanceDetails.launchDetails.sourceDetailsOutput will appear here...Build instance configuration templates for instance pools with shape, image, and block volumes. This tool helps OCI engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.
Your team has 4 instance pools (web, app, worker, batch) currently each defined with hand-crafted configurations. The builder generates: 4 instance configurations using a shared template structure, each with specific shape/image differences. After migration, updates flow consistently — change the AMI in one configuration, rolling-replace the pool to pick it up. Operational burden drops from 'maintain 4 separate config sets' to 'maintain 1 template + 4 small overrides'.
Instance configurations are the TEMPLATE used by Instance Pools. Define once in the configuration, instantiate many times in the pool. Updates to the configuration apply to NEW instances launched from it, not existing instances — to update existing, recreate the pool or use rolling replacement.
Reuse instance configurations across multiple pools when shapes/images/networking are identical. A single 'standard-web-tier-config' can underpin dev, staging, and production pools. Updates flow through one configuration to all pools that reference it.
Always include cloud-init user data in the configuration. The user data script bootstraps each new instance: install dependencies, pull config, register with monitoring. Without user data, every new instance from the pool requires manual configuration — defeating the point of pools.
The builder constructs OCI Instance Configuration definitions: instanceType=compute, instance details (compartment, shape, OCPU/memory for Flex, AD/FD placement, image OCID, boot volume size, additional block volumes), networking (subnet OCID, NSG list, primary VNIC details with assign-public-ip, hostname), metadata including ssh_authorized_keys and user_data (base64-encoded cloud-init script), and tags. Output is generated as oci compute-management instance-configuration commands and Terraform oci_core_instance_configuration resources.
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.