Compute Engine resources are hosted in multiple locations worldwide.These locations are composed of regions and zones.

Regions are independent geographic areas that consist ofzones. Zones and regions arelogical abstractions of underlying physical resources. For more information aboutregion-specific considerations, seeGeography and regions.

Resources that live in a zone, such asCompute Engine instances or zonaldisks, are referred to as zonal resources.Other resources, likestatic external IP addresses,are regional. Regional resources can be used by any resource in that region,regardless of zone, while zonal resources can only be used by other resources inthe same zone. For example, to attach a zonal persistent disk to an instance,both resources must be in the same zone. Similarly, if you want to assign astatic IP address to an instance, the instance must be in the same region asthe static IP address.

Putting resources in different zones in a region reduces the risk of aninfrastructure outage affecting all resources simultaneously.Putting resources in different regions provides an even higher degree of failureindependence. This lets you design robust systems with resources spreadacross different failure domains.

Only certain resources are region- or zone-specific. Other resources, such asimages, are global resources that can be used by any other resources across anylocation. For information on global, regional, and zonal Compute Engineresources, seeGlobal, Regional, and Zonal Resources.

Google Cloud also offers specialized AI zones that provide high-capacity GPUsand TPUs for AI and ML workloads. These zones have unique characteristics,including specific network latency requirements and shared fate with a parentzone. For more information, seeAI zones.

Identifying a region or zone

Each region in Compute Engine contains a number of zones. Each zone namecontains two parts that describe each zone in detail. The first part of the zonename is theregion and the second part of the name describes thezone inthe region:

• Region

  Regions are collections of zones. Zones have high-bandwidth,low-latency network connections to other zones in the same region. In orderto deploy fault-tolerant applications that have high availability, Googlerecommends deploying applications across multiple zones and multiple regions.This helps protect against unexpected failures of components, up to andincluding a single zone or region.

  Choose regions that make sense for your scenario. For example, if youonly have customers in the US, or if you have specific needs that requireyour data to live in the US, it makes sense to store your resources inzones in theus-central1 region or zones in theus-east1 region.

• Zone

  Azone is a deployment area within a region. Zones whichare specialized for AI and ML workloads are called AI zones. Non-AI zonesare referred to asstandard zones or justzones.Depending on how widely you want to distribute your resources, createcompute instances across multiple zones in multiple regions for redundancy.

  • Standard zone

    A standard zone name contains two parts: theregion and thezone in the region. For example, the fully qualified name for zonea in regionus-central1 isus-central1-a.

  • AI zone

    AI zones follow an extended naming convention to differentiate them fromnon-AI zones. For an AI zone, the<zone> variable consists of threeparts: the string ai (to identify it as an AI zone), a number (indicatingits deployment group), and a letter (indicating the shared software updateschedule). For example, the fully qualified name for AI zoneai2b inregionus-west4 isus-west4-ai2b. This AI zone shares its deploymentrollout wave with the standardus-west4-b zone.

Resource quotas

Certain resources, such as static IPs, images, firewall rules, and VPC networks,have defined project-wide quota limits and per-region quota limits. When youcreate these resources, it counts towards your total project-wide quota or yourper-region quota, if applicable. If any of the affected quota limits areexceeded, you won't be able to add more resources of the same type in thatproject or region.

To see a comprehensive list of quotas that apply to your project, visit theQuotas page in the Google Cloud console.

For example, if your global target pools quota is 50 and you create 25 targetpools in example-region-1 and 25 target pools in example-region-2, you reachyour project-wide quota and won't be able to create more target pools in anyregion within your project until you free up space. Similarly, if you have aper-region quota of 7 reserved IP addresses, you can only reserve up to 7 IPaddresses in a single region. After you reach that limit, you will either needto reserve IP addresses in a new region or release some IP addresses.

Transparent maintenance

Google regularly maintains its infrastructure by patching systems with thelatest software, performing routine tests and preventative maintenance, andgenerally ensuring that Google infrastructure is as fast and efficient as Googleknows how to make it.

By default, all compute instances are configured so that these maintenanceevents are transparent to your applications and workloads. Google uses acombination of datacenter innovations, operational best practices, and livemigration technology to move running virtual machine instances out of the way ofmaintenance that is being performed. Your instance continues to run within thesame zone with no action on your part.

By default, most virtual machines are set to live migrate, but you can also setyour virtual machines to stop and reboot. Some machine series support onlystop and reboot for maintenance operations. The two options differ in thefollowing ways:

• Live migrate

  Compute Engine automatically migrates your running instance. Themigration process will impact guest performance to some degree but yourinstance remains online throughout the migration process. The exact guestperformance impact and duration depends on many factors, but it is expectedmost applications and workloads will not notice. For more information,seeLive Migration.

• Stop and reboot

  Compute Engine automatically signals your instance to shut down,waits a short time for it to shut down cleanly, and then restarts it awayfrom the maintenance event.

For more information on how to set the options above for your instances, seeSet VM host maintenance policy.

Choosing a region and zone

You choose which region or zone hosts your resources, which controls where yourdata is stored and used. Choosing a region and zone is important for severalreasons:

Handling failures

Distribute your resources across multiple zones and regionsto tolerate outages. Google designs zones to minimize the risk of correlatedfailures caused by physical infrastructure outages like power, cooling, ornetworking. Thus, if a zone becomes unavailable, you can transfer traffic toanother zone in the same region to keep your services running. Similarly, youcan mitigate the impact of a region outage on your application by runningbackup services in a different region. For more information about distributingyour resources and designing a robust system, seeDesigning resilient systems.

Decreased network latency

To decrease network latency, you might want to choose a region or zone that isclose to your point of service. For example, if you mostly have customers onthe East coast of the United States of America, then you might want to choosea primary region and zone that is close to that area and a backup region andzone that is also close by.

Optimized AI and ML acceleration

For workloads that require high-capacity AI accelerators, AI zones areavailable in select regions. These specialized zones provide GPU andTPU resources for AI and ML training and inference. You can selectan AI zone to use infrastructure that is optimized for maximizing AI andML throughput. See theAI zonessection for details.

For more information about how to choose a region and zone for yourCompute Engine resources, seeBest practices for Compute Engine regions selection.

Location selection tips

During compute instance creation, Compute Engine canautomatically select zones for your instances based on capacity andavailability using the following methods:

• Thebulk instance creation APIcan automatically choose the zone in which to create instances.
• A regional managed instance group (MIG) can be configured with atarget distribution shape,which can automatically create instances in zones where resources areavailable.
• If you are creating an instance in the Google Cloud console and you know themachine type and region that you want but you aren't sure which zone toselect, you can selectAny and Google will choose a zone for you based onthe machine type and availability.

When selecting zones yourself, here are some things to keep in mind:

• Communication within and across regions will incur different costs.

  Generally, communication within regions will always be cheaper and fasterthan communication across different regions.

• Design important systems with redundancy across multiple zones or regions.

  At some point in time, your instances might experiencean unexpected failure. To mitigate the effects of these possible events,you should duplicate important systems in multiple zones and regions.

  For example, by hosting instances in zoneseurope-west1-b andeurope-west1-c, ifeurope-west1-b fails unexpectedly, your instancesin zoneeurope-west1-c will still be available. However, if you hostall your instances ineurope-west1-b, you will not be able toaccess any instances ifeurope-west1-b goes offline. Also, considerhosting your resources across regions. For example, to plan for continuedavailability of your workload in the unlikely scenario that theeurope-west1 region experiences a failure, consider deploying the workloadon backup instances in theeurope-west3 region. For more tips on how todesign systems for availability, seeDesigning resilient systems.

Available regions and zones

You can use the Google Cloud console, the Google Cloud CLI, or REST tosee available regions and zones.You can also get the complete list of available machine types in all regions andzones by using thegcloud compute machine-types list command.For example, running the following command displays all the regions and zoneswhere you can usec4d-standard-4 machine types.

gcloud compute machine-types list --filter="name=c4d-standard-4"

Each zone offers a variety of processors. When you create aninstance in a zone, your instance uses the default processor supported in thatzone. For example, if you create an instance in theus-central1-a zone, yourinstance by default uses an Intel Haswell processor, unless you specify anotheroption.

Alternatively, you can choose your desired CPU platform. For more information,readSpecifying a minimum CPU platform for VM instances.

Consider the following information about resource availability before youselect the regions and zones where you create your instances:

• Local SSD disks are available in all regionsand zones.
• GPUs andTPUs are available only inspecific zones.
• Sole-tenancy is available in regionsand zones where machine series withsole-tenant node typesare available.
• Confidential VMis available only with certain machine series in specific zones.

For information about hardware and feature support for all machine series, seeMachine series comparison.For example, to see which machine series support both Intel TDX and soletenancy, in theChoose instance properties to compare field, select bothConfidential Computing andSole tenancy.

Zones	Location	Machine types	CPUs	Options	CO2 emissions
africa-south1-a	Johannesburg, South Africa	E2, N4, N2 , N2D, C4 , C4A, T2D	Intel Cascade Lake, Ice Lake, Emerald Rapids, AMD EPYC Rome, AMD EPYC Milan, Google Axion	Intel TDX
asia-northeast1-c	Tokyo, Japan, APAC	E2, N4, N2 , N2D, N1, C4 , C4A, C4D, C3 , T2D, Z3, M1, C2 , A2, G2, A3	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Turin, Google Axion	GPUs, Intel TDX
asia-south1-c	Mumbai, India, APAC	E2, N4, N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, Z3, X4, M4, M3, M1, C2 , C2D, A3, G2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Google Axion	GPUs, AMD SEV-SNP, Intel TDX
asia-southeast1-b	Jurong West, Singapore, APAC	E2, N4 , N4A, N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, C2 , C2D, T2D, T2A, Z3, M4, M3, M2, M1, A4 , A2, A3, G4, G2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Ampere Altra Arm, Google Axion	GPUs, AMD SEV-SNP, Intel TDX
asia-southeast1-c	Jurong West, Singapore, APAC	E2, N4 , N4A, N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, T2A, Z3, M1, C2 , C2D, A2, A3, G4, G2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Ampere Altra Arm, Google Axion	GPUs, AMD SEV-SNP, Intel TDX
asia-southeast2-a	Jakarta, Indonesia, APAC	E2, N4 , N2 , N2D, N1, C4 , C3 , T2D, M1	Intel Ivy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, AMD EPYC Rome, AMD EPYC Milan	GPUs, AMD SEV-SNP
europe-west3-b	Frankfurt, Germany, Europe	E2, N4 , N4A, N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, X4, M4, M3, M2, M1, C2 , C2D, G2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Google Axion	GPUs, AMD SEV-SNP
europe-west3-c	Frankfurt, Germany, Europe	E2, N4 , N4A, N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, Z3, M3, M1, C2 , C2D	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Google Axion	AMD SEV-SNP
europe-west4-a	Eemshaven, Netherlands, Europe	E2, N4 , N4A, N4D, N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, T2A, Z3, M4, M3, M2, M1, C2 , C2D, A3, A2, G4, G2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Ampere Altra Arm, Google Axion	GPUs, AMD SEV-SNP, Intel TDX	Low CO2
europe-west4-b	Eemshaven, Netherlands, Europe	E2, N4 , N4A, N4D, N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, T2A, Z3, X4, M4, M3, M2, M1, H4D, H3, C2 , C2D, A4 , A3, A2, G4, G2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Ampere Altra Arm, Google Axion	GPUs, AMD SEV-SNP, Intel TDX	Low CO2
europe-west4-c	Eemshaven, Netherlands, Europe	E2, N4 , N4A, N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, T2A, Z3, X4, M2, M1, H3, C2 , C2D, A3, G2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Ampere Altra Arm, Google Axion	GPUs, AMD SEV-SNP, Intel TDX, NVIDIA Confidential Computing	Low CO2
europe-west6-a	Zurich, Switzerland, Europe	E2, N2 , N1, C2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake		Low CO2
europe-west6-b	Zurich, Switzerland, Europe	E2, N4, N2 , N2D, N1, C4 , T2D, M1, C2 , G2, Z3	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, AMD EPYC Rome, AMD EPYC Milan	GPUs, Intel TDX	Low CO2
europe-west9-b	Paris, France, Europe	E2, N4, N2 , N2D, C4 , C3 , T2D, M3, M1	Intel Broadwell, Haswell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, AMD EPYC Rome, AMD EPYC Milan	Intel TDX	Low CO2
europe-west9-c	Paris, France, Europe	E2, N4 , N2 , N2D, C4 , C3  T2D, M1, A3	Intel Broadwell, Haswell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, AMD EPYC Rome, AMD EPYC Milan	AMD SEV-SNP, Intel TDX, NVIDIA Confidential Computing	Low CO2
us-central1-b	Council Bluffs, Iowa, North America	E2, N4 , N4D, N4A, N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, T2A, M4, M3, M2, M1, C2 , C2D, A4X Max, A4 , A3, A2, G4, G2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Ampere Altra Arm, Google Axion, NVIDIA Grace	GPUs, AMD SEV-SNP, Intel TDX	Low CO2
us-central1-c	Council Bluffs, Iowa, North America	E2, N4 , N4D, N4A, N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, Z3, X4, M4, M3, M2, M1, C2 , C2D, A3, A2, G2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Google Axion	GPUs, AMD SEV-SNP, Intel TDX	Low CO2
us-central1-f	Council Bluffs, Iowa, North America	E2, N4 , N4A, N2 , N2D, N1, C4 , C4A, C3 , C3D, T2D, T2A, Z3, M1, C2 , C2D, A2, G4	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Ampere Altra Arm, Google Axion	GPUs, Intel TDX
us-east1-d	Moncks Corner, South Carolina, North America	E2, N4 , N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, Z3, M3, M1, C2 , C2D, G2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Google Axion	GPUs, Intel TDX
us-east4-a	Ashburn, Virginia, North America	E2, N4 , N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, Z3, X4, M4, M3, M2, M1, C2 , C2D, A3, G2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Google Axion	GPUs, Intel TDX
us-east4-b	Ashburn, Virginia, North America	E2, N4, N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, Z3, M4, M3, M2, M1, C2 , C2D, A4X Max, A4 , A3	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Google Axion, NVIDIA Grace	GPUs, Intel TDX
us-east5-a	Columbus, Ohio, North America	E2, N4 , N2 , N2D, C4 , C4A, C3 , T2D, Z3, M4, C2 , A3, G4	Intel Broadwell, Haswell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Turin, Google Axion	GPUs, NVIDIA Confidential Computing
us-east5-b	Columbus, Ohio, North America	E2, N4, N2 , N2D, C4 , C4A, C3 , C3D, T2D, Z3, M4, C2 , G4	Intel Broadwell, Haswell, Skylake, Cascade Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Google Axion	GPUs, Intel TDX
us-east5-c	Columbus, Ohio, North America	E2, N4, N2 , N2D, C4 , C3 , T2D, Z3, C2 , G4	Intel Broadwell, Haswell, Skylake, Cascade Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Turin	GPUs, Intel TDX
us-south1-a	Dallas, Texas, North America	E2, N4, N2 , N2D, C4 , C4A, C3 , T2D, G4	Intel Broadwell, Haswell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Turin, Google Axion	GPUs, Intel TDX	Low CO2
us-west1-b	The Dalles, Oregon, North America	E2, N4 , N4D, N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, Z3, C2 , C2D, M4, M3, M1, A3, G4, G2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Google Axion	GPUs, Intel TDX	Low CO2
us-west1-c	The Dalles, Oregon, North America	E2, N4 , N4A, N4D, N2 , N2D, N1, C4 , C4A, T2D, C3 , C2 , C2D, G4, G2, A3	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Turin, Google Axion	GPUs, AMD SEV	Low CO2
us-west2-a	Los Angeles, California, North America	E2, N2 , N2D, N1, C4 , C4A, C3 , C3D, T2D, C2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, Google Axion	AMD SEV
us-west2-b	Los Angeles, California, North America	E2, N2 , N2D, N1, C4A, C3 , T2D, M1, C2	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, AMD EPYC Rome, AMD EPYC Milan, Google Axion	GPUs, AMD SEV
us-west2-c	Los Angeles, California, North America	E2, N4, N2 , N2D, N1, C4 , C4A, C3 , M1, C2 , A4	Intel Ivy Bridge, Sandy Bridge, Haswell, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, Google Axion	GPUs, AMD SEV
us-west3-a	Salt Lake City, Utah, North America	E2, N4, N2 , N2D, N1, C4 , C3 , T2D, C2 , M3, G4	Intel Ivy Bridge, Sandy Bridge, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Turin	GPUs, AMD SEV
us-west3-b	Salt Lake City, Utah, North America	E2, N4, N2 , N2D, N1, C4 , C3 , T2D, C2 , A4 , A2	Intel Ivy Bridge, Sandy Bridge, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan	GPUs, AMD SEV
us-west3-c	Salt Lake City, Utah, North America	E2, N4, N2 , N2D, N1, C4 , C3 , T2D, C2 , A4	Intel Ivy Bridge, Sandy Bridge, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, AMD EPYC Rome, AMD EPYC Milan	GPUs, AMD SEV
us-west4-a	Las Vegas, Nevada, North America	E2, N4 , N4D, N2 , N2D, N1, C4 , C4A, C4D, C3 , C3D, T2D, C2 , C2D, X4, M3, M2, M1, A3, G4, G2	Intel Ivy Bridge, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Genoa, AMD EPYC Turin, Google Axion	GPUs, AMD SEV
us-west4-b	Las Vegas, Nevada, North America	E2, N4 , N4D, N2 , N2D, N1, C4 , C4A, C4D, C3 , T2D, C2 , C2D, X4, M3, M2, M1, A2	Intel Ivy Bridge, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Turin, Google Axion	GPUs, AMD SEV
us-west4-c	Las Vegas, Nevada, North America	E2, N4 , N4D, N2 , N2D, N1, C4A, C4 , C3 , T2D, C2 , C2D, G2	Intel Ivy Bridge, Broadwell, Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, AMD EPYC Rome, AMD EPYC Milan, AMD EPYC Turin, Google Axion	GPUs, AMD SEV

What's next

• Learn more aboutgeography and regions.
• Learn how toview available regions and zones.
• Learn how tochange your default zone or region.
• Learn more about theglobal, regional, and zonal resources.