Creating an Instance Using QuickStarts

You can use QuickStarts to quickly create an instance using a default configuration.

Prerequisites

Procedure

  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. On the Instances page, click Create Instance.
    The QuickStarts page appears.
  3. Specify a name for the instance or use the default value. Names can contain only alphanumeric characters, hyphens, and underscores. The first and last characters cannot be hyphen or underscore.
  4. 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.
  5. Select the IP network that you want to add your instance to.
  6. Select an existing SSH public key, or create an SSH key pair and download the SSH private key. Save the private key on your local system and make a note of the path where you’ve saved it. You’ll need the private key later, when you log in to the instance.

    Note:

    If you download the SSH key, you can use it to access your instance from UNIX and UNIX-like systems. If you want to access your instance by using PuTTY on Windows, generate the SSH key using PuTTY and add the SSH public key to your Compute Classic account.

    Note:

    If you select a Windows image, you don’t need an SSH key. Enter the administrator password instead. You’ll use this password to access the Windows instance using RDP later.

  7. Click Create.
    The QuickStarts instance is created. 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.

A QuickStarts 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.

    • (Available only on Oracle Cloud at Customer) Has one interface on an IP network with the same name and is added to a vNICset of the same name.

    • (Not available on Oracle Cloud at Customer) Has one interface on the default IP network and is added to a vNICset of the name which is same as the name of the instance.

    • 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 or RDP 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 or RDP 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.

Tip:

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.