Stay organized with collections Save and categorize content based on your preferences.
This page describes the naming convention for Compute Engine resources.
Resources are the fundamental components that make up a Cloud service or product. For example, resources on Compute Engine include but are not limited to:
To learn more about resources, see Global, regional, and zonal resources documentation.
Naming conventionWhen you create a new resource on Compute Engine, you have to provide properties such as a name for the resource.
For resources on Compute Engine, the resource name must meet the following format (unless specified differently in the documentation for creating that resource):
^[a-z]([-a-z0-9]*[a-z0-9])?. This means that the first character must be a lowercase letter, and all the following characters must be hyphens, lowercase letters, or digits, except the last character, which cannot be a hyphen.In general, resource names must be unique within a location within a project. For example, an external IP address name must be unique within the region where it resides. However, you can reuse names across locations.
If the vmDnsSetting setting for the Compute Engine project resource isn't set to ZonalOnly then all VM names must be unique across the project. We strongly recommend using the vmDnsSetting:ZonalOnly setting for your projects, not only so you can reuse VM names across zones and regions, but also because it offers higher reliability by isolating failures in the DNS registration to individual zones. For more information, see Zonal DNS names.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-07 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["This page outlines the naming conventions for Compute Engine resources, which are fundamental components of the cloud service."],["Resource names must be 1-63 characters long, adhere to RFC 1035 conventions, and follow a specific regular expression pattern starting with a lowercase letter and excluding hyphens as the last character."],["Resource names must generally be unique within a location in a project, but they can be reused across different locations."],["When `vmDnsSetting` is not set to `ZonalOnly`, all VM names must be unique across the project, whereas using `ZonalOnly` allows name reuse and provides higher reliability."]]],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4