Overview

To assign an IPv6 address to an instance, your instance must be connected to a network that has an IPv6-enabled subnet and is attached to a router.

If your instance was created before IPv6 was enabled on the network, you may need to reboot the instance for it to obtain an IPv6 address.

Prerequisites

Before your instance can receive an IPv6 address, ensure the following:

• A network has been created.
• The network includes an IPv6 subnet.
• A router is attached to the network.
• Your instance is connected to this network.

Scenario 1: Creating a New Instance with IPv6

If you are launching a new instance:

1. Create a network.
2. Create an IPv6 subnet on the network.
3. Attach the network to a router.
4. Launch the instance and select the IPv6-enabled network.

The instance will automatically receive an IPv6 address during provisioning.

Scenario 2: Enabling IPv6 on an Existing Network

If your instance already exists and you later add an IPv6 subnet to its network:

1. Add an IPv6 subnet to the existing network.
2. Ensure the network is connected to a router.
3. Reboot the instance.

After the reboot, the instance will request network configuration again and should receive an IPv6 address.

Verify the IPv6 Address

After the instance has started (or restarted):

1. Open the Instance Details page.
2. Check the Network section.

If configured correctly, an IPv6 address will be displayed alongside the instance’s IPv4 address (if applicable).

There are two ways to create a network in Public Cloud:

1. From the Networks page
   • Navigate to Public Cloud.
   • Select Networks from the submenu.
   • Click Create Network.
2. During Instance Creation
   • While launching a new instance, you can create and attach a network as part of the deployment process.

Filling in the Create Network Fields

1. In the Leaseweb Customer Portal, navigate to your Public Cloud section
2. Go to the Networks page:
   • Navigate to Public Cloud.
   • Select Networks from the submenu.
   • Click Create Network.

3. Fill in the details as follows:

Best Practice

For most users, the recommended configuration is:

After a network is created, it can be used when launching instances, allowing them to connect to the network. If external connectivity is required, the network can also be attached to a router.

What is Extended Lifecycle Support?

When an operating system (OS) reaches its End-of-Life (EOL) date, the vendor stops issuing security updates, leaving servers and virtual machines on that OS more exposed to vulnerabilities. 

WebPros, the company behind Plesk and cPanel, runs an Extended Lifecycle Support (ELS) program for affected OS versions. This gives customers additional time to plan an upgrade while continuing to receive critical security updates. 

How ELS fees work

Where an ELS program is active, an additional monthly fee applies per control panel license on the affected OS. Leaseweb passes this fee through to customers and it appears as a separate line item on your invoice. 

New ELS fees can be introduced, or prices can be adjusted on a half-yearly or annual basis. Leaseweb will communicate any changes in advance via email. 

Affected operating systems

cPanel

Plesk

How to avoid ELS fees

Upgrading to a supported OS is the only way to remove the ELS fee from your invoice. Leaseweb strongly recommends doing this as soon as possible, as running an EOL OS carries security risks regardless of the ELS program, and fees may increase over time. 

For a list of currently supported operating systems, refer to the official documentation for Plesk and cPanel. 

Projects help you organize resources, users, and access permissions within your Public Cloud environment, which is why you will automatically have a Default Project created for your account.

How to Create a New Project

You can create up to 3 projects per account, including the default project that is created automatically:

1. Open the Project dropdown in the top navigation.
2. Click New Project.
   • You will be redirected to the Project Settings page.

3. Enter:
   • Project Name: A unique name for your project.
   • Description: Optional information describing the purpose of the project.
4. Click Create Project.

How to Manage Projects

The Project Settings page allows you to manage all project-related resources and permissions. Within a project, you can view and manage project quotas, SSH keys and users.

How to Manage Project Quotas

Project quotas define the resources available to the project, such as:

• vCPUs
• RAM
• Volumes

These quotas determine how many resources can be created within the project. Each project comes with the following default resource quotas:

These quotas define the maximum amount of compute, memory, and storage resources that can be allocated within a project. If you require additional resources, you can request a quota increase through our support, by opening a ticket from the Customer Portal.

To increase your quotas, go to Settings, select the project for which you want to increase the quotas, and click Increase Quotas.

A new pop-up will appear, where you can specify the quota limits you would like to set for your project.

After your request has been reviewed, you will receive a confirmation in the ticket.

How to Manage SSH Keys

SSH keys can be managed at the project level and are used to securely access instances created within that project.

From the SSH Keys section, you can:

• View existing SSH keys
• Add new SSH keys
• Remove unused SSH keys

How to Manage Project Users

Users determine who can access and manage resources within a project.

To use the OpenStack API, you must first create a user account. Each user has their own credentials for authenticating with the API and managing resources.

You can create multiple users to collaborate within the same project.

From the Users section, you can:

• View project members
• Add users to the project
• Remove users from the project

Example Project Use Cases

You may choose to separate workloads into different projects, for example:

Using separate projects helps keep resources organized while providing clear visibility into quotas, users, and access management.

When accessing a server’s iLO 3 web portal or virtual console, you may run into browser compatibility problems, firmware quirks, or access-related issues. This article walks you through the step‑by‑step process of connecting to an iLO 3 controller via its web interface and launching the embedded remote console.

It covers the prerequisites you need before you can start:

• How to connect to the remote management VPN
• How to locate your user credentials
• Meet the required browser and Java specifications
• Troubleshoot common connection errors and apply quick‑fix work‑arounds.

By the end of this article, you will be able to:

• Access the iLO 3 GUI securely from any workstation connected to the remote management virtual private network
• Open the virtual console to perform BIOS configuration, OS installation, or hardware diagnostics without physical presence
• Diagnose and resolve typical connectivity problems that prevent iLO 3 access.

What Is iLO3 and Why Is It Important

iLO 3 (Integrated Lights-Out 3) is a remote management technology used in HPE ProLiant servers that allows administrators to monitor and control hardware independently of the operating system. It provides out-of-band access for tasks like remote console access, power cycling, and system health monitoring, even when the server is turned off or unresponsive.

The remote access console allows you to work on your server as if you were sitting in front of it with a physical screen, monitor and keyboard. This makes it possible to make changes to your server before it boots, or inside its BIOS, which are generally not possible via SSH, RDP or other similar remote management methods.

Leaseweb Remote Management VPN

Before proceeding any further with this guide, make sure that you are connected to our isolated, secure, remote management VPN. Please follow these instructions in order to get connected. Once you are connected, you can proceed with this article.

How to Get Your IPMI IP Address and Credentials

To find the IP address and credentials that correspond to your servers IPMI / iLO 3 interface, follow the steps below:

1. Open the Leaseweb Customer Portal
2. Go to your server’s page under the Dedicated Servers option
3. Select Actions -> Remote Management

A window will appear in the center of your screen, similar to the one shown below. This window contains all the information you need to access your server’s IPMI/iLO 3 interface.

Here you will see the IPMI IP address, as well as a link that will load the web interface when clicked. You will also find the username and password (IPMI Credentials) that you will use to log in to the IPMI / iLO 3 interface. We will explain how to use these later in this article.

Back to the top ↑

How to Launch an IPMI Reset

If you are connected to the remote management VPN but cannot log in with your credentials, or the IPMI interface does not load in your browser, we recommend resetting the IPMI controller. Do this by performing an IPMI reset. Click on the launch an IPMI Reset link at the bottom of the window to proceed.

The IPMI reset job will reboot the server and PXE boot it into an automated live environment. During this process, the server’s IPMI/iLO 3 network settings will be reconfigured, and a new username and password will be generated. Once the reset is complete, the updated credentials will be available in your Customer Portal.

HPE Lights-Out Standalone Remote Console for Windows

For the best experience when accessing your server’s console, we recommend you use HPE Lights-Out Standalone Remote Console for Windows.

HPE Lights-Out Standalone Remote Console for Windows is a lightweight application developed by HP that can be installed on your Windows computer. It allows you to access and control your server’s console directly, without the need to use a web browser.

You can download it directly from the HP website. After downloading it, you can proceed to install it. Once the application is installed, you should find an icon like the one shown below on your desktop or in the Start menu under All Programs.

How to Connect to HPE Lights-Out Standalone Remote Console for Windows

1. Opening the program. You will see an interface like the one shown below:

2. To connect to your server’s console you will need your:
   • Network Address
   • Username
   • Password
3. Get these details by following the steps from How to Get Your IPMI IP Address and Credentials
4. Enter the details and click Connect

Once you are connected, you will see a screen similar to the one shown above. From here you can manage your sever just as if you were sitting physically in front of it with a screen, mouse and keyboard.

Back to the top ↑

iLO 3 Web Interface and Console via Browser

The Integrated Lights-Out 3 web interface allows you to manage your server. You can perform actions like shutdown and reboot your server, monitor the health of the hardware and temperature and so much more.

1. To access it, go to Actions -> Remote Management
2. Click on the Login to IPMI Interface button
   • Alternatively, you can enter the IPMI IP Address as a URL in your browser. In this example, the IP address is 10.59.65.25 so the URL would be https://10.59.65.25/

When the web interface successfully loads, you should see the login screen shown below.

iLO 3 TLS Errors

If you see an SSL/TLS error instead of the iLO 3 login screen, know that these errors are very common when accessing the iLO 3 web interface, especially on older hardware. Below are some of the most common SSL/TLS warnings and errors you may encounter.

Error 1: Potential Security Risk Ahead

The warning appears because the SSL certificate on the iLO3 does not match the address used to access it. Since the iLO3 interface is not publicly exposed, and should remain internal, a publicly trusted SSL certificate is not required.

The warning can be concerning, but it is merely informational and does not pose any danger to your IPMI / iLO 3 access.

To proceed past this error:

1. Click the Advanced button
2. Then select Accept the Risk and Continue

Different browsers may display slightly different buttons, but the process to resolve remains the same.

Error 2: This site can’t provide a secure connection

Some browsers may display a TLS error, as shown below, when accessing the iLO 3 web interface. iLO 3 no longer receives firmware updates and only supports TLS 1.1 or earlier, which can cause this error on modern browsers.

To bypass this error and access the web interface, you will need to temporarily enable TLS 1.1 in your browser. If you did not encounter this error when loading the iLO 3 web interface, you can proceed to the next step.

Back to the top ↑

Logging into iLo3

The username and password to log into iLO 3 can be found inside your Leaseweb Customer Portal – see here.

1. Enter your username and password
2. Click Log In to proceed

You will see the below overview. You can check the status of your server, On / Off, as well as the status of the hardware health.

Loading the Console Via the Web Interface

Before proceeding with this section, please make sure you have Java 8 or better installed on your system. You can download it from Java.com.

1. To open the console, click on the Java Web Start link
2. This will initiate a download. Once the download finishes, double-click on it to run it.

3. Click Continue to finalize the installation

Back to the top ↑

Java Security Errors

You may receive a Java security error message when attempting to launch the Java Web Start, which is very common and a result of Java’s strict security settings. Please follow this KB Article here to add the URL of your server’s IPMI interface into Java’s Exception Site List.

After clicking Continue above, you should see this message. Check off the checkbox to the left and click Run.

The below image confirms that you have successfully opened your server’s console via the web interface:

From this console you can make BIOS level changes and boot your server with custom images. Proceed to the next step to learn how to mount an ISO image.

How to mount an ISO

When managing a server, it is sometimes necessary to use an ISO image to boot the server into specialized software and tools, or to perform a custom operating system installation.

1. Open the console interface
2. Click on the Virtual Devices menu at the top
3. Click on Image File CD/DVD-ROM

4. Find and select the ISO image you need and click Open

5. Click on the Virtual Devices menu at the top once again to confirm your ISO image was successfully mounted, if you see a check mark next to Image File CD/DVD-ROM
   • If no check mark is shown, try again from step 2

6. Reboot the server -> click Keyboard -> CTRL-ALT-DEL. This will initiate a graceful reboot of your server

Back to the top ↑

Troubleshooting ISO Booting

If you successfully mounted an ISO but the server did not boot from it, the boot order may be configured to prioritize the server’s internal disk over the virtual CD-ROM drive. The cause could be that the server started the operating system that was already installed instead of booting from the mounted ISO.

1. To rearrange your boot order, reboot and press the F9 key as the server boots. This will take you into the BIOS menu

2. Go to the Standard Boot Order (IPL) section in the BIOS menu
   • You may notice that the CD-ROM device is set to 3 in the boot order, while the Hard Disk is set to 2. This means the Hard Disk has higher priority. If an operating system is already installed on the Hard Disk, the server will boot into it instead of the ISO you just mounted

3. Using the arrow keys move the CD-ROM option up to number 2
4. Press the ESC key followed by the ESC again to go to the main menu
5. Press F10 to Exit the BIOS menu and reboot.

Back to the top ↑

Alternatives for Custom OS Installation

If you experience issues installing the operating system using the ISO boot method, you can use the netboot.xyz option available through our automation.

Netboot.xyz uses PXE/network booting instead of booting directly from an ISO image. When the server boots from the network, netboot.xyz downloads the installation files and boot components required for the selected operating system directly from the configured repositories. This allows the operating system installation to proceed without mounting or booting from an ISO image.

1. Go to Actions -> Customer Installation
2. Select the boot file netboot.xyz menu
3. Check the Power cycle after the creation of the reservation box
4. Click Submit.

The server will reboot on the netboot.xyz boot file to load the neboot.xyz menu. If you chose to gracefully reboot your server, you could leave the power cycle after the creation of the reservation checkbox unchecked. Once netboot.xyz has booted it should look as shown below.

To learn more about netboot.xyz and other PXE boot option, check out this Knowledge Base article.

The OpenStack Command Line Interface (CLI) enables you to manage your Leaseweb Public Cloud resources directly from the terminal. Using the CLI, you can create and manage instances, networks, volumes, security groups, floating IPs, and other OpenStack resources without relying on the Customer Portal.

This guide walks you through installing the OpenStack CLI using either Python’s pip package manager or your operating system’s native package manager. It also explains how to configure authentication using a clouds.yaml file, connect to your Leaseweb Public Cloud project, and verify that your CLI is ready to use.

Install Openstack CLI

Via pip

Prerequisites:

• Your system must have Python 3 interpreter installed
• Your Python interpreter must have venv module installed

1. Create a python virtual environment in some folder:

python3 -m venv openstack-venv

2. Load the virtual environment:

. openstack-venv/bin/activate

3. Install python-openstackclient package:

pip install python-openstackclient

On Windows

Windows does not have the Python interpreter installed by default. Therefore, you should install it first, either inside WSL, or by downloading the installer from the official website: https://www.python.org/downloads/windows/

When installing, we advice you set the “Add python.exec to PATH” enabled, so you don’t have to type full path to python binary.

Once the python is installed, you may use the following commands to install python-openstackclient:

# Create virtual environment
python.exe -m venv openstack-venv

# Load it (you may need to run "Set-ExecutionPolicy -ExecutionPolicy RemoteSigned" in Powershell as Administrator
.\openstack-venv\Scripts\Activate.ps1

# Install python-openstackclient package
pip.exe install python-openstackclient

# Run openstack client
openstack

Via package manager

As the alternative for installing into a virtual environment directly from PyPi repository, you may use the openstack client packages most operating systems provide

Debian / Ubuntu

Install the python3-openstackclient package:

apt install python3-openstackclient

AlmaLinux / RockyLinux / Other RHEL-based

Install the python3-openstackclient package:

dnf install python3-openstackclient

Arch Linux

Install the python3-openstackclient package:

pacman -S python3-openstackclient

MacOS (Homebrew)

Install the openstackclient package:

brew install openstackclient

Connect to Leaseweb Public Cloud

Once the Openstack client is installed, you have to provide it with the clouds.yaml file with your credentials.

Obtain the credentials from Leaseweb Customer portal

1. Log in to the Leaseweb customer portal at https://secure.leaseweb.com
2. Navigate to the Public Cloud -> Settings page.
3. Switch to the Users tab and create a new user if necessary.
4. At the Projects tab, click Edit button next the project you want this user be member of.
5. Switch to the Users tab, and add your user to the project.

Once the user is created, take a note of the following items:

• Project name
• User name you have created
• The password for the user you have created
• Your customer ID: you can find it by clicking on the icon of your customer portal user in the top right corner of the page. This number is displayed under your company name.
• Availability zone name: it is displayed on the top right corner of most of the Public Cloud customer portal pages.

Create clouds.yaml file

Once you have all the credentials at hand, create the file ~/.config/openstack/clouds.yaml with the following content:

clouds:
  openstack:
    auth:
      auth_url: https://identity.leasewebcloud.com/v3
      username: "<the user you have created at previous step>"
      project_name: "<the name of the project>"
      project_domain_name: "<the customer ID you have obtained at previous step>"
      user_domain_name: "<the customer ID you have obtained at previous step>"
    region_name: "<the availability zone name, e.g. eu-west-3-az1>"
    interface: "public"
    identity_api_version: 3

Verify that the connection works:

openstack project list
# .. it should not return any error

Using clouds.yaml with multiple availability zones / regions

The clouds.yaml file allows storing multiple credentials in it so you don’t have to maintain multiple files with multiple regions, projects, and availability zones credentials. Simply define multiple credentials under the clouds: section:

clouds:
  az1-project1:
    auth:
      auth_url: https://identity.leasewebcloud.com/v3
      username: "<the user name>"
      project_name: "project1"
      project_domain_name: "1234567"
      user_domain_name: "1234567"
    region_name: "eu-west-3-az1"
    interface: "public"
    identity_api_version: 3
  az2-project2:
    auth:
      auth_url: https://identity.leasewebcloud.com/v3
      username: "<the user name>"
      project_name: "project2"
      project_domain_name: "1234567"
      user_domain_name: "1234567"
    region_name: "eu-west-3-az2"
    interface: "public"
    identity_api_version: 3

Set the value of the OS_CLOUD environment variable to the credentials you want to use, or use the command line argument –os-cloud=<credentials name> to use it:

# Set the environment variable OS_CLOUD to use credentials az1-project1
export OS_CLOUD="az1-project1"

# List instances
openstack server list

# Or set it via command line arguments
openstack --os-cloud=az2-project2 server list

Create a Load Balancer

A Load Balancer distributes incoming traffic across multiple backend instances, improving the availability, scalability, and reliability of your applications.

This article explains how to create a Load Balancer, the required network configuration, and the available deployment options.

Prerequisites

Before creating a Load Balancer, ensure that:

• You have an existing project.
• You have created a Network.
• The Network contains at least one Subnet.
• Your instances are connected to the same Network

Note: A Load Balancer cannot be created without an existing subnet.

Network Requirements

• A Load Balancer must be attached to a Subnet within a Network.
• During the creation process, you will be asked to select an existing subnet.
• The Load Balancer is created on the selected subnet and is used to route traffic to backend instances.
  
• If you do not already have a network, complete the following steps first:
  • Create a Network.
  • Create a Subnet within the network.
  • Connect your backend instances to the subnet.

Public Connectivity

A Network by itself does not provide connectivity to the public Internet. If you want your application to be publicly accessible, the Network must be connected to a Router.

The router provides connectivity between your Network and the external network.

Without a Router, the Load Balancer is only reachable by resources connected to the same Network.

Create a Load Balancer

Launch wizard consists of the following configuration steps.

1. Select a Region
   • Select the region where the Load Balancer will be deployed.
2. Select an Availability Zone
   • Choose the Availability Zone where the Load Balancer will be deployed.
     • AZ-01
     • AZ-02
   • A Load Balancer can currently distribute traffic only to backend instances located in the same Availability Zone. For example, a Load Balancer deployed in AZ-01 can balance traffic only to instances running in AZ-01.
3. Select an Instance Type
   • Choose the Load Balancer size that best matches your expected workload.

4. Add a Name for your load balancer instance
5. Add a Description for your load balancer instance (optional)
6. Select a Subnet
   • Select the subnet where the Load Balancer Virtual IP (VIP) will be created.
   • Only subnets within the selected Availability Zone are available for selection.
   • The selected subnet must be connected to the backend instances that will receive traffic.
     

Review and Create

Review the selected configuration:

• Region
• Availability Zone
• Subnet
• Instance Type

If everything is correct, click Create Load Balancer.

The Load Balancer will enter the Creating state while it is being provisioned.

Once provisioning is complete, the status changes to Active, indicating that the Load Balancer is ready to be configured.

How to Check Your Current Status Right Now

You can instantly verify if your IP ranges that you have announced by Leaseweb, have valid Route Objects and ROAs using the public tools like NLNOG IRR Explorer and Arelion looking Glass

• https://irrexplorer.nlnog.net
• https://lg.twelve99.net

RR Status: Must display an active ‘route’ or ‘route6’ object.

PKI Status: Must display ‘Valid’. (If it reads “No (covering) RPKI ROA found”, you must issue a ROA).

How to create valid Route Object and ROA-record for your prefix

To prevent your prefixes from receiving warnings or being withdrawn from being announced on the internet, please complete the following steps with your RIR, see below for detailed information:

1. Create/Update IRR Route Objects:
Ensure every IP subnet announced has a valid ‘route’ or ‘route6’ object in an authoritative IRR registry (e.g., RADB, RIPE, APNIC, ARIN) referencing our correct regional ASN.

2. Publish RPKI ROA Records:
Log into your RIR portal (ARIN, RIPE NCC, or APNIC) and create a signed ROA for all IP ranges binding them to the correct Leaseweb ASN. Ensure your ‘maxLength’ accommodates all announced subnets e.g., ‘/24’ or ‘/48’ (for IPv6 prefixes).

Documentation

Direct links to official documentation and portal instructions for creating RPKI ROA records (Route Origin Authorizations) and IRR Route Objects (route / route6) across RIPE, APNIC, ARIN, and RADB:

1. RIPE NCC (Europe, Middle East, Central Asia)

• ROA Records (Hosted RPKI):
  • Documentation: RIPE NCC Hosted Certificate Authority Management
  • How to create: Log in to my.ripe.net, navigate to the RPKI Dashboard, and under the BGP Announcements or ROAs tab, click New ROA. Enter your prefix, origin Autonomous System Number (ASN), and set the maxLength (leaving it default/equal to the prefix length is recommended).
• Route Objects (RIPE Database / IRR):
  • Documentation: RIPE Database Documentation – Creating Route Objects
  • How to create: Log in to my.ripe.net, navigate to the RIPE Database Webupdates section, select route (IPv4) or route6 (IPv6), fill in route: <prefix>, origin: <AS-number>, and mnt-by: <MAINT-ID>, then submit.

2. ARIN (North America & Caribbean)

• ROA Records (RPKI):
  • Documentation: ARIN Route Origin Authorizations (ROAs) Guide | ARIN RPKI RESTful API Guide
  • How to create: Log in to ARIN Online, select Routing Security from the navigation menu, select Manage RPKI for your organization, click Create ROA, and enter your Origin ASN, Prefix, and Max Length.
• Route Objects (ARIN IRR):
  • Documentation: ARIN Internet Routing Registry (IRR) User Guide
  • How to create: In ARIN Online, go to Routing Security → IRR, click Create Object, select route or route6, specify your prefix, origin ASN, and maintainer, then submit.

3. APNIC (Asia-Pacific)

• ROA Records & Route Objects (MyAPNIC One-Stop Creation):
  • Documentation: APNIC Resource Certification & RPKI Overview | Creating Route Objects Guide
  • How to create: APNIC allows creating both simultaneously. Log in to MyAPNIC, go to Resources → Route Management, click Create Route, enter the IP prefix and Origin ASN, and tick the ROA and/or Whois Route Attributes options to generate both the RPKI ROA and IRR route/route6 objects together.

4. RADB (Routing Assets Database – IRR)

• Note: RADB is an independent Internet Routing Registry (IRR) and does not host RPKI CAs for creating ROAs directly; it is strictly used for IRR route/route6 objects.
• Route Objects (IRR):
  • Documentation: RADB Documentation & Portal | RADB API & Object Management Guide
  • How to create: Log in to the RADB Portal, navigate to Maintain Objects, click Create Object, select route (IPv4) or route6 (IPv6), and enter the required fields (route:, origin:, descr:, and mnt-by:).

Leaseweb ASNs per datacenter

A new instance can be launched through the Leaseweb Customer Portal or via the OpenStack API.

If you launch an instance of a type covered by a Savings Plan, it will be included under your Savings Plan and will not incur additional compute charges, provided you do not exceed the number of instances covered by the plan.

How to Launch a Public Cloud Instance from the Customer Portal

1. Go to your Leaseweb Customer Portal account.
2. From the menu, select Public Cloud and click Launch Instance.
3. Configure your instance on the Launch page.

Prerequisites

• An SSH key created to securely connect to your instance.
• A Network and Router configured for your project.

How to Configure a New Instance

1. Select a Region

• By default, the region you are currently logged in to will be selected.
• In order to switch to a different region, you are required to switch your account to the corresponding sales organization. You can do this by clicking on your profile icon in the top right corner.

2. Select the Availability Zone

• Choose the Availability Zone where you want to launch your instance.
  • Select either eu-west-3-az1 or eu-west-3-az2.

Back to the top ↑

3. Add the Instance Name and Description

• Enter a name for your instance and, optionally, add a description to help identify its purpose.

4. Choose an Instance Source

• If you are just getting started, simply select the operating system image and its version for your instance.

• By default, the storage volume is deleted when the instance is terminated.
• To keep the volume after deleting the instance, uncheck the Delete Volume on Instance Termination option.
• You can also launch an instance from a Snapshot or Volume if available / set up.

5. Configure the Storage Volume

• Configure the volume size and type for your instance.
• By default, a minimum of 5 GB is required to install the operating system image.
• You can attach additional storage volumes to the instance later if needed.

6. Select Instance Type

• Select the vintage and instance type according to your required compute type and size of the instance, including CPU and RAM allocated to the instance.

7. (Optional) Add User data

• User data allows you to automatically install packages or run scripts when the instance starts for the first time.
• This step is optional.

8. Select a Key Pair

• A key pair provides a secure way to connect to your instance. Select an existing key pair or create a new one.

Back to the top ↑

9. Select the Network

• Select a network for your instance. If you have not created one yet, you can create it directly from the networks page on the customer portal.

10. (Optional) Add Security Groups

• Adding Security Groups is optional and allows you to control which network traffic can access your instance.

11. Set the Amount of Instances

Specify the number of instances you want to launch. You can create one, or multiple instances, in a single request.

The maximum number of instances you can launch at once is 10.

12. Review the Summary

• Click the Launch button when you are ready to create your instance.
• A summary will display the selected instance specifications and the estimated costs before deployment. Review and continue with the launch.