Actions140
- Application Load Balancer Actions
- Contract Actions
- Datacenter Actions
- Firewall Rule Actions
- Image Actions
- IP Block Actions
- Kubernetes Cluster Actions
- LAN Actions
- Load Balancer Actions
- Location Actions
- NAT Gateway Actions
- Network Load Balancer Actions
- NIC Actions
- Node Pool Actions
- Private Cross-Connect Actions
- Request Actions
- Security Group Actions
- Server Actions
- Snapshot Actions
- Target Group Actions
- Volume Actions
Server → Create
AI-generatedSummary
Creates a server in the specified IONOS Cloud data center. Choose a server type, provide its required sizing or template and boot-volume details, and optionally set placement, boot, and network options.
Inputs
- Datacenter ID (required) — ID of the data center where the server will be created.
- Name (required) — Name for the server.
- Cores and RAM (MB) (required) — For Enterprise and VCPU servers, set the processor core count (minimum 1) and memory (minimum 256 MB). These fields are hidden for CUBE and GPU types, whose resources come from the template.
- Server Type — Select Enterprise, CUBE, VCPU, or GPU; defaults to Enterprise.
- Template UUID (required) — For CUBE and GPU servers, provide the template UUID, which determines cores, RAM, and, for GPU servers, GPU resources.
- Volume (required) — For CUBE and GPU servers, configure the boot volume, including its image and optional image password, bus, disk type, availability zone, licence type, name, serial exposure, and legacy BIOS requirement. GPU servers support only IONOS Cloud Linux images and Linux licence type; CUBE servers support the listed licence types. Some volume settings are ignored or not applicable for particular types.
- Additional Fields — Optionally set server availability zone, boot CD-ROM or boot volume UUID, CPU family, NIC multi-queue, or placement group ID.
- Include Request Status — When enabled, include request tracking information from the asynchronous operation's Location header.
- Include Response Headers — When enabled, return the response body under a body key alongside HTTP headers and status code.
- Request Options — Configure request batching, SSL certificate validation, an HTTP proxy, or timeout.
Output shape
A server creation response, typically containing the created server record.
Creation is asynchronous; request tracking information is included only when enabled. With Include Response Headers enabled, the response body is nested under body with headers and statusCode alongside it. Source bodies were not present in the supplied source pack, so the returned record shape cannot be confirmed from implementation.