Learn about the first steps of creating and connecting to a Public Cloud instance.

Free trial: Create your first Public Cloud project and get $200 free credit^[1]. Get started now!

Public Cloud instances are easy to deploy and manage. However, being part of the OVHcloud Public Cloud ecosystem, instances offer many configuration options and can be adjusted to different use cases. The following instructions include all the necessary (and optional) steps to create an instance in the OVHcloud Control Panel and access it remotely. You can then go ahead with your Public Cloud project according to your needs.

Requirements

A Public Cloud project in your OVHcloud account

OVHcloud Control Panel Access

Direct link: Public Cloud Projects
Navigation path: Public Cloud > Select your project

Take advantage of reduced prices by committing to 1 to 36 months for your Public Cloud resources. More information can be found on our Savings Plans page.

Instructions

If you have not created a Public Cloud project yet, start with our guide on creating a project.

Important technical details about the OVHcloud Public Cloud are available on this guide page.

Content overview

Step 1: Creating SSH keys
Step 2: Importing SSH keys
Step 3: Preparing the network configuration
Step 4: Creating the instance
Step 5: Connecting to the instance
Step 6: First steps on a new instance
- 6.1 User management
  - 6.1.1 Setting a password for the current user account
  - 6.1.2 Enabling remote logins via password
- 6.2 Additional SSH keys

Step 1: Create an SSH key set

You need to provide a public SSH key when creating Public Cloud instances in the OVHcloud Control Panel. After the instance is created, you can configure your remote access at your own discretion.

Exception: Login authentication on Windows instances requires a username and password because Windows uses RDP (Remote Desktop Protocol).

If you already have an SSH key pair ready to use, you can skip this step.

The SSH protocol enables encrypted client-server communication. An SSH key pair consists of a public key and a private key.

The public key is added to your Public Cloud instance (and can also be stored in the OVHcloud Control Panel).
The private key is stored on your local device and must be secured from unauthorized access. Only client devices with the matching private key can access your instance. A user account password is not required to connect.

You have two options to create and manage your SSH keys:

Command line interface of your OS (basic Open SSH client)
Additional software (compatible with the Open SSH protocol) with a command line or graphical interface

Most contemporary desktop operating systems natively include the Open SSH client, which can be accessed through the system's command line application (cmd, PowerShell, Terminal, etc.). If you are not familiar with using SSH keys as an authentication method, you can use the instructions in this guide to get started and create your key pair.

If you use an alternative software, refer to its user documentation. Instructions for the open-source solution PuTTY are available in this guide.

Step 2: Import SSH keys

You can store your public SSH keys in the Public Cloud section of the OVHcloud Control Panel. This is not mandatory, but makes the instance creation process more convenient.

Stored SSH keys help you to create your instances faster in the OVHcloud Control Panel. To change key pairs and add users once an instance is created, please refer to the guide on additional SSH keys.

Public SSH keys added to your OVHcloud Control Panel will be available for Public Cloud services of all regions. You can store keys encrypted with RSA, ECDSA, and ED25519.

Open SSH Keys in the left-hand menu under Project Management. Then, click + Add an SSH key.

In the pop-up window, provide a Name and your public Key string, for example, the one created in Step 1. Confirm by clicking Add.

You can now select this key in Step 4 to add it to a new instance.

Step 3: Prepare the network configuration

Before creating your instance, we recommend considering the way the instance will be used in terms of networking.

If you do not need to configure the instance with a private network at this time, you can proceed with Step 4. You can create an instance exposed to the public internet. (See Public Mode below.)
If the instance needs to be connected to a new private network (OVHcloud vRack), create your vRack first before continuing. You can find the details in the Public Cloud vRack guide.

Public Cloud Networking - Modes

Public Mode

Instances in Public Mode are exposed to the public internet directly via IPv4/IPv6. IP addresses cannot be modified, but instances can have Additional IP addresses attached (including your own) and they can be connected to a vRack.

Private Mode

Instances in Private Mode can only be exposed to the public internet via a Gateway or a Load Balancer service and Floating IP addresses.

For more information, please consult our guides in the Public Cloud Networking section. The Concepts guide provides an introduction to Public Cloud Networking.

Local Private Mode

Local Private Mode only applies if you create an instance in a Local Zone. They can be exposed to the public internet directly via IPv4/IPv6. Only instances in the same Local Zone can be connected via private networks. Local Zones are not compatible with vRack. In this mode, DHCP automatically provides IP addresses to your instances.

Find out more on our Local Zones web page.

Step 4: Creating an instance

A public SSH key is mandatory when an instance is created in the OVHcloud Control Panel (Windows instances excluded).

Refer to Step 1 and Step 2 of this guide if you do not have SSH keys ready.

NOTE: If you wish to create your instance via the OVHcloud API, expand and follow the instructions below. After that, you can proceed to Step 5.

Creating an instance via OVHcloud API

Get the id for your SSH key:

GET /cloud/project/{serviceName}/sshkey
Get the id for the instance flavor you want to create:

GET /cloud/project/{serviceName}/flavor
Get the id for the image you want to use:

GET /cloud/project/{serviceName}/image
To see the parameters of your existing instance(s), use the following call:

GET /cloud/project/{serviceName}/instance
Get the id for the network you want to connect to your instance:

GET /cloud/project/{serviceName}/network/public
Create your new instance with the following call:

POST /cloud/project/{serviceName}/instance

Example Request Body:

On the Home page, click Create the instance.

In this step, you choose the instance model (also called a "flavor") which determines the resources allocated to your instance: processor, memory, and associated capabilities. Use the tabs to select the model type that best suits your use case to access our range of optimized instances.

The Discovery model type brings together instances with shared resources, offered at competitive prices. They are particularly well suited for discovering the OVHcloud Public Cloud, performing tests, or hosting light workloads such as web applications.

Your Public Cloud resources total will initially be limited for cost control and security reasons. You can verify these quotas by clicking Quota and Regions in the left-hand navigation bar under Project Management. Please consult the dedicated documentation for more information.

Note that you can upgrade your instance after creation to have more resources available. However, downgrading to a smaller model is not possible with a regular instance.

Additional information

Instance model categories

Server Type	Guaranteed Resources	Usage Notes
General Purpose	✓	Development servers, web, or business applications
Compute Optimized	✓	Video encoding or other high-performance computing
Memory Optimized	✓	Databases, analysis, and in-memory calculations
GPU	✓	Massive parallel processing power for specialized applications (rendering, big data, deep learning, etc.)
Discovery	-	Hosted on shared resources for testing and development environments

Regions and Local Zones

Regions

A region is defined as a location in the world comprised of one or several data centers where OVHcloud services are hosted. You can find more information on regions, geographical divisions, and the availability of services on our region web page.

Local Zones

Local Zones are an extension of regions that bring OVHcloud services closer to specific locations, offering reduced latency and improved performance for applications. You can find more information on the Local Zones web page and in the Local Zones documentation.

Select a location closest to your users or customers. Note that if you select a Local Zone in this step, network limitations will apply to the instance (see Step 3).

For more information, refer to the information on the Local Zones web page and in the Local Zones documentation.

The choice of region determines how your instance is deployed (1-AZ or Local Zones). To understand the differences in terms of resilience, availability, and architecture, see our Comparison and resilience of Deployment Modes - Understanding 1-AZ / Local Zones guide.

Click on the appropriate tab and select an operating system for your instance from the drop-down menus.

The images available in this step depend on the choices made in the previous steps, i.e., compatibility with the instance model and regional availability. For example, if you want to select a Windows OS and there are no options in the Windows tab, you need to modify the choices of the previous steps.

If you select an operating system that requires paid licensing, these costs will be automatically included in the project invoice.

NOTE: B3/C3/R3 instances have the option to use a Windows Operating system. To use this option with OpenStack CLI, you must select a flavor labeled with "win" (i.e., win-b3-8).

The Windows Server license billing is separate from the instance. On your invoice, you will therefore see two separate lines:

A line for your instance consumption.
A line for Windows license consumption calculated per vCPU.

Example: For a B3-16 instance with Windows Server (4 vCores and 16 GB of RAM):

You will be billed based on the hourly cost of the B3-16 instance.
Windows license will be billed hourly for 4 vCore.

For better readability, the total price per hour, including instance and license is displayed directly on our Pricing page.

With the exception of Windows instances, configuring your instance also requires adding a public SSH key. You have two options:

Use a public key already stored in the OVHcloud Control Panel

To add a key that is already stored in the OVHcloud Control Panel (see Step 2), select it from the list. Then click Next.

Enter a public key directly

To add a public key by pasting the key string, click the Add a key button.

Enter a name for the key and the key string in the respective fields. Then click Next.

Before clicking Next, you can optionally use the button Add a key to store this key in the OVHcloud Control Panel (see Step 2 for details).

PCI_gettingStarted_ firstInstance08*.png

NOTE: Available resources may vary. Please contact Customer Support with any questions.

This step offers several configuration options:

Number of instances to be created

You can create multiple instances based on the selections in the creation steps but resource quota limitations will apply.

Flexible instance

A Flex instance is a single 50 GB disk instance designed to offer faster snapshot creation and restoration.

It allows resizing to higher or lower models while maintaining fixed storage. Classic models only allow resizing to higher models.

Instance name

Enter a full name for your instance. The commercial reference of the instance model is the default value. If necessary, you can also add the region and date to facilitate the identification and management of your instances.

Post-installation script

You can add your script in this field.

Automatic instance backup

If you wish to enable them, select the Automatic instance backup box and choose a rotation type, i.e., the maximum number of backups kept in the history: 7 or 14 days. You can find more information about instance backups in our dedicated guide.

When you have made your selections, click Next.

In this step, you will configure the network for your instance.

Regions

Private mode

You can connect the instance to a private network and a Floating IP.

NOTE: If you click on Create a new private network, the instance creation process will be interrupted. Follow the steps in our dedicated guide to create your private network, then restart the instance creation process.

Click Next to proceed to the final step.

Public mode

The instance will be exposed to the public internet directly via IPv4/IPv6.

Public mode is the standard network model and allows your instances to have a public network port attached. Select a private network (vRack) in this mode to create an instance with both a public and a private IP.

NOTE: If you click on Create a new private network, the instance creation process will be interrupted. Follow the step in our dedicated guide to create your private network, then restart the instance creation process.

Local Zones

You can choose to attach the instance to a private network, make it publicly reachable, or both.

Public Network

If you select the option Public network, the instance will be exposed to the public internet directly via IPv4/IPv6.

You can additionally connect the instance to a private network (not compatible with vRack) if you select Local Private Network compatible with Local Zones (see tab Local Private Network).

Local Private Network

Tick the check box Local Private Network compatible with Local Zones. If you select this option without also selecting Public network, the instance will remain fully private, attached to a private network (not compatible with vRack). Choose an existing network from the list via the option Attach an existing private network or create a new one for the Local Zone by choosing Create a local private network (without interrupting the instance creation process).

PCI_gettingStarted_ firstInstance12.5.png

Click Next to proceed to the final step.

Depending on the instance model you choose, hourly billing may be the only option displayed.

We recommend choosing hourly billing if there is any doubt regarding the usage period because it is not possible to choose it after the service delivery. For certain instance flavors, you will have the option to switch to a monthly subscription as soon as the instance is available on the "Instances" page.

NOTE: If you choose to be billed hourly, you will continue to be billed as long as the instance is not deleted. It does not matter if the instance is not actually used during this time.

Hourly billing

Hourly billing is the best choice if you have not determined the length of the usage period. If you decide to keep the instance for long-term use, you can still switch to a monthly subscription.

The instance will be billed as long as it is not deleted, regardless of the actual usage of the instance.

Monthly billing

Monthly billing will result in lower costs over time but cannot be changed to hourly billing after the instance is created.

Find more details in our Public Cloud billing guide.

Once you have made sure that your configuration choices are correct, click on the Create an instance button to finish creating your new instance. It may take a few minutes until your service is delivered.

Step 5: Connecting to your instance

The instructions in this section concern remote connections through the Open SSH and RDP protocols through a public network (internet).

Note that we provide alternative ways of access (mainly used for troubleshooting) which are only available via your OVHcloud Control Panel:

If you have installed an OS with an application, refer to our guide on the first steps with applications as well as the official documentation by the respective publisher.

5.1: Verify the instance status in the OVHcloud Control Panel

Select Next in the left-hand menu under Compute. Your instance is ready when the status shows Enabled. If the instance was recently created and has a different status, click on the Refresh 🔄 button located next to the search filter.

Click on the instance's name in this table to open the Dashboard, in which you can find all information about the instance. To learn more about the functions available on this page, consult our guide on managing instances in the Control Panel.

A user with elevated permissions (sudo) is automatically created on the instance. The username reflects the image installed ("ubuntu", "debian", "fedora", etc.). You can use this and the IPv4 address (found in Dashboard > Networks section) to SSH into your instance.

If your SSH key pair is set up correctly, you can now connect to the instance with the preconfigured user and your SSH key. You can find more detailed instructions in the subsequent paragraphs.

Access via VNC console on a new GNU/Linux OS instance created in the Control Panel must be enabled first as described in the guide section below.

This guide does not cover private networking for instances. Please consult our documentation on Public Cloud Networking regarding this topic.

If you receive error messages regarding your SSH keys, verify that your local device has a properly configured private SSH key using the information in this guide.

If you still encounter issues, you can replace the key pair with the help of this guide.

If you have created an instance without an SSH key, via the OVHcloud API or the OpenStack Horizon interface, you can only add an SSH key to your instance via rescue mode by following the instructions set out in this guide.

You can access your instance immediately after creation through the command line interface of your local device (Terminal, Command prompt, Powershell, etc.) via SSH.

ssh username@IPv4_instance

Example:

ssh ubuntu@203.0.113.101

Depending on your setup, you will have to enter a passphrase that protects your private key or specify the path to your key file. Consult our SSH keys guide for detailed information on this topic.

If you use an alternative SSH client software, refer to its user documentation. A usage example for the open-source solution PuTTY is available in this guide.

Continue with Step 6 below.

5.3: Windows instances

5.3.1: Finish the installation of the Windows instance

After verifying that the Windows instance is installed, open the VNC console tab in your OVHcloud Control Panel.

You will then need to complete the initial setup of your Windows OS. Follow the steps below by navigating through the tabs:

Configure your country/region, the preferred Windows language, and your keyboard layout. Then click on the button Next at the bottom right.

PCI_gettingStarted_ firstInstance16*.png

Set a password for your Windows Administrator account and confirm it, then click on Finish.

PCI_gettingStarted_ firstInstance17.png

Windows will apply your settings and then display the login screen. Click on the Send CtrlAltDel button in the top right corner to sign in.

PCI_gettingStarted_ firstInstance18.png

Enter the Administrator password you have created in the previous step and click on the Arrow button.

PCI_gettingStarted_ firstInstance19.png

5.3.2: Log in remotely from Windows

On your local Windows device, you can use the Remote Desktop Connection client application to connect to your instance.

PCI_gettingStarted_ firstInstance20.png

Enter the IPv4 address of your instance, then your username and passphrase. Usually a warning message will appear, asking to confirm the connection because of an unknown certificate. Click on Yes to log in.

If you experience any issues with this procedure, verify that remote (RDP) connections are allowed on your device by checking your system settings, firewall rules and possible network restrictions.

5.3.3: Log in remotely from another OS

Connections from a desktop OS other than Windows usually require a client software compatible with the Remote Desktop Protocol (RDP). Some desktop environments and operating systems might have a native client built in.

Whichever client you are using, you only need the IP address of your instance and your password for the Administrator account to connect.

Example of use

The free and open-source software Remmina Remote Desktop Client is available for many GNU/Linux desktop distributions. If you do not find Remmina in your desktop environment's software manager, you can obtain it from the official website.

PCI_gettingStarted_ firstInstance21.png

Open Remmina and make sure the connection protocol is set to "RDP". Enter the IPv4 address of your Public Cloud instance and press Enter.

PCI_gettingStarted_ firstInstance22.png

If a certificate warning message appears, click on Yes. Enter the username and your password for Windows and click on OK to establish the connection.

PCI_gettingStarted_ firstInstance23*.png

You can find some useful items in the left-hand toolbar. For example, click on on the icon Toggle dynamic resolution update to improve the window resolution.

PCI_gettingStarted_ firstInstance24.png

5.4: VNC console access

The VNC console allows you to connect to your instances even when other means of access are not available.

Select Instances in the left-hand navigation bar under Compute. Click on the instance name, and select the VNC console tab.

You will need to have a user account with a password configured on the instance to use the VNC console. To set a password for the preconfigured account, follow Step 6.1.1 below.

Log in with your Windows credentials. If there is an active login session, you will have immediate access. There will be a noticeable latency compared to an RDP connection.

Step 6: First steps on a new instance

Windows instances: There are no additional steps required for instances with a Windows OS installed. You can find more information in the Go further section below.

6.1: User management

When configuring user accounts and permission levels on an instance, we recommend using our How to configure user accounts and root access on a server guide.

6.1.1: Set a password for the current user account

When logged on to your instance, set a password for the current user by entering this command:

sudo passwd

Enter a passphrase, confirm with Enter and repeat.

New password: 
Retype new password:
passwd: password updated successfully

This is sufficient to enable logins via the VNC console in your OVHcloud Control Panel. Remote SSH logins with this password however are still disabled by default.

6.1.2: How to enable remote logins via password (optional)

NOTE: This step is not necessary and should only be executed if you have a viable reason to enable this access type; for example if you need to temporarily log in to the instance from a device that does not have your private SSH key stored on it.

The following example illustrates a temporary solution on an instance with Ubuntu installed. Note that you might need to adjust the commands according to your OS. It is not recommended to keep this configuration permanently because it adds a potential security risk by opening the system to SSH-based attacks.

When logged on to your instance, open the pertinent configuration file with a text editor. Example:

sudo nano /etc/ssh/sshd_config

Edit the line #PasswordAuthentication yes as follows:

PasswordAuthentication yes

Edit the line Include /etc/ssh/sshd_config.d/*.conf as follows:

#Include /etc/ssh/sshd_config.d/*.conf

Save the file and close the editor.

Restart the SSH service with one of the following commands:

sudo systemctl restart ssh

sudo systemctl restart sshd

You can now log in via SSH with username and password as well.

Reverse these changes to return to the key-based login for the instance.

6.2: Additional SSH keys

If you want to allow more user accounts to access the instance, the standard procedure is as follows:

Create the account on the instance.
Create a new SSH key pair on the device concerned.
Add the public key to the instance.

Use our dedicated guide for a detailed explanation of these steps.

Go further

For more information and tutorials, please see our other Public Cloud support guides or explore the guides for other OVHcloud products and services.

[1]: Receive $200.00 (USD) in Public Cloud credits ("Public Cloud Credits") when you create your first Public Cloud infrastructure project. Offer applies only to Public Cloud services purchased from OVHcloud datacenters in the United States. Offer available only to customers who, at the time when the Public Cloud Credits are applied, are not purchasing Public Cloud services from OVHcloud and who purchase at least $0.99 (USD) Public Cloud services from OVHcloud. No code is required. The Public Cloud Credits will be added to eligible accounts within 30 days of OVHcloud’s receipt of the $0.99 for your purchase of Public Cloud credits. The Public Cloud Credits are valid for 90 days fro the day the credit has been applied. The time of order placement shall be determined by OVHcloud’s time of registering the corresponding order. Offer is subject to availability. The Public Cloud Credits will automatically be applied to your next bill(s) up to a maximum amount of $200.00. Any unused portion of the Public Cloud Credits will expire. The Public Cloud Credits have no monetary value, and cannot be exchanged, transferred, or refunded. Once the Public Cloud Credits are exhausted or expired, your account will be debited in accordance with OVHcloud’s billing guide. Void where prohibited.