s3.bucket-objects.restore-version

Make an older version the current one (copied over its key)

POST /s3/api/buckets/{name}/objects/restore-versionIAM s3:PutObjectChanges stateDestructive

Also needs s3:GetObjectVersion. The older version stays; the copy is a new latest version. The same as CopyObject with x-amz-copy-source: bucket/key?versionId=….

Request syntax

POST /s3/api/buckets/{name}/objects/restore-version
{
  "key": "string",
  "versionId": "string"
}

Path parameters

  • nameRequired

    string

    Constraints: 3-63 chars, /^[a-z0-9][a-z0-9-]*[a-z0-9]$/

Request body

  • keyRequired

    string

    Key of the object

    Constraints: min 1 chars

  • versionIdRequired

    string

    The older version to make the current one again

    Constraints: 1-1024 chars, /^[A-Za-z0-9._\-+=/]+$/

Response

200; data is { versionId }: the id of the new current version (null when the store gives none).

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 s3:PutObject 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 s3 bucket-objects restore-version name --key example --version-id example

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