Creating an Instance

Use the steps in this topic to create a bare metal or virtual machine (VM) Compute instance.

Tip

If this is your first time creating an instance, consider following the Getting Started Tutorial for a guided workflow through the steps required to create an instance.

When you create an instance, the instance is automatically attached to a virtual network interface card (VNIC) in the cloud network's subnet and given a private IP address from the subnet's CIDR. You can let the IP address be automatically assigned, or you can specify a particular address of your choice. The private IP address lets instances within the cloud network communicate with each other. If you've set up the cloud network for DNS, instances can instead use fully qualified domain names (FQDNs).

If the subnet is public, you can optionally assign the instance a public IP address. A public IP address is required to communicate with the instance over the internet, and to establish a Secure Shell (SSH) or Remote Desktop Protocol (RDP) connection to the instance from outside the cloud network.

Note

Partner images and pre-built Oracle enterprise images are not available in Government Cloud realms.
Warning

Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.

Required IAM Policy

To use Oracle Cloud Infrastructure, you must be given the required type of access in a policy  written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which compartment  you should work in.

Tip

When you create an instance, several other resources are involved, such as an image, a cloud network, and a subnet. Those other resources can be in the same compartment  with the instance or in other compartments. You must have the required level of access to each of the compartments involved in order to launch the instance. This is also true when you attach a volume to an instance; they don't have to be in the same compartment, but if they're not, you need the required level of access to each of the compartments.

For administrators: The simplest policy to enable users to create instances is listed in Let users launch Compute instances. It gives the specified group general access to manage instances and images, along with the required level of access to attach existing block volumes to the instances. If the group needs to create block volumes, they'll need the ability to manage block volumes (see Let volume admins manage block volumes, backups, and volume groups).

If you're new to policies, see Getting Started with Policies and Common Policies. For reference material about writing policies for instances, cloud networks, or other Core Services API resources, see Details for the Core Services.

Partner Image Catalog

If the group needs to create instances based on partner images, they'll need the manage permission for app-catalog-listing to create subscriptions to images from the Partner Image catalog. See Let users list and subscribe to images from the Partner Image catalog.

Recommended Networking Launch Types

When you launch a VM instance, by default, Oracle Cloud Infrastructure chooses a recommended networking type for the VNIC based on the instance shape and OS image. The networking interface handles functions such as disk input/output and network communication. The following options are available:

  • Paravirtualized networking: For general purpose workloads such as enterprise applications, microservices, and small databases. Paravirtualized networking also provides increased flexibility to use the same image across different hardware platforms.
  • Hardware-assisted (SR-IOV) networking: Single root input/output virtualization. For low-latency workloads such as video streaming, real-time applications, and large or clustered databases. Hardware-assisted (SR-IOV) networking uses the VFIO driver framework.

The following table lists the default and supported networking types for VM shapes.

Shape series

Default Networking Type Supported Networking Types

VM.Standard1

SR-IOV Paravirtualized, SR-IOV
VM.Standard2

Paravirtualized

Paravirtualized, SR-IOV
VM.Standard.E2 Paravirtualized Paravirtualized only
VM.Standard.E3 SR-IOV

Paravirtualized, SR-IOV

Note: Due to driver support, the Windows Server 2012 platform image supports paravirtualized networking only.

VM.DenseIO1 SR-IOV Paravirtualized, SR-IOV
VM.DenseIO2 Paravirtualized Paravirtualized, SR-IOV
VM.GPU2 SR-IOV Paravirtualized, SR-IOV
VM.GPU3 SR-IOV Paravirtualized, SR-IOV

To use paravirtualized networking, you must also use an image that supports paravirtualized networking. Paravirtualized networking is supported on these Oracle-provided images:

  • Oracle Linux 7, Oracle Linux 6: Images published in March 2019 or later.
  • CentOS 7, CentOS 6: Images published in July 2019 or later.
  • Ubuntu 18.04, Ubuntu 16.04: Images published in March 2019 or later.
  • Windows Server 2019: All images.
  • Windows Server 2016: Images published in August 2019 or later.

SR-IOV networking is supported on all Oracle-provided images, except for Windows Server 2019 when launched using a VM.Standard2 shape.

You can create an instance that uses a specific networking type instead of the default. However, depending on compatibility between the shape and image that you choose, the instance might not launch properly. You can test whether it succeeded by connecting to the instance. If the connection fails, the networking type is not supported. Relaunch the instance using a supported networking type.

Creating a Linux Instance

Use the following steps to create a Linux instance.

Prerequisites

Before you start, you'll need these things:

  • A virtual cloud network (VCN) to launch the instance in. For information about setting up cloud networks, see Overview of Networking.
  • If you want to use your own Secure Shell (SSH) key to connect to the instance using SSH, you'll need the public key from the SSH key pair that you plan to use. The key must be in OpenSSH format. You must use your own key pair if you will connect to the instance from a Windows system that does not have OpenSSH installed. For more information, see Managing Key Pairs on Linux Instances

To create a Linux instance

  1. Open the navigation menu. Under Core Infrastructure, go to Compute and click Instances.
  2. Select a Compartment that you have permission to work in.

    By default, the instance launches in the current compartment. The other resources that you choose can come from different compartments.

  3. Click Create Instance.
  4. Enter a name for the instance. You can add or change the name later. The name doesn't need to be unique, because an Oracle Cloud Identifier (OCID) uniquely identifies the instance.
  5. By default, an Oracle Linux 7.x image  is used to boot the instance. To select a different image or a boot volume, in the Image or operating system section, click Change Image. The following options are available:

    • Platform Images: Pre-built images for Oracle Cloud Infrastructure. For more information about platform images, see Oracle-Provided Images.
    • Oracle Images: Pre-built Oracle enterprise images and solutions enabled for Oracle Cloud Infrastructure.
    • Partner Images: Trusted third-party images published by Oracle partners. Click the down arrow in the row for an image to view additional details about the image, or to change the image build. For more information, see Overview of Marketplace and Working with Listings.
    • Custom Images: Custom images created or imported into your Oracle Cloud Infrastructure environment. For more information, see Managing Custom Images.
    • Boot Volumes: Boot volumes that are available for creating a new instance in your Oracle Cloud Infrastructure environment. For more information, see Boot Volumes.
    • Image OCID: Create an instance using a specific version of an image by providing the image OCID . To determine the image OCID for Oracle-provided images, see Oracle-Provided Image Release Notes.

    Choose an image or boot volume, and then click Select Image or Select Boot Volume.

  6. Click Show Shape, Network and Storage Options.
  7. Select the Availability domain that you want to create the instance in.

    Note

    If you're creating an instance from a boot volume, you must create the instance in the same availability domain as the boot volume.
  8. In the Shape section, click Change Shape. Then, do the following:

    1. In the Instance type section, select Virtual Machine or Bare Metal Machine.
    2. If you're creating a virtual machine, in the Shape series section, select a processor group, and then choose a shape . The following options are available:

      • AMD Rome: The flexible shape, which uses the current generation AMD processor and has a customizable number of OCPUs. For Select the number of OCPUs, choose the number of OCPUs that you want to allocate to this instance by dragging the slider. The amount of memory and other resources scale proportionately.
      • Intel Skylake: Standard shapes that use the current generation Intel processor and have a fixed number of OCPUs.
      • Specialty and Legacy: Standard shapes with previous generation Intel and AMD processors, the Always Free VM.Standard.E2.1.Micro shape, Dense I/O shapes, GPU shapes, and HPC shapes.

      If a shape is disabled, it means that the shape is either incompatible with the image that you selected previously, or not available in the current availability domain. If you don't see a shape, it means that you don't have service limits for the shape. You can request a service limit increase.

      For more information about shapes, see Compute Shapes.

    3. Click Select Shape.
  9. In the Configure networking section, configure the network details for the instance:

    • Virtual cloud network compartment: The compartment containing the network in which to create the instance.
    • Virtual cloud network: The network in which to create the instance.
    • Subnet compartment: The compartment containing a subnet within the cloud network to attach the instance to.
    • Subnet: A subnet within the cloud network to attach the instance to. The subnets are either public or private. Private means the instances in that subnet can't have public IP addresses. For more information, see Access to the Internet. Subnets can also be either AD-specific or regional (regional ones have "regional" after the name). We recommend using regional subnets. For more information, see About Regional Subnets.
    • Use network security groups to control traffic: Select this check box to add the instance's primary VNIC  to at least one network security group (NSG) of your choice. NSGs have security rules that apply only to the VNICs in that NSG. For more information, see Network Security Groups.
    • If the subnet is public, you can optionally assign the instance a public IP address. A public IP address makes the instance accessible from the internet. Select the Assign a public IP address option. For more information, see Access to the Internet.
  10. In the Boot volume section, configure the size and encryption options for the instance's boot volume:

    • To specify a custom size for the boot volume, select the Specify a custom boot volume size check box. Then, enter a custom size from 50 GB to 32 TB. The specified size must be larger than the default boot volume size for the selected image. See Custom Boot Volume Sizes for more information.
    • For VM instances, you can optionally select the Use in-transit encryption check box. See Block Volume Encryption for more information. If you are using your own Vault service encryption key for the boot volume, then this key is also used for in-transit encryption. Otherwise, the Oracle-provided encryption key is used.
    • Boot volumes are encrypted by default, but you can optionally use your own Vault service encryption key to encrypt the data in this volume. To use the Vault service for your encryption needs, select the Encrypt this volume with a key that you manage check box. Then, select the Vault compartment and Vault that contain the master encryption key you want to use. Also select the Master encryption key compartment and Master encryption key. For more information about encryption, see Overview of Vault. If you enable this option, this key is used for both data at rest encryption and in-transit encryption.
    • The Block Volume elastic performance feature lets you change the volume performance for boot volumes. When you create an instance, its boot volume is configured with the default volume performance set to Balanced. After you launch the instance, you can modify the performance setting. For steps to modify the performance setting, see Changing the Performance of a Volume. For more information about this feature, see Block Volume Elastic Performance.

  11. In the Add SSH keys section, generate an SSH key pair or upload your own public key. Select one of the following options:

    • Generate SSH keys: Oracle Cloud Infrastructure generates an RSA key pair for the instance. Click Save Private Key, and then save the private key on your computer. Optionally, click Save Public Key and then save the public key.

      Warning

      Anyone who has access to the private key can connect to the instance. Store the private key in a secure location.
      Important

      To use a key pair that is generated by Oracle Cloud Infrastructure, you must access the instance from a system that has OpenSSH installed. UNIX-based systems (including Linux and OS X), Windows 10, and Windows Server 2019 should have OpenSSH. For more information, see Managing Key Pairs on Linux Instances.
    • Choose SSH key files: Upload the public key (.pub) portion of your key pair. Either browse to the key file that you want to upload, or drag and drop the file into the box. To provide multiple keys, press and hold down the Command key (on Mac) or the CTRL key (on Windows) while selecting files.
    • Paste SSH keys: Paste the public key (.pub) portion of your key pair in the box.
    • No SSH keys: Select this option only if you do not want to connect to the instance using SSH. You cannot provide a public key or save the key pair that is generated by Oracle Cloud Infrastructure after the instance is created.
  12. (Optional) To configure advanced networking and management settings, click Show Advanced Options. The following options are available:

    • On the Management tab, you can configure the following:

      • Choose a compartment for your instance: The compartment that you want to launch the instance in.
      • Choose a fault domain: The fault domain to use for the instance. If you do not specify the fault domain, the system selects one for you. The fault domain cannot be changed after you create the instance. If you want to use a different fault domain, you must terminate the instance and launch a new instance in the preferred fault domain. For more information, see Fault Domains and Best Practices for Your Compute Instance.
      • Initialization Script: User data to be used by cloud-init to run custom scripts or provide custom cloud-init configuration. Browse to the file that you want to upload, or drag and drop the file into the box. The file or script does not need to be base64-encoded, because the Console performs this encoding when the information is submitted. For information about how to take advantage of user data, see the cloud-init documentation. The total maximum size for user data and other metadata that you provide is 32,000 bytes.
      • Enable monitoring: Select this check box to collect metrics for this instance. When enabled, the Oracle Cloud Agent software on the instance emits metrics for this instance to the Monitoring service using the oci_computeagent metric namespace.

        This option is available for supported images only. If you use a legacy version of a supported image, you might also have to install the Oracle Cloud Agent software. For more information, see Enabling Monitoring for Compute Instances.

      • Use Oracle Cloud Agent to manage this instance: Select this check box to let Oracle Cloud Agent automate operational tasks for the instance, such as installing patches. For more information, see OS Management.

        Important

        Oracle Autonomous Linux instances cannot be managed by the OS Management service. See this known issue for more information.
      • Tags: Optionally, you can apply tags. If you have permissions to create a resource, you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator.
    • On the Networking tab, you can configure the following:

      • Private IP Address: An available private IP address of your choice from the subnet's CIDR. If you don't specify a value, the private IP address is automatically assigned.
      • Hostname: A hostname to be used for DNS within the cloud network. Available only if the VCN and subnet both have DNS labels. For more information, see DNS in Your Virtual Cloud Network.
      • Launch Options: The networking launch type. Available only for VMs. For more information, see Recommended Networking Launch Types.
    • On the Image tab, you can change the image build. By default, the latest build of the image is used to create the instance. You can select an older build of the image that is compatible with the shape you selected. Only compatible image builds are displayed in the list. You must select a shape before you can change the image build.

    • On the Host tab, you can choose to launch the instance on a dedicated virtual machine host. This lets you run the instance in isolation, so that it is not running on shared infrastructure. To do this, select the Launch the virtual machine on a dedicated host check box, and then select a dedicated virtual machine host from the drop-down list. Before you can place an instance on a dedicated virtual machine host, you must create a dedicated virtual machine host in the same availability domain and fault domain as the instance. You can only place an instance on a dedicated virtual machine host at the time that you create the instance. For more information, see Dedicated Virtual Machine Hosts.

  13. Click Create.

    To track the progress of the operation, you can monitor the associated work request. For more information, see Using the Console to View Work Requests.

After the instance is provisioned, details about it appear in the instance list. To view additional details, including IP addresses, click the instance name.

When the instance is fully provisioned and running, you can connect to it using SSH as described in Connecting to an Instance.

You also can attach a volume to the instance, provided the volume is in the same availability domain. For background information about volumes, see Overview of Block Volume.

For steps to let additional users connect to the instance, see Adding Users on an Instance.

Creating a Windows Instance

Use the following steps to create a Windows instance.

Prerequisites

Before you start, you'll need these things:

  • A virtual cloud network (VCN) to launch the instance in. For information about setting up VCNs, see Overview of Networking.
  • A VCN security rule that enables Remote Desktop Protocol (RDP) access so that you can connect to your instance. Specifically, you need a stateful ingress rule for TCP traffic on destination port 3389 from source 0.0.0.0/0 and any source port. For more information, see Security Rules. You can implement this security rule in a network security group that you will add this Windows instance to. Or, you can implement this security rule in a security list that is used by the instance's subnet.

    To enable RDP access
    1. Open the navigation menu. Under Core Infrastructure, go to Networking and click Virtual Cloud Networks.
    2. Click the cloud network that you're interested in.
    3. To add the rule to a network security group that the instance belongs to:

      1. Under Resources, click Network Security Groups. Then click the network security group that you're interested in.
      2. Click Add Rules.
      3. Enter the following values for the rule:

        • Stateless: Leave the check box cleared.
        • Source Type: CIDR
        • Source CIDR: 0.0.0.0/0
        • IP Protocol: RDP (TCP/3389)
        • Source Port Range: All
        • Destination Port Range: 3389
        • Description: An optional description of the rule.
      4. When done, click Add.
    4. Or, to add the rule to a security list that is used by the instance's subnet:

      1. Under Resources, click Security Lists. Then click the security list you're interested in.
      2. Click Add Ingress Rules.
      3. Enter the following values for the rule:

        • Stateless: Leave the check box cleared.
        • Source Type: CIDR
        • Source CIDR: 0.0.0.0/0
        • IP Protocol: RDP (TCP/3389)
        • Source Port Range: All
        • Destination Port Range: 3389
        • Description: An optional description of the rule.
      4. When done, click Add Ingress Rules.

To create a Windows instance

  1. Open the navigation menu. Under Core Infrastructure, go to Compute and click Instances.
  2. Select a Compartment you have permission to work in.

    By default, the instance launches in the current compartment. The other resources that you choose can come from different compartments.

  3. Click Create Instance.
  4. Enter a name for the instance. You can add or change the name later. The name doesn't need to be unique, because an Oracle Cloud Identifier (OCID) uniquely identifies the instance.

    Important

    Use only these ASCII characters in the instance name: uppercase letters (A-Z), lowercase letters (a-z), numbers (0-9), and hyphens (-). See this known issue for more information.
  5. In the Image or operating system section, you choose the image  that's used to boot the instance. Click Change Image. The following options are available:

    • Platform Images: Pre-built images for Oracle Cloud Infrastructure. For more information about platform images, see Oracle-Provided Images.
    • Oracle Images: Pre-built Oracle enterprise images and solutions enabled for Oracle Cloud Infrastructure.
    • Partner Images: Trusted third-party images published by Oracle partners. Click the down arrow in the row for an image to view additional details about the image, or to change the image build. For more information, see Overview of Marketplace and Working with Listings.
    • Custom Images: Custom images created or imported into your Oracle Cloud Infrastructure environment. For more information, see Managing Custom Images.
    • Boot Volumes: Boot volumes that are available for creating a new instance in your Oracle Cloud Infrastructure environment. For more information, see Boot Volumes.
    • Image OCID: Create an instance using a specific version of an image by providing the image OCID . To determine the image OCID for Oracle-provided images, see Oracle-Provided Image Release Notes.

    Choose an image or boot volume, and then click Select Image or Select Boot Volume.

  6. Click Show Shape, Network and Storage Options.
  7. Select the Availability domain that you want to create the instance in.

    Note

    If you're creating an instance from a boot volume, you must create the instance in the same availability domain as the boot volume.
  8. In the Shape section, click Change Shape. Then, do the following:

    1. In the Instance type section, select Virtual Machine or Bare Metal Machine.
    2. If you're creating a virtual machine, in the Shape series section, select a processor group, and then choose a shape . The following options are available:

      • AMD Rome: The flexible shape, which uses the current generation AMD processor and has a customizable number of OCPUs. For Select the number of OCPUs, choose the number of OCPUs that you want to allocate to this instance by dragging the slider. The amount of memory and other resources scale proportionately.
      • Intel Skylake: Standard shapes that use the current generation Intel processor and have a fixed number of OCPUs.
      • Specialty and Legacy: Standard shapes with previous generation Intel and AMD processors, the Always Free VM.Standard.E2.1.Micro shape, Dense I/O shapes, GPU shapes, and HPC shapes.

      If a shape is disabled, it means that the shape is either incompatible with the image that you selected previously, or not available in the current availability domain. If you don't see a shape, it means that you don't have service limits for the shape. You can request a service limit increase.

      For more information about shapes, see Compute Shapes.

    3. Click Select Shape.
  9. In the Configure networking section, configure the network details for the instance:

    • Virtual cloud network compartment: The compartment containing the network in which to create the instance.
    • Virtual cloud network: The network in which to create the instance.
    • Subnet compartment: The compartment containing a subnet within the cloud network to attach the instance to.
    • Subnet: A subnet within the cloud network to attach the instance to. The subnets are either public or private. Private means the instances in that subnet can't have public IP addresses. For more information, see Access to the Internet. Subnets can also be either AD-specific or regional (regional ones have "regional" after the name). We recommend using regional subnets. For more information, see About Regional Subnets.
    • Use network security groups to control traffic: Select this check box to add the instance's primary VNIC  to at least one network security group (NSG) of your choice. NSGs have security rules that apply only to the VNICs in that NSG. For more information, see Network Security Groups.
    • If the subnet is public, you can optionally assign the instance a public IP address. A public IP address makes the instance accessible from the internet. Select the Assign a public IP address option. For more information, see Access to the Internet.

  10. In the Boot volume section, configure the size and encryption options for the instance's boot volume:

    • To specify a custom size for the boot volume, select the Specify a custom boot volume size check box. Then, enter a custom size from 50 GB (256 GB for Oracle-provided Windows images) to 32 TB. The specified size must be larger than the selected image's default boot volume size. See Custom Boot Volume Sizes for more information.
    • For VM instances, you can optionally select the Use in-transit encryption check box. See Block Volume Encryption for more information. If you are using your own Vault service encryption key for the boot volume, then this key is also used for in-transit encryption. Otherwise, the Oracle-provided encryption key is used.
    • Boot volumes are encrypted by default, but you can optionally use your own Vault service encryption key to encrypt the data in this volume. To use the Vault service for your encryption needs, select the Encrypt this volume with a key that you manage check box. Then, select the Vault compartment and Vault that contain the master encryption key you want to use. Also select the Master encryption key compartment and Master encryption key. For more information about encryption, see Overview of Vault.
    • The Block Volume elastic performance feature lets you change the volume performance for boot volumes. When you create an instance, its boot volume is configured with the default volume performance set to Balanced. After you launch the instance, you can modify the performance setting. For steps to modify the performance setting, see Changing the Performance of a Volume. For more information about this feature, see Block Volume Elastic Performance.

  11. Skip the Add SSH keys section. An SSH key pair is only required for Linux instances. For Windows instances, you connect to the instance using a password. An initial password will be provided when you finish launching the instance.
  12. (Optional) To configure advanced networking and management settings, click Show Advanced Options. The following options are available:

    • On the Management tab, you can configure the following:

      • Choose a compartment for your instance: The compartment that you want to launch the instance in.
      • Choose a fault domain: The fault domain to use for the instance. If you do not specify the fault domain, the system selects one for you. The fault domain cannot be changed after you create the instance. If you want to use a different fault domain, you must terminate the instance and launch a new instance in the preferred fault domain. For more information, see Fault Domains and Best Practices for Your Compute Instance.
      • Initialization Script: User data to be used by cloudbase-init to run custom scripts or provide custom cloudbase-init configuration. Browse to the file that you want to upload, or drag and drop the file into the box. The file or script does not need to be base64-encoded, because the Console performs this encoding when the information is submitted. For information about how to take advantage of user data, see the cloudbase-init documentation. The total maximum size for user data and other metadata that you provide is 32,000 bytes.

        Warning

        Do not include anything in the script that could trigger a reboot, because this could impact the instance launch and cause it to fail. Any actions requiring a reboot should only be performed once the instance state is RUNNING.
      • Enable monitoring: Select this check box to collect metrics for this instance. When enabled, the Oracle Cloud Agent software on the instance emits metrics for this instance to the Monitoring service using the oci_computeagent metric namespace.

        This option is available for supported images only. If you use a legacy version of a supported image, you might also have to install the Oracle Cloud Agent software. For more information, see Enabling Monitoring for Compute Instances.

      • Use Oracle Cloud Agent to manage this instance: Select this check box to let Oracle Cloud Agent automate operational tasks for the instance, such as installing patches. For more information, see OS Management.
      • Tags: Optionally, you can apply tags. If you have permissions to create a resource, you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator.
    • On the Networking tab, you can configure the following:

      • Private IP address: An available private IP address of your choice from the subnet's CIDR. If you don't specify a value, the private IP address is automatically assigned.
      • Hostname: A hostname to be used for DNS within the cloud network. Available only if the VCN and subnet both have DNS labels. For more information, see DNS in Your Virtual Cloud Network.
      • Launch Options: The networking launch type. Available only for VMs. For more information, see Recommended Networking Launch Types.
    • On the Image tab, you can change the image build. By default, the latest build of the image is used to create the instance. You can select an older build of the image that is compatible with the shape you selected. Only compatible image builds are displayed in the list. You must select a shape before you can change the image build.
    • On the Host tab, you can choose to launch the instance on a dedicated virtual machine host. This lets you run the instance in isolation, so that it is not running on shared infrastructure. To do this, select the Launch the virtual machine on a dedicated host check box, and then select a dedicated virtual machine host from the drop-down list. Before you can place an instance on a dedicated virtual machine host, you must create a dedicated virtual machine host in the same availability domain and fault domain as the instance. You can only place an instance on a dedicated virtual machine host at the time you create the instance. For more information, see Dedicated Virtual Machine Hosts.
  13. Click Create.

    To track the progress of the operation, you can monitor the associated work request. For more information, see Using the Console to View Work Requests.

After the instance is provisioned, details about it appear in the instance list. To view additional details, including IP addresses and the initial Windows password, click the instance name.

When the instance is fully provisioned and running, you can connect to it using Remote Desktop as described in Connecting to an Instance.

You also can attach a volume to the instance, provided the volume is in the same availability domain. For background information about volumes, see Overview of Block Volume.

For steps to let additional users connect to the instance, see Adding Users on an Instance.

Managing Tags for an Instance

You can add tags to your resources to help you organize them according to your business needs. You can add tags at the time you create a resource, or you can update the resource later with the desired tags. For general information about applying tags, see Resource Tags.

To manage tags for an instance
  1. Open the navigation menu. Under Core Infrastructure, go to Compute and click Instances.
  2. Click the instance that you're interested in.

  3. Click the Tags tab to view or edit the existing tags. Or click More Actions, and then click Add tags to add new ones.

Using the API

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

Use these API operations to manage instances:

You can also launch instances from images that are published by Oracle partners in the Partner Image catalog. Use these APIs to work with the Partner Image catalog listings: