本頁面中的部分或全部資訊可能不適用於 Trusted Cloud by S3NS。
配額與限制
本文列出 Artifact Registry 適用的配額和系統限制。
- 配額會指定您可使用的可計數共用資源數量。配額是由 Artifact Registry 等 Trusted Cloud by S3NS 服務定義。
- 系統限制是無法變更的固定值。
Trusted Cloud by S3NS 會使用配額來確保公平性，並減少資源使用量和可用性暴增的情況。配額會限制專案可使用的Trusted Cloud 資源 Trusted Cloud 數量。配額適用於各種資源類型，包括硬體、軟體和網路元件。舉例來說，配額可以限制對服務發出的 API 呼叫數、專案並行使用的負載平衡器數量，或是可建立的專案數量。配額可以預防服務過載，進而保障Trusted Cloud 使用者社群的權益。配額也能協助您管理自己的 Trusted Cloud 資源。
Cloud Quotas 系統會執行下列操作：
在大多數情況下，如果您嘗試使用的資源超過配額，系統會封鎖資源存取權，導致您嘗試執行的工作失敗。
配額通常是在 Trusted Cloud 專案
層級套用。在一個專案中使用資源，不會影響另一個專案的可用配額。在 Trusted Cloud 專案中，所有應用程式和 IP 位址會共用配額。
Artifact Registry 資源也有系統限制。
系統限制無法變更。
Artifact Registry 對傳入要求的頻率設有上限，並會以專案和使用者為單位限定配額。
如需有關配額政策、查看配額及管理配額的資訊，請參閱使用配額一文。
請前往 API 資訊主頁，瞭解您目前的 API 活動。
配額
Artifact Registry 會強制執行下列配額。
每項專案的要求配額
| 配額 |
值 |
其他資訊 |
| 每分鐘要求數 |
60,000 |
|
| 每分鐘寫入要求數 |
18,000 |
在大多數情況下，單一 HTTP 要求或 API 呼叫會計為單一要求。
不過，部分作業會計為多項要求。舉例來說，批次要求 (例如 `ImportAptArtifacts`) 可能會針對批次中的每個項目收取配額費用。Docker 提取或推送作業通常會產生多項 HTTP 要求，因此系統會針對每項要求收取配額費用。 |
| 每分鐘刪除要求數 |
18,000 |
|
每位使用者的要求配額
在專案中，每位使用者可傳送的要求次數並沒有預設的配額上限。不過，您可以選擇在專案中設定每位使用者的配額上限。每位使用者的配額上限適用於每位已通過驗證的使用者。如果用戶端 IP 位址會將未經驗證的要求傳送至公開存放區，則同樣適用這類配額上限。
Cloud KMS 配額和 Artifact Registry
在 Artifact Registry 中使用 CMEK 時，專案可能會耗用 Cloud KMS 密碼編譯要求配額。舉例來說，每次上傳或下載 CMEK 加密的存放區時，都會消耗這些配額。
使用 CMEK 金鑰進行加密和解密作業時，只有在使用外部 (Cloud EKM) 金鑰時，才會影響 Cloud KMS 配額。
確認您有足夠的配額，可為應用程式和工作流程啟用應用程式層 Secret 加密功能。詳情請參閱「Cloud KMS 配額」。
使用限制
Artifact Registry 會強制實行下列用量限制。
| 用量限制 |
值 |
| 每分鐘的存放區建立和刪除作業數 |
30 |
列出存放區中構件的限制
所有格式的格式專屬 API 要求上限為 10,000 次。舉例來說，如果存放區含有超過 10,000 個映像檔或標記，列出容器映像檔的 Docker Registry API 方法將會傳回不完整的清單。
這項限制不適用於 gcloud artifacts docker images list 指令或 Artifact Registry API 要求。
申請提高配額
如要調整大部分配額，請使用 Trusted Cloud 控制台。
詳情請參閱「要求調整配額」。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-25 (世界標準時間)。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-08-25 (世界標準時間)。"],[[["\u003cp\u003eArtifact Registry has both quotas, which are adjustable limits on resource usage, and system limits, which are fixed values that cannot be changed.\u003c/p\u003e\n"],["\u003cp\u003eQuotas are used to manage resource usage, prevent service overload, and ensure fairness among Google Cloud users, and they generally apply at the Google Cloud project level.\u003c/p\u003e\n"],["\u003cp\u003eArtifact Registry enforces quotas on a per-project and per-user basis, with limits on requests per minute, write requests per minute, and delete requests per minute in each region or multi-region.\u003c/p\u003e\n"],["\u003cp\u003eUsage limits include restrictions such as a maximum number of cleanup policy deletions per repository per day, a maximum data retrieval from upstream of remote repository per request, and limits on upstream host reads per organization for remote repositories.\u003c/p\u003e\n"],["\u003cp\u003eWhen using remote repositories, requests to upstream hosts count against the organization's upstream host read request limit, and caching artifacts in the remote repository counts towards the project's write and request quotas.\u003c/p\u003e\n"]]],[],null,["# Quotas and limits\n\nThis document lists the quotas and system limits that apply to\nArtifact Registry.\n\n- *Quotas* specify the amount of a countable, shared resource that you can use. Quotas are defined by Google Cloud services such as Artifact Registry.\n- *System limits* are fixed values that cannot be changed.\n\nGoogle Cloud uses quotas to help ensure fairness and reduce\nspikes in resource use and availability. A quota restricts how much of a\nGoogle Cloud resource your Google Cloud project can use. Quotas\napply to a range of resource types, including hardware, software, and network\ncomponents. For example, quotas can restrict the number of API calls to a\nservice, the number of load balancers used concurrently by your project, or the\nnumber of projects that you can create. Quotas protect the community of\nGoogle Cloud users by preventing the overloading of services. Quotas also\nhelp you to manage your own Google Cloud resources.\n\nThe Cloud Quotas system does the following:\n\n- Monitors your consumption of Google Cloud products and services\n- Restricts your consumption of those resources\n- Provides a way to [request changes to the quota value](/docs/quotas/help/request_increase) and [automate quota adjustments](/docs/quotas/quota-adjuster)\n\nIn most cases, when you attempt to consume more of a resource than its quota\nallows, the system blocks access to the resource, and the task that\nyou're trying to perform fails.\n\nQuotas generally apply at the Google Cloud project\nlevel. Your use of a resource in one project doesn't affect\nyour available quota in another project. Within a Google Cloud project, quotas\nare shared across all applications and IP addresses.\n\n\nThere are also *system limits* on Artifact Registry resources.\nSystem limits can't be changed.\n\nArtifact Registry limits the maximum rate of incoming requests and enforces\nquotas on a per-project and per-user basis.\n\nFor more information about quota policies, viewing your quotas, and managing\nyour quotas, see the [Cloud Quotas documentation](/docs/quotas/overview).\n\nGo to the [API dashboard](https://console.cloud.google.com/apis/dashboard) for your current API\nactivity.\n\nQuotas\n------\n\nArtifact Registry enforces the following quotas.\n\n### Per-project request quota\n\n### Per-user request quota\n\nBy default, projects have unlimited per-user quotas. You can optionally\n[cap](/docs/quotas/view-manage#capping_usage)\nthese per-user quotas within a project. A per-user quota applies per authenticated user\nor per client IP address for unauthenticated requests to a public repository.\n\n\u003cbr /\u003e\n\n\n### Cloud KMS quotas and Artifact Registry\n\n\u003cbr /\u003e\n\nWhen you use CMEK in Artifact Registry,\nyour projects can consume Cloud KMS cryptographic requests\nquotas.\nFor example, CMEK-encrypted repositories\ncan consume these quotas for each upload or download.\n\nEncryption and decryption operations using CMEK keys affect Cloud KMS\nquotas only if you use hardware (Cloud HSM) or external\n(Cloud EKM) keys.\n\n\nConfirm that you have enough quota to enable application-layer secrets encryption for your applications and workflows. For more information, see\n[Cloud KMS quotas](/kms/quotas).\n\nArtifact Analysis quotas\n------------------------\n\nSee [Artifact Analysis quotas and\nlimits](/artifact-analysis/quotas) for information on scanning usage policies.\n\nPublic upstream quotas\n----------------------\n\nIf you use remote repositories to cache public upstream repositories, you might\nbe subject to the upstream repositories' read and write quotas.\n\nUsage Limits\n------------\n\nArtifact Registry enforces the following usage limits.\n\nNote: Deletions requested by cleanup policies count towards the deletions limit as well as the delete request quota.\n\n### Remote Repository Limits\n\nWhen you request an artifact from your remote repository, and the artifact\nhasn't already been cached in your remote, the artifact is requested from the\nupstream repository, and then stored in your remote repository. Requests to\nupstream hosts count against your organization's upstream host read request\nlimit, and caching the artifact in your remote repository uses your project's\nwrite and request quotas. Once the artifact has been cached to your remote,\nrequests for that artifact only count against your project's request quota.\n\nArtifact Registry enforces the following usage limits for remote\nrepositories.\n\n### Limit for listing artifacts in a repository\n\nFormat-specific API requests to all formats are limited to 10,000. For example,\nthe Docker Registry API method to\n[list container images](https://docs.docker.com/registry/spec/api/#listing-image-tags)\nreturns an incomplete list if a repository has more than 10,000 images or tags.\n\nThe limitation does not apply to the\n[gcloud artifacts docker images list](/sdk/gcloud/reference/artifacts/docker/images/list)\ncommand or Artifact Registry API requests.\n\nRequest a quota increase\n------------------------\n\nTo adjust most quotas, use the Google Cloud console.\nFor more information, see\n[Request a quota adjustment](/docs/quotas/help/request_increase)."]]
