Stay organized with collections
Save and categorize content based on your preferences.
This page describes the steps to enable and disable Artifact Registry.
If you use Container Registry, you can enable Artifact Registry in the same
project. Each service operates independently.
See Pricing for information about charges for Artifact Registry.
See the Artifact Analysis documentation for information about enabling
Artifact Analysis APIs and pricing for vulnerability scanning.
Enabling service
Sign in to your Google Cloud account. If you're new to
Google Cloud,
create an account to evaluate how our products perform in
real-world scenarios. New customers also get $300 in free credits to
run, test, and deploy workloads.
In the Google Cloud console, on the project selector page,
select or create a Google Cloud project.
Install and initialize Google Cloud CLI if it is not
already installed. For an existing installation, update components of
the Google Cloud CLI with the command:
gcloud components update.
To check your version of the gcloud CLI, run the command:
Before you disable the Artifact Registry API, ensure that any artifacts
that you want to keep are available in another location. It is recommended that
you delete repositories before disabling the API.
When you disable the Artifact Registry API, the following conditions apply:
Repositories and artifacts in repositories become inaccessible.
Data might be deleted within 7 days after the API is disabled.
To disable the API from the Google Cloud console:
console
Go to the API Overview
page for Artifact Registry.
Select the project where the API is enabled.
Click Manage.
Click Disable API.
gcloud
Run the following command to disable the API for your current project:
[[["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-09-03 UTC."],[[["\u003cp\u003eArtifact Registry can be enabled in the same project as Container Registry, with each service functioning independently.\u003c/p\u003e\n"],["\u003cp\u003eEnabling the Artifact Registry API can be done via the Google Cloud console or with the \u003ccode\u003egcloud\u003c/code\u003e command, and requires the gcloud CLI to be installed and up to date.\u003c/p\u003e\n"],["\u003cp\u003eDisabling the Artifact Registry API makes repositories and artifacts inaccessible, and data may be deleted within seven days, thus it is recommended to delete any unneeded repositories beforehand.\u003c/p\u003e\n"],["\u003cp\u003eAfter enabling, you can configure access permissions and authentication for various package types such as Docker, Java, Node.js, and Python.\u003c/p\u003e\n"],["\u003cp\u003eInformation regarding charges for Artifact Registry and vulnerability scanning, can be found in their respective documentation pages on the site.\u003c/p\u003e\n"]]],[],null,["This page describes the steps to enable and disable Artifact Registry.\nIf you use Container Registry, you can enable Artifact Registry in the same project. Each service operates independently.\n\nSee [Pricing](../pricing) for information about charges for Artifact Registry.\n\nSee the Artifact Analysis documentation for information about enabling\n[Artifact Analysis](/artifact-analysis/docs/enabling-disabling-artifact-analysis) APIs and [pricing](/artifact-analysis/pricing) for vulnerability scanning.\n\nEnabling service\n\n- Sign in to your Google Cloud account. If you're new to Google Cloud, [create an account](https://console.cloud.google.com/freetrial) to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.\n- In the Google Cloud console, on the project selector page,\n select or create a Google Cloud project.\n\n | **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n-\n [Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n- In the Google Cloud console, on the project selector page,\n select or create a Google Cloud project.\n\n | **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n-\n [Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n1. Install and initialize [Google Cloud CLI](/sdk/docs) if it is not already installed. For an existing installation, update components of the Google Cloud CLI with the command: `gcloud components update`.\n\n To check your version of the gcloud CLI, run the command: \n\n ```\n gcloud version\n ```\n | **Note:** On Ubuntu, use the [Debian package](/sdk/docs/install#deb) to install gcloud CLI. The gcloud CLI snap package does not include `kubectl` or extensions to authenticate with Artifact Registry using the gcloud CLI.\n2. Enable the API from [Google Cloud console](https://console.cloud.google.com/flows/enableapi?apiid=artifactregistry.googleapis.com) or with the following `gcloud` command: \n\n ```\n gcloud services enable artifactregistry.googleapis.com\n ```\n\nDisabling service\n\nBefore you disable the Artifact Registry API, ensure that any artifacts\nthat you want to keep are available in another location. It is recommended that\nyou [delete](/artifact-registry/docs/repositories/delete-repos) repositories before disabling the API.\n\nWhen you disable the Artifact Registry API, the following conditions apply:\n\n- Repositories and artifacts in repositories become inaccessible.\n- Data might be deleted within 7 days after the API is disabled.\n\nTo disable the API from the Google Cloud console: \n\nconsole\n\n1. Go to the [API Overview](https://console.cloud.google.com/apis/library/artifactregistry.googleapis.com) page for Artifact Registry.\n2. Select the project where the API is enabled.\n3. Click **Manage**.\n4. Click **Disable API**.\n\ngcloud\n\nRun the following command to disable the API for your current project: \n\n gcloud services disable artifactregistry.googleapis.com\n\nWhat's next\n\n- Configure [access permissions](/artifact-registry/docs/access-control) for repositories\n- Configure authentication to repositories:\n - [Docker](/artifact-registry/docs/docker/authentication)\n - [Java](/artifact-registry/docs/java/authentication)\n - [Node.js](/artifact-registry/docs/nodejs/authentication)\n - [Python](/artifact-registry/docs/python/authentication)"]]
