Stay organized with collections
Save and categorize content based on your preferences.
You must specify a name for every Vertex AI model and
endpoint that you create. The rules
for naming are consistent for both types of resource. Each name:
Must only contain letters, numbers, dashes and underscores.
Is case-sensitive.
Must start with a letter.
Must be no more than 128 characters long.
You should create names that you can distinguish in lists of resources or
identify by the dataset they use, for example:
[[["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-25 UTC."],[],[],null,["# Resource names\n\nYou must specify a name for every Vertex AI model and\nendpoint that you create. The rules\nfor naming are consistent for both types of resource. Each name:\n\n- Must only contain letters, numbers, dashes and underscores.\n- Is case-sensitive.\n- Must start with a letter.\n- Must be no more than 128 characters long.\n\nYou should create names that you can distinguish in lists of resources or\nidentify by the dataset they use, for example:\n\n- \u003cvar translate=\"no\"\u003eUSE_CASE\u003c/var\u003e`-a-v1-model`\n- \u003cvar translate=\"no\"\u003eUSE_CASE\u003c/var\u003e`-a-v1-endpoint`\n- \u003cvar translate=\"no\"\u003eUSE_CASE\u003c/var\u003e`-a-v1-pipeline`\n- \u003cvar translate=\"no\"\u003eOWNER_NAME\u003c/var\u003e`-`\u003cvar translate=\"no\"\u003eUSE_CASE\u003c/var\u003e`-a-v1-model`"]]