How to create a Public Cloud instance and connect to it
Find out how to configure Public Cloud instances in the OVHcloud Console and the first steps with your instances
Objective
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 Console and access it remotely.
You can then go further with your Public Cloud project according to your needs.
This guide explains how to get started with a Public Cloud instance.
Requirements
- A Public Cloud project in your OVHcloud account
OVHcloud Console Access
- Direct link:
- Navigation path:
Public Cloud> Select your project >Compute>Instances
Take advantage of reduced prices by committing to a period of 1 to 36 months on your Public Cloud resources. More information on our Savings Plans page.
Instructions
If you have not created a Public Cloud project yet, start with our guide on how to create a project.
Important technical details about the OVHcloud Public Cloud are available on this guide page.
Content overview
- Objective
- Requirements
- Instructions
- Go further
You need to provide a public SSH key when creating Public Cloud instances in the OVHcloud Console. After the instance is created you can configure your remote access at your own discretion.
Exception: Login authentication on Windows instances requires username and password because Windows uses RDP (Remote Desktop Protocol).
Step 1: Create an SSH key set
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 Console).
- 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 2 options to create and manage your SSH keys:
- Command line interface of your OS (basic OpenSSH client)
- Additional software (compatible with the OpenSSH protocol) with a command line or graphical interface
Most contemporary desktop operating systems natively include the OpenSSH 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. A usage example for the open-source solution PuTTY is available in our guide: How to use PuTTY.
Step 2: Import SSH keys
You can store your public SSH keys in your Public Cloud project. 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 Console. 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 Console will be available for Public Cloud services of all regions. You can store keys encrypted with RSA, ECDSA and ED25519.
In the left-hand menu of your Public Cloud project, click Project Management, then the SSH keys tab. Click Create an SSH key.
In the new window, enter a name for the key in the Name field. Fill in the Key field with 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 to consider 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 enable public connectivity when creating the instance. (See Public connectivity below.)
- If the instance needs to be connected to a new private network (OVHcloud vRack), please note that the vRack is created automatically when you create your Public Cloud project. No prior action is therefore required. For more information, see the Public Cloud vRack guide.
Public Cloud Networking - Public connectivity
Public connectivity
All instances are created in a private network. Public connectivity is an option you enable separately. Three types of public IP address are available:
- Basic IP: a public IP address tied directly to the instance (direct attachment to the Ext-Net network), exposed immediately via IPv4/IPv6.
- Additional IP: a public IP address independent of the instance, used in addition to a Basic IP (including your own IP via BYOIP), which can be attached, detached or moved to another resource (including outside Public Cloud). Instances with an Additional IP can also be connected to a vRack.
- Floating IP: a reusable public IP address, associated with the instance via a Gateway (or used with a Load Balancer). Like an Additional IP, it can be detached and reattached at any time, but it is reserved for Public Cloud/cloud-native usage and requires a Gateway.
For more information, please consult our guides in the Public Cloud Network services section. The Concepts guide provides an introduction to Public Cloud Networking, and the Public Cloud IP types guide compares the three types of public IP addresses.
Local Zones
In a Local Zone, instances 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 Local Zones, DHCP automatically provides IP addresses to your instances.
Find out more on the Local Zones web page.
Step 4: Create the instance
In the left-hand menu of your Public Cloud project, click Instances under Compute, then click Create instance. The Create an instance page opens.
4.1 Name
Enter a full name for your instance in the Instance name section.
4.2 Location
In the Select a region section, select a location closest to your users. You can filter the locations by deployment mode. Note that selecting a Local Zone applies network limitations (see Step 3). Refer to the guide Deployment Mode Comparison for differences between 3-AZ, 1-AZ and Local Zones.
4.3 Model
In the Select a model section, open the Instance model list and select the model category suited to your use case, then select the model type in the Type list. The model (flavor) determines the resources allocated to your instance: processor, memory, and associated capabilities.
Your total Public Cloud resources will initially be limited. Check your quotas in the left-hand menu: click Project Management, then the Quotas tab. See the dedicated documentation for more information.
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. See step 4.9 for details.
4.4 Image
In the Select an image section, select the image family in the Distribution type list, then choose your OS and its version in the Image version list. Available options depend on the model and region chosen.
4.5 SSH key (not applicable to Windows instances)
In the Select an SSH key section, select a stored SSH key from the list (see Step 2), or click Create a new SSH key to paste a public key directly.
4.6 Snapshot
In the Snapshot settings section, automatic snapshots are enabled by default, in the regions where they are available. Select the rotation type (7 or 14 days).
4.7 Network
The Network settings section is split into two parts:
- Private network: Select an existing private network or click
Create a private network. If a private network is selected but does not have a gateway, toggleAssign a gatewayto attach a gateway automatically. - Assign public connectivity: Enable the
Assign a public IPtoggle to assign a public IP. It is disabled by default: without a public IP, a Floating IP, a gateway or an SSH proxy, you cannot connect to the instance from the Internet. Choose Basic Public IP (linked to the instance) (billed per second, tied to the instance lifetime, incompatible with a gateway) or Assign a Floating IP (Reusable) (persistent and reusable).
See Step 3 for an overview of public connectivity options.
4.8 Billing
If the model offers both billing methods, the Billing section lets you choose between Monthly (lower cost, non-reversible) and Hourly (flexible, convertible to monthly). Hourly billing runs until the instance is deleted. See the billing documentation.
4.9 Advanced settings (optional)
- Flexible instance (available for eligible models only): single 50 GB disk, allows resizing to higher or lower models.
- Post-installation script: add your post-installation script.
4.10 Finalize
Review the summary on the right side of the screen and set the Number of instances to be created. Click Create my instance. Delivery may take a few minutes.
Step 5: Connect to the instance
The instructions in this part concern remote connections by means of the OpenSSH 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 Console:
If you have installed an OS with application, refer to our guide on first steps with applications as well as the official documentation by the respective publisher.
5.1: Verify the instance status in the OVHcloud Console
In the left-hand menu of your Public Cloud project, click Instances under Compute. Your instance is ready when its status is Active in the table. If the instance was recently created and has a different status, wait a few moments.
Click on the instance's name in this table to open its Overview tab, on 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 OVHcloud Console.
A user with elevated permissions (sudo) is automatically created on the instance. The username reflects the image installed, e.g "ubuntu", "debian", "fedora", etc. You can verify this in the Connection details card of the Overview tab, under Login information.
Via the OVHcloud CLI, check the instance status and retrieve its IP address with:
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 OVHcloud Console 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 Network services regarding this topic.
5.2: First login on an instance with a GNU/Linux OS installed
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.
Example:
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 of the instance in the .
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.

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.
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.
Open Remmina and make sure the connection protocol is set to "RDP". Enter the IPv4 address of your Public Cloud instance and press Enter.

5.4: VNC console access
The VNC console allows you to connect to your instances even when other means of access are not available.
In the left-hand menu of your Public Cloud project, click Instances under Compute. Click on the instance name and open the VNC console tab.
You will need to have a user account with a password configured on the instance in order to use the VNC console. To set a password for the preconfigured account, follow the steps in section 6.1.1 below.
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 to make use of the information in our user account 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:
Enter a passphrase, confirm with Enter and repeat.
This is sufficient to enable logins via the VNC console in your . Remote SSH logins with this password however are still disabled by default.
6.1.2: How to enable remote logins via password (optional)
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:
Edit the line #PasswordAuthentication yes as follows:
Edit the line Include /etc/ssh/sshd_config.d/*.conf as follows:
Save the file and close the editor.
Restart the SSH service with one of the following commands:
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
How to activate a Windows licence on an instance with no Basic IP
How to reset a Windows Administrator password
Instance management in the OVHcloud Console
How to get started with OpenStack
How to get started with Horizon
For training or technical assistance implementing our solutions, contact your sales representative or visit our Professional Services page to request a quote and have your project analysed by our experts.
Join our community of users.




