Oracle Cloud Infrastructure Documentation

Creating an Instance

You can create an instance using the Console or API. When you create an instance, it 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 either let the IP address be automatically assigned, or specify a particular address of your choice. The private IP address lets instances within the cloud network communicate with each other. They can instead use fully qualified domain names (FQDNs) if you've set up the cloud network for DNS (see DNS in Your Virtual Cloud Network).

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 RDP connection to the instance from outside the cloud network. For more information, see Access to the Internet.

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.

Note

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

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 An IAM document that specifies who has what type of access to your resources. It is used in different ways: to mean an individual statement written in the policy language; to mean a collection of statements in a single, named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall body of policies your organization uses to control access to resources. 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 A collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization. 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 A collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization. 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 managing 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).

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.

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.

Recommended Networking Launch Types

When you launch a virtual machine (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 Type 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.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 2016: Images published in August 2019 or later.

SR-IOV networking is supported on all Oracle-provided images.

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.

Using the Console

To create a Linux instance
To create a Windows instance

Managing Tags for an Instance

You can apply tags to your resources, such as instances, to help you organize them according to your business needs. You can apply tags when you create an instance, or you can update the instance later with the tags that you want.

To manage tags for an instance

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:

Oracle Cloud Infrastructure enables you to launch instances from images published by Oracle partners from the Partner Image catalog. Use these APIs to work with the Partner Image catalog listings: