Root Password in the Control Panel

Bit by bit, we're increasing our cloud security. Now, we've revamped how we handle your service passwords with a new encrypted format. There's a myriad of encryption methods out there, but we've settled on RSA asymmetric encryption, widely recognized as one of the most robust options available today. Here's the rundown: You generate a password for your server or DBaaS, which then gets securely stored in an encrypted state within a dedicated database. This password gets encrypted using a public key, neatly stores in container A. Accessing the data requires decryption, for which a private key, securely stored in container B, is necessary. So, your password resides in one spot, the public key in another, and the private key in yet another. This setup reduces the chances of any successful hacking attempts to virtually zero. And as per usual, here are some handy links for you to create a new server or database.

Everything you need to configure network settings, control traffic and load is now in the overall "Networks" section. How it was Private networks, firewall and load balancers were located in different places in the panel. You had to navigate through the menu looking for the necessary features. It was awkward! How it is now But now you can switch between the services in a single window making it much easier to work with them. Soon we will add Floating IPs—the IPs that can be transferred between services in the same availability zone. Cool, I'm going to check it out →

You have asked for automatic configuration of new virtual machines and we have delivered ;) This task is solved by cloud-init, a new tool available in the cloud server creation section. An important benefit Cloud-init is triggered automatically the first time you start a new VM. Just provide a script for the cloud-init agent and it will do everything for you: → Install the required package. → Create a user. → Enable the necessary security settings. → Handle network settings. Scripting and editing → You can work with scripts in #cloud-config and #bin/sh format — they are the ones you need to start the cloud-init process. → Once the cloud server is created, the given script is saved. You can edit it later on a running machine. Try cloud-init in action →