Expert Mode: Launching Instances Using Cockpit

Using Cockpit, you can launch one or more fully custom instances in the public Cloud or in a Virtual Private Cloud (VPC).

The Basic, Advanced and Expert Modes enable you to define different attributes of the instances, but only the Expert Mode enables you to launch several instances in the same launch request. These instances are grouped within a same reservation.

Open the Create Instance Window

  1. Click Compute > Instances.

  2. Click Create > Expert Mode.
    The CREATE INSTANCE window appears.

    You can also click the OMI from which you want to launch instances in the Outscale Machine Images page, and then click Create Instance . The CREATE INSTANCE window appears with the selected OMI.

Configure Your Instance

Choose a Name, Tenancy Option, and Shutdown Behavior

  1. (optional) In the Instance name field, type a name for your instances.

    This name must contain between 1 and 255 ASCII printable characters.

    This name is used as a tag associated with your instance.

  2. (optional) Check the Tenancy box to launch dedicated instances.
    For more information, see About Instances.

  3. (optional) Select one of the following values from the Shutdown behavior option list:

    • Stop: When you initiate shutdown, the instances stop.

    • Terminate: When you initiate shutdown, the instances stop and are terminated.

    • Restart: When you initiate shutdown, the instances stop then automatically restart.

  4. Click Next.
    The OMI selection screen appears.

Choose an OMI

  1. Select an OMI for your instances.

  2. Click Next.
    The Instance type selection screen appears.

Choose an Instance Type and the Number of Instances

  1. In the OUTSCALE Instance Type section, specify the following attributes for your instances:

    • CPU: The processor generation.

    • Performance: The performance flag. For more information, see 3DS OUTSCALE’s Offering Refinements FAQ.

    • Core(s): The number of vCores, up to 78.

    • Memory (GiB): The amount of memory, up to 1039 GiB.

    For more information about instance types, see Instance Types.

    To function properly, Windows instances require at least a v3 processor generation, 2 vCores, and 4 GiB of memory.

  2. In the Number of Instances section, specify the number of instances you want to launch.

    You can launch up to 20 instances at a time.

  3. Click Next.
    The VPC screen appears.

Choose the Public Cloud or a VPC and an AZ

  1. If you want to launch instances in the public Cloud:

    1. Leave No VPC selected.

    2. Select the AZ where you want to launch your instances.

      When launching instances in the public Cloud, you cannot define the private IP of the instances.

  2. If you want to launch instances in a VPC:

    1. Select a VPC.

    2. Select one of the subnets of the VPC.

    3. (optional) In the Private IP field, if you are launching one instance only, type the private IP address for the instance, within the IP address range of the subnet.

      When you launch instances in a VPC using the Expert mode:

      • Only the AZ of the chosen subnet is listed.

      • Flexible network interfaces (FNIs) are automatically created and attached to the instances.

  3. Click Next.
    The Security group screen appears.

Choose Security Groups

  1. If you want to assign one or more existing security groups to your instances, select them from the list.

    This list depends on the choice you made in the Public/Private Cloud screen. If you chose a VPC, only the security groups of the chosen VPC are listed.

  2. To create a new security group to assign to the instances:

    1. In the Name field of the New Security Group section, type a name for the security group.

    2. In the Description field, type its description.

      • The name must be unique in your account for the public Cloud or for each VPC.

      • The name of the security group must not start with sg-.

      • Each name and description can contain between 1 and 255 characters. Allowed characters are a-z, A-Z, 0-9, spaces, and _.-:/()#,@[]+=&;\{}!$*.

  3. Click Next.
    The Keypair screen appears.

    If you do not choose any security group, the default security group of the account or VPC is assigned to the instances.

Choose a Keypair

  1. If you want to assign an existing keypair to your instances, select it from the list.

    If you have set a default keypair in the Settings page of Cockpit, it is pre-selected.

  2. If you want to create a new keypair to assign to your instances, type a name for the keypair in the Name field of the New Keypair section.

  3. Click Next.
    The User Data screen appears.

    In Expert Mode, you can launch an instance without assigning any keypair to it. However, all official OMIs use keypairs as their authentication system. Therefore, if you want to be able to access an instance launched from an official OMI, you need to assign it a keypair either during this step or later. To assign a keypair later, see Modifying an Instance Attribute.

Specify User Data

  1. (optional) Type user data for the instances in the User Data fields.
    For more information, see Configuring an Instance with User Data and OUTSCALE Tags.

    Cockpit then encodes this user data to Base64. The maximum size for the Base64-encoded user data is 500 kibibytes (KiB).

  2. Click Next.
    The Summary screen appears.

Confirm the Launch

  1. Review the settings you have specified for the instances.

  2. Click Create to validate.
    The instances are launched.

    If you have created a keypair, you are prompted to download a file containing the private key of the keypair. Save this file carefully, as it is required to connect to your instances. 3DS OUTSCALE cannot provide any copy in case of loss.

Related Pages