All pricing

This page lists all the pricing for Compute Engine.

Note: This page is a list
of Compute Engine pricing in a single place for convenience. It is
intended for reference purposes and does not provide detailed pricing
explanations. For explanations on how pricing works, see the following pages:

Compute Engine charges for usage based on the following price sheet. A bill
is sent out at the end of each billing cycle, listing previous usage and
charges. Prices on this page are listed in U.S. dollars (USD).

For Compute Engine, disk size, machine type memory, and network usage
are calculated in gigabytes (GB), where 1 GB is 230 bytes. This unit of measurement is also known as a gibibyte (GiB).

If you pay in a currency other than USD, the prices listed in your currency on
Cloud Platform SKUs apply.

You can also find pricing information with the following options:

See the estimated costs of your instances and Compute Engine
resources when you create them in the Google Cloud Console.

All RHEL and RHEL for SAP images are charged a 1 minute
minimum. After 1 minute, RHEL images are charged in 1 second
increments.

SLES images and SLES for SAP images

SLES images:

$0.02 USD/hour for f1-micro and g1-small machine types

$0.11 USD/hour for all other machine types

SLES for SAP images:

$0.17 USD/hour for instances with 1 - 2 vCPUs

$0.34 USD/hour for instances with 3 - 4 vCPUs

$0.41 USD/hour for instances with 5 or more vCPUs

All SLES images are charged a 1 minute minimum. After 1
minute, SLES images are charged in 1 second increments.

Windows Server images

Public images for several versions of Windows Server are available in either
the Server Core configuration or the Server with Desktop Experience
configuration. Both configurations are available at the following prices:

$0.023 USD/hour for f1-micro and g1-small machine types

$0.046 USD per core/hour for all other machine types

Standard machine types, high-CPU machine types, and high-memory machine types
are charged based on the number of CPUs. For example, n1-standard-4, n1-highcpu-4, and n1-highmem-4 are
machine-types with 4 vCPUs, and are charged at $0.184 USD/hour (4 x $0.046
USD/hour).

SQL Server images

SQL Server images incur costs in addition to the cost for
Windows Server images and the cost for the selected
machine type.

$0.399 USD per core/hour for
SQL Server Enterprise

$0.1645 USD per core/hour for
SQL Server Standard

$0.011 USD per core/hour for
SQL Server Web

No additional charge for SQL Server Express

Microsoft SQL Server licensing requires a core license to be assigned to each
virtual CPU on your virtual machine instance, with a four core minimum for each
instance. Instances with fewer than 4 vCPUs will be charged for SQL Server at 4
x $0.1645 USD/hour ($0.658 USD/hour) to comply with these requirements. For
instances with 4 or more vCPUs, Compute Engine charges you for
Microsoft SQL Server licenses in increments of 2. However, instances with
a custom machine type
will be charged for the number of SQL Server licenses that is equal to the
number of vCPUs.

If you pay in a currency other than USD, the prices listed in your currency on
Cloud Platform SKUs apply.

*These charges are for egress through
internal IP
addresses. There are different
charges for egress through
external IP addresses,
regardless of whether the instances are in the same zone. The prices are
used regardless of network or subnet. The price for traffic within a zone
using internal IP addresses is the same even if
the traffic is to a different subnet or network. The price on traffic
between zones in the same region is the same if the two instances are in
the same subnet, different subnets, or different networks. Pricing is the
same whether the instances are in a VPC network or a legacy network.

† Oceania includes Australia, New Zealand, and
surrounding Pacific Ocean islands such as Papua New Guinea and Fiji. This
region excludes Hawaii.

Internet egress rates*

Note: The monthly usage is counted by each
SKU, while the "Wordwide Destinations" may contain multiple SKUs. For more
information, see Google Cloud
SKUs.

If you pay in a currency other than USD, the prices listed in your currency on
Cloud Platform SKUs apply.

Packet Mirroring

Note: The following pricing will come into effect from
June 20, 2020. There is no charge for Packet Mirroring until that time.

You are charged for the amount of data processed by Packet Mirroring. You
are not charged for packet mirroring forwarding rules. The costs for the data
processed by Packet Mirroring are described in the following table.

Traffic sent between the external IP addresses of two virtual machines in
different regions, not including traffic between US regions, is charged at
Internet Egress
pricing.

It is not possible to charge traffic through the external IP address of two
virtual machine instances in the same zone as Egress to the same zone
because Compute Engine cannot determine the zone of a virtual machine
through the external IP address.

External IP address pricing

You are charged for static and ephemeral external IP addresses according to
the following table.

If you reserve a static external IP address and do not assign it to a
resource such as a VM instance or a forwarding rule, you are charged at a higher
rate than for static and ephemeral external IP addresses that are in use.

In use or not

Google Cloud considers a static external IP address as in use if it is
associated with a VM instance whether the instance is running or stopped. If the
instance is deleted or if the IP address is dissociated from the instance,
Google Cloud considers the static IP address as not in use.

For an ephemeral IP address, Google Cloud considers the address as in
use only when the associated VM instance is running. When the instance is
stopped or deleted, Google Cloud releases the ephemeral IP address and no
longer considers it as in use.

You can check whether a static external IP address is in use by making a
gcloud compute addresses list request. This command returns a list
of static external IP addresses and their statuses:

In this example, IPv4 address-1 is in use
while IPv4 address-2 is reserved but not being used.
Both addresses are charged according to the External IP address pricing
table in this document.

Network Telemetry

Network logs generate charges. You are charged for the following
products:

VPC Flow Logs

Firewall Rules Logging

Cloud NAT logging

Log generation

Price (USD)

0—10 TB per month

0.50/GB

10—30 TB per month

0.25/GB

30—50 TB per month

0.10/GB

>50 TB per month

0.05/GB

Logs are sent to Cloud Logging. Logs can be further exported to Pub/Sub,
Cloud Storage, or BigQuery. Pub/Sub, Cloud Storage, or
BigQuery charges apply in addition to log generation charges. For more information
on exporting logs, see Overview of logs export.

If you store your logs in Cloud Logging, logs generation charges are
waived, and only Logging charges apply.

If you send and then exclude your logs from Cloud Logging, log
generation charges apply.

Load balancing and forwarding rules

The following pricing applies to all types of load balancing other than
Internal HTTP(S) Load Balancing. For Internal HTTP(S) Load Balancing, see the Internal HTTP(S) Load Balancing section.

Forwarding rules pricing examples

You can create up to 5 forwarding rules for the price of $0.025/hour. For
example, if you create one forwarding rule, you are charged $0.025/hour. If you
have 3 forwarding rules, you are still charged $0.025/hour. However, if you have
10 forwarding rules, you are charged as follows:

For most load balancing use cases, you need only one forwarding rule per load
balancer.

Google Cloud charges for global forwarding
rules and regional forwarding
rules separately, and also per project. For example, if you use one global
forwarding and one regional forwarding rule in two separate projects (four rules
total), you are charged $0.10/hour (4 x $0.025/hour).

This example doesn't include the egress cost
of sending replies from the backends.

Internal HTTP(S) Load Balancing

Note: Promotion: Through March 31, 2020,
Internal HTTP(S) Load Balancing is offered without charge to all
customers.

To ensure optimal performance and reliability, each load balancer is
allocated at least one proxy per zone
in the load balancer's GCP region. For example, the us-west1
region has three zones: us-west1-a, us-west1-b, and
us-west1-c. The minimum hourly charge due to proxies in
us-west1 is calculated as follows:

User-defined request headers and Google Cloud Armor charges

If a backend service has a Google Cloud Armor policy associated with it,
you can use the user-defined request headers feature with that backend service
without any additional charge for the user-defined request headers feature.

If a backend service does not have a Google Cloud Armor
policy associated with it, the charges are $0.75 per million HTTP(S) requests
sent to those backend services that use the user-defined request headers
feature.

Protocol forwarding

Protocol forwarding is charged at the same rates as the load balancing service. There is a charge
for a forwarding rule and the ingress data processed by a target instance.

SSL certificates

There is no charge for self-managed and Google-managed SSL certificates.