blib/lib/Paws/Glacier.pm

filter: Statementstmt 58.8% 110 / 187 Branchbran 2.9% 1 / 34 Conditioncond 33.3% 1 / 3 MC/DCmcdc 0.0% 0 / 2 Subroutinesub 84.7% 39 / 46 Podpod 88.1% 37 / 42 totaltotal 59.8% 188 / 314 CC 27 SCAR 31.2
CC
27
Cov
50%
ListAllJobs
56.0
ListAllMultipartUploads
56.0
ListAllParts
56.0
CRAP 22.6
« blib/lib/Paws/ElasticBeanstalk.pm ↑ Summary blib/lib/Paws/Support.pm »
1 package Paws::Glacier;
2 5 ▶ use Moose;
Subroutine BEGIN: called CC=1 SCAR=0.0
3 11 ▶ sub service { 'glacier' }
Subroutine service: called CC=1 SCAR=0.0
Pod undocumented
4 40 ▶ sub signing_name { 'glacier' }
Subroutine signing_name: called CC=1 SCAR=0.0
Pod undocumented
5 41 ▶ sub version { '2012-06-01' }
Subroutine version: called CC=1 SCAR=0.0
Pod undocumented
6 0 ▶ sub flattened_arrays { 0 }
Subroutine flattened_arrays: not called CC=1 SCAR=6.9
Pod undocumented
7 5 has max_attempts => (is => 'ro', isa => 'Int', default => 5);
8 11 ▶ has retry => (is => 'ro', isa => 'HashRef', default => sub {
Subroutine __ANON__: called CC=1 SCAR=0.0
9 11 { base => 'rand', type => 'exponential', growth_factor => 2 }
10 5 });
11 11 ▶ has retriables => (is => 'ro', isa => 'ArrayRef', default => sub { [
Subroutine __ANON__: called CC=1 SCAR=0.5
12 4 ▶ sub { defined $_[0]->http_status and $_[0]->http_status == 408 and $_[0]->code eq 'RequestTimeoutException' },
Subroutine __ANON__: called CC=3 SCAR=14.2
Branch: 1 branch
BranchTrueFalseTotal
defined $_[0]->http_status and $_[0]->http_status == 408 and $_[0]->code eq "RequestTimeoutException" 0 4 4
Condition33%1/3
defined $_[0]->http_status and $_[0]->http_status == 408
!ll&&!rl&&r
040
MC/DC0%0/2
defined $_[0]->http_status and $_[0]->http_status == 408
defined $_[0]->http_status $_[0]->http_status == 408
Truth table33%1/3
A and B
A= defined $_[0]->http_statusB= $_[0]->http_status == 408
ABresult
0X0
100
111
13 11 ] });
14  
15 5 with 'Paws::API::Caller', 'Paws::API::EndpointResolver', 'Paws::Net::V4Signature', 'Paws::Net::GlacierCaller';
16  
17
18 1 ▶ sub AbortMultipartUpload {
Subroutine AbortMultipartUpload: called CC=1 SCAR=0.0
Pod documented
19 1 my $self = shift;
20 1 my $call_object = $self->new_with_coercions('Paws::Glacier::AbortMultipartUpload', @_);
21 1 return $self->caller->do_call($self, $call_object);
22 }
23 1 ▶ sub AbortVaultLock {
Subroutine AbortVaultLock: called CC=1 SCAR=0.0
Pod documented
24 1 my $self = shift;
25 1 my $call_object = $self->new_with_coercions('Paws::Glacier::AbortVaultLock', @_);
26 1 return $self->caller->do_call($self, $call_object);
27 }
28 2 ▶ sub AddTagsToVault {
Subroutine AddTagsToVault: called CC=1 SCAR=0.0
Pod documented
29 2 my $self = shift;
30 2 my $call_object = $self->new_with_coercions('Paws::Glacier::AddTagsToVault', @_);
31 2 return $self->caller->do_call($self, $call_object);
32 }
33 2 ▶ sub CompleteMultipartUpload {
Subroutine CompleteMultipartUpload: called CC=1 SCAR=0.0
Pod documented
34 2 my $self = shift;
35 2 my $call_object = $self->new_with_coercions('Paws::Glacier::CompleteMultipartUpload', @_);
36 2 return $self->caller->do_call($self, $call_object);
37 }
38 0 ▶ sub CompleteVaultLock {
Subroutine CompleteVaultLock: not called CC=1 SCAR=6.9
Pod documented
39 0 my $self = shift;
40 0 my $call_object = $self->new_with_coercions('Paws::Glacier::CompleteVaultLock', @_);
41 0 return $self->caller->do_call($self, $call_object);
42 }
43 3 ▶ sub CreateVault {
Subroutine CreateVault: called CC=1 SCAR=0.0
Pod documented
44 3 my $self = shift;
45 3 my $call_object = $self->new_with_coercions('Paws::Glacier::CreateVault', @_);
46 3 return $self->caller->do_call($self, $call_object);
47 }
48 1 ▶ sub DeleteArchive {
Subroutine DeleteArchive: called CC=1 SCAR=0.0
Pod documented
49 1 my $self = shift;
50 1 my $call_object = $self->new_with_coercions('Paws::Glacier::DeleteArchive', @_);
51 1 return $self->caller->do_call($self, $call_object);
52 }
53 2 ▶ sub DeleteVault {
Subroutine DeleteVault: called CC=1 SCAR=0.0
Pod documented
54 2 my $self = shift;
55 2 my $call_object = $self->new_with_coercions('Paws::Glacier::DeleteVault', @_);
56 2 return $self->caller->do_call($self, $call_object);
57 }
58 1 ▶ sub DeleteVaultAccessPolicy {
Subroutine DeleteVaultAccessPolicy: called CC=1 SCAR=0.0
Pod documented
59 1 my $self = shift;
60 1 my $call_object = $self->new_with_coercions('Paws::Glacier::DeleteVaultAccessPolicy', @_);
61 1 return $self->caller->do_call($self, $call_object);
62 }
63 1 ▶ sub DeleteVaultNotifications {
Subroutine DeleteVaultNotifications: called CC=1 SCAR=0.0
Pod documented
64 1 my $self = shift;
65 1 my $call_object = $self->new_with_coercions('Paws::Glacier::DeleteVaultNotifications', @_);
66 1 return $self->caller->do_call($self, $call_object);
67 }
68 1 ▶ sub DescribeJob {
Subroutine DescribeJob: called CC=1 SCAR=0.0
Pod documented
69 1 my $self = shift;
70 1 my $call_object = $self->new_with_coercions('Paws::Glacier::DescribeJob', @_);
71 1 return $self->caller->do_call($self, $call_object);
72 }
73 2 ▶ sub DescribeVault {
Subroutine DescribeVault: called CC=1 SCAR=0.0
Pod documented
74 2 my $self = shift;
75 2 my $call_object = $self->new_with_coercions('Paws::Glacier::DescribeVault', @_);
76 2 return $self->caller->do_call($self, $call_object);
77 }
78 1 ▶ sub GetDataRetrievalPolicy {
Subroutine GetDataRetrievalPolicy: called CC=1 SCAR=0.0
Pod documented
79 1 my $self = shift;
80 1 my $call_object = $self->new_with_coercions('Paws::Glacier::GetDataRetrievalPolicy', @_);
81 1 return $self->caller->do_call($self, $call_object);
82 }
83 1 ▶ sub GetJobOutput {
Subroutine GetJobOutput: called CC=1 SCAR=0.0
Pod documented
84 1 my $self = shift;
85 1 my $call_object = $self->new_with_coercions('Paws::Glacier::GetJobOutput', @_);
86 1 return $self->caller->do_call($self, $call_object);
87 }
88 1 ▶ sub GetVaultAccessPolicy {
Subroutine GetVaultAccessPolicy: called CC=1 SCAR=0.0
Pod documented
89 1 my $self = shift;
90 1 my $call_object = $self->new_with_coercions('Paws::Glacier::GetVaultAccessPolicy', @_);
91 1 return $self->caller->do_call($self, $call_object);
92 }
93 1 ▶ sub GetVaultLock {
Subroutine GetVaultLock: called CC=1 SCAR=0.0
Pod documented
94 1 my $self = shift;
95 1 my $call_object = $self->new_with_coercions('Paws::Glacier::GetVaultLock', @_);
96 1 return $self->caller->do_call($self, $call_object);
97 }
98 1 ▶ sub GetVaultNotifications {
Subroutine GetVaultNotifications: called CC=1 SCAR=0.0
Pod documented
99 1 my $self = shift;
100 1 my $call_object = $self->new_with_coercions('Paws::Glacier::GetVaultNotifications', @_);
101 1 return $self->caller->do_call($self, $call_object);
102 }
103 1 ▶ sub InitiateJob {
Subroutine InitiateJob: called CC=1 SCAR=0.0
Pod documented
104 1 my $self = shift;
105 1 my $call_object = $self->new_with_coercions('Paws::Glacier::InitiateJob', @_);
106 1 return $self->caller->do_call($self, $call_object);
107 }
108 3 ▶ sub InitiateMultipartUpload {
Subroutine InitiateMultipartUpload: called CC=1 SCAR=0.0
Pod documented
109 3 my $self = shift;
110 3 my $call_object = $self->new_with_coercions('Paws::Glacier::InitiateMultipartUpload', @_);
111 3 return $self->caller->do_call($self, $call_object);
112 }
113 1 ▶ sub InitiateVaultLock {
Subroutine InitiateVaultLock: called CC=1 SCAR=0.0
Pod documented
114 1 my $self = shift;
115 1 my $call_object = $self->new_with_coercions('Paws::Glacier::InitiateVaultLock', @_);
116 1 return $self->caller->do_call($self, $call_object);
117 }
118 1 ▶ sub ListJobs {
Subroutine ListJobs: called CC=1 SCAR=0.0
Pod documented
119 1 my $self = shift;
120 1 my $call_object = $self->new_with_coercions('Paws::Glacier::ListJobs', @_);
121 1 return $self->caller->do_call($self, $call_object);
122 }
123 1 ▶ sub ListMultipartUploads {
Subroutine ListMultipartUploads: called CC=1 SCAR=0.0
Pod documented
124 1 my $self = shift;
125 1 my $call_object = $self->new_with_coercions('Paws::Glacier::ListMultipartUploads', @_);
126 1 return $self->caller->do_call($self, $call_object);
127 }
128 1 ▶ sub ListParts {
Subroutine ListParts: called CC=1 SCAR=0.0
Pod documented
129 1 my $self = shift;
130 1 my $call_object = $self->new_with_coercions('Paws::Glacier::ListParts', @_);
131 1 return $self->caller->do_call($self, $call_object);
132 }
133 1 ▶ sub ListProvisionedCapacity {
Subroutine ListProvisionedCapacity: called CC=1 SCAR=0.0
Pod documented
134 1 my $self = shift;
135 1 my $call_object = $self->new_with_coercions('Paws::Glacier::ListProvisionedCapacity', @_);
136 1 return $self->caller->do_call($self, $call_object);
137 }
138 2 ▶ sub ListTagsForVault {
Subroutine ListTagsForVault: called CC=1 SCAR=0.0
Pod documented
139 2 my $self = shift;
140 2 my $call_object = $self->new_with_coercions('Paws::Glacier::ListTagsForVault', @_);
141 2 return $self->caller->do_call($self, $call_object);
142 }
143 5 ▶ sub ListVaults {
Subroutine ListVaults: called CC=1 SCAR=0.0
Pod documented
144 5 my $self = shift;
145 5 my $call_object = $self->new_with_coercions('Paws::Glacier::ListVaults', @_);
146 5 return $self->caller->do_call($self, $call_object);
147 }
148 1 ▶ sub PurchaseProvisionedCapacity {
Subroutine PurchaseProvisionedCapacity: called CC=1 SCAR=0.0
Pod documented
149 1 my $self = shift;
150 1 my $call_object = $self->new_with_coercions('Paws::Glacier::PurchaseProvisionedCapacity', @_);
151 1 return $self->caller->do_call($self, $call_object);
152 }
153 1 ▶ sub RemoveTagsFromVault {
Subroutine RemoveTagsFromVault: called CC=1 SCAR=0.0
Pod documented
154 1 my $self = shift;
155 1 my $call_object = $self->new_with_coercions('Paws::Glacier::RemoveTagsFromVault', @_);
156 1 return $self->caller->do_call($self, $call_object);
157 }
158 1 ▶ sub SetDataRetrievalPolicy {
Subroutine SetDataRetrievalPolicy: called CC=1 SCAR=0.0
Pod documented
159 1 my $self = shift;
160 1 my $call_object = $self->new_with_coercions('Paws::Glacier::SetDataRetrievalPolicy', @_);
161 1 return $self->caller->do_call($self, $call_object);
162 }
163 1 ▶ sub SetVaultAccessPolicy {
Subroutine SetVaultAccessPolicy: called CC=1 SCAR=0.0
Pod documented
164 1 my $self = shift;
165 1 my $call_object = $self->new_with_coercions('Paws::Glacier::SetVaultAccessPolicy', @_);
166 1 return $self->caller->do_call($self, $call_object);
167 }
168 1 ▶ sub SetVaultNotifications {
Subroutine SetVaultNotifications: called CC=1 SCAR=0.0
Pod documented
169 1 my $self = shift;
170 1 my $call_object = $self->new_with_coercions('Paws::Glacier::SetVaultNotifications', @_);
171 1 return $self->caller->do_call($self, $call_object);
172 }
173 1 ▶ sub UploadArchive {
Subroutine UploadArchive: called CC=1 SCAR=0.0
Pod documented
174 1 my $self = shift;
175 1 my $call_object = $self->new_with_coercions('Paws::Glacier::UploadArchive', @_);
176 1 return $self->caller->do_call($self, $call_object);
177 }
178 2 ▶ sub UploadMultipartPart {
Subroutine UploadMultipartPart: called CC=1 SCAR=0.0
Pod documented
179 2 my $self = shift;
180 2 my $call_object = $self->new_with_coercions('Paws::Glacier::UploadMultipartPart', @_);
181 2 return $self->caller->do_call($self, $call_object);
182 }
183
184 0 ▶ sub ListAllJobs {
Subroutine ListAllJobs: not called CC=7 SCAR=40.3
Pod documented
185 0 my $self = shift;
186  
187 0 ▶ my $callback = shift @_ if (ref($_[0]) eq 'CODE');
Branch: 1 branch
BranchTrueFalseTotal
if ref $_[0] eq "CODE" 0 0 0
188 0 my $result = $self->ListJobs(@_);
189 0 my $next_result = $result;
190  
191 0 ▶ if (not defined $callback) {
Branch: 1 branch
BranchTrueFalseTotal
if (not defined $callback) { } 0 0 0
192 0 ▶ while ($next_result->Marker) {
Branch: 1 branch
BranchTrueFalseTotal
if ($next_result->Marker) 0 0 0
193 0 $next_result = $self->ListJobs(@_, marker => $next_result->Marker);
194 0 push @{ $result->JobList }, @{ $next_result->JobList };
195 }
196 0 return $result;
197 } else {
198 0 ▶ while ($result->Marker) {
Branch: 1 branch
BranchTrueFalseTotal
if ($result->Marker) 0 0 0
199 0 $callback->($_ => 'JobList') foreach (@{ $result->JobList });
200 0 $result = $self->ListJobs(@_, marker => $result->Marker);
201 }
202 0 $callback->($_ => 'JobList') foreach (@{ $result->JobList });
203 }
204  
205 return undef
206 0 }
207 0 ▶ sub ListAllMultipartUploads {
Subroutine ListAllMultipartUploads: not called CC=7 SCAR=40.3
Pod documented
208 0 my $self = shift;
209  
210 0 ▶ my $callback = shift @_ if (ref($_[0]) eq 'CODE');
Branch: 1 branch
BranchTrueFalseTotal
if ref $_[0] eq "CODE" 0 0 0
211 0 my $result = $self->ListMultipartUploads(@_);
212 0 my $next_result = $result;
213  
214 0 ▶ if (not defined $callback) {
Branch: 1 branch
BranchTrueFalseTotal
if (not defined $callback) { } 0 0 0
215 0 ▶ while ($next_result->Marker) {
Branch: 1 branch
BranchTrueFalseTotal
if ($next_result->Marker) 0 0 0
216 0 $next_result = $self->ListMultipartUploads(@_, marker => $next_result->Marker);
217 0 push @{ $result->UploadsList }, @{ $next_result->UploadsList };
218 }
219 0 return $result;
220 } else {
221 0 ▶ while ($result->Marker) {
Branch: 1 branch
BranchTrueFalseTotal
if ($result->Marker) 0 0 0
222 0 $callback->($_ => 'UploadsList') foreach (@{ $result->UploadsList });
223 0 $result = $self->ListMultipartUploads(@_, marker => $result->Marker);
224 }
225 0 $callback->($_ => 'UploadsList') foreach (@{ $result->UploadsList });
226 }
227  
228 return undef
229 0 }
230 0 ▶ sub ListAllParts {
Subroutine ListAllParts: not called CC=7 SCAR=40.3
Pod documented
231 0 my $self = shift;
232  
233 0 ▶ my $callback = shift @_ if (ref($_[0]) eq 'CODE');
Branch: 1 branch
BranchTrueFalseTotal
if ref $_[0] eq "CODE" 0 0 0
234 0 my $result = $self->ListParts(@_);
235 0 my $next_result = $result;
236  
237 0 ▶ if (not defined $callback) {
Branch: 1 branch
BranchTrueFalseTotal
if (not defined $callback) { } 0 0 0
238 0 ▶ while ($next_result->Marker) {
Branch: 1 branch
BranchTrueFalseTotal
if ($next_result->Marker) 0 0 0
239 0 $next_result = $self->ListParts(@_, marker => $next_result->Marker);
240 0 push @{ $result->Parts }, @{ $next_result->Parts };
241 }
242 0 return $result;
243 } else {
244 0 ▶ while ($result->Marker) {
Branch: 1 branch
BranchTrueFalseTotal
if ($result->Marker) 0 0 0
245 0 $callback->($_ => 'Parts') foreach (@{ $result->Parts });
246 0 $result = $self->ListParts(@_, marker => $result->Marker);
247 }
248 0 $callback->($_ => 'Parts') foreach (@{ $result->Parts });
249 }
250  
251 return undef
252 0 }
253 0 ▶ sub ListAllVaults {
Subroutine ListAllVaults: not called CC=7 SCAR=40.3
Pod documented
254 0 my $self = shift;
255  
256 0 ▶ my $callback = shift @_ if (ref($_[0]) eq 'CODE');
Branch: 1 branch
BranchTrueFalseTotal
if ref $_[0] eq "CODE" 0 0 0
257 0 my $result = $self->ListVaults(@_);
258 0 my $next_result = $result;
259  
260 0 ▶ if (not defined $callback) {
Branch: 1 branch
BranchTrueFalseTotal
if (not defined $callback) { } 0 0 0
261 0 ▶ while ($next_result->Marker) {
Branch: 1 branch
BranchTrueFalseTotal
if ($next_result->Marker) 0 0 0
262 0 $next_result = $self->ListVaults(@_, marker => $next_result->Marker);
263 0 push @{ $result->VaultList }, @{ $next_result->VaultList };
264 }
265 0 return $result;
266 } else {
267 0 ▶ while ($result->Marker) {
Branch: 1 branch
BranchTrueFalseTotal
if ($result->Marker) 0 0 0
268 0 $callback->($_ => 'VaultList') foreach (@{ $result->VaultList });
269 0 $result = $self->ListVaults(@_, marker => $result->Marker);
270 }
271 0 $callback->($_ => 'VaultList') foreach (@{ $result->VaultList });
272 }
273  
274 return undef
275 0 }
276  
277  
278 0 ▶ sub operations { qw/AbortMultipartUpload AbortVaultLock AddTagsToVault CompleteMultipartUpload CompleteVaultLock CreateVault DeleteArchive DeleteVault DeleteVaultAccessPolicy DeleteVaultNotifications DescribeJob DescribeVault GetDataRetrievalPolicy GetJobOutput GetVaultAccessPolicy GetVaultLock GetVaultNotifications InitiateJob InitiateMultipartUpload InitiateVaultLock ListJobs ListMultipartUploads ListParts ListProvisionedCapacity ListTagsForVault ListVaults PurchaseProvisionedCapacity RemoveTagsFromVault SetDataRetrievalPolicy SetVaultAccessPolicy SetVaultNotifications UploadArchive UploadMultipartPart / }
Subroutine operations: not called CC=1 SCAR=6.9
Pod undocumented
279  
280 5 1;
281  
282 ### main pod documentation begin ###
283  
284 =head1 NAME
285  
286 Paws::Glacier - Perl Interface to AWS Amazon Glacier
287  
288 =head1 SYNOPSIS
289  
290 use Paws;
291  
292 my $obj = Paws->service('Glacier');
293 my $res = $obj->Method(
294 Arg1 => $val1,
295 Arg2 => [ 'V1', 'V2' ],
296 # if Arg3 is an object, the HashRef will be used as arguments to the constructor
297 # of the arguments type
298 Arg3 => { Att1 => 'Val1' },
299 # if Arg4 is an array of objects, the HashRefs will be passed as arguments to
300 # the constructor of the arguments type
301 Arg4 => [ { Att1 => 'Val1' }, { Att1 => 'Val2' } ],
302 );
303  
304 =head1 DESCRIPTION
305  
306 Amazon S3 Glacier (Glacier) is a storage solution for "cold data."
307  
308 Glacier is an extremely low-cost storage service that provides secure,
309 durable, and easy-to-use storage for data backup and archival. With
310 Glacier, customers can store their data cost effectively for months,
311 years, or decades. Glacier also enables customers to offload the
312 administrative burdens of operating and scaling storage to AWS, so they
313 don't have to worry about capacity planning, hardware provisioning,
314 data replication, hardware failure and recovery, or time-consuming
315 hardware migrations.
316  
317 Glacier is a great storage choice when low storage cost is paramount
318 and your data is rarely retrieved. If your application requires fast or
319 frequent access to your data, consider using Amazon S3. For more
320 information, see Amazon Simple Storage Service (Amazon S3)
321 (http://aws.amazon.com/s3/).
322  
323 You can store any kind of data in any format. There is no maximum limit
324 on the total amount of data you can store in Glacier.
325  
326 If you are a first-time user of Glacier, we recommend that you begin by
327 reading the following sections in the I<Amazon S3 Glacier Developer
328 Guide>:
329  
330 =over
331  
332 =item *
333  
334 What is Amazon S3 Glacier
335 (https://docs.aws.amazon.com/amazonglacier/latest/dev/introduction.html)
336 - This section of the Developer Guide describes the underlying data
337 model, the operations it supports, and the AWS SDKs that you can use to
338 interact with the service.
339  
340 =item *
341  
342 Getting Started with Amazon S3 Glacier
343 (https://docs.aws.amazon.com/amazonglacier/latest/dev/amazon-glacier-getting-started.html)
344 - The Getting Started section walks you through the process of creating
345 a vault, uploading archives, creating jobs to download archives,
346 retrieving the job output, and deleting archives.
347  
348 =back
349  
350  
351 For the AWS API documentation, see L<https://docs.aws.amazon.com/glacier/>
352  
353  
354 =head1 METHODS
355  
356 =head2 AbortMultipartUpload
357  
358 =over
359  
360 =item AccountId => Str
361  
362 =item UploadId => Str
363  
364 =item VaultName => Str
365  
366  
367 =back
368  
369 Each argument is described in detail in: L<Paws::Glacier::AbortMultipartUpload>
370  
371 Returns: nothing
372  
373 This operation aborts a multipart upload identified by the upload ID.
374  
375 After the Abort Multipart Upload request succeeds, you cannot upload
376 any more parts to the multipart upload or complete the multipart
377 upload. Aborting a completed upload fails. However, aborting an
378 already-aborted upload will succeed, for a short time. For more
379 information about uploading a part and completing a multipart upload,
380 see UploadMultipartPart and CompleteMultipartUpload.
381  
382 This operation is idempotent.
383  
384 An AWS account has full permission to perform all operations (actions).
385 However, AWS Identity and Access Management (IAM) users don't have any
386 permissions by default. You must grant them explicit permission to
387 perform specific actions. For more information, see Access Control
388 Using AWS Identity and Access Management (IAM)
389 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
390  
391 For conceptual information and underlying REST API, see Working with
392 Archives in Amazon S3 Glacier
393 (https://docs.aws.amazon.com/amazonglacier/latest/dev/working-with-archives.html)
394 and Abort Multipart Upload
395 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-multipart-abort-upload.html)
396 in the I<Amazon Glacier Developer Guide>.
397  
398  
399 =head2 AbortVaultLock
400  
401 =over
402  
403 =item AccountId => Str
404  
405 =item VaultName => Str
406  
407  
408 =back
409  
410 Each argument is described in detail in: L<Paws::Glacier::AbortVaultLock>
411  
412 Returns: nothing
413  
414 This operation aborts the vault locking process if the vault lock is
415 not in the C<Locked> state. If the vault lock is in the C<Locked> state
416 when this operation is requested, the operation returns an
417 C<AccessDeniedException> error. Aborting the vault locking process
418 removes the vault lock policy from the specified vault.
419  
420 A vault lock is put into the C<InProgress> state by calling
421 InitiateVaultLock. A vault lock is put into the C<Locked> state by
422 calling CompleteVaultLock. You can get the state of a vault lock by
423 calling GetVaultLock. For more information about the vault locking
424 process, see Amazon Glacier Vault Lock
425 (https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-lock.html).
426 For more information about vault lock policies, see Amazon Glacier
427 Access Control with Vault Lock Policies
428 (https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-lock-policy.html).
429  
430 This operation is idempotent. You can successfully invoke this
431 operation multiple times, if the vault lock is in the C<InProgress>
432 state or if there is no policy associated with the vault.
433  
434  
435 =head2 AddTagsToVault
436  
437 =over
438  
439 =item AccountId => Str
440  
441 =item VaultName => Str
442  
443 =item [Tags => L<Paws::Glacier::TagMap>]
444  
445  
446 =back
447  
448 Each argument is described in detail in: L<Paws::Glacier::AddTagsToVault>
449  
450 Returns: nothing
451  
452 This operation adds the specified tags to a vault. Each tag is composed
453 of a key and a value. Each vault can have up to 10 tags. If your
454 request would cause the tag limit for the vault to be exceeded, the
455 operation throws the C<LimitExceededException> error. If a tag already
456 exists on the vault under a specified key, the existing key value will
457 be overwritten. For more information about tags, see Tagging Amazon S3
458 Glacier Resources
459 (https://docs.aws.amazon.com/amazonglacier/latest/dev/tagging.html).
460  
461  
462 =head2 CompleteMultipartUpload
463  
464 =over
465  
466 =item AccountId => Str
467  
468 =item UploadId => Str
469  
470 =item VaultName => Str
471  
472 =item [ArchiveSize => Str]
473  
474 =item [Checksum => Str]
475  
476  
477 =back
478  
479 Each argument is described in detail in: L<Paws::Glacier::CompleteMultipartUpload>
480  
481 Returns: a L<Paws::Glacier::ArchiveCreationOutput> instance
482  
483 You call this operation to inform Amazon S3 Glacier (Glacier) that all
484 the archive parts have been uploaded and that Glacier can now assemble
485 the archive from the uploaded parts. After assembling and saving the
486 archive to the vault, Glacier returns the URI path of the newly created
487 archive resource. Using the URI path, you can then access the archive.
488 After you upload an archive, you should save the archive ID returned to
489 retrieve the archive at a later point. You can also get the vault
490 inventory to obtain a list of archive IDs in a vault. For more
491 information, see InitiateJob.
492  
493 In the request, you must include the computed SHA256 tree hash of the
494 entire archive you have uploaded. For information about computing a
495 SHA256 tree hash, see Computing Checksums
496 (https://docs.aws.amazon.com/amazonglacier/latest/dev/checksum-calculations.html).
497 On the server side, Glacier also constructs the SHA256 tree hash of the
498 assembled archive. If the values match, Glacier saves the archive to
499 the vault; otherwise, it returns an error, and the operation fails. The
500 ListParts operation returns a list of parts uploaded for a specific
501 multipart upload. It includes checksum information for each uploaded
502 part that can be used to debug a bad checksum issue.
503  
504 Additionally, Glacier also checks for any missing content ranges when
505 assembling the archive, if missing content ranges are found, Glacier
506 returns an error and the operation fails.
507  
508 Complete Multipart Upload is an idempotent operation. After your first
509 successful complete multipart upload, if you call the operation again
510 within a short period, the operation will succeed and return the same
511 archive ID. This is useful in the event you experience a network issue
512 that causes an aborted connection or receive a 500 server error, in
513 which case you can repeat your Complete Multipart Upload request and
514 get the same archive ID without creating duplicate archives. Note,
515 however, that after the multipart upload completes, you cannot call the
516 List Parts operation and the multipart upload will not appear in List
517 Multipart Uploads response, even if idempotent complete is possible.
518  
519 An AWS account has full permission to perform all operations (actions).
520 However, AWS Identity and Access Management (IAM) users don't have any
521 permissions by default. You must grant them explicit permission to
522 perform specific actions. For more information, see Access Control
523 Using AWS Identity and Access Management (IAM)
524 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
525  
526 For conceptual information and underlying REST API, see Uploading Large
527 Archives in Parts (Multipart Upload)
528 (https://docs.aws.amazon.com/amazonglacier/latest/dev/uploading-archive-mpu.html)
529 and Complete Multipart Upload
530 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-multipart-complete-upload.html)
531 in the I<Amazon Glacier Developer Guide>.
532  
533  
534 =head2 CompleteVaultLock
535  
536 =over
537  
538 =item AccountId => Str
539  
540 =item LockId => Str
541  
542 =item VaultName => Str
543  
544  
545 =back
546  
547 Each argument is described in detail in: L<Paws::Glacier::CompleteVaultLock>
548  
549 Returns: nothing
550  
551 This operation completes the vault locking process by transitioning the
552 vault lock from the C<InProgress> state to the C<Locked> state, which
553 causes the vault lock policy to become unchangeable. A vault lock is
554 put into the C<InProgress> state by calling InitiateVaultLock. You can
555 obtain the state of the vault lock by calling GetVaultLock. For more
556 information about the vault locking process, Amazon Glacier Vault Lock
557 (https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-lock.html).
558  
559 This operation is idempotent. This request is always successful if the
560 vault lock is in the C<Locked> state and the provided lock ID matches
561 the lock ID originally used to lock the vault.
562  
563 If an invalid lock ID is passed in the request when the vault lock is
564 in the C<Locked> state, the operation returns an
565 C<AccessDeniedException> error. If an invalid lock ID is passed in the
566 request when the vault lock is in the C<InProgress> state, the
567 operation throws an C<InvalidParameter> error.
568  
569  
570 =head2 CreateVault
571  
572 =over
573  
574 =item AccountId => Str
575  
576 =item VaultName => Str
577  
578  
579 =back
580  
581 Each argument is described in detail in: L<Paws::Glacier::CreateVault>
582  
583 Returns: a L<Paws::Glacier::CreateVaultOutput> instance
584  
585 This operation creates a new vault with the specified name. The name of
586 the vault must be unique within a region for an AWS account. You can
587 create up to 1,000 vaults per account. If you need to create more
588 vaults, contact Amazon S3 Glacier.
589  
590 You must use the following guidelines when naming a vault.
591  
592 =over
593  
594 =item *
595  
596 Names can be between 1 and 255 characters long.
597  
598 =item *
599  
600 Allowed characters are a-z, A-Z, 0-9, '_' (underscore), '-' (hyphen),
601 and '.' (period).
602  
603 =back
604  
605 This operation is idempotent.
606  
607 An AWS account has full permission to perform all operations (actions).
608 However, AWS Identity and Access Management (IAM) users don't have any
609 permissions by default. You must grant them explicit permission to
610 perform specific actions. For more information, see Access Control
611 Using AWS Identity and Access Management (IAM)
612 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
613  
614 For conceptual information and underlying REST API, see Creating a
615 Vault in Amazon Glacier
616 (https://docs.aws.amazon.com/amazonglacier/latest/dev/creating-vaults.html)
617 and Create Vault
618 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-vault-put.html)
619 in the I<Amazon Glacier Developer Guide>.
620  
621  
622 =head2 DeleteArchive
623  
624 =over
625  
626 =item AccountId => Str
627  
628 =item ArchiveId => Str
629  
630 =item VaultName => Str
631  
632  
633 =back
634  
635 Each argument is described in detail in: L<Paws::Glacier::DeleteArchive>
636  
637 Returns: nothing
638  
639 This operation deletes an archive from a vault. Subsequent requests to
640 initiate a retrieval of this archive will fail. Archive retrievals that
641 are in progress for this archive ID may or may not succeed according to
642 the following scenarios:
643  
644 =over
645  
646 =item *
647  
648 If the archive retrieval job is actively preparing the data for
649 download when Amazon S3 Glacier receives the delete archive request,
650 the archival retrieval operation might fail.
651  
652 =item *
653  
654 If the archive retrieval job has successfully prepared the archive for
655 download when Amazon S3 Glacier receives the delete archive request,
656 you will be able to download the output.
657  
658 =back
659  
660 This operation is idempotent. Attempting to delete an already-deleted
661 archive does not result in an error.
662  
663 An AWS account has full permission to perform all operations (actions).
664 However, AWS Identity and Access Management (IAM) users don't have any
665 permissions by default. You must grant them explicit permission to
666 perform specific actions. For more information, see Access Control
667 Using AWS Identity and Access Management (IAM)
668 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
669  
670 For conceptual information and underlying REST API, see Deleting an
671 Archive in Amazon Glacier
672 (https://docs.aws.amazon.com/amazonglacier/latest/dev/deleting-an-archive.html)
673 and Delete Archive
674 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-archive-delete.html)
675 in the I<Amazon Glacier Developer Guide>.
676  
677  
678 =head2 DeleteVault
679  
680 =over
681  
682 =item AccountId => Str
683  
684 =item VaultName => Str
685  
686  
687 =back
688  
689 Each argument is described in detail in: L<Paws::Glacier::DeleteVault>
690  
691 Returns: nothing
692  
693 This operation deletes a vault. Amazon S3 Glacier will delete a vault
694 only if there are no archives in the vault as of the last inventory and
695 there have been no writes to the vault since the last inventory. If
696 either of these conditions is not satisfied, the vault deletion fails
697 (that is, the vault is not removed) and Amazon S3 Glacier returns an
698 error. You can use DescribeVault to return the number of archives in a
699 vault, and you can use Initiate a Job (POST jobs)
700 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-initiate-job-post.html)
701 to initiate a new inventory retrieval for a vault. The inventory
702 contains the archive IDs you use to delete archives using Delete
703 Archive (DELETE archive)
704 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-archive-delete.html).
705  
706 This operation is idempotent.
707  
708 An AWS account has full permission to perform all operations (actions).
709 However, AWS Identity and Access Management (IAM) users don't have any
710 permissions by default. You must grant them explicit permission to
711 perform specific actions. For more information, see Access Control
712 Using AWS Identity and Access Management (IAM)
713 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
714  
715 For conceptual information and underlying REST API, see Deleting a
716 Vault in Amazon Glacier
717 (https://docs.aws.amazon.com/amazonglacier/latest/dev/deleting-vaults.html)
718 and Delete Vault
719 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-vault-delete.html)
720 in the I<Amazon S3 Glacier Developer Guide>.
721  
722  
723 =head2 DeleteVaultAccessPolicy
724  
725 =over
726  
727 =item AccountId => Str
728  
729 =item VaultName => Str
730  
731  
732 =back
733  
734 Each argument is described in detail in: L<Paws::Glacier::DeleteVaultAccessPolicy>
735  
736 Returns: nothing
737  
738 This operation deletes the access policy associated with the specified
739 vault. The operation is eventually consistent; that is, it might take
740 some time for Amazon S3 Glacier to completely remove the access policy,
741 and you might still see the effect of the policy for a short time after
742 you send the delete request.
743  
744 This operation is idempotent. You can invoke delete multiple times,
745 even if there is no policy associated with the vault. For more
746 information about vault access policies, see Amazon Glacier Access
747 Control with Vault Access Policies
748 (https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-access-policy.html).
749  
750  
751 =head2 DeleteVaultNotifications
752  
753 =over
754  
755 =item AccountId => Str
756  
757 =item VaultName => Str
758  
759  
760 =back
761  
762 Each argument is described in detail in: L<Paws::Glacier::DeleteVaultNotifications>
763  
764 Returns: nothing
765  
766 This operation deletes the notification configuration set for a vault.
767 The operation is eventually consistent; that is, it might take some
768 time for Amazon S3 Glacier to completely disable the notifications and
769 you might still receive some notifications for a short time after you
770 send the delete request.
771  
772 An AWS account has full permission to perform all operations (actions).
773 However, AWS Identity and Access Management (IAM) users don't have any
774 permissions by default. You must grant them explicit permission to
775 perform specific actions. For more information, see Access Control
776 Using AWS Identity and Access Management (IAM)
777 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
778  
779 For conceptual information and underlying REST API, see Configuring
780 Vault Notifications in Amazon S3 Glacier
781 (https://docs.aws.amazon.com/amazonglacier/latest/dev/configuring-notifications.html)
782 and Delete Vault Notification Configuration
783 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-vault-notifications-delete.html)
784 in the Amazon S3 Glacier Developer Guide.
785  
786  
787 =head2 DescribeJob
788  
789 =over
790  
791 =item AccountId => Str
792  
793 =item JobId => Str
794  
795 =item VaultName => Str
796  
797  
798 =back
799  
800 Each argument is described in detail in: L<Paws::Glacier::DescribeJob>
801  
802 Returns: a L<Paws::Glacier::GlacierJobDescription> instance
803  
804 This operation returns information about a job you previously
805 initiated, including the job initiation date, the user who initiated
806 the job, the job status code/message and the Amazon SNS topic to notify
807 after Amazon S3 Glacier (Glacier) completes the job. For more
808 information about initiating a job, see InitiateJob.
809  
810 This operation enables you to check the status of your job. However, it
811 is strongly recommended that you set up an Amazon SNS topic and specify
812 it in your initiate job request so that Glacier can notify the topic
813 after it completes the job.
814  
815 A job ID will not expire for at least 24 hours after Glacier completes
816 the job.
817  
818 An AWS account has full permission to perform all operations (actions).
819 However, AWS Identity and Access Management (IAM) users don't have any
820 permissions by default. You must grant them explicit permission to
821 perform specific actions. For more information, see Access Control
822 Using AWS Identity and Access Management (IAM)
823 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
824  
825 For more information about using this operation, see the documentation
826 for the underlying REST API Describe Job
827 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-describe-job-get.html)
828 in the I<Amazon Glacier Developer Guide>.
829  
830  
831 =head2 DescribeVault
832  
833 =over
834  
835 =item AccountId => Str
836  
837 =item VaultName => Str
838  
839  
840 =back
841  
842 Each argument is described in detail in: L<Paws::Glacier::DescribeVault>
843  
844 Returns: a L<Paws::Glacier::DescribeVaultOutput> instance
845  
846 This operation returns information about a vault, including the vault's
847 Amazon Resource Name (ARN), the date the vault was created, the number
848 of archives it contains, and the total size of all the archives in the
849 vault. The number of archives and their total size are as of the last
850 inventory generation. This means that if you add or remove an archive
851 from a vault, and then immediately use Describe Vault, the change in
852 contents will not be immediately reflected. If you want to retrieve the
853 latest inventory of the vault, use InitiateJob. Amazon S3 Glacier
854 generates vault inventories approximately daily. For more information,
855 see Downloading a Vault Inventory in Amazon S3 Glacier
856 (https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-inventory.html).
857  
858 An AWS account has full permission to perform all operations (actions).
859 However, AWS Identity and Access Management (IAM) users don't have any
860 permissions by default. You must grant them explicit permission to
861 perform specific actions. For more information, see Access Control
862 Using AWS Identity and Access Management (IAM)
863 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
864  
865 For conceptual information and underlying REST API, see Retrieving
866 Vault Metadata in Amazon S3 Glacier
867 (https://docs.aws.amazon.com/amazonglacier/latest/dev/retrieving-vault-info.html)
868 and Describe Vault
869 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-vault-get.html)
870 in the I<Amazon Glacier Developer Guide>.
871  
872  
873 =head2 GetDataRetrievalPolicy
874  
875 =over
876  
877 =item AccountId => Str
878  
879  
880 =back
881  
882 Each argument is described in detail in: L<Paws::Glacier::GetDataRetrievalPolicy>
883  
884 Returns: a L<Paws::Glacier::GetDataRetrievalPolicyOutput> instance
885  
886 This operation returns the current data retrieval policy for the
887 account and region specified in the GET request. For more information
888 about data retrieval policies, see Amazon Glacier Data Retrieval
889 Policies
890 (https://docs.aws.amazon.com/amazonglacier/latest/dev/data-retrieval-policy.html).
891  
892  
893 =head2 GetJobOutput
894  
895 =over
896  
897 =item AccountId => Str
898  
899 =item JobId => Str
900  
901 =item VaultName => Str
902  
903 =item [Range => Str]
904  
905  
906 =back
907  
908 Each argument is described in detail in: L<Paws::Glacier::GetJobOutput>
909  
910 Returns: a L<Paws::Glacier::GetJobOutputOutput> instance
911  
912 This operation downloads the output of the job you initiated using
913 InitiateJob. Depending on the job type you specified when you initiated
914 the job, the output will be either the content of an archive or a vault
915 inventory.
916  
917 You can download all the job output or download a portion of the output
918 by specifying a byte range. In the case of an archive retrieval job,
919 depending on the byte range you specify, Amazon S3 Glacier (Glacier)
920 returns the checksum for the portion of the data. You can compute the
921 checksum on the client and verify that the values match to ensure the
922 portion you downloaded is the correct data.
923  
924 A job ID will not expire for at least 24 hours after Glacier completes
925 the job. That a byte range. For both archive and inventory retrieval
926 jobs, you should verify the downloaded size against the size returned
927 in the headers from the B<Get Job Output> response.
928  
929 For archive retrieval jobs, you should also verify that the size is
930 what you expected. If you download a portion of the output, the
931 expected size is based on the range of bytes you specified. For
932 example, if you specify a range of C<bytes=0-1048575>, you should
933 verify your download size is 1,048,576 bytes. If you download an entire
934 archive, the expected size is the size of the archive when you uploaded
935 it to Amazon S3 Glacier The expected size is also returned in the
936 headers from the B<Get Job Output> response.
937  
938 In the case of an archive retrieval job, depending on the byte range
939 you specify, Glacier returns the checksum for the portion of the data.
940 To ensure the portion you downloaded is the correct data, compute the
941 checksum on the client, verify that the values match, and verify that
942 the size is what you expected.
943  
944 A job ID does not expire for at least 24 hours after Glacier completes
945 the job. That is, you can download the job output within the 24 hours
946 period after Amazon Glacier completes the job.
947  
948 An AWS account has full permission to perform all operations (actions).
949 However, AWS Identity and Access Management (IAM) users don't have any
950 permissions by default. You must grant them explicit permission to
951 perform specific actions. For more information, see Access Control
952 Using AWS Identity and Access Management (IAM)
953 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
954  
955 For conceptual information and the underlying REST API, see Downloading
956 a Vault Inventory
957 (https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-inventory.html),
958 Downloading an Archive
959 (https://docs.aws.amazon.com/amazonglacier/latest/dev/downloading-an-archive.html),
960 and Get Job Output
961 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-job-output-get.html)
962  
963  
964 =head2 GetVaultAccessPolicy
965  
966 =over
967  
968 =item AccountId => Str
969  
970 =item VaultName => Str
971  
972  
973 =back
974  
975 Each argument is described in detail in: L<Paws::Glacier::GetVaultAccessPolicy>
976  
977 Returns: a L<Paws::Glacier::GetVaultAccessPolicyOutput> instance
978  
979 This operation retrieves the C<access-policy> subresource set on the
980 vault; for more information on setting this subresource, see Set Vault
981 Access Policy (PUT access-policy)
982 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-SetVaultAccessPolicy.html).
983 If there is no access policy set on the vault, the operation returns a
984 C<404 Not found> error. For more information about vault access
985 policies, see Amazon Glacier Access Control with Vault Access Policies
986 (https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-access-policy.html).
987  
988  
989 =head2 GetVaultLock
990  
991 =over
992  
993 =item AccountId => Str
994  
995 =item VaultName => Str
996  
997  
998 =back
999  
1000 Each argument is described in detail in: L<Paws::Glacier::GetVaultLock>
1001  
1002 Returns: a L<Paws::Glacier::GetVaultLockOutput> instance
1003  
1004 This operation retrieves the following attributes from the
1005 C<lock-policy> subresource set on the specified vault:
1006  
1007 =over
1008  
1009 =item *
1010  
1011 The vault lock policy set on the vault.
1012  
1013 =item *
1014  
1015 The state of the vault lock, which is either C<InProgess> or C<Locked>.
1016  
1017 =item *
1018  
1019 When the lock ID expires. The lock ID is used to complete the vault
1020 locking process.
1021  
1022 =item *
1023  
1024 When the vault lock was initiated and put into the C<InProgress> state.
1025  
1026 =back
1027  
1028 A vault lock is put into the C<InProgress> state by calling
1029 InitiateVaultLock. A vault lock is put into the C<Locked> state by
1030 calling CompleteVaultLock. You can abort the vault locking process by
1031 calling AbortVaultLock. For more information about the vault locking
1032 process, Amazon Glacier Vault Lock
1033 (https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-lock.html).
1034  
1035 If there is no vault lock policy set on the vault, the operation
1036 returns a C<404 Not found> error. For more information about vault lock
1037 policies, Amazon Glacier Access Control with Vault Lock Policies
1038 (https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-lock-policy.html).
1039  
1040  
1041 =head2 GetVaultNotifications
1042  
1043 =over
1044  
1045 =item AccountId => Str
1046  
1047 =item VaultName => Str
1048  
1049  
1050 =back
1051  
1052 Each argument is described in detail in: L<Paws::Glacier::GetVaultNotifications>
1053  
1054 Returns: a L<Paws::Glacier::GetVaultNotificationsOutput> instance
1055  
1056 This operation retrieves the C<notification-configuration> subresource
1057 of the specified vault.
1058  
1059 For information about setting a notification configuration on a vault,
1060 see SetVaultNotifications. If a notification configuration for a vault
1061 is not set, the operation returns a C<404 Not Found> error. For more
1062 information about vault notifications, see Configuring Vault
1063 Notifications in Amazon S3 Glacier
1064 (https://docs.aws.amazon.com/amazonglacier/latest/dev/configuring-notifications.html).
1065  
1066 An AWS account has full permission to perform all operations (actions).
1067 However, AWS Identity and Access Management (IAM) users don't have any
1068 permissions by default. You must grant them explicit permission to
1069 perform specific actions. For more information, see Access Control
1070 Using AWS Identity and Access Management (IAM)
1071 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
1072  
1073 For conceptual information and underlying REST API, see Configuring
1074 Vault Notifications in Amazon S3 Glacier
1075 (https://docs.aws.amazon.com/amazonglacier/latest/dev/configuring-notifications.html)
1076 and Get Vault Notification Configuration
1077 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-vault-notifications-get.html)
1078 in the I<Amazon Glacier Developer Guide>.
1079  
1080  
1081 =head2 InitiateJob
1082  
1083 =over
1084  
1085 =item AccountId => Str
1086  
1087 =item VaultName => Str
1088  
1089 =item [JobParameters => L<Paws::Glacier::JobParameters>]
1090  
1091  
1092 =back
1093  
1094 Each argument is described in detail in: L<Paws::Glacier::InitiateJob>
1095  
1096 Returns: a L<Paws::Glacier::InitiateJobOutput> instance
1097  
1098 This operation initiates a job of the specified type, which can be a
1099 select, an archival retrieval, or a vault retrieval. For more
1100 information about using this operation, see the documentation for the
1101 underlying REST API Initiate a Job
1102 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-initiate-job-post.html).
1103  
1104  
1105 =head2 InitiateMultipartUpload
1106  
1107 =over
1108  
1109 =item AccountId => Str
1110  
1111 =item VaultName => Str
1112  
1113 =item [ArchiveDescription => Str]
1114  
1115 =item [PartSize => Str]
1116  
1117  
1118 =back
1119  
1120 Each argument is described in detail in: L<Paws::Glacier::InitiateMultipartUpload>
1121  
1122 Returns: a L<Paws::Glacier::InitiateMultipartUploadOutput> instance
1123  
1124 This operation initiates a multipart upload. Amazon S3 Glacier creates
1125 a multipart upload resource and returns its ID in the response. The
1126 multipart upload ID is used in subsequent requests to upload parts of
1127 an archive (see UploadMultipartPart).
1128  
1129 When you initiate a multipart upload, you specify the part size in
1130 number of bytes. The part size must be a megabyte (1024 KB) multiplied
1131 by a power of 2-for example, 1048576 (1 MB), 2097152 (2 MB), 4194304 (4
1132 MB), 8388608 (8 MB), and so on. The minimum allowable part size is 1
1133 MB, and the maximum is 4 GB.
1134  
1135 Every part you upload to this resource (see UploadMultipartPart),
1136 except the last one, must have the same size. The last one can be the
1137 same size or smaller. For example, suppose you want to upload a 16.2 MB
1138 file. If you initiate the multipart upload with a part size of 4 MB,
1139 you will upload four parts of 4 MB each and one part of 0.2 MB.
1140  
1141 You don't need to know the size of the archive when you start a
1142 multipart upload because Amazon S3 Glacier does not require you to
1143 specify the overall archive size.
1144  
1145 After you complete the multipart upload, Amazon S3 Glacier (Glacier)
1146 removes the multipart upload resource referenced by the ID. Glacier
1147 also removes the multipart upload resource if you cancel the multipart
1148 upload or it may be removed if there is no activity for a period of 24
1149 hours.
1150  
1151 An AWS account has full permission to perform all operations (actions).
1152 However, AWS Identity and Access Management (IAM) users don't have any
1153 permissions by default. You must grant them explicit permission to
1154 perform specific actions. For more information, see Access Control
1155 Using AWS Identity and Access Management (IAM)
1156 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
1157  
1158 For conceptual information and underlying REST API, see Uploading Large
1159 Archives in Parts (Multipart Upload)
1160 (https://docs.aws.amazon.com/amazonglacier/latest/dev/uploading-archive-mpu.html)
1161 and Initiate Multipart Upload
1162 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-multipart-initiate-upload.html)
1163 in the I<Amazon Glacier Developer Guide>.
1164  
1165  
1166 =head2 InitiateVaultLock
1167  
1168 =over
1169  
1170 =item AccountId => Str
1171  
1172 =item VaultName => Str
1173  
1174 =item [Policy => L<Paws::Glacier::VaultLockPolicy>]
1175  
1176  
1177 =back
1178  
1179 Each argument is described in detail in: L<Paws::Glacier::InitiateVaultLock>
1180  
1181 Returns: a L<Paws::Glacier::InitiateVaultLockOutput> instance
1182  
1183 This operation initiates the vault locking process by doing the
1184 following:
1185  
1186 =over
1187  
1188 =item *
1189  
1190 Installing a vault lock policy on the specified vault.
1191  
1192 =item *
1193  
1194 Setting the lock state of vault lock to C<InProgress>.
1195  
1196 =item *
1197  
1198 Returning a lock ID, which is used to complete the vault locking
1199 process.
1200  
1201 =back
1202  
1203 You can set one vault lock policy for each vault and this policy can be
1204 up to 20 KB in size. For more information about vault lock policies,
1205 see Amazon Glacier Access Control with Vault Lock Policies
1206 (https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-lock-policy.html).
1207  
1208 You must complete the vault locking process within 24 hours after the
1209 vault lock enters the C<InProgress> state. After the 24 hour window
1210 ends, the lock ID expires, the vault automatically exits the
1211 C<InProgress> state, and the vault lock policy is removed from the
1212 vault. You call CompleteVaultLock to complete the vault locking process
1213 by setting the state of the vault lock to C<Locked>.
1214  
1215 After a vault lock is in the C<Locked> state, you cannot initiate a new
1216 vault lock for the vault.
1217  
1218 You can abort the vault locking process by calling AbortVaultLock. You
1219 can get the state of the vault lock by calling GetVaultLock. For more
1220 information about the vault locking process, Amazon Glacier Vault Lock
1221 (https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-lock.html).
1222  
1223 If this operation is called when the vault lock is in the C<InProgress>
1224 state, the operation returns an C<AccessDeniedException> error. When
1225 the vault lock is in the C<InProgress> state you must call
1226 AbortVaultLock before you can initiate a new vault lock policy.
1227  
1228  
1229 =head2 ListJobs
1230  
1231 =over
1232  
1233 =item AccountId => Str
1234  
1235 =item VaultName => Str
1236  
1237 =item [Completed => Str]
1238  
1239 =item [Limit => Str]
1240  
1241 =item [Marker => Str]
1242  
1243 =item [Statuscode => Str]
1244  
1245  
1246 =back
1247  
1248 Each argument is described in detail in: L<Paws::Glacier::ListJobs>
1249  
1250 Returns: a L<Paws::Glacier::ListJobsOutput> instance
1251  
1252 This operation lists jobs for a vault, including jobs that are
1253 in-progress and jobs that have recently finished. The List Job
1254 operation returns a list of these jobs sorted by job initiation time.
1255  
1256 Amazon Glacier retains recently completed jobs for a period before
1257 deleting them; however, it eventually removes completed jobs. The
1258 output of completed jobs can be retrieved. Retaining completed jobs for
1259 a period of time after they have completed enables you to get a job
1260 output in the event you miss the job completion notification or your
1261 first attempt to download it fails. For example, suppose you start an
1262 archive retrieval job to download an archive. After the job completes,
1263 you start to download the archive but encounter a network error. In
1264 this scenario, you can retry and download the archive while the job
1265 exists.
1266  
1267 The List Jobs operation supports pagination. You should always check
1268 the response C<Marker> field. If there are no more jobs to list, the
1269 C<Marker> field is set to C<null>. If there are more jobs to list, the
1270 C<Marker> field is set to a non-null value, which you can use to
1271 continue the pagination of the list. To return a list of jobs that
1272 begins at a specific job, set the marker request parameter to the
1273 C<Marker> value for that job that you obtained from a previous List
1274 Jobs request.
1275  
1276 You can set a maximum limit for the number of jobs returned in the
1277 response by specifying the C<limit> parameter in the request. The
1278 default limit is 50. The number of jobs returned might be fewer than
1279 the limit, but the number of returned jobs never exceeds the limit.
1280  
1281 Additionally, you can filter the jobs list returned by specifying the
1282 optional C<statuscode> parameter or C<completed> parameter, or both.
1283 Using the C<statuscode> parameter, you can specify to return only jobs
1284 that match either the C<InProgress>, C<Succeeded>, or C<Failed> status.
1285 Using the C<completed> parameter, you can specify to return only jobs
1286 that were completed (C<true>) or jobs that were not completed
1287 (C<false>).
1288  
1289 For more information about using this operation, see the documentation
1290 for the underlying REST API List Jobs
1291 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-jobs-get.html).
1292  
1293  
1294 =head2 ListMultipartUploads
1295  
1296 =over
1297  
1298 =item AccountId => Str
1299  
1300 =item VaultName => Str
1301  
1302 =item [Limit => Str]
1303  
1304 =item [Marker => Str]
1305  
1306  
1307 =back
1308  
1309 Each argument is described in detail in: L<Paws::Glacier::ListMultipartUploads>
1310  
1311 Returns: a L<Paws::Glacier::ListMultipartUploadsOutput> instance
1312  
1313 This operation lists in-progress multipart uploads for the specified
1314 vault. An in-progress multipart upload is a multipart upload that has
1315 been initiated by an InitiateMultipartUpload request, but has not yet
1316 been completed or aborted. The list returned in the List Multipart
1317 Upload response has no guaranteed order.
1318  
1319 The List Multipart Uploads operation supports pagination. By default,
1320 this operation returns up to 50 multipart uploads in the response. You
1321 should always check the response for a C<marker> at which to continue
1322 the list; if there are no more items the C<marker> is C<null>. To
1323 return a list of multipart uploads that begins at a specific upload,
1324 set the C<marker> request parameter to the value you obtained from a
1325 previous List Multipart Upload request. You can also limit the number
1326 of uploads returned in the response by specifying the C<limit>
1327 parameter in the request.
1328  
1329 Note the difference between this operation and listing parts
1330 (ListParts). The List Multipart Uploads operation lists all multipart
1331 uploads for a vault and does not require a multipart upload ID. The
1332 List Parts operation requires a multipart upload ID since parts are
1333 associated with a single upload.
1334  
1335 An AWS account has full permission to perform all operations (actions).
1336 However, AWS Identity and Access Management (IAM) users don't have any
1337 permissions by default. You must grant them explicit permission to
1338 perform specific actions. For more information, see Access Control
1339 Using AWS Identity and Access Management (IAM)
1340 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
1341  
1342 For conceptual information and the underlying REST API, see Working
1343 with Archives in Amazon S3 Glacier
1344 (https://docs.aws.amazon.com/amazonglacier/latest/dev/working-with-archives.html)
1345 and List Multipart Uploads
1346 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-multipart-list-uploads.html)
1347 in the I<Amazon Glacier Developer Guide>.
1348  
1349  
1350 =head2 ListParts
1351  
1352 =over
1353  
1354 =item AccountId => Str
1355  
1356 =item UploadId => Str
1357  
1358 =item VaultName => Str
1359  
1360 =item [Limit => Str]
1361  
1362 =item [Marker => Str]
1363  
1364  
1365 =back
1366  
1367 Each argument is described in detail in: L<Paws::Glacier::ListParts>
1368  
1369 Returns: a L<Paws::Glacier::ListPartsOutput> instance
1370  
1371 This operation lists the parts of an archive that have been uploaded in
1372 a specific multipart upload. You can make this request at any time
1373 during an in-progress multipart upload before you complete the upload
1374 (see CompleteMultipartUpload. List Parts returns an error for completed
1375 uploads. The list returned in the List Parts response is sorted by part
1376 range.
1377  
1378 The List Parts operation supports pagination. By default, this
1379 operation returns up to 50 uploaded parts in the response. You should
1380 always check the response for a C<marker> at which to continue the
1381 list; if there are no more items the C<marker> is C<null>. To return a
1382 list of parts that begins at a specific part, set the C<marker> request
1383 parameter to the value you obtained from a previous List Parts request.
1384 You can also limit the number of parts returned in the response by
1385 specifying the C<limit> parameter in the request.
1386  
1387 An AWS account has full permission to perform all operations (actions).
1388 However, AWS Identity and Access Management (IAM) users don't have any
1389 permissions by default. You must grant them explicit permission to
1390 perform specific actions. For more information, see Access Control
1391 Using AWS Identity and Access Management (IAM)
1392 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
1393  
1394 For conceptual information and the underlying REST API, see Working
1395 with Archives in Amazon S3 Glacier
1396 (https://docs.aws.amazon.com/amazonglacier/latest/dev/working-with-archives.html)
1397 and List Parts
1398 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-multipart-list-parts.html)
1399 in the I<Amazon Glacier Developer Guide>.
1400  
1401  
1402 =head2 ListProvisionedCapacity
1403  
1404 =over
1405  
1406 =item AccountId => Str
1407  
1408  
1409 =back
1410  
1411 Each argument is described in detail in: L<Paws::Glacier::ListProvisionedCapacity>
1412  
1413 Returns: a L<Paws::Glacier::ListProvisionedCapacityOutput> instance
1414  
1415 This operation lists the provisioned capacity units for the specified
1416 AWS account.
1417  
1418  
1419 =head2 ListTagsForVault
1420  
1421 =over
1422  
1423 =item AccountId => Str
1424  
1425 =item VaultName => Str
1426  
1427  
1428 =back
1429  
1430 Each argument is described in detail in: L<Paws::Glacier::ListTagsForVault>
1431  
1432 Returns: a L<Paws::Glacier::ListTagsForVaultOutput> instance
1433  
1434 This operation lists all the tags attached to a vault. The operation
1435 returns an empty map if there are no tags. For more information about
1436 tags, see Tagging Amazon S3 Glacier Resources
1437 (https://docs.aws.amazon.com/amazonglacier/latest/dev/tagging.html).
1438  
1439  
1440 =head2 ListVaults
1441  
1442 =over
1443  
1444 =item AccountId => Str
1445  
1446 =item [Limit => Str]
1447  
1448 =item [Marker => Str]
1449  
1450  
1451 =back
1452  
1453 Each argument is described in detail in: L<Paws::Glacier::ListVaults>
1454  
1455 Returns: a L<Paws::Glacier::ListVaultsOutput> instance
1456  
1457 This operation lists all vaults owned by the calling user's account.
1458 The list returned in the response is ASCII-sorted by vault name.
1459  
1460 By default, this operation returns up to 10 items. If there are more
1461 vaults to list, the response C<marker> field contains the vault Amazon
1462 Resource Name (ARN) at which to continue the list with a new List
1463 Vaults request; otherwise, the C<marker> field is C<null>. To return a
1464 list of vaults that begins at a specific vault, set the C<marker>
1465 request parameter to the vault ARN you obtained from a previous List
1466 Vaults request. You can also limit the number of vaults returned in the
1467 response by specifying the C<limit> parameter in the request.
1468  
1469 An AWS account has full permission to perform all operations (actions).
1470 However, AWS Identity and Access Management (IAM) users don't have any
1471 permissions by default. You must grant them explicit permission to
1472 perform specific actions. For more information, see Access Control
1473 Using AWS Identity and Access Management (IAM)
1474 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
1475  
1476 For conceptual information and underlying REST API, see Retrieving
1477 Vault Metadata in Amazon S3 Glacier
1478 (https://docs.aws.amazon.com/amazonglacier/latest/dev/retrieving-vault-info.html)
1479 and List Vaults
1480 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-vaults-get.html)
1481 in the I<Amazon Glacier Developer Guide>.
1482  
1483  
1484 =head2 PurchaseProvisionedCapacity
1485  
1486 =over
1487  
1488 =item AccountId => Str
1489  
1490  
1491 =back
1492  
1493 Each argument is described in detail in: L<Paws::Glacier::PurchaseProvisionedCapacity>
1494  
1495 Returns: a L<Paws::Glacier::PurchaseProvisionedCapacityOutput> instance
1496  
1497 This operation purchases a provisioned capacity unit for an AWS
1498 account.
1499  
1500  
1501 =head2 RemoveTagsFromVault
1502  
1503 =over
1504  
1505 =item AccountId => Str
1506  
1507 =item VaultName => Str
1508  
1509 =item [TagKeys => ArrayRef[Str|Undef]]
1510  
1511  
1512 =back
1513  
1514 Each argument is described in detail in: L<Paws::Glacier::RemoveTagsFromVault>
1515  
1516 Returns: nothing
1517  
1518 This operation removes one or more tags from the set of tags attached
1519 to a vault. For more information about tags, see Tagging Amazon S3
1520 Glacier Resources
1521 (https://docs.aws.amazon.com/amazonglacier/latest/dev/tagging.html).
1522 This operation is idempotent. The operation will be successful, even if
1523 there are no tags attached to the vault.
1524  
1525  
1526 =head2 SetDataRetrievalPolicy
1527  
1528 =over
1529  
1530 =item AccountId => Str
1531  
1532 =item [Policy => L<Paws::Glacier::DataRetrievalPolicy>]
1533  
1534  
1535 =back
1536  
1537 Each argument is described in detail in: L<Paws::Glacier::SetDataRetrievalPolicy>
1538  
1539 Returns: nothing
1540  
1541 This operation sets and then enacts a data retrieval policy in the
1542 region specified in the PUT request. You can set one policy per region
1543 for an AWS account. The policy is enacted within a few minutes of a
1544 successful PUT operation.
1545  
1546 The set policy operation does not affect retrieval jobs that were in
1547 progress before the policy was enacted. For more information about data
1548 retrieval policies, see Amazon Glacier Data Retrieval Policies
1549 (https://docs.aws.amazon.com/amazonglacier/latest/dev/data-retrieval-policy.html).
1550  
1551  
1552 =head2 SetVaultAccessPolicy
1553  
1554 =over
1555  
1556 =item AccountId => Str
1557  
1558 =item VaultName => Str
1559  
1560 =item [Policy => L<Paws::Glacier::VaultAccessPolicy>]
1561  
1562  
1563 =back
1564  
1565 Each argument is described in detail in: L<Paws::Glacier::SetVaultAccessPolicy>
1566  
1567 Returns: nothing
1568  
1569 This operation configures an access policy for a vault and will
1570 overwrite an existing policy. To configure a vault access policy, send
1571 a PUT request to the C<access-policy> subresource of the vault. An
1572 access policy is specific to a vault and is also called a vault
1573 subresource. You can set one access policy per vault and the policy can
1574 be up to 20 KB in size. For more information about vault access
1575 policies, see Amazon Glacier Access Control with Vault Access Policies
1576 (https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-access-policy.html).
1577  
1578  
1579 =head2 SetVaultNotifications
1580  
1581 =over
1582  
1583 =item AccountId => Str
1584  
1585 =item VaultName => Str
1586  
1587 =item [VaultNotificationConfig => L<Paws::Glacier::VaultNotificationConfig>]
1588  
1589  
1590 =back
1591  
1592 Each argument is described in detail in: L<Paws::Glacier::SetVaultNotifications>
1593  
1594 Returns: nothing
1595  
1596 This operation configures notifications that will be sent when specific
1597 events happen to a vault. By default, you don't get any notifications.
1598  
1599 To configure vault notifications, send a PUT request to the
1600 C<notification-configuration> subresource of the vault. The request
1601 should include a JSON document that provides an Amazon SNS topic and
1602 specific events for which you want Amazon S3 Glacier to send
1603 notifications to the topic.
1604  
1605 Amazon SNS topics must grant permission to the vault to be allowed to
1606 publish notifications to the topic. You can configure a vault to
1607 publish a notification for the following vault events:
1608  
1609 =over
1610  
1611 =item *
1612  
1613 B<ArchiveRetrievalCompleted> This event occurs when a job that was
1614 initiated for an archive retrieval is completed (InitiateJob). The
1615 status of the completed job can be "Succeeded" or "Failed". The
1616 notification sent to the SNS topic is the same output as returned from
1617 DescribeJob.
1618  
1619 =item *
1620  
1621 B<InventoryRetrievalCompleted> This event occurs when a job that was
1622 initiated for an inventory retrieval is completed (InitiateJob). The
1623 status of the completed job can be "Succeeded" or "Failed". The
1624 notification sent to the SNS topic is the same output as returned from
1625 DescribeJob.
1626  
1627 =back
1628  
1629 An AWS account has full permission to perform all operations (actions).
1630 However, AWS Identity and Access Management (IAM) users don't have any
1631 permissions by default. You must grant them explicit permission to
1632 perform specific actions. For more information, see Access Control
1633 Using AWS Identity and Access Management (IAM)
1634 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
1635  
1636 For conceptual information and underlying REST API, see Configuring
1637 Vault Notifications in Amazon S3 Glacier
1638 (https://docs.aws.amazon.com/amazonglacier/latest/dev/configuring-notifications.html)
1639 and Set Vault Notification Configuration
1640 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-vault-notifications-put.html)
1641 in the I<Amazon Glacier Developer Guide>.
1642  
1643  
1644 =head2 UploadArchive
1645  
1646 =over
1647  
1648 =item AccountId => Str
1649  
1650 =item VaultName => Str
1651  
1652 =item [ArchiveDescription => Str]
1653  
1654 =item [Body => Str]
1655  
1656 =item [Checksum => Str]
1657  
1658  
1659 =back
1660  
1661 Each argument is described in detail in: L<Paws::Glacier::UploadArchive>
1662  
1663 Returns: a L<Paws::Glacier::ArchiveCreationOutput> instance
1664  
1665 This operation adds an archive to a vault. This is a synchronous
1666 operation, and for a successful upload, your data is durably persisted.
1667 Amazon S3 Glacier returns the archive ID in the C<x-amz-archive-id>
1668 header of the response.
1669  
1670 You must use the archive ID to access your data in Amazon S3 Glacier.
1671 After you upload an archive, you should save the archive ID returned so
1672 that you can retrieve or delete the archive later. Besides saving the
1673 archive ID, you can also index it and give it a friendly name to allow
1674 for better searching. You can also use the optional archive description
1675 field to specify how the archive is referred to in an external index of
1676 archives, such as you might create in Amazon DynamoDB. You can also get
1677 the vault inventory to obtain a list of archive IDs in a vault. For
1678 more information, see InitiateJob.
1679  
1680 You must provide a SHA256 tree hash of the data you are uploading. For
1681 information about computing a SHA256 tree hash, see Computing Checksums
1682 (https://docs.aws.amazon.com/amazonglacier/latest/dev/checksum-calculations.html).
1683  
1684 You can optionally specify an archive description of up to 1,024
1685 printable ASCII characters. You can get the archive description when
1686 you either retrieve the archive or get the vault inventory. For more
1687 information, see InitiateJob. Amazon Glacier does not interpret the
1688 description in any way. An archive description does not need to be
1689 unique. You cannot use the description to retrieve or sort the archive
1690 list.
1691  
1692 Archives are immutable. After you upload an archive, you cannot edit
1693 the archive or its description.
1694  
1695 An AWS account has full permission to perform all operations (actions).
1696 However, AWS Identity and Access Management (IAM) users don't have any
1697 permissions by default. You must grant them explicit permission to
1698 perform specific actions. For more information, see Access Control
1699 Using AWS Identity and Access Management (IAM)
1700 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
1701  
1702 For conceptual information and underlying REST API, see Uploading an
1703 Archive in Amazon Glacier
1704 (https://docs.aws.amazon.com/amazonglacier/latest/dev/uploading-an-archive.html)
1705 and Upload Archive
1706 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-archive-post.html)
1707 in the I<Amazon Glacier Developer Guide>.
1708  
1709  
1710 =head2 UploadMultipartPart
1711  
1712 =over
1713  
1714 =item AccountId => Str
1715  
1716 =item UploadId => Str
1717  
1718 =item VaultName => Str
1719  
1720 =item [Body => Str]
1721  
1722 =item [Checksum => Str]
1723  
1724 =item [Range => Str]
1725  
1726  
1727 =back
1728  
1729 Each argument is described in detail in: L<Paws::Glacier::UploadMultipartPart>
1730  
1731 Returns: a L<Paws::Glacier::UploadMultipartPartOutput> instance
1732  
1733 This operation uploads a part of an archive. You can upload archive
1734 parts in any order. You can also upload them in parallel. You can
1735 upload up to 10,000 parts for a multipart upload.
1736  
1737 Amazon Glacier rejects your upload part request if any of the following
1738 conditions is true:
1739  
1740 =over
1741  
1742 =item *
1743  
1744 B<SHA256 tree hash does not match>To ensure that part data is not
1745 corrupted in transmission, you compute a SHA256 tree hash of the part
1746 and include it in your request. Upon receiving the part data, Amazon S3
1747 Glacier also computes a SHA256 tree hash. If these hash values don't
1748 match, the operation fails. For information about computing a SHA256
1749 tree hash, see Computing Checksums
1750 (https://docs.aws.amazon.com/amazonglacier/latest/dev/checksum-calculations.html).
1751  
1752 =item *
1753  
1754 B<Part size does not match>The size of each part except the last must
1755 match the size specified in the corresponding InitiateMultipartUpload
1756 request. The size of the last part must be the same size as, or smaller
1757 than, the specified size.
1758  
1759 If you upload a part whose size is smaller than the part size you
1760 specified in your initiate multipart upload request and that part is
1761 not the last part, then the upload part request will succeed. However,
1762 the subsequent Complete Multipart Upload request will fail.
1763  
1764 =item *
1765  
1766 B<Range does not align>The byte range value in the request does not
1767 align with the part size specified in the corresponding initiate
1768 request. For example, if you specify a part size of 4194304 bytes (4
1769 MB), then 0 to 4194303 bytes (4 MB - 1) and 4194304 (4 MB) to 8388607
1770 (8 MB - 1) are valid part ranges. However, if you set a range value of
1771 2 MB to 6 MB, the range does not align with the part size and the
1772 upload will fail.
1773  
1774 =back
1775  
1776 This operation is idempotent. If you upload the same part multiple
1777 times, the data included in the most recent request overwrites the
1778 previously uploaded data.
1779  
1780 An AWS account has full permission to perform all operations (actions).
1781 However, AWS Identity and Access Management (IAM) users don't have any
1782 permissions by default. You must grant them explicit permission to
1783 perform specific actions. For more information, see Access Control
1784 Using AWS Identity and Access Management (IAM)
1785 (https://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html).
1786  
1787 For conceptual information and underlying REST API, see Uploading Large
1788 Archives in Parts (Multipart Upload)
1789 (https://docs.aws.amazon.com/amazonglacier/latest/dev/uploading-archive-mpu.html)
1790 and Upload Part
1791 (https://docs.aws.amazon.com/amazonglacier/latest/dev/api-upload-part.html)
1792 in the I<Amazon Glacier Developer Guide>.
1793  
1794  
1795  
1796  
1797 =head1 PAGINATORS
1798  
1799 Paginator methods are helpers that repetively call methods that return partial results
1800  
1801 =head2 ListAllJobs(sub { },AccountId => Str, VaultName => Str, [Completed => Str, Limit => Str, Marker => Str, Statuscode => Str])
1802  
1803 =head2 ListAllJobs(AccountId => Str, VaultName => Str, [Completed => Str, Limit => Str, Marker => Str, Statuscode => Str])
1804  
1805  
1806 If passed a sub as first parameter, it will call the sub for each element found in :
1807  
1808 - JobList, passing the object as the first parameter, and the string 'JobList' as the second parameter
1809  
1810 If not, it will return a a L<Paws::Glacier::ListJobsOutput> instance with all the C<param>s; from all the responses. Please take into account that this mode can potentially consume vasts ammounts of memory.
1811  
1812  
1813 =head2 ListAllMultipartUploads(sub { },AccountId => Str, VaultName => Str, [Limit => Str, Marker => Str])
1814  
1815 =head2 ListAllMultipartUploads(AccountId => Str, VaultName => Str, [Limit => Str, Marker => Str])
1816  
1817  
1818 If passed a sub as first parameter, it will call the sub for each element found in :
1819  
1820 - UploadsList, passing the object as the first parameter, and the string 'UploadsList' as the second parameter
1821  
1822 If not, it will return a a L<Paws::Glacier::ListMultipartUploadsOutput> instance with all the C<param>s; from all the responses. Please take into account that this mode can potentially consume vasts ammounts of memory.
1823  
1824  
1825 =head2 ListAllParts(sub { },AccountId => Str, UploadId => Str, VaultName => Str, [Limit => Str, Marker => Str])
1826  
1827 =head2 ListAllParts(AccountId => Str, UploadId => Str, VaultName => Str, [Limit => Str, Marker => Str])
1828  
1829  
1830 If passed a sub as first parameter, it will call the sub for each element found in :
1831  
1832 - Parts, passing the object as the first parameter, and the string 'Parts' as the second parameter
1833  
1834 If not, it will return a a L<Paws::Glacier::ListPartsOutput> instance with all the C<param>s; from all the responses. Please take into account that this mode can potentially consume vasts ammounts of memory.
1835  
1836  
1837 =head2 ListAllVaults(sub { },AccountId => Str, [Limit => Str, Marker => Str])
1838  
1839 =head2 ListAllVaults(AccountId => Str, [Limit => Str, Marker => Str])
1840  
1841  
1842 If passed a sub as first parameter, it will call the sub for each element found in :
1843  
1844 - VaultList, passing the object as the first parameter, and the string 'VaultList' as the second parameter
1845  
1846 If not, it will return a a L<Paws::Glacier::ListVaultsOutput> instance with all the C<param>s; from all the responses. Please take into account that this mode can potentially consume vasts ammounts of memory.
1847  
1848  
1849  
1850  
1851  
1852 =head1 SEE ALSO
1853  
1854 This service class forms part of L<Paws>
1855  
1856 =head1 BUGS and CONTRIBUTIONS
1857  
1858 The source code is located here: L<https://github.com/pplu/aws-sdk-perl>
1859  
1860 Please report bugs to: L<https://github.com/pplu/aws-sdk-perl/issues>
1861  
1862 =cut
1863  
« blib/lib/Paws/ElasticBeanstalk.pm ↑ Summary blib/lib/Paws/Support.pm »