| _key | core | string | |
| agent_config | core | json | |
| availability_config | core | json | |
| availability_domain | core | string | The availability domain the instance is running in.Example: `Uocm:PHX-AD-1` |
| capacity_reservation_id | core | string | The OCID of the compute capacity reservation this instance is launched under.When this field contains an empty string or is null, the instance is not currently in a capacity reservation.For more information, see [Capacity Reservations](/iaas/Content/Compute/Tasks/reserve-capacity.htm#default). |
| cluster_placement_group_id | core | string | The OCID of the cluster placement group of the instance. |
| compartment_id | core | string | The OCID of the compartment that contains the instance. |
| dedicated_vm_host_id | core | string | The OCID of the dedicated virtual machine host that the instance is placed on. |
| fault_domain | core | string | The name of the fault domain the instance is running in.A fault domain is a grouping of hardware and infrastructure within an availability domain.Each availability domain contains three fault domains. Fault domains let you distribute yourinstances so that they are not on the same physical hardware within a single availability domain.A hardware failure or Compute hardware maintenance that affects one fault domain does not affectinstances in other fault domains.If you do not specify the fault domain, the system selects one for you.Example: `FAULT-DOMAIN-1` |
| id | core | string | The OCID of the instance. |
| image_id | core | string | Deprecated. Use `sourceDetails` instead. |
| instance_options | core | json | |
| ipxe_script | core | string | When a bare metal or virtual machineinstance boots, the iPXE firmware that runs on the instance isconfigured to run an iPXE script to continue the boot process.If you want more control over the boot process, you can provideyour own custom iPXE script that will run when the instance boots.Be aware that the same iPXE script will runevery time an instance boots, not only after the initialLaunchInstance call.The default iPXE script connects to the instance's local bootvolume over iSCSI and performs a network boot. If you use a custom iPXEscript and want to network-boot from the instance's local boot volumeover iSCSI the same way as the default iPXE script, use thefollowing iSCSI IP address: 169.254.0.2, and boot volume IQN:iqn.2015-02.oracle.boot.If your instance boot volume attachment type is paravirtualized,the boot volume is attached to the instance through virtio-scsi and no iPXE script is used.If your instance boot volume attachment type is paravirtualizedand you use custom iPXE to network boot into your instance,the primary boot volume is attached as a data volume through virtio-scsi drive.For more information about the Bring Your Own Image feature ofOracle Cloud Infrastructure, see[Bring Your Own Image](/iaas/Content/Compute/References/bringyourownimage.htm).For more information about iPXE, see http://ipxe.org. |
| launch_mode | core | string | Specifies the configuration mode for launching virtual machine (VM) instances. The configuration modes are:* `NATIVE` - VM instances launch with iSCSI boot and VFIO devices. The default value for platform images.* `EMULATED` - VM instances launch with emulated devices, such as the E1000 network driver and emulated SCSI disk controller.* `PARAVIRTUALIZED` - VM instances launch with paravirtualized devices using VirtIO drivers.* `CUSTOM` - VM instances launch with custom configuration settings specified in the `LaunchOptions` parameter. |
| launch_options | core | json | |
| lifecycle_state | core | string | The current state of the instance. |
| oci_display_name | core | string | A user-friendly name. Does not have to be unique, and it's changeable.Avoid entering confidential information. |
| platform_config | core | json | |
| preemptible_instance_config | core | json | |
| region | core | string | The region that contains the availability domain the instance is running in.For the us-phoenix-1 and us-ashburn-1 regions, `phx` and `iad` are returned, respectively.For all other regions, the full region name is returned.Examples: `phx`, `eu-frankfurt-1` |
| security_attributes_state | core | string | The lifecycle state of the `securityAttributes` |
| shape | core | string | The shape of the instance. The shape determines the number of CPUs and the amount of memoryallocated to the instance. You can enumerate all available shapes by calling[ListShapes](#/en/iaas/latest/Shape/ListShapes). |
| shape_config | core | json | |
| source_details | core | json | |
| tags | core | hstore | |
| tenancy_ocid | core | string | |
| time_created | core | timestamp | The date and time the instance was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).Example: `2016-08-25T21:10:29.600Z` |
| time_maintenance_reboot_due | core | timestamp | The date and time the instance is expected to be stopped / started, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).After that time if instance hasn't been rebooted, Oracle will reboot the instance within 24 hours of the due time.Regardless of how the instance was stopped, the flag will be reset to empty as soon as instance reaches Stopped state.Example: `2018-05-25T21:10:29.600Z` |