Class: Aws::Glacier::Client
- Inherits:
-
Seahorse::Client::Base
- Object
- Seahorse::Client::Base
- Aws::Glacier::Client
- Includes:
- ClientStubs
- Defined in:
- gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb
Overview
An API client for Glacier. To construct a client, you need to configure a :region
and :credentials
.
client = Aws::Glacier::Client.new(
region: region_name,
credentials: credentials,
# ...
)
For details on configuring region and credentials see the developer guide.
See #initialize for a full list of supported configuration options.
Instance Attribute Summary
Attributes inherited from Seahorse::Client::Base
API Operations collapse
-
#abort_multipart_upload(params = {}) ⇒ Struct
This operation aborts a multipart upload identified by the upload ID.
-
#abort_vault_lock(params = {}) ⇒ Struct
This operation aborts the vault locking process if the vault lock is not in the
Locked
state. -
#add_tags_to_vault(params = {}) ⇒ Struct
This operation adds the specified tags to a vault.
-
#complete_multipart_upload(params = {}) ⇒ Types::ArchiveCreationOutput
You call this operation to inform Amazon S3 Glacier (Glacier) that all the archive parts have been uploaded and that Glacier can now assemble the archive from the uploaded parts.
-
#complete_vault_lock(params = {}) ⇒ Struct
This operation completes the vault locking process by transitioning the vault lock from the
InProgress
state to theLocked
state, which causes the vault lock policy to become unchangeable. -
#create_vault(params = {}) ⇒ Types::CreateVaultOutput
This operation creates a new vault with the specified name.
-
#delete_archive(params = {}) ⇒ Struct
This operation deletes an archive from a vault.
-
#delete_vault(params = {}) ⇒ Struct
This operation deletes a vault.
-
#delete_vault_access_policy(params = {}) ⇒ Struct
This operation deletes the access policy associated with the specified vault.
-
#delete_vault_notifications(params = {}) ⇒ Struct
This operation deletes the notification configuration set for a vault.
-
#describe_job(params = {}) ⇒ Types::GlacierJobDescription
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 S3 Glacier (Glacier) completes the job.
-
#describe_vault(params = {}) ⇒ Types::DescribeVaultOutput
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.
-
#get_data_retrieval_policy(params = {}) ⇒ Types::GetDataRetrievalPolicyOutput
This operation returns the current data retrieval policy for the account and region specified in the GET request.
-
#get_job_output(params = {}) ⇒ Types::GetJobOutputOutput
This operation downloads the output of the job you initiated using InitiateJob.
-
#get_vault_access_policy(params = {}) ⇒ Types::GetVaultAccessPolicyOutput
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)][1]. -
#get_vault_lock(params = {}) ⇒ Types::GetVaultLockOutput
This operation retrieves the following attributes from the
lock-policy
subresource set on the specified vault:. -
#get_vault_notifications(params = {}) ⇒ Types::GetVaultNotificationsOutput
This operation retrieves the
notification-configuration
subresource of the specified vault. -
#initiate_job(params = {}) ⇒ Types::InitiateJobOutput
This operation initiates a job of the specified type, which can be a select, an archival retrieval, or a vault retrieval.
-
#initiate_multipart_upload(params = {}) ⇒ Types::InitiateMultipartUploadOutput
This operation initiates a multipart upload.
-
#initiate_vault_lock(params = {}) ⇒ Types::InitiateVaultLockOutput
This operation initiates the vault locking process by doing the following:.
-
#list_jobs(params = {}) ⇒ Types::ListJobsOutput
This operation lists jobs for a vault, including jobs that are in-progress and jobs that have recently finished.
-
#list_multipart_uploads(params = {}) ⇒ Types::ListMultipartUploadsOutput
This operation lists in-progress multipart uploads for the specified vault.
-
#list_parts(params = {}) ⇒ Types::ListPartsOutput
This operation lists the parts of an archive that have been uploaded in a specific multipart upload.
-
#list_provisioned_capacity(params = {}) ⇒ Types::ListProvisionedCapacityOutput
This operation lists the provisioned capacity units for the specified AWS account.
-
#list_tags_for_vault(params = {}) ⇒ Types::ListTagsForVaultOutput
This operation lists all the tags attached to a vault.
-
#list_vaults(params = {}) ⇒ Types::ListVaultsOutput
This operation lists all vaults owned by the calling user's account.
-
#purchase_provisioned_capacity(params = {}) ⇒ Types::PurchaseProvisionedCapacityOutput
This operation purchases a provisioned capacity unit for an AWS account.
-
#remove_tags_from_vault(params = {}) ⇒ Struct
This operation removes one or more tags from the set of tags attached to a vault.
-
#set_data_retrieval_policy(params = {}) ⇒ Struct
This operation sets and then enacts a data retrieval policy in the region specified in the PUT request.
-
#set_vault_access_policy(params = {}) ⇒ Struct
This operation configures an access policy for a vault and will overwrite an existing policy.
-
#set_vault_notifications(params = {}) ⇒ Struct
This operation configures notifications that will be sent when specific events happen to a vault.
-
#upload_archive(params = {}) ⇒ Types::ArchiveCreationOutput
This operation adds an archive to a vault.
-
#upload_multipart_part(params = {}) ⇒ Types::UploadMultipartPartOutput
This operation uploads a part of an archive.
Instance Method Summary collapse
-
#initialize(options) ⇒ Client
constructor
A new instance of Client.
-
#wait_until(waiter_name, params = {}, options = {}) {|w.waiter| ... } ⇒ Boolean
Polls an API operation until a resource enters a desired state.
Methods included from ClientStubs
#api_requests, #stub_data, #stub_responses
Methods inherited from Seahorse::Client::Base
add_plugin, api, clear_plugins, define, new, #operation_names, plugins, remove_plugin, set_api, set_plugins
Methods included from Seahorse::Client::HandlerBuilder
#handle, #handle_request, #handle_response
Constructor Details
#initialize(options) ⇒ Client
Returns a new instance of Client.
433 434 435 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 433 def initialize(*args) super end |
Instance Method Details
#abort_multipart_upload(params = {}) ⇒ Struct
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 S3 Glacier and Abort Multipart Upload in the Amazon Glacier Developer Guide.
503 504 505 506 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 503 def abort_multipart_upload(params = {}, = {}) req = build_request(:abort_multipart_upload, params) req.send_request() end |
#abort_vault_lock(params = {}) ⇒ Struct
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.
565 566 567 568 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 565 def abort_vault_lock(params = {}, = {}) req = build_request(:abort_vault_lock, params) req.send_request() end |
#add_tags_to_vault(params = {}) ⇒ Struct
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 S3 Glacier Resources.
625 626 627 628 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 625 def (params = {}, = {}) req = build_request(:add_tags_to_vault, params) req.send_request() end |
#complete_multipart_upload(params = {}) ⇒ Types::ArchiveCreationOutput
You call this operation to inform Amazon S3 Glacier (Glacier) that all the archive parts have been uploaded and that Glacier can now assemble the archive from the uploaded parts. After assembling and saving the archive to the vault, 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, Glacier also constructs the SHA256 tree hash of the assembled archive. If the values match, 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, Glacier also checks for any missing content ranges when assembling the archive, if missing content ranges are found, 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.
752 753 754 755 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 752 def complete_multipart_upload(params = {}, = {}) req = build_request(:complete_multipart_upload, params) req.send_request() end |
#complete_vault_lock(params = {}) ⇒ Struct
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.
819 820 821 822 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 819 def complete_vault_lock(params = {}, = {}) req = build_request(:complete_vault_lock, params) req.send_request() end |
#create_vault(params = {}) ⇒ Types::CreateVaultOutput
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 S3 Glacier.
You must use the following guidelines when naming a vault.
Names can be between 1 and 255 characters long.
Allowed characters are a-z, A-Z, 0-9, '_' (underscore), '-' (hyphen), and '.' (period).
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.
898 899 900 901 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 898 def create_vault(params = {}, = {}) req = build_request(:create_vault, params) req.send_request() end |
#delete_archive(params = {}) ⇒ Struct
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:
If the archive retrieval job is actively preparing the data for download when Amazon S3 Glacier receives the delete archive request, the archival retrieval operation might fail.
If the archive retrieval job has successfully prepared the archive for download when Amazon S3 Glacier receives the delete archive request, you will be able to download the output.
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.
972 973 974 975 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 972 def delete_archive(params = {}, = {}) req = build_request(:delete_archive, params) req.send_request() end |
#delete_vault(params = {}) ⇒ Struct
This operation deletes a vault. Amazon S3 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 S3 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 S3 Glacier Developer Guide.
1040 1041 1042 1043 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 1040 def delete_vault(params = {}, = {}) req = build_request(:delete_vault, params) req.send_request() end |
#delete_vault_access_policy(params = {}) ⇒ Struct
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 S3 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.
1092 1093 1094 1095 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 1092 def delete_vault_access_policy(params = {}, = {}) req = build_request(:delete_vault_access_policy, params) req.send_request() end |
#delete_vault_notifications(params = {}) ⇒ Struct
This operation deletes the notification configuration set for a vault. The operation is eventually consistent; that is, it might take some time for Amazon S3 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 S3 Glacier and Delete Vault Notification Configuration in the Amazon S3 Glacier Developer Guide.
1152 1153 1154 1155 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 1152 def delete_vault_notifications(params = {}, = {}) req = build_request(:delete_vault_notifications, params) req.send_request() end |
#describe_job(params = {}) ⇒ Types::GlacierJobDescription
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 S3 Glacier (Glacier) completes the job. For more information about initiating a job, see InitiateJob.
A job ID will not expire for at least 24 hours after 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 more information about using this operation, see the documentation for the underlying REST API Describe Job in the Amazon Glacier Developer Guide.
1317 1318 1319 1320 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 1317 def describe_job(params = {}, = {}) req = build_request(:describe_job, params) req.send_request() end |
#describe_vault(params = {}) ⇒ Types::DescribeVaultOutput
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 S3 Glacier generates vault inventories approximately daily. For more information, see Downloading a Vault Inventory in Amazon S3 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 S3 Glacier and Describe Vault in the Amazon Glacier Developer Guide.
The following waiters are defined for this operation (see #wait_until for detailed usage):
- vault_exists
- vault_not_exists
1414 1415 1416 1417 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 1414 def describe_vault(params = {}, = {}) req = build_request(:describe_vault, params) req.send_request() end |
#get_data_retrieval_policy(params = {}) ⇒ Types::GetDataRetrievalPolicyOutput
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.
1476 1477 1478 1479 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 1476 def get_data_retrieval_policy(params = {}, = {}) req = build_request(:get_data_retrieval_policy, params) req.send_request() end |
#get_job_output(params = {}) ⇒ Types::GetJobOutputOutput
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 S3 Glacier (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 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 S3 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, 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 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
1632 1633 1634 1635 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 1632 def get_job_output(params = {}, = {}, &block) req = build_request(:get_job_output, params) req.send_request(, &block) end |
#get_vault_access_policy(params = {}) ⇒ Types::GetVaultAccessPolicyOutput
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.
1694 1695 1696 1697 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 1694 def get_vault_access_policy(params = {}, = {}) req = build_request(:get_vault_access_policy, params) req.send_request() end |
#get_vault_lock(params = {}) ⇒ Types::GetVaultLockOutput
This operation retrieves the following attributes from the
lock-policy
subresource set on the specified vault:
The vault lock policy set on the vault.
The state of the vault lock, which is either
InProgess
orLocked
.When the lock ID expires. The lock ID is used to complete the vault locking process.
When the vault lock was initiated and put into the
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.
1780 1781 1782 1783 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 1780 def get_vault_lock(params = {}, = {}) req = build_request(:get_vault_lock, params) req.send_request() end |
#get_vault_notifications(params = {}) ⇒ Types::GetVaultNotificationsOutput
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 S3 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 S3 Glacier and Get Vault Notification Configuration in the Amazon Glacier Developer Guide.
1862 1863 1864 1865 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 1862 def get_vault_notifications(params = {}, = {}) req = build_request(:get_vault_notifications, params) req.send_request() end |
#initiate_job(params = {}) ⇒ Types::InitiateJobOutput
This operation initiates a job of the specified type, which can be a select, an archival retrieval, or a vault retrieval. For more information about using this operation, see the documentation for the underlying REST API Initiate a Job.
2002 2003 2004 2005 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 2002 def initiate_job(params = {}, = {}) req = build_request(:initiate_job, params) req.send_request() end |
#initiate_multipart_upload(params = {}) ⇒ Types::InitiateMultipartUploadOutput
This operation initiates a multipart upload. Amazon S3 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.
After you complete the multipart upload, Amazon S3 Glacier (Glacier) removes the multipart upload resource referenced by the ID. 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.
2114 2115 2116 2117 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 2114 def initiate_multipart_upload(params = {}, = {}) req = build_request(:initiate_multipart_upload, params) req.send_request() end |
#initiate_vault_lock(params = {}) ⇒ Types::InitiateVaultLockOutput
This operation initiates the vault locking process by doing the following:
Installing a vault lock policy on the specified vault.
Setting the lock state of vault lock to
InProgress
.Returning a lock ID, which is used to complete the vault locking process.
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.
2213 2214 2215 2216 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 2213 def initiate_vault_lock(params = {}, = {}) req = build_request(:initiate_vault_lock, params) req.send_request() end |
#list_jobs(params = {}) ⇒ Types::ListJobsOutput
This operation lists jobs for a vault, including jobs that are in-progress and jobs that have recently finished. 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 50. 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 more information about using this operation, see the documentation for the underlying REST API List Jobs.
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
2415 2416 2417 2418 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 2415 def list_jobs(params = {}, = {}) req = build_request(:list_jobs, params) req.send_request() end |
#list_multipart_uploads(params = {}) ⇒ Types::ListMultipartUploadsOutput
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 50 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 S3 Glacier and List Multipart Uploads in the Amazon Glacier Developer Guide.
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
2547 2548 2549 2550 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 2547 def list_multipart_uploads(params = {}, = {}) req = build_request(:list_multipart_uploads, params) req.send_request() end |
#list_parts(params = {}) ⇒ Types::ListPartsOutput
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 50 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 S3 Glacier and List Parts in the Amazon Glacier Developer Guide.
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
2677 2678 2679 2680 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 2677 def list_parts(params = {}, = {}) req = build_request(:list_parts, params) req.send_request() end |
#list_provisioned_capacity(params = {}) ⇒ Types::ListProvisionedCapacityOutput
This operation lists the provisioned capacity units for the specified AWS account.
2736 2737 2738 2739 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 2736 def list_provisioned_capacity(params = {}, = {}) req = build_request(:list_provisioned_capacity, params) req.send_request() end |
#list_tags_for_vault(params = {}) ⇒ Types::ListTagsForVaultOutput
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 S3 Glacier Resources.
2796 2797 2798 2799 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 2796 def (params = {}, = {}) req = build_request(:list_tags_for_vault, params) req.send_request() end |
#list_vaults(params = {}) ⇒ Types::ListVaultsOutput
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 10 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 S3 Glacier and List Vaults in the Amazon Glacier Developer Guide.
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
2900 2901 2902 2903 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 2900 def list_vaults(params = {}, = {}) req = build_request(:list_vaults, params) req.send_request() end |
#purchase_provisioned_capacity(params = {}) ⇒ Types::PurchaseProvisionedCapacityOutput
This operation purchases a provisioned capacity unit for an AWS account.
2945 2946 2947 2948 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 2945 def purchase_provisioned_capacity(params = {}, = {}) req = build_request(:purchase_provisioned_capacity, params) req.send_request() end |
#remove_tags_from_vault(params = {}) ⇒ Struct
This operation removes one or more tags from the set of tags attached to a vault. For more information about tags, see Tagging Amazon S3 Glacier Resources. This operation is idempotent. The operation will be successful, even if there are no tags attached to the vault.
2999 3000 3001 3002 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 2999 def (params = {}, = {}) req = build_request(:remove_tags_from_vault, params) req.send_request() end |
#set_data_retrieval_policy(params = {}) ⇒ Struct
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.
3065 3066 3067 3068 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 3065 def set_data_retrieval_policy(params = {}, = {}) req = build_request(:set_data_retrieval_policy, params) req.send_request() end |
#set_vault_access_policy(params = {}) ⇒ Struct
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.
3124 3125 3126 3127 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 3124 def set_vault_access_policy(params = {}, = {}) req = build_request(:set_vault_access_policy, params) req.send_request() end |
#set_vault_notifications(params = {}) ⇒ Struct
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 S3 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:
ArchiveRetrievalCompleted This event occurs when a job that was initiated for an archive retrieval is completed (InitiateJob). The status of the completed job can be "Succeeded" or "Failed". The notification sent to the SNS topic is the same output as returned from DescribeJob.
InventoryRetrievalCompleted This event occurs when a job that was initiated for an inventory retrieval is completed (InitiateJob). The status of the completed job can be "Succeeded" or "Failed". The notification sent to the SNS topic is the same output as returned from DescribeJob.
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 S3 Glacier and Set Vault Notification Configuration in the Amazon Glacier Developer Guide.
3218 3219 3220 3221 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 3218 def set_vault_notifications(params = {}, = {}) req = build_request(:set_vault_notifications, params) req.send_request() end |
#upload_archive(params = {}) ⇒ Types::ArchiveCreationOutput
This operation adds an archive to a vault. This is a synchronous
operation, and for a successful upload, your data is durably
persisted. Amazon S3 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 S3 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.
3334 3335 3336 3337 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 3334 def upload_archive(params = {}, = {}) req = build_request(:upload_archive, params) req.send_request() end |
#upload_multipart_part(params = {}) ⇒ Types::UploadMultipartPartOutput
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:
SHA256 tree hash does not matchTo ensure that part data is not corrupted in transmission, you compute a SHA256 tree hash of the part and include it in your request. Upon receiving the part data, Amazon S3 Glacier also computes a SHA256 tree hash. If these hash values don't match, the operation fails. For information about computing a SHA256 tree hash, see Computing Checksums.
Part size does not matchThe size of each part except the last must match the size specified in the corresponding InitiateMultipartUpload request. The size of the last part must be the same size as, or smaller than, the specified size.
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. Range does not alignThe byte range value in the request does not align with the part size specified in the corresponding initiate request. For example, if you specify a part size of 4194304 bytes (4 MB), then 0 to 4194303 bytes (4 MB - 1) and 4194304 (4 MB) to 8388607 (8 MB - 1) are valid part ranges. However, if you set a range value of 2 MB to 6 MB, the range does not align with the part size and the upload 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.
3461 3462 3463 3464 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 3461 def upload_multipart_part(params = {}, = {}) req = build_request(:upload_multipart_part, params) req.send_request() end |
#wait_until(waiter_name, params = {}, options = {}) {|w.waiter| ... } ⇒ Boolean
Polls an API operation until a resource enters a desired state.
Basic Usage
A waiter will call an API operation until:
- It is successful
- It enters a terminal state
- It makes the maximum number of attempts
In between attempts, the waiter will sleep.
# polls in a loop, sleeping between attempts
client.wait_until(waiter_name, params)
Configuration
You can configure the maximum number of polling attempts, and the delay (in seconds) between each polling attempt. You can pass configuration as the final arguments hash.
# poll for ~25 seconds
client.wait_until(waiter_name, params, {
max_attempts: 5,
delay: 5,
})
Callbacks
You can be notified before each polling attempt and before each
delay. If you throw :success
or :failure
from these callbacks,
it will terminate the waiter.
started_at = Time.now
client.wait_until(waiter_name, params, {
# disable max attempts
max_attempts: nil,
# poll for 1 hour, instead of a number of attempts
before_wait: -> (attempts, response) do
throw :failure if Time.now - started_at > 3600
end
})
Handling Errors
When a waiter is unsuccessful, it will raise an error. All of the failure errors extend from Waiters::Errors::WaiterFailed.
begin
client.wait_until(...)
rescue Aws::Waiters::Errors::WaiterFailed
# resource did not enter the desired state in time
end
Valid Waiters
The following table lists the valid waiter names, the operations they call,
and the default :delay
and :max_attempts
values.
waiter_name | params | :delay | :max_attempts |
---|---|---|---|
vault_exists | #describe_vault | 3 | 15 |
vault_not_exists | #describe_vault | 3 | 15 |
3572 3573 3574 3575 3576 |
# File 'gems/aws-sdk-glacier/lib/aws-sdk-glacier/client.rb', line 3572 def wait_until(waiter_name, params = {}, = {}) w = waiter(waiter_name, ) yield(w.waiter) if block_given? # deprecated w.wait(params) end |