Creating an Instance Using Visual Object Editor

Not Oracle Cloud at Customer This topic does not apply to Oracle Cloud at Customer.

When you create an instance using visual object editor, a single orchestration v2 is created automatically to manage the instance and its associated resources.

Storage volumes and networking objects used by the instance are created in the same orchestration. Instances are nonpersistent by default. However, storage volumes and other objects are created with persistence set to true, so that if you suspend the orchestration, instances are shut down, but storage volumes aren’t deleted. Terminating the orchestration, however, will cause all objects to be deleted and any data on storage volumes will be lost.


You can’t create Windows instances using the Visual Object Editor. Create Windows instances using QuickStarts or by using the Create Instance wizard.



  1. Sign in to the Compute Classic console. If your domain spans multiple sites, select the appropriate site. To change the site, click the Site menu near the top of the page.
  2. Click Visualization in the top right corner.
  3. In the palette on the left, expand Storage, and then and drag and drop Instance on to the canvas in the center pane.
  4. Select or enter the following information in the Create Instance dialog box. Select the appropriate image. If you select an image from Oracle Cloud Marketplace, accept the terms and wait for the app to be installed before continuing.
    • Instance Name: Enter a name for the instance or use the default value.

    • Boot Image: Select the image you want to use. The image specifies the operating system and disk size of the instance.

      Only Oracle-provided images and private images are available. Oracle Cloud Marketplace images are not listed.

    • Shape: Select the shape that you want to use. The shape specifies the OCPU and memory resources to be allocated to the instance. If you select a high I/O shape, an NVMe SSD disk is automatically attached to your instance. This is a local, nonpersistent NVMe SSD disk, which provides high I/O access rates. This disk is attached to your instance with the device name /dev/xvdz. After your instance is created, you can mount this disk and format it as required. The size of this NVMe SSD disk is fixed depending on the selected shape.


      High I/O shapes aren’t available in all regions.

      For more information about shapes, see About Shapes.

    • SSH Key: Select an existing SSH public key.

    • Storage Size: The size is set automatically to accommodate the disk size that’s specified in the image that you selected earlier. If you want a larger boot disk than that specified in the image, then enter a larger size.


      You can increase the size of a storage volume after creating it, even if the storage volume is attached to an instance. See Increasing the Size of a Storage Volume. However, you can’t reduce the size of a storage volume after you’ve created it. So ensure that you don’t overestimate your storage requirement.

    • IP Network: Select the IP network that you want to attach your instance to.
  5. Click Create.
    An orchestration v2 is created. For example, if you created an instance and specified the name of the instance as vm1, an orchestration v2 is created with the same name. While the instance is being created, you can monitor the corresponding orchestration on the Orchestrations page. When the instance is created, it is listed on the Instances page.

An instance is created with the following general configuration:

  • Uses a persistent boot disk. You won’t be able to create an instance snapshot of this instance.

  • In sites which support public IP address reservations, security rules, and access control lists in IP networks:

    • Doesn’t have an interface on the shared network.

    • Has one interface on the default IP network and is added to a vNICset of the same name.

    • Has one IP address from the /oracle/public/cloud-ippool IP address pool and another IP address from the /oracle/public/public-ippool IP address pool.

    • Has the required security rules and ACL set up to enable SSH access to the instance and all egress traffic.

  • In sites which don’t support public IP address reservations, security rules, and access control lists in IP networks:

    • Has an interface on the shared network.

    • Is added to the default security list.

    • Has a temporary public IP address.

    • Has the required security rule set up to enable SSH access.

  • Is nonpersistent. This allows you to update the instance by suspending the corresponding orchestration v2. When the orchestration is suspended, the instance status changes to Inactive and you can update any attribute of the instance.

  • Has persistence specified as true for all other objects.

After your instance is created, you can log in to your instance. See Logging In to an Instance.


To ensure that Compute Classic instances provide a resilient platform for your workloads, make sure that the latest security patches are applied to the operating system running on the instances. In addition, before deploying applications on an instance, review the security configuration of the operating system and verify that it complies with your security policies and standards.

For security and patching-related guidelines, see the documentation for your operating system.