Errors - Basaltic

Errors

Code	Status	Means
`KMS_KEY_NOT_FOUND`	404	No key with that id in your account. A key belonging to another account reads the same way.
`KMS_KEY_NAME_EXISTS`	409	Another key of yours already holds the name.
`KMS_KEY_DISABLED`	409	Crypto operation on a `disabled` key.
`KMS_KEY_IN_USE`	409	A resource, retained encrypted data, or an encrypted write still depends on the key. Remove those dependencies before scheduling deletion.
`KMS_KEY_PENDING_DELETION`	409	Crypto, enable, disable or update on a key inside the deletion window. Cancel first.
`KMS_INVALID_KEY_USAGE`	400	Operation from the usage the key is not pinned to, or a spec/usage pair the spec cannot satisfy.
`KMS_INVALID_KEY_SPEC`	400	Unknown spec, or an encryption context supplied for an asymmetric key.
`KMS_UNSUPPORTED_SIGNING_ALGORITHM`	400	`signing_algorithm` does not match the key spec.
`KMS_INVALID_DELETION_WINDOW`	400	`recovery_window_days` outside 7–30.

Rotation errors

See key rotation for status polling and retries. Reuse the original Idempotency-Key after a timeout. If reconciliation remains pending, contact support with the key and rotation IDs.

Code	Status
`KMS_ROTATION_IN_PROGRESS`	409	A rotation is active or awaiting reconciliation. Poll its status; do not create a new intent to bypass it.
`KMS_ROTATION_NOT_FOUND`	404	The rotation does not belong to this key and account, or does not exist.
`KMS_INVALID_KEY_VERSION`	400	The requested material version does not exist.
`INVALID_INPUT`	400	Missing enabled, invalid period (90–2560 days), malformed version, or ciphertext that cannot be rewrapped.