ecr.storage.put-quotaSet the organization's storage quota
A push (or pull-through fill) that would store more is refused with DENIED and the numbers; a layer already stored always passes. A repository has its own storageQuotaBytes (PATCH /ecr/api/repositories/{id}). Lowering a quota deletes nothing.
Request syntax
PUT /ecr/api/storage-quota
{
"quotaBytes": "number"
}Request body
quotaBytesRequirednumber
Cap in bytes on the layers in the organization’s repositories, each counted once: 1 MiB (1048576) to 1 PiB. null removes it. Required. A push over it is refused; lowering it deletes nothing. The platform quota applies too, whichever is lower
Constraints: integer, 1048576-1125899906842624
May be null.
Response
200 with { quotaBytes, usedBytes, warning }: usedBytes is what the quota counts (layers in repositories); warning says when the registry already stores more than the new quota, so pushes are refused until images are deleted (else null).
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow ecr:PutRegistryStorageQuota on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud ecr storage put-quota --quota-bytes 1curl -X PUT "https://console.platform-development.deutschecloud.app/ecr/api/storage-quota" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"quotaBytes":1}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_ecr_storage_put-quota.