Compare
Amazon Web Services vs Google Cloud: cloud comparison
Updated: · Comparison generated from structured data
Direct answer
Choosing between Amazon Web Services and Google Cloud depends first on location, required services and GPU access. 3 documented capabilities are only available on Amazon Web Services and 0 only on Google Cloud. Measured performance is covered on the benchmark pages.
Executive summary
Amazon Web Services and Google Cloud document 25 and 22 of the same 26 criteria respectively, with 22 capabilities in common. Amazon Web Services bills per-second and Google Cloud bills per-second. Amazon Web Services has a Local Zone in Türkiye; Google Cloud has an announced Türkiye region. Amazon Web Services offers H100, H200, L40S; Google Cloud offers H100, H200.
Key findings
- 01 Capabilities documented only by Amazon Web Services: S3-compatible object storage, Infrastructure located in Türkiye, NVIDIA L40S instances.
- 02 Capabilities documented only by Google Cloud: none.
Overview
| Amazon Web Services | Google Cloud | |
|---|---|---|
| Headquarters | Seattle, United States | Mountain View, United States |
| Operator | Amazon Web Services, Inc. | Google LLC |
| Regions | Global regions; in Türkiye an Istanbul Local Zone (GA May 2026) with a subset of services, parented to Europe (Frankfurt). | Global regions; a Türkiye region has been announced (with Turkcell) but is not yet open. |
| 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 second — Compute Engine VMs are billed per second with a one-minute minimum; sustained- and committed-use discounts apply to eligible machine types. |
| Documented capabilities | 25 / 26 | 22 / 26 |
| Technologies | Nitro System, S3 API, CloudFormation, Terraform | Kubernetes (GKE), Terraform, Cloud Storage XML API |
Availability and regions
Amazon Web Services
- Europe (Frankfurt) eu-central-1 Generally available
- Istanbul Local Zone istanbul-local-zone Generally available
Google Cloud
- Frankfurt europe-west3 Generally available
- Türkiye (announced) turkiye-announced Coming soon
Features
| Criterion | AWS | Google Cloud |
|---|---|---|
| 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. | Planned Announced November 2025; not yet open. |
| 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). | Yes Per-second with a one-minute minimum. |
| Dedicated / single-tenant resources Dedicated hosts, bare metal or organisation-dedicated cloud capacity. | Yes Dedicated Hosts and bare-metal instances. | Yes Sole-tenant nodes. |
| NVIDIA H100 instances On-demand or reservable instances with NVIDIA H100 GPUs. | Yes | Yes |
| NVIDIA H200 instances On-demand or reservable instances with NVIDIA H200 GPUs. | Yes | Yes |
| 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 | Yes |
| Kubernetes node autoscaling Worker node count scales automatically within configured limits. | Yes | Yes |
| Kubernetes LoadBalancer integration Services of type LoadBalancer provision a provider load balancer automatically. | Yes | Yes |
| Kubernetes storage classes (CSI) Persistent volumes provisioned dynamically through a provider storage class. | Yes | Yes |
| Storage & data | ||
| Block storage volumes Persistent, attachable and expandable block volumes. | Yes | Yes |
| Volume snapshots Point-in-time snapshots of block volumes. | Yes | Yes |
| S3-compatible object storage Object storage reachable through the S3 API or an S3-compatible API. | Yes Native S3. | Partial XML API interoperability with HMAC keys; not full S3 API parity. |
| Managed backup service Scheduled backup and restore for instances or volumes managed by the provider. | Yes | Yes |
| Managed database Provider-operated relational database service. | Yes | Yes |
| Networking | ||
| L4 load balancer (TCP/UDP) Transport-layer load balancing. | Yes | Yes |
| 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 Static external IP addresses. |
| 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. | Yes Cloud Router and Cloud NAT. |
| Security groups / cloud firewall Stateful, API-managed network access rules. | Yes | Yes VPC firewall rules and policies. |
| Security & auditing | ||
| Control-plane audit logging A provider service that records management (API/console) operations against cloud resources. | Yes AWS CloudTrail. | Yes Cloud Audit Logs. |
| User identity attribution in audit events Each audit event identifies the authenticated principal that performed the operation. | Yes | Yes |
Pricing and GPUs
| Provider | NVIDIA H100 | NVIDIA H200 | NVIDIA 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 |
| Google Cloud | Generally available A3 High / A3 Mega Up to 8 H100 GPUs per VM; zone availability varies. | Generally available A3 Ultra 8 H200 GPUs per VM; zone availability varies. | Not offered | Announced |
Prices are shown in the currency each provider publishes; no exchange-rate conversion is applied.
Benchmarks
Sources
- [1] Now Open — AWS Local Zones in Istanbul, Türkiye — AWS Official documentation accessed:
- [2] Introducing three new NVIDIA GPU-based Amazon EC2 instances (P5e, G6, G6e) — AWS Official documentation accessed:
- [3] Amazon EC2 On-Demand Pricing — AWS Official documentation accessed:
- [4] AWS CloudTrail User Guide — AWS Official documentation accessed:
- [5] New Google Cloud region coming to Türkiye — Google Cloud Official documentation accessed:
- [6] GPU locations — Compute Engine — Google Cloud Official documentation accessed:
- [7] Cloud Audit Logs overview — Google Cloud Official documentation accessed:
Related research
Provider discovery
AWS alternatives with infrastructure in Türkiye
AWS, PortvMind Cloud, Google Cloud, Azure and the other tracked providers when a workload needs an AWS alternative in Türkiye.
Cloud security & auditing
AWS CloudTrail alternatives: audit logging on other clouds and OpenStack
CloudTrail's equivalents on Google Cloud, Azure, OpenStack-based clouds and smaller providers, compared on scope, identity, retention, export and integrity.
GPU & AI infrastructure
Best GPU for LLM inference: matching H100, H200 and L40S to model size
Which GPU to use for LLM inference by model size, precision, context length and concurrency — a sizing guide for Qwen, Llama, DeepSeek and MiniMax.
Cloud security & auditing
Cloud activity monitoring: how audit logs, alerts and metrics fit together
The difference between cloud audit logging, activity monitoring and performance monitoring, and how to build alerts on audit events across providers.