HomeComputeInstancesHow to
Create an Instance
Update content

How to create an Instance

Reviewed on 16 June 2023Published on 26 May 2021

This page shows how to create your first Scaleway Instance. An Instance is a virtual machine in the cloud. Just like a physical machine, it has resources - virtualized CPU, RAM, storage etc. - which vary depending on the Instance type you choose. After you have created your Instance you can connect to it and use it for a wide range of computing use cases depending on the Instance type you chose, from running small scale tests and personal projects, to hosting applications and development environments, to setting up a production server.

Security & Identity (IAM):

You may need certain IAM permissions to carry out some actions described on this page. This means:

  • you are the Owner of the Scaleway Organization in which the actions will be carried out, or
  • you are an IAM user of the Organization, with a policy granting you the necessary permission sets

Select a tab below for instructions on how to create an Instance via either our console, our API, or our CLI.

  1. Click Instances in the Compute section of the side menu. The Instance creation wizard displays.


    If you have existing Instances in your account, you will see a list of these Instances instead of the Instance creation page, and the «Plus Icon» button for creating new Instances.

  2. Click Create Instance. The Instance creation wizard displays.

  3. Complete the following steps in the wizard:

    • Choose an Availability Zone, which is the geographical region where your Instance will be deployed.
    • Choose an Instance type. Different Instance types have different prices, processing power, memory, storage options and bandwidth. See our dedicated documentation to help choose the best Instance type for your needs.
    • Choose an Image to run on your Instance. This can be an operating system, an InstantApp or a custom image. A complete list of all available Linux distributions and InstantApps can be found here.

    When choosing an image for an Enterprise Instance, be aware this Instance type is not compatible with bootscripts, except for rescue mode. InstantApps are also not available for this Instance type.

    • Add Volumes. Volumes are storage spaces used by your Instances.
      • For GP1 Instances you can leave the default settings of a maximum local storage, or choose how much local and/or block storage you want. Your system volume is the volume on which your Instance will boot. The system volume can be either a local or a block volume.
      • PLAY2, PRO2, and Enterprise Instances boot directly on block volumes. You can add several block volumes and define how much storage you want for each.

    Note that:

    • a volume with an OS image should be at least 10 GB (125 GB for a GPU OS).
    • if several Block Storage volumes are connected to your Instance, the first volume will contain the OS and is required to boot the Instance. You can change your boot volume after you create the Instance.
    • if you have two or more volumes with identical operating systems, or a volume with no operating system, choosing one of these as your boot volume may cause unpredictable boot behavior.
    • Enter a Name for your Instance, or leave the randomly-generated name in place. Optionally, you can also add tags to help you organize your Instance.
    • Click Advanced options if you want to configure a flexible IP, a local bootscript or a cloud-init configuration. Otherwise, leave these options at their default values.
    • Verify the SSH keys that will give you access to your Instance.
    • Verify the Estimated cost of your Instance, based on the specifications you chose.
  4. Click Create Instance to finish. The creation of your Instance begins, and you will be informed when the Instance is ready.

    Your Instance is now created, and you are redirected to the Overview tab. From here, you can see information including your Instance’s Public IP, the SSH command to use to connect to it, and other information, settings, and actions for the Instance.

See Also