Table of Contents
Glacier.Client¶A low-level client representing Amazon Glacier:
client = session.create_client('glacier')
These are the available methods:
abort_multipart_upload()abort_vault_lock()add_tags_to_vault()can_paginate()complete_multipart_upload()complete_vault_lock()create_vault()delete_archive()delete_vault()delete_vault_access_policy()delete_vault_notifications()describe_job()describe_vault()generate_presigned_url()get_data_retrieval_policy()get_job_output()get_paginator()get_vault_access_policy()get_vault_lock()get_vault_notifications()get_waiter()initiate_job()initiate_multipart_upload()initiate_vault_lock()list_jobs()list_multipart_uploads()list_parts()list_provisioned_capacity()list_tags_for_vault()list_vaults()purchase_provisioned_capacity()remove_tags_from_vault()set_data_retrieval_policy()set_vault_access_policy()set_vault_notifications()upload_archive()upload_multipart_part()abort_multipart_upload(**kwargs)¶This operation aborts a multipart upload identified by the upload ID.
After the Abort Multipart Upload request succeeds, you cannot upload any more parts to the multipart upload or complete the multipart upload. Aborting a completed upload fails. However, aborting an already-aborted upload will succeed, for a short time. For more information about uploading a part and completing a multipart upload, see UploadMultipartPart and CompleteMultipartUpload .
This operation is idempotent.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and underlying REST API, see Working with Archives in Amazon Glacier and Abort Multipart Upload in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.abort_multipart_upload(
vaultName='string',
uploadId='string'
)
| Parameters: |
|
|---|---|
| Returns: | None |
Examples
The example deletes an in-progress multipart upload to a vault named my-vault:
response = client.abort_multipart_upload(
accountId='-',
uploadId='19gaRezEXAMPLES6Ry5YYdqthHOC_kGRCT03L9yetr220UmPtBYKk-OssZtLqyFu7sY1_lR7vgFuJV6NtcV5zpsJ',
vaultName='my-vault',
)
print(response)
Expected Output:
{
'ResponseMetadata': {
'...': '...',
},
}
abort_vault_lock(**kwargs)¶This operation aborts the vault locking process if the vault lock is not in the Locked state. If the vault lock is in the Locked state 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 InitiateVaultLock . A vault lock is put into the Locked state by calling CompleteVaultLock . You can get the state of a vault lock by calling GetVaultLock . 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.
See also: AWS API Documentation
Request Syntax
response = client.abort_vault_lock(
vaultName='string'
)
| Parameters: |
|
|---|---|
| Returns: | None |
Examples
The example aborts the vault locking process if the vault lock is not in the Locked state for the vault named examplevault.
response = client.abort_vault_lock(
accountId='-',
vaultName='examplevault',
)
print(response)
Expected Output:
{
'ResponseMetadata': {
'...': '...',
},
}
This operation adds the specified tags to a vault. Each tag is composed of a key and a value. Each vault can have up to 10 tags. If your request would cause the tag limit for the vault to be exceeded, the operation throws the LimitExceededException error. If a tag already exists on the vault under a specified key, the existing key value will be overwritten. For more information about tags, see Tagging Amazon Glacier Resources .
See also: AWS API Documentation
Request Syntax
response = client.add_tags_to_vault(
vaultName='string',
Tags={
'string': 'string'
}
)
| Parameters: |
|
|---|---|
| Returns: | None |
Examples
The example adds two tags to a my-vault.
response = client.add_tags_to_vault(
Tags={
'examplekey1': 'examplevalue1',
'examplekey2': 'examplevalue2',
},
accountId='-',
vaultName='my-vault',
)
print(response)
Expected Output:
{
'ResponseMetadata': {
'...': '...',
},
}
can_paginate(operation_name)¶Check if an operation can be paginated.
| Parameters: | operation_name (string) – The operation name. This is the same name
as the method name on the client. For example, if the
method name is create_foo, and you’d normally invoke the
operation as client.create_foo(**kwargs), if the
create_foo operation can be paginated, you can use the
call client.get_paginator("create_foo"). |
|---|---|
| Returns: | True if the operation can be paginated,
False otherwise. |
complete_multipart_upload(**kwargs)¶You call this operation to inform Amazon Glacier that all the archive parts have been uploaded and that Amazon Glacier can now assemble the archive from the uploaded parts. After assembling and saving the archive to the vault, Amazon Glacier returns the URI path of the newly created archive resource. Using the URI path, you can then access the archive. After you upload an archive, you should save the archive ID returned to retrieve the archive at a later point. You can also get the vault inventory to obtain a list of archive IDs in a vault. For more information, see InitiateJob .
In the request, you must include the computed SHA256 tree hash of the entire archive you have uploaded. For information about computing a SHA256 tree hash, see Computing Checksums . On the server side, Amazon Glacier also constructs the SHA256 tree hash of the assembled archive. If the values match, Amazon Glacier saves the archive to the vault; otherwise, it returns an error, and the operation fails. The ListParts operation returns a list of parts uploaded for a specific multipart upload. It includes checksum information for each uploaded part that can be used to debug a bad checksum issue.
Additionally, Amazon Glacier also checks for any missing content ranges when assembling the archive, if missing content ranges are found, Amazon Glacier returns an error and the operation fails.
Complete Multipart Upload is an idempotent operation. After your first successful complete multipart upload, if you call the operation again within a short period, the operation will succeed and return the same archive ID. This is useful in the event you experience a network issue that causes an aborted connection or receive a 500 server error, in which case you can repeat your Complete Multipart Upload request and get the same archive ID without creating duplicate archives. Note, however, that after the multipart upload completes, you cannot call the List Parts operation and the multipart upload will not appear in List Multipart Uploads response, even if idempotent complete is possible.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and underlying REST API, see Uploading Large Archives in Parts (Multipart Upload) and Complete Multipart Upload in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.complete_multipart_upload(
vaultName='string',
uploadId='string',
archiveSize='string',
checksum='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'location': 'string',
'checksum': 'string',
'archiveId': 'string'
}
Response Structure
|
Examples
The example completes a multipart upload for a 3 MiB archive.
response = client.complete_multipart_upload(
accountId='-',
archiveSize='3145728',
checksum='9628195fcdbcbbe76cdde456d4646fa7de5f219fb39823836d81f0cc0e18aa67',
uploadId='19gaRezEXAMPLES6Ry5YYdqthHOC_kGRCT03L9yetr220UmPtBYKk-OssZtLqyFu7sY1_lR7vgFuJV6NtcV5zpsJ',
vaultName='my-vault',
)
print(response)
Expected Output:
{
'archiveId': 'NkbByEejwEggmBz2fTHgJrg0XBoDfjP4q6iu87-TjhqG6eGoOY9Z8i1_AUyUsuhPAdTqLHy8pTl5nfCFJmDl2yEZONi5L26Omw12vcs01MNGntHEQL8MBfGlqrEXAMPLEArchiveId',
'checksum': '9628195fcdbcbbe76cdde456d4646fa7de5f219fb39823836d81f0cc0e18aa67',
'location': '/111122223333/vaults/my-vault/archives/NkbByEejwEggmBz2fTHgJrg0XBoDfjP4q6iu87-TjhqG6eGoOY9Z8i1_AUyUsuhPAdTqLHy8pTl5nfCFJmDl2yEZONi5L26Omw12vcs01MNGntHEQL8MBfGlqrEXAMPLEArchiveId',
'ResponseMetadata': {
'...': '...',
},
}
complete_vault_lock(**kwargs)¶This operation completes the vault locking process by transitioning the vault lock from the InProgress state to the Locked state, which causes the vault lock policy to become unchangeable. A vault lock is put into the InProgress state by calling InitiateVaultLock . You can obtain the state of the vault lock by calling GetVaultLock . For more information about the vault locking process, 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 Locked state, 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 InvalidParameter error.
See also: AWS API Documentation
Request Syntax
response = client.complete_vault_lock(
vaultName='string',
lockId='string'
)
| Parameters: |
|
|---|---|
| Returns: | None |
Examples
The example completes the vault locking process by transitioning the vault lock from the InProgress state to the Locked state.
response = client.complete_vault_lock(
accountId='-',
lockId='AE863rKkWZU53SLW5be4DUcW',
vaultName='example-vault',
)
print(response)
Expected Output:
{
'ResponseMetadata': {
'...': '...',
},
}
create_vault(**kwargs)¶This operation creates a new vault with the specified name. The name of the vault must be unique within a region for an AWS account. You can create up to 1,000 vaults per account. If you need to create more vaults, contact Amazon Glacier.
You must use the following guidelines when naming a vault.
This operation is idempotent.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and underlying REST API, see Creating a Vault in Amazon Glacier and Create Vault in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.create_vault(
vaultName='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'location': 'string'
}
Response Structure
|
Examples
The following example creates a new vault named my-vault.
response = client.create_vault(
accountId='-',
vaultName='my-vault',
)
print(response)
Expected Output:
{
'location': '/111122223333/vaults/my-vault',
'ResponseMetadata': {
'...': '...',
},
}
delete_archive(**kwargs)¶This operation deletes an archive from a vault. Subsequent requests to initiate a retrieval of this archive will fail. Archive retrievals that are in progress for this archive ID may or may not succeed according to the following scenarios:
This operation is idempotent. Attempting to delete an already-deleted archive does not result in an error.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and underlying REST API, see Deleting an Archive in Amazon Glacier and Delete Archive in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.delete_archive(
vaultName='string',
archiveId='string'
)
| Parameters: |
|
|---|---|
| Returns: | None |
Examples
The example deletes the archive specified by the archive ID.
response = client.delete_archive(
accountId='-',
archiveId='NkbByEejwEggmBz2fTHgJrg0XBoDfjP4q6iu87-TjhqG6eGoOY9Z8i1_AUyUsuhPAdTqLHy8pTl5nfCFJmDl2yEZONi5L26Omw12vcs01MNGntHEQL8MBfGlqrEXAMPLEArchiveId',
vaultName='examplevault',
)
print(response)
Expected Output:
{
'ResponseMetadata': {
'...': '...',
},
}
delete_vault(**kwargs)¶This operation deletes a vault. Amazon Glacier will delete a vault only if there are no archives in the vault as of the last inventory and there have been no writes to the vault since the last inventory. If either of these conditions is not satisfied, the vault deletion fails (that is, the vault is not removed) and Amazon Glacier returns an error. You can use DescribeVault to return the number of archives in a vault, and you can use Initiate a Job (POST jobs) to initiate a new inventory retrieval for a vault. The inventory contains the archive IDs you use to delete archives using Delete Archive (DELETE archive) .
This operation is idempotent.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and underlying REST API, see Deleting a Vault in Amazon Glacier and Delete Vault in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.delete_vault(
vaultName='string'
)
| Parameters: |
|
|---|---|
| Returns: | None |
Examples
The example deletes a vault named my-vault:
response = client.delete_vault(
accountId='-',
vaultName='my-vault',
)
print(response)
Expected Output:
{
'ResponseMetadata': {
'...': '...',
},
}
delete_vault_access_policy(**kwargs)¶This operation deletes the access policy associated with the specified vault. The operation is eventually consistent; that is, it might take some time for Amazon Glacier to completely remove the access policy, and you might still see the effect of the policy for a short time after you send the delete request.
This operation is idempotent. You can invoke delete multiple times, even if there is no policy associated with the vault. For more information about vault access policies, see Amazon Glacier Access Control with Vault Access Policies .
See also: AWS API Documentation
Request Syntax
response = client.delete_vault_access_policy(
vaultName='string'
)
| Parameters: |
|
|---|---|
| Returns: | None |
Examples
The example deletes the access policy associated with the vault named examplevault.
response = client.delete_vault_access_policy(
accountId='-',
vaultName='examplevault',
)
print(response)
Expected Output:
{
'ResponseMetadata': {
'...': '...',
},
}
delete_vault_notifications(**kwargs)¶This operation deletes the notification configuration set for a vault. The operation is eventually consistent; that is, it might take some time for Amazon Glacier to completely disable the notifications and you might still receive some notifications for a short time after you send the delete request.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and underlying REST API, see Configuring Vault Notifications in Amazon Glacier and Delete Vault Notification Configuration in the Amazon Glacier Developer Guide.
See also: AWS API Documentation
Request Syntax
response = client.delete_vault_notifications(
vaultName='string'
)
| Parameters: |
|
|---|---|
| Returns: | None |
Examples
The example deletes the notification configuration set for the vault named examplevault.
response = client.delete_vault_notifications(
accountId='-',
vaultName='examplevault',
)
print(response)
Expected Output:
{
'ResponseMetadata': {
'...': '...',
},
}
describe_job(**kwargs)¶This operation returns information about a job you previously initiated, including the job initiation date, the user who initiated the job, the job status code/message and the Amazon SNS topic to notify after Amazon Glacier completes the job. For more information about initiating a job, see InitiateJob .
Note
This operation enables you to check the status of your job. However, it is strongly recommended that you set up an Amazon SNS topic and specify it in your initiate job request so that Amazon Glacier can notify the topic after it completes the job.
A job ID will not expire for at least 24 hours after Amazon Glacier completes the job.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For information about the underlying REST API, see Working with Archives in Amazon Glacier in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.describe_job(
vaultName='string',
jobId='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'JobId': 'string',
'JobDescription': 'string',
'Action': 'ArchiveRetrieval'|'InventoryRetrieval',
'ArchiveId': 'string',
'VaultARN': 'string',
'CreationDate': 'string',
'Completed': True|False,
'StatusCode': 'InProgress'|'Succeeded'|'Failed',
'StatusMessage': 'string',
'ArchiveSizeInBytes': 123,
'InventorySizeInBytes': 123,
'SNSTopic': 'string',
'CompletionDate': 'string',
'SHA256TreeHash': 'string',
'ArchiveSHA256TreeHash': 'string',
'RetrievalByteRange': 'string',
'Tier': 'string',
'InventoryRetrievalParameters': {
'Format': 'string',
'StartDate': 'string',
'EndDate': 'string',
'Limit': 'string',
'Marker': 'string'
}
}
Response Structure
|
Examples
The example returns information about the previously initiated job specified by the job ID.
response = client.describe_job(
accountId='-',
jobId='zbxcm3Z_3z5UkoroF7SuZKrxgGoDc3RloGduS7Eg-RO47Yc6FxsdGBgf_Q2DK5Ejh18CnTS5XW4_XqlNHS61dsO4Cn',
vaultName='my-vault',
)
print(response)
Expected Output:
{
'Action': 'InventoryRetrieval',
'Completed': False,
'CreationDate': '2015-07-17T20:23:41.616Z',
'InventoryRetrievalParameters': {
'Format': 'JSON',
},
'JobId': 'zbxcm3Z_3z5UkoroF7SuZKrxgGoDc3RloGduS7Eg-RO47Yc6FxsdGBgf_Q2DK5Ejh18CnTS5XW4_XqlNHS61dsO4CnMW',
'StatusCode': 'InProgress',
'VaultARN': 'arn:aws:glacier:us-west-2:0123456789012:vaults/my-vault',
'ResponseMetadata': {
'...': '...',
},
}
describe_vault(**kwargs)¶This operation returns information about a vault, including the vault’s Amazon Resource Name (ARN), the date the vault was created, the number of archives it contains, and the total size of all the archives in the vault. The number of archives and their total size are as of the last inventory generation. This means that if you add or remove an archive from a vault, and then immediately use Describe Vault, the change in contents will not be immediately reflected. If you want to retrieve the latest inventory of the vault, use InitiateJob . Amazon Glacier generates vault inventories approximately daily. For more information, see Downloading a Vault Inventory in Amazon Glacier .
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and underlying REST API, see Retrieving Vault Metadata in Amazon Glacier and Describe Vault in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.describe_vault(
vaultName='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'VaultARN': 'string',
'VaultName': 'string',
'CreationDate': 'string',
'LastInventoryDate': 'string',
'NumberOfArchives': 123,
'SizeInBytes': 123
}
Response Structure
|
Examples
The example retrieves data about a vault named my-vault.
response = client.describe_vault(
accountId='-',
vaultName='my-vault',
)
print(response)
Expected Output:
{
'CreationDate': '2016-09-23T19:27:18.665Z',
'NumberOfArchives': 0,
'SizeInBytes': 0,
'VaultARN': 'arn:aws:glacier:us-west-2:111122223333:vaults/my-vault',
'VaultName': 'my-vault',
'ResponseMetadata': {
'...': '...',
},
}
generate_presigned_url(ClientMethod, Params=None, ExpiresIn=3600, HttpMethod=None)¶Generate a presigned url given a client, its method, and arguments
| Parameters: |
|
|---|---|
| Returns: | The presigned url |
get_data_retrieval_policy(**kwargs)¶This operation returns the current data retrieval policy for the account and region specified in the GET request. For more information about data retrieval policies, see Amazon Glacier Data Retrieval Policies .
See also: AWS API Documentation
Request Syntax
response = client.get_data_retrieval_policy(
)
| Parameters: | accountId (string) – The
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax{
'Policy': {
'Rules': [
{
'Strategy': 'string',
'BytesPerHour': 123
},
]
}
}
Response Structure
|
Examples
The example returns the current data retrieval policy for the account.
response = client.get_data_retrieval_policy(
accountId='-',
)
print(response)
Expected Output:
{
'Policy': {
'Rules': [
{
'BytesPerHour': 10737418240,
'Strategy': 'BytesPerHour',
},
],
},
'ResponseMetadata': {
'...': '...',
},
}
get_job_output(**kwargs)¶This operation downloads the output of the job you initiated using InitiateJob . Depending on the job type you specified when you initiated the job, the output will be either the content of an archive or a vault inventory.
You can download all the job output or download a portion of the output by specifying a byte range. In the case of an archive retrieval job, depending on the byte range you specify, Amazon Glacier returns the checksum for the portion of the data. You can compute the checksum on the client and verify that the values match to ensure the portion you downloaded is the correct data.
A job ID will not expire for at least 24 hours after Amazon Glacier completes the job. That a byte range. For both archive and inventory retrieval jobs, you should verify the downloaded size against the size returned in the headers from the Get Job Output response.
For archive retrieval jobs, you should also verify that the size is what you expected. If you download a portion of the output, the expected size is based on the range of bytes you specified. For example, if you specify a range of bytes=0-1048575 , you should verify your download size is 1,048,576 bytes. If you download an entire archive, the expected size is the size of the archive when you uploaded it to Amazon Glacier The expected size is also returned in the headers from the Get Job Output response.
In the case of an archive retrieval job, depending on the byte range you specify, Amazon Glacier returns the checksum for the portion of the data. To ensure the portion you downloaded is the correct data, compute the checksum on the client, verify that the values match, and verify that the size is what you expected.
A job ID does not expire for at least 24 hours after Amazon Glacier completes the job. That is, you can download the job output within the 24 hours period after Amazon Glacier completes the job.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and the underlying REST API, see Downloading a Vault Inventory , Downloading an Archive , and Get Job Output
See also: AWS API Documentation
Request Syntax
response = client.get_job_output(
vaultName='string',
jobId='string',
range='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'body': StreamingBody(),
'checksum': 'string',
'status': 123,
'contentRange': 'string',
'acceptRanges': 'string',
'contentType': 'string',
'archiveDescription': 'string'
}
Response Structure
|
Examples
The example downloads the output of a previously initiated inventory retrieval job that is identified by the job ID.
response = client.get_job_output(
accountId='-',
jobId='zbxcm3Z_3z5UkoroF7SuZKrxgGoDc3RloGduS7Eg-RO47Yc6FxsdGBgf_Q2DK5Ejh18CnTS5XW4_XqlNHS61dsO4CnMW',
range='',
vaultName='my-vaul',
)
print(response)
Expected Output:
{
'acceptRanges': 'bytes',
'body': 'inventory-data',
'contentType': 'application/json',
'status': 200,
'ResponseMetadata': {
'...': '...',
},
}
get_paginator(operation_name)¶Create a paginator for an operation.
| Parameters: | operation_name (string) – The operation name. This is the same name
as the method name on the client. For example, if the
method name is create_foo, and you’d normally invoke the
operation as client.create_foo(**kwargs), if the
create_foo operation can be paginated, you can use the
call client.get_paginator("create_foo"). |
|---|---|
| Raises: | OperationNotPageableError – Raised if the operation is not
pageable. You can use the client.can_paginate method to
check if an operation is pageable. |
| Return type: | L{botocore.paginate.Paginator} |
| Returns: | A paginator object. |
get_vault_access_policy(**kwargs)¶This operation retrieves the access-policy subresource set on the vault; for more information on setting this subresource, see Set Vault Access Policy (PUT access-policy) . If there is no access policy set on the vault, the operation returns a 404 Not found error. For more information about vault access policies, see Amazon Glacier Access Control with Vault Access Policies .
See also: AWS API Documentation
Request Syntax
response = client.get_vault_access_policy(
vaultName='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'policy': {
'Policy': 'string'
}
}
Response Structure
|
Examples
The example retrieves the access-policy set on the vault named example-vault.
response = client.get_vault_access_policy(
accountId='-',
vaultName='example-vault',
)
print(response)
Expected Output:
{
'policy': {
'Policy': '{"Version":"2012-10-17","Statement":[{"Sid":"Define-owner-access-rights","Effect":"Allow","Principal":{"AWS":"arn:aws:iam::999999999999:root"},"Action":"glacier:DeleteArchive","Resource":"arn:aws:glacier:us-west-2:999999999999:vaults/examplevault"}]}',
},
'ResponseMetadata': {
'...': '...',
},
}
get_vault_lock(**kwargs)¶This operation retrieves the following attributes from the lock-policy subresource set on the specified vault:
InProgess or Locked .InProgress state.A vault lock is put into the InProgress state by calling InitiateVaultLock . A vault lock is put into the Locked state by calling CompleteVaultLock . You can abort the vault locking process by calling AbortVaultLock . For more information about the vault locking process, Amazon Glacier Vault Lock .
If there is no vault lock policy set on the vault, the operation returns a 404 Not found error. For more information about vault lock policies, Amazon Glacier Access Control with Vault Lock Policies .
See also: AWS API Documentation
Request Syntax
response = client.get_vault_lock(
vaultName='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'Policy': 'string',
'State': 'string',
'ExpirationDate': 'string',
'CreationDate': 'string'
}
Response Structure
|
Examples
The example retrieves the attributes from the lock-policy subresource set on the vault named examplevault.
response = client.get_vault_lock(
accountId='-',
vaultName='examplevault',
)
print(response)
Expected Output:
{
'CreationDate': 'exampledate',
'ExpirationDate': 'exampledate',
'Policy': '{"Version":"2012-10-17","Statement":[{"Sid":"Define-vault-lock","Effect":"Deny","Principal":{"AWS":"arn:aws:iam::999999999999:root"},"Action":"glacier:DeleteArchive","Resource":"arn:aws:glacier:us-west-2:999999999999:vaults/examplevault","Condition":{"NumericLessThanEquals":{"glacier:ArchiveAgeinDays":"365"}}}]}',
'State': 'InProgress',
'ResponseMetadata': {
'...': '...',
},
}
get_vault_notifications(**kwargs)¶This operation retrieves the notification-configuration subresource of the specified vault.
For information about setting a notification configuration on a vault, see SetVaultNotifications . If a notification configuration for a vault is not set, the operation returns a 404 Not Found error. For more information about vault notifications, see Configuring Vault Notifications in Amazon Glacier .
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and underlying REST API, see Configuring Vault Notifications in Amazon Glacier and Get Vault Notification Configuration in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.get_vault_notifications(
vaultName='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'vaultNotificationConfig': {
'SNSTopic': 'string',
'Events': [
'string',
]
}
}
Response Structure
|
Examples
The example retrieves the notification-configuration for the vault named my-vault.
response = client.get_vault_notifications(
accountId='-',
vaultName='my-vault',
)
print(response)
Expected Output:
{
'vaultNotificationConfig': {
'Events': [
'InventoryRetrievalCompleted',
'ArchiveRetrievalCompleted',
],
'SNSTopic': 'arn:aws:sns:us-west-2:0123456789012:my-vault',
},
'ResponseMetadata': {
'...': '...',
},
}
get_waiter(waiter_name)¶initiate_job(**kwargs)¶This operation initiates a job of the specified type. In this release, you can initiate a job to retrieve either an archive or a vault inventory (a list of archives in a vault).
Retrieving data from Amazon Glacier is a two-step process:
Note
A data retrieval policy can cause your initiate retrieval job request to fail with a PolicyEnforcedException exception. For more information about data retrieval policies, see Amazon Glacier Data Retrieval Policies . For more information about the PolicyEnforcedException exception, see Error Responses .
The retrieval request is executed asynchronously. When you initiate a retrieval job, Amazon Glacier creates a job and returns a job ID in the response. When Amazon Glacier completes the job, you can get the job output (archive or inventory data). For information about getting job output, see GetJobOutput operation.
The job must complete before you can get its output. To determine when a job is complete, you have the following options:
Note
The information you get via notification is same that you get by calling DescribeJob .
If for a specific event, you add both the notification configuration on the vault and also specify an SNS topic in your initiate job request, Amazon Glacier sends both notifications. For more information, see SetVaultNotifications .
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
About the Vault Inventory
Amazon Glacier prepares an inventory for each vault periodically, every 24 hours. When you initiate a job for a vault inventory, Amazon Glacier returns the last inventory for the vault. The inventory data you get might be up to a day or two days old. Also, the initiate inventory job might take some time to complete before you can download the vault inventory. So you do not want to retrieve a vault inventory for each vault operation. However, in some scenarios, you might find the vault inventory useful. For example, when you upload an archive, you can provide an archive description but not an archive name. Amazon Glacier provides you a unique archive ID, an opaque string of characters. So, you might maintain your own database that maps archive names to their corresponding Amazon Glacier assigned archive IDs. You might find the vault inventory useful in the event you need to reconcile information in your database with the actual vault inventory.
Range Inventory Retrieval
You can limit the number of inventory items retrieved by filtering on the archive creation date or by setting a limit.
Filtering by Archive Creation Date
You can retrieve inventory items for archives created between StartDate and EndDate by specifying values for these parameters in the InitiateJob request. Archives created on or after the StartDate and before the EndDate will be returned. If you only provide the StartDate without the EndDate , you will retrieve the inventory for all archives created on or after the StartDate . If you only provide the EndDate without the StartDate , you will get back the inventory for all archives created before the EndDate .
Limiting Inventory Items per Retrieval
You can limit the number of inventory items returned by setting the Limit parameter in the InitiateJob request. The inventory job output will contain inventory items up to the specified Limit . If there are more inventory items available, the result is paginated. After a job is complete you can use the DescribeJob operation to get a marker that you use in a subsequent InitiateJob request. The marker will indicate the starting point to retrieve the next set of inventory items. You can page through your entire inventory by repeatedly making InitiateJob requests with the marker from the previous DescribeJob output, until you get a marker from DescribeJob that returns null, indicating that there are no more inventory items available.
You can use the Limit parameter together with the date range parameters.
About Ranged Archive Retrieval
You can initiate an archive retrieval for the whole archive or a range of the archive. In the case of ranged archive retrieval, you specify a byte range to return or the whole archive. The range specified must be megabyte (MB) aligned, that is the range start value must be divisible by 1 MB and range end value plus 1 must be divisible by 1 MB or equal the end of the archive. If the ranged archive retrieval is not megabyte aligned, this operation returns a 400 response. Furthermore, to ensure you get checksum values for data you download using Get Job Output API, the range must be tree hash aligned.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and the underlying REST API, see Initiate a Job and Downloading a Vault Inventory
Expedited and Bulk Archive Retrievals
When retrieving an archive, you can specify one of the following options in the Tier field of the request body:
For more information about expedited and bulk retrievals, see Retrieving Amazon Glacier Archives .
See also: AWS API Documentation
Request Syntax
response = client.initiate_job(
vaultName='string',
jobParameters={
'Format': 'string',
'Type': 'string',
'ArchiveId': 'string',
'Description': 'string',
'SNSTopic': 'string',
'RetrievalByteRange': 'string',
'Tier': 'string',
'InventoryRetrievalParameters': {
'StartDate': 'string',
'EndDate': 'string',
'Limit': 'string',
'Marker': 'string'
}
}
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'location': 'string',
'jobId': 'string'
}
Response Structure
|
Examples
The example initiates an inventory-retrieval job for the vault named examplevault.
response = client.initiate_job(
accountId='-',
jobParameters={
'Description': 'My inventory job',
'Format': 'CSV',
'SNSTopic': 'arn:aws:sns:us-west-2:111111111111:Glacier-InventoryRetrieval-topic-Example',
'Type': 'inventory-retrieval',
},
vaultName='examplevault',
)
print(response)
Expected Output:
{
'jobId': ' HkF9p6o7yjhFx-K3CGl6fuSm6VzW9T7esGQfco8nUXVYwS0jlb5gq1JZ55yHgt5vP54ZShjoQzQVVh7vEXAMPLEjobID',
'location': '/111122223333/vaults/examplevault/jobs/HkF9p6o7yjhFx-K3CGl6fuSm6VzW9T7esGQfco8nUXVYwS0jlb5gq1JZ55yHgt5vP54ZShjoQzQVVh7vEXAMPLEjobID',
'ResponseMetadata': {
'...': '...',
},
}
initiate_multipart_upload(**kwargs)¶This operation initiates a multipart upload. Amazon Glacier creates a multipart upload resource and returns its ID in the response. The multipart upload ID is used in subsequent requests to upload parts of an archive (see UploadMultipartPart ).
When you initiate a multipart upload, you specify the part size in number of bytes. The part size must be a megabyte (1024 KB) multiplied by a power of 2-for example, 1048576 (1 MB), 2097152 (2 MB), 4194304 (4 MB), 8388608 (8 MB), and so on. The minimum allowable part size is 1 MB, and the maximum is 4 GB.
Every part you upload to this resource (see UploadMultipartPart ), except the last one, must have the same size. The last one can be the same size or smaller. For example, suppose you want to upload a 16.2 MB file. If you initiate the multipart upload with a part size of 4 MB, you will upload four parts of 4 MB each and one part of 0.2 MB.
Note
You don’t need to know the size of the archive when you start a multipart upload because Amazon Glacier does not require you to specify the overall archive size.
After you complete the multipart upload, Amazon Glacier removes the multipart upload resource referenced by the ID. Amazon Glacier also removes the multipart upload resource if you cancel the multipart upload or it may be removed if there is no activity for a period of 24 hours.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and underlying REST API, see Uploading Large Archives in Parts (Multipart Upload) and Initiate Multipart Upload in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.initiate_multipart_upload(
vaultName='string',
archiveDescription='string',
partSize='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'location': 'string',
'uploadId': 'string'
}
Response Structure
|
Examples
The example initiates a multipart upload to a vault named my-vault with a part size of 1 MiB (1024 x 1024 bytes) per file.
response = client.initiate_multipart_upload(
accountId='-',
partSize='1048576',
vaultName='my-vault',
)
print(response)
Expected Output:
{
'location': '/111122223333/vaults/my-vault/multipart-uploads/19gaRezEXAMPLES6Ry5YYdqthHOC_kGRCT03L9yetr220UmPtBYKk-OssZtLqyFu7sY1_lR7vgFuJV6NtcV5zpsJ',
'uploadId': '19gaRezEXAMPLES6Ry5YYdqthHOC_kGRCT03L9yetr220UmPtBYKk-OssZtLqyFu7sY1_lR7vgFuJV6NtcV5zpsJ',
'ResponseMetadata': {
'...': '...',
},
}
initiate_vault_lock(**kwargs)¶This operation initiates the vault locking process by doing the following:
InProgress .You can set one vault lock policy for each vault and this policy can be up to 20 KB in size. For more information about vault lock policies, see Amazon Glacier Access Control with Vault Lock Policies .
You must complete the vault locking process within 24 hours after the vault lock enters the InProgress state. After the 24 hour window ends, the lock ID expires, the vault automatically exits the InProgress state, and the vault lock policy is removed from the vault. You call CompleteVaultLock to complete the vault locking process by setting the state of the vault lock to Locked .
After a vault lock is in the Locked state, you cannot initiate a new vault lock for the vault.
You can abort the vault locking process by calling AbortVaultLock . You can get the state of the vault lock by calling GetVaultLock . For more information about the vault locking process, Amazon Glacier Vault Lock .
If this operation is called when the vault lock is in the InProgress state, the operation returns an AccessDeniedException error. When the vault lock is in the InProgress state you must call AbortVaultLock before you can initiate a new vault lock policy.
See also: AWS API Documentation
Request Syntax
response = client.initiate_vault_lock(
vaultName='string',
policy={
'Policy': 'string'
}
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'lockId': 'string'
}
Response Structure
|
Examples
The example initiates the vault locking process for the vault named my-vault.
response = client.initiate_vault_lock(
accountId='-',
policy={
'Policy': '{"Version":"2012-10-17","Statement":[{"Sid":"Define-vault-lock","Effect":"Deny","Principal":{"AWS":"arn:aws:iam::999999999999:root"},"Action":"glacier:DeleteArchive","Resource":"arn:aws:glacier:us-west-2:999999999999:vaults/examplevault","Condition":{"NumericLessThanEquals":{"glacier:ArchiveAgeinDays":"365"}}}]}',
},
vaultName='my-vault',
)
print(response)
Expected Output:
{
'lockId': 'AE863rKkWZU53SLW5be4DUcW',
'ResponseMetadata': {
'...': '...',
},
}
list_jobs(**kwargs)¶This operation lists jobs for a vault, including jobs that are in-progress and jobs that have recently finished.
Note
Amazon Glacier retains recently completed jobs for a period before deleting them; however, it eventually removes completed jobs. The output of completed jobs can be retrieved. Retaining completed jobs for a period of time after they have completed enables you to get a job output in the event you miss the job completion notification or your first attempt to download it fails. For example, suppose you start an archive retrieval job to download an archive. After the job completes, you start to download the archive but encounter a network error. In this scenario, you can retry and download the archive while the job exists.
To retrieve an archive or retrieve a vault inventory from Amazon Glacier, you first initiate a job, and after the job completes, you download the data. For an archive retrieval, the output is the archive data. For an inventory retrieval, it is the inventory list. The List Job operation returns a list of these jobs sorted by job initiation time.
The List Jobs operation supports pagination. You should always check the response Marker field. If there are no more jobs to list, the Marker field is set to null . If there are more jobs to list, the Marker field is set to a non-null value, which you can use to continue the pagination of the list. To return a list of jobs that begins at a specific job, set the marker request parameter to the Marker value for that job that you obtained from a previous List Jobs request.
You can set a maximum limit for the number of jobs returned in the response by specifying the limit parameter in the request. The default limit is 1000. The number of jobs returned might be fewer than the limit, but the number of returned jobs never exceeds the limit.
Additionally, you can filter the jobs list returned by specifying the optional statuscode parameter or completed parameter, or both. Using the statuscode parameter, you can specify to return only jobs that match either the InProgress , Succeeded , or Failed status. Using the completed parameter, you can specify to return only jobs that were completed (true ) or jobs that were not completed (false ).
For the underlying REST API, see List Jobs .
See also: AWS API Documentation
Request Syntax
response = client.list_jobs(
vaultName='string',
limit='string',
marker='string',
statuscode='string',
completed='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'JobList': [
{
'JobId': 'string',
'JobDescription': 'string',
'Action': 'ArchiveRetrieval'|'InventoryRetrieval',
'ArchiveId': 'string',
'VaultARN': 'string',
'CreationDate': 'string',
'Completed': True|False,
'StatusCode': 'InProgress'|'Succeeded'|'Failed',
'StatusMessage': 'string',
'ArchiveSizeInBytes': 123,
'InventorySizeInBytes': 123,
'SNSTopic': 'string',
'CompletionDate': 'string',
'SHA256TreeHash': 'string',
'ArchiveSHA256TreeHash': 'string',
'RetrievalByteRange': 'string',
'Tier': 'string',
'InventoryRetrievalParameters': {
'Format': 'string',
'StartDate': 'string',
'EndDate': 'string',
'Limit': 'string',
'Marker': 'string'
}
},
],
'Marker': 'string'
}
Response Structure
|
Examples
The example lists jobs for the vault named my-vault.
response = client.list_jobs(
accountId='-',
vaultName='my-vault',
)
print(response)
Expected Output:
{
'JobList': [
{
'Action': 'ArchiveRetrieval',
'ArchiveId': 'kKB7ymWJVpPSwhGP6ycSOAekp9ZYe_--zM_mw6k76ZFGEIWQX-ybtRDvc2VkPSDtfKmQrj0IRQLSGsNuDp-AJVlu2ccmDSyDUmZwKbwbpAdGATGDiB3hHO0bjbGehXTcApVud_wyDw',
'ArchiveSHA256TreeHash': '9628195fcdbcbbe76cdde932d4646fa7de5f219fb39823836d81f0cc0e18aa67',
'ArchiveSizeInBytes': 3145728,
'Completed': False,
'CreationDate': '2015-07-17T21:16:13.840Z',
'JobDescription': 'Retrieve archive on 2015-07-17',
'JobId': 'l7IL5-EkXyEY9Ws95fClzIbk2O5uLYaFdAYOi-azsX_Z8V6NH4yERHzars8wTKYQMX6nBDI9cMNHzyZJO59-8N9aHWav',
'RetrievalByteRange': '0-3145727',
'SHA256TreeHash': '9628195fcdbcbbe76cdde932d4646fa7de5f219fb39823836d81f0cc0e18aa67',
'SNSTopic': 'arn:aws:sns:us-west-2:0123456789012:my-vault',
'StatusCode': 'InProgress',
'VaultARN': 'arn:aws:glacier:us-west-2:0123456789012:vaults/my-vault',
},
{
'Action': 'InventoryRetrieval',
'Completed': False,
'CreationDate': '2015-07-17T20:23:41.616Z',
'InventoryRetrievalParameters': {
'Format': 'JSON',
},
'JobId': 'zbxcm3Z_3z5UkoroF7SuZKrxgGoDc3RloGduS7Eg-RO47Yc6FxsdGBgf_Q2DK5Ejh18CnTS5XW4_XqlNHS61dsO4CnMW',
'StatusCode': 'InProgress',
'VaultARN': 'arn:aws:glacier:us-west-2:0123456789012:vaults/my-vault',
},
],
'ResponseMetadata': {
'...': '...',
},
}
list_multipart_uploads(**kwargs)¶This operation lists in-progress multipart uploads for the specified vault. An in-progress multipart upload is a multipart upload that has been initiated by an InitiateMultipartUpload request, but has not yet been completed or aborted. The list returned in the List Multipart Upload response has no guaranteed order.
The List Multipart Uploads operation supports pagination. By default, this operation returns up to 1,000 multipart uploads in the response. You should always check the response for a marker at which to continue the list; if there are no more items the marker is null . To return a list of multipart uploads that begins at a specific upload, set the marker request parameter to the value you obtained from a previous List Multipart Upload request. You can also limit the number of uploads returned in the response by specifying the limit parameter in the request.
Note the difference between this operation and listing parts ( ListParts ). The List Multipart Uploads operation lists all multipart uploads for a vault and does not require a multipart upload ID. The List Parts operation requires a multipart upload ID since parts are associated with a single upload.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and the underlying REST API, see Working with Archives in Amazon Glacier and List Multipart Uploads in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.list_multipart_uploads(
vaultName='string',
marker='string',
limit='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'UploadsList': [
{
'MultipartUploadId': 'string',
'VaultARN': 'string',
'ArchiveDescription': 'string',
'PartSizeInBytes': 123,
'CreationDate': 'string'
},
],
'Marker': 'string'
}
Response Structure
|
Examples
The example lists all the in-progress multipart uploads for the vault named examplevault.
response = client.list_multipart_uploads(
accountId='-',
vaultName='examplevault',
)
print(response)
Expected Output:
{
'Marker': 'null',
'UploadsList': [
{
'ArchiveDescription': 'archive 1',
'CreationDate': '2012-03-19T23:20:59.130Z',
'MultipartUploadId': 'xsQdFIRsfJr20CW2AbZBKpRZAFTZSJIMtL2hYf8mvp8dM0m4RUzlaqoEye6g3h3ecqB_zqwB7zLDMeSWhwo65re4C4Ev',
'PartSizeInBytes': 4194304,
'VaultARN': 'arn:aws:glacier:us-west-2:012345678901:vaults/examplevault',
},
{
'ArchiveDescription': 'archive 2',
'CreationDate': '2012-04-01T15:00:00.000Z',
'MultipartUploadId': 'nPyGOnyFcx67qqX7E-0tSGiRi88hHMOwOxR-_jNyM6RjVMFfV29lFqZ3rNsSaWBugg6OP92pRtufeHdQH7ClIpSF6uJc',
'PartSizeInBytes': 4194304,
'VaultARN': 'arn:aws:glacier:us-west-2:012345678901:vaults/examplevault',
},
{
'ArchiveDescription': 'archive 3',
'CreationDate': '2012-03-20T17:03:43.221Z',
'MultipartUploadId': 'qt-RBst_7yO8gVIonIBsAxr2t-db0pE4s8MNeGjKjGdNpuU-cdSAcqG62guwV9r5jh5mLyFPzFEitTpNE7iQfHiu1XoV',
'PartSizeInBytes': 4194304,
'VaultARN': 'arn:aws:glacier:us-west-2:012345678901:vaults/examplevault',
},
],
'ResponseMetadata': {
'...': '...',
},
}
list_parts(**kwargs)¶This operation lists the parts of an archive that have been uploaded in a specific multipart upload. You can make this request at any time during an in-progress multipart upload before you complete the upload (see CompleteMultipartUpload . List Parts returns an error for completed uploads. The list returned in the List Parts response is sorted by part range.
The List Parts operation supports pagination. By default, this operation returns up to 1,000 uploaded parts in the response. You should always check the response for a marker at which to continue the list; if there are no more items the marker is null . To return a list of parts that begins at a specific part, set the marker request parameter to the value you obtained from a previous List Parts request. You can also limit the number of parts returned in the response by specifying the limit parameter in the request.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and the underlying REST API, see Working with Archives in Amazon Glacier and List Parts in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.list_parts(
vaultName='string',
uploadId='string',
marker='string',
limit='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'MultipartUploadId': 'string',
'VaultARN': 'string',
'ArchiveDescription': 'string',
'PartSizeInBytes': 123,
'CreationDate': 'string',
'Parts': [
{
'RangeInBytes': 'string',
'SHA256TreeHash': 'string'
},
],
'Marker': 'string'
}
Response Structure
|
Examples
The example lists all the parts of a multipart upload.
response = client.list_parts(
accountId='-',
uploadId='OW2fM5iVylEpFEMM9_HpKowRapC3vn5sSL39_396UW9zLFUWVrnRHaPjUJddQ5OxSHVXjYtrN47NBZ-khxOjyEXAMPLE',
vaultName='examplevault',
)
print(response)
Expected Output:
{
'ArchiveDescription': 'archive description',
'CreationDate': '2012-03-20T17:03:43.221Z',
'Marker': 'null',
'MultipartUploadId': 'OW2fM5iVylEpFEMM9_HpKowRapC3vn5sSL39_396UW9zLFUWVrnRHaPjUJddQ5OxSHVXjYtrN47NBZ-khxOjyEXAMPLE',
'PartSizeInBytes': 4194304,
'Parts': [
{
'RangeInBytes': '0-4194303',
'SHA256TreeHash': '01d34dabf7be316472c93b1ef80721f5d4',
},
{
'RangeInBytes': '4194304-8388607',
'SHA256TreeHash': '0195875365afda349fc21c84c099987164',
},
],
'VaultARN': 'arn:aws:glacier:us-west-2:012345678901:vaults/demo1-vault',
'ResponseMetadata': {
'...': '...',
},
}
list_provisioned_capacity(**kwargs)¶This operation lists the provisioned capacity for the specified AWS account.
See also: AWS API Documentation
Request Syntax
response = client.list_provisioned_capacity(
)
| Parameters: | accountId (string) – The
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax{
'ProvisionedCapacityList': [
{
'CapacityId': 'string',
'StartDate': 'string',
'ExpirationDate': 'string'
},
]
}
Response Structure
|
Examples
The example lists the provisioned capacity units for an account.
response = client.list_provisioned_capacity(
accountId='-',
)
print(response)
Expected Output:
{
'ProvisionedCapacityList': [
{
'CapacityId': 'zSaq7NzHFQDANTfQkDen4V7z',
'ExpirationDate': '2016-12-12T00:00:00.000Z',
'StartDate': '2016-11-11T20:11:51.095Z',
},
{
'CapacityId': 'yXaq7NzHFQNADTfQkDen4V7z',
'ExpirationDate': '2017-01-15T00:00:00.000Z',
'StartDate': '2016-12-13T20:11:51.095Z',
},
],
'ResponseMetadata': {
'...': '...',
},
}
This operation lists all the tags attached to a vault. The operation returns an empty map if there are no tags. For more information about tags, see Tagging Amazon Glacier Resources .
See also: AWS API Documentation
Request Syntax
response = client.list_tags_for_vault(
vaultName='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'Tags': {
'string': 'string'
}
}
Response Structure
|
Examples
The example lists all the tags attached to the vault examplevault.
response = client.list_tags_for_vault(
accountId='-',
vaultName='examplevault',
)
print(response)
Expected Output:
{
'Tags': {
'date': 'july2015',
'id': '1234',
},
'ResponseMetadata': {
'...': '...',
},
}
list_vaults(**kwargs)¶This operation lists all vaults owned by the calling user’s account. The list returned in the response is ASCII-sorted by vault name.
By default, this operation returns up to 1,000 items. If there are more vaults to list, the response marker field contains the vault Amazon Resource Name (ARN) at which to continue the list with a new List Vaults request; otherwise, the marker field is null . To return a list of vaults that begins at a specific vault, set the marker request parameter to the vault ARN you obtained from a previous List Vaults request. You can also limit the number of vaults returned in the response by specifying the limit parameter in the request.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and underlying REST API, see Retrieving Vault Metadata in Amazon Glacier and List Vaults in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.list_vaults(
marker='string',
limit='string'
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'VaultList': [
{
'VaultARN': 'string',
'VaultName': 'string',
'CreationDate': 'string',
'LastInventoryDate': 'string',
'NumberOfArchives': 123,
'SizeInBytes': 123
},
],
'Marker': 'string'
}
Response Structure
|
Examples
The example lists all vaults owned by the specified AWS account.
response = client.list_vaults(
accountId='-',
limit='',
marker='',
)
print(response)
Expected Output:
{
'VaultList': [
{
'CreationDate': '2015-04-06T21:23:45.708Z',
'LastInventoryDate': '2015-04-07T00:26:19.028Z',
'NumberOfArchives': 1,
'SizeInBytes': 3178496,
'VaultARN': 'arn:aws:glacier:us-west-2:0123456789012:vaults/my-vault',
'VaultName': 'my-vault',
},
],
'ResponseMetadata': {
'...': '...',
},
}
purchase_provisioned_capacity(**kwargs)¶This operation purchases a provisioned capacity unit for an AWS account.
See also: AWS API Documentation
Request Syntax
response = client.purchase_provisioned_capacity(
)
| Parameters: | accountId (string) – The AWS account ID of the account that owns the vault. 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 use an account ID, don’t include any hyphens (‘-‘) in the ID.
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax{
'capacityId': 'string'
}
Response Structure
|
Examples
The example purchases provisioned capacity unit for an AWS account.
response = client.purchase_provisioned_capacity(
accountId='-',
)
print(response)
Expected Output:
{
'capacityId': 'zSaq7NzHFQDANTfQkDen4V7z',
'ResponseMetadata': {
'...': '...',
},
}
This operation removes one or more tags from the set of tags attached to a vault. For more information about tags, see Tagging Amazon Glacier Resources . This operation is idempotent. The operation will be successful, even if there are no tags attached to the vault.
See also: AWS API Documentation
Request Syntax
response = client.remove_tags_from_vault(
vaultName='string',
TagKeys=[
'string',
]
)
| Parameters: |
|
|---|---|
| Returns: | None |
Examples
The example removes two tags from the vault named examplevault.
response = client.remove_tags_from_vault(
TagKeys=[
'examplekey1',
'examplekey2',
],
accountId='-',
vaultName='examplevault',
)
print(response)
Expected Output:
{
'ResponseMetadata': {
'...': '...',
},
}
set_data_retrieval_policy(**kwargs)¶This operation sets and then enacts a data retrieval policy in the region specified in the PUT request. You can set one policy per region for an AWS account. The policy is enacted within a few minutes of a successful PUT operation.
The set policy operation does not affect retrieval jobs that were in progress before the policy was enacted. For more information about data retrieval policies, see Amazon Glacier Data Retrieval Policies .
See also: AWS API Documentation
Request Syntax
response = client.set_data_retrieval_policy(
Policy={
'Rules': [
{
'Strategy': 'string',
'BytesPerHour': 123
},
]
}
)
| Parameters: |
|
|---|---|
| Returns: | None |
Examples
The example sets and then enacts a data retrieval policy.
response = client.set_data_retrieval_policy(
Policy={
'Rules': [
{
'BytesPerHour': 10737418240,
'Strategy': 'BytesPerHour',
},
],
},
accountId='-',
)
print(response)
Expected Output:
{
'ResponseMetadata': {
'...': '...',
},
}
set_vault_access_policy(**kwargs)¶This operation configures an access policy for a vault and will overwrite an existing policy. To configure a vault access policy, send a PUT request to the access-policy subresource of the vault. An access policy is specific to a vault and is also called a vault subresource. You can set one access policy per vault and the policy can be up to 20 KB in size. For more information about vault access policies, see Amazon Glacier Access Control with Vault Access Policies .
See also: AWS API Documentation
Request Syntax
response = client.set_vault_access_policy(
vaultName='string',
policy={
'Policy': 'string'
}
)
| Parameters: |
|
|---|---|
| Returns: | None |
Examples
The example configures an access policy for the vault named examplevault.
response = client.set_vault_access_policy(
accountId='-',
policy={
'Policy': '{"Version":"2012-10-17","Statement":[{"Sid":"Define-owner-access-rights","Effect":"Allow","Principal":{"AWS":"arn:aws:iam::999999999999:root"},"Action":"glacier:DeleteArchive","Resource":"arn:aws:glacier:us-west-2:999999999999:vaults/examplevault"}]}',
},
vaultName='examplevault',
)
print(response)
Expected Output:
{
'ResponseMetadata': {
'...': '...',
},
}
set_vault_notifications(**kwargs)¶This operation configures notifications that will be sent when specific events happen to a vault. By default, you don’t get any notifications.
To configure vault notifications, send a PUT request to the notification-configuration subresource of the vault. The request should include a JSON document that provides an Amazon SNS topic and specific events for which you want Amazon Glacier to send notifications to the topic.
Amazon SNS topics must grant permission to the vault to be allowed to publish notifications to the topic. You can configure a vault to publish a notification for the following vault events:
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and underlying REST API, see Configuring Vault Notifications in Amazon Glacier and Set Vault Notification Configuration in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.set_vault_notifications(
vaultName='string',
vaultNotificationConfig={
'SNSTopic': 'string',
'Events': [
'string',
]
}
)
| Parameters: |
|
|---|---|
| Returns: | None |
Examples
The example sets the examplevault notification configuration.
response = client.set_vault_notifications(
accountId='-',
vaultName='examplevault',
vaultNotificationConfig={
'Events': [
'ArchiveRetrievalCompleted',
'InventoryRetrievalCompleted',
],
'SNSTopic': 'arn:aws:sns:us-west-2:012345678901:mytopic',
},
)
print(response)
Expected Output:
{
'ResponseMetadata': {
'...': '...',
},
}
upload_archive(**kwargs)¶This operation adds an archive to a vault. This is a synchronous operation, and for a successful upload, your data is durably persisted. Amazon Glacier returns the archive ID in the x-amz-archive-id header of the response.
You must use the archive ID to access your data in Amazon Glacier. After you upload an archive, you should save the archive ID returned so that you can retrieve or delete the archive later. Besides saving the archive ID, you can also index it and give it a friendly name to allow for better searching. You can also use the optional archive description field to specify how the archive is referred to in an external index of archives, such as you might create in Amazon DynamoDB. You can also get the vault inventory to obtain a list of archive IDs in a vault. For more information, see InitiateJob .
You must provide a SHA256 tree hash of the data you are uploading. For information about computing a SHA256 tree hash, see Computing Checksums .
You can optionally specify an archive description of up to 1,024 printable ASCII characters. You can get the archive description when you either retrieve the archive or get the vault inventory. For more information, see InitiateJob . Amazon Glacier does not interpret the description in any way. An archive description does not need to be unique. You cannot use the description to retrieve or sort the archive list.
Archives are immutable. After you upload an archive, you cannot edit the archive or its description.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and underlying REST API, see Uploading an Archive in Amazon Glacier and Upload Archive in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.upload_archive(
vaultName='string',
archiveDescription='string',
body=b'bytes'|file
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'location': 'string',
'checksum': 'string',
'archiveId': 'string'
}
Response Structure
|
Examples
The example adds an archive to a vault.
response = client.upload_archive(
accountId='-',
archiveDescription='',
body='example-data-to-upload',
checksum='',
vaultName='my-vault',
)
print(response)
Expected Output:
{
'archiveId': 'kKB7ymWJVpPSwhGP6ycSOAekp9ZYe_--zM_mw6k76ZFGEIWQX-ybtRDvc2VkPSDtfKmQrj0IRQLSGsNuDp-AJVlu2ccmDSyDUmZwKbwbpAdGATGDiB3hHO0bjbGehXTcApVud_wyDw',
'checksum': '969fb39823836d81f0cc028195fcdbcbbe76cdde932d4646fa7de5f21e18aa67',
'location': '/0123456789012/vaults/my-vault/archives/kKB7ymWJVpPSwhGP6ycSOAekp9ZYe_--zM_mw6k76ZFGEIWQX-ybtRDvc2VkPSDtfKmQrj0IRQLSGsNuDp-AJVlu2ccmDSyDUmZwKbwbpAdGATGDiB3hHO0bjbGehXTcApVud_wyDw',
'ResponseMetadata': {
'...': '...',
},
}
upload_multipart_part(**kwargs)¶This operation uploads a part of an archive. You can upload archive parts in any order. You can also upload them in parallel. You can upload up to 10,000 parts for a multipart upload.
Amazon Glacier rejects your upload part request if any of the following conditions is true:
Note
If you upload a part whose size is smaller than the part size you specified in your initiate multipart upload request and that part is not the last part, then the upload part request will succeed. However, the subsequent Complete Multipart Upload request will fail.
This operation is idempotent. If you upload the same part multiple times, the data included in the most recent request overwrites the previously uploaded data.
An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don’t have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see Access Control Using AWS Identity and Access Management (IAM) .
For conceptual information and underlying REST API, see Uploading Large Archives in Parts (Multipart Upload) and Upload Part in the Amazon Glacier Developer Guide .
See also: AWS API Documentation
Request Syntax
response = client.upload_multipart_part(
vaultName='string',
uploadId='string',
range='string',
body=b'bytes'|file
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'checksum': 'string'
}
Response Structure
|
Examples
The example uploads the first 1 MiB (1024 x 1024 bytes) part of an archive.
response = client.upload_multipart_part(
accountId='-',
body='part1',
checksum='c06f7cd4baacb087002a99a5f48bf953',
range='bytes 0-1048575/*',
uploadId='19gaRezEXAMPLES6Ry5YYdqthHOC_kGRCT03L9yetr220UmPtBYKk-OssZtLqyFu7sY1_lR7vgFuJV6NtcV5zpsJ',
vaultName='examplevault',
)
print(response)
Expected Output:
{
'checksum': 'c06f7cd4baacb087002a99a5f48bf953',
'ResponseMetadata': {
'...': '...',
},
}
The available paginators are:
Glacier.Paginator.ListJobsGlacier.Paginator.ListMultipartUploadsGlacier.Paginator.ListPartsGlacier.Paginator.ListVaultsGlacier.Paginator.ListJobs¶paginator = client.get_paginator('list_jobs')
paginate(**kwargs)¶Creates an iterator that will paginate through responses from Glacier.Client.list_jobs().
See also: AWS API Documentation
Request Syntax
response_iterator = paginator.paginate(
vaultName='string',
statuscode='string',
completed='string',
PaginationConfig={
'MaxItems': 123,
'PageSize': 123,
'StartingToken': 'string'
}
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'JobList': [
{
'JobId': 'string',
'JobDescription': 'string',
'Action': 'ArchiveRetrieval'|'InventoryRetrieval',
'ArchiveId': 'string',
'VaultARN': 'string',
'CreationDate': 'string',
'Completed': True|False,
'StatusCode': 'InProgress'|'Succeeded'|'Failed',
'StatusMessage': 'string',
'ArchiveSizeInBytes': 123,
'InventorySizeInBytes': 123,
'SNSTopic': 'string',
'CompletionDate': 'string',
'SHA256TreeHash': 'string',
'ArchiveSHA256TreeHash': 'string',
'RetrievalByteRange': 'string',
'Tier': 'string',
'InventoryRetrievalParameters': {
'Format': 'string',
'StartDate': 'string',
'EndDate': 'string',
'Limit': 'string',
'Marker': 'string'
}
},
],
'NextToken': 'string'
}
Response Structure
|
Glacier.Paginator.ListMultipartUploads¶paginator = client.get_paginator('list_multipart_uploads')
paginate(**kwargs)¶Creates an iterator that will paginate through responses from Glacier.Client.list_multipart_uploads().
See also: AWS API Documentation
Request Syntax
response_iterator = paginator.paginate(
vaultName='string',
PaginationConfig={
'MaxItems': 123,
'PageSize': 123,
'StartingToken': 'string'
}
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'UploadsList': [
{
'MultipartUploadId': 'string',
'VaultARN': 'string',
'ArchiveDescription': 'string',
'PartSizeInBytes': 123,
'CreationDate': 'string'
},
],
'NextToken': 'string'
}
Response Structure
|
Glacier.Paginator.ListParts¶paginator = client.get_paginator('list_parts')
paginate(**kwargs)¶Creates an iterator that will paginate through responses from Glacier.Client.list_parts().
See also: AWS API Documentation
Request Syntax
response_iterator = paginator.paginate(
vaultName='string',
uploadId='string',
PaginationConfig={
'MaxItems': 123,
'PageSize': 123,
'StartingToken': 'string'
}
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'MultipartUploadId': 'string',
'VaultARN': 'string',
'ArchiveDescription': 'string',
'PartSizeInBytes': 123,
'CreationDate': 'string',
'Parts': [
{
'RangeInBytes': 'string',
'SHA256TreeHash': 'string'
},
],
'NextToken': 'string'
}
Response Structure
|
Glacier.Paginator.ListVaults¶paginator = client.get_paginator('list_vaults')
paginate(**kwargs)¶Creates an iterator that will paginate through responses from Glacier.Client.list_vaults().
See also: AWS API Documentation
Request Syntax
response_iterator = paginator.paginate(
PaginationConfig={
'MaxItems': 123,
'PageSize': 123,
'StartingToken': 'string'
}
)
| Parameters: |
|
|---|---|
| Return type: | dict |
| Returns: | Response Syntax {
'VaultList': [
{
'VaultARN': 'string',
'VaultName': 'string',
'CreationDate': 'string',
'LastInventoryDate': 'string',
'NumberOfArchives': 123,
'SizeInBytes': 123
},
],
'NextToken': 'string'
}
Response Structure
|
The available waiters are:
Glacier.Waiter.VaultExists¶waiter = client.get_waiter('vault_exists')
wait(**kwargs)¶Polls Glacier.Client.describe_vault() every 3 seconds until a successful state is reached. An error is returned after 15 failed checks.
See also: AWS API Documentation
Request Syntax
waiter.wait(
vaultName='string'
)
| Parameters: |
|
|---|---|
| Returns: | None |
Glacier.Waiter.VaultNotExists¶waiter = client.get_waiter('vault_not_exists')
wait(**kwargs)¶Polls Glacier.Client.describe_vault() every 3 seconds until a successful state is reached. An error is returned after 15 failed checks.
See also: AWS API Documentation
Request Syntax
waiter.wait(
vaultName='string'
)
| Parameters: |
|
|---|---|
| Returns: | None |