Skip to content
Cloud Provider Benchmarks

Compare

Amazon Web Services vs Hetzner: services, regions and GPUs

Updated: · Comparison generated from structured data

Direct answer

Choosing between Amazon Web Services and Hetzner depends first on location, required services and GPU access. 15 documented capabilities are only available on Amazon Web Services and 0 only on Hetzner. Measured performance is covered on the benchmark pages.

Executive summary

Amazon Web Services and Hetzner document 25 and 10 of the same 26 criteria respectively, with 10 capabilities in common. Amazon Web Services bills per-second and Hetzner bills per-hour. Amazon Web Services has a Local Zone in Türkiye; Hetzner has no infrastructure in Türkiye. Amazon Web Services offers H100, H200, L40S; Hetzner offers none of H100/H200/L40S.

Key findings

  1. 01 Capabilities documented only by Amazon Web Services: Per-second or per-minute billing, Managed Kubernetes, Kubernetes node autoscaling, Kubernetes LoadBalancer integration, Kubernetes storage classes (CSI), Volume snapshots, Managed database, L4 load balancer (TCP/UDP), Virtual router with NAT, Control-plane audit logging, User identity attribution in audit events, Infrastructure located in Türkiye, NVIDIA H100 instances, NVIDIA H200 instances, NVIDIA L40S instances.
  2. 02 Capabilities documented only by Hetzner: none.

Overview

Overview
Amazon Web ServicesHetzner
Headquarters Seattle, United StatesGunzenhausen, Germany
Operator Amazon Web Services, Inc.Hetzner Online GmbH
Regions Global regions; in Türkiye an Istanbul Local Zone (GA May 2026) with a subset of services, parented to Europe (Frankfurt).Cloud locations in Germany (Falkenstein, Nuremberg), Finland (Helsinki), the United States and Singapore; none in Türkiye.
Billing model Per second — On-demand Linux EC2 instances are billed per second with a 60-second minimum; other operating systems and services have their own meters.Per hour — Cloud servers are billed per started hour up to a monthly price cap. Object Storage has an hourly base price with included storage and egress quotas.
Documented capabilities 25 / 26 10 / 26
Technologies Nitro System, S3 API, CloudFormation, Terraformhcloud API, Terraform (hcloud provider), Kubernetes CCM/CSI, S3 API

Availability and regions

Amazon Web Services

  • Europe (Frankfurt) eu-central-1 Generally available
  • Istanbul Local Zone istanbul-local-zone Generally available

Hetzner

  • Falkenstein fsn1 Generally available
  • Nuremberg nbg1 Generally available
  • Helsinki hel1 Generally available

Features

Documented capabilities against the same criteria
Criterion AWS Hetzner
Data residency
Infrastructure located in Türkiye Generally available compute and storage capacity physically located in Türkiye (full region or local zone). Yes Istanbul Local Zone with a subset of services (GA May 2026); not a full region. No
Compute & GPU
Virtual machine instances Self-service virtual machines with selectable CPU/RAM profiles. Yes Yes
Per-second or per-minute billing Standard compute billed at per-second or per-minute granularity rather than per started hour. Yes Per-second for Linux on-demand (60 s minimum). No Per started hour with a monthly cap.
Dedicated / single-tenant resources Dedicated hosts, bare metal or organisation-dedicated cloud capacity. Yes Dedicated Hosts and bare-metal instances. Yes Dedicated root servers.
NVIDIA H100 instances On-demand or reservable instances with NVIDIA H100 GPUs. Yes No
NVIDIA H200 instances On-demand or reservable instances with NVIDIA H200 GPUs. Yes No
NVIDIA L40S instances On-demand or reservable instances with NVIDIA L40S GPUs. Yes No
Platform & automation
API and Terraform automation Documented API plus an available Terraform provider for infrastructure as code. Yes Yes
Open-source cloud stack (OpenStack-based) The provider publicly states that its IaaS control plane is built on OpenStack or an equivalent open-source stack. No No
Kubernetes
Managed Kubernetes Provider-operated Kubernetes control plane. Yes No CCM and CSI driver for self-managed clusters only.
Kubernetes node autoscaling Worker node count scales automatically within configured limits. Yes Partial Through the upstream cluster autoscaler on self-managed clusters.
Kubernetes LoadBalancer integration Services of type LoadBalancer provision a provider load balancer automatically. Yes Partial Via the Hetzner cloud-controller-manager on self-managed clusters.
Kubernetes storage classes (CSI) Persistent volumes provisioned dynamically through a provider storage class. Yes Partial Via the Hetzner CSI driver on self-managed clusters.
Storage & data
Block storage volumes Persistent, attachable and expandable block volumes. Yes Yes
Volume snapshots Point-in-time snapshots of block volumes. Yes No Server snapshots only; no volume snapshots.
S3-compatible object storage Object storage reachable through the S3 API or an S3-compatible API. Yes Native S3. Yes EU locations; partial S3 API coverage.
Managed backup service Scheduled backup and restore for instances or volumes managed by the provider. Yes Yes Server backups.
Managed database Provider-operated relational database service. Yes No
Networking
L4 load balancer (TCP/UDP) Transport-layer load balancing. Yes Partial TCP only (no UDP).
L7 load balancer (HTTP/HTTPS) Application-layer load balancing with HTTP health checks. Yes Yes
Reassignable static public IP Static public addresses that can be moved between resources (Floating/Reserved/Elastic IP). Yes Elastic IP addresses. Yes
Private networks / VPC Isolated tenant networks with custom CIDR ranges. Yes Yes
Virtual router with NAT Managed router or NAT gateway for egress and inter-subnet routing, including static routes. Yes Route tables and NAT Gateway. No Network routes are supported; NAT requires a self-managed gateway server.
Security groups / cloud firewall Stateful, API-managed network access rules. Yes Yes Stateful firewalls.
Security & auditing
Control-plane audit logging A provider service that records management (API/console) operations against cloud resources. Yes AWS CloudTrail. Unverified
User identity attribution in audit events Each audit event identifies the authenticated principal that performed the operation. Yes Unverified

Pricing and GPUs

GPU availability and published per-GPU-hour list prices by provider
Provider NVIDIA H100NVIDIA H200NVIDIA L40S Türkiye infrastructure
Amazon Web Services Generally available EC2 P5 Single-GPU p5.4xlarge and 8-GPU p5.48xlarge sizes; availability varies by region. Generally available EC2 P5e / P5en 8-GPU instances; availability varies by region. Generally available EC2 G6e 1 to 8 L40S GPUs per instance. Yes
Hetzner Not offered Not offered Not offered No

Prices are shown in the currency each provider publishes; no exchange-rate conversion is applied.

Benchmarks

Sources

  1. [1] Now Open — AWS Local Zones in Istanbul, Türkiye — AWS Official documentation accessed:
  2. [2] Introducing three new NVIDIA GPU-based Amazon EC2 instances (P5e, G6, G6e) — AWS Official documentation accessed:
  3. [3] Amazon EC2 On-Demand Pricing — AWS Official documentation accessed:
  4. [4] AWS CloudTrail User Guide — AWS Official documentation accessed:
  5. [5] Hetzner Cloud — Hetzner Official documentation accessed:
  6. [6] Object Storage overview (Hetzner Docs) — Hetzner Official documentation accessed:
  7. [7] Dedicated servers with GPU (GEX) — Hetzner Official documentation accessed:
  8. [8] Hetzner Cloud Review 2026 — C9 Group Secondary source accessed: