本页面上的部分或全部信息可能不适用于 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 配额系统执行以下操作：
在大多数情况下，当您尝试消耗的资源超出其配额允许的范围时，系统会阻止对资源的访问，并且您尝试执行的任务会失败。
配额通常在 Trusted Cloud 项目级层应用。您在一个项目中使用资源不会影响您在另一个项目中的可用配额。在 Trusted Cloud 项目中，配额在所有应用和 IP 地址间共享。
Artifact Registry 资源也有系统限制。系统限制不能更改。
Artifact Registry 会限制传入请求的最大速率，并按项目和用户实施相应的配额。
如需了解配额政策以及如何查看和管理您的配额，请参阅使用配额。
如需查看您当前的 API 活动情况，请转到 API 信息中心。
配额
Artifact Registry 会强制执行以下配额。
每个项目的请求配额
| 配额 |
值 |
其他信息 |
| 每分钟请求数 |
60000 |
|
| 每分钟写入请求数 |
18,000 |
在大多数情况下，单个 HTTP 请求或 API 调用计为 1 个请求。
不过，某些操作会算作多个请求。例如，像 `ImportAptArtifacts` 这样的批量请求可能会针对批次中的每个项目收取配额费用。Docker pull 或 push 通常会发出多个 HTTP 请求，因此每个请求都会消耗配额。 |
| 每分钟删除请求数 |
18,000 |
|
每位用户的请求配额
默认情况下，项目的每位用户配额不受限制。您可以选择为项目中每位用户的配额设置上限。每位用户的配额会应用于每个经过身份验证的用户或每个客户端 IP 地址（针对向公共代码库发送的未经身份验证的请求）。
Cloud KMS 配额和 Artifact Registry
在 Artifact Registry 中使用 CMEK 时，您的项目可能会消耗 Cloud KMS 加密请求配额。例如，由 CMEK 加密的制品库可为每次上传或下载消耗这些配额。
仅当您使用外部 (Cloud EKM) 密钥时，使用 CMEK 密钥执行的加密和解密操作才会影响 Cloud KMS 配额。
请确认您有足够的配额，以便为您的应用和工作流启用应用层 Secret 加密。如需了解详情，请参阅 Cloud KMS 配额。
使用限制
Artifact Registry 实施以下用量限额。
| 用量限制 |
值 |
| 每分钟的代码库创建和删除操作数 |
30 |
列出代码库中的制品时需要遵循的限制
针对所有格式的格式专属 API 请求数量上限为 10,000 次。例如，如果代码库包含的映像或标记超过 10000 个，则用于列出容器映像的 Docker Registry API 方法将返回不完整的列表。
此限制不适用于 gcloud artifacts docker images list 命令或 Artifact Registry API 请求。
申请增加配额
如需调整大多数配额，请使用 Trusted Cloud 控制台。如需了解详情，请参阅申请配额调整。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：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"]],["最后更新时间 (UTC)：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)."]]
