Learn how to configure Public Cloud instances in the OVHcloud Control Panel and the first steps to take with your instances.
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 further 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 a period of 12 or 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
- Requirements
-
Instructions
- Content overview
- Step 1: Create an SSH key set
- Step 2: Import SSH keys
- Step 3: Prepare the network configuration
- Step 4: Create the instance
- Step 5: Connect to the instance
- Step 6: First steps on a new instance
- Go further
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 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 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 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 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 Settings. Click on the button Add an SSH key.
In the new window, enter a name for the key. 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.
Use the following call to import your public SSH key:
Parameters:
-
serviceName: your Public Cloud project ID -
name: name of the SSH key -
publicKey: content of your public key
Note the id returned — it will be needed when creating the instance.
Make sure you have installed and configured the OVHcloud CLI, then import your key:
Verify the import and note the name of the key for Step 4:
Make sure you have configured your OpenStack environment (dedicated guide), then import your key:
Verify the import:
Declare the resource in your .tf file:
Refer to the Terraform guide for the initial provider setup.
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 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), 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 - 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 Network Services 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 the Local Zones web page.
Step 4: Create the instance
A public SSH key is required when creating an instance (except for Windows instances). Refer to Step 1 and Step 2 if you do not have SSH keys ready to use.
On the Home page, click Create the instance.
4.1 Select a model
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.
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 |
4.2 Select a location
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.
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).
1-AZ 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.
4.3 Select an image
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 keybutton.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 buttonAdd a keyto store this key in the OVHcloud Control Panel (see Step 2 for details).
4.4 Configure your instance
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 backupbox 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.
4.5 Configure your network
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 selectingPublic 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).
Click Next to proceed to the final step.
4.6 Billing
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.
Retrieve the required identifiers:
Create the instance:
Main parameters:
-
name: instance name -
flavorId: model ID -
imageId: OS image ID -
region: deployment region -
sshKeyId: SSH key ID (from Step 2) -
monthlyBilling:truefor monthly billing
Refer to the OVHcloud API documentation to configure your API access.
Retrieve the required identifiers:
Create the instance:
Replace US-EAST-VA-1 with your region. For interactive creation with guided selection:
Check the status after creation:
Retrieve the required information:
Create the instance:
Check the status:
Refer to the OpenStack environment setup guide for initial configuration.
Complete configuration example:
Refer to the Terraform guide for OVHcloud Public Cloud for the initial provider setup and authentication.
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 Control Panel:
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 Control Panel
Select Instances in the left-hand navigation bar under Compute. Your instance is ready when the status is set to Enabled in the table. 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 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 Control Panel.
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 on the right-hand side of the Dashboard in the section Networks.
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 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 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 tab VNC console 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.
Set a password for your Windows Administrator account and confirm it, then click on Finish.
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.
Enter the Administrator password you have created in the previous step and click on the Arrow button.
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.
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.
You can find some useful items in the left-hand toolbar. For example, click on the icon Toggle dynamic resolution update to improve the window resolution.
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 open the tab VNC console.
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.
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 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 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:
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 license for an instance in private mode
How to reset a Windows Administrator password
Instance management in the Control Panel
How to get started with OpenStack
How to get started with Horizon
If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for a custom analysis of your project.
For more information and tutorials, please see our other Public Cloud support guides or explore the guides for other OVHcloud products and services.