Complete Vault Lock (POST lockId)
This operation completes the vault locking process by transitioning the vault lock from
InProgress state to the
Locked state, which causes the vault
lock policy to become unchangeable. A vault lock is put into the
state by calling Initiate Vault Lock (POST lock-policy). You can obtain the state of the vault lock by
calling Get Vault Lock (GET lock-policy). For more
information about the vault locking process, see Amazon Glacier Vault Lock.
This operation is idempotent. This request is always successful if the vault lock is in the
Locked state and the provided lock ID matches the lock ID originally used to
lock the vault.
If an invalid lock ID is passed in the request when the vault lock is in the
the operation returns an
AccessDeniedException error. If an invalid lock ID is
passed in the request when the vault lock is in the
InProgress state, the operation throws an
To complete the vault locking process, send an HTTP
POST request to the URI
of the vault's
lock-policy subresource with a valid lock ID.
lockIdHTTP/1.1 Host: glacier.
AccountId value is the AWS account ID. This value must match the AWS account ID associated with the credentials used to sign the request.
You can either specify an AWS account ID or optionally a single '
-' (hyphen), in which case Amazon Glacier uses the AWS account ID associated with the credentials used to sign the request.
If you specify your account ID, do not include any hyphens ('-') in the ID.
lockId value is the lock ID obtained from a Initiate Vault Lock (POST lock-policy)
This operation uses only request headers that are common to all operations. For information about common request headers, see Common Request Headers.
This operation does not have a request body.
If the operation request is successful, the service returns an HTTP
HTTP/1.1 204 No Content x-amzn-RequestId: x-amzn-RequestId Date: Date
This operation uses only response headers that are common to most responses. For information about common response headers, see Common Response Headers.
This operation does not return a response body.
For information about Amazon Glacier exceptions and error messages, see Error Responses.
The following example sends an HTTP POST request with the lock ID to complete the vault locking process.
POST /-/vaults/examplevault/lock-policy/AE863rKkWZU53SLW5be4DUcW HTTP/1.1 Host: glacier.us-west-2.amazonaws.com x-amz-Date: 20141123T120000Z Authorization: AWS4-HMAC-SHA256 Credential=AKIAIOSFODNN7EXAMPLE/20141123/us-west-2/glacier/aws4_request,SignedHeaders=host;x-amz-date;x-amz-glacier-version,Signature=9257c16da6b25a715ce900a5b45b03da0447acf430195dcb540091b12966f2a2 Content-Length:
If the request was successful, Amazon Glacier returns an
HTTP 204 No Content
response, as shown in the following example.
HTTP/1.1 204 No Content x-amzn-RequestId: AAABZpJrTyioDC_HsOmHae8EZp_uBSJr6cnGOLKp_XJCl-Q Date: Sun, 23 Nov 2014 12:02:00 GMT