Skip to main content
POST
Rewrap ciphertext with current key material
Requires the IAM action kms:Rewrap. See KMS permissions for the full list, what each one covers, and an example policy.

Authorizations

Authorization
string
header
required

An OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. This is the recommended way to authenticate.

Get one by exchanging a service account's access key pair at POST /v1/oauth/token with grant_type=client_credentials. It is the standard client-credentials grant, so any OAuth-aware library will obtain and refresh it for you.

Tokens last an hour by default. The same access key pair is separately your AWS SigV4 credential for the S3-compatible object endpoint, which speaks nothing else.

Path Parameters

key_id
string<uuid>
required

Body

application/json
ciphertext
string<byte>
required

Base64-encoded ciphertext or wrapped data key produced by this KMS key. AAD is neither required nor changed.

Response

Success

ciphertext
string<byte>

Base64-encoded opaque, versioned ciphertext. Store verbatim; do not parse its internal layout. Decrypt selects the original material version automatically after rotation.

Example:

"AQIDBHByb2QtbWFzdGVyL2VuY3J5cHRlZA=="

key_crn
string

CRN of the key the ciphertext was sealed under.

Example:

"crn:kms:sa-saopaulo-1:my-account:key/prod-master"