Changes to AMD Opteron Virtual Machines

note starting july 29th, creating new vms with amd opteron cpus will no longer be possible existing vms can continue to run and will be unaffected by this change they can also undergo regular power cycles without impacting functionality best practices for provisioning new opteron vms for terraform users configuration check ensure that the cpu family parameter in your terraform configuration file ( tf ) is not set to amd opteron the cpu family parameter is optional, but if it is set to amd opteron , it must be updated or removed to avoid errors for more information about the available options, see data centers https //api ionos com/docs/cloud/v6/#tag/data centers provisioning before provisioning new vms, verify that the terraform configuration file ( tf ) is updated appropriately run terraform plan to confirm the configuration is correct provision the vm using terraform apply for crossplane users configuration check if the specification file has the cpufamily set to amd opteron , it should be updated to avoid errors failure to update the cpufamily parameter will result in an error when managing vms verification check your specification files for the cpufamily parameter update the parameter from amd opteron to the appropriate value according to your needs limitations while creating new vms with amd opteron these limitations apply when you try to create new vms you cannot select amd opteron as the cpu architecture for new vms you cannot switch a running or deallocated vm's cpu family to amd opteron for further assistance or questions, contact support https //docs ionos com/cloud/support/general information/contact information