Abort Vault Lock (DELETE lock-policy)
This operation aborts the vault locking process if the vault lock is not in the
Locked state. If the vault lock is in the
when this operation is requested, the operation returns an
AccessDeniedException error. Aborting the vault locking process removes
the vault lock policy from the specified vault.
A vault lock is put into the
InProgress state by calling Initiate Vault Lock (POST lock-policy). A vault
lock is put into the
Locked state by calling Complete Vault Lock (POST lockId). You can
get the state of a vault lock by calling Get Vault Lock (GET lock-policy). For more information about the vault
locking process, see Amazon Glacier Vault Lock. For more
information about vault lock policies, see Amazon Glacier Access Control with Vault Lock Policies.
This operation is idempotent. You can successfully invoke this operation multiple times, if
the vault lock is in the
InProgress state or if there is no policy
associated with the vault.
To delete the vault lock policy, send an HTTP
DELETE request to the URI
of the vault's
vaultName/lock-policy HTTP/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.
This operation does not use request parameters.
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 policy is successfully deleted, Amazon Glacier returns an
HTTP 204 No Content response.
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 demonstrates how to abort the vault locking process.
In this example, a
DELETE request is sent to the
lock-policy subresource of the vault named
DELETE /-/vaults/examplevault/lock-policy 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 x-amz-glacier-version: 2012-06-01
If the policy is successfully deleted 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:00:00 GMT