# ionoscloud\_server Dedicated Core Servers or [Enterprise Servers](https://docs.ionos.com/cloud/compute-services/compute-engine/dedicated-core) are provisioned and hosted in one of IONOS' physical data centers. Dedicated Core Servers behave exactly like physical servers. They can be configured and managed with your choice of the operating system. Check out [Limitations](https://docs.ionos.com/cloud/compute-services/compute-engine/dedicated-core#limitations). ## Example Usage This resource will create an operational server. After this section completes, the provisioner can be called. ### Dedicated Core Server ```hcl data "ionoscloud_image" "example" { type = "HDD" cloud_init = "V1" image_alias = "ubuntu:latest" location = "us/las" } resource "ionoscloud_datacenter" "example" { name = "Datacenter Example" location = "us/las" description = "Datacenter Description" sec_auth_protection = false } resource "ionoscloud_lan" "example" { datacenter_id = ionoscloud_datacenter.example.id public = true name = "Lan Example" } resource "ionoscloud_ipblock" "example" { location = ionoscloud_datacenter.example.location size = 4 name = "IP Block Example" } resource "ionoscloud_server" "example" { name = "Server Example" datacenter_id = ionoscloud_datacenter.example.id cores = 1 ram = 1024 image_name = data.ionoscloud_image.example.name image_password = random_password.server_image_password.result type = "ENTERPRISE" volume { name = "system" size = 5 disk_type = "SSD Standard" user_data = "foo" bus = "VIRTIO" availability_zone = "ZONE_1" } nic { lan = ionoscloud_lan.example.id name = "system" dhcp = true firewall_active = true firewall_type = "BIDIRECTIONAL" ips = [ ionoscloud_ipblock.example.ips[0], ionoscloud_ipblock.example.ips[1] ] firewall { protocol = "TCP" name = "SSH" port_range_start = 22 port_range_end = 22 source_mac = "00:0a:95:9d:68:17" source_ip = ionoscloud_ipblock.example.ips[2] target_ip = ionoscloud_ipblock.example.ips[3] type = "EGRESS" } } label { key = "labelkey1" value = "labelvalue1" } label { key = "labelkey2" value = "labelvalue2" } } resource "random_password" "server_image_password" { length = 16 special = false } ``` ### With IPv6 Enabled ```hcl resource "ionoscloud_datacenter" "example" { name = "Resource Server Test" location = "us/las" } resource "ionoscloud_ipblock" "webserver_ipblock" { location = "us/las" size = 4 name = "webserver_ipblock" } resource "ionoscloud_lan" "example" { datacenter_id = ionoscloud_datacenter.example.id public = true name = "public" ipv6_cidr_block = cidrsubnet(ionoscloud_datacenter.example.ipv6_cidr_block,8,10) } resource "ionoscloud_server" "example" { name = "Resource Server Test" datacenter_id = ionoscloud_datacenter.example.id cores = 1 ram = 1024 image_name ="ubuntu:latest" image_password = random_password.server_image_password.result type = "ENTERPRISE" volume { name = "system" size = 5 disk_type = "SSD Standard" user_data = "foo" bus = "VIRTIO" availability_zone = "ZONE_1" } nic { lan = ionoscloud_lan.example.id name = "system" dhcp = true firewall_active = true firewall_type = "BIDIRECTIONAL" ips = [ ionoscloud_ipblock.webserver_ipblock.ips[0], ionoscloud_ipblock.webserver_ipblock.ips[1] ] dhcpv6 = true ipv6_cidr_block = cidrsubnet(ionoscloud_lan.example.ipv6_cidr_block,16,24) ipv6_ips = [ cidrhost(cidrsubnet(ionoscloud_lan.example.ipv6_cidr_block,16,24),10), cidrhost(cidrsubnet(ionoscloud_lan.example.ipv6_cidr_block,16,24),20), cidrhost(cidrsubnet(ionoscloud_lan.example.ipv6_cidr_block,16,24),30) ] firewall { protocol = "TCP" name = "SSH" port_range_start = 22 port_range_end = 22 source_mac = "00:0a:95:9d:68:17" source_ip = ionoscloud_ipblock.webserver_ipblock.ips[2] target_ip = ionoscloud_ipblock.webserver_ipblock.ips[3] type = "EGRESS" } } } resource "random_password" "server_image_password" { length = 16 special = false } ``` ### CUBE Server ```hcl data "ionoscloud_template" "example" { name = "Basic Cube XS" } resource "ionoscloud_datacenter" "example" { name = "Datacenter Example" location = "de/txl" } resource "ionoscloud_lan" "example" { datacenter_id = ionoscloud_datacenter.example.id public = true name = "Lan Example" } resource "ionoscloud_server" "example" { name = "Server Example" availability_zone = "ZONE_2" image_name = "ubuntu:latest" type = "CUBE" template_uuid = data.ionoscloud_template.example.id image_password = random_password.server_image_password.result datacenter_id = ionoscloud_datacenter.example.id volume { name = "Volume Example" licence_type = "LINUX" disk_type = "DAS" } nic { lan = ionoscloud_lan.example.id name = "Nic Example" dhcp = true firewall_active = true } } resource "random_password" "server_image_password" { length = 16 special = false } ``` ### Server that boots from CDROM ```hcl resource "ionoscloud_datacenter" "cdrom" { name = "CDROM Test" location = "de/txl" description = "CDROM image test" sec_auth_protection = false } resource "ionoscloud_lan" "public" { datacenter_id = ionoscloud_datacenter.cdrom.id public = true name = "Uplink" } data "ionoscloud_image" "cdrom" { image_alias = "ubuntu:latest_iso" type = "CDROM" location = "de/txl" cloud_init = "NONE" } resource "ionoscloud_server" "test" { datacenter_id = ionoscloud_datacenter.cdrom.id name = "ubuntu_latest_from_cdrom" cores = 1 ram = 1024 cpu_family = ionoscloud_datacenter.cdrom.cpu_architecture[0].cpu_family type = "ENTERPRISE" volume { name = "hdd0" disk_type = "HDD" size = 50 licence_type = "OTHER" } nic { lan = 1 dhcp = true firewall_active = false } } ``` ## Argument reference * `template_uuid` - (Optional)\[string] The UUID of the template for creating a CUBE server; the available templates for CUBE servers can be found on the templates resource * `name` - (Required)\[string] The name of the server. * `datacenter_id` - (Required)\[string] The ID of a Virtual Data Center. * `hostname` - (Optional)(Computed)\[string] The hostname of the resource. Allowed characters are a-z, 0-9 and - (minus). Hostname should not start with minus and should not be longer than 63 characters. If no value provided explicitly, it will be populated with the name of the server * `cores` - (Optional)(Computed)\[integer] Number of server CPU cores. * `ram` - (Optional)(Computed)\[integer] The amount of memory for the server in MB. * `image_name` - (Optional)\[string] The name, ID or alias of the image. May also be a snapshot ID. It is required if `licence_type` is not provided. Attribute is immutable. * `availability_zone` - (Optional)\[string] The availability zone in which the server should exist. E.g: `AUTO`, `ZONE_1`, `ZONE_2`. This property is immutable. * `licence_type` - (Optional)\[string] Sets the OS type of the server. * `cpu_family` - (Optional)\[string] CPU architecture on which server gets provisioned; not all CPU architectures are available in all datacenter regions; available CPU architectures can be retrieved from the datacenter resource. E.g.: "INTEL\_SKYLAKE" or "INTEL\_XEON". * `vm_state` - (Optional)\[string] Sets the power state of the server. E.g: `RUNNING`, `SHUTOFF` or `SUSPENDED`. SUSPENDED state is only valid for cube. SHUTOFF state is only valid for enterprise(dedicated core). * `volume` - (Optional) See the [Volume](https://docs.ionos.com/sections-test/terraform/resources/volume) section. * `nic` - (Optional) See the [Nic](https://docs.ionos.com/sections-test/terraform/resources/nic) section. * `firewall` - (Optional) Allows to define firewall rules inline in the server. See the [Firewall](https://docs.ionos.com/sections-test/terraform/resources/firewall) section. * `boot_volume` - (Computed) The associated boot volume. * `boot_cdrom` - ***DEPRECATED*** Please refer to [ionoscloud\_server\_boot\_device\_selection](https://docs.ionos.com/sections-test/terraform/resources/server_boot_device_selection) (Optional)(Computed)\[string] The associated boot drive, if any. Must be the UUID of a bootable CDROM image that can be retrieved using the [ionoscloud\_image](https://docs.ionos.com/sections-test/terraform/data-sources/image) data source. * `boot_image` - (Optional)\[string] The image or snapshot UUID / name. May also be an image alias. It is required if `licence_type` is not provided. * `primary_nic` - (Computed) The associated NIC. * `primary_ip` - (Computed) The associated IP address. * `firewallrule_id` - (Computed) The associated firewall rule. * `firewallrule_ids` - (Computed) The associated firewall rules. * `ssh_key_path` - (Optional)\[list] List of absolute paths to files containing a public SSH key that will be injected into IonosCloud provided Linux images. Also accepts ssh keys directly. Required for IonosCloud Linux images. Required if `image_password` is not provided. Does not support `~` expansion to homedir in the given path. This property is immutable. * `ssh_keys` - (Optional)\[list] Immutable List of absolute or relative paths to files containing public SSH key that will be injected into IonosCloud provided Linux images. Also accepts ssh keys directly. Public SSH keys are set on the image as authorized keys for appropriate SSH login to the instance using the corresponding private key. This field may only be set in creation requests. When reading, it always returns null. SSH keys are only supported if a public Linux image is used for the volume creation. Does not support `~` expansion to homedir in the given path. * `image_password` - (Optional)\[string] Required if `ssh_key_path` is not provided. * `type` - (Optional)(Computed)\[string] Server usages: \* `type` - Server usages: [ENTERPRISE](https://docs.ionos.com/cloud/compute-services/compute-engine/dedicated-core) now named dedicated core, [CUBE](https://docs.ionos.com/cloud/compute-services/cubes) or [VCPU](https://docs.ionos.com/cloud/compute-services/compute-engine/vcpu-server). This property is immutable. * `label` - (Optional)\[set] A label can be seen as an object with only two required fields: `key` and `value`, both of the `string` type. Please check the example presented above to see how a `label` can be used in the plan. A server can have multiple labels. * `key` - (Required)\[string] The key of the label. * `value` - (Required)\[string] The value of the label. * `inline_volume_ids` - (Computed) A list with the IDs for the volumes that are defined inside the server resource. * `security_groups_ids` - (Optional) The list of Security Group IDs for the * `allow_replace` - (Optional)\[bool] When set to true, allows the update of immutable fields by first destroying and then re-creating the server. * `nic_multi_queue` - (Optional)\[bool] Activate or deactivate the Multi Queue feature on all NICs of the server. This feature is beneficial to enable when the NICs are experiencing performance issues (e.g. low throughput). Toggling this feature will also initiate a restart of the server. If the specified value is `true`, the feature will be activated; if it is not specified or set to `false`, the feature will be deactivated. The feature cannot be activated for `CUBE` servers. ⚠️ ***Warning:**** ****`allow_replace`**** ****- lets you update immutable fields, but it first destroys and then re-creates the server in order to do it. This field should be used with care, understanding the risks.*** > **⚠ WARNING** > > Image\_name under volume level is deprecated, please use image\_name under server level ssh\_key\_path and ssh\_keys fields are immutable. > **⚠ WARNING** > > If you want to create a **CUBE** server, you have to provide the `template_uuid`. In this case you can not set `cores`, `ram` and `volume.size` arguments, these being mutually exclusive with `template_uuid`. > > In all the other cases (**ENTERPRISE** servers) you have to provide values for `cores`, `ram` and `volume size`. ## Import Resource Server can be imported using the `resource id` and the `datacenter id`, e.g.. Passing only resource id and datacenter id means that the first nic found linked to the server will be attached to it. ```hcl import { to = ionoscloud_server.example id = "datacenter id/server id" } ``` Auto-generate the server resource in the `generated.tf` file using the following command: ```shell terraform plan -generate-config-out=generated.tf ``` The older syntax can be for importing the resource is still supported: ```shell terraform import ionoscloud_server.myserver datacenter uuid/server uuid ``` Optionally, you can pass `primary_nic` and `firewallrule_id` so terraform will know to import also the first nic and firewall rule (if it exists on the server): ```shell terraform import ionoscloud_server.myserver datacenter uuid/server uuid/primary nic id/firewall rule id ``` ## Notes Please note that for any secondary volume, you need to set the **licence\_type** property to **UNKNOWN** ⚠️ **Note:** Important for deleting an `firewall` rule from within a list of inline resources defined on the same nic. There is one limitation to removing one firewall rule from the middle of the list of `firewall` rules. Terraform will actually modify the existing rules and delete the last one. More details [here](https://github.com/hashicorp/terraform/issues/14275). There is a workaround described in the issue that involves moving the resources in the list prior to deletion. `terraform state mv .[] .[]`