Creating an Instance
 Configuration by Entering Configuration Values.

Avoid entering confidential information in names and tags.

Console
CLI
API

Create or get the following resources and information:

An image or boot volume and the compartment where the image or boot volume is located

A virtual cloud network (VCN) and subnet and the compartment where the VCN and subnet are located

A public Secure Shell (SSH) key if users will connect to the instance using SSH

On the Compute Cloud@Customer Console Dashboard, do one of the following to open the Create Instance dialog box:

Click Compute/Create Virtual Machine Instance.

Click Compute/View Images. For the image that you want to use to create the instance, click Actions menu (), then click the Create Instance From Image. You might have to change the compartment at the top of the image list to see the image you want.

When you use the Create Instance From Image option, the image name is already entered in the Create Instance dialog box and you can't change it. You don't need to enter any of the information described in "Source Image" in the following step.

In the Create Instance dialog box, enter the following information:

Name: Enter a name for the instance. Instance names have the following characteristics:

Can be changed after the instance is created.

Doesn't need to be unique.

Can contain only alphanumeric characters and the hyphen (-) character.

Can be a maximum of 63 characters.

Create in Compartment: Select the compartment where you want to create the instance.

Fault Domain: (Optional) Select a fault domain. By default, the system automatically selects the best fault domain for the instance when the instance is created. If you specify a fault domain, and the requested fault domain cannot accommodate the instance, instance launch fails. The fault domain can be changed after the instance is created.

Source Image: Select an image or boot volume.

Select the Source Type: Platform Image, Custom Image, or Boot Volume.

If you selected Custom Image or Boot Volume, select the compartment where the image or boot volume that you want to use is located.

Select an image or boot volume from the list.

If you selected Platform Image, you see a tabular list with columns Operating System, OS Version, and Image Build (the date the image was built). You can use the drop-down menu arrow to the right of the OS Version to select a different version. For example, for the Oracle Linux operating system, you can use the drop-down menu to select 9, 8, or 7.9.

If you selected Custom Image, you see a tabular list with columns Name, Operating System, and OS Version. You can use the arrows in the column headings to sort the list. You can filter the list by using the Operating System drop-down menu above the list of images.

If you selected Boot Volume, you see a tabular list with columns Name, Size (GB), and Created (the date the boot volume was created). You can use the arrows in the column headings to sort the list. In the Boot Volume section (after the Shape section), you can customize the boot volume size.

If the list is too long to fit in one view, use the arrow to view another page of the list.

To use a platform image that was previously available but is no longer listed, use the CLI to create the instance and specify the OCID of the image.

The source image can't be changed after the instance is created.

Shape: If you're using a platform image, select the VM.PCAStandard.E5.Flex shape, and configure the number of OCPUs and memory.

For the OCPU and memory values, click inside each value field to see the minimum and maximum allowed values. The OCPU and memory configuration can be changed after the instance is created.

For a description of the supported shape, see Compute Shape.

Boot Volume: (Optional) Check the box to specify a custom boot volume size or volume performance setting.

Boot volume size (GB): The default boot volume size for the selected image is shown. To specify a larger size, enter an integer of gigabytes up to 16384 GB (16 TB) or use the increment and decrement arrows. You can't enter a value smaller than the default.

Boot volume performance (VPUs): Use the increment and decrement arrows to toggle between balanced performance (10 VPUs/GB) and high performance (20 VPUs/GB). For more information see Block Volume Performance Options.

Subnet: Select a subnet.

Select a VCN from the list. You might need to change the compartment to the compartment where the VCN is located.

Select a subnet.

Public IP Address: To connect to the instance using SSH, check the Assign Public IP box to have a public IP address assigned to the instance. This box is checked by default if you specified a public subnet. If you don't check this box, or if you clear this box, and then want to assign a public IP address later, see Assigning an Ephemeral Public IP Address to an Instance for instructions.

Private IP Address: (Optional) Specify an available private IP address from the subnet's CIDR. By default, a private IP address is automatically assigned.

Hostname: (Optional) Enter a hostname if you're using DNS within the cloud network. The hostname must be unique across all VNICs in the subnet.

By default, the instance name is used for the hostname. The hostname can also be configured in the OS after the instance is created.

If this is a UNIX instance, see Creating a Mount Target and Mounting File Systems on UNIX-based Instances for more information about setting the host name correctly for mounting file systems.

SSH Keys: To connect to the instance using SSH, provide a public SSH key.

 Note



You can't provide this SSH key after the instance is created.

Initialization Script: (Optional) Provide an initialization script. This is a file of data to be used for custom instance initialization.

Network Security Group: (Optional) By default, the new instance isn't attached to any NSG. Check the box labeled Enable Network Security Group to add the primary VNIC for this instance to one or more NSGs.

Select an NSG from the drop-down list. You might need to change the compartment to find the NSG you want.

Click Add Another NSG if you want to attach to another NSG.

To remove an NSG from the list, click the trash can to the right of that NSG. To remove the last NSG or all NSGs, clear the Enable Network Security Groups box.

To update NSG attachments for this instance later, see Updating a VNIC.

See Controlling Traffic with Network Security Groups for information about NSGs.

Instance Options: Check the box to disable Legacy Instance Metadata Service Endpoints. By default, legacy (/v1) Instance Metadata Service (IMDS) routes are enabled. If you have upgraded your applications to use /v2 endpoints, check this box to disable /v1 endpoints. For more information about the Instance Metadata Service, see Retrieving Instance Metadata from Within the Instance. For more information about upgrading your applications, see Upgrading to IMDS Version 2 Endpoints.

Availability configuration: (Optional) Check the "Restore instance lifecycle state after infrastructure maintenance" box to specify that running instances should be automatically restarted after a maintenance operation such as live migration. This is the default. If this box isn't checked, the instance is recovered in the stopped state.

Tagging: Optionally, add one or more tags to this resource. If you aren't sure whether to apply tags, skip this option (you can apply tags later). For more information about tagging resources, see Resource Tags.

Click Create Instance.

On success, the instance details page is displayed. On the Configuration tab, the Shape Configuration column shows the shape, the number of OCPUs, the network bandwidth, and the total memory. On the Networking tab, the VNIC column shows the VCN and subnet, and the Instance Access column shows the primary private IP address and any assigned public IP address.

To check the status of the instance launch, scroll to the Resources section and click Work Request(s).

If instance launch fails because of resource constraints, try remedies such as the following:

Specify a different fault domain, or don't specify any fault domain and allow the system to choose it.

Specify a less resource-intensive shape.

Stop an instance that you no longer need .

Terminate an instance that you no longer need.

If the status of the work request is Failed, and no reason is listed for the failure, the cause of the failure might be temporary. Wait a short time and then retry the instance create.



For more information click here https://docs.oracle.com/en-us/iaas/compute-cloud-at-customer/topics/compute/creating-an-instance.htm#creating-an-instance