ecr.signing.add-key

Trust a cosign public key or a notation certificate

POST /ecr/api/signing-keysIAM ecr:CreateSigningKeyChanges state

kind "cosign": the PEM public key (cosign.pub; ECDSA, RSA ≥ 2048 or Ed25519). kind "notation": PEM certificate(s) — a root, an intermediate or the signing certificate — that a signature's chain must reach. repositoryPattern (* globs, default "*") limits which repositories the key may vouch for.

Request syntax

POST /ecr/api/signing-keys
{
  "name": "string",
  "kind": "enum",
  "pem": "string",
  "repositoryPattern": "string"
}

Request body

  • nameRequired

    string

    A name for the key, unique in the organization: 1–64 letters, digits, space, . _ - (starting with a letter or digit)

    Constraints: 1-64 chars, /^[A-Za-z0-9][A-Za-z0-9 ._-]*$/

  • kindRequired

    enum

    cosign: a cosign public key; notation: a Notary Project (notation) certificate

    One of: cosign, notation

  • pemRequired

    string

    PEM text, up to 64 KiB. cosign: the public key (cosign.pub; ECDSA, RSA of at least 2048 bits or Ed25519). notation: one or more certificates (a root, an intermediate or the signing certificate) a signature’s chain must reach. Material that does not parse as that kind is refused with 400

    Constraints: 1-65536 chars

  • repositoryPatternOptional

    string

    Which repositories the key may vouch for: a repository name with * globs (team/*), 1–255 characters; * (every repository) when omitted

    Constraints: 1-255 chars, /^[a-z0-9._/*-]+$/

Response

201 with the key: id, name, kind (cosign or notation), fingerprint, summary (the key or certificate described), repositoryPattern, pem (as given) and createdAt. 400 when the PEM is not a usable key or certificate of that kind (with why); 409 when the name or the key itself is already trusted, or with code QuotaExceeded at the signing-key quota.

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:CreateSigningKey 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 signing add-key --name example --kind cosign --pem example

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_ecr_signing_add-key.