정규 표현식 ^[a-z]([-a-z0-9]*[a-z0-9])?와 일치해야 합니다. 즉, 첫 문자는 소문자이고 그 다음에 오는 모든 문자는 하이픈, 소문자, 숫자여야 합니다. 단, 마지막 문자에는 하이픈을 사용할 수 없습니다.
이름 고유성
일반적으로 리소스 이름은 리소스가 위치하는 프로젝트 내에서 고유해야 합니다.
예를 들어 외부 IP 주소 이름은 외부 IP 주소가 위치하는 리전 내에서 고유해야 합니다. 그러나 여러 위치에서 이름을 재사용할 수 있습니다.
Compute Engine 프로젝트 리소스의 vmDnsSetting 설정이 ZonalOnly로 설정되지 않은 경우 모든 VM 이름은 프로젝트 전체에서 고유해야 합니다. 프로젝트에 vmDnsSetting:ZonalOnly 설정을 사용하는 것이 좋습니다. 영역 및 리전 간에 VM 이름을 재사용할 수 있을 뿐만 아니라 DNS 등록 장애를 개별 영역으로 격리하여 더 높은 안정성을 제공하기 때문입니다. 자세한 내용은 영역 DNS 이름을 참조하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eThis page outlines the naming conventions for Compute Engine resources, which are fundamental components of the cloud service.\u003c/p\u003e\n"],["\u003cp\u003eResource 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.\u003c/p\u003e\n"],["\u003cp\u003eResource names must generally be unique within a location in a project, but they can be reused across different locations.\u003c/p\u003e\n"],["\u003cp\u003eWhen \u003ccode\u003evmDnsSetting\u003c/code\u003e is not set to \u003ccode\u003eZonalOnly\u003c/code\u003e, all VM names must be unique across the project, whereas using \u003ccode\u003eZonalOnly\u003c/code\u003e allows name reuse and provides higher reliability.\u003c/p\u003e\n"]]],[],null,["*** ** * ** ***\n\nThis page describes the naming convention for Compute Engine resources.\n\nResources are the fundamental components that make up a Cloud service or\nproduct. For example, resources on Compute Engine include but are not\nlimited to:\n\n- [Disks](/compute/docs/disks) and [disk snapshots](/compute/docs/disks/create-snapshots)\n- [Images and image families](/compute/docs/images)\n- [Instance templates](/compute/docs/instance-templates)\n- [Instance groups](/compute/docs/instance-groups)\n- [Machine images](/compute/docs/machine-images)\n- [Node groups](/compute/docs/nodes) and [node templates](/compute/docs/nodes)\n- [Compute Engine instances](/compute/docs/instances)\n\nTo learn\nmore about resources, see\n[Global, regional, and zonal resources documentation](/compute/docs/regions-zones/global-regional-zonal-resources).\n\nNaming convention\n\nWhen you create a new resource on Compute Engine, you have to provide\nproperties such as a name for the resource.\n\nFor resources on Compute Engine, the resource\nname must meet the following format (unless specified differently in the\ndocumentation for creating that resource):\n\n- Be 1-63 characters in length.\n- Comply with [RFC 1035](https://www.ietf.org/rfc/rfc1035.txt) conventions.\n- Match the regular expression `^[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.\n\nName uniqueness\n\nIn general, resource names must be unique within a location within a project.\nFor example, an external IP address name must be unique within the region where\nit resides. However, you can reuse names across locations.\n\nIf the `vmDnsSetting` setting for the Compute Engine project resource isn't\nset to `ZonalOnly` then all VM names must be unique across the project. We\n*strongly recommend* using the `vmDnsSetting:ZonalOnly` setting for your\nprojects, not only so you can reuse VM names across zones and regions, but also\nbecause it offers higher reliability by isolating failures in the DNS\nregistration to individual zones. For more information, see\n[Zonal DNS names](/compute/docs/networking/zonal-dns)."]]
