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 on DCD features, you can visit the page.

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:

• : Create, configure and delete entire data centers. Cross-connect between VDCs and tailor user access across your organization.

• : Setup, pause, and restart virtual instances with customizable storage, CPU, and RAM capacity. Instances can be scaled based on usage.

• : Upload, edit and delete your own private images or use images provided by IONOS Cloud. Create or save snapshots for use with future instances.

• Networking: Reserve and manage static public . Create and manage private and public LANs including firewall setups.

• Basic Features: Save and manage ; connect via , launch instances via , record networking via flow logs and monitor your instance use with monitoring software.

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

If you are ready to get started with the Data Center Designer, consult our beginner . These step-by-step instruction sets will teach you how to and configure initial user settings.

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.

Virtual servers that you create in the are provisioned and hosted in one of IONOS physical data centers. Virtual servers behave exactly like physical servers. They can be configured and managed with your choice of the operating system. Information on creating a server can be found here.

Boot options: For each server, you can select to boot from a virtual CD-ROM/DVD drive or from a storage device (/). Any operating system can be used 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 virtual servers and storage devices across multiple .

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. With upscaling resources, you can change the resources of a virtual server during operation without restarting it. This means you can add RAM or ("hot plug"). This 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 they may have to be activated manually depending on the derivative. For more information see the Linux VirtIO page.

For IONOS images, the supported properties are already preset. Without restarting the 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've used the scaling up approach. Without restarting the server, only upscaling can be done.

Limitations

CPU Types: Virtual server configurations are subject to the following limitations, by CPU type:

AMD CPU

Intel® CPU

A single Intel® physical core with Hyper-Threading Technology is exposed to the operating system of your virtual 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.

Recommended for beginners:

Selected user guides:

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

Creating 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.

• Name: Your choice is recommended to be unique to this .

• 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.

4. You will also notice that the Cube comes with an Unnamed Direct Attached Storage. Click on the device and rename it in the Inspector.

• 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.

Adding 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.

• Size in GB: Specify the required storage capacity for the

• 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.

Connecting to the internet

1. Each virtual machine 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.

• Primary IP: The primary is automatically assigned by the IONOS DHCP . You can, however, enter an IP address for manual assignment by selecting one of the reserved IPs from the drop-down menu. Private IP addresses should be entered manually. The has to be connected to the Internet.

• 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.

Provisioning 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.

The data center will now be provisioned with the new Cube. DCD will display a Provisioning Complete notification once your cloud infrastructure is ready.

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.

Usually, clicking on a data center in the My Data Centers list opens the data center. However, if this is your first time using DCD, you will need to create your first Virtual Data Center (). Learn how to set VDC defaults in the .

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.

A Virtual Data Center (VDC) is a collection of cloud resources for creating an enterprise-grade IT infrastructure. A Local Area Network (LAN) in a VDC refers to the interconnected network of Virtual Machines (VMs) within a single physical server or cluster of servers. The LAN in a VDC is a critical component of cloud computing infrastructure that enables efficient and secure communication between VMs and other resources within the data center.

VDC operates in a dual-stack mode that is, the Network Interface Cards (NICs) can communicate over IPv4, IPv6, or both. In Data Center Designer (DCD), IPv6 can be enabled for both Private and Public LANs, but on provisioning, only Public IPv6 addresses are allocated to all LANs.

IONOS IPv6 is operated by a team of experts and qualified network administrators. Contact IONOS support team for all your queries.

It may be desirable to enhance the configuration of CoreDNS by incorporating additional settings. To ensure the persistence of these changes during control plane maintenance, it is necessary to create a ConfigMap within the kube-system namespace. The ConfigMap should be named coredns-additional-conf and should include a data entry with the key extra.conf. The value associated with this entry must be a string that encompasses the supplementary configuration.

Below is an illustrative example that demonstrates the process of adding a custom DNS entry for example.abc:

apiVersion: v1
kind: ConfigMap
metadata:
  name: coredns-additional-conf
  namespace: kube-system
data:
    extra.conf: |
      example.abc:53 {
        hosts {
          1.2.3.4 example.abc
          2.3.4.5 server.example.abc
          fallthrough
        }
      }

Latest Release: DBaaS MongoDB User Guide

Getting Started

With Data Center Designer (DCD), IONOS Cloud's visual user interface, you can create a fully functioning Virtual Data Center (VDC). Learn more about DCD with our code-free guide:

APIs, SDKs & Tools

Product User Guides

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

With IONOS Cloud , you can quickly provision and . Leverage our user guides, reference documentation, and FAQs to support your hosting needs.

Product Overview

Developer Tools

Recommended How-To's

Frequently Asked Questions

Change Log

10 October 2021 | Live Vertical Scaling Overview section updated

Access inside of the Virtual Data Center can be controlled for both Users, user Groups, and Resources. Please consult the following instructions for all three.

User Access Control

When you create a new Virtual Data Center (), only you, as the Contract Owner, have access to the space and the infrastructure contained within. However, you might want to assign maintenance duties to another member of your organization. This tutorial teaches you how to create new users and how to assign privileges to them. This will allow them to work with the resources that you created inside of the VDC.

Creating a new User

The User Manager lets you create new users, add them to user groups, and assign privileges to each Group. Privileges either limit or expand access, based on the user role in your organization. This panel lets you control user access to specific areas of your VDC.

To access the User Manager, go to Menu > Management > Users & Groups.

1. In the User Manager, click + Create in the Users tab.

2. Enter the user's First Name, Last Name, Email, and Password. Click Create.

Creating a Group

The creation of Groups is useful when you need to assign specific duties to a specific group of a team member. For example, you may want to assign certain duties to a team of Quality Assurance experts. You have to create a Group called "Quality Assurance" and add it to the User Manager. Later, you can add members to this group. You can then assign privileges to the entire Group.

To create a group, use the following procedure:

1. In the Groups tab, click + Create and enter a Group Name in the drop-down.

2. Click Create to confirm. The group is now created and visible in the list.

You can now assign permissions, users, and resources to your Quality Assurance department.

Adding Users to a Group

Users are added to your Quality Assurance group on an individual basis. Once you have created a new member, you must assign them to the Group.

1. In the Groups tab, select the required group.

2. In the Members tab, add Users from the + Add User drop-down.

3. To remove users, select the required user and click Remove User.

Users assigned to the group now have privileges and access rights to resources corresponding to their group membership.

By assigning a user to a group, a contract owner or administrator not only defines which actions a user is authorized to perform in the DCD but also which resources (VDCs, , , IP blocks) members of this group can access.

Administrators do not need to be managed in groups as they automatically have access to all resources associated with the contract.

Assigning privileges to Groups

1. In the Groups tab, select the required group.

2. In the Privileges tab, check or uncheck boxes, as appropriate, next to the privilege name.

You do not need to save your selections. This action automatically grants/removes privileges.

Adding Groups to a Resource

1. Select a resource from the Resources tab in the User Manager panel.

2. Under the Visible to Groups tab, click + Add Group.

3. Click on a Group which was previously created.

4. The selected group is now able to see the resource.

Assigning Resources from the Groups tab

1. In the Groups tab, select the required group.

2. Open the Resources of Group tab.

3. Click on + Grant Access and select the resource from the dropdown.

This enables read access to the selected resource.

Check each box to enable editing or sharing of a resource. To disable access, select the required resource and uncheck either the permission box or click Revoke Access.

You can enable IPv6 on Virtual Servers and Cloud Cubes 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 virtual servers and cubes, you can ensure that they are accessible to IPv6-enabled networks and clients.

This tutorial contains a detailed description of how to manually configure your IONOS Cloud infrastructure for each server via the Virtual Data Center (VDC). 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 Server

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

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

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

• Availability Zone: Select a zone from the drop-down list to host the server on the chosen zone.

• CPU Architecture: Choose between AMD or Intel cores.

• Cores: Choose the number of CPU cores.

• RAM: Choose any size starting from 0.25 GB to the maximum limit allotted to you. The size can be increased or reduced in steps of 0.25 GB. The maximum limit varies based on your contract resource limits and the chosen data center. For more information about creating a full-fledged server, see Configure a Virtual Server.

Add storage to the server

1. Drag a Storage element from the Palette onto a 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: 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. For more information about adding storage to the server, see Configure a Virtual Server.

Connect to the internet

1. Drag a Network Interface Card (NIC) element from the Palette into the Workspace to connect the elements.

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.

• Firewall: It is Disabled by default. Select a value from the drop-down list to configure your firewall settings. For more information, see Configure a Firewall.

For more information about network configuration, see Configure a Network

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

After configuring data centers, you can specify a preferred default data center location, IP settings, and resource capacity for future VDCs. For more information about configuring VDC defaults, see My Settings.

Your IONOS Cloud infrastructure is set up in Virtual Data Centers (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

Square Element icons serve as building blocks for your VDC. Each Element represents an IONOS Cloud product or service. Keep in mind that some Elements are compatible, while others aren't. For example, a Server icon can be combined with the Storage (HDD or SSD) icon. In practice, this would represent the physical act of connecting a hard drive to a server machine. For more information, see Setup Storage.

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

When an Element is selected, the Inspector pane will appear on the right. You can configure Element properties, such as Name and Availability Zone.

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.

4. The Details button, to the right of each VDC, displays all associated VMs, resources, and status. The different status indications are on, off, or de-allocated.

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

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.

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 [email protected]
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 [email protected]

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:

[email protected]'s password:

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

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

To update IPv6 configurations for LANs in the Data Center Designer (DCD), follow these steps:

1. Select the LAN you want to update IPv6 for.

2. You can update your IPv6 CIDR block with prefix length /64 from the VDCs allocated range.

3. Start the provisioning by clicking PROVISION CHANGES in the Inspector pane.

The Virtual Data Center (VDC) will now be provisioned with the new network settings. In this case, the existing configuration gets reprovisioned accordingly.

• One limitation of IPv6 is that a /56 block is typically assigned to a data center, with a /64 block assigned inside this /56 block to the Local Area Network (LAN). The difference between a /56 and a /64 block is 8, resulting in 2^8 (2 to the power of 8) blocks, or a total of 256 blocks. This limitation can impact the scalability and flexibility of IPv6 addressing in large networks. Therefore, it is important to carefully consider the allocation of IPv6 blocks to ensure efficient utilization of available resources.

• You will get a new /56 prefix every time you create a new data center. If your services depend on static IPv6 addresses, and you want to rebuild your data center, you must not delete the data center itself, but only its components, such as, LANs, NICs, etc. For more information about how to create new Data Center LANs in DCD, see .

• Currently, only Ubuntu and Windows images are supported. If you want to use images other than these, you need to tweak the OS initialization process of your image. For example, the Dynamic Host Configuration Protocol version 6 (DHCPv6) client may need to be run manually after restarting the system for Debian. We are currently working on supporting IPv6 on all IONOS images selectable in the DCD. Generally, if the interfaces have not received an IPv6 address from the IONOS DHCP server, try to run the DHCPv6 client manually. For more information, see .

• AlmaLinux operates seamlessly when the hostname aligns with the requirements of the Network Manager DHCPv6 client. To ensure smooth functionality, it is crucial to have a valid hostname. For more information, see the .

• In previous versions of Rocky Linux, it is important to note that the IPv6 protocol may not be readily available after the initial boot. For the latest version Rocky Linux 9.0, you can use IPv6 support right from the first boot.

• Currently, IPv6 is not available for Managed Services such as Application Load Balancer (ALB), Network Load Balancer (NLB), Network Address Translation (NAT) Gateway, IP Failover and Managed Kubernetes (MK8s).

To disable IPv6 for LANs in the Data Center Designer (DCD), follow these steps:

1. Select the LAN you want to disable IPv6 for, and clear the Activate IPV6 for this LAN checkbox.

2. Start the provisioning by clicking PROVISION CHANGES in the Inspector pane.

The Virtual Data Center (VDC) is provisioned with the new network settings. On disabling IPv6 on a LAN, existing IPv6 configuration on the Network Interface Card (NICs) will be removed or deleted.

1. How do I configure IPv6 on my network?

   IPv6 can be configured via the Data Center Designer (DCD) or Cloud API using IPv6-enabled LAN. You can get IPv6 support by configuring the network. For more information about how to enable IPv6 on Virtual Data Center LANs in DCD, see .

2. Why do we need IPv6 configuration in DCD?

   The main reason for the transition to IPv6 is the exhaustion of available IPv4 addresses due to the exponential growth of the internet and the increasing number of devices connected to it.

3. If I use private images, do I need to adapt them in any way so that they support IONOS IPv6?

   IONOS IPv6 implementation currently supports Ubuntu and Windows images. If you want to use images other than Ubuntu, you may need to tweak the OS initialization process of your image. For example, the Dynamic Host Configuration Protocol version 6 (DHCPv6) client may need to be run manually after the system boot. We are currently working on supporting IPv6 on all IONOS public images selectable in the DCD. Generally, if the interfaces have not received an IPv6 address from the IONOS Dynamic Host Configuration Protocol (DHCP) server, try to run the dhcp6 client manually.

   For other operating systems, the DHCPv6 client may require a manual restart to apply the new configuration received from the DHCPv6 server. This is because the client device may have cached the previous configuration information and needs to clear it before applying the new one. However, not all DHCPv6 implementations require a manual restart, as some may be able to automatically apply the new configuration without any intervention.

You can download the generated Kubeconfig for your cluster to be used with the kubectl command. The file will be generated on the fly when you request it.

You can download the file from the or from the Inspector pane, in case the viewed data center contains active node pools.

Using the Kubernetes Manager

1. Go to MANAGER Resources > Kubernetes Manager

2. Select a cluster from the list

3. Click on kubeconfig.yaml or to kubeconfig.json for downloading

Using the Inspector pane

1. Open a data center containing node pools

2. Select a Server that is managed by Kubernetes

3. On the right, select Open Kubernetes Manager

4. Choose between kubeconfig.yaml or to kubeconfig.json for download

IONOS's Database as a Service (DBaaS) consists of fully managed databases, with high availability, performance, and reliability hosted in IONOS Cloud and integrated with other IONOS Cloud services.

Database Engines

We currently offer the following database engines:

MongoDB

IONOS DBaaS lets you quickly set up and manage database clusters. Using IONOS DBaaS, you can manage MongoDB clusters, along with their scaling, security and creating snapshots for backups.

PostgreSQL

IONOS DBaaS, gives you access to the capabilities of the database engine. Using IONOS DBaaS, you can manage PostgreSQL cluster operations, database scaling, patch your database, create backups, and security.

Quick Links:

Will DBaaS be ever offered on Cloud Cubes?

As for now, DBaaS is only offered on Virtual Servers. Cloud Cubes may be used in the future as well.

Is there a connection pooling option for PosgreSQL?

IONOS DBaaS doesn't provide connection pooling. However, you may use a connection pooler (such as pgbouncer) between your application and the database.

After the connection limit has been reached, will there be an error?

Depending on the library you are using, it should be something like:

failed to create DB connection: addr x.x.x.x:5432: connection refused.

How do we prevent reaching the connection limit?

The best way to manage connections is to have your application maintain a pool of at least 10-20 connections. It is considered bad practice to have a lot of DB connections. However, letting the user configure max_connections themselves in the future is an option.

Can I scale the deployment to increase its connection limit?

Yes, see for more info.

What are the supported backup methods?

We provide an automated backup within our cloud. If you want to backup to somewhere else, you may use a client-side tool, such as .

What are the main considerations for latency and performance?

The number of standby nodes (in addition to primary node) doesn’t really matter. If you have one or ten makes no difference. Synchronous modes are slower in write performance due to the increase in latency for communication between a primary node and a standby node.

Why can't I restore to the time I specified?

If you're receiving an error message Parameter out of bounds: The recovery target time is before the newest basebackup., please check the earliestRecoveryTargetTime of your backup. Your target time of the restore needs to be after this timestamp. Maybe you have another backup for your cluster with an earlier earliestRecoveryTargetTime and can use that.

If the earliestRecoveryTargetTime is missing in your backup, the cluster from where you want to restore wasn't able to do a base backup. This can happen, when you e.g. quickly delete a newly created cluster, since the base backup will be triggered up to a minute after the cluster is available.

RAM

The WiredTiger cache uses only a part of the RAM; the remainder is available for other system services and MongoDB calculations. The size of the RAM used for caching is calculated as 50% of (RAM size - 1 GB) with a minimum of 256 MB. For example, a 1 GB RAM instance uses 256 MB, a 2 GB RAM instance uses 512 MB, a 4 GB instance uses 1.5 GB, and so on.

You get the best performance if your working set fits into the cache, but it is not required. The working set is the size of all indexes plus the size of all frequently accessed documents.

To view the size of all databases' indexes and documents, you can use a similar script as described in the . You must estimate what percentage of all documents are accessed at the same time based on your knowledge of the workload.

Additionally, each connection can use up to 1 MB of RAM that is not used by WiredTiger.

Disk

The disk contains:

• Logs written by . They can take up to 2% of the disk space before MongoD deletes them.

• OpLogs for the last 24 hours. The size of these depends on your workload. There is no upper limit, so they can grow quite large. But they are removed after 24 hours on their own.

• The data itself.

Operating system and applications are kept separately, outside of the configured storage, and are managed by IONOS.

Limitations

Connection Limits: As each connection requires a separate thread, the number of connections is limited to 51200 connections.

CPU: The total upper limit for CPU cores depends on your quota. A single instance can't exceed 16 cores.

RAM: The total upper limit for RAM depends on your quota. A single instance can't exceed 64 GB.

Storage: The upper limit for storage size is 1280 GB.

Backups: Storing cluster backups is limited to the last 7 days. Deleting a cluster also immediately removes all backups of it.

Backups

MongoDB Backups: A cluster can have multiple snapshots. They are created:

1. when a cluster is created, known as initial sync which usually happens in less than 24hs.

2. after a restore.

A snapshot is a copy of the data in the cluster at a certain time. Every 24 hours, a base snapshot is taken, and every Sunday, a full snapshot is taken. We keep snapshots for the last 7 days, so recovery is possible from up to a week ago.

You can restore from any snapshot as long as it was created with the same or older MongoDB patch version.

Snapshots are stored in an IONOS S3 Object Storage buckets in the same region as your database. Databases in regions where IONOS S3 Object Storage is not available will be backed up to eu-central-2.

Recovery

Recovery is achieved via restore jobs. A restore job is responsible to create and catalog a cluster restoration process. A valid snapshot reference is required for a restore job to recover the database from. The API exposes available snapshots of a cluster.

There must be no other active restore job for the cluster in order to create a new one.

To view cluster metrics in DCD, select the cluster of interest from the available Databases. The chosen database will open up. In Properties, select the database name next to the Monitor Databases option. The cluster metrics will open up:

It is possible to choose a time frame for metrics and instances of interest.

Overview

Machines use IP addresses to communicate over a network, and IONOS has introduced Internet Protocol version 6 (IPv6) to its compute instances, offering a significantly larger pool of unique addresses. This upgrade enables support for the ever-growing number of connected devices.

At IONOS, we recognize the significance of IPv6 configuration in virtual environments and offer a flexible and scalable infrastructure that accommodates IPv6 configuration, allowing our customers to take advantage of the latest features.

One of the primary requirements is to ensure that VMs in the VDC can access services on the internet over IPv6. IONOS allows you to do the necessary provisions to provide seamless service access.

In addition to being a client to an IPv6 service, a Virtual Machine (VM) in the IONOS Virtual Data Center (VDC) can provide a service, such as a simple REST API, over IPv6. In this case, it is essential to ensure that the IPv6 address assigned to the VM is static. If DHCPv6 is enabled, the NICs can receive their static IPv6 address(es) using DHCPv6. You do not need to log in to every server and hardcode the IPv6 address. A Network Interface Card (NIC) has a Media Access Control address (MAC) and it sends a DHCPv6-Discover request to every user asking for a configuration for its MAC address. DHCPv6 shares configuration information with NIC, containing the IPv6 address. Our DHCPv6 has the information on which MAC address gets which IPv6 address(es). This is a critical requirement to allow you to access the service continuously, without any interruptions.

Concepts

IONOS supports the internet standard IPv6. Following are a few concepts associated with it:

• IPv6 or Internet Protocol version 6, is the most recent version of the Internet Protocol (IP) that provides a new generation of addressing and routing capabilities. The IPv6 is designed to replace the older IPv4 protocol, which is limited in its available address space.

• IPv6 uses 128-bit addresses, providing an almost limitless number of unique addresses. This allows for a much larger number of devices to be connected to the Internet.

• IPv6 defines several types of addresses, including unicast, multicast, and anycast addresses. Unicast addresses identify a single interface on a device, multicast addresses identify a group of devices, and anycast addresses identify a group of interfaces that can respond to a packet.

• IPv6 addresses are divided into two parts: a prefix and an interface identifier. The prefix is used for routing and can be assigned by an Internet Service Provider (ISP) or network administrator, while the interface identifier is typically generated by the device.

• As IPv6 adoption continues, transition mechanisms are used to ensure compatibility between IPv6 and IPv4 networks. These mechanisms include dual-stack, tunneling, and translation methods. For more information about IPv6 see our latest blog on IPv6: Everything about the New Internet Standard.

Cluster options

To guarantee partition tolerance, only odd numbers of cluster members are allowed. For the playground edition you can only have 1 replica. All other editions allow the use of 3 replicas. Soon we will allow more than 3 replicas per cluster.

All of these sizes are automatically highly available and replicate your data between instances. One instance is the primary, which accepts write transactions, and the others are secondary, which can optionally be used for read operations.

Replication

All instances in an IONOS MongoDB cluster are members of the same replica set, so all secondary instances replicate the data from the primary instance.

By default the write concern before acknowledging a write operations is set to "majority" with j: true. The term "majority" means the write operation must be propagated to the majority of instances. In a three-instance cluster, for example, at least two instances must have the operation before the primary acknowledges it. The j option also requires that the change has already been persisted to the on-disk journal of these instances.

If data is not replicated to the majority, it may be lost in the event of a primary instance failure and subsequent rollback.

Changing the commit guarantees per transaction

You can change the write concern for single operations, for example due to performance reasons. See the official documentation on write concerns.

Read preferences

You can determine which instance to use for read operations by setting the read preference on the client side, if your client supports it.

If you read from the primary instance, you always get the most up-to-date data. You can spread the load by reading from secondary sources, but you might get stale data. However, you can get consistency guarantees using a read concern.

The user who creates the 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 it in the DCD. For more information, see the Virtual Servers page.

Creating a Server

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

The created 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 virtual 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. Please 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.

Adding a bootable drive

1. Drag a storage element (HDD or SSD) from the Palette onto a 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 on the right.

Configuring 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; the size can be increased after provisioning, even while the server is running, as long as this is supported by its operating system. 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 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 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, select the appropriate check box in the Add Storage dialog box. If you wish to boot from the network, set this on the server: Server 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.

Adding 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 server to other elements, such as an internet access element or other servers through their NICs.

• Provision your changes.

The server is available according to your settings.

Start, Suspend or Reset a 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. 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 server to shut down and reboot, but data loss may result.

Suspending a server

1. Choose a server. From the Settings tab in the Inspector, select Power > Suspend. The server is not deleted. This only suspends it and deallocates resources.

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.

The server is switched off. CPU, RAM, and IP addresses are released and billing is suspended. Connected storage devices will still be billed. Reserved IP addresses are not removed from the server. The deallocated virtual machine is marked by a red cross in DCD.

Starting a server

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

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

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

The server is booted. A new public IP address is assigned depending on the configuration. Billing is resumed.

Resetting a server

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

2. (Optional) In the dialog 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 checking the appropriate box and clicking Apply STOP.

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

Result: The server will shut down and reboot.

Scaling a Server

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

2. Modify storage:

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

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

4. Provision your changes.

The CPU size is adjusted in the DCD. You must set the new size at the operating system level of your VM.

Deleting a Server

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

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

1. Select the 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 that appears, choose whether you also want to delete storage devices that belong to the server.

4. Provision your changes

The server and its storage devices are deleted.

With IONOS Cloud Block Storage, you can quickly provision virtual servers and other Infrastructure-as-a-Service (IaaS) offerings. Consult our user guides, reference documentation, and FAQs to support your hosting needs.

Developer Tools

Recommended How-To's

Learn More

Change Log

10 October 2021 | Live Vertical Scaling Overview section updated

How-Tos

How-Tos

Activate and configure a Firewall for each Network Interface Card (NIC) to better protect your servers from attacks. IONOS Cloud Firewalls can filter incoming (ingress), outgoing (egress), or bidirectional traffic. When configuring firewalls, define appropriate rules to filter traffic accordingly.

Activating a Firewall

1. In the Workspace, select a Virtual Machine (VM) with a NIC.

2. From the Inspector, open the Network tab.

3. Open the properties of the NIC for which you wish to set up a Firewall.

4. To activate the Firewall,choose between Ingress / Egress / Bidirectional

Activating the Firewall without additional rules will block all incoming traffic. You can now add exceptions for ports and protocols by clicking Manage Rules.

Managing Firewall Rules

To create rules, define a new rule by clicking Create Firewall Rule. Additionally, you may add an existing set of rules by clicking Rules from Template. As a third option, you may import an existing rule set by clicking Clone Rules from other NIC.

Modify the values of the Firewall rule:

• Name: Enter a name for the rule.

• Source MAC: Enter the MAC address to be passed through by the firewall.

• Source IP: Enter the IP address to be passed through by the firewall.

• Target IP: If you use virtual IP addresses on the same network interface, you can enter them here to allow access.

• Port Range Start: Set the first port of an entire port range.

• Port Range End: Set the last port of a port range, or enter the port from Port Range Start if you only want this port to be allowed.

• ICMP Type: Enter the ICMP Type to be allowed. Example: 0 or 8 for echo requests (ping) or 30 for traceroutes.

• ICMP Code: Enter the ICMP Code to be allowed. Example: 0 for echo requests.

• IP Version: Select a version from the drop-down list. By default, it is Auto.

Click Save to confirm your Firewall setup.

You can enable the IPv6 LAN and configure the network to support IPv6. Using IPv6 LANs, devices can communicate on the same LAN using standard IPv6 protocols. IONOS LANs can help users in forwarding packets between devices and networks, ensuring that the network operates smoothly and efficiently.

Quicklinks

With IONOS Cloud Managed Kubernetes, you can quickly set up Kubernetes clusters and manage Node Pools. Consult our user guides, reference documentation, and FAQs to support your hosting needs.

Developer Tools

Recommended How-To's

Learn More

Creating a cluster in the Kubernetes Manager

1. Go to Containers > Managed Kubernetes.

2. Select Create Cluster.

3. Give the cluster a unique Name.

4. Select the Kubernetes Version you want to run in the cluster.

5. Click Create Cluster.

Result: The cluster will now be created and can be further modified and populated with node pools once its status is active.

To access the Kubernetes API provided by the cluster simply download the kubeconfig file and use it with tools like kubectl.

Configuring a cluster in Cluster Settings

1. Select Cluster name from the list and type a new name.

2. Select the Version of Kubernetes you want to run on the node pool.

3. Select the Maintenance time of your preferred maintenance window. Necessary maintenance for Managed Kubernetes will be performed accordingly.

4. Click Update Cluster to save your changes.

Deleting a cluster

1. Open the Kubernetes Manager.

2. Select the cluster from the list.

3. Click the Delete in the menu.

4. Confirm the deletion when prompted.

All Kubernetes API instructions can be found in the main Cloud API specification file.

To access the Kubernetes API provided by the cluster, simply download the kubeconfig for the cluster and use it with tools like kubectl.

Retrieve Kubernetes configuration files

GET https://api.ionos.com/cloudapi/v6/k8s/{k8sClusterId}/kubeconfig

Retrieve a configuration file for the specified Kubernetes cluster, in YAML or JSON format as defined in the Accept header; the default Accept header is application/yaml.

Path Parameters

Query Parameters

Headers

{}

{
    "httpStatus": 400,
    "messages": {
        "errorCode": "123",
        "message": "Error message example."
    }
}

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 . 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, capacity, and reserved . 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 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 or from . 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 .

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 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 .

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 .

With IONOS Cloud Networks, you can quickly provision and other Infrastructure-as-a-Service () offerings. Consult our user guides, reference documentation, and FAQs to support your hosting needs.

Developer Tools

Recommended How-To's

Learn More

Change Log

10 October 2021 | Live Vertical Scaling Overview section updated

If you want to build a network using static , IONOS Cloud offers you the option to reserve IP addresses for a fee. You can register one or more addresses in an IP block using the IP Manager. It is not possible to reserve a specific IP address; you are assigned a random address by IONOS Cloud.

An IP address can only be used in the data center from the region where it was reserved. Therefore, if you need an IP address for your virtual data center in Karlsruhe, you should reserve the IP address there. Each IP address can only be used once, but different IP addresses from a block can be used in different networks, provided these networks are provisioned in the same region where the IP block is located.

Reserving and using IP addresses is restricted to authorized users only. Contract owners and administrators may grant privileges to reserve IP addresses.

Reserving an IP address

1. Open the IP Manager: Menu > MANAGER Resources > IP Manager.

2. Click on + Reserve IPs.

3. Enter the following IP block information:

• Name: Enter a name for the IP block.

• Number of IPs: Enter the number of IPs you want to reserve.

• Region: Enter the location of the IONOS data center where you want your IPs to be available.

4. Confirm your entries by clicking Reserve IPs.

The number of IPs you have reserved are available as an IP block. The IP block details should now be visible on the right.

Returning an IP address

IP addresses cannot be returned individually, but only as a block and only when they are not in use. Please keep in mind that if you return a static IP address, you can't reserve it again afterwards.

1. Open the IP Manager: Menu > MANAGER Resources > IP Manager.

2. Ensure the IPs you want to release are not in use.

3. Select the required IP block.

4. Click Delete to return the IP block to the pool.

5. In the dialog that appears, confirm your action by clicking OK.

The IP block and all IP addresses contained are released and removed from your IONOS Cloud account.

A upgrade generally happens automatically during weekly maintenance. You can also trigger it manually, e.g. when upgrading to a higher version of . In any case the node pool upgrade will result in rebuilding all nodes belonging to the node pool.

During the upgrade, an "old" node in a node pool is replaced by a new node. This may be necessary for several reasons:

• Software updates: Since the nodes are considered immutable, IONOS Cloud does not install software updates on the running nodes, but replaces them with new ones.

• Configuration changes: Some configuration changes require replacing all included nodes.

Considerations: Multiple node pools of the same cluster can be upgraded at the same time. A node pool upgrade locks the affected node pool and you cannot make any changes until the upgrade is complete. During a node pool upgrade, all of its nodes are replaced one by one, starting with the oldest one. Depending on the number of nodes and your workload, the upgrade can take several hours.

Rebuilding a node

The rebuilding process consists of the following steps:

1. Provision a new node to replace the "old" one and wait for it to register in the control plane.

2. Exclude the "old" node from scheduling to avoid deploying additional pods to it.

3. Drain all existing workload from the "old" node.

• First, IONOS Cloud tries to gracefully drain the node.

- are enforced for up to 1 hour.

- for pods is respected for up to 1 hour.

• If the process takes more than 1 hour, all remaining pods are deleted.

4. Delete the "old" node from the node pool.

Draining nodes

Please consider the following node drain updates and their impact on the maintenance procedure:

Under the current platform setup, a node drain considers PodDisruptionBudgets (PDBs). If a concrete eviction of a pod violates an existing PDB, the drain would fail. If the drain of a node fails, the attempt to delete this node would also fail.

In the past, we observed problems with unprepared workloads or misconfigured PDBs, which often led to failing drains, node deletions and resulting failure in node pool maintenance.

To prevent this, the node drain will split into two stages. In the first stage, the system will continue to try to gracefully evict the pods from the node. If this fails, the second stage will forcefully drain the node by deleting all remaining pods. This deletion will bypass checking PDBs. This prevents nodes from failing during the drain.

How does this affect node pool maintenance?

As a result of the two-stage procedure, the process will stop failing due to unprepared workloads or misconfigured PDBs. However, please note that this change may still cause interruptions to workloads that are not prepared for maintenance. During maintenance, nodes are replaced one-by-one. For each node in a node pool, a new node is created. After that, the old node is drained and then deleted.

At times, a pod would not return to READY after having been evicted from a node during maintenance. In such cases, a PDB was in place for a pod’s workload. This led to failed maintenance and the rest of the workload left untouched. With the force drain behavior, the maintenance process will proceed and all parts of the workload will be evicted and potentially end up in a non-READY state. This might lead to an interruption of the workload. To prevent this, please ensure that your workload’s pods are prepared for eviction at any time.

Failover procedures

Planned failover: During a failure or planned failover, the client must reconnect to the database. A planned failover is signaled to the client by the closing of the TCP connection on the server. The client must also close the connection and reconnect.

In the event of a failure, the connection might not be closed correctly. The new leader will send a gratuitous ARP packet to update the MAC address in the client's ARP table. Open TCP connections will be reset once the client sends a TCP packet. We recommend re-establishing a connection to the database by using an exponential back-off retry with an initial immediate retry.

Uncontrolled disconnection: Since we do not allow read connections to standby nodes, only primary disconnections are possible. However, uncontrolled disconnections can happen during maintenance windows, a cluster change, and during unexpected situations such as loss of storage disk space. Such disconnections are destructive for the ongoing transactions and also clients should reconnect.

If a node is disconnected from the cluster, then a new node will be created and provisioned. Losing a primary node leads to the same situation when a client should reconnect. Losing a replica is not noticeable to the customer.

PostgreSQL upgrades

IONOS Cloud updates and patches your database cluster to achieve high standards of functionality and security. This includes minor patches for PostgreSQL, as well as patches for the underlying OS. We try to make these updates unnoticeable to your operation. However, occasionally, we might have to restart your PostgreSQL instance to allow the changes to take effect. These interruptions will only occur during the maintenance window for your database, which is a weekly four-hour window.

When your cluster only contains one replica you might experience a short down-time during this maintenance window, while your database instance is being updated. In a replicated cluster, we only update standbys, but we might perform a switchover in order to change the leader node.

Considerations: Updates to a new minor version are always backward compatible. Such updates are done during the maintenance window with no additional actions from the user side.

Major Version Upgrades

Prerequisites:

• Read the migration guide from Postgres (e.g. ) and make sure your database cluster can be upgraded

• Test the upgrade on development cluster with similar / the same data (you can create a new database cluster as a clone of your existing cluster)

• Prepare for a downtime during the major version upgrade

• Ensure the database cluster has enough available storage. While the upgrade is space-efficient (i.e. it does not copy the data directory), some temporary data is written to disk.

Before upgrading PostgreSQL major versions, customers should be aware that IONOS Cloud is not responsible for customer data or any utilized postgreSQL functionality. Hence, it is the responsibility of the customer to ensure that the migration to a new PostgreSQL major version does not impact their operations.

As per : "New major versions also typically introduce some user-visible incompatibilities, so application programming changes might be required."

Supported Versions

Starting with version 10, PostgreSQL moved to a yearly release schedule, where each major version is supported for 5 years after initial release. You can find more details at . We strive to support new versions as soon as possible.

When a major version approaches its end of life (EOL), we will announce the deprecation and removal of the version at least 3 months in advance. About 1 month before the EOL, no new database can be created with the deprecated version (the exact date will be part of the first announcement). When the EOL is reached, not yet upgraded databases will be upgraded in their next maintenance window.

You can migrate your existing databases over to DBaaS using the pg_dump, pg_restore and psql tools.

Using the SQL script format

To dump a database use the following command:

The -t <tablename> flag is optional and can be added if you only want to dump a single table.

This command will create a script file containing all instructions to recreate your database. It is the most portable format available. To restore it, simply feed it into psql. The database to restore to has to already exist.

The flag -F c is selecting the custom archive format. If you are interested in the other available formats, please refer to the .

To restore from a custom format archive you have to use pg_restore. The following command assumes that the database to restore to already exists.

When specifying the -C parameter, pg_restore can be instructed to recreate the database for you. For this to work you will need to specify a database that already exists. This database is used for initially connecting to and creating the new database. In this example we will use the database "postgres", which is the default database that should exist in every PostgreSQL cluster. The name of the database to restore to will be read from the archive.

Large databases can be restored concurrently by adding the -j <number> parameter and specifying the number of jobs to run concurrently.

For more information on pg_restore see the .

5 January 2022 | Product documentation updates:

• Upgrades added to Features

• WAL and Logs added to Resource Usage

• Logs changed in Limitations

• explained rotation of log files

• new Performance section (Estimates)

• further details regarding max_connections

21 December 2021 | Product documentation updates:

• new sections: High Availability and Scaling; Failover and Upgrade; Backup and Recovery

• new section: Activate Extensions

• new section: PostgreSQL FAQ

10 October 2021 | API documentation updates:

• the API swagger doc URL has changed: it is now (cutting out the "cloudapi" part)

• Renamed all parameters from snake_case to camelCase

• lastModifiedBy and createdBy now contain the unique username instead of the display name

• createdByUserId and lastModifiedByUserId now contain the UUID of the user, which is also used in other Cloud APIs.

• ram_size is now ram and changes to a plain integer (in megabytes)

• cpu_core_count is now cores

• replicas is now instances

• vdc_connection is now connection

• vdc_id is now datacenterId

• ip_address is now cidr

• in maintenance window: weekday is now dayOfTheWeek

• metadata is no longer part of the properties. metadata and id move up to sit beside properties

• lifecycle_status is now state and moves to metadata

• For cloning/restoring the backup: all parameters are now in the request body

• error messages no longer contain a titlefield

• backup_enabled field is now removed. Backup is always enabled and the option was deprecated for some time.

• the swagger spec was migrated to v3

IONOS DBaaS offers you to use a replicated MongoDB setup in minutes.

DBaaS is fully integrated into the . You may also manage it via automation tools like and .

Compatibility: DBaaS currently supports MongoDB version 5.0.

Locations: Offered only in limited locations due to technical reasons. Currently available are de/fra, de/txl, gb/lhr, es/vit, us/ewr and fr/par.

Features

High availability: Multi-instance clusters across different physical hosts with automatic data replication and failure handling.

Security: Communication between instances and between the client and cluster are protected with TLS using Let's Encrypt.

Backup: Daily snapshots are kept for up to seven days.

Restore: Databases can be restored in-place.

Resources: Cluster instances are dedicated Cubes, with a dedicated CPU, storage, and RAM. All data is stored on high-performance directly attached NVMe devices and encrypted at rest.

Network: Clusters can be accessed via private LANs.

Platform Tasks

DBaaS services offered by IONOS Cloud:

Our platform is responsible for all back-end operations required to maintain your database in optimal operational health.

• Database management via the DCD or the DBaaS API

• Configuring default values, for example for data replication and security related settings

• Automated backups for a period of 7 days

• Regular patches and upgrades during maintenance

• Disaster recovery via automated backup

• Service monitoring: both for the database and the underlying infrastructure

Customer database administration duties:

Tasks related to the optimal health of the database remain the responsibility of the customer. These include:

• Choosing an adequate sizing

• Data organisation

• Creation of indexes

• Updating statistics

• Consultation of access plans to optimise queries

Terminology

• Cluster: The whole MongoDB cluster, currently equal to the replica set.

• Instance: A single server or replica set member inside a MongoDB cluster.

Quick Links:

DBaaS API - OpenAPI Specification

Endpoint: https://api.ionos.com/databases/mongodb

To make authenticated requests to the API, you must include a few fields in the request headers. Please find relevant descriptions below:

Request parameter headers

Examples

We use curl in our examples, as this tool is available on Windows 10, Linux and macOS. Please refer to our blogpost about curl on Windows if you encounter any problems:

This guide shows you how to connect to a database from your managed Kubernetes cluster.

We assume the following prerequisites:

• A datacenter with id xyz-my-datacenter.

• A private LAN with id 3 using the network 10.1.1.0/24.

• A database connected to LAN 3 with IP 10.1.1.5/24.

• A Kubernetes cluster with id xyz-my-cluster.

In this guide we use DHCP to assign IPs to node pools. Therefore, it is important that the database is in the same subnet that is used by the DHCP server.

To enable connectivity, you must connect the node pools to the private LAN in which the database is exposed:

Wait for the node pool to become available. To test the connectivity let's create a pod that contains the Postgres tool pg_isready. If you have multiple node pools make sure to schedule the pod only the node pools that are attached to the additional LAN.

Let's create the pod...

... and attach to it.

If everything works, we should see that the database is accepting connections. If you see connection issues, make sure that the node is properly connected to the LAN. To debug the node start a debugging container ...

... and follow the .

With IONOS Cloud Database as a service, you can quickly setup and manage MongoDB database clusters. Leverage our user guides, reference documentation, and FAQs to support your hosting needs.

Product Overview

API How-Tos

With IONOS Cloud Monitoring as a Service (MaaS), you can track any virtual instance in your data center and set triggers when usage limits are reached. Leverage our user guides, reference documentation, and FAQs to support your hosting needs.

Developer Tools

Recommended How-To's

Change Log

10 October 2021 | Live Vertical Scaling Overview section updated

This How-to shows you how to migrate your MongoDB data from one cluster to another one. For example how to migrate from your existing on-premise MongoDB cluster to the IONOS MongoDB cluster.

This migration requires some downtime, as you need to stop write operations to your old cluster during dumping the data.

High level plan

The steps for a migration are as follows:

1. Preparations

2. Stop writes to old cluster - start of downtime

3. Dump data from old cluster using mongodump

4. Optionally: copy dump

5. Restore data into new cluster using mongorestore

6. Use the new cluster - end of downtime

Preparations

A place to run mongodump and mongorestore

You need one machine that can access the old cluster, that can run mongodump, and one machine that can access the new cluster, that can run mongorestore.

Both can happen on the same machine. If they're two different machines, you need a way to copy the data dump from one machine to the other.

Check MongoDB version

Both clusters need to be running the same major version. You can see the version in the greeting if you connect with mongosh or you can query it with db.version().

Access to old cluster

If your old cluster has access control enabled, you need a user with permissions for find to all databases. Easiest is to grant the backup role to the user that you want to use for dumping the data.

You can then verify that you can connect by using the command for mongodump mentioned in the section "Dump old data" and then aborting the dump with Ctrl-C.

User in new cluster

You need one user with write permissions to all databases that your dump contains.

Additionally you can't restore the users and roles via mongorestore. So you have to create all the users with their credentials and roles via the IONOS API. You can list all the users and roles in your old cluster with db.system.users.find() in the admin database and can then create them in the new cluster according to the documentation on . You can't see the plain text password on your old cluster, so you need to collect them from wherever you stored them.

Dump data from old cluster

You can dump the data from the old cluster with this command:

Optionally you can limit data using --db, --collection, or --query flags to only dump specific databases, collections, or documents.

Restore data in new cluster

You can restore the dumped date in the new cluster with this command:

admin.system.* resources are excluded, since you can't modify users and roles from inside MongoDB in an IONOS MongoDB cluster. You need to use the IONOS API for them.

Setting up a private network

DCD helps you connect the elements of your infrastructure and build a network to set up a functional virtual data center. Without a connected internet access element, your network is private.

The quickest way to connect elements is to drag them from the Palette directly onto elements that are already in the Workspace. The DCD will then show you whether and how the elements can be connected automatically.

1. Drag the elements from the Palette into the Workspace and connect them through their NICs.

2. In the Workspace, select the required VM; the Inspector will show its properties on the right.

3. From the Inspector, open the Network tab. Now you can access NIC properties.

4. Set NIC properties according to the following rules:

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

• Primary IP: The primary IP address is automatically assigned by the IONOS DHCP server. You can, however, enter an IP address for manual assignment by selecting one of the reserved IPs from the drop-down menu. Private IP addresses (according to RFC 1918) must be entered manually. The NIC has to be connected to the Internet.

• 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 check box 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.

When ready, provision your changes. The VDC will create a private network according to set properties.

Splitting LANs

1. To split a LAN, select the required LAN in the Workspace.

2. In the Inspector, open the Actions menu and select Split LAN.

3. Confirm by clicking Split LAN.

4. Make further changes to your data center and provision your changes when ready.

The selected LAN is split and new IPs are assigned to the NICs in the new LAN.

Merging LANs

1. To merge a LAN, select the required LAN in the Workspace.

2. To integrate this LAN into another LAN.

3. In the Inspector, open the Actions menu and select Merge LAN with another LAN.

4. In the dialog that appears, select the LANs to be merged with the selected LAN.

5. Select the checkboxes of the LANs you wish to keep separate.

6. Confirm by clicking Merge LANs.

(Optional) Make further changes to your data center.

7. Provision your changes

The selected LANs are merged and new IPs are assigned to the NICs in the newly integrated LAN.

Adding Internet access

Servers with internet access are assigned an IP automatically by the IONOS DHCP server. Please note that multiple servers sharing the same internet interface also share the same subnet. With required permissions, you can add as many internet access elements as you wish.

Users who do not have the permissions to add a new internet access element, can connect to an existing element in their VDC, provided they have the permissions to edit it.

1. To add internet access, drag the Internet element from the Palette onto the Workspace.

2. Connect this element with Servers.

3. Set further properties of the connection at the respective NIC.

This guide shows you how to connect to a MongoDB cluster from your managed Kubernetes cluster.

We assume the following prerequisites:

• A data center with id xyz-my-datacenter.

• A private LAN with id 3.

• A MongoDB cluster connected to LAN 3, with the connection string mongodb+srv://m-xyz-example.mongodb.de-txl.ionos.com.

• A Kubernetes cluster with id xyz-my-k8s-cluster.

• ionosctl set up with your IONOS credentials.

In this guide, we use DHCP to assign IP addresses to node pools. Therefore, it is important that the database is in the same subnet that's used by the DHCP server.

To enable connectivity, you must connect the node pools to the private LAN with the MongoDB cluster:

ionosctl k8s nodepool create --cluster-id xyz-my-k8s-cluster --datacenter-id xyz-my-datacenter --lan-ids 3 --dhcp=true --name=my_nodepool

Wait for the node pool to become available. To test the connectivity you can create a pod that contains the MongoDB tool mongosh. If you have multiple node pools, make sure to schedule the pod on one of the node of the node pools that are attached to the private LAN.

# pod.yaml
apiVersion: v1
kind: Pod
metadata:
  name: connectivity-test
  labels:
    role: connectivity-test
spec:
  containers:
  - name: mongo
    image: mongo
    stdin: true
    tty: true
    command:
      - "/bin/bash"

Let's create the pod...

kubectl apply -f pod.yaml

... and attach to it.

kubectl attach -it connectivity-test
If you don't see a command prompt, try pressing enter.
root@connectivity-test:/# mongosh "mongodb+srv://m-xyz-example.mongodb.de-txl.ionos.com"
Current Mongosh Log ID:	631063ca901a9459bab0b4d4
Connecting to:		mongodb+srv://m-xyz-example.mongodb.de-txl.ionos.com/?appName=mongosh+1.5.4
Using MongoDB:		5.0.10
Using Mongosh:		1.5.4

For mongosh info see: https://docs.mongodb.com/mongodb-shell/


To help improve our products, anonymous usage data is collected and sent to MongoDB periodically (https://www.mongodb.com/legal/privacy-policy).
You can opt-out by running the disableTelemetry() command.

Enterprise a0def940-2455-11ed-a564-7a0f508690ac [primary] test> 

If everything works, we should see that the database is accepting connections. If you see connection issues, make sure that the node is properly connected to the LAN. To debug the node start a debugging container ...

kubectl debug node/$(kubectl get po connectivity-test -o jsonpath="{.spec.nodeName}") -it --image=busybox

... and follow the network troubleshooting guide.

A Cloud Cube (or just Cube) is a virtual machine 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 the Cloud Cubes.

You can create and configure your Cubes visually using the DCD interface. See the Setup a Cloud Cube page for more information. However, the creation and management of Cubes is easily automated via the Cloud API, as well as our custom-made tools and SDKs.

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 VDC 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 Cores for the enterprise VM instances and SSD 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 NVMe volumes 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 IP address.

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.

Add-on network block storage: You may attach more HDD or SSD (Standard or Premium) block storage. Each Cube supports up to 23 block storage devices in addition to the existing NVMe volume. Added HDD and SSD devices, as well as CD-ROMs, can be unmounted and deleted any time after the Cube is provisioned for use.

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.

Users who are not contract owners or administrators need access rights to view, use, or edit resources in a . These access rights are assigned to groups and are inherited by group members.

Setting access rights and ownership

Users can access a resource with the following access rights:

• Read: Users can see and use the resource, but they cannot modify it. Read access is automatically granted as soon as a user is assigned to a group that has this access right.

• Edit: Users can modify and delete the resource.

• Share: Users can share a resource, including their access rights, with the groups to which they belong.

A user who created a resource is the owner of that resource and can specify its access rights.

The owner is shown in the Security tab of a resource.

Setting restrictions using Two-Factor Authentication

In addition to enabling access to resource, for users of authorized groups only, data centers and snapshots can be protected even further by restricting access to users who have 2-factor authentication activated. Other users cannot see or select these resources - even if they belong to an authorized group.

Depending on their role, users can set access rights at the resource level and in the User Manager.

Setting access rights at the resource level

1. Select the required resource

2. Open the data center:

• Images: Menu Bar > Resource Manager > Image Manager > Image.

• Snapshots: Menu Bar > Resource Manager > Image Manager > Snapshot.

• IP addresses: Menu Bar > Resource Manager > IP Manager.

• Kubernetes Cluster: Menu Bar > Resource Manager > Kubernetes Manager.

3. Select the required resource

4. Open Security > Visible to Groups

5. Enable access:

• From the + Add Group menu, select the required groups. Read access is granted. Users can see and use, but not modify the resource.

• (Optional) Select further permissions (Edit, Share). You may only share permissions that you have yourself.

6. Restrict or disable access:

• Select the required group

• Deactivate the checkbox of the permission

Read access is retained.

Alternatively, you can click Remove Group. Access will be disabled for all members of the selected group.

Optional: To protect the resource (data center, snapshots) more thoroughly by only allowing access to users whose login is secured with 2-factor authentication, activate the 2-Factor Protected check box.

Setting access rights in the User Manager

Contract owners and administrators can also define in the User Manager who may access a resource to what extent.

Set the access rights in the User Manager

1. Open the User Manager: Menu Bar > Resource Manager > User Manager.

2. In the Resources, select the required resource.

3. Open the Visible to Groups.

4. Enable access

• From the + Add Group list, add the required groups.

• (Optional) To enable write access or sharing of a resource, activate the relevant check box.

5. Disable access: deactivate the checkbox of the permission or click Remove Group.

Optional: To protect the resource (data center, snapshots) more thoroughly by only allowing access to users whose login is secured with 2-factor authentication, activate the 2-Factor Protected check box.

Assigning resources to a group

1. In the Groups, select the required group.

2. Open the Resources of Group.

3. To enable access:

• Select the required resource by clicking on + Grant Access. This enables read access to the selected resource.

• (Optional) To enable write access or sharing of a resource, activate the respective check box.

4. To disable access:

• Select the required resource.

• Deactivate the check box of the appropriate permission or click on Revoke Access.

You can find more information about managing the Groups here.

With IONOS Cloud Database as a Service, you can quickly setup and manage a PostgreSQL database. Leverage our user guides, reference documentation, and FAQs to support your hosting needs.

Product Overview

DCD How-Tos

API How-Tos

API Reference

SDK Reference

Frequently Asked Questions

Quick Links:

DBaaS API - OpenAPI Specification

Endpoint: https://api.ionos.com/docs/postgresql/v1/

To make authenticated requests to the API, you must include a few fields in the request headers. Please find relevant descriptions below:

Request parameter headers

Examples

We use curl in our examples, as this tool is available on Windows 10, Linux and macOS. Please refer to our blogpost about curl on Windows if you encounter any problems:

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 [email protected]
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 [email protected]

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:

[email protected]'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 Cubes.

Managing IP Failover groups

To make sure that high-availability (HA) or setups on your are effective in case of events such as a physical server failure, you should set up "IP failover groups".

They are essential to all HA or fail-over setups irrespective of the mechanism or protocol used.

A failover group is characterized by the following components:

• Members: The same (reserved, public) is assigned to all members of an IP failover group so that communication within this group can continue in the event of a failure. You can set up multiple IP failover groups. A can be a member of multiple IP failover groups. Virtual servers should be spread over different .\ \ The rules for managing the traffic between your VMs in event of a failure are specified at the operating system level using the options and features for setting up high-availability or fail-over configurations. Users must have access rights for the IPs they wish to use.

• Master: During the initial provisioning, the master of an IP failover group in the DCD represents the master of the HA setup on your virtual machines. If you change the master later, you won't have to change the master of the IP failover group in the DCD.

• Primary IP address: The IP address of the IP failover group can be provisioned as the primary or additional IP address. We recommend that you provide the IP address used for the IP failover group as the primary IP address, as it is used to calculate the gateway IP, which is advantageous for some backup solutions. Please note that this will replace the previously provisioned primary IP address. When there are multiple IP failover groups in a LAN, a involved in multiple of these groups can only be used once for the primary IP address. The DCD will alert you accordingly.

Limitations and restrictions

For technical reasons this feature can only be used subject to the following limitations:

• In public LANs that do not contain load balancers.

• With reserved public IP addresses only - DHCP-generated IP addresses cannot be used.

• Virtual MAC addresses are not supported.

• IP failover must be configured for all HA setups.

Creating an IP Failover Group