Overview
9 min
a cube https //docs ionos com/cloud/support/general information/glossary of terms#cloud cubes is a virtual machine (vm) https //docs ionos com/cloud/support/general information/glossary of terms#virtual machine vm with an attached nvme volume you can use each newly created cube as a new vm, either standalone or in combination with other products for more information, see cubes https //docs ionos com/cloud/compute services/cubes/cubes faq you can create and configure your cubes visually using the dcd https //docs ionos com/cloud/support/general information/glossary of terms#dcd interface for more information, see create a cube https //docs ionos com/cloud/compute services/cubes/dcd how tos/set up cube however, the creation and management of cubes are easily automated via the api docid 7ka0om8xn8lizkthrroxi , as well as our custom made tools and sdks https //docs ionos com/cloud/support/general information/glossary of terms#sdk configuration templates you may choose between nine template sizes each template varies by processor, memory, and storage capacity warning configuration templates are set upon provisioning and cannot subsequently be changed the breakdown of resources is as follows basic cubes size vcpus ram nvme storage basic cube xs 1 2 gb 60 gb basic cube s 2 4 gb 120 gb basic cube m 4 8 gb 240 gb basic cube l 8 16 gb 480 gb basic cube xl 16 32 gb 960 gb memory cubes size vcpus ram nvme storage memory cube s 2 8 gb 120 gb memory cube m 4 16 gb 240 gb memory cube l 8 32 gb 480 gb memory cube xl 16 64 gb 960 gb resource usage counters the use of cubes' vcpu, ram, and nvme storage resources counts into existing vdc https //docs ionos com/cloud/support/general information/glossary of terms#vdc resource usage however, dedicated resource usage counters are enabled for cubes these counters permit granular monitoring of vcpus and nvme storage, which differ from dedicated core servers for the enterprise vm instances and ssd https //docs ionos com/cloud/support/general information/glossary of terms#ssd block storage billing suspended cubes continue to incur costs if you do not delete unused instances, you will incur usage charges we recommend creating snapshots of nvme volumes https //docs ionos com/cloud/support/general information/glossary of terms#non volatile memory express nvme you do not need immediately and deleting unused instances to save costs use these snapshots to recreate identical cubes as needed recreated instances may be assigned a different ip address https //docs ionos com/cloud/support/general information/glossary of terms#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 https //docs ionos com/cloud/support/general information/glossary of terms#hdd or ssd https //docs ionos com/cloud/support/general information/glossary of terms#ssd (standard or premium) block storage based on the need 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 data security provides direct attached storage (das) for cube instances, offering nvme volumes on the same physical host as the cube for das volumes created after feature availability, implements encryption at rest and secure deletion, mirroring the security features https //docs ionos com/cloud/backup and storage/block storage/overview/data security of block storage encryption at rest protects inactive data on physical media das uses the same encryption technology as block storage, aes xts (256 bit) encryption method each volume has a unique, securely stored encryption key that is inaccessible to root users secure deletion ensures that deleted data cannot be restored, even with physical media access when a das volume is deleted metadata is "zeroed out," destroying the block mapping the volume's encryption key is destroyed, making any remaining encrypted data unreadable limitations 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 note you can contact support https //docs ionos com/cloud/support/general information/contact information to increase the resource limits for your account
