Welcome to the previous release notes section of our documentation portal for IONOS Cloud. This section is dedicated to archiving previous release notes for the year, excluding the latest release.

• November 2023 Releases

• October 2023 Releases

• September 2023 Releases

• August 2023 Releases

• July 2023 Releases

• June 2023 Releases

• May 2023 Releases

Latest Release: December 2023

Getting Started

With the Data Center Designer (DCD), IONOS Cloud's visual user interface, you can create a fully functioning Virtual Data Center (VDC).

APIs, SDKs & Tools

Product User Guides

Set up and manage your products and services via examples and troubleshooting cases below:

The Data Center Designer (DCD) is a unique tool for creating and managing your . DCD's graphical user interface makes data center configuration intuitive and straightforward. You can drag-and-drop virtual elements to set up and configure data center infrastructure components.

As is the case with a physical data center, you can use the DCD to connect various virtual elements to create a complete hosting infrastructure. For more information about the DCD features, see .

The same visual design approach is used to make any adjustments at a later time. You can log in to the DCD and scale your infrastructure capacity on the go. Alternatively, you can set defaults and create new resources when needed.

Core Functionality

The DCD allows the customer to both control and manage the following services provided by IONOS Cloud:

Compatibility

As a web application, the DCD is supported by the following browsers:

• Google Chrome™: Version 30+

• Mozilla® Firefox®: Version 28+

• Apple® Safari®: Version 5+

• Opera™: Version 12+

• Microsoft® Internet Explorer®: Version 11 & Edge

We recommend using Google Chrome™ and Mozilla® Firefox®.

Next Steps

What's new

Red Hat Enterprise Linux (RHEL) 8 Images

Red Hat Enterprise Linux (RHEL) 9 Images

Private Node Pools

Enhanced Features Released for Backup Service

Renamed Managed Backup to Backup Service

Revamped IONOS S3 Object Storage Web Console

New Feature Set in IONOS S3 Object Storage Web Console

Container Registry Vulnerability Scanning General Availability

New Container Registry Web Console

Documentation updates

Reorganized subtopics in Block Storage

Your IONOS Cloud infrastructure is set up in (VDCs). Here you will find all the building blocks and the resources required to configure and manage your products and services.

Creating a new VDC

1. On the Menu bar, click Data Center Designer. A drop-down panel will open.

You can create a VDC from the menu.

Or alternatively,

• Name: Enter an appropriate name for your VDC.

• Description: Describe your new VDC (optional).

• Region: Choose the physical IONOS data center location that will host your infrastructure.

3. Confirm your actions by clicking Create Data Center.

4. The data center is created and opened in the Workspace. You will find the VDC has been added to the My Data Centers list in the Dashboard.

Inside the Data Center Designer

You can set up your data center infrastructure by using a drag-and-drop visual interface. The DCD User Interface (UI) contains the following elements:

Element icons

The Palette and the Workspace

The Palette is a dynamic sidebar that contains VDC Elements. You can click and drag each Element from the Palette into your Workspace and position there, as required.

All cloud products and services are compatible with each other. You may create a Server and add Storage to it. A LAN Network will interconnect your Servers.

Some Elements may connect automatically via drag-and-drop. The DCD will then join the two if able. Otherwise, it will open configuration space for approval.

Selecting an element and pressing Delete or Backspace removes it from the Workspace.

The Context Menu

Right-clicking an element inside of the Workspace reveals additional functions. For example, you may right-click a Cube or a Server to Power it up or down. You may also use Pause or Delete, to remove it from your data center infrastructure.

The Context Menu always offers different options, depending on the Element.

The Inspector pane

This pane allows you to finalize the creation of your data center. Once your VDC is set up, click PROVISION CHANGES. This makes your infrastructure available for use.

Using the Start Center

The Start Center is an alternative option in VDC creation and management. You may access existing VDCs or create a new one from the Start Center view.

1. Inside the Dashboard Menu bar, select Data Center Designer > Open Start Center.

2 . The Start Center left section lists all your data centers in alphabetical order. The Create Data Center section, on the right, can also be used to create new VDCs.

3. The location region and version number are shown for each VDC. Version numbers begin at 0 and are incremented by 1 each time the data center is provisioned.

5. You can click on each VDC name on the list to open it.

1. Open the in your web browser by going to .

2. Select your preferred language (DE | EN) in the top right corner of the Log in window.

3. Enter the Email and Password created during registration.

4. Click the Log in button.

Dashboard

Once you have logged in, you will see the Dashboard. The Dashboard shows a concise overview of your data centers, resource allocation, and options for help and support. You may click on the IONOS logo, in the Menu bar, at any time, to return to the Dashboard.

Inside the Dashboard, you can see the My Data Centers list and the Resource Allocation view. The Resource Allocation view shows the current usage of resources across your infrastructure.

Menu bar

The Menu bar, at the top of every DCD screen, has buttons that allow you to access the DCD features, notifications, and help. These buttons also allow you to manage your account.

Recommended for beginners:

Selected user guides:

This section lists the most commonly referred topics in the User Guides.

This tutorial contains a detailed description of how to manually configure your IONOS Cloud infrastructure for each server via the Virtual Data Center (). It comprises all the building blocks and the necessary resources required to configure, operate, and manage your products and services. You can configure and manage multiple VDCs.

It is also possible to configure settings for each server automatically.

Create a Dedicated Core Server

1. Drag the Dedicated Core server element from the Palette into the Workspace.

2. To configure your Dedicated Core server, enter the following details in the Settings tab of the Inspector pane:

• Name: Enter a server name unique to the VDC.

• CPU Architecture: Choose between AMD or Intel cores.

• Cores: Choose the number of CPU cores.

Add storage to the Dedicated Core Server

1. Drag a Storage element from the Palette onto a Dedicated Core server in the Workspace.

2. To configure your Storage element, enter the following details in the Inspector pane:

• Name: Enter a storage name unique to the VDC.

• Availability Zone: Select a zone from the drop-down list to host the storage element associated with the server.

• Size in GB: Choose the required storage capacity.

• Performance: This option is available for SSD block storages only. Select a value from the drop-down list based on the requirement. You can either select Premium or Standard, and the performance of your storage element varies accordingly.

• Image: Select an image from the drop-down list. You can select one of IONOS images or choose your own.

• Password: Enter a password for the chosen image on the server—a root or an administrator password.

• Backup Unit: Select a backup unit from the drop-down list. Click Create Backup Unit to instantly create a new backup unit if unavailable.

Connect to the internet

2. To configure your NIC element, enter the following details in the Network tab of the Inspector pane:

• Name: Enter a NIC name unique to this VDC.

• Media Access Control Address (MAC) and Primary IPv4 addresses are added automatically.

• LAN: The name of the configured LAN is displayed. To select another network, select a value from the drop-down list.

Provision Changes

1. Start the provisioning process by clicking PROVISION CHANGES in the Inspector pane.

2. Review your changes in the Validation tab of the Provision Data Center dialog.

3. Confirm changes by entering your password. Resolve conflicts without a password.

4. When you are ready, click Provision Now to start provisioning resources.

The data center will now be provisioned. DCD will display a Provisioning Complete notification when your cloud infrastructure is ready.

Next steps

The Remote Console is used to connect to a server when, for example, no SSH is available. You must have the root or administrator password for this type of log-in to the server.

Procedure

1. Start the Remote Console from the server.

2. Open the data center containing the required server.

3. In the Workspace, select the server.

4. In the Inspector, choose Remote Console or select Remote Console from the context menu of the server.

5. Start the Remote Console from the Start Center (contract owners and administrators only).

6. Open the Start Center: Menu Bar > Data Center Designer > Open Start Center

7. Open the Details of the required data center. A list of servers in this data center is displayed.

8. Select the server and click Open Remote Console.

Remote Console version matching your browser opens; you can now log on to the server with root or administrator password.

The following are a few FAQs to provide an insight about renaming the product from Virtual Server(s) to Dedicated Core Server(s).

What is the reason for renaming "Virtual Servers" to "Dedicated Core Servers"?

The name change is part of our ongoing efforts to better reflect the performance and benefits of our Virtual Machines. "Dedicated Core Servers" emphasizes the dedicated nature of the compute resources assigned to each instance, ensuring consistent performance and increased reliability.

Will there be any changes in the features or specifications of the product with this name update?

No, there won't be any changes in the features or specifications of the product. The only update is the product name from "Virtual Servers" to "Dedicated Core Servers".

What is the difference between "Virtual Servers" and "Dedicated Core Servers"?

The underlying technology and capabilities of the Virtual Machines remain the same. The primary difference lies in the name. With "Dedicated Core Servers," you can still expect virtualized environments but with the added emphasis on dedicated resources per instance.

Will the pricing change with this new name?

There will be no changes to the pricing structure due to the name update. The costs and billing for our Virtual Machines, now known as "Dedicated Core Servers," will remain the same as they were for "Virtual Servers."

Are "Dedicated Core Server" instances isolated from each other?

Yes, "Dedicated Core Server" instances are isolated from one another. Each instance operates independently, with dedicated CPU cores, memory, and storage, ensuring a high level of performance and security.

How will this name change affect existing users of "Virtual Servers"?

Existing users of "Virtual Servers" will experience no functional changes or disruptions due to the name update. Your current virtual server instances will be referred to as "Dedicated Core Server" instances from now on.

Can I still use the same APIs and tools to manage Dedicated Core Servers?

Yes, you can continue to use the same APIs and tools that were used to manage regular virtual servers for the newly renamed Dedicated Core Servers.

Are there any actions I need to take as a user after this renaming?

No, as a user, you do not need to take any action. The name change is purely cosmetic, and your existing configurations and access to your instances will remain unchanged.

Will there be any updates to the user interface or API documentation as a result of this name change?

Yes, we will update the user interface and API documentation to reflect the new name "Dedicated Core Servers". Rest assured, the changes will be cosmetic, and the functionality will remain consistent.

Can I still create and manage multiple "Dedicated Core Servers" instances under my account?

Absolutely! You can continue to create and manage multiple "Dedicated Core Server" instances as per your requirements, just as you did with "Virtual Servers."

Where can I find more information or support regarding "Dedicated Core Server" instances?

For more information or support, you can refer to our documentation on the "Dedicated Core Server" product page on our documentation portal. Additionally, our customer support team is available to assist you with any questions or concerns you may have.

Dedicated Core Servers that you create in the DCD are provisioned and hosted in one of IONOS physical data centers. Dedicated Core Servers behave exactly like physical servers. They can be configured and managed with your choice of the operating system. For more information about creating a Dedicated Core Server, see Create a Server.

Boot options: For each server, you can select to boot from a virtual CD-ROM/DVD drive or from a storage device (HDD or SSD) using any operating system on the platform. The only requirement is the use of KVM VirtIO drivers. IONOS provides a number of ready-to-boot images with multiple versions of Microsoft Windows and different Linux distributions, including Red Hat Enterprise Linux.

Availability Zones

Secure your data, enhance reliability, and set up high-availability scenarios by deploying your Dedicated Core Servers and storage devices across multiple Availability Zones.

Assigning different Availability Zones ensures that servers or storage devices reside on separate physical resources at IONOS.

For example, a server or a storage device assigned to Availability Zone 1 resides on a different resource than a server or storage device assigned to Availability Zone 2.

You have the following Availability Zone options:

• Zone 1

• Zone 2

• A - Auto (default; our system automatically assigns an Availability Zone upon provisioning)

Live Vertical Scaling (LVS)

If the capacity of your Virtual Data Center no longer matches your requirements, you can still increase or decrease your resources after provisioning. Upscaling resources allows you to change the resources of a Dedicated Core Server without restarting it, permitting you to add RAM or NICs ("hot plug") to it while it is running. This change allows you to react to peak loads quickly without compromising performance.

After uploading, you can define the properties for your own images before applying them to new storage volumes. The settings must be supported by the image, otherwise, they will not work as expected. After provisioning, you can change the settings directly on the storage device, which will require a restart of the server.

The types of resources that you can scale without rebooting will depend on the operating system of your VMs. Since kernel 2.6.25, Linux has LVO modules installed by default, but you may have to activate them manually depending on the derivative. For more information, see Linux VirtIO page.

For IONOS images, the supported properties are already preset. Without restarting the Dedicated Core Server, its resources can be scaled as follows:

• Upscaling: CPU, RAM, NICs, storage volumes

• Downscaling: NICs, storage volumes

Scaling up is the increase or speed up of a component to handle a larger load. The goal is to increase the number of resources that support an application to achieve or maintain accurate performance. Scaling down means reducing system resources, irrespective of whether you have used the scaling up approach. Without restarting the Dedicated Core Server, only upscaling is possible.

Limitations

CPU Types: Dedicated Core Server configurations are subject to the following limitations, by CPU type:

AMD CPU

Intel® CPU

*Additional RAM sizes are available on request. To increase the RAM size, contact your sales representative or customer support.

A single Intel® physical core with Hyper-Threading Technology is exposed to the operating system of your Dedicated Core Server as two distinct “logical cores”, which process separate threads.

RAM Sizes: Because the working memory (RAM) size cannot be processed during the initial configuration, newly provisioned servers with more than 8 GB of RAM may not start successfully when created from IONOS Windows images.

Live Vertical Scaling: Linux supports the entire scope of IONOS Live Vertical Scaling, whereas Windows is limited to CPU scaling. Furthermore, it is not possible to use LVS to reduce storage size after provisioning.

A vCPU Server that you create is a new virtual machine provisioned and hosted in one of IONOS physical data centers. A vCPU Server behaves exactly like physical servers and you can use them either standalone or in combination with other IONOS Cloud products.

You can create and configure your vCPU Server visually using the DCD interface. For more information, see Set Up a vCPU Server. However, the creation and management of a vCPU Server can be easily automated via the Cloud API, as well as our custom-made tools like SDKs.

vCPU Servers add a new dimension to your computing experience. These servers are configured with virtual CPUs and distributed among multiple users sharing the same physical server. The performance of your vCPU Server relies on various factors, including the underlying CPU of the physical server, virtual machine configurations, and the current load on the physical server. Our Data Center Dashboard (DCD) lets you closely monitor your CPU utilization and other essential metrics through the Monitoring Manager.

Boot options: For each vCPU Server, you can select to boot from a virtual CD-ROM/DVD drive or from a storage device (HDD or SSD) using any operating system on the platform. The only requirement is the use of KVM VirtIO drivers. IONOS provides a number of ready-to-boot images with current versions of Linux operating systems.

Availability Zones

Secure your data, enhance reliability, and set up high-availability scenarios by deploying your vCPU Servers and storage devices across multiple Availability Zones allowing you to deploy your Shared vCPU instances in different geographic regions.

Assigning different Availability Zones ensures that vCPU Servers or storage devices reside on separate physical resources at IONOS. This helps ensure high availability and fault tolerance for your applications, as well as providing low-latency connections to your target audience.

For example, a vCPU Server or a storage device assigned to Availability Zone 1 resides on a different resource than a vCPU Server or storage device assigned to Availability Zone 2.

You have the following Availability Zone options:

• Zone 1

• Zone 2

• A - Auto (default; our system automatically assigns an Availability Zone upon provisioning)

Live Vertical Scaling (LVS)

If the capacity of your Virtual Data Center (VDC) no longer matches your requirements, you can still increase or decrease your resources after provisioning. Upscaling resources allows you to change the resources of a vCPU Server without restarting it, permitting you to add RAM or NICs ("hot plug") to it while it is running. This change allows you to react to peak loads quickly without compromising performance.

After uploading, you can define the properties for your own images before applying them to new storage volumes. The settings must be supported by the image, otherwise, they will not work as expected. After provisioning, you can change the settings directly on the storage device, which will require a restart of the vCPU Server.

The types of resources that you can scale without rebooting will depend on the operating system of your vCPU Server. Since kernel 2.6.25, Linux has LVO modules installed by default, but you may have to activate them manually depending on the derivative. For more information, see Linux VirtIO.

For IONOS images, the supported properties are already preset. Without restarting the vCPU Server, its resources can be scaled as follows:

• Upscaling: CPU, RAM, NICs, storage volumes

• Downscaling: NICs, storage volumes

Scaling up is the increase or speed up of a component to handle a larger load. The goal is to increase the number of resources that support an application to achieve or maintain accurate performance. Scaling down means reducing system resources, whether or not you have used the scaling up approach. Without restarting the vCPU Server, only Upscaling is possible.

vCPU Server Features

vCPU Server provides the following features:

• Flexible Resource Allocation provides you with presets, which are recommended vCPU-to-RAM configurations for your virtual machines. Furthermore, this option empowers you to add or remove compute resources flexibly in order to meet your specific needs.

• The Robust Compute Engine platform supports the vCPU servers, ensuring seamless integration. Additionally, the features offered by the Compute Engine platform remain accessible for utilization with vCPU servers

• Virtualization Technology enables efficient and secure isolation between different virtual machines (VMs), ensuring the performance of one VM does not impact the others.

• Reliable Performance and computing capabilities make it suitable for a wide range of applications. The underlying infrastructure is optimized to provide reliable CPU performance, ensuring your applications run smoothly.

• Easy Management via the intuitive Data Center Designer. You can easily create, modify, and delete vCPU Servers, monitor their usage, and adjust the resources according to your needs.

vCPU Server Benefits

vCPU Server provides the following benefits:

• Cost-Effective: vCPU Server helps reduce costs when compared to major hyperscalers with similar resource configurations. This makes it an ideal choice for small to medium-sized businesses or individuals with budget constraints.

• Scalability: With IONOS vCPU Server, you have the flexibility to scale your computing resources up or down based on your requirements. This ensures that you can meet the demands of your applications without overprovisioning or paying for unused resources.

• Reliability and Availability: IONOS's cloud infrastructure ensures high availability and reliability. By distributing resources across multiple physical servers, IONOS minimizes the impact of hardware failures, providing a stable and resilient environment for your applications.

• Easy Setup: Setting up IONOS vCPU Server is straightforward. The IONOS DCD and Cloud API offers controls for provisioning and configuring vCPU Servers, allowing you to get up and running quickly.

Limitations of vCPU Servers

This section lists the limitations of vCPU Servers:

CPU Family of a vCPU Server cannot be chosen at the time of creation and cannot be changed later. vCPU Server configurations are subject to the following:

*Larger RAM sizes can be made available on request.

RAM Sizes: Because the working memory (RAM) size cannot be processed during the initial configuration, a newly provisioned vCPU Server with more than 8 GB of RAM may not start successfully when created from the IONOS Windows images.

Live Vertical Scaling: Linux supports the entire scope of IONOS Live Vertical Scaling, whereas Windows is limited to CPU scaling. Furthermore, it is not possible to use LVS to reduce storage size after provisioning.

When creating storages based on IONOS Linux images, you can insert SSH keys into your VM. This lets you access your VM safely and allows for secure communication. SSH keys that you intend to use more often can be saved in the DCD's SSH Key Manager.

Types of SSH keys

Default SSH keys: SSH keys that you intend to use often and mark them as such in the SSH Key Manager. Default SSH keys are preselected when you configure storage devices. You can specify which SSH keys are actually to be used before provisioning and deselecting the preselected standard keys in favor of another SSH key.

Ad-hoc SSH keys: SSH keys that you only use once and don't intend to save in the SSH Key Manager for later re-use.

Generating an SSH key

SSH keys can be generated and used on macOS or Linux if both OpenSSH and the ssh-keygen command-line tools are installed. OpenSSH is a collection of tools for establishing SSH connections to remote servers, while ssh-keygen is a utility for generating SSH keys.

Manually generate SSH keys when working with OpenSSH via the Terminal application by following the steps below.

1. Enter the following command below into the Terminal window and press ENTER.

ssh-keygen

The key generation process is initiated by the command above. When you run this command, the ssh-keygen utility prompts you for a location to save the key.

2. Accept the default location by pressing the ENTER key, or enter the path to the file where you want to save the key /home/username/.ssh/id_rsa.

Enter file in which to save the key (/home/username/.ssh/id_rsa):

/home/username/.ssh/id_rsa already exists.
Overwrite (y/n)?

3. Enter the passphrase that will be used to encrypt the private key file on the disk. You can also press ENTER to accept the default (no passphrase). However, we recommend that you use a passphrase.

4. Enter your passphrase once more.

After you confirm the passphrase, the public and private keys are generated and saved in the specified location. Thus, the confirmation will look like this:

Your identification has been saved in /home/username/.ssh/id_rsa.
Your public key has been saved in /home/username/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:AcP/ieiAOoD7MjrKepXks/qHAhrRasGOysiaIR94Quk username@mb01739.local
The key's randomart image is:
+---[RSA 3072]----+
|     .o          |
|      .o         |
|..     ..        |
|.oo .   ..       |
|+=.+ . .So .     |
|X+. * . . o      |
|&Eo. *           |
|&Oo.o o          |
|@O++..           |
+----[SHA256]-----+

You can copy the public key to your clipboard by running the following command:

 pbcopy < ~/.ssh/id_rsa.pub

Storing SSH keys

In the SSH Key Manager of the DCD, you can save and manage up to 100 public SSH keys for the setup of SSH accesses. This saves you from having to repeatedly copy and paste the public part of an SSH key from an external source.

1. To open the SSH Key Manager, go to Menu > MANAGER resources > SSH Key Manager.

2. In the SSH Key Manager, select + Add Key.

3. Enter a Name and click Add.

4. Copy and paste the public key to the SSH key field. Alternatively, you may upload it via Select key file. Please ensure the SSH keys you enter are valid. The DCD does not validate syntax or format.

5. (Optional) Activate the Default checkbox to have the SSH key automatically pre-selected when SSH access is configured.

6. Click Save to store the key.

The SSH key is stored in the SSH Key Manager and can be used for the configuration of SSH accesses.

Deleting an SSH key in the SSH Key Manager

To delete an existing SSH key, select the SSH key from the list and click Delete Key.

The SSH key is removed from the SSH Key Manager.

Connecting via OpenSSH

You can connect to your virtual instance via OpenSSH. Still, you will need the terminal application, which varies depending on your operating system. For:

• Linux: Search Terminal or press CTRL+ALT+T

• macOS: Search Terminal

• Windows: Search Bash. If you don’t have Bash installed, use PuTTY instead.

The steps below will show you how to connect to your VM.

1. Open the Terminal application and enter the SSH connection command below. After the @, add the IP address of your VM instance. Then press ENTER.

ssh root@85.215.230.154

2. Authentication is the next step in the connection process. If you've added the SSH keys, you'll be able to connect to the VM immediately or after entering your key pair's passphrase.

If you haven't already added SSH keys, you'll be asked for your password:

root@85.215.230.154's password:

3. Once you’ve entered the password, press ENTER.

If the SSH key is configured correctly, this will log you into VM.

Generating an SSH key

SSH keys can be generated and used on macOS or Linux if both OpenSSH and the ssh-keygen command-line tools are installed. OpenSSH is a collection of tools for establishing SSH connections to remote servers, while ssh-keygen is a utility for generating SSH keys.

An SSH key is composed of two files. The first is the private key, which should never be shared. The other is a public key that enables you to access your provisioned Cubes. When you generate the keys, you will use ssh-keygen to store them in a secure location so that you can connect to your instances without encountering the login prompt.

Manually generate SSH keys when working with OpenSSH via the Terminal application by following the steps below.

Enter the following command below into the Terminal window and press ENTER.

ssh-keygen

The key generation process is initiated by the command above. When you run this command, the ssh-keygen utility prompts you for a location to save the key.

Accept the default location by pressing the ENTER key, or enter the path to the file where you want to save the key /home/username/.ssh/id_rsa.

Enter file in which to save the key (/home/username/.ssh/id_rsa):

/home/username/.ssh/id_rsa already exists.
Overwrite (y/n)?

Enter the passphrase that will be used to encrypt the private key file on the disk. You can also press ENTER to accept the default (no passphrase). However, we recommend that you use a passphrase.

Enter your passphrase once more.

After you confirm the passphrase, the public and private keys are generated and saved in the specified location. Thus, the confirmation will look like this:

Your identification has been saved in /home/username/.ssh/id_rsa.
Your public key has been saved in /home/username/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:AcP/ieiAOoD7MjrKepXks/qHAhrRasGOysiaIR94Quk username@mb01739.local
The key's randomart image is:
+---[RSA 3072]----+
|     .o          |
|      .o         |
|..     ..        |
|.oo .   ..       |
|+=.+ . .So .     |
|X+. * . . o      |
|&Eo. *           |
|&Oo.o o          |
|@O++..           |
+----[SHA256]-----+

The public key is saved to the fileid_rsa.pubwhich will be the key you upload to your DCD account. Your private key is saved to the id_rsa file in the .ssh directory and is used to verify that the public key you use belongs to the same DCD account.

You can copy the public key to your clipboard by running the following command:

 pbcopy < ~/.ssh/id_rsa.pub

Adding the SSH key to the DCD Resource Manager

In addition to the SSH Keys stored in the SSH Key Manager, the IONOS Cloud Cubes SSH key concept includes:

• Default keys

• Ad-hoc SSH Keys.

Default keys are SSH keys that you intend to use frequently and have marked as such in the SSH Key Manager. When you configure storage devices, the default SSH keys are pre-selected. You can, however, specify which SSH keys are to be used before provisioning and deselect the preselected standard keys in favor of another SSH key.

Ad-hoc SSH keys, on the other hand, are SSH keys that you only use once and do not intend to save in the SSH Key Manager for future use.

The DCD's SSH Key Manager allows you to save and manage up to 100 public SSH keys for SSH access setup. This saves you from having to copy and paste the public part of an SSH key from an external source multiple times.

Log in to your DCD account after copying the SSH key to the clipboard (Link).

1. Open the SSH Key Manager: Menu > Management > SSH Keys

2. Select the + Add Key in the top left corner.

3. Paste the SSH key from the clipboard into the SSH Key field. If you have saved your SSH Key in a file, you can upload it by selecting the Choose file button in the Select Key file field.

Optional: Select the Default checkbox to have the SSH key pre-selected when configuring SSH access.

4. Click Save to save the key. The SSH key has now been saved in the SSH Key Manager and is visible in the SSH Key Manager's table of keys.

Connecting via OpenSSH

You can connect to your Cubes instance via OpenSSH. Still, you will need the terminal application, which varies depending on your operating system. For:

• Linux: Search Terminal or press CTRL+ALT+T

• macOS: Search Terminal

• Windows: Search Bash. If you don’t have Bash installed, use PuTTY instead.

The steps below will show you how to connect to your Cubes.

Open the Terminal application and enter the SSH connection command below. After the @, add the IP address of your Cubes instance. Then press ENTER.

ssh root@85.215.230.154

Authentication is the next step in the connection process. If you've added the SSH keys, you'll be able to connect to the Cubes immediately or after entering your key pair's passphrase.

If you haven't already added SSH keys, you'll be asked for your password:

root@85.215.230.154's password:

Nothing is displayed in the terminal when you enter your password, making it easier to paste in the initial password. Pasting into text-based terminals is different from other desktop applications. It is also different from one window manager to another:

• For Linux Gnome Terminal, use CTRL+SHIFT+V.

• For macOS, use the SHIFT-CMD-V or a middle mouse button.

• For Bash on Windows, right-click on the window bar, choose Edit, then Paste. You can also right-click to paste if you enable QuickEdit mode.

Once you’ve entered the password, press ENTER.

If the SSH key is configured correctly, this will log you into the Cloud Cubes.

Introduction

The Account Management panel is accessed by clicking on your name and email address. Here you can perform key administrative tasks related to your account and contract. Only Contract Owners have complete access. Consult access levels by user Role:

My Settings

You can set default values for future VDCs. Each time you open a new VDC, DCD will place your resources in the preset location, assigning them the same number of cores, memory size, storage capacity, and reserved IP addresses. For example, you can specify that all new VDCs must be located in Karlsruhe, or that all processors will use the Intel architecture.

1. Go to Account Management > My Settings.

2. In the My Settings panel, set default values for Session, Data Center, Server, and Storage.

Your new values are valid immediately. You may undo your changes by clicking on Reset or the Reset All button.

Password & Security

Your IONOS Cloud account comes with a number of security features to protect you from unauthorized access:

Changing your password

You define the password for your IONOS account yourself during the registration process. Your password must contain at least eight characters and a mixture of upper and lowercase letters and special characters.

1. Go to Account Management > Password & Security > Change Password.

2. Enter your Current Password and the New Password twice. Click Change Password.

The password is changed and becomes effective with the next login.

2-Factor Authentication

In addition to log-in credentials, this authentication method also requires an app-generated security code. Once 2-Factor Authentication has been activated, you can only access your account by receiving this code from the Google Authenticator App. This method can be extended to hide specific data centers and snapshots from users, even if they belong to an authorized group. This feature is only available in DCD.

Prerequisites: The Google Authenticator App is compatible with all Android or iOS mobile devices. You can install it on your device, free of charge, from the Google Play Store or from Apple iTunes. The app must be able to access your camera and the time on the mobile device needs to be set automatically.

Setting Support PIN

To ensure support calls are made by authorized users, we usually ask for the support PIN to verify the account. You can set your support PIN in the DCD and change it at any time. To set or change your support PIN, use the following procedure:

1. Go to Account Management > Password & Security > Set Support PIN.

2. Enter your support PIN in the PIN field. Click Set Support PIN.

The support PIN is now saved. You can use it to verify your account with Customer Support.

Resource Overview

In this tab, you can track the global usage of resources available in your account.

Furthermore, this page provides an overview of usage limits per virtual instance.

Cost and Usage

In this tab, you can view the breakdown of estimated costs for the next invoice. The costs displayed in the DCD are a non-binding extrapolation based on your resource allocation since the last invoice. Please refer to your invoice for the actual costs. For more pricing information, please visit our Features and prices page.

1. Go to Account Management > Cost and Usage. The list breaks down your Snapshot, IP address, and Data Center usage.

2. You may click the down arrow to expand each section to view individual item charges.

The Total amount displayed excludes VAT.

Payment Method

As a contract owner, you can choose between two payment methods: direct debit or a credit card.

1. Open the Account Management > Payment Method.

2. Choose either method, enter your information, and Submit.

Credit card data are safely stored with our payment service provider. If you choose to pay by direct debit, you will receive a form from us with which we ask you to give us a direct debit authorisation in writing.

Contract Owners

Custom settings: If you wish to change your e-mail address or username, please contact your sales representative or our IONOS enterprise support team.

Removing a user account: As a contract owner or administrator, you can cancel a user account by removing the user from the User Manager. Resources created by the user are not deleted.

Canceling your account: If you wish to cancel your Enterprise Cloud (IaaS) contract and delete your account including all VDCs completely, please contact your IONOS account manager or the IONOS enterprise support team.

With IONOS Cloud Compute Engine, you can quickly provision Dedicated Core servers and vCPU Servers. Leverage our user guides, reference documentation, and FAQs to support your hosting needs.

Product Overview

Developer Tools

Recommended How-To's

Frequently Asked Questions

A user with full root or administrator access rights can create a vCPU Server. A vCPU Server, once provisioned, retains all its settings, such as resources, drive allocation, password, etc., even after a restart at the operating system level. A vCPU Server is deleted from your Virtual Data Center (VDC) only when you delete it from the DCD. For more information, see vCPU Servers.

Create a vCPU Server

1. Drag the vCPU Server element from the Palette onto the Workspace.

The created vCPU Server is automatically highlighted in turquoise. The Inspector pane allows you to configure the properties of this individual vCPU instance.

2. In the Inspector pane on the right, configure your vCPU Server in the Settings tab.

• Name: Choose a name unique to this VDC.

• Availability Zone: The zone where you wish to physically host the vCPU. Choosing A - Auto selects a zone automatically. This setting can be changed after provisioning.

• Preset: Select an appropriate configuration from the drop-down list. The values S, M, L, XL, and XXL contain predefined vCPU-to-RAM ratios. You can always override the values to suit your needs and the Preset automatically changes to Custom when you edit the predefined ratio indicating that you are no longer using the predefined ratio.

• vCPUs: Specify the number of vCPUs. You may change these after provisioning. The capabilities are limited to your customer contract limits. For more information about the contract resource limits in DCD, see Resource Overview.

• RAM: Specify RAM size; you may choose any size between 0.25 GB to 240 GB in steps of 0.25 GB. This setting can be increased after provisioning.

• SSH Keys: Select premade SSH Key. You must first have a key stored in the SSH Key Manager. For more information about how to create and add SSH Keys, see OpenSSH Instructions.

• Ad-hoc Key: Copy and paste the public part of your SSH key into this field.

Add a bootable drive

1. Drag a storage element (HDD or SSD) from the Palette onto a vCPU server in the Workspace to connect them together. The highlighted vCPU will expand with a storage section.

2. Click the Unnamed HDD Storage to highlight the storage section. Now you can see new options in the Inspector pane on the right.

Configure Storage

1. Enter a name that is unique within your VDC.

2. Select a zone in which you want the storage device to be maintained. When you select A (Auto), our system assigns the optimal Zone. The Availability Zone cannot be changed after provisioning.

3. Specify the required storage capacity. You can increase the size after provisioning, even while the vCPU Server is running, as long as its operating system supports it. It is not possible to reduce the storage size after provisioning.

You can select one of IONOS images or snapshots, or use your own. Only images and snapshots that you have access to are available for selection. Since provisioning does not require you to specify an image, you can also create empty storage volumes.

Authentication

1. Set the root or administrator password for your vCPU according to the guidelines. This is recommended for both operating system types.

2. Select an SSH key stored in the SSH Key Manager.

3. Copy and paste the public part of your SSH key into this field.

4. Select the storage volume from which the vCPU is to boot by clicking on BOOT or Make Boot Device.

5. Provision your changes. The storage device is now provisioned and configured according to your settings.

Alternative Mode

• When adding a storage element using the Inspector, select the appropriate checkbox in the Add Storage dialog box. If you wish to boot from the network, set this on the vCPU: vCPU in the Workspace > Inspector > Storage.

• It is recommended to always use VirtIO to benefit from the full performance of InfiniBand. IDE is intended for troubleshooting if, for instance, the operating system has no VirtIO drivers installed. In this case, Windows usually displays a "blue screen" when booting.

• After provisioning, the Live Vertical Scaling properties of the selected image are displayed. You can make changes to these properties later, which will require a reboot. You can set the properties of your uploaded images before you apply them to storage volumes in the Image Manager.

• (Optional) Add and configure further storage elements.

• (Optional) Make further changes to your data center.

• Provision your changes. The storage device is now provisioned and configured according to your settings.

Add a CD-ROM drive

To assign an image and specify a boot device, you need to add and configure a storage element.

• Click on CD-ROM to add a CD-ROM drive so that you can use ISO images to install and configure an operating system from scratch.

• Set up a network by connecting the vCPU Server to other elements, such as an internet access element or other vCPU Server through their NICs.

• Provision your changes.

The vCPU Server is available according to your settings.

Stop, Start or Reset a vCPU Server

At IONOS, we maintain dedicated resources for each customer. Hence, you do not share your physical CPU with other IONOS clients. For this reason, the vCPU Server switched off at the operating system level, still incurs costs.

You can shut down a vCPU Server completely via the DCD and deallocate all its resources to avoid incurring costs. A vCPU Server deallocated this way remains in your infrastructure while the resources are released and can then be redistributed.

Shutting down a vCPU Server at the operating system level alone does not deallocate the resources or suspend the billing. Regardless of how you shut down the vCPU Server, you can restart it only via the DCD.

A reset forces the vCPU Server to shut down and reboot but may result in data loss.

Stop a vCPU Server

1. Choose a vCPU Server. From the Settings tab in the Inspector pane, select Power > Stop.

2. In the dialog box that appears, confirm your action by selecting the appropriate checkbox and clicking Apply STOP.

3. Provision your changes. Confirm the action by entering your password.

Start a vCPU Server

1. Choose a vCPU Server. From the Settings tab in the Inspector pane, select Power > Start.

2. In the dialog box that appears, confirm your action by selecting the appropriate checkbox and clicking Apply START.

3. Provision your changes. Confirm the action by entering your password.

Reset a vCPU Server

1. Choose a vCPU Server. From the Settings tab in the Inspector pane, select Power > Reset.

2. (Optional) In the dialog box that appears, connect using the Remote Console and shut down the vCPU Server at the operating system level to prevent data loss.

3. Confirm your action by selecting the appropriate checkbox and clicking Apply RESET.

4. Provision your changes. Confirm the action by entering your password.

Scale a vCPU Server

1. In the Workspace, select the required vCPU Server and use the Inspector pane on the right.

2. Modify storage:

• (Optional) Create a snapshot of the system for recovery in the event of problems.

3. In the Workspace, select the required vCPU Server and increase the CPU size.

4. Provision your changes. You must set the new size at the operating system level of your vCPU Server.

Delete a vCPU Server

When you no longer need a particular vCPU Server, with or without the associated storage devices, in your cloud infrastructure, you can remove it with a single mouse click or via the keyboard.

To ensure that no processes are interrupted, and no data is lost, we recommend you turn off the vCPU Server before you delete it.

1. Select the vCPU Server in the Workspace.

2. Right-click and open the context menu of the element. Select Delete Server.

2. You may also select the element icon and press the DEL key.

3. In the dialog box that appears, choose whether you also want to delete storage devices that belong to the vCPU Server.

4. Provision your changes.

You can enable IPv6 on Dedicated Core servers and vCPU Servers when you create them or after you create them.

Set up IPv6

You can set up IPv6 to improve the network connectivity for your virtualized environment. By setting up IPv6 for your Dedicated Core servers and vCPU Servers, you can ensure that they are accessible to IPv6-enabled networks and clients.

The user who creates the Dedicated Core server has full root or administrator access rights. A server, once provisioned, retains all its settings (resources, drive allocation, password, etc.), even after a restart at the operating system level. The server will only be removed from your Virtual Data Center once you delete a server in the DCD. For more information, see Dedicated Core Servers.

Create a Dedicated Core Server

1. Drag the Dedicated Core server element from the Palette onto the Workspace.

The created Dedicated Core server is automatically highlighted in turquoise. The Inspector pane allows you to configure the properties of this individual server instance.

2. In the Inspector pane on the right, configure your server in the Settings tab.

• Name: Choose a name unique to this VDC.

• Availability Zone: The zone where you wish to physically host the server. Choosing A - Auto selects a zone automatically. This setting can be changed after provisioning.

• CPU Architecture: Choose between AMD or Intel cores. You can later change the CPU type for a Dedicated Core server that is already running, though you will have to restart it first.

• Cores: Specify the number of CPU cores. You may change these after provisioning. Note that there are configuration limits.

• RAM: Specify RAM size; you may choose any size between 0.25 GB to 240 GB in steps of 0.25 GB. This setting can be increased after provisioning.

• SSH Keys: Select premade SSH Key. You must first have a key stored in the SSH Key Manager. Learn how to create and add SSH Keys.

• Ad-hoc Key: Copy and paste the public part of your SSH key into this field.

Add a bootable drive

1. Drag a storage element (HDD or SSD) from the Palette onto a Dedicated Core server in the Workspace to connect them together. The highlighted VM will expand with a storage section.

2. Click the Unnamed HDD Storage to highlight the storage section. Now you can see new options in the Inspector pane on the right.

Configure Storage

1. Enter a name that is unique within your VDC.

2. Select a zone in which you want the storage device to be maintained. When you select A (Auto), our system assigns the optimal Zone. The Availability Zone cannot be changed after provisioning.

3. Specify the required storage capacity. You can increase the size after provisioning, even while the vCPU Server is running, as long as its operating system supports it. It is not possible to reduce the storage size after provisioning.

You can select one of IONOS images or snapshots, or use your own. Only images and snapshots that you have access to are available for selection. Since provisioning does not require you to specify an image, you can also create empty storage volumes.

Authentication

1. Set the root or administrator password for your Dedicated Core server according to the guidelines. This is recommended for both operating system types.

2. Select an SSH key stored in the SSH Key Manager.

3. Copy and paste the public part of your SSH key into this field.

4. Select the storage volume from which the Dedicated Core server is to boot by clicking on BOOT or Make Boot Device.

5. Provision your changes. The storage device is now provisioned and configured according to your settings.

Alternative Mode

• When adding a storage element using the Inspector pane, select the appropriate check box in the Add Storage dialog box. If you wish to boot from the network, set this on the Dedicated Core server: Dedicated Core server in the Workspace > Inspector pane > Storage.

• It is recommended to always use VirtIO to benefit from the full performance of InfiniBand. IDE is intended for troubleshooting if, for instance, the operating system has no VirtIO drivers installed. In this case, Windows usually displays a "blue screen" when booting.

• After provisioning, the Live Vertical Scaling properties of the selected image are displayed. You can make changes to these properties later, which will require a reboot. You can set the properties of your uploaded images before you apply them to storage volumes in the Image Manager.

• (Optional) Add and configure further storage elements.

• (Optional) Make further changes to your data center.

• Provision your changes. The storage device is now provisioned and configured according to your settings.

Add a CD-ROM drive

To assign an image and specify a boot device, you need to add and configure a storage element.

• Click on CD-ROM to add a CD-ROM drive so that you can use ISO images to install and configure an operating system from scratch.

• Set up a network by connecting the Dedicated Core server to other elements, such as an internet access element or other servers through their NICs.

• Provision your changes.

The Dedicated Core server is available according to your settings.

Stop, Start, or Reset a Dedicated Core Server

We maintain dedicated resources available for each customer. You do not share your physical CPUs with other IONOS clients. For this reason, the servers switched off at the operating system level, still incur costs.

You should use the DCD to shut down virtual machines so that resources are completely deallocated, and no costs are incurred. Dedicated Core servers deallocated this way remain in your infrastructure while the resources are released and can then be redistributed.

This can only be done in the DCD. Shutting down a VM at the operating system level alone does not deallocate the resources or suspend the billing. Regardless of how the VM is shut down, it can only be restarted using the DCD.

A reset forces the Dedicated Core server to shut down and reboot but may result in data loss.

Stop a Dedicated Core Server

1. Choose a Dedicated Core server. From the Settings tab in the Inspector pane, select Power > Stop.

2. In the dialog box that appears, confirm your action by selecting the appropriate checkbox and clicking Apply STOP.

3. Provision your changes. Confirm the action by entering your password.

Start a Dedicated Core Server

1. Choose a Dedicated Core server. From the Settings tab in the Inspector pane, select Power > Start.

2. In the dialog box that appears, confirm your action by selecting the appropriate box and clicking Apply START.

3. Provision your changes. Confirm the action by entering your password.

Reset a Dedicated Core Server

1. Choose a Dedicated Core server. From the Settings tab in the Inspector pane, select Power > Reset.

2. (Optional) In the dialog box that appears, connect using the Remote Console and shut down the VM at the operating system level to prevent data loss.

3. Confirm your action by selecting the appropriate box and clicking Apply RESET.

4. Provision your changes. Confirm the action by entering your password.

Scale a Dedicated Core Server

1. In the Workspace, select the required Dedicated Core server and use the Inspector pane on the right.

2. Modify storage:

• (Optional) Create a snapshot of the system for recovery in the event of problems.

3. In the Workspace, select the required Dedicated Core server and increase the CPU size.

4. Provision your changes. You must set the new size at the operating system level of your VM.

Delete a Dedicated Core Server

When you no longer need a particular Dedicated Core server, with or without the associated storage devices, in your cloud infrastructure, you can remove it with a single mouse click or via the keyboard.

To ensure that no processes are interrupted and no data is lost, we recommend you turn off the Dedicated Core server before you delete it.

1. Select the Dedicated Core server in the Workspace.

2. Right-click and open the context menu of the element. Select Delete.

2. You may also select the element icon and press the DEL key.

3. In the dialog box that appears, choose whether you also want to delete storage devices that belong to the server.

4. Provision your changes.

Overview

Cloud-init is a software package that automates the initialization of servers during system boot. When you deploy a new Linux server from an image, cloud-init gives you the option to set default user data.

User data must be written in shell scripts or cloud-config directives using YAML syntax. You can modify IONOS cloud-init's behavior via user-data. You can pass the user data in various formats to the IONOS cloud-init at launch time. Typically, this happens as a template, a parameter in the CLI, etc. This method is highly compatible across platforms and fully secure.

Compatibility: This service is supported on all public IONOS Cloud Linux distributions. You may submit user data through the DCD or via Cloud API. Existing cloud-init configurations from other providers are compatible with IONOS Cloud.

Limitations: Cloud-init is available on all public Linux images supplied by IONOS Cloud. If you wish to use your own Linux image, please make sure that it is cloud-init supported first. Otherwise, there is no guarantee that the package will function as intended. Windows images are currently out of scope; adding them may be considered at a later stage.

Provisioning: Cloud-init can only be set at initial provisioning. It cannot be applied to instances that have already been provisioned. Settings cannot be changed once provisioned.

Laptops: When using a laptop, scroll down the properties panel of the block storage volume that you want to create and configure, as additional fields are not immediately visible on a small screen. Clout-Init may only become visible when an supported image has been selected.

Supported user data formats

The following table demonstrates the use of cloud-config and user-data scripts. However, the cloud-init package supports a variety of formats.

Configuring user data via the DCD

1. Log in to the DCD with your username and password.

2. In the Workspace, create a new virtual instance and attach any storage device to it.

3. Select the storage device and from the Inspector pane associate an Image with it.

   • To associate a private image, select Own Images from the drop-down list.

   • To associate a public image, select IONOS Images from the drop-down list. Once you choose an image, additional fields will appear in the Inspector pane.

1. Enter a Password. It is required for Remote Console access. You may change it later.

2. (Optional) Upload a new SSH key or use an existing file. SSH Keys can also be injected as user data utilizing cloud-init.

3. (Optional) Add a specific key to the Ad-hoc SSH Key field.

4. Select No configuration for Cloud-Init user data and the Cloud-Init User Data window appears.

5. Enter your User Data either using a bash script or a cloud-config file with a YAML syntax. For sample scripts, see Use shell scripts, Use cloud-config directives, and Configure user data via API.

1. To complete setup, return to the Inspector pane and click Provision Changes.

Use shell scripts

Using shell scripts is an easy way to bootstrap a server. The code creates, installs, and configures our CentOS web server in the following example. It also rewrites the default index.html file.

#!/bin/bash
# Use this for your user data (script from top to bottom)
# install httpd (Linux 2 version)
yum update -y
yum install -y httpd
systemctl start httpd
systemctl enable httpd
echo "<h1>Hello World from $(hostname -f)</h1>" > /var/www/html/index.html

To test if the cloud-init bootstrapped your VM successfully, you can open the corresponding IP address in your browser. You will be greeted with a “Hello World” message from your web server.

Use cloud-config directives

You can also bootstrap cloud-init images using cloud-config directives. The cloud-init website outlines all the supported modules and provides examples of basic directives.

Example 1: Create a swap partition

The following script is an example of how to create a swap partition with second block storage using a YAML script:

#cloud-config
fs_setup:
  - label: mylabel
    device: /dev/vda
    filesystem: ext4
  - label: swap
    device: /dev/vdb
    filesystem: swap
mounts:
- [ /dev/vda, /, ext4, defaults, 0, 0 ]
- [ /dev/vdb, none, swap, sw, 0, 0 ]

Example 2: Resize the file system

The following script is an example of how to resize your file system according to the chosen size of the block storage. It will also create a user with an SSH key using a cloud-config YAML script:

#cloud-config
resize_rootfs: True
users:
  - name: pb-user
    gecos: Demo User
    sudo: ALL=(ALL) NOPASSWD:ALL
    groups: users, admin
    ssh_import_id: None
    lock_passwd: true
    ssh_authorized_keys:
      - ssh-rsa AAAA...

Output log files

The cloud-init output log file (/var/log/cloud-init-output.log) captures console output. Depending on the default configuration for logging, a second log file exists within /var/log/cloud-init.log. This provides a comprehensive record based on the user data.

Configure user data via API

The cloud API offers increased convenience if you want to automate the provisioning and configuration of cloud instances. Enter the following details:

• Name: Enter the userData.

• Type: Enter the type in the form of a string.

• Description: The cloud-init configuration for the volume as base64 encoded string. The property is immutable and is only allowed to be set on a new volume creation. It is mandatory to provide either public image or imageAliasthat has cloud-init compatibility in conjunction with this property.

Cloud-init is configured on the volume resource for cloud API V6 or later versions. For more information, see CLOUD API (6.0).

Curl example

The following script is an example of how to configure userData using curl:

curl --include \
     --request POST \
     --user '<user:password>' \
     --header "Content-Type: application/json" \
     --data-binary '{
         "properties": {
             "name": "Server-01",
             "ram": 2048,
             "cores": 1,
             "availabilityZone": "ZONE_1",
             "cpuFamily": "INTEL_SKYLAKE"
         },
         "entities": {
             "volumes": {
                 "items": [ {
                    "properties": {
                      "size": 10,
                      "type": "HDD",
                      "name": "Server-01_HDD",
                      "image": "bf4d1400-b48d-11eb-b9b3-d2869b2d44d9",
                      "imagePassword": "<pAsSW0rD>",
                      "sshKeys": ["<ssh_key>"],
                      "userData": "I2Nsb3VkLWNvbmZpZwoKcGFja2FnZXM6CiAgLSBodHRwZAogIC0gZmlyZXdhbGxkCgpydW5jbWQ6CiAgLSAvYmluL3N5c3RlbWN0bCBlbmFibGUgaHR0cGQKICAtIC9iaW4vc3lzdGVtY3RsIHN0YXJ0IGh0dHBkCiAgLSAvYmluL2ZpcmV3YWxsLW9mZmxpbmUtY21kIC0tYWRkLXBvcnQ9ODAvdGNwCiAgLSAvYmluL3N5c3RlbWN0bCBlbmFibGUgZmlyZXdhbGxkCiAgLSAvYmluL3N5c3RlbWN0bCBzdGFydCBmaXJld2FsbGQKICAtIGxvYWRrZXlzIGRlCgp3cml0ZV9maWxlczoKLSBjb250ZW50OiB8CiAgICA8IURPQ1RZUEUgaHRtbD4KICAgIDxodG1sPgogICAgICA8aGVhZD4KICAgICAgPC9oZWFkPgogICAgICA8Ym9keT4KICAgICAgICA8cD5XZWxjb21lIHRvIHlvdXIgbmV3IHdlYiBzZXJ2ZXIuPC9wPgogICAgICA8L2JvZHk+CiAgICA8L2h0bWw+CiAgcGF0aDogL3Zhci93d3cvaHRtbC9pbmRleC5odG1sCgpmaW5hbF9tZXNzYWdlOiAiVGhlIHN5c3RlbSBpcyBmaW5hbGx5IHVwLCBhZnRlciAkVVBUSU1FIHNlY29uZHMiCg=="
                    }
                 } ]
             },
             "nics": {
                 "items": [ {
                    "properties": {
                      "name": "NIC001",
                      "dhcp": true,
                      "lan": 1
                      }
                    } ]
             }
        }
        }' \
 https://api.ionos.com/cloudapi/v6/datacenters/<datacenter_id>/servers

IONOS Cloud Cubes are virtual private service instances with shared resources. Refer to our user guides, reference documentation, and FAQs to support your hosting needs.

Developer Tools

Recommended How-To's

Learn More

Generating an SSH key

can be generated and used on macOS or Linux if both OpenSSH and the ssh-keygen command-line tools are installed. OpenSSH is a collection of tools for establishing to remote servers, while ssh-keygen is a utility for generating SSH keys.

An SSH key is composed of two files. The first is the private key, which should never be shared. The other is a public key that enables you to access your provisioned Cubes. When you generate the keys, you will use ssh-keygen to store them in a secure location so that you can connect to your instances without encountering the login prompt.

Manually generate SSH keys when working with OpenSSH via the Terminal application by following the steps below.

Enter the following command below into the Terminal window and press ENTER.

The key generation process is initiated by the command above. When you run this command, the ssh-keygen utility prompts you for a location to save the key.

Accept the default location by pressing the ENTER key, or enter the path to the file where you want to save the key /home/username/.ssh/id_rsa.

Enter the passphrase that will be used to encrypt the private key file on the disk. You can also press ENTER to accept the default (no passphrase). However, we recommend that you use a passphrase.

Enter your passphrase once more.

After you confirm the passphrase, the public and private keys are generated and saved in the specified location. Thus, the confirmation will look like this:

You can copy the public key to your clipboard by running the following command:

Adding the SSH key to the DCD Resource Manager

• Default keys

• Ad-hoc SSH Keys.

Ad-hoc SSH keys, on the other hand, are SSH keys that you only use once and do not intend to save in the SSH Key Manager for future use.

The DCD's SSH Key Manager allows you to save and manage up to 100 public SSH keys for SSH access setup. This saves you from having to copy and paste the public part of an SSH key from an external source multiple times.

Log in to your DCD account after copying the SSH key to the clipboard (Link).

1. Open the SSH Key Manager: Menu > Management > SSH Keys

2. Select the + Add Key in the top left corner.

3. Paste the SSH key from the clipboard into the SSH Key field. If you have saved your SSH Key in a file, you can upload it by selecting the Choose file button in the Select Key file field.

Optional: Select the Default checkbox to have the SSH key pre-selected when configuring SSH access.

4. Click Save to save the key. The SSH key has now been saved in the SSH Key Manager and is visible in the SSH Key Manager's table of keys.

Connecting via OpenSSH

You can connect to your Cubes instance via OpenSSH. Still, you will need the terminal application, which varies depending on your operating system. For:

• Linux: Search Terminal or press CTRL+ALT+T

• macOS: Search Terminal

• Windows: Search Bash. If you don’t have Bash installed, use PuTTY instead.

The steps below will show you how to connect to your Cubes.

Authentication is the next step in the connection process. If you've added the SSH keys, you'll be able to connect to the Cubes immediately or after entering your key pair's passphrase.

If you haven't already added SSH keys, you'll be asked for your password:

Nothing is displayed in the terminal when you enter your password, making it easier to paste in the initial password. Pasting into text-based terminals is different from other desktop applications. It is also different from one window manager to another:

• For Linux Gnome Terminal, use CTRL+SHIFT+V.

• For macOS, use the SHIFT-CMD-V or a middle mouse button.

• For Bash on Windows, right-click on the window bar, choose Edit, then Paste. You can also right-click to paste if you enable QuickEdit mode.

Once you’ve entered the password, press ENTER.

Overview

is a software package that automates the initialization of during system boot. When you deploy a new Linux server from an , cloud-init gives you the option to set default user data. User data must be written in shell scripts or cloud-config directives using YAML syntax. This method is highly compatible across platforms and fully secure.

Compatibility: This service is supported on all public IONOS Cloud Linux distributions (Debian, CentOS, and Ubuntu). You may submit user data through the or via . Existing cloud-init configurations from other providers are compatible with IONOS Cloud.

Limitations: Cloud-init is available on all public images supplied by IONOS Cloud. If you wish to use your own Linux image, please make sure that it is cloud-init supported first. Otherwise, there is no guarantee that the package will function as intended. Windows images are currently out of scope; adding them may be considered at a later stage.

Provisioning: Cloud-init can only be set at initial provisioning. It cannot be applied to instances that have already been provisioned. Settings can't be changed once provisioned.

Laptops: When using a laptop, please scroll down the properties panel, as additional fields are not immediately visible on a small screen.

Supported user data formats

This tutorial demonstrates the use of cloud-config and user-data scripts. However, the cloud-init package supports a variety of formats.

Configuring user data via DCD

1. In the DCD, create a new virtual instance and attach any storage device to it.

2. Ensure the storage device is selected. Its Inspector pane should be visible on the right.

3. When choosing the Image, you may either use your own or pick one that is supplied by IONOS.

For IONOS supplied images, select No image selected > IONOS Images.

Alternatively, for private images select No image selected > Own Images.

4. Once you choose an image, additional fields will appear in the Inspector pane.

5. A Root password is required for Remote Console access. You may change it later.

6. SSH keys are optional. You may upload a new key or use an existing file. SSH keys can also be injected as user data utilizing cloud-init.

7. You may add a specific key to the Ad-hoc SSH Key field.

8. Under Cloud-init user data, select No configuration and a window will appear.

9. Input your cloud-init data. Either use a bash script or a cloud-config file with YAML syntax. Sample scripts are provided below.

10. To complete setup, return to the Inspector and click Provision Changes. Cloud-init automatically runs at boot, applying the changes requested.

Using shell scripts

Using shell scripts is an easy way to bootstrap a server. In the example script below, the code creates and configures our CentOS web server.

Allow enough time for the instance to launch and run the commands in your script, and then check to see that your script has completed the tasks that you intended.

Using cloud-config directives

Cloud-init images can also be bootstrapped using cloud-config directives. The cloud-init website outlines all supported modules and gives examples of basic directives.

Modules

Examples

Example 1: Creating a swap partition

The following script is an example of how to create a swap partition with second block storage, using a YAML script:

Example 2: Resizing the file system

The following script is an example of how to resize your file system according to the chosen size of the block storage. It will also create a user with an SSH key, using a cloud-config YAML script:

Output log files

The cloud-init output log file (/var/log/cloud-init-output.log) captures console output. Depending on the default configuration for logging, a second log file exists under /var/log/cloud-init.log. **** This provides a comprehensive record based on user data.

Configuring user data via API

Cloud API provides enhanced convenience if you want to automate the provisioning and configuration of cloud instances. Cloud-init is configured on the volume resource in Cloud API V6 (or later). Please find the link to the documentation below:

Name: userData

Type: string

Description: The cloud-init configuration for the volume as base64 encoded string. The property is immutable and is only allowed to be set on a new volume creation. It is mandatory to provide either public image or imageAliasthat has cloud-init compatibility in conjunction with this property.

Curl example

The is used to connect to a when, for example, no is available. You must have the root or administrator password for this type of log-in to the server.

Procedure

1. Start the Remote Console from the server.

2. Open the data center containing the required server.

3. In the Workspace, select the server.

4. In the Inspector, choose Remote Console or select Remote Console from the context menu of the server.

5. Start the Remote Console from the Start Center (contract owners and administrators only).

6. Open the Start Center: Menu Bar > Data Center Designer > Open Start Center

7. Open the Details of the required data center. A list of servers in this data center is displayed.

8. Select the server and click Open Remote Console.

Remote Console version matching your browser opens; you can now log on to the server with root or administrator password.

Create a Cube

1. Drag the Cube element from the Palette into the Workspace.

2. Click the Cube element to highlight it. The Inspector will appear on the right.

3. In the Inspector, configure your Cube from the Settings tab.

• Template: choose the appropriate configuration template.

• vCPUs: set automatically when a Template is chosen.

• RAM in GB: set automatically when a Template is chosen.

• Storage in GB: set automatically when a Template is chosen.

• Name: Your choice is recommended to be unique to this Virtual Data Center (VDC).

• Size in GB: Specify the required storage capacity.

• Image: You can select one of IONOS' images or use your own.

• Password: The combination should be between 8 and 50 characters in length; using only Latin characters and numbers.

• Backup Unit: Backs up all data with version history to local storage or your private cloud storage.

Add more Storage

1. Drop a Storage element from the Palette onto a Cube in the Workspace to connect both.

2. In the Inspector, configure your Storage device in the Settings tab.

• Name: Your choice is recommended to be unique to this Virtual Data Center (VDC).

• Availability Zone: Choose the Zone where you wish to host the Storage device.

• Performance: Depends on the size of the SSD.

• Image: You can select one of IONOS' images or use your own.

• Password: The combination should be between 8 and 50 characters in length; using only Latin characters and numbers.

• Backup Unit: Backs up all data with version history to local storage or your private cloud storage.

Connect to the internet

1. Each compute instance has a NIC, which is activated via the Autoport symbol. Connect the Cube to the Internet by dragging a line from the Cube's Autoport to the Internet's NIC.

2. In the Inspector, configure your LAN device in the Network tab.

• Name: Your choice is recommended to be unique to this Virtual Data Center (VDC).

• MAC: The MAC address will be assigned automatically upon provisioning.

• Failover: If you have an HA setup including a failover configuration on your VMs, you can create and manage IP failover groups that support your HA setup.

• Firewall: Configure a firewall.

• DHCP: It is often necessary to run a DHCP server in your virtual data center (e.g. PXE boot for fast rollout of VMs). If you use your own DHCP server, clear this checkbox so that your IPs are not reassigned by the IONOS DHCP server.

• Additional IPs: In order to use "floating" or virtual IPs, you can assign additional IPs to a NIC by selecting them from the drop-down menu.

Suspend a Cube

1. Choose a Cube. From the Settings tab in the Inspector, select Power > Suspend.

2. (Optional) In the dialog that appears, connect using Remote Console and shut down the VM at the operating system level to prevent data loss.

3. Confirm your action by checking the appropriate box and clicking Apply SUSPEND.

4. Provision your changes. Confirm the action by entering your password.

Resume a Cube

1. Choose a Cube. From the Settings tab in the Inspector, select Power > Resume.

2. Confirm your action by checking the appropriate box and clicking Apply RESUME.

3. Provision your changes. Confirm the action by entering your password.

Provision Changes

1. Start the provisioning process by clicking PROVISION CHANGES in the Inspector.

2. The Provision Data Center dialog opens. Review your changes in the Validation tab.

3. Confirm changes with your password. Resolve outstanding errors without a password.

4. Once ready, click Provision Now to start provisioning resources.

What are Cloud Cubes?

For a long time, the duopoly of virtual private servers (VPS) and dedicated cloud servers dominated virtualized computing environments.

Enter Cloud Cubes — virtual private service instances — the next generation of IaaS. Developed by IONOS Cloud, Cubes are ideal for specific workloads that do not require high compute performance from all resources at all times — development and testing environments, website hosting, simple web applications, and so on.

While based on shared resources, the Cubes can rival physical servers through a platform design that can redistribute available performance capacities among individual instances. At the same time, reduced operational complexity and highly optimized resource utilization translate into lower operating costs.

Cubes instances come complete with vCPUs, RAM, and direct-attached NVMe storage volumes; choose among standard by selecting one of several for your Cubes. Storage capacities can be expanded further by to your Cubes.

Cubes instances can be used together with all enterprise-grade features, resources, and services, offered by IONOS Cloud.

Affordable, quickly available, and with everything you need — have your Cubes up and running in minutes in the IONOS Cloud.

When creating based on IONOS Linux images, you can inject into your . This lets you access your VM safely and allows for secure communication. SSH keys that you intend to use more often can be saved in the SSH Key Manager.

Types of SSH keys

Default SSH keys: SSH keys that you intend to use often and mark them as such in the SSH Key Manager. Default SSH keys are preselected when you configure storage devices. You can specify which SSH keys are actually to be used before and deselecting the preselected standard keys in favor of another SSH key.

Ad-hoc SSH keys: SSH keys that you only use once and don't intend to save in the SSH Key Manager for later re-use.

Generating an SSH key

SSH keys can be generated and used on macOS or Linux if both OpenSSH and the ssh-keygen command-line tools are installed. OpenSSH is a collection of tools for establishing SSH connections to remote servers, while ssh-keygen is a utility for generating SSH keys.

Manually generate SSH keys when working with OpenSSH via the Terminal application by following the steps below.

1. Enter the following command below into the Terminal window and press ENTER.

The key generation process is initiated by the command above. When you run this command, the ssh-keygen utility prompts you for a location to save the key.

2. Accept the default location by pressing the ENTER key, or enter the path to the file where you want to save the key /home/username/.ssh/id_rsa.

3. Enter the passphrase that will be used to encrypt the private key file on the disk. You can also press ENTER to accept the default (no passphrase). However, we recommend that you use a passphrase.

4. Enter your passphrase once more.

After you confirm the passphrase, the public and private keys are generated and saved in the specified location. Thus, the confirmation will look like this:

You can copy the public key to your clipboard by running the following command:

Storing SSH keys

In the SSH Key Manager of the DCD, you can save and manage up to 100 public SSH keys for the setup of SSH accesses. This saves you from having to repeatedly copy and paste the public part of an SSH key from an external source.

1. To open the SSH Key Manager, go to Menu > MANAGER resources > SSH Key Manager.

2. In the SSH Key Manager, select + Add Key.

3. Enter a Name and click Add.

4. Copy and paste the public key to the SSH key field. Alternatively, you may upload it via Select key file. Please ensure the SSH keys you enter are valid. The DCD does not validate syntax or format.

5. (Optional) Activate the Default checkbox to have the SSH key automatically pre-selected when SSH access is configured.

6. Click Save to store the key.

The SSH key is stored in the SSH Key Manager and can be used for the configuration of SSH accesses.

Deleting an SSH key in the SSH Key Manager

To delete an existing SSH key, select the SSH key from the list and click Delete Key.

The SSH key is removed from the SSH Key Manager.

Connecting via OpenSSH

You can connect to your virtual instance via OpenSSH. Still, you will need the terminal application, which varies depending on your operating system. For:

• Linux: Search Terminal or press CTRL+ALT+T

• macOS: Search Terminal

• Windows: Search Bash. If you don’t have Bash installed, use PuTTY instead.

The steps below will show you how to connect to your VM.

1. Open the Terminal application and enter the SSH connection command below. After the @, add the IP address of your VM instance. Then press ENTER.

2. Authentication is the next step in the connection process. If you've added the SSH keys, you'll be able to connect to the VM immediately or after entering your key pair's passphrase.

If you haven't already added SSH keys, you'll be asked for your password:

3. Once you’ve entered the password, press ENTER.

If the SSH key is configured correctly, this will log you into VM.

Dedicated Core Servers

What are the maximum resources available for a Server?

Cores

Dedicated Core Server configurations are subject to the following limits, according to the CPU type:

• AMD CPU: Up to 62 cores and 230 GB RAM

• Intel® CPU: Up to 51 Intel® cores and 230 GB RAM

HDD storage

• Minimum: 1 GB

• Maximum: 4 TB

SSD storage

• Minimum: 1 GB

• Maximum: 4 TB

What are the Availability Zones?

IONOS data centers are divided into separate areas called Availability Zones.

You can enhance reliability and set up high-availability scenarios by deploying redundant Dedicated Core Servers and storage devices across multiple Availability Zones.

How do I change the Availability Zone?

• Select the server in the DCD Workspace

• Use Inspector > Properties > Availability Zone menu to change the Availability Zone

What is Live Vertical Scaling?

Live Vertical Scaling (LVS) technology permits you to scale the number of CPU cores and amount of RAM while the server is running, without having to restart it. Please note that Windows only allows scaling the number of CPU cores, but not the amount of RAM. For scaling to more than eight CPU cores, Windows requires a reboot.

Why do I sometimes see steal time in my Dedicated Core servers?

How do I reboot a Dedicated Core server?

Dedicated Core servers can be restarted at the operating system level (using the reboot command, for instance). You can also use the DCD reset function, which functions similarly to a physical server's reset button.

How do I shut down a Dedicated Core server?

You should use the DCD to shut down your server completely. Your VM will then be marked as "shut down" in the DCD. Shutting down a VM at the operating system level alone does not deallocate its resources or suspend the billing.

How do I delete a Dedicated Core server?

You can delete a Dedicated Core server from the DCD Workspace by right-clicking on it and selecting Delete Server from the list, or by selecting the server and pressing the Del key on your keyboard.

What do I do when my VM isn't accessible?

Try to connect to your VM using the Remote Console to see if it is up and running. If you have trouble logging on to your VM, please provide our support team with screenshots of error messages and prompts from the Remote Console.

• Windows users: Please send us a screenshot of the Task Manager.

• Linux users: Please send us the output of uptime and top.

How do I get the root/admin passwords with IONOS images?

When using IONOS-provided images, you set the passwords yourself prior to provisioning.

Why does my newly provisioned server not start?

Newly provisioned servers with more than 8 GB of RAM may not start successfully when created from IONOS Windows images, because the RAM size cannot be processed during the initial configuration.

An error is displayed according to the server version; for example, Windows Server 2012 R2 displays the following message:

"Windows could not finish configuring the system. To attempt to resume configuration, restart the computer."

We recommend initially setting the RAM size to 8 GB, and rescaling it as needed after the initial provisioning and configuration is complete.

Which CPU architecture should I choose?

The choice of CPU architecture primarily depends on your workload and performance requirements. Intel® processors are oftentimes more powerful than AMD processors. Intel® processors are designed for compute-intensive applications and workloads where the benefits of hyperthreading and multitasking can be fully exploited. Intel® cores cost twice as much as AMD cores. Therefore, it is recommended that you measure and compare the actual performance of both CPU architectures against your own workload. You can change the CPU type in the DCD or use the API, and see for yourself whether Intel® processors deliver significant performance gains, or more economical AMD cores still meet your requirements.

With our unique "Core Technology Choice" feature, we are the only cloud computing provider that makes it possible to flexibly change the processor architecture per virtual instance.

What do I do if the cursor in the Remote Console disappears?

When the cursor disappears after logging on to the Remote Console, you can reconnect to the server using the appropriate menu entry.

vCPU Servers

What are the maximum resources available for a vCPU Server?

Cores

vCPU Server configurations are subject to the following limits:

• Up to 120 cores and 512 GB RAM

A CPU Family of a vCPU server cannot be chosen at the time of creation and cannot be changed later.

HDD storage

• Minimum: 1 GB

• Maximum: 4 TB

SSD storage

• Minimum: 1 GB

• Maximum: 4 TB

What are the Availability Zones?

IONOS data centers are divided into separate areas called Availability Zones.

You can enhance reliability and set up high-availability scenarios by deploying redundant vCPU Servers and storage devices across multiple Availability Zones.

How do I change the Availability Zone?

• Select the vCPU Server in the DCD Workspace.

• Navigate to the Inspector pane > Properties > Availability Zone menu to change the Availability Zone.

What is Live Vertical Scaling?

Live Vertical Scaling (LVS) technology permits you to scale the number of CPU cores and amount of RAM while the server is running, without having to restart it. Please note that Windows only allows scaling the number of CPU cores, but not the amount of RAM. For scaling to more than eight CPU cores, Windows requires a reboot.

How do I reboot a server?

Servers can be restarted at the operating system level (using the reboot command, for instance). You can also use the DCD reset function, which functions similarly to a physical server's reset button.

How do I shut down a server?

You should use the DCD to shut down your server completely. Your VM will then be marked as "shut down" in the DCD. Shutting down a VM at the operating system level alone does not deallocate its resources or suspend the billing.

How do I delete a server?

You can delete a server from the DCD Workspace by right-clicking on it and selecting Delete Server from the list, or by selecting the server and pressing the Del key on your keyboard.

What do I do when my VM isn't accessible?

Try to connect to your VM using the Remote Console to see if it is up and running. If you have trouble logging on to your VM, please provide our support team with screenshots of error messages and prompts from the Remote Console.

• Windows users: Please send us a screenshot of the Task Manager.

• Linux users: Please send us the output of uptime and top.

How do I get the root/admin passwords with IONOS images?

When using IONOS-provided images, you set the passwords yourself prior to provisioning.

Why does my newly provisioned server not start?

Newly provisioned servers with more than 8 GB of RAM may not start successfully when created from IONOS Windows images, because the RAM size cannot be processed during the initial configuration.

An error is displayed according to the server version; for example, Windows Server 2012 R2 displays the following message:

"Windows could not finish configuring the system. To attempt to resume configuration, restart the computer."

We recommend initially setting the RAM size to 8 GB, and rescaling it as needed after the initial provisioning and configuration is complete.

Which CPU architecture should I choose?

A CPU Family of a vCPU server cannot be chosen at the time of creation and cannot be changed later.

What do I do if the cursor in the Remote Console disappears?

When the cursor disappears after logging on to the Remote Console, you can reconnect to the server using the appropriate menu entry.

PVPanic Device

What is the PVPanic device for?

The device monitors VM/OS crashes. PVPanic is a simulated device, through which a guest panic event is sent to the hypervisor, and a QMP event is generated.

Do I need to restart the VM to get PVPanic?

No, the PVPanic device is plug-and-play. However, installing drivers may require a restart.

What happens if Windows VMs complain about an unknown device?

This is no cause for concern. First of all, you do not need to reboot the VM. However, you will need to reinstall appropriate drivers (which are provided by IONOS Cloud).

Are there any risks when enabling the use of PVPanic?

There are no issues found when enabling pvpanic. However, users cannot choose whether or not to enable the device; it is always available for use.

Something else to consider - PVPanic does not offer bidirectional communication between the VM and the hypervisor. Instead, the communication only goes from the VM towards the hypervisor.

Are there any compatibility issues with AMD or Intel processors?

There are no special requirements or limitations to any components of a virtualized server. Therefore, PVPanic is completely compatible with AMD and Intel processors.

Do we support hardware solutions?

The PVPanic device is implemented as an ISA device (using IOPORT).

Does my Linux image support the Pvpanic device?

Check the kernel config CONFIG_PVPANIC parameter.

For example:

m = PVPanic device is available as module y = PVPanic device is native available in the kernel n = PVPanic device is not available

When the device is not available (CONFIG_PVPANIC=n), use another kernel or image.

How do I install the device driver for the pvpanic device on Windows?

For your virtual machines running Microsoft Windows, we provide an ISO image that includes all the relevant drivers for your instance. Just log into DCD, open your chosen virtual data center, add a CD-ROM drive and insert the driver ISO as shown below (this can also be done via CloudAPI).

Once provisioning is complete, you can log into your OS by adding drivers for the unknown device through the Device Manager. Just enter devmgmt.msc in the Windows search bar, console, or PowerShell to open it.

Since this is a Plug & Play driver, there is no need to reboot the machine.

The Cloud API lets you manage Cloud Cubes resources programmatically using conventional HTTP requests. All the functionality available in the IONOS Cloud Data Center Designer is also available through the API.

You can use the API to create, destroy, and retrieve information about your Cubes. You can also use the API to suspend or resume your Cubes.

However, not all actions are shared between Dedicated Core Servers and Cloud Cubes. Since Cubes come with direct-attached storage, a composite call is required for setup.

Furthermore, when provisioning Cubes, Templates must be used. Templates will not be compatible with Servers that still support full flex configuration.

APIs & SDKs

Retrieving available Templates and Template details

Retrieve Template list

GET https://api.ionos.com/docs/cloud/v6/#tag/Templates/cloudapi/v6/templates

This method retrieves a list of configuration templates that are currently available. Instances have a fixed configuration of vCPU, RAM and direct-attached storage size.

Path Parameters

Retrieve Template details

GET https://api.ionos.com/docs/cloud/v6/#tag/Templates/cloudapi/v6/templates?depth=1

Retrieves Template information. Refine your request by adding the optional query parameter

depth

. The response will show a template's ID, number of cores, ram and storage size.

Path Parameters

Query Parameters

Creating instances with composite calls

The payload of a composite call to configure a Cubes instance is different from that of a POST request to create an enterprise server. In a single request you can create a new instance, as well as its direct-attached storage device and image (public image, private image, or snapshot). When the request is processed, a Cubes instance is created and the direct-attached storage is mounted automatically.

Create an instance

POST https://api.ionos.com/cloudapi/v6/datacenter/{datacenterId}/servers

This method creates an instance in a specific data center.

\

Replace {datacenterID} with the unique ID of your data center. Your Cloud Cube will be provisioned in this location.

Path Parameters

Suspend an instance

POST https://api.ionos.com/cloudapi/v6/datacenters/{datacenterId}/servers/{serverId}/suspend

This method suspends an instance.

Path Parameters

Setup, Resume and Delete

Resume instance

POST https://api.ionos.com/cloudapi/v6/datacenters/{datacenterId}/servers/{serverId}/resume

This method resumes a suspended instance.

Path Parameters

Delete instance

DELETE https://api.ionos.com/cloudapi/v6/datacenters/{datacenterId}/servers/{serverId}

This method deletes an instance.

Path Parameters

A is a with an attached NVMe Volume. Each Cube you create is a new virtual machine you can use, either standalone or in combination with other IONOS Cloud products. For more information, see .

You can create and configure your Cubes visually using the interface. For more information, see . However, the creation and management of Cubes are easily automated via the , as well as our custom-made tools and .

Configuration templates

You may choose between eight template sizes. Each template varies by processor, memory, and storage capacity. The breakdown of resources is as follows:

Resource usage

Counters: The use of Cubes' vCPU, RAM, and NVMe storage resources counts into existing resource usage. However, dedicated resource usage counters are enabled for Cloud Cubes. These counters permit granular monitoring of vCPUs and NVMe storage, which differ from Dedicated Core Servers for the enterprise VM instances and block storage.

Billing: Please note that suspended Cubes continue to incur costs. If you do not delete unused instances, you will continue to be charged for usage. Save on costs by creating snapshots of that you do not immediately need and delete unused instances. At a later time, use these snapshots to recreate identical Cubes as needed. Please note that recreated instances may be assigned a different .

Storage options

Included direct-attached storage: A default Cube comes ready with a high-speed direct-attached NVMe storage volume. Please check Configuration Templates for NVMe Storage sizes.

Boot options: Any storage device, including the CD-ROM, can be selected as the boot volume. You may also boot from the network.

Images and snapshots: Images and snapshots can be created from and copied to direct-attached storage, block storage devices, and CD-ROM drives. Also, direct-attached storage volume snapshots and block storage volumes can be used interchangeably

Disaster recovery

A recovery point is generated daily for each Cube NVMe storage volume. This recovery point can be used to recreate the instance again with the same contents, except for those stored in added volumes.

IONOS Cloud network block storage devices are already protected by a double-redundant setup, which is not included in the recovery points. Instead, recovered block storage devices will automatically be mounted to new Cubes instances.

Limitations

Cloud Cubes are limited to a maximum of 24 devices. The NVMe volume already occupies one of these slots.

You may not change the properties of a configuration template (vCPU, RAM, and direct-attached storage size) after the Cube is provisioned.

The direct-attached NVMe storage volume is set upon provisioning and cannot be unmounted or deleted from the instance.