Limitations

this section covers cloud gpu vm policies and infrastructure limitations deployment & availability frankfurt data center you can currently access cloud gpu vms only in the frankfurt de/fra/2 data center the availability zone is always set to auto and cannot be changed instance limits by default, you can deploy only 1 cloud gpu vm using the h200–s template to deploy templates sized m , l , or xl , or to run multiple s instances, you must first request a resource limit increase through the support https //docs ionos com/cloud/support/general information/contact information instance lifecycle policy maintenance reboots while we prioritize planned maintenance windows, critical security patches, urgent stability issues or incidents may require emergency maintenance with extremely short or no notification design your applications to handle unexpected restarts and configure services to restart automatically on boot maintenance downtime gpu cloud vms do not support seamless background transfers during maintenance consequently, some planned infrastructure updates will require a temporary shutdown or reboot of your instance fixed resource scaling size your servers appropriately at creation time cpu core and ram upscaling or downscaling are not currently supported after provisioning management restrictions templates you cannot create new templates or modify existing templates boot volume restrictions the first connected boot volume has the following restrictions it cannot be detached from the vm it cannot be upscaled after deployment size must be determined during the initial provisioning resource scaling restrictions size servers appropriately at creation time, because cpu core and ram upscaling or downscaling are not currently supported plan your workload requirements carefully during the initial provisioning volume management additional volumes support standard management operations, including scaling, detaching, and attaching, through the api, or the dcd