> For the complete documentation index, see [llms.txt](https://docs.ionos.com/puppet-v6/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/puppet-v6/types/compute-engine/server.md).

# server

Type representing a IonosCloud server.

## Parameters:

| Name | Required | Description             |
| ---- | :------: | ----------------------- |
| name |   true   | The name of the server. |

## Properties:

| Name               | Required | Description                                                                                         |
| ------------------ | :------: | --------------------------------------------------------------------------------------------------- |
| ensure             |    No    | Valid values are `present`, `absent`, `running`, `stopped`, `suspended`.                            |
| type               |    No    | The type of the server. Valid values are `ENTERPRISE`, `CUBE`.                                      |
| template\_uuid     |    No    | The template UUID of the server, needed for a CUBE server.                                          |
| datacenter\_id     |    No    | The virtual data center where the server will reside.                                               |
| datacenter\_name   |    No    | The name of the virtual data center where the server will reside.                                   |
| cores              |    No    | The number of CPU cores assigned to the server.                                                     |
| cpu\_family        |    No    | The CPU family of the server. Valid values are `AMD_OPTERON`, `INTEL_XEON`, `INTEL_SKYLAKE`.        |
| ram                |    No    | The amount of RAM in MB assigned to the server.                                                     |
| availability\_zone |    No    | The availability zone of where the server will reside. Valid values are `AUTO`, `ZONE_1`, `ZONE_2`. |
| boot\_volume       |    No    | The boot volume name, if more than one volume it attached to the server.                            |
| licence\_type      |    No    | The OS type of the server. Valid values are `LINUX`, `WINDOWS`, `WINDOWS2016`, `UNKNOWN`, `OTHER`.  |
| volumes            |    No    | A list of volumes to associate with the server.                                                     |
| cdroms             |    No    | A list of Cdroms to associate with the server.                                                      |
| purge\_volumes     |    No    | Sets whether attached volumes are removed when server is removed. Valid values are `true`, `false`. |
| nics               |    No    | A list of network interfaces associated with the server.                                            |
| id                 |    No    | The server ID.                                                                                      |
| \*\*\*             |          |                                                                                                     |

### Changeable properties:

* cores
* cpu\_family
* ram
* availability\_zone
* boot\_volume
* volumes
* nics

## Examples

### To list resources:

```bash
puppet resource server
```

> ***NOTE:*** If two resources have the same name only one of them will be shown.

### To create, update or delete a resource:

```ruby
$datacenter_name = 'MyDataCenter'

server { 'worker4' :
  ensure          => present,
  cores           => 1,
  datacenter_name => $datacenter_name,
  ram             => 1024,
  cpu_family      => 'INTEL_SKYLAKE',
  volumes         => [
    {
      name              => 'system',
      size              => 50,
      bus               => 'VIRTIO',
      volume_type       => 'SSD',
      licence_type      => 'LINUX',
      availability_zone => 'AUTO'
    }
  ],
  nics            => [
    {
      name            => 'testnic3',
      dhcp            => true,
      lan             => 'public',
      ips             => ['127.0.0.1'],
      firewall_active => true,
      firewall_type   => 'EGRESS',
      firewall_rules  => [
        {
          name             => 'HTTP3',
          type             => 'INGRESS',
          protocol         => 'TCP',
          port_range_start => 76,
          port_range_end   => 80
        },
        {
          name             => 'SSH',
          type             => 'INGRESS',
          protocol         => 'TCP',
          port_range_start => 22,
          port_range_end   => 27
        }
      ],
      flowlogs        => [
        {
          name      => 'test2',
          action    => 'ALL',
          bucket    => 'testtest234134124214',
          direction => 'INGRESS',
        }
      ]
    },
    {
      name            => 'testnic2',
      dhcp            => true,
      lan             => 'public',
      ips             => ['127.0.0.1'],
      firewall_active => true,
      firewall_type   => 'INGRESS',
    }
  ],
  cdroms          => [
    {
      id => '1c511436-5bfa-11ec-adcb-2e0e2737acfd',
    }
  ]
}
```

> ***NOTE:*** If two resources with the same name ar found an error will be thrown, this only applies to cases where the resource cannot be identified. Example: an error is thrown for two servers with the same name in the same datacenter, not for two servers with the same name, but in different datacenters.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ionos.com/puppet-v6/types/compute-engine/server.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.