aws/api: Update S3 API.
[software/guile-aws.git] / aws / api / s3-2006-03-01.normal.json
1 {
2 "version": "2.0",
3 "metadata": {
4 "apiVersion": "2006-03-01",
5 "checksumFormat": "md5",
6 "endpointPrefix": "s3",
7 "globalEndpoint": "s3.amazonaws.com",
8 "protocol": "rest-xml",
9 "serviceAbbreviation": "Amazon S3",
10 "serviceFullName": "Amazon Simple Storage Service",
11 "serviceId": "S3",
12 "signatureVersion": "s3",
13 "uid": "s3-2006-03-01"
14 },
15 "operations": {
16 "AbortMultipartUpload": {
17 "name": "AbortMultipartUpload",
18 "http": {
19 "method": "DELETE",
20 "requestUri": "/{Bucket}/{Key+}",
21 "responseCode": 204
22 },
23 "input": {
24 "shape": "AbortMultipartUploadRequest"
25 },
26 "output": {
27 "shape": "AbortMultipartUploadOutput"
28 },
29 "errors": [
30 {
31 "shape": "NoSuchUpload"
32 }
33 ],
34 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/mpUploadAbort.html",
35 "documentation": "<p>This operation aborts a multipart upload. After a multipart upload is aborted, no additional parts can be uploaded using that upload ID. The storage consumed by any previously uploaded parts will be freed. However, if any part uploads are currently in progress, those part uploads might or might not succeed. As a result, it might be necessary to abort a given multipart upload multiple times in order to completely free all storage consumed by all parts. </p> <p>To verify that all parts have been removed, so you don't get charged for the part storage, you should call the <a>ListParts</a> operation and ensure that the parts list is empty.</p> <p>For information about permissions required to use the multipart upload API, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload API and Permissions</a>.</p> <p>The following operations are related to <code>AbortMultipartUpload</code>:</p> <ul> <li> <p> <a>CreateMultipartUpload</a> </p> </li> <li> <p> <a>UploadPart</a> </p> </li> <li> <p> <a>CompleteMultipartUpload</a> </p> </li> <li> <p> <a>ListParts</a> </p> </li> <li> <p> <a>ListMultipartUploads</a> </p> </li> </ul>"
36 },
37 "CompleteMultipartUpload": {
38 "name": "CompleteMultipartUpload",
39 "http": {
40 "method": "POST",
41 "requestUri": "/{Bucket}/{Key+}"
42 },
43 "input": {
44 "shape": "CompleteMultipartUploadRequest"
45 },
46 "output": {
47 "shape": "CompleteMultipartUploadOutput"
48 },
49 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/mpUploadComplete.html",
50 "documentation": "<p>Completes a multipart upload by assembling previously uploaded parts.</p> <p>You first initiate the multipart upload and then upload all parts using the <a>UploadPart</a> operation. After successfully uploading all relevant parts of an upload, you call this operation to complete the upload. Upon receiving this request, Amazon S3 concatenates all the parts in ascending order by part number to create a new object. In the Complete Multipart Upload request, you must provide the parts list. You must ensure that the parts list is complete. This operation concatenates the parts that you provide in the list. For each part in the list, you must provide the part number and the <code>ETag</code> value, returned after that part was uploaded.</p> <p>Processing of a Complete Multipart Upload request could take several minutes to complete. After Amazon S3 begins processing the request, it sends an HTTP response header that specifies a 200 OK response. While processing is in progress, Amazon S3 periodically sends white space characters to keep the connection from timing out. Because a request could fail after the initial 200 OK response has been sent, it is important that you check the response body to determine whether the request succeeded.</p> <p>Note that if <code>CompleteMultipartUpload</code> fails, applications should be prepared to retry the failed requests. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ErrorBestPractices.html\">Amazon S3 Error Best Practices</a>.</p> <p>For more information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading Objects Using Multipart Upload</a>.</p> <p>For information about permissions required to use the multipart upload API, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload API and Permissions</a>.</p> <p> <code>GetBucketLifecycle</code> has the following special errors:</p> <ul> <li> <p>Error code: <code>EntityTooSmall</code> </p> <ul> <li> <p>Description: Your proposed upload is smaller than the minimum allowed object size. Each part must be at least 5 MB in size, except the last part.</p> </li> <li> <p>400 Bad Request</p> </li> </ul> </li> <li> <p>Error code: <code>InvalidPart</code> </p> <ul> <li> <p>Description: One or more of the specified parts could not be found. The part might not have been uploaded, or the specified entity tag might not have matched the part's entity tag.</p> </li> <li> <p>400 Bad Request</p> </li> </ul> </li> <li> <p>Error code: <code>InvalidPartOrder</code> </p> <ul> <li> <p>Description: The list of parts was not in ascending order. The parts list must be specified in order by part number.</p> </li> <li> <p>400 Bad Request</p> </li> </ul> </li> <li> <p>Error code: <code>NoSuchUpload</code> </p> <ul> <li> <p>Description: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.</p> </li> <li> <p>404 Not Found</p> </li> </ul> </li> </ul> <p>The following operations are related to <code>DeleteBucketMetricsConfiguration</code>:</p> <ul> <li> <p> <a>CreateMultipartUpload</a> </p> </li> <li> <p> <a>UploadPart</a> </p> </li> <li> <p> <a>AbortMultipartUpload</a> </p> </li> <li> <p> <a>ListParts</a> </p> </li> <li> <p> <a>ListMultipartUploads</a> </p> </li> </ul>"
51 },
52 "CopyObject": {
53 "name": "CopyObject",
54 "http": {
55 "method": "PUT",
56 "requestUri": "/{Bucket}/{Key+}"
57 },
58 "input": {
59 "shape": "CopyObjectRequest"
60 },
61 "output": {
62 "shape": "CopyObjectOutput"
63 },
64 "errors": [
65 {
66 "shape": "ObjectNotInActiveTierError"
67 }
68 ],
69 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTObjectCOPY.html",
70 "documentation": "<p>Creates a copy of an object that is already stored in Amazon S3.</p> <note> <p>You can store individual objects of up to 5 TB in Amazon S3. You create a copy of your object up to 5 GB in size in a single atomic operation using this API. However, for copying an object greater than 5 GB, you must use the multipart upload Upload Part - Copy API. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjctsUsingRESTMPUapi.html\">Copy Object Using the REST Multipart Upload API</a>.</p> </note> <p>When copying an object, you can preserve all metadata (default) or specify new metadata. However, the ACL is not preserved and is set to private for the user making the request. To override the default ACL setting, specify a new ACL when generating a copy request. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Using ACLs</a>.</p> <important> <p>Amazon S3 transfer acceleration does not support cross-region copies. If you request a cross-region copy using a transfer acceleration endpoint, you get a 400 <code>Bad Request</code> error. For more information about transfer acceleration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html\">Transfer Acceleration</a>.</p> </important> <p>All copy requests must be authenticated. Additionally, you must have <i>read</i> access to the source object and <i>write</i> access to the destination bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html\">REST Authentication</a>. Both the Region that you want to copy the object from and the Region that you want to copy the object to must be enabled for your account.</p> <p>To only copy an object under certain conditions, such as whether the <code>Etag</code> matches or whether the object was modified before or after a specified date, use the request parameters <code>x-amz-copy-source-if-match</code>, <code>x-amz-copy-source-if-none-match</code>, <code>x-amz-copy-source-if-unmodified-since</code>, or <code> x-amz-copy-source-if-modified-since</code>.</p> <note> <p>All headers with the <code>x-amz-</code> prefix, including <code>x-amz-copy-source</code>, must be signed.</p> </note> <p>You can use this operation to change the storage class of an object that is already stored in Amazon S3 using the <code>StorageClass</code> parameter. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html\">Storage Classes</a>.</p> <p>The source object that you are copying can be encrypted or unencrypted. If the source object is encrypted, it can be encrypted by server-side encryption using AWS managed encryption keys or by using a customer-provided encryption key. When copying an object, you can request that Amazon S3 encrypt the target object by using either the AWS managed encryption keys or by using your own encryption key. You can do this regardless of the form of server-side encryption that was used to encrypt the source, or even if the source object was not encrypted. For more information about server-side encryption, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html\">Using Server-Side Encryption</a>.</p> <p>A copy request might return an error when Amazon S3 receives the copy request or while Amazon S3 is copying the files. If the error occurs before the copy operation starts, you receive a standard Amazon S3 error. If the error occurs during the copy operation, the error response is embedded in the <code>200 OK</code> response. This means that a <code>200 OK</code> response can contain either a success or an error. Design your application to parse the contents of the response and handle it appropriately.</p> <p>If the copy is successful, you receive a response with information about the copied object.</p> <note> <p>If the request is an HTTP 1.1 request, the response is chunk encoded. If it were not, it would not contain the content-length, and you would need to read the entire body.</p> </note> <p>Consider the following when using request headers:</p> <ul> <li> <p> Consideration 1 – If both the <code>x-amz-copy-source-if-match</code> and <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the request and evaluate as follows, Amazon S3 returns 200 OK and copies the data:</p> <ul> <li> <p> <code>x-amz-copy-source-if-match</code> condition evaluates to true</p> </li> <li> <p> <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to false</p> </li> </ul> </li> <li> <p> Consideration 2 – If both of the <code>x-amz-copy-source-if-none-match</code> and <code>x-amz-copy-source-if-modified-since</code> headers are present in the request and evaluate as follows, Amazon S3 returns the <code>412 Precondition Failed</code> response code:</p> <ul> <li> <p> <code>x-amz-copy-source-if-none-match</code> condition evaluates to false</p> </li> <li> <p> <code>x-amz-copy-source-if-modified-since</code> condition evaluates to true</p> </li> </ul> </li> </ul> <p>The copy request charge is based on the storage class and Region you specify for the destination object. For pricing information, see <a href=\"https://aws.amazon.com/s3/pricing/\">Amazon S3 Pricing</a>.</p> <p>Following are other considerations when using <code>CopyObject</code>:</p> <dl> <dt>Versioning</dt> <dd> <p>By default, <code>x-amz-copy-source</code> identifies the current version of an object to copy. (If the current version is a delete marker, Amazon S3 behaves as if the object was deleted.) To copy a different version, use the <code>versionId</code> subresource.</p> <p>If you enable versioning on the target bucket, Amazon S3 generates a unique version ID for the object being copied. This version ID is different from the version ID of the source object. Amazon S3 returns the version ID of the copied object in the <code>x-amz-version-id</code> response header in the response.</p> <p>If you do not enable versioning or suspend it on the target bucket, the version ID that Amazon S3 generates is always null.</p> <p>If the source object's storage class is GLACIER, you must restore a copy of this object before you can use it as a source object for the copy operation. For more information, see .</p> </dd> <dt>Access Permissions</dt> <dd> <p>When copying an object, you can optionally specify the accounts or groups that should be granted specific permissions on the new object. There are two ways to grant the permissions using the request headers:</p> <ul> <li> <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned ACL</a>.</p> </li> <li> <p>Specify access permissions explicitly with the <code>x-amz-grant-read</code>, <code>x-amz-grant-read-acp</code>, <code>x-amz-grant-write-acp</code>, and <code>x-amz-grant-full-control</code> headers. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>.</p> </li> </ul> <p>You can use either a canned ACL or specify access permissions explicitly. You cannot do both.</p> </dd> <dt>Server-Side- Encryption-Specific Request Headers</dt> <dd> <p>To encrypt the target object, you must provide the appropriate encryption-related request headers. The one you use depends on whether you want to use AWS managed encryption keys or provide your own encryption key. </p> <ul> <li> <p>To encrypt the target object using server-side encryption with an AWS managed encryption key, provide the following request headers, as appropriate.</p> <ul> <li> <p> <code>x-amz-server-side​-encryption</code> </p> </li> <li> <p> <code>x-amz-server-side-encryption-aws-kms-key-id</code> </p> </li> <li> <p> <code>x-amz-server-side-encryption-context</code> </p> </li> </ul> <note> <p>If you specify <code>x-amz-server-side-encryption:aws:kms</code>, but don't provide <code>x-amz-server-side-encryption-aws-kms-key-id</code>, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data. If you want to use a customer managed AWS KMS CMK, you must provide the <code>x-amz-server-side-encryption-aws-kms-key-id</code> of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and not asymmetric CMKs. For more information, see <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html\">Using Symmetric and Asymmetric Keys</a> in the <i>AWS Key Management Service Developer Guide</i>.</p> </note> <important> <p>All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.</p> </important> <p>For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html\">Protecting Data Using Server-Side Encryption with CMKs stored in KMS</a>.</p> </li> <li> <p>To encrypt the target object using server-side encryption with an encryption key that you provide, use the following headers.</p> <ul> <li> <p>x-amz-server-side​-encryption​-customer-algorithm</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key-MD5</p> </li> </ul> </li> <li> <p>If the source object is encrypted using server-side encryption with customer-provided encryption keys, you must use the following headers.</p> <ul> <li> <p>x-amz-copy-source​-server-side​-encryption​-customer-algorithm</p> </li> <li> <p>x-amz-copy-source​-server-side​-encryption​-customer-key</p> </li> <li> <p>x-amz-copy-source-​server-side​-encryption​-customer-key-MD5</p> </li> </ul> <p>For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html\">Protecting Data Using Server-Side Encryption with CMKs stored in Amazon KMS</a>.</p> </li> </ul> </dd> <dt>Access-Control-List (ACL)-Specific Request Headers</dt> <dd> <p>You also can use the following access control–related headers with this operation. By default, all objects are private. Only the owner has full access control. When adding a new object, you can grant permissions to individual AWS accounts or to predefined groups defined by Amazon S3. These permissions are then added to the access control list (ACL) on the object. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Using ACLs</a>. With this operation, you can grant access permissions using one of the following two methods:</p> <ul> <li> <p>Specify a canned ACL (<code>x-amz-acl</code>) — Amazon S3 supports a set of predefined ACLs, known as <i>canned ACLs</i>. Each canned ACL has a predefined set of grantees and permissions. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned ACL</a>.</p> </li> <li> <p>Specify access permissions explicitly — To explicitly grant access permissions to specific AWS accounts or groups, use the following headers. Each header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>. In the header, you specify a list of grantees who get the specific permission. To grant permissions explicitly, use:</p> <ul> <li> <p>x-amz-grant-read</p> </li> <li> <p>x-amz-grant-write</p> </li> <li> <p>x-amz-grant-read-acp</p> </li> <li> <p>x-amz-grant-write-acp</p> </li> <li> <p>x-amz-grant-full-control</p> </li> </ul> <p>You specify each grantee as a type=value pair, where the type is one of the following:</p> <ul> <li> <p> <code>emailAddress</code> – if the value specified is the email address of an AWS account</p> </li> <li> <p> <code>id</code> – if the value specified is the canonical user ID of an AWS account</p> </li> <li> <p> <code>uri</code> – if you are granting permissions to a predefined group</p> </li> </ul> <p>For example, the following <code>x-amz-grant-read</code> header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:</p> <p> <code>x-amz-grant-read: emailAddress=\"xyz@amazon.com\", emailAddress=\"abc@amazon.com\" </code> </p> </li> </ul> </dd> </dl> <p>The following operations are related to <code>CopyObject</code>:</p> <ul> <li> <p> <a>PutObject</a> </p> </li> <li> <p> <a>GetObject</a> </p> </li> </ul> <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjectsExamples.html\">Copying Objects</a>.</p>",
71 "alias": "PutObjectCopy"
72 },
73 "CreateBucket": {
74 "name": "CreateBucket",
75 "http": {
76 "method": "PUT",
77 "requestUri": "/{Bucket}"
78 },
79 "input": {
80 "shape": "CreateBucketRequest"
81 },
82 "output": {
83 "shape": "CreateBucketOutput"
84 },
85 "errors": [
86 {
87 "shape": "BucketAlreadyExists"
88 },
89 {
90 "shape": "BucketAlreadyOwnedByYou"
91 }
92 ],
93 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketPUT.html",
94 "documentation": "<p>Creates a new bucket. To create a bucket, you must register with Amazon S3 and have a valid AWS Access Key ID to authenticate requests. Anonymous requests are never allowed to create buckets. By creating the bucket, you become the bucket owner.</p> <p>Not every string is an acceptable bucket name. For information on bucket naming restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html\">Working with Amazon S3 Buckets</a>.</p> <p>By default, the bucket is created in the US East (N. Virginia) Region. You can optionally specify a Region in the request body. You might choose a Region to optimize latency, minimize costs, or address regulatory requirements. For example, if you reside in Europe, you will probably find it advantageous to create buckets in the EU (Ireland) Region. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro\">How to Select a Region for Your Buckets</a>.</p> <note> <p>If you send your create bucket request to the <code>s3.amazonaws.com</code> endpoint, the request goes to the us-east-1 Region. Accordingly, the signature calculations in Signature Version 4 must use us-east-1 as the Region, even if the location constraint in the request specifies another Region where the bucket is to be created. If you create a bucket in a Region other than US East (N. Virginia), your application must be able to handle 307 redirect. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html\">Virtual Hosting of Buckets</a>.</p> </note> <p>When creating a bucket using this operation, you can optionally specify the accounts or groups that should be granted specific permissions on the bucket. There are two ways to grant the appropriate permissions using the request headers.</p> <ul> <li> <p>Specify a canned ACL using the <code>x-amz-acl</code> request header. Amazon S3 supports a set of predefined ACLs, known as <i>canned ACLs</i>. Each canned ACL has a predefined set of grantees and permissions. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned ACL</a>.</p> </li> <li> <p>Specify access permissions explicitly using the <code>x-amz-grant-read</code>, <code>x-amz-grant-write</code>, <code>x-amz-grant-read-acp</code>, <code>x-amz-grant-write-acp</code>, and <code>x-amz-grant-full-control</code> headers. These headers map to the set of permissions Amazon S3 supports in an ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>.</p> <p>You specify each grantee as a type=value pair, where the type is one of the following:</p> <ul> <li> <p> <code>emailAddress</code> – if the value specified is the email address of an AWS account</p> </li> <li> <p> <code>id</code> – if the value specified is the canonical user ID of an AWS account</p> </li> <li> <p> <code>uri</code> – if you are granting permissions to a predefined group</p> </li> </ul> <p>For example, the following <code>x-amz-grant-read</code> header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:</p> <p> <code>x-amz-grant-read: emailAddress=\"xyz@amazon.com\", emailAddress=\"abc@amazon.com\" </code> </p> </li> </ul> <note> <p>You can use either a canned ACL or specify access permissions explicitly. You cannot do both.</p> </note> <p>The following operations are related to <code>CreateBucket</code>:</p> <ul> <li> <p> <a>PutObject</a> </p> </li> <li> <p> <a>DeleteBucket</a> </p> </li> </ul>",
95 "alias": "PutBucket"
96 },
97 "CreateMultipartUpload": {
98 "name": "CreateMultipartUpload",
99 "http": {
100 "method": "POST",
101 "requestUri": "/{Bucket}/{Key+}?uploads"
102 },
103 "input": {
104 "shape": "CreateMultipartUploadRequest"
105 },
106 "output": {
107 "shape": "CreateMultipartUploadOutput"
108 },
109 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/mpUploadInitiate.html",
110 "documentation": "<p>This operation initiates a multipart upload and returns an upload ID. This upload ID is used to associate all of the parts in the specific multipart upload. You specify this upload ID in each of your subsequent upload part requests (see <a>UploadPart</a>). You also include this upload ID in the final request to either complete or abort the multipart upload request.</p> <p>For more information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html\">Multipart Upload Overview</a>.</p> <p>If you have configured a lifecycle rule to abort incomplete multipart uploads, the upload must complete within the number of days specified in the bucket lifecycle configuration. Otherwise, the incomplete multipart upload becomes eligible for an abort operation and Amazon S3 aborts the multipart upload. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config\">Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle Policy</a>.</p> <p>For information about the permissions required to use the multipart upload API, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload API and Permissions</a>.</p> <p>For request signing, multipart upload is just a series of regular requests. You initiate a multipart upload, send one or more requests to upload parts, and then complete the multipart upload process. You sign each request individually. There is nothing special about signing multipart upload requests. For more information about signing, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html\">Authenticating Requests (AWS Signature Version 4)</a>.</p> <note> <p> After you initiate a multipart upload and upload one or more parts, to stop being charged for storing the uploaded parts, you must either complete or abort the multipart upload. Amazon S3 frees up the space used to store the parts and stop charging you for storing them only after you either complete or abort a multipart upload. </p> </note> <p>You can optionally request server-side encryption. For server-side encryption, Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. You can provide your own encryption key, or use AWS Key Management Service (AWS KMS) customer master keys (CMKs) or Amazon S3-managed encryption keys. If you choose to provide your own encryption key, the request headers you provide in <a>UploadPart</a>) and <a>UploadPartCopy</a>) requests must match the headers you used in the request to initiate the upload by using <code>CreateMultipartUpload</code>. </p> <p>To perform a multipart upload with encryption using an AWS KMS CMK, the requester must have permission to the <code>kms:Encrypt</code>, <code>kms:Decrypt</code>, <code>kms:ReEncrypt*</code>, <code>kms:GenerateDataKey*</code>, and <code>kms:DescribeKey</code> actions on the key. These permissions are required because Amazon S3 must decrypt and read data from the encrypted file parts before it completes the multipart upload.</p> <p>If your AWS Identity and Access Management (IAM) user or role is in the same AWS account as the AWS KMS CMK, then you must have these permissions on the key policy. If your IAM user or role belongs to a different account than the key, then you must have the permissions on both the key policy and your IAM user or role.</p> <p> For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html\">Protecting Data Using Server-Side Encryption</a>.</p> <dl> <dt>Access Permissions</dt> <dd> <p>When copying an object, you can optionally specify the accounts or groups that should be granted specific permissions on the new object. There are two ways to grant the permissions using the request headers:</p> <ul> <li> <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned ACL</a>.</p> </li> <li> <p>Specify access permissions explicitly with the <code>x-amz-grant-read</code>, <code>x-amz-grant-read-acp</code>, <code>x-amz-grant-write-acp</code>, and <code>x-amz-grant-full-control</code> headers. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>.</p> </li> </ul> <p>You can use either a canned ACL or specify access permissions explicitly. You cannot do both.</p> </dd> <dt>Server-Side- Encryption-Specific Request Headers</dt> <dd> <p>You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. The option you use depends on whether you want to use AWS managed encryption keys or provide your own encryption key. </p> <ul> <li> <p>Use encryption keys managed by Amazon S3 or customer master keys (CMKs) stored in AWS Key Management Service (AWS KMS) – If you want AWS to manage the keys used to encrypt data, specify the following headers in the request.</p> <ul> <li> <p>x-amz-server-side​-encryption</p> </li> <li> <p>x-amz-server-side-encryption-aws-kms-key-id</p> </li> <li> <p>x-amz-server-side-encryption-context</p> </li> </ul> <note> <p>If you specify <code>x-amz-server-side-encryption:aws:kms</code>, but don't provide <code>x-amz-server-side-encryption-aws-kms-key-id</code>, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data.</p> </note> <important> <p>All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.</p> </important> <p>For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html\">Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS</a>.</p> </li> <li> <p>Use customer-provided encryption keys – If you want to manage your own encryption keys, provide all the following headers in the request.</p> <ul> <li> <p>x-amz-server-side​-encryption​-customer-algorithm</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key-MD5</p> </li> </ul> <p>For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html\">Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS</a>.</p> </li> </ul> </dd> <dt>Access-Control-List (ACL)-Specific Request Headers</dt> <dd> <p>You also can use the following access control–related headers with this operation. By default, all objects are private. Only the owner has full access control. When adding a new object, you can grant permissions to individual AWS accounts or to predefined groups defined by Amazon S3. These permissions are then added to the access control list (ACL) on the object. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Using ACLs</a>. With this operation, you can grant access permissions using one of the following two methods:</p> <ul> <li> <p>Specify a canned ACL (<code>x-amz-acl</code>) — Amazon S3 supports a set of predefined ACLs, known as <i>canned ACLs</i>. Each canned ACL has a predefined set of grantees and permissions. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned ACL</a>.</p> </li> <li> <p>Specify access permissions explicitly — To explicitly grant access permissions to specific AWS accounts or groups, use the following headers. Each header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>. In the header, you specify a list of grantees who get the specific permission. To grant permissions explicitly, use:</p> <ul> <li> <p>x-amz-grant-read</p> </li> <li> <p>x-amz-grant-write</p> </li> <li> <p>x-amz-grant-read-acp</p> </li> <li> <p>x-amz-grant-write-acp</p> </li> <li> <p>x-amz-grant-full-control</p> </li> </ul> <p>You specify each grantee as a type=value pair, where the type is one of the following:</p> <ul> <li> <p> <code>emailAddress</code> – if the value specified is the email address of an AWS account</p> </li> <li> <p> <code>id</code> – if the value specified is the canonical user ID of an AWS account</p> </li> <li> <p> <code>uri</code> – if you are granting permissions to a predefined group</p> </li> </ul> <p>For example, the following <code>x-amz-grant-read</code> header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:</p> <p> <code>x-amz-grant-read: emailAddress=\"xyz@amazon.com\", emailAddress=\"abc@amazon.com\" </code> </p> </li> </ul> </dd> </dl> <p>The following operations are related to <code>CreateMultipartUpload</code>:</p> <ul> <li> <p> <a>UploadPart</a> </p> </li> <li> <p> <a>CompleteMultipartUpload</a> </p> </li> <li> <p> <a>AbortMultipartUpload</a> </p> </li> <li> <p> <a>ListParts</a> </p> </li> <li> <p> <a>ListMultipartUploads</a> </p> </li> </ul>",
111 "alias": "InitiateMultipartUpload"
112 },
113 "DeleteBucket": {
114 "name": "DeleteBucket",
115 "http": {
116 "method": "DELETE",
117 "requestUri": "/{Bucket}",
118 "responseCode": 204
119 },
120 "input": {
121 "shape": "DeleteBucketRequest"
122 },
123 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketDELETE.html",
124 "documentation": "<p>Deletes the bucket. All objects (including all object versions and delete markers) in the bucket must be deleted before the bucket itself can be deleted.</p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> </p> </li> <li> <p> </p> </li> </ul>"
125 },
126 "DeleteBucketAnalyticsConfiguration": {
127 "name": "DeleteBucketAnalyticsConfiguration",
128 "http": {
129 "method": "DELETE",
130 "requestUri": "/{Bucket}?analytics",
131 "responseCode": 204
132 },
133 "input": {
134 "shape": "DeleteBucketAnalyticsConfigurationRequest"
135 },
136 "documentation": "<p>Deletes an analytics configuration for the bucket (specified by the analytics configuration ID).</p> <p>To use this operation, you must have permissions to perform the <code>s3:PutAnalyticsConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p>For information about the Amazon S3 analytics feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html\">Amazon S3 Analytics – Storage Class Analysis</a>. </p> <p>The following operations are related to <code>DeleteBucketAnalyticsConfiguration</code>:</p> <ul> <li> <p> </p> </li> <li> <p> </p> </li> <li> <p> </p> </li> </ul>"
137 },
138 "DeleteBucketCors": {
139 "name": "DeleteBucketCors",
140 "http": {
141 "method": "DELETE",
142 "requestUri": "/{Bucket}?cors",
143 "responseCode": 204
144 },
145 "input": {
146 "shape": "DeleteBucketCorsRequest"
147 },
148 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketDELETEcors.html",
149 "documentation": "<p>Deletes the <code>cors</code> configuration information set for the bucket.</p> <p>To use this operation, you must have permission to perform the <code>s3:PutBucketCORS</code> action. The bucket owner has this permission by default and can grant this permission to others. </p> <p>For information about <code>cors</code>, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html\">Enabling Cross-Origin Resource Sharing</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p class=\"title\"> <b>Related Resources:</b> </p> <ul> <li> <p> </p> </li> <li> <p> <a>RESTOPTIONSobject</a> </p> </li> </ul>"
150 },
151 "DeleteBucketEncryption": {
152 "name": "DeleteBucketEncryption",
153 "http": {
154 "method": "DELETE",
155 "requestUri": "/{Bucket}?encryption",
156 "responseCode": 204
157 },
158 "input": {
159 "shape": "DeleteBucketEncryptionRequest"
160 },
161 "documentation": "<p>This implementation of the DELETE operation removes default encryption from the bucket. For information about the Amazon S3 default encryption feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//bucket-encryption.html\">Amazon S3 Default Bucket Encryption</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p>To use this operation, you must have permissions to perform the <code>s3:PutEncryptionConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//s3-access-control.html\">Managing Access Permissions to your Amazon S3 Resources</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>PutBucketEncryption</a> </p> </li> <li> <p> <a>GetBucketEncryption</a> </p> </li> </ul>"
162 },
163 "DeleteBucketInventoryConfiguration": {
164 "name": "DeleteBucketInventoryConfiguration",
165 "http": {
166 "method": "DELETE",
167 "requestUri": "/{Bucket}?inventory",
168 "responseCode": 204
169 },
170 "input": {
171 "shape": "DeleteBucketInventoryConfigurationRequest"
172 },
173 "documentation": "<p>Deletes an inventory configuration (identified by the inventory ID) from the bucket.</p> <p>To use this operation, you must have permissions to perform the <code>s3:PutInventoryConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p>For information about the Amazon S3 inventory feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html\">Amazon S3 Inventory</a>.</p> <p>Operations related to <code>DeleteBucketInventoryConfiguration</code> include: </p> <ul> <li> <p> <a>GetBucketInventoryConfiguration</a> </p> </li> <li> <p> <a>PutBucketInventoryConfiguration</a> </p> </li> <li> <p> <a>ListBucketInventoryConfigurations</a> </p> </li> </ul>"
174 },
175 "DeleteBucketLifecycle": {
176 "name": "DeleteBucketLifecycle",
177 "http": {
178 "method": "DELETE",
179 "requestUri": "/{Bucket}?lifecycle",
180 "responseCode": 204
181 },
182 "input": {
183 "shape": "DeleteBucketLifecycleRequest"
184 },
185 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketDELETElifecycle.html",
186 "documentation": "<p>Deletes the lifecycle configuration from the specified bucket. Amazon S3 removes all the lifecycle configuration rules in the lifecycle subresource associated with the bucket. Your objects never expire, and Amazon S3 no longer automatically deletes any objects on the basis of rules contained in the deleted lifecycle configuration.</p> <p>To use this operation, you must have permission to perform the <code>s3:PutLifecycleConfiguration</code> action. By default, the bucket owner has this permission and the bucket owner can grant this permission to others.</p> <p>There is usually some time lag before lifecycle configuration deletion is fully propagated to all the Amazon S3 systems.</p> <p>For more information about the object expiration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html#intro-lifecycle-rules-actions\">Elements to Describe Lifecycle Actions</a>.</p> <p>Related actions include:</p> <ul> <li> <p> <a>PutBucketLifecycleConfiguration</a> </p> </li> <li> <p> <a>GetBucketLifecycleConfiguration</a> </p> </li> </ul>"
187 },
188 "DeleteBucketMetricsConfiguration": {
189 "name": "DeleteBucketMetricsConfiguration",
190 "http": {
191 "method": "DELETE",
192 "requestUri": "/{Bucket}?metrics",
193 "responseCode": 204
194 },
195 "input": {
196 "shape": "DeleteBucketMetricsConfigurationRequest"
197 },
198 "documentation": "<p>Deletes a metrics configuration for the Amazon CloudWatch request metrics (specified by the metrics configuration ID) from the bucket. Note that this doesn't include the daily storage metrics.</p> <p> To use this operation, you must have permissions to perform the <code>s3:PutMetricsConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p>For information about CloudWatch request metrics for Amazon S3, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html\">Monitoring Metrics with Amazon CloudWatch</a>. </p> <p>The following operations are related to <code>DeleteBucketMetricsConfiguration</code>:</p> <ul> <li> <p> <a>GetBucketMetricsConfiguration</a> </p> </li> <li> <p> <a>PutBucketMetricsConfiguration</a> </p> </li> <li> <p> <a>ListBucketMetricsConfigurations</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html\">Monitoring Metrics with Amazon CloudWatch</a> </p> </li> </ul>"
199 },
200 "DeleteBucketPolicy": {
201 "name": "DeleteBucketPolicy",
202 "http": {
203 "method": "DELETE",
204 "requestUri": "/{Bucket}?policy",
205 "responseCode": 204
206 },
207 "input": {
208 "shape": "DeleteBucketPolicyRequest"
209 },
210 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketDELETEpolicy.html",
211 "documentation": "<p>This implementation of the DELETE operation uses the policy subresource to delete the policy of a specified bucket. If you are using an identity other than the root user of the AWS account that owns the bucket, the calling identity must have the <code>DeleteBucketPolicy</code> permissions on the specified bucket and belong to the bucket owner's account to use this operation. </p> <p>If you don't have <code>DeleteBucketPolicy</code> permissions, Amazon S3 returns a <code>403 Access Denied</code> error. If you have the correct permissions, but you're not using an identity that belongs to the bucket owner's account, Amazon S3 returns a <code>405 Method Not Allowed</code> error. </p> <important> <p>As a security precaution, the root user of the AWS account that owns a bucket can always use this operation, even if the policy explicitly denies the root user the ability to perform this action.</p> </important> <p>For more information about bucket policies, see <a href=\" https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html\">Using Bucket Policies and UserPolicies</a>. </p> <p>The following operations are related to <code>DeleteBucketPolicy</code> </p> <ul> <li> <p> <a>CreateBucket</a> </p> </li> <li> <p> <a>DeleteObject</a> </p> </li> </ul>"
212 },
213 "DeleteBucketReplication": {
214 "name": "DeleteBucketReplication",
215 "http": {
216 "method": "DELETE",
217 "requestUri": "/{Bucket}?replication",
218 "responseCode": 204
219 },
220 "input": {
221 "shape": "DeleteBucketReplicationRequest"
222 },
223 "documentation": "<p> Deletes the replication configuration from the bucket.</p> <p>To use this operation, you must have permissions to perform the <code>s3:PutReplicationConfiguration</code> action. The bucket owner has these permissions by default and can grant it to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>. </p> <note> <p>It can take a while for the deletion of a replication configuration to fully propagate.</p> </note> <p> For information about replication configuration, see <a href=\" https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html\">Replication</a> in the <i>Amazon S3 Developer Guide</i>. </p> <p>The following operations are related to <code>DeleteBucketReplication</code>:</p> <ul> <li> <p> <a>PutBucketReplication</a> </p> </li> <li> <p> <a>GetBucketReplication</a> </p> </li> </ul>"
224 },
225 "DeleteBucketTagging": {
226 "name": "DeleteBucketTagging",
227 "http": {
228 "method": "DELETE",
229 "requestUri": "/{Bucket}?tagging",
230 "responseCode": 204
231 },
232 "input": {
233 "shape": "DeleteBucketTaggingRequest"
234 },
235 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketDELETEtagging.html",
236 "documentation": "<p>Deletes the tags from the bucket.</p> <p>To use this operation, you must have permission to perform the <code>s3:PutBucketTagging</code> action. By default, the bucket owner has this permission and can grant this permission to others. </p> <p>The following operations are related to <code>DeleteBucketTagging</code>:</p> <ul> <li> <p> <a>GetBucketTagging</a> </p> </li> <li> <p> <a>PutBucketTagging</a> </p> </li> </ul>"
237 },
238 "DeleteBucketWebsite": {
239 "name": "DeleteBucketWebsite",
240 "http": {
241 "method": "DELETE",
242 "requestUri": "/{Bucket}?website",
243 "responseCode": 204
244 },
245 "input": {
246 "shape": "DeleteBucketWebsiteRequest"
247 },
248 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketDELETEwebsite.html",
249 "documentation": "<p>This operation removes the website configuration for a bucket. Amazon S3 returns a <code>200 OK</code> response upon successfully deleting a website configuration on the specified bucket. You will get a <code>200 OK</code> response if the website configuration you are trying to delete does not exist on the bucket. Amazon S3 returns a <code>404</code> response if the bucket specified in the request does not exist.</p> <p>This DELETE operation requires the <code>S3:DeleteBucketWebsite</code> permission. By default, only the bucket owner can delete the website configuration attached to a bucket. However, bucket owners can grant other users permission to delete the website configuration by writing a bucket policy granting them the <code>S3:DeleteBucketWebsite</code> permission. </p> <p>For more information about hosting websites, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html\">Hosting Websites on Amazon S3</a>. </p> <p>The following operations are related to <code>DeleteBucketWebsite</code>:</p> <ul> <li> <p> <a>GetBucketWebsite</a> </p> </li> <li> <p> <a>PutBucketWebsite</a> </p> </li> </ul>"
250 },
251 "DeleteObject": {
252 "name": "DeleteObject",
253 "http": {
254 "method": "DELETE",
255 "requestUri": "/{Bucket}/{Key+}",
256 "responseCode": 204
257 },
258 "input": {
259 "shape": "DeleteObjectRequest"
260 },
261 "output": {
262 "shape": "DeleteObjectOutput"
263 },
264 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTObjectDELETE.html",
265 "documentation": "<p>Removes the null version (if there is one) of an object and inserts a delete marker, which becomes the latest version of the object. If there isn't a null version, Amazon S3 does not remove any objects.</p> <p>To remove a specific version, you must be the bucket owner and you must use the version Id subresource. Using this subresource permanently deletes the version. If the object deleted is a delete marker, Amazon S3 sets the response header, <code>x-amz-delete-marker</code>, to true. </p> <p>If the object you want to delete is in a bucket where the bucket versioning configuration is MFA Delete enabled, you must include the <code>x-amz-mfa</code> request header in the DELETE <code>versionId</code> request. Requests that include <code>x-amz-mfa</code> must use HTTPS. </p> <p> For more information about MFA Delete, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMFADelete.html\">Using MFA Delete</a>. To see sample requests that use versioning, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectDELETE.html#ExampleVersionObjectDelete\">Sample Request</a>. </p> <p>You can delete objects by explicitly calling the DELETE Object API or configure its lifecycle (<a>PutBucketLifecycle</a>) to enable Amazon S3 to remove them for you. If you want to block users or accounts from removing or deleting objects from your bucket, you must deny them the <code>s3:DeleteObject</code>, <code>s3:DeleteObjectVersion</code>, and <code>s3:PutLifeCycleConfiguration</code> actions. </p> <p>The following operation is related to <code>DeleteObject</code>:</p> <ul> <li> <p> <a>PutObject</a> </p> </li> </ul>"
266 },
267 "DeleteObjectTagging": {
268 "name": "DeleteObjectTagging",
269 "http": {
270 "method": "DELETE",
271 "requestUri": "/{Bucket}/{Key+}?tagging",
272 "responseCode": 204
273 },
274 "input": {
275 "shape": "DeleteObjectTaggingRequest"
276 },
277 "output": {
278 "shape": "DeleteObjectTaggingOutput"
279 },
280 "documentation": "<p>Removes the entire tag set from the specified object. For more information about managing object tags, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html\"> Object Tagging</a>.</p> <p>To use this operation, you must have permission to perform the <code>s3:DeleteObjectTagging</code> action.</p> <p>To delete tags of a specific object version, add the <code>versionId</code> query parameter in the request. You will need permission for the <code>s3:DeleteObjectVersionTagging</code> action.</p> <p>The following operations are related to <code>DeleteBucketMetricsConfiguration</code>:</p> <ul> <li> <p> <a>PutObjectTagging</a> </p> </li> <li> <p> <a>GetObjectTagging</a> </p> </li> </ul>"
281 },
282 "DeleteObjects": {
283 "name": "DeleteObjects",
284 "http": {
285 "method": "POST",
286 "requestUri": "/{Bucket}?delete"
287 },
288 "input": {
289 "shape": "DeleteObjectsRequest"
290 },
291 "output": {
292 "shape": "DeleteObjectsOutput"
293 },
294 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/multiobjectdeleteapi.html",
295 "documentation": "<p>This operation enables you to delete multiple objects from a bucket using a single HTTP request. If you know the object keys that you want to delete, then this operation provides a suitable alternative to sending individual delete requests, reducing per-request overhead.</p> <p>The request contains a list of up to 1000 keys that you want to delete. In the XML, you provide the object key names, and optionally, version IDs if you want to delete a specific version of the object from a versioning-enabled bucket. For each key, Amazon S3 performs a delete operation and returns the result of that delete, success, or failure, in the response. Note that if the object specified in the request is not found, Amazon S3 returns the result as deleted.</p> <p> The operation supports two modes for the response: verbose and quiet. By default, the operation uses verbose mode in which the response includes the result of deletion of each key in your request. In quiet mode the response includes only keys where the delete operation encountered an error. For a successful deletion, the operation does not return any information about the delete in the response body.</p> <p>When performing this operation on an MFA Delete enabled bucket, that attempts to delete any versioned objects, you must include an MFA token. If you do not provide one, the entire request will fail, even if there are non-versioned objects you are trying to delete. If you provide an invalid token, whether there are versioned keys in the request or not, the entire Multi-Object Delete request will fail. For information about MFA Delete, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/Versioning.html#MultiFactorAuthenticationDelete\"> MFA Delete</a>.</p> <p>Finally, the Content-MD5 header is required for all Multi-Object Delete requests. Amazon S3 uses the header value to ensure that your request body has not been altered in transit.</p> <p>The following operations are related to <code>DeleteObjects</code>:</p> <ul> <li> <p> <a>CreateMultipartUpload</a> </p> </li> <li> <p> <a>UploadPart</a> </p> </li> <li> <p> <a>CompleteMultipartUpload</a> </p> </li> <li> <p> <a>ListParts</a> </p> </li> <li> <p> <a>AbortMultipartUpload</a> </p> </li> </ul>",
296 "alias": "DeleteMultipleObjects"
297 },
298 "DeletePublicAccessBlock": {
299 "name": "DeletePublicAccessBlock",
300 "http": {
301 "method": "DELETE",
302 "requestUri": "/{Bucket}?publicAccessBlock",
303 "responseCode": 204
304 },
305 "input": {
306 "shape": "DeletePublicAccessBlockRequest"
307 },
308 "documentation": "<p>Removes the <code>PublicAccessBlock</code> configuration for an Amazon S3 bucket. To use this operation, you must have the <code>s3:PutBucketPublicAccessBlock</code> permission. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p>The following operations are related to <code>DeleteBucketMetricsConfiguration</code>:</p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html\">Using Amazon S3 Block Public Access</a> </p> </li> <li> <p> <a>GetPublicAccessBlock</a> </p> </li> <li> <p> <a>PutPublicAccessBlock</a> </p> </li> <li> <p> <a>GetBucketPolicyStatus</a> </p> </li> </ul>"
309 },
310 "GetBucketAccelerateConfiguration": {
311 "name": "GetBucketAccelerateConfiguration",
312 "http": {
313 "method": "GET",
314 "requestUri": "/{Bucket}?accelerate"
315 },
316 "input": {
317 "shape": "GetBucketAccelerateConfigurationRequest"
318 },
319 "output": {
320 "shape": "GetBucketAccelerateConfigurationOutput"
321 },
322 "documentation": "<p>This implementation of the GET operation uses the <code>accelerate</code> subresource to return the Transfer Acceleration state of a bucket, which is either <code>Enabled</code> or <code>Suspended</code>. Amazon S3 Transfer Acceleration is a bucket-level feature that enables you to perform faster data transfers to and from Amazon S3.</p> <p>To use this operation, you must have permission to perform the <code>s3:GetAccelerateConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//s3-access-control.html\">Managing Access Permissions to your Amazon S3 Resources</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p>You set the Transfer Acceleration state of an existing bucket to <code>Enabled</code> or <code>Suspended</code> by using the <a>PutBucketAccelerateConfiguration</a> operation. </p> <p>A GET <code>accelerate</code> request does not return a state value for a bucket that has no transfer acceleration state. A bucket has no Transfer Acceleration state if a state has never been set on the bucket. </p> <p>For more information about transfer acceleration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//transfer-acceleration.html\">Transfer Acceleration</a> in the Amazon Simple Storage Service Developer Guide.</p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>PutBucketAccelerateConfiguration</a> </p> </li> </ul>"
323 },
324 "GetBucketAcl": {
325 "name": "GetBucketAcl",
326 "http": {
327 "method": "GET",
328 "requestUri": "/{Bucket}?acl"
329 },
330 "input": {
331 "shape": "GetBucketAclRequest"
332 },
333 "output": {
334 "shape": "GetBucketAclOutput"
335 },
336 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGETacl.html",
337 "documentation": "<p>This implementation of the <code>GET</code> operation uses the <code>acl</code> subresource to return the access control list (ACL) of a bucket. To use <code>GET</code> to return the ACL of the bucket, you must have <code>READ_ACP</code> access to the bucket. If <code>READ_ACP</code> permission is granted to the anonymous user, you can return the ACL of the bucket without using an authorization header.</p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> </p> </li> </ul>"
338 },
339 "GetBucketAnalyticsConfiguration": {
340 "name": "GetBucketAnalyticsConfiguration",
341 "http": {
342 "method": "GET",
343 "requestUri": "/{Bucket}?analytics"
344 },
345 "input": {
346 "shape": "GetBucketAnalyticsConfigurationRequest"
347 },
348 "output": {
349 "shape": "GetBucketAnalyticsConfigurationOutput"
350 },
351 "documentation": "<p>This implementation of the GET operation returns an analytics configuration (identified by the analytics configuration ID) from the bucket.</p> <p>To use this operation, you must have permissions to perform the <code>s3:GetAnalyticsConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\"> Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a> in the <i>Amazon Simple Storage Service Developer Guide</i>. </p> <p>For information about Amazon S3 analytics feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html\">Amazon S3 Analytics – Storage Class Analysis</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> </p> </li> <li> <p> </p> </li> <li> <p> </p> </li> </ul>"
352 },
353 "GetBucketCors": {
354 "name": "GetBucketCors",
355 "http": {
356 "method": "GET",
357 "requestUri": "/{Bucket}?cors"
358 },
359 "input": {
360 "shape": "GetBucketCorsRequest"
361 },
362 "output": {
363 "shape": "GetBucketCorsOutput"
364 },
365 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGETcors.html",
366 "documentation": "<p>Returns the cors configuration information set for the bucket.</p> <p> To use this operation, you must have permission to perform the s3:GetBucketCORS action. By default, the bucket owner has this permission and can grant it to others.</p> <p> For more information about cors, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html\"> Enabling Cross-Origin Resource Sharing</a>.</p> <p>The following operations are related to <code>GetBucketCors</code>:</p> <ul> <li> <p> <a>PutBucketCors</a> </p> </li> <li> <p> <a>DeleteBucketCors</a> </p> </li> </ul>"
367 },
368 "GetBucketEncryption": {
369 "name": "GetBucketEncryption",
370 "http": {
371 "method": "GET",
372 "requestUri": "/{Bucket}?encryption"
373 },
374 "input": {
375 "shape": "GetBucketEncryptionRequest"
376 },
377 "output": {
378 "shape": "GetBucketEncryptionOutput"
379 },
380 "documentation": "<p>Returns the default encryption configuration for an Amazon S3 bucket. For information about the Amazon S3 default encryption feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html\">Amazon S3 Default Bucket Encryption</a>.</p> <p> To use this operation, you must have permission to perform the <code>s3:GetEncryptionConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p>The following operations are related to <code>GetBucketEncryption</code>:</p> <ul> <li> <p> <a>PutBucketEncryption</a> </p> </li> <li> <p> <a>DeleteBucketEncryption</a> </p> </li> </ul>"
381 },
382 "GetBucketInventoryConfiguration": {
383 "name": "GetBucketInventoryConfiguration",
384 "http": {
385 "method": "GET",
386 "requestUri": "/{Bucket}?inventory"
387 },
388 "input": {
389 "shape": "GetBucketInventoryConfigurationRequest"
390 },
391 "output": {
392 "shape": "GetBucketInventoryConfigurationOutput"
393 },
394 "documentation": "<p>Returns an inventory configuration (identified by the inventory configuration ID) from the bucket.</p> <p>To use this operation, you must have permissions to perform the <code>s3:GetInventoryConfiguration</code> action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p>For information about the Amazon S3 inventory feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html\">Amazon S3 Inventory</a>.</p> <p>The following operations are related to <code>GetBucketInventoryConfiguration</code>:</p> <ul> <li> <p> <a>DeleteBucketInventoryConfiguration</a> </p> </li> <li> <p> <a>ListBucketInventoryConfigurations</a> </p> </li> <li> <p> <a>PutBucketInventoryConfiguration</a> </p> </li> </ul>"
395 },
396 "GetBucketLifecycle": {
397 "name": "GetBucketLifecycle",
398 "http": {
399 "method": "GET",
400 "requestUri": "/{Bucket}?lifecycle"
401 },
402 "input": {
403 "shape": "GetBucketLifecycleRequest"
404 },
405 "output": {
406 "shape": "GetBucketLifecycleOutput"
407 },
408 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGETlifecycle.html",
409 "documentation": "<important> <p>For an updated version of this API, see <a>GetBucketLifecycleConfiguration</a>. If you configured a bucket lifecycle using the <code>filter</code> element, you should see the updated version of this topic. This topic is provided for backward compatibility.</p> </important> <p>Returns the lifecycle configuration information set on the bucket. For information about lifecycle configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html\">Object Lifecycle Management</a>.</p> <p> To use this operation, you must have permission to perform the <code>s3:GetLifecycleConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p> <code>GetBucketLifecycle</code> has the following special error:</p> <ul> <li> <p>Error code: <code>NoSuchLifecycleConfiguration</code> </p> <ul> <li> <p>Description: The lifecycle configuration does not exist.</p> </li> <li> <p>HTTP Status Code: 404 Not Found</p> </li> <li> <p>SOAP Fault Code Prefix: Client</p> </li> </ul> </li> </ul> <p>The following operations are related to <code>GetBucketLifecycle</code>:</p> <ul> <li> <p> <a>GetBucketLifecycleConfiguration</a> </p> </li> <li> <p> <a>PutBucketLifecycle</a> </p> </li> <li> <p> <a>DeleteBucketLifecycle</a> </p> </li> </ul>",
410 "deprecated": true
411 },
412 "GetBucketLifecycleConfiguration": {
413 "name": "GetBucketLifecycleConfiguration",
414 "http": {
415 "method": "GET",
416 "requestUri": "/{Bucket}?lifecycle"
417 },
418 "input": {
419 "shape": "GetBucketLifecycleConfigurationRequest"
420 },
421 "output": {
422 "shape": "GetBucketLifecycleConfigurationOutput"
423 },
424 "documentation": "<note> <p>Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name prefix, one or more object tags, or a combination of both. Accordingly, this section describes the latest API. The response describes the new filter element that you can use to specify a filter to select a subset of objects to which the rule applies. If you are still using previous version of the lifecycle configuration, it works. For the earlier API description, see <a>GetBucketLifecycle</a>.</p> </note> <p>Returns the lifecycle configuration information set on the bucket. For information about lifecycle configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html\">Object Lifecycle Management</a>.</p> <p>To use this operation, you must have permission to perform the <code>s3:GetLifecycleConfiguration</code> action. The bucket owner has this permission, by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p> <code>GetBucketLifecycleConfiguration</code> has the following special error:</p> <ul> <li> <p>Error code: <code>NoSuchLifecycleConfiguration</code> </p> <ul> <li> <p>Description: The lifecycle configuration does not exist.</p> </li> <li> <p>HTTP Status Code: 404 Not Found</p> </li> <li> <p>SOAP Fault Code Prefix: Client</p> </li> </ul> </li> </ul> <p>The following operations are related to <code>DeleteBucketMetricsConfiguration</code>:</p> <ul> <li> <p> <a>GetBucketLifecycle</a> </p> </li> <li> <p> <a>PutBucketLifecycle</a> </p> </li> <li> <p> <a>DeleteBucketLifecycle</a> </p> </li> </ul>"
425 },
426 "GetBucketLocation": {
427 "name": "GetBucketLocation",
428 "http": {
429 "method": "GET",
430 "requestUri": "/{Bucket}?location"
431 },
432 "input": {
433 "shape": "GetBucketLocationRequest"
434 },
435 "output": {
436 "shape": "GetBucketLocationOutput"
437 },
438 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGETlocation.html",
439 "documentation": "<p>Returns the Region the bucket resides in. You set the bucket's Region using the <code>LocationConstraint</code> request parameter in a <code>CreateBucket</code> request. For more information, see <a>CreateBucket</a>.</p> <p> To use this implementation of the operation, you must be the bucket owner.</p> <p>The following operations are related to <code>GetBucketLocation</code>:</p> <ul> <li> <p> <a>GetObject</a> </p> </li> <li> <p> <a>CreateBucket</a> </p> </li> </ul>"
440 },
441 "GetBucketLogging": {
442 "name": "GetBucketLogging",
443 "http": {
444 "method": "GET",
445 "requestUri": "/{Bucket}?logging"
446 },
447 "input": {
448 "shape": "GetBucketLoggingRequest"
449 },
450 "output": {
451 "shape": "GetBucketLoggingOutput"
452 },
453 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGETlogging.html",
454 "documentation": "<p>Returns the logging status of a bucket and the permissions users have to view and modify that status. To use GET, you must be the bucket owner.</p> <p>The following operations are related to <code>GetBucketLogging</code>:</p> <ul> <li> <p> <a>CreateBucket</a> </p> </li> <li> <p> <a>PutBucketLogging</a> </p> </li> </ul>"
455 },
456 "GetBucketMetricsConfiguration": {
457 "name": "GetBucketMetricsConfiguration",
458 "http": {
459 "method": "GET",
460 "requestUri": "/{Bucket}?metrics"
461 },
462 "input": {
463 "shape": "GetBucketMetricsConfigurationRequest"
464 },
465 "output": {
466 "shape": "GetBucketMetricsConfigurationOutput"
467 },
468 "documentation": "<p>Gets a metrics configuration (specified by the metrics configuration ID) from the bucket. Note that this doesn't include the daily storage metrics.</p> <p> To use this operation, you must have permissions to perform the <code>s3:GetMetricsConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p> For information about CloudWatch request metrics for Amazon S3, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html\">Monitoring Metrics with Amazon CloudWatch</a>.</p> <p>The following operations are related to <code>GetBucketMetricsConfiguration</code>:</p> <ul> <li> <p> <a>PutBucketMetricsConfiguration</a> </p> </li> <li> <p> <a>DeleteBucketMetricsConfiguration</a> </p> </li> <li> <p> <a>ListBucketMetricsConfigurations</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html\">Monitoring Metrics with Amazon CloudWatch</a> </p> </li> </ul>"
469 },
470 "GetBucketNotification": {
471 "name": "GetBucketNotification",
472 "http": {
473 "method": "GET",
474 "requestUri": "/{Bucket}?notification"
475 },
476 "input": {
477 "shape": "GetBucketNotificationConfigurationRequest"
478 },
479 "output": {
480 "shape": "NotificationConfigurationDeprecated"
481 },
482 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGETnotification.html",
483 "documentation": "<p> No longer used, see <a>GetBucketNotificationConfiguration</a>.</p>",
484 "deprecated": true
485 },
486 "GetBucketNotificationConfiguration": {
487 "name": "GetBucketNotificationConfiguration",
488 "http": {
489 "method": "GET",
490 "requestUri": "/{Bucket}?notification"
491 },
492 "input": {
493 "shape": "GetBucketNotificationConfigurationRequest"
494 },
495 "output": {
496 "shape": "NotificationConfiguration"
497 },
498 "documentation": "<p>Returns the notification configuration of a bucket.</p> <p>If notifications are not enabled on the bucket, the operation returns an empty <code>NotificationConfiguration</code> element.</p> <p>By default, you must be the bucket owner to read the notification configuration of a bucket. However, the bucket owner can use a bucket policy to grant permission to other users to read this configuration with the <code>s3:GetBucketNotification</code> permission.</p> <p>For more information about setting and reading the notification configuration on a bucket, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html\">Setting Up Notification of Bucket Events</a>. For more information about bucket policies, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html\">Using Bucket Policies</a>.</p> <p>The following operation is related to <code>GetBucketNotification</code>:</p> <ul> <li> <p> <a>PutBucketNotification</a> </p> </li> </ul>"
499 },
500 "GetBucketPolicy": {
501 "name": "GetBucketPolicy",
502 "http": {
503 "method": "GET",
504 "requestUri": "/{Bucket}?policy"
505 },
506 "input": {
507 "shape": "GetBucketPolicyRequest"
508 },
509 "output": {
510 "shape": "GetBucketPolicyOutput"
511 },
512 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGETpolicy.html",
513 "documentation": "<p>Returns the policy of a specified bucket. If you are using an identity other than the root user of the AWS account that owns the bucket, the calling identity must have the <code>GetBucketPolicy</code> permissions on the specified bucket and belong to the bucket owner's account in order to use this operation.</p> <p>If you don't have <code>GetBucketPolicy</code> permissions, Amazon S3 returns a <code>403 Access Denied</code> error. If you have the correct permissions, but you're not using an identity that belongs to the bucket owner's account, Amazon S3 returns a <code>405 Method Not Allowed</code> error.</p> <important> <p>As a security precaution, the root user of the AWS account that owns a bucket can always use this operation, even if the policy explicitly denies the root user the ability to perform this action.</p> </important> <p>For more information about bucket policies, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html\">Using Bucket Policies and User Policies</a>.</p> <p>The following operation is related to <code>GetBucketPolicy</code>:</p> <ul> <li> <p> <a>GetObject</a> </p> </li> </ul>"
514 },
515 "GetBucketPolicyStatus": {
516 "name": "GetBucketPolicyStatus",
517 "http": {
518 "method": "GET",
519 "requestUri": "/{Bucket}?policyStatus"
520 },
521 "input": {
522 "shape": "GetBucketPolicyStatusRequest"
523 },
524 "output": {
525 "shape": "GetBucketPolicyStatusOutput"
526 },
527 "documentation": "<p>Retrieves the policy status for an Amazon S3 bucket, indicating whether the bucket is public. In order to use this operation, you must have the <code>s3:GetBucketPolicyStatus</code> permission. For more information about Amazon S3 permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a Policy</a>.</p> <p> For more information about when Amazon S3 considers a bucket public, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status\">The Meaning of \"Public\"</a>. </p> <p>The following operations are related to <code>GetBucketPolicyStatus</code>:</p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html\">Using Amazon S3 Block Public Access</a> </p> </li> <li> <p> <a>GetPublicAccessBlock</a> </p> </li> <li> <p> <a>PutPublicAccessBlock</a> </p> </li> <li> <p> <a>DeletePublicAccessBlock</a> </p> </li> </ul>"
528 },
529 "GetBucketReplication": {
530 "name": "GetBucketReplication",
531 "http": {
532 "method": "GET",
533 "requestUri": "/{Bucket}?replication"
534 },
535 "input": {
536 "shape": "GetBucketReplicationRequest"
537 },
538 "output": {
539 "shape": "GetBucketReplicationOutput"
540 },
541 "documentation": "<p>Returns the replication configuration of a bucket.</p> <note> <p> It can take a while to propagate the put or delete a replication configuration to all Amazon S3 systems. Therefore, a get request soon after put or delete can return a wrong result. </p> </note> <p> For information about replication configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html\">Replication</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p>This operation requires permissions for the <code>s3:GetReplicationConfiguration</code> action. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html\">Using Bucket Policies and User Policies</a>.</p> <p>If you include the <code>Filter</code> element in a replication configuration, you must also include the <code>DeleteMarkerReplication</code> and <code>Priority</code> elements. The response also returns those elements.</p> <p>For information about <code>GetBucketReplication</code> errors, see <a>ReplicationErrorCodeList</a> </p> <p>The following operations are related to <code>GetBucketReplication</code>:</p> <ul> <li> <p> <a>PutBucketReplication</a> </p> </li> <li> <p> <a>DeleteBucketReplication</a> </p> </li> </ul>"
542 },
543 "GetBucketRequestPayment": {
544 "name": "GetBucketRequestPayment",
545 "http": {
546 "method": "GET",
547 "requestUri": "/{Bucket}?requestPayment"
548 },
549 "input": {
550 "shape": "GetBucketRequestPaymentRequest"
551 },
552 "output": {
553 "shape": "GetBucketRequestPaymentOutput"
554 },
555 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTrequestPaymentGET.html",
556 "documentation": "<p>Returns the request payment configuration of a bucket. To use this version of the operation, you must be the bucket owner. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RequesterPaysBuckets.html\">Requester Pays Buckets</a>.</p> <p>The following operations are related to <code>GetBucketRequestPayment</code>:</p> <ul> <li> <p> <a>ListObjects</a> </p> </li> </ul>"
557 },
558 "GetBucketTagging": {
559 "name": "GetBucketTagging",
560 "http": {
561 "method": "GET",
562 "requestUri": "/{Bucket}?tagging"
563 },
564 "input": {
565 "shape": "GetBucketTaggingRequest"
566 },
567 "output": {
568 "shape": "GetBucketTaggingOutput"
569 },
570 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGETtagging.html",
571 "documentation": "<p>Returns the tag set associated with the bucket.</p> <p>To use this operation, you must have permission to perform the <code>s3:GetBucketTagging</code> action. By default, the bucket owner has this permission and can grant this permission to others.</p> <p> <code>GetBucketTagging</code> has the following special error:</p> <ul> <li> <p>Error code: <code>NoSuchTagSetError</code> </p> <ul> <li> <p>Description: There is no tag set associated with the bucket.</p> </li> </ul> </li> </ul> <p>The following operations are related to <code>GetBucketTagging</code>:</p> <ul> <li> <p> <a>PutBucketTagging</a> </p> </li> <li> <p> <a>DeleteBucketTagging</a> </p> </li> </ul>"
572 },
573 "GetBucketVersioning": {
574 "name": "GetBucketVersioning",
575 "http": {
576 "method": "GET",
577 "requestUri": "/{Bucket}?versioning"
578 },
579 "input": {
580 "shape": "GetBucketVersioningRequest"
581 },
582 "output": {
583 "shape": "GetBucketVersioningOutput"
584 },
585 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGETversioningStatus.html",
586 "documentation": "<p>Returns the versioning state of a bucket.</p> <p>To retrieve the versioning state of a bucket, you must be the bucket owner.</p> <p>This implementation also returns the MFA Delete status of the versioning state. If the MFA Delete status is <code>enabled</code>, the bucket owner must use an authentication device to change the versioning state of the bucket.</p> <p>The following operations are related to <code>GetBucketVersioning</code>:</p> <ul> <li> <p> <a>GetObject</a> </p> </li> <li> <p> <a>PutObject</a> </p> </li> <li> <p> <a>DeleteObject</a> </p> </li> </ul>"
587 },
588 "GetBucketWebsite": {
589 "name": "GetBucketWebsite",
590 "http": {
591 "method": "GET",
592 "requestUri": "/{Bucket}?website"
593 },
594 "input": {
595 "shape": "GetBucketWebsiteRequest"
596 },
597 "output": {
598 "shape": "GetBucketWebsiteOutput"
599 },
600 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGETwebsite.html",
601 "documentation": "<p>Returns the website configuration for a bucket. To host website on Amazon S3, you can configure a bucket as website by adding a website configuration. For more information about hosting websites, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html\">Hosting Websites on Amazon S3</a>. </p> <p>This GET operation requires the <code>S3:GetBucketWebsite</code> permission. By default, only the bucket owner can read the bucket website configuration. However, bucket owners can allow other users to read the website configuration by writing a bucket policy granting them the <code>S3:GetBucketWebsite</code> permission.</p> <p>The following operations are related to <code>DeleteBucketWebsite</code>:</p> <ul> <li> <p> <a>DeleteBucketWebsite</a> </p> </li> <li> <p> <a>PutBucketWebsite</a> </p> </li> </ul>"
602 },
603 "GetObject": {
604 "name": "GetObject",
605 "http": {
606 "method": "GET",
607 "requestUri": "/{Bucket}/{Key+}"
608 },
609 "input": {
610 "shape": "GetObjectRequest"
611 },
612 "output": {
613 "shape": "GetObjectOutput"
614 },
615 "errors": [
616 {
617 "shape": "NoSuchKey"
618 }
619 ],
620 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTObjectGET.html",
621 "documentation": "<p>Retrieves objects from Amazon S3. To use <code>GET</code>, you must have <code>READ</code> access to the object. If you grant <code>READ</code> access to the anonymous user, you can return the object without using an authorization header.</p> <p>An Amazon S3 bucket has no directory hierarchy such as you would find in a typical computer file system. You can, however, create a logical hierarchy by using object key names that imply a folder structure. For example, instead of naming an object <code>sample.jpg</code>, you can name it <code>photos/2006/February/sample.jpg</code>.</p> <p>To get an object from such a logical hierarchy, specify the full key name for the object in the <code>GET</code> operation. For a virtual hosted-style request example, if you have the object <code>photos/2006/February/sample.jpg</code>, specify the resource as <code>/photos/2006/February/sample.jpg</code>. For a path-style request example, if you have the object <code>photos/2006/February/sample.jpg</code> in the bucket named <code>examplebucket</code>, specify the resource as <code>/examplebucket/photos/2006/February/sample.jpg</code>. For more information about request types, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html#VirtualHostingSpecifyBucket\">HTTP Host Header Bucket Specification</a>.</p> <p>To distribute large files to many people, you can save bandwidth costs by using BitTorrent. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3Torrent.html\">Amazon S3 Torrent</a>. For more information about returning the ACL of an object, see <a>GetObjectAcl</a>.</p> <p>If the object you are retrieving is stored in the GLACIER or DEEP_ARCHIVE storage classes, before you can retrieve the object you must first restore a copy using . Otherwise, this operation returns an <code>InvalidObjectStateError</code> error. For information about restoring archived objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html\">Restoring Archived Objects</a>.</p> <p>Encryption request headers, like <code>x-amz-server-side-encryption</code>, should not be sent for GET requests if your object uses server-side encryption with CMKs stored in AWS KMS (SSE-KMS) or server-side encryption with Amazon S3–managed encryption keys (SSE-S3). If your object does use these types of keys, you’ll get an HTTP 400 BadRequest error.</p> <p>If you encrypt an object by using server-side encryption with customer-provided encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object, you must use the following headers:</p> <ul> <li> <p>x-amz-server-side​-encryption​-customer-algorithm</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key-MD5</p> </li> </ul> <p>For more information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side Encryption (Using Customer-Provided Encryption Keys)</a>.</p> <p>Assuming you have permission to read object tags (permission for the <code>s3:GetObjectVersionTagging</code> action), the response also returns the <code>x-amz-tagging-count</code> header that provides the count of number of tags associated with the object. You can use <a>GetObjectTagging</a> to retrieve the tag set associated with an object.</p> <p> <b>Permissions</b> </p> <p>You need the <code>s3:GetObject</code> permission for this operation. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a Policy</a>. If the object you request does not exist, the error Amazon S3 returns depends on whether you also have the <code>s3:ListBucket</code> permission.</p> <ul> <li> <p>If you have the <code>s3:ListBucket</code> permission on the bucket, Amazon S3 will return an HTTP status code 404 (\"no such key\") error.</p> </li> <li> <p>If you don’t have the <code>s3:ListBucket</code> permission, Amazon S3 will return an HTTP status code 403 (\"access denied\") error.</p> </li> </ul> <p> <b>Versioning</b> </p> <p>By default, the GET operation returns the current version of an object. To return a different version, use the <code>versionId</code> subresource.</p> <note> <p>If the current version of the object is a delete marker, Amazon S3 behaves as if the object was deleted and includes <code>x-amz-delete-marker: true</code> in the response.</p> </note> <p>For more information about versioning, see <a>PutBucketVersioning</a>. </p> <p> <b>Overriding Response Header Values</b> </p> <p>There are times when you want to override certain response header values in a GET response. For example, you might override the Content-Disposition response header value in your GET request.</p> <p>You can override values for a set of response headers using the following query parameters. These response header values are sent only on a successful request, that is, when status code 200 OK is returned. The set of headers you can override using these parameters is a subset of the headers that Amazon S3 accepts when you create an object. The response headers that you can override for the GET response are <code>Content-Type</code>, <code>Content-Language</code>, <code>Expires</code>, <code>Cache-Control</code>, <code>Content-Disposition</code>, and <code>Content-Encoding</code>. To override these header values in the GET response, you use the following request parameters.</p> <note> <p>You must sign the request, either using an Authorization header or a presigned URL, when using these parameters. They cannot be used with an unsigned (anonymous) request.</p> </note> <ul> <li> <p> <code>response-content-type</code> </p> </li> <li> <p> <code>response-content-language</code> </p> </li> <li> <p> <code>response-expires</code> </p> </li> <li> <p> <code>response-cache-control</code> </p> </li> <li> <p> <code>response-content-disposition</code> </p> </li> <li> <p> <code>response-content-encoding</code> </p> </li> </ul> <p> <b>Additional Considerations about Request Headers</b> </p> <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers are present in the request as follows: <code>If-Match</code> condition evaluates to <code>true</code>, and; <code>If-Unmodified-Since</code> condition evaluates to <code>false</code>; then, S3 returns 200 OK and the data requested. </p> <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code> headers are present in the request as follows:<code> If-None-Match</code> condition evaluates to <code>false</code>, and; <code>If-Modified-Since</code> condition evaluates to <code>true</code>; then, S3 returns 304 Not Modified response code.</p> <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p> <p>The following operations are related to <code>GetObject</code>:</p> <ul> <li> <p> <a>ListBuckets</a> </p> </li> <li> <p> <a>GetObjectAcl</a> </p> </li> </ul>"
622 },
623 "GetObjectAcl": {
624 "name": "GetObjectAcl",
625 "http": {
626 "method": "GET",
627 "requestUri": "/{Bucket}/{Key+}?acl"
628 },
629 "input": {
630 "shape": "GetObjectAclRequest"
631 },
632 "output": {
633 "shape": "GetObjectAclOutput"
634 },
635 "errors": [
636 {
637 "shape": "NoSuchKey"
638 }
639 ],
640 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTObjectGETacl.html",
641 "documentation": "<p>Returns the access control list (ACL) of an object. To use this operation, you must have READ_ACP access to the object.</p> <p> <b>Versioning</b> </p> <p>By default, GET returns ACL information about the current version of an object. To return ACL information about a different version, use the versionId subresource.</p> <p>The following operations are related to <code>GetObjectAcl</code>:</p> <ul> <li> <p> <a>GetObject</a> </p> </li> <li> <p> <a>DeleteObject</a> </p> </li> <li> <p> <a>PutObject</a> </p> </li> </ul>"
642 },
643 "GetObjectLegalHold": {
644 "name": "GetObjectLegalHold",
645 "http": {
646 "method": "GET",
647 "requestUri": "/{Bucket}/{Key+}?legal-hold"
648 },
649 "input": {
650 "shape": "GetObjectLegalHoldRequest"
651 },
652 "output": {
653 "shape": "GetObjectLegalHoldOutput"
654 },
655 "documentation": "<p>Gets an object's current Legal Hold status. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking Objects</a>.</p>"
656 },
657 "GetObjectLockConfiguration": {
658 "name": "GetObjectLockConfiguration",
659 "http": {
660 "method": "GET",
661 "requestUri": "/{Bucket}?object-lock"
662 },
663 "input": {
664 "shape": "GetObjectLockConfigurationRequest"
665 },
666 "output": {
667 "shape": "GetObjectLockConfigurationOutput"
668 },
669 "documentation": "<p>Gets the Object Lock configuration for a bucket. The rule specified in the Object Lock configuration will be applied by default to every new object placed in the specified bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking Objects</a>.</p>"
670 },
671 "GetObjectRetention": {
672 "name": "GetObjectRetention",
673 "http": {
674 "method": "GET",
675 "requestUri": "/{Bucket}/{Key+}?retention"
676 },
677 "input": {
678 "shape": "GetObjectRetentionRequest"
679 },
680 "output": {
681 "shape": "GetObjectRetentionOutput"
682 },
683 "documentation": "<p>Retrieves an object's retention settings. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking Objects</a>.</p>"
684 },
685 "GetObjectTagging": {
686 "name": "GetObjectTagging",
687 "http": {
688 "method": "GET",
689 "requestUri": "/{Bucket}/{Key+}?tagging"
690 },
691 "input": {
692 "shape": "GetObjectTaggingRequest"
693 },
694 "output": {
695 "shape": "GetObjectTaggingOutput"
696 },
697 "documentation": "<p>Returns the tag-set of an object. You send the GET request against the tagging subresource associated with the object.</p> <p>To use this operation, you must have permission to perform the <code>s3:GetObjectTagging</code> action. By default, the GET operation returns information about current version of an object. For a versioned bucket, you can have multiple versions of an object in your bucket. To retrieve tags of any other version, use the versionId query parameter. You also need permission for the <code>s3:GetObjectVersionTagging</code> action.</p> <p> By default, the bucket owner has this permission and can grant this permission to others.</p> <p> For information about the Amazon S3 object tagging feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html\">Object Tagging</a>.</p> <p>The following operation is related to <code>GetObjectTagging</code>:</p> <ul> <li> <p> <a>PutObjectTagging</a> </p> </li> </ul>"
698 },
699 "GetObjectTorrent": {
700 "name": "GetObjectTorrent",
701 "http": {
702 "method": "GET",
703 "requestUri": "/{Bucket}/{Key+}?torrent"
704 },
705 "input": {
706 "shape": "GetObjectTorrentRequest"
707 },
708 "output": {
709 "shape": "GetObjectTorrentOutput"
710 },
711 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTObjectGETtorrent.html",
712 "documentation": "<p>Return torrent files from a bucket. BitTorrent can save you bandwidth when you're distributing large files. For more information about BitTorrent, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3Torrent.html\">Amazon S3 Torrent</a>.</p> <note> <p>You can get torrent only for objects that are less than 5 GB in size and that are not encrypted using server-side encryption with customer-provided encryption key.</p> </note> <p>To use GET, you must have READ access to the object.</p> <p>The following operation is related to <code>GetObjectTorrent</code>:</p> <ul> <li> <p> <a>GetObject</a> </p> </li> </ul>"
713 },
714 "GetPublicAccessBlock": {
715 "name": "GetPublicAccessBlock",
716 "http": {
717 "method": "GET",
718 "requestUri": "/{Bucket}?publicAccessBlock"
719 },
720 "input": {
721 "shape": "GetPublicAccessBlockRequest"
722 },
723 "output": {
724 "shape": "GetPublicAccessBlockOutput"
725 },
726 "documentation": "<p>Retrieves the <code>PublicAccessBlock</code> configuration for an Amazon S3 bucket. To use this operation, you must have the <code>s3:GetBucketPublicAccessBlock</code> permission. For more information about Amazon S3 permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a Policy</a>.</p> <important> <p>When Amazon S3 evaluates the <code>PublicAccessBlock</code> configuration for a bucket or an object, it checks the <code>PublicAccessBlock</code> configuration for both the bucket (or the bucket that contains the object) and the bucket owner's account. If the <code>PublicAccessBlock</code> settings are different between the bucket and the account, Amazon S3 uses the most restrictive combination of the bucket-level and account-level settings.</p> </important> <p>For more information about when Amazon S3 considers a bucket or an object public, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status\">The Meaning of \"Public\"</a>.</p> <p>The following operations are related to <code>GetPublicAccessBlock</code>:</p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html\">Using Amazon S3 Block Public Access</a> </p> </li> <li> <p> <a>PutPublicAccessBlock</a> </p> </li> <li> <p> <a>GetPublicAccessBlock</a> </p> </li> <li> <p> <a>DeletePublicAccessBlock</a> </p> </li> </ul>"
727 },
728 "HeadBucket": {
729 "name": "HeadBucket",
730 "http": {
731 "method": "HEAD",
732 "requestUri": "/{Bucket}"
733 },
734 "input": {
735 "shape": "HeadBucketRequest"
736 },
737 "errors": [
738 {
739 "shape": "NoSuchBucket"
740 }
741 ],
742 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketHEAD.html",
743 "documentation": "<p>This operation is useful to determine if a bucket exists and you have permission to access it. The operation returns a <code>200 OK</code> if the bucket exists and you have permission to access it. Otherwise, the operation might return responses such as <code>404 Not Found</code> and <code>403 Forbidden</code>. </p> <p>To use this operation, you must have permissions to perform the <code>s3:ListBucket</code> action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p>"
744 },
745 "HeadObject": {
746 "name": "HeadObject",
747 "http": {
748 "method": "HEAD",
749 "requestUri": "/{Bucket}/{Key+}"
750 },
751 "input": {
752 "shape": "HeadObjectRequest"
753 },
754 "output": {
755 "shape": "HeadObjectOutput"
756 },
757 "errors": [
758 {
759 "shape": "NoSuchKey"
760 }
761 ],
762 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTObjectHEAD.html",
763 "documentation": "<p>The HEAD operation retrieves metadata from an object without returning the object itself. This operation is useful if you're only interested in an object's metadata. To use HEAD, you must have READ access to the object.</p> <p>A <code>HEAD</code> request has the same options as a <code>GET</code> operation on an object. The response is identical to the <code>GET</code> response except that there is no response body.</p> <p>If you encrypt an object by using server-side encryption with customer-provided encryption keys (SSE-C) when you store the object in Amazon S3, then when you retrieve the metadata from the object, you must use the following headers:</p> <ul> <li> <p>x-amz-server-side​-encryption​-customer-algorithm</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key-MD5</p> </li> </ul> <p>For more information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side Encryption (Using Customer-Provided Encryption Keys)</a>.</p> <note> <p>Encryption request headers, like <code>x-amz-server-side-encryption</code>, should not be sent for GET requests if your object uses server-side encryption with CMKs stored in AWS KMS (SSE-KMS) or server-side encryption with Amazon S3–managed encryption keys (SSE-S3). If your object does use these types of keys, you’ll get an HTTP 400 BadRequest error.</p> </note> <p>Request headers are limited to 8 KB in size. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/RESTCommonRequestHeaders.html\">Common Request Headers</a>.</p> <p>Consider the following when using request headers:</p> <ul> <li> <p> Consideration 1 – If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers are present in the request as follows:</p> <ul> <li> <p> <code>If-Match</code> condition evaluates to <code>true</code>, and;</p> </li> <li> <p> <code>If-Unmodified-Since</code> condition evaluates to <code>false</code>;</p> </li> </ul> <p>Then Amazon S3 returns <code>200 OK</code> and the data requested.</p> </li> <li> <p> Consideration 2 – If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code> headers are present in the request as follows:</p> <ul> <li> <p> <code>If-None-Match</code> condition evaluates to <code>false</code>, and;</p> </li> <li> <p> <code>If-Modified-Since</code> condition evaluates to <code>true</code>;</p> </li> </ul> <p>Then Amazon S3 returns the <code>304 Not Modified</code> response code.</p> </li> </ul> <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p> <p> <b>Permissions</b> </p> <p>You need the <code>s3:GetObject</code> permission for this operation. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a Policy</a>. If the object you request does not exist, the error Amazon S3 returns depends on whether you also have the s3:ListBucket permission.</p> <ul> <li> <p>If you have the <code>s3:ListBucket</code> permission on the bucket, Amazon S3 returns an HTTP status code 404 (\"no such key\") error.</p> </li> <li> <p>If you don’t have the <code>s3:ListBucket</code> permission, Amazon S3 returns an HTTP status code 403 (\"access denied\") error.</p> </li> </ul> <p>The following operation is related to <code>HeadObject</code>:</p> <ul> <li> <p> <a>GetObject</a> </p> </li> </ul>"
764 },
765 "ListBucketAnalyticsConfigurations": {
766 "name": "ListBucketAnalyticsConfigurations",
767 "http": {
768 "method": "GET",
769 "requestUri": "/{Bucket}?analytics"
770 },
771 "input": {
772 "shape": "ListBucketAnalyticsConfigurationsRequest"
773 },
774 "output": {
775 "shape": "ListBucketAnalyticsConfigurationsOutput"
776 },
777 "documentation": "<p>Lists the analytics configurations for the bucket. You can have up to 1,000 analytics configurations per bucket.</p> <p>This operation supports list pagination and does not return more than 100 configurations at a time. You should always check the <code>IsTruncated</code> element in the response. If there are no more configurations to list, <code>IsTruncated</code> is set to false. If there are more configurations to list, <code>IsTruncated</code> is set to true, and there will be a value in <code>NextContinuationToken</code>. You use the <code>NextContinuationToken</code> value to continue the pagination of the list by passing the value in continuation-token in the request to <code>GET</code> the next page.</p> <p>To use this operation, you must have permissions to perform the <code>s3:GetAnalyticsConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p>For information about Amazon S3 analytics feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html\">Amazon S3 Analytics – Storage Class Analysis</a>. </p> <p>The following operations are related to <code>ListBucketAnalyticsConfigurations</code>:</p> <ul> <li> <p> <a>GetBucketAnalyticsConfiguration</a> </p> </li> <li> <p> <a>DeleteBucketAnalyticsConfiguration</a> </p> </li> <li> <p> <a>PutBucketAnalyticsConfiguration</a> </p> </li> </ul>"
778 },
779 "ListBucketInventoryConfigurations": {
780 "name": "ListBucketInventoryConfigurations",
781 "http": {
782 "method": "GET",
783 "requestUri": "/{Bucket}?inventory"
784 },
785 "input": {
786 "shape": "ListBucketInventoryConfigurationsRequest"
787 },
788 "output": {
789 "shape": "ListBucketInventoryConfigurationsOutput"
790 },
791 "documentation": "<p>Returns a list of inventory configurations for the bucket. You can have up to 1,000 analytics configurations per bucket.</p> <p>This operation supports list pagination and does not return more than 100 configurations at a time. Always check the <code>IsTruncated</code> element in the response. If there are no more configurations to list, <code>IsTruncated</code> is set to false. If there are more configurations to list, <code>IsTruncated</code> is set to true, and there is a value in <code>NextContinuationToken</code>. You use the <code>NextContinuationToken</code> value to continue the pagination of the list by passing the value in continuation-token in the request to <code>GET</code> the next page.</p> <p> To use this operation, you must have permissions to perform the <code>s3:GetInventoryConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p>For information about the Amazon S3 inventory feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html\">Amazon S3 Inventory</a> </p> <p>The following operations are related to <code>ListBucketInventoryConfigurations</code>:</p> <ul> <li> <p> <a>GetBucketInventoryConfiguration</a> </p> </li> <li> <p> <a>DeleteBucketInventoryConfiguration</a> </p> </li> <li> <p> <a>PutBucketInventoryConfiguration</a> </p> </li> </ul>"
792 },
793 "ListBucketMetricsConfigurations": {
794 "name": "ListBucketMetricsConfigurations",
795 "http": {
796 "method": "GET",
797 "requestUri": "/{Bucket}?metrics"
798 },
799 "input": {
800 "shape": "ListBucketMetricsConfigurationsRequest"
801 },
802 "output": {
803 "shape": "ListBucketMetricsConfigurationsOutput"
804 },
805 "documentation": "<p>Lists the metrics configurations for the bucket. The metrics configurations are only for the request metrics of the bucket and do not provide information on daily storage metrics. You can have up to 1,000 configurations per bucket.</p> <p>This operation supports list pagination and does not return more than 100 configurations at a time. Always check the <code>IsTruncated</code> element in the response. If there are no more configurations to list, <code>IsTruncated</code> is set to false. If there are more configurations to list, <code>IsTruncated</code> is set to true, and there is a value in <code>NextContinuationToken</code>. You use the <code>NextContinuationToken</code> value to continue the pagination of the list by passing the value in <code>continuation-token</code> in the request to <code>GET</code> the next page.</p> <p>To use this operation, you must have permissions to perform the <code>s3:GetMetricsConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p>For more information about metrics configurations and CloudWatch request metrics, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html\">Monitoring Metrics with Amazon CloudWatch</a>.</p> <p>The following operations are related to <code>ListBucketMetricsConfigurations</code>:</p> <ul> <li> <p> <a>PutBucketMetricsConfiguration</a> </p> </li> <li> <p> <a>GetBucketMetricsConfiguration</a> </p> </li> <li> <p> <a>DeleteBucketMetricsConfiguration</a> </p> </li> </ul>"
806 },
807 "ListBuckets": {
808 "name": "ListBuckets",
809 "http": {
810 "method": "GET",
811 "requestUri": "/"
812 },
813 "output": {
814 "shape": "ListBucketsOutput"
815 },
816 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTServiceGET.html",
817 "documentation": "<p>Returns a list of all buckets owned by the authenticated sender of the request.</p>",
818 "alias": "GetService"
819 },
820 "ListMultipartUploads": {
821 "name": "ListMultipartUploads",
822 "http": {
823 "method": "GET",
824 "requestUri": "/{Bucket}?uploads"
825 },
826 "input": {
827 "shape": "ListMultipartUploadsRequest"
828 },
829 "output": {
830 "shape": "ListMultipartUploadsOutput"
831 },
832 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/mpUploadListMPUpload.html",
833 "documentation": "<p>This operation lists in-progress multipart uploads. An in-progress multipart upload is a multipart upload that has been initiated using the Initiate Multipart Upload request, but has not yet been completed or aborted.</p> <p>This operation returns at most 1,000 multipart uploads in the response. 1,000 multipart uploads is the maximum number of uploads a response can include, which is also the default value. You can further limit the number of uploads in a response by specifying the <code>max-uploads</code> parameter in the response. If additional multipart uploads satisfy the list criteria, the response will contain an <code>IsTruncated</code> element with the value true. To list the additional multipart uploads, use the <code>key-marker</code> and <code>upload-id-marker</code> request parameters.</p> <p>In the response, the uploads are sorted by key. If your application has initiated more than one multipart upload using the same object key, then uploads in the response are first sorted by key. Additionally, uploads are sorted in ascending order within each key by the upload initiation time.</p> <p>For more information on multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading Objects Using Multipart Upload</a>.</p> <p>For information on permissions required to use the multipart upload API, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload API and Permissions</a>.</p> <p>The following operations are related to <code>ListMultipartUploads</code>:</p> <ul> <li> <p> <a>CreateMultipartUpload</a> </p> </li> <li> <p> <a>UploadPart</a> </p> </li> <li> <p> <a>CompleteMultipartUpload</a> </p> </li> <li> <p> <a>ListParts</a> </p> </li> <li> <p> <a>AbortMultipartUpload</a> </p> </li> </ul>"
834 },
835 "ListObjectVersions": {
836 "name": "ListObjectVersions",
837 "http": {
838 "method": "GET",
839 "requestUri": "/{Bucket}?versions"
840 },
841 "input": {
842 "shape": "ListObjectVersionsRequest"
843 },
844 "output": {
845 "shape": "ListObjectVersionsOutput"
846 },
847 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGETVersion.html",
848 "documentation": "<p>Returns metadata about all of the versions of objects in a bucket. You can also use request parameters as selection criteria to return metadata about a subset of all the object versions. </p> <note> <p> A 200 OK response can contain valid or invalid XML. Make sure to design your application to parse the contents of the response and handle it appropriately.</p> </note> <p>To use this operation, you must have READ access to the bucket.</p> <p>The following operations are related to <code>ListObjectVersions</code>:</p> <ul> <li> <p> <a>ListObjectsV2</a> </p> </li> <li> <p> <a>GetObject</a> </p> </li> <li> <p> <a>PutObject</a> </p> </li> <li> <p> <a>DeleteObject</a> </p> </li> </ul>",
849 "alias": "GetBucketObjectVersions"
850 },
851 "ListObjects": {
852 "name": "ListObjects",
853 "http": {
854 "method": "GET",
855 "requestUri": "/{Bucket}"
856 },
857 "input": {
858 "shape": "ListObjectsRequest"
859 },
860 "output": {
861 "shape": "ListObjectsOutput"
862 },
863 "errors": [
864 {
865 "shape": "NoSuchBucket"
866 }
867 ],
868 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGET.html",
869 "documentation": "<p>Returns some or all (up to 1,000) of the objects in a bucket. You can use the request parameters as selection criteria to return a subset of the objects in a bucket. A 200 OK response can contain valid or invalid XML. Be sure to design your application to parse the contents of the response and handle it appropriately.</p> <important> <p>This API has been revised. We recommend that you use the newer version, <a>ListObjectsV2</a>, when developing applications. For backward compatibility, Amazon S3 continues to support <code>ListObjects</code>.</p> </important> <p>The following operations are related to <code>ListObjects</code>:</p> <ul> <li> <p> <a>ListObjectsV2</a> </p> </li> <li> <p> <a>GetObject</a> </p> </li> <li> <p> <a>PutObject</a> </p> </li> <li> <p> <a>CreateBucket</a> </p> </li> <li> <p> <a>ListBuckets</a> </p> </li> </ul>",
870 "alias": "GetBucket"
871 },
872 "ListObjectsV2": {
873 "name": "ListObjectsV2",
874 "http": {
875 "method": "GET",
876 "requestUri": "/{Bucket}?list-type=2"
877 },
878 "input": {
879 "shape": "ListObjectsV2Request"
880 },
881 "output": {
882 "shape": "ListObjectsV2Output"
883 },
884 "errors": [
885 {
886 "shape": "NoSuchBucket"
887 }
888 ],
889 "documentation": "<p>Returns some or all (up to 1,000) of the objects in a bucket. You can use the request parameters as selection criteria to return a subset of the objects in a bucket. A <code>200 OK</code> response can contain valid or invalid XML. Make sure to design your application to parse the contents of the response and handle it appropriately.</p> <p>To use this operation, you must have READ access to the bucket.</p> <p>To use this operation in an AWS Identity and Access Management (IAM) policy, you must have permissions to perform the <code>s3:ListBucket</code> action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <important> <p>This section describes the latest revision of the API. We recommend that you use this revised API for application development. For backward compatibility, Amazon S3 continues to support the prior version of this API, <a>ListObjects</a>.</p> </important> <p>To get a list of your buckets, see <a>ListBuckets</a>.</p> <p>The following operations are related to <code>ListObjectsV2</code>:</p> <ul> <li> <p> <a>GetObject</a> </p> </li> <li> <p> <a>PutObject</a> </p> </li> <li> <p> <a>CreateBucket</a> </p> </li> </ul>"
890 },
891 "ListParts": {
892 "name": "ListParts",
893 "http": {
894 "method": "GET",
895 "requestUri": "/{Bucket}/{Key+}"
896 },
897 "input": {
898 "shape": "ListPartsRequest"
899 },
900 "output": {
901 "shape": "ListPartsOutput"
902 },
903 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/mpUploadListParts.html",
904 "documentation": "<p>Lists the parts that have been uploaded for a specific multipart upload. This operation must include the upload ID, which you obtain by sending the initiate multipart upload request (see <a>CreateMultipartUpload</a>). This request returns a maximum of 1,000 uploaded parts. The default number of parts returned is 1,000 parts. You can restrict the number of parts returned by specifying the <code>max-parts</code> request parameter. If your multipart upload consists of more than 1,000 parts, the response returns an <code>IsTruncated</code> field with the value of true, and a <code>NextPartNumberMarker</code> element. In subsequent <code>ListParts</code> requests you can include the part-number-marker query string parameter and set its value to the <code>NextPartNumberMarker</code> field value from the previous response.</p> <p>For more information on multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading Objects Using Multipart Upload</a>.</p> <p>For information on permissions required to use the multipart upload API, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload API and Permissions</a>.</p> <p>The following operations are related to <code>ListParts</code>:</p> <ul> <li> <p> <a>CreateMultipartUpload</a> </p> </li> <li> <p> <a>UploadPart</a> </p> </li> <li> <p> <a>CompleteMultipartUpload</a> </p> </li> <li> <p> <a>AbortMultipartUpload</a> </p> </li> <li> <p> <a>ListMultipartUploads</a> </p> </li> </ul>"
905 },
906 "PutBucketAccelerateConfiguration": {
907 "name": "PutBucketAccelerateConfiguration",
908 "http": {
909 "method": "PUT",
910 "requestUri": "/{Bucket}?accelerate"
911 },
912 "input": {
913 "shape": "PutBucketAccelerateConfigurationRequest"
914 },
915 "documentation": "<p>Sets the accelerate configuration of an existing bucket. Amazon S3 Transfer Acceleration is a bucket-level feature that enables you to perform faster data transfers to Amazon S3.</p> <p> To use this operation, you must have permission to perform the s3:PutAccelerateConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p> The Transfer Acceleration state of a bucket can be set to one of the following two values:</p> <ul> <li> <p> Enabled – Enables accelerated data transfers to the bucket.</p> </li> <li> <p> Suspended – Disables accelerated data transfers to the bucket.</p> </li> </ul> <p>The <a>GetBucketAccelerateConfiguration</a> operation returns the transfer acceleration state of a bucket.</p> <p>After setting the Transfer Acceleration state of a bucket to Enabled, it might take up to thirty minutes before the data transfer rates to the bucket increase.</p> <p> The name of the bucket used for Transfer Acceleration must be DNS-compliant and must not contain periods (\".\").</p> <p> For more information about transfer acceleration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html\">Transfer Acceleration</a>.</p> <p>The following operations are related to <code>PutBucketAccelerateConfiguration</code>:</p> <ul> <li> <p> <a>GetBucketAccelerateConfiguration</a> </p> </li> <li> <p> <a>CreateBucket</a> </p> </li> </ul>"
916 },
917 "PutBucketAcl": {
918 "name": "PutBucketAcl",
919 "http": {
920 "method": "PUT",
921 "requestUri": "/{Bucket}?acl"
922 },
923 "input": {
924 "shape": "PutBucketAclRequest"
925 },
926 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketPUTacl.html",
927 "documentation": "<p>Sets the permissions on an existing bucket using access control lists (ACL). For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Using ACLs</a>. To set the ACL of a bucket, you must have <code>WRITE_ACP</code> permission.</p> <p>You can use one of the following two ways to set a bucket's permissions:</p> <ul> <li> <p>Specify the ACL in the request body</p> </li> <li> <p>Specify permissions using request headers</p> </li> </ul> <note> <p>You cannot specify access permission using both the body and the request headers.</p> </note> <p>Depending on your application needs, you may choose to set the ACL on a bucket using either the request body or the headers. For example, if you have an existing application that updates a bucket ACL using the request body, then you can continue to use that approach.</p> <p> <b>Access Permissions</b> </p> <p>You can set access permissions using one of the following methods:</p> <ul> <li> <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. Amazon S3 supports a set of predefined ACLs, known as <i>canned ACLs</i>. Each canned ACL has a predefined set of grantees and permissions. Specify the canned ACL name as the value of <code>x-amz-acl</code>. If you use this header, you cannot use other access control-specific headers in your request. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned ACL</a>.</p> </li> <li> <p>Specify access permissions explicitly with the <code>x-amz-grant-read</code>, <code>x-amz-grant-read-acp</code>, <code>x-amz-grant-write-acp</code>, and <code>x-amz-grant-full-control</code> headers. When using these headers, you specify explicit access permissions and grantees (AWS accounts or Amazon S3 groups) who will receive the permission. If you use these ACL-specific headers, you cannot use the <code>x-amz-acl</code> header to set a canned ACL. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>.</p> <p>You specify each grantee as a type=value pair, where the type is one of the following:</p> <ul> <li> <p> <code>emailAddress</code> – if the value specified is the email address of an AWS account</p> </li> <li> <p> <code>id</code> – if the value specified is the canonical user ID of an AWS account</p> </li> <li> <p> <code>uri</code> – if you are granting permissions to a predefined group</p> </li> </ul> <p>For example, the following <code>x-amz-grant-write</code> header grants create, overwrite, and delete objects permission to LogDelivery group predefined by Amazon S3 and two AWS accounts identified by their email addresses.</p> <p> <code>x-amz-grant-write: uri=\"http://acs.amazonaws.com/groups/s3/LogDelivery\", emailAddress=\"xyz@amazon.com\", emailAddress=\"abc@amazon.com\" </code> </p> </li> </ul> <p>You can use either a canned ACL or specify access permissions explicitly. You cannot do both.</p> <p> <b>Grantee Values</b> </p> <p>You can specify the person (grantee) to whom you're assigning access rights (using request elements) in the following ways:</p> <ul> <li> <p>By Email address:</p> <p> <code>&lt;Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:type=\"AmazonCustomerByEmail\"&gt;&lt;EmailAddress&gt;&lt;&gt;Grantees@email.com&lt;&gt;&lt;/EmailAddress&gt;lt;/Grantee&gt;</code> </p> <p>The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.</p> </li> <li> <p>By the person's ID:</p> <p> <code>&lt;Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:type=\"CanonicalUser\"&gt;&lt;ID&gt;&lt;&gt;ID&lt;&gt;&lt;/ID&gt;&lt;DisplayName&gt;&lt;&gt;GranteesEmail&lt;&gt;&lt;/DisplayName&gt; &lt;/Grantee&gt;</code> </p> <p>DisplayName is optional and ignored in the request</p> </li> <li> <p>By URI:</p> <p> <code>&lt;Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:type=\"Group\"&gt;&lt;URI&gt;&lt;&gt;http://acs.amazonaws.com/groups/global/AuthenticatedUsers&lt;&gt;&lt;/URI&gt;&lt;/Grantee&gt;</code> </p> </li> </ul> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>CreateBucket</a> </p> </li> <li> <p> <a>DeleteBucket</a> </p> </li> <li> <p> <a>GetObjectAcl</a> </p> </li> </ul>"
928 },
929 "PutBucketAnalyticsConfiguration": {
930 "name": "PutBucketAnalyticsConfiguration",
931 "http": {
932 "method": "PUT",
933 "requestUri": "/{Bucket}?analytics"
934 },
935 "input": {
936 "shape": "PutBucketAnalyticsConfigurationRequest"
937 },
938 "documentation": "<p>Sets an analytics configuration for the bucket (specified by the analytics configuration ID). You can have up to 1,000 analytics configurations per bucket.</p> <p>You can choose to have storage class analysis export analysis reports sent to a comma-separated values (CSV) flat file. See the <code>DataExport</code> request element. Reports are updated daily and are based on the object filters that you configure. When selecting data export, you specify a destination bucket and an optional destination prefix where the file is written. You can export the data to a destination bucket in a different account. However, the destination bucket must be in the same Region as the bucket that you are making the PUT analytics configuration to. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html\">Amazon S3 Analytics – Storage Class Analysis</a>. </p> <important> <p>You must create a bucket policy on the destination bucket where the exported file is written to grant permissions to Amazon S3 to write objects to the bucket. For an example policy, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/example-bucket-policies.html#example-bucket-policies-use-case-9\">Granting Permissions for Amazon S3 Inventory and Storage Class Analysis</a>.</p> </important> <p>To use this operation, you must have permissions to perform the <code>s3:PutAnalyticsConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p class=\"title\"> <b>Special Errors</b> </p> <ul> <li> <ul> <li> <p> <i>HTTP Error: HTTP 400 Bad Request</i> </p> </li> <li> <p> <i>Code: InvalidArgument</i> </p> </li> <li> <p> <i>Cause: Invalid argument.</i> </p> </li> </ul> </li> <li> <ul> <li> <p> <i>HTTP Error: HTTP 400 Bad Request</i> </p> </li> <li> <p> <i>Code: TooManyConfigurations</i> </p> </li> <li> <p> <i>Cause: You are attempting to create a new configuration but have already reached the 1,000-configuration limit.</i> </p> </li> </ul> </li> <li> <ul> <li> <p> <i>HTTP Error: HTTP 403 Forbidden</i> </p> </li> <li> <p> <i>Code: AccessDenied</i> </p> </li> <li> <p> <i>Cause: You are not the owner of the specified bucket, or you do not have the s3:PutAnalyticsConfiguration bucket permission to set the configuration on the bucket.</i> </p> </li> </ul> </li> </ul> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> </p> </li> <li> <p> </p> </li> <li> <p> </p> </li> </ul>"
939 },
940 "PutBucketCors": {
941 "name": "PutBucketCors",
942 "http": {
943 "method": "PUT",
944 "requestUri": "/{Bucket}?cors"
945 },
946 "input": {
947 "shape": "PutBucketCorsRequest"
948 },
949 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketPUTcors.html",
950 "documentation": "<p>Sets the <code>cors</code> configuration for your bucket. If the configuration exists, Amazon S3 replaces it.</p> <p>To use this operation, you must be allowed to perform the <code>s3:PutBucketCORS</code> action. By default, the bucket owner has this permission and can grant it to others.</p> <p>You set this configuration on a bucket so that the bucket can service cross-origin requests. For example, you might want to enable a request whose origin is <code>http://www.example.com</code> to access your Amazon S3 bucket at <code>my.example.bucket.com</code> by using the browser's <code>XMLHttpRequest</code> capability.</p> <p>To enable cross-origin resource sharing (CORS) on a bucket, you add the <code>cors</code> subresource to the bucket. The <code>cors</code> subresource is an XML document in which you configure rules that identify origins and the HTTP methods that can be executed on your bucket. The document is limited to 64 KB in size. </p> <p>When Amazon S3 receives a cross-origin request (or a pre-flight OPTIONS request) against a bucket, it evaluates the <code>cors</code> configuration on the bucket and uses the first <code>CORSRule</code> rule that matches the incoming browser request to enable a cross-origin request. For a rule to match, the following conditions must be met:</p> <ul> <li> <p>The request's <code>Origin</code> header must match <code>AllowedOrigin</code> elements.</p> </li> <li> <p>The request method (for example, GET, PUT, HEAD, and so on) or the <code>Access-Control-Request-Method</code> header in case of a pre-flight <code>OPTIONS</code> request must be one of the <code>AllowedMethod</code> elements. </p> </li> <li> <p>Every header specified in the <code>Access-Control-Request-Headers</code> request header of a pre-flight request must match an <code>AllowedHeader</code> element. </p> </li> </ul> <p> For more information about CORS, go to <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html\">Enabling Cross-Origin Resource Sharing</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>GetBucketCors</a> </p> </li> <li> <p> <a>DeleteBucketCors</a> </p> </li> <li> <p> <a>RESTOPTIONSobject</a> </p> </li> </ul>"
951 },
952 "PutBucketEncryption": {
953 "name": "PutBucketEncryption",
954 "http": {
955 "method": "PUT",
956 "requestUri": "/{Bucket}?encryption"
957 },
958 "input": {
959 "shape": "PutBucketEncryptionRequest"
960 },
961 "documentation": "<p>This implementation of the <code>PUT</code> operation uses the <code>encryption</code> subresource to set the default encryption state of an existing bucket.</p> <p>This implementation of the <code>PUT</code> operation sets default encryption for a bucket using server-side encryption with Amazon S3-managed keys SSE-S3 or AWS KMS customer master keys (CMKs) (SSE-KMS).</p> <important> <p>This operation requires AWS Signature Version 4. For more information, see <a href=\"sig-v4-authenticating-requests.html\"> Authenticating Requests (AWS Signature Version 4)</a>. </p> </important> <p>To use this operation, you must have permissions to perform the <code>s3:PutEncryptionConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a> in the Amazon Simple Storage Service Developer Guide. </p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>GetBucketEncryption</a> </p> </li> <li> <p> <a>DeleteBucketEncryption</a> </p> </li> </ul>"
962 },
963 "PutBucketInventoryConfiguration": {
964 "name": "PutBucketInventoryConfiguration",
965 "http": {
966 "method": "PUT",
967 "requestUri": "/{Bucket}?inventory"
968 },
969 "input": {
970 "shape": "PutBucketInventoryConfigurationRequest"
971 },
972 "documentation": "<p>This implementation of the <code>PUT</code> operation adds an inventory configuration (identified by the inventory ID) to the bucket. You can have up to 1,000 inventory configurations per bucket. </p> <p>Amazon S3 inventory generates inventories of the objects in the bucket on a daily or weekly basis, and the results are published to a flat file. The bucket that is inventoried is called the <i>source</i> bucket, and the bucket where the inventory flat file is stored is called the <i>destination</i> bucket. The <i>destination</i> bucket must be in the same AWS Region as the <i>source</i> bucket. </p> <p>When you configure an inventory for a <i>source</i> bucket, you specify the <i>destination</i> bucket where you want the inventory to be stored, and whether to generate the inventory daily or weekly. You can also configure what object metadata to include and whether to inventory all object versions or only current versions. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//storage-inventory.html\">Amazon S3 Inventory</a> in the Amazon Simple Storage Service Developer Guide.</p> <important> <p>You must create a bucket policy on the <i>destination</i> bucket to grant permissions to Amazon S3 to write objects to the bucket in the defined location. For an example policy, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/example-bucket-policies.html#example-bucket-policies-use-case-9\"> Granting Permissions for Amazon S3 Inventory and Storage Class Analysis.</a> </p> </important> <p>To use this operation, you must have permissions to perform the <code>s3:PutInventoryConfiguration</code> action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a> in the Amazon Simple Storage Service Developer Guide.</p> <p class=\"title\"> <b>Special Errors</b> </p> <ul> <li> <p class=\"title\"> <b>HTTP 400 Bad Request Error</b> </p> <ul> <li> <p> <i>Code:</i> InvalidArgument</p> </li> <li> <p> <i>Cause:</i> Invalid Argument</p> </li> </ul> </li> <li> <p class=\"title\"> <b>HTTP 400 Bad Request Error</b> </p> <ul> <li> <p> <i>Code:</i> TooManyConfigurations</p> </li> <li> <p> <i>Cause:</i> You are attempting to create a new configuration but have already reached the 1,000-configuration limit. </p> </li> </ul> </li> <li> <p class=\"title\"> <b>HTTP 403 Forbidden Error</b> </p> <ul> <li> <p> <i>Code:</i> AccessDenied</p> </li> <li> <p> <i>Cause:</i> You are not the owner of the specified bucket, or you do not have the <code>s3:PutInventoryConfiguration</code> bucket permission to set the configuration on the bucket </p> </li> </ul> </li> </ul> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>GetBucketInventoryConfiguration</a> </p> </li> <li> <p> <a>DeleteBucketInventoryConfiguration</a> </p> </li> <li> <p> <a>ListBucketInventoryConfigurations</a> </p> </li> </ul>"
973 },
974 "PutBucketLifecycle": {
975 "name": "PutBucketLifecycle",
976 "http": {
977 "method": "PUT",
978 "requestUri": "/{Bucket}?lifecycle"
979 },
980 "input": {
981 "shape": "PutBucketLifecycleRequest"
982 },
983 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketPUTlifecycle.html",
984 "documentation": "<important> <p>For an updated version of this API, see <a>PutBucketLifecycleConfiguration</a>. This version has been deprecated. Existing lifecycle configurations will work. For new lifecycle configurations, use the updated API. </p> </important> <p>Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle configuration. For information about lifecycle configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//object-lifecycle-mgmt.html\">Object Lifecycle Management</a> in the <i>Amazon Simple Storage Service Developer Guide</i>. </p> <p>By default, all Amazon S3 resources, including buckets, objects, and related subresources (for example, lifecycle configuration and website configuration) are private. Only the resource owner, the AWS account that created the resource, can access it. The resource owner can optionally grant access permissions to others by writing an access policy. For this operation, users must get the <code>s3:PutLifecycleConfiguration</code> permission.</p> <p>You can also explicitly deny permissions. Explicit denial also supersedes any other permissions. If you want to prevent users or accounts from removing or deleting objects from your bucket, you must deny them permissions for the following actions: </p> <ul> <li> <p> <code>s3:DeleteObject</code> </p> </li> <li> <p> <code>s3:DeleteObjectVersion</code> </p> </li> <li> <p> <code>s3:PutLifecycleConfiguration</code> </p> </li> </ul> <p>For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//s3-access-control.html\">Managing Access Permissions to your Amazon S3 Resources</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p>For more examples of transitioning objects to storage classes such as STANDARD_IA or ONEZONE_IA, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//intro-lifecycle-rules.html#lifecycle-configuration-examples\">Examples of Lifecycle Configuration</a>.</p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>GetBucketLifecycle</a>(Deprecated)</p> </li> <li> <p> <a>GetBucketLifecycleConfiguration</a> </p> </li> <li> <p> </p> </li> <li> <p>By default, a resource owner—in this case, a bucket owner, which is the AWS account that created the bucket—can perform any of the operations. A resource owner can also grant others permission to perform the operation. For more information, see the following topics in the Amazon Simple Storage Service Developer Guide: </p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//using-with-s3-actions.html\">Specifying Permissions in a Policy</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev//s3-access-control.html\">Managing Access Permissions to your Amazon S3 Resources</a> </p> </li> </ul> </li> </ul>",
985 "deprecated": true
986 },
987 "PutBucketLifecycleConfiguration": {
988 "name": "PutBucketLifecycleConfiguration",
989 "http": {
990 "method": "PUT",
991 "requestUri": "/{Bucket}?lifecycle"
992 },
993 "input": {
994 "shape": "PutBucketLifecycleConfigurationRequest"
995 },
996 "documentation": "<p>Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle configuration. For information about lifecycle configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <note> <p>Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name prefix, one or more object tags, or a combination of both. Accordingly, this section describes the latest API. The previous version of the API supported filtering based only on an object key name prefix, which is supported for backward compatibility. For the related API description, see <a>PutBucketLifecycle</a>.</p> </note> <p> <b>Rules</b> </p> <p>You specify the lifecycle configuration in your request body. The lifecycle configuration is specified as XML consisting of one or more rules. Each rule consists of the following:</p> <ul> <li> <p>Filter identifying a subset of objects to which the rule applies. The filter can be based on a key name prefix, object tags, or a combination of both.</p> </li> <li> <p>Status whether the rule is in effect.</p> </li> <li> <p>One or more lifecycle transition and expiration actions that you want Amazon S3 to perform on the objects identified by the filter. If the state of your bucket is versioning-enabled or versioning-suspended, you can have many versions of the same object (one current version and zero or more noncurrent versions). Amazon S3 provides predefined actions that you can specify for current and noncurrent object versions.</p> </li> </ul> <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html\">Object Lifecycle Management</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html\">Lifecycle Configuration Elements</a>.</p> <p> <b>Permissions</b> </p> <p>By default, all Amazon S3 resources are private, including buckets, objects, and related subresources (for example, lifecycle configuration and website configuration). Only the resource owner (that is, the AWS account that created it) can access the resource. The resource owner can optionally grant access permissions to others by writing an access policy. For this operation, a user must get the s3:PutLifecycleConfiguration permission.</p> <p>You can also explicitly deny permissions. Explicit deny also supersedes any other permissions. If you want to block users or accounts from removing or deleting objects from your bucket, you must deny them permissions for the following actions:</p> <ul> <li> <p>s3:DeleteObject</p> </li> <li> <p>s3:DeleteObjectVersion</p> </li> <li> <p>s3:PutLifecycleConfiguration</p> </li> </ul> <p>For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p>The following are related to <code>PutBucketLifecycleConfiguration</code>:</p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-configuration-examples.html\">Examples of Lifecycle Configuration</a> </p> </li> <li> <p> <a>GetBucketLifecycleConfiguration</a> </p> </li> <li> <p> <a>DeleteBucketLifecycle</a> </p> </li> </ul>"
997 },
998 "PutBucketLogging": {
999 "name": "PutBucketLogging",
1000 "http": {
1001 "method": "PUT",
1002 "requestUri": "/{Bucket}?logging"
1003 },
1004 "input": {
1005 "shape": "PutBucketLoggingRequest"
1006 },
1007 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketPUTlogging.html",
1008 "documentation": "<p>Set the logging parameters for a bucket and to specify permissions for who can view and modify the logging parameters. All logs are saved to buckets in the same AWS Region as the source bucket. To set the logging status of a bucket, you must be the bucket owner.</p> <p>The bucket owner is automatically granted FULL_CONTROL to all logs. You use the <code>Grantee</code> request element to grant access to other people. The <code>Permissions</code> request element specifies the kind of access the grantee has to the logs.</p> <p> <b>Grantee Values</b> </p> <p>You can specify the person (grantee) to whom you're assigning access rights (using request elements) in the following ways:</p> <ul> <li> <p>By the person's ID:</p> <p> <code>&lt;Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:type=\"CanonicalUser\"&gt;&lt;ID&gt;&lt;&gt;ID&lt;&gt;&lt;/ID&gt;&lt;DisplayName&gt;&lt;&gt;GranteesEmail&lt;&gt;&lt;/DisplayName&gt; &lt;/Grantee&gt;</code> </p> <p>DisplayName is optional and ignored in the request.</p> </li> <li> <p>By Email address:</p> <p> <code> &lt;Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:type=\"AmazonCustomerByEmail\"&gt;&lt;EmailAddress&gt;&lt;&gt;Grantees@email.com&lt;&gt;&lt;/EmailAddress&gt;&lt;/Grantee&gt;</code> </p> <p>The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.</p> </li> <li> <p>By URI:</p> <p> <code>&lt;Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:type=\"Group\"&gt;&lt;URI&gt;&lt;&gt;http://acs.amazonaws.com/groups/global/AuthenticatedUsers&lt;&gt;&lt;/URI&gt;&lt;/Grantee&gt;</code> </p> </li> </ul> <p>To enable logging, you use LoggingEnabled and its children request elements. To disable logging, you use an empty BucketLoggingStatus request element:</p> <p> <code>&lt;BucketLoggingStatus xmlns=\"http://doc.s3.amazonaws.com/2006-03-01\" /&gt;</code> </p> <p>For more information about server access logging, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerLogs.html\">Server Access Logging</a>. </p> <p>For more information about creating a bucket, see <a>CreateBucket</a>. For more information about returning the logging status of a bucket, see <a>GetBucketLogging</a>.</p> <p>The following operations are related to <code>PutBucketLogging</code>:</p> <ul> <li> <p> <a>PutObject</a> </p> </li> <li> <p> <a>DeleteBucket</a> </p> </li> <li> <p> <a>CreateBucket</a> </p> </li> <li> <p> <a>GetBucketLogging</a> </p> </li> </ul>"
1009 },
1010 "PutBucketMetricsConfiguration": {
1011 "name": "PutBucketMetricsConfiguration",
1012 "http": {
1013 "method": "PUT",
1014 "requestUri": "/{Bucket}?metrics"
1015 },
1016 "input": {
1017 "shape": "PutBucketMetricsConfigurationRequest"
1018 },
1019 "documentation": "<p>Sets a metrics configuration (specified by the metrics configuration ID) for the bucket. You can have up to 1,000 metrics configurations per bucket. If you're updating an existing metrics configuration, note that this is a full replacement of the existing metrics configuration. If you don't include the elements you want to keep, they are erased.</p> <p>To use this operation, you must have permissions to perform the <code>s3:PutMetricsConfiguration</code> action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p>For information about CloudWatch request metrics for Amazon S3, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html\">Monitoring Metrics with Amazon CloudWatch</a>.</p> <p>The following operations are related to <code>PutBucketMetricsConfiguration</code>:</p> <ul> <li> <p> <a>DeleteBucketMetricsConfiguration</a> </p> </li> <li> <p> <a>PutBucketMetricsConfiguration</a> </p> </li> <li> <p> <a>ListBucketMetricsConfigurations</a> </p> </li> </ul> <p> <code>GetBucketLifecycle</code> has the following special error:</p> <ul> <li> <p>Error code: <code>TooManyConfigurations</code> </p> <ul> <li> <p>Description: You are attempting to create a new configuration but have already reached the 1,000-configuration limit.</p> </li> <li> <p>HTTP Status Code: HTTP 400 Bad Request</p> </li> </ul> </li> </ul>"
1020 },
1021 "PutBucketNotification": {
1022 "name": "PutBucketNotification",
1023 "http": {
1024 "method": "PUT",
1025 "requestUri": "/{Bucket}?notification"
1026 },
1027 "input": {
1028 "shape": "PutBucketNotificationRequest"
1029 },
1030 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketPUTnotification.html",
1031 "documentation": "<p> No longer used, see the <a>PutBucketNotificationConfiguration</a> operation.</p>",
1032 "deprecated": true
1033 },
1034 "PutBucketNotificationConfiguration": {
1035 "name": "PutBucketNotificationConfiguration",
1036 "http": {
1037 "method": "PUT",
1038 "requestUri": "/{Bucket}?notification"
1039 },
1040 "input": {
1041 "shape": "PutBucketNotificationConfigurationRequest"
1042 },
1043 "documentation": "<p>Enables notifications of specified events for a bucket. For more information about event notifications, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html\">Configuring Event Notifications</a>.</p> <p>Using this API, you can replace an existing notification configuration. The configuration is an XML file that defines the event types that you want Amazon S3 to publish and the destination where you want Amazon S3 to publish an event notification when it detects an event of the specified type.</p> <p>By default, your bucket has no event notifications configured. That is, the notification configuration will be an empty <code>NotificationConfiguration</code>.</p> <p> <code>&lt;NotificationConfiguration&gt;</code> </p> <p> <code>&lt;/NotificationConfiguration&gt;</code> </p> <p>This operation replaces the existing notification configuration with the configuration you include in the request body.</p> <p>After Amazon S3 receives this request, it first verifies that any Amazon Simple Notification Service (Amazon SNS) or Amazon Simple Queue Service (Amazon SQS) destination exists, and that the bucket owner has permission to publish to it by sending a test notification. In the case of AWS Lambda destinations, Amazon S3 verifies that the Lambda function permissions grant Amazon S3 permission to invoke the function from the Amazon S3 bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html\">Configuring Notifications for Amazon S3 Events</a>.</p> <p>You can disable notifications by adding the empty NotificationConfiguration element.</p> <p>By default, only the bucket owner can configure notifications on a bucket. However, bucket owners can use a bucket policy to grant permission to other users to set this configuration with <code>s3:PutBucketNotification</code> permission.</p> <note> <p>The PUT notification is an atomic operation. For example, suppose your notification configuration includes SNS topic, SQS queue, and Lambda function configurations. When you send a PUT request with this configuration, Amazon S3 sends test messages to your SNS topic. If the message fails, the entire PUT operation will fail, and Amazon S3 will not add the configuration to your bucket.</p> </note> <p> <b>Responses</b> </p> <p>If the configuration in the request body includes only one <code>TopicConfiguration</code> specifying only the <code>s3:ReducedRedundancyLostObject</code> event type, the response will also include the <code>x-amz-sns-test-message-id</code> header containing the message ID of the test notification sent to the topic.</p> <p>The following operation is related to <code>PutBucketNotificationConfiguration</code>:</p> <ul> <li> <p> <a>GetBucketNotificationConfiguration</a> </p> </li> </ul>"
1044 },
1045 "PutBucketPolicy": {
1046 "name": "PutBucketPolicy",
1047 "http": {
1048 "method": "PUT",
1049 "requestUri": "/{Bucket}?policy"
1050 },
1051 "input": {
1052 "shape": "PutBucketPolicyRequest"
1053 },
1054 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketPUTpolicy.html",
1055 "documentation": "<p>Applies an Amazon S3 bucket policy to an Amazon S3 bucket. If you are using an identity other than the root user of the AWS account that owns the bucket, the calling identity must have the <code>PutBucketPolicy</code> permissions on the specified bucket and belong to the bucket owner's account in order to use this operation.</p> <p>If you don't have <code>PutBucketPolic</code>y permissions, Amazon S3 returns a <code>403 Access Denied</code> error. If you have the correct permissions, but you're not using an identity that belongs to the bucket owner's account, Amazon S3 returns a <code>405 Method Not Allowed</code> error.</p> <important> <p> As a security precaution, the root user of the AWS account that owns a bucket can always use this operation, even if the policy explicitly denies the root user the ability to perform this action. </p> </important> <p>For more information about bucket policies, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html\">Using Bucket Policies and User Policies</a>.</p> <p>The following operations are related to <code>PutBucketPolicy</code>:</p> <ul> <li> <p> <a>CreateBucket</a> </p> </li> <li> <p> <a>DeleteBucket</a> </p> </li> </ul>"
1056 },
1057 "PutBucketReplication": {
1058 "name": "PutBucketReplication",
1059 "http": {
1060 "method": "PUT",
1061 "requestUri": "/{Bucket}?replication"
1062 },
1063 "input": {
1064 "shape": "PutBucketReplicationRequest"
1065 },
1066 "documentation": "<p> Creates a replication configuration or replaces an existing one. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html\">Replication</a> in the <i>Amazon S3 Developer Guide</i>. </p> <note> <p>To perform this operation, the user or role performing the operation must have the <a href=\"https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_passrole.html\">iam:PassRole</a> permission.</p> </note> <p>Specify the replication configuration in the request body. In the replication configuration, you provide the name of the destination bucket where you want Amazon S3 to replicate objects, the IAM role that Amazon S3 can assume to replicate objects on your behalf, and other relevant information.</p> <p>A replication configuration must include at least one rule, and can contain a maximum of 1,000. Each rule identifies a subset of objects to replicate by filtering the objects in the source bucket. To choose additional subsets of objects to replicate, add a rule for each subset. All rules must specify the same destination bucket.</p> <p>To specify a subset of the objects in the source bucket to apply a replication rule to, add the Filter element as a child of the Rule element. You can filter objects based on an object key prefix, one or more object tags, or both. When you add the Filter element in the configuration, you must also add the following elements: <code>DeleteMarkerReplication</code>, <code>Status</code>, and <code>Priority</code>.</p> <p>For information about enabling versioning on a bucket, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/Versioning.html\">Using Versioning</a>.</p> <p>By default, a resource owner, in this case the AWS account that created the bucket, can perform this operation. The resource owner can also grant others permissions to perform the operation. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a Policy</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p> <b>Handling Replication of Encrypted Objects</b> </p> <p>By default, Amazon S3 doesn't replicate objects that are stored at rest using server-side encryption with CMKs stored in AWS KMS. To replicate AWS KMS-encrypted objects, add the following: <code>SourceSelectionCriteria</code>, <code>SseKmsEncryptedObjects</code>, <code>Status</code>, <code>EncryptionConfiguration</code>, and <code>ReplicaKmsKeyID</code>. For information about replication configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/replication-config-for-kms-objects.html\">Replicating Objects Created with SSE Using CMKs stored in AWS KMS</a>.</p> <p>For information on <code>PutBucketReplication</code> errors, see <a>ReplicationErrorCodeList</a> </p> <p>The following operations are related to <code>PutBucketReplication</code>:</p> <ul> <li> <p> <a>GetBucketReplication</a> </p> </li> <li> <p> <a>DeleteBucketReplication</a> </p> </li> </ul>"
1067 },
1068 "PutBucketRequestPayment": {
1069 "name": "PutBucketRequestPayment",
1070 "http": {
1071 "method": "PUT",
1072 "requestUri": "/{Bucket}?requestPayment"
1073 },
1074 "input": {
1075 "shape": "PutBucketRequestPaymentRequest"
1076 },
1077 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTrequestPaymentPUT.html",
1078 "documentation": "<p>Sets the request payment configuration for a bucket. By default, the bucket owner pays for downloads from the bucket. This configuration parameter enables the bucket owner (only) to specify that the person requesting the download will be charged for the download. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RequesterPaysBuckets.html\">Requester Pays Buckets</a>.</p> <p>The following operations are related to <code>PutBucketRequestPayment</code>:</p> <ul> <li> <p> <a>CreateBucket</a> </p> </li> <li> <p> <a>GetBucketRequestPayment</a> </p> </li> </ul>"
1079 },
1080 "PutBucketTagging": {
1081 "name": "PutBucketTagging",
1082 "http": {
1083 "method": "PUT",
1084 "requestUri": "/{Bucket}?tagging"
1085 },
1086 "input": {
1087 "shape": "PutBucketTaggingRequest"
1088 },
1089 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketPUTtagging.html",
1090 "documentation": "<p>Sets the tags for a bucket.</p> <p>Use tags to organize your AWS bill to reflect your own cost structure. To do this, sign up to get your AWS account bill with tag key values included. Then, to see the cost of combined resources, organize your billing information according to resources with the same tag key values. For example, you can tag several resources with a specific application name, and then organize your billing information to see the total cost of that application across several services. For more information, see <a href=\"https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html\">Cost Allocation and Tagging</a>.</p> <note> <p>Within a bucket, if you add a tag that has the same key as an existing tag, the new value overwrites the old value. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/CostAllocTagging.html\">Using Cost Allocation in Amazon S3 Bucket Tags</a>.</p> </note> <p>To use this operation, you must have permissions to perform the <code>s3:PutBucketTagging</code> action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a>.</p> <p> <code>PutBucketTagging</code> has the following special errors:</p> <ul> <li> <p>Error code: <code>InvalidTagError</code> </p> <ul> <li> <p>Description: The tag provided was not a valid tag. This error can occur if the tag did not pass input validation. For information about tag restrictions, see <a href=\"https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2//allocation-tag-restrictions.html\">User-Defined Tag Restrictions</a> and <a href=\"https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2//aws-tag-restrictions.html\">AWS-Generated Cost Allocation Tag Restrictions</a>.</p> </li> </ul> </li> <li> <p>Error code: <code>MalformedXMLError</code> </p> <ul> <li> <p>Description: The XML provided does not match the schema.</p> </li> </ul> </li> <li> <p>Error code: <code>OperationAbortedError </code> </p> <ul> <li> <p>Description: A conflicting conditional operation is currently in progress against this resource. Please try again.</p> </li> </ul> </li> <li> <p>Error code: <code>InternalError</code> </p> <ul> <li> <p>Description: The service was unable to apply the provided tag to the bucket.</p> </li> </ul> </li> </ul> <p>The following operations are related to <code>PutBucketTagging</code>:</p> <ul> <li> <p> <a>GetBucketTagging</a> </p> </li> <li> <p> <a>DeleteBucketTagging</a> </p> </li> </ul>"
1091 },
1092 "PutBucketVersioning": {
1093 "name": "PutBucketVersioning",
1094 "http": {
1095 "method": "PUT",
1096 "requestUri": "/{Bucket}?versioning"
1097 },
1098 "input": {
1099 "shape": "PutBucketVersioningRequest"
1100 },
1101 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketPUTVersioningStatus.html",
1102 "documentation": "<p>Sets the versioning state of an existing bucket. To set the versioning state, you must be the bucket owner.</p> <p>You can set the versioning state with one of the following values:</p> <p> <b>Enabled</b>—Enables versioning for the objects in the bucket. All objects added to the bucket receive a unique version ID.</p> <p> <b>Suspended</b>—Disables versioning for the objects in the bucket. All objects added to the bucket receive the version ID null.</p> <p>If the versioning state has never been set on a bucket, it has no versioning state; a <a>GetBucketVersioning</a> request does not return a versioning state value.</p> <p>If the bucket owner enables MFA Delete in the bucket versioning configuration, the bucket owner must include the <code>x-amz-mfa request</code> header and the <code>Status</code> and the <code>MfaDelete</code> request elements in a request to set the versioning state of the bucket.</p> <important> <p>If you have an object expiration lifecycle policy in your non-versioned bucket and you want to maintain the same permanent delete behavior when you enable versioning, you must add a noncurrent expiration policy. The noncurrent expiration lifecycle policy will manage the deletes of the noncurrent object versions in the version-enabled bucket. (A version-enabled bucket maintains one current and zero or more noncurrent object versions.) For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html#lifecycle-and-other-bucket-config\">Lifecycle and Versioning</a>.</p> </important> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>CreateBucket</a> </p> </li> <li> <p> <a>DeleteBucket</a> </p> </li> <li> <p> <a>GetBucketVersioning</a> </p> </li> </ul>"
1103 },
1104 "PutBucketWebsite": {
1105 "name": "PutBucketWebsite",
1106 "http": {
1107 "method": "PUT",
1108 "requestUri": "/{Bucket}?website"
1109 },
1110 "input": {
1111 "shape": "PutBucketWebsiteRequest"
1112 },
1113 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketPUTwebsite.html",
1114 "documentation": "<p>Sets the configuration of the website that is specified in the <code>website</code> subresource. To configure a bucket as a website, you can add this subresource on the bucket with website configuration information such as the file name of the index document and any redirect rules. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html\">Hosting Websites on Amazon S3</a>.</p> <p>This PUT operation requires the <code>S3:PutBucketWebsite</code> permission. By default, only the bucket owner can configure the website attached to a bucket; however, bucket owners can allow other users to set the website configuration by writing a bucket policy that grants them the <code>S3:PutBucketWebsite</code> permission.</p> <p>To redirect all website requests sent to the bucket's website endpoint, you add a website configuration with the following elements. Because all requests are sent to another website, you don't need to provide index document name for the bucket.</p> <ul> <li> <p> <code>WebsiteConfiguration</code> </p> </li> <li> <p> <code>RedirectAllRequestsTo</code> </p> </li> <li> <p> <code>HostName</code> </p> </li> <li> <p> <code>Protocol</code> </p> </li> </ul> <p>If you want granular control over redirects, you can use the following elements to add routing rules that describe conditions for redirecting requests and information about the redirect destination. In this case, the website configuration must provide an index document for the bucket, because some requests might not be redirected. </p> <ul> <li> <p> <code>WebsiteConfiguration</code> </p> </li> <li> <p> <code>IndexDocument</code> </p> </li> <li> <p> <code>Suffix</code> </p> </li> <li> <p> <code>ErrorDocument</code> </p> </li> <li> <p> <code>Key</code> </p> </li> <li> <p> <code>RoutingRules</code> </p> </li> <li> <p> <code>RoutingRule</code> </p> </li> <li> <p> <code>Condition</code> </p> </li> <li> <p> <code>HttpErrorCodeReturnedEquals</code> </p> </li> <li> <p> <code>KeyPrefixEquals</code> </p> </li> <li> <p> <code>Redirect</code> </p> </li> <li> <p> <code>Protocol</code> </p> </li> <li> <p> <code>HostName</code> </p> </li> <li> <p> <code>ReplaceKeyPrefixWith</code> </p> </li> <li> <p> <code>ReplaceKeyWith</code> </p> </li> <li> <p> <code>HttpRedirectCode</code> </p> </li> </ul>"
1115 },
1116 "PutObject": {
1117 "name": "PutObject",
1118 "http": {
1119 "method": "PUT",
1120 "requestUri": "/{Bucket}/{Key+}"
1121 },
1122 "input": {
1123 "shape": "PutObjectRequest"
1124 },
1125 "output": {
1126 "shape": "PutObjectOutput"
1127 },
1128 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTObjectPUT.html",
1129 "documentation": "<p>Adds an object to a bucket. You must have WRITE permissions on a bucket to add an object to it.</p> <p>Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added the entire object to the bucket.</p> <p>Amazon S3 is a distributed system. If it receives multiple write requests for the same object simultaneously, it overwrites all but the last object written. Amazon S3 does not provide object locking; if you need this, make sure to build it into your application layer or use versioning instead.</p> <p>To ensure that data is not corrupted traversing the network, use the <code>Content-MD5</code> header. When you use this header, Amazon S3 checks the object against the provided MD5 value and, if they do not match, returns an error. Additionally, you can calculate the MD5 while putting an object to Amazon S3 and compare the returned ETag to the calculated MD5 value.</p> <note> <p>To configure your application to send the request headers before sending the request body, use the <code>100-continue</code> HTTP status code. For PUT operations, this helps you avoid sending the message body if the message is rejected based on the headers (for example, because authentication fails or a redirect occurs). For more information on the <code>100-continue</code> HTTP status code, see Section 8.2.3 of <a href=\"http://www.ietf.org/rfc/rfc2616.txt\">http://www.ietf.org/rfc/rfc2616.txt</a>.</p> </note> <p>You can optionally request server-side encryption. With server-side encryption, Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts the data when you access it. You have the option to provide your own encryption key or use AWS managed encryption keys. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html\">Using Server-Side Encryption</a>.</p> <dl> <dt>Access Permissions</dt> <dd> <p>You can optionally specify the accounts or groups that should be granted specific permissions on the new object. There are two ways to grant the permissions using the request headers:</p> <ul> <li> <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned ACL</a>.</p> </li> <li> <p>Specify access permissions explicitly with the <code>x-amz-grant-read</code>, <code>x-amz-grant-read-acp</code>, <code>x-amz-grant-write-acp</code>, and <code>x-amz-grant-full-control</code> headers. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>.</p> </li> </ul> <p>You can use either a canned ACL or specify access permissions explicitly. You cannot do both.</p> </dd> <dt>Server-Side- Encryption-Specific Request Headers</dt> <dd> <p>You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. The option you use depends on whether you want to use AWS managed encryption keys or provide your own encryption key. </p> <ul> <li> <p>Use encryption keys managed by Amazon S3 or customer master keys (CMKs) stored in AWS Key Management Service (AWS KMS) – If you want AWS to manage the keys used to encrypt data, specify the following headers in the request.</p> <ul> <li> <p>x-amz-server-side​-encryption</p> </li> <li> <p>x-amz-server-side-encryption-aws-kms-key-id</p> </li> <li> <p>x-amz-server-side-encryption-context</p> </li> </ul> <note> <p>If you specify <code>x-amz-server-side-encryption:aws:kms</code>, but don't provide <code>x-amz-server-side-encryption-aws-kms-key-id</code>, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data. If you want to use a customer managed AWS KMS CMK, you must provide the <code>x-amz-server-side-encryption-aws-kms-key-id</code> of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and not asymmetric CMKs. For more information, see <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html\">Using Symmetric and Asymmetric Keys</a> in the <i>AWS Key Management Service Developer Guide</i>.</p> </note> <important> <p>All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.</p> </important> <p>For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html\">Protecting Data Using Server-Side Encryption with CMKs stored in AWS</a>.</p> </li> <li> <p>Use customer-provided encryption keys – If you want to manage your own encryption keys, provide all the following headers in the request.</p> <ul> <li> <p>x-amz-server-side​-encryption​-customer-algorithm</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key-MD5</p> </li> </ul> <p>For more information about server-side encryption with CMKs stored in KMS (SSE-KMS), see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html\">Protecting Data Using Server-Side Encryption with CMKs stored in AWS</a>.</p> </li> </ul> </dd> <dt>Access-Control-List (ACL)-Specific Request Headers</dt> <dd> <p>You also can use the following access control–related headers with this operation. By default, all objects are private. Only the owner has full access control. When adding a new object, you can grant permissions to individual AWS accounts or to predefined groups defined by Amazon S3. These permissions are then added to the Access Control List (ACL) on the object. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Using ACLs</a>. With this operation, you can grant access permissions using one of the following two methods:</p> <ul> <li> <p>Specify a canned ACL (<code>x-amz-acl</code>) — Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned ACL</a>.</p> </li> <li> <p>Specify access permissions explicitly — To explicitly grant access permissions to specific AWS accounts or groups, use the following headers. Each header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>. In the header, you specify a list of grantees who get the specific permission. To grant permissions explicitly use:</p> <ul> <li> <p>x-amz-grant-read</p> </li> <li> <p>x-amz-grant-write</p> </li> <li> <p>x-amz-grant-read-acp</p> </li> <li> <p>x-amz-grant-write-acp</p> </li> <li> <p>x-amz-grant-full-control</p> </li> </ul> <p>You specify each grantee as a type=value pair, where the type is one of the following:</p> <ul> <li> <p> <code>emailAddress</code> – if the value specified is the email address of an AWS account</p> <important> <p>Using email addresses to specify a grantee is only supported in the following AWS Regions: </p> <ul> <li> <p>US East (N. Virginia)</p> </li> <li> <p>US West (N. California)</p> </li> <li> <p> US West (Oregon)</p> </li> <li> <p> Asia Pacific (Singapore)</p> </li> <li> <p>Asia Pacific (Sydney)</p> </li> <li> <p>Asia Pacific (Tokyo)</p> </li> <li> <p>EU (Ireland)</p> </li> <li> <p>South America (São Paulo)</p> </li> </ul> <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the AWS General Reference</p> </important> </li> <li> <p> <code>id</code> – if the value specified is the canonical user ID of an AWS account</p> </li> <li> <p> <code>uri</code> – if you are granting permissions to a predefined group</p> </li> </ul> <p>For example, the following <code>x-amz-grant-read</code> header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:</p> <p> <code>x-amz-grant-read: emailAddress=\"xyz@amazon.com\", emailAddress=\"abc@amazon.com\" </code> </p> </li> </ul> </dd> <dt>Server-Side- Encryption-Specific Request Headers</dt> <dd> <p>You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. The option you use depends on whether you want to use AWS-managed encryption keys or provide your own encryption key. </p> <ul> <li> <p>Use encryption keys managed by Amazon S3 or customer master keys (CMKs) stored in AWS Key Management Service (AWS KMS) – If you want AWS to manage the keys used to encrypt data, specify the following headers in the request.</p> <ul> <li> <p>x-amz-server-side​-encryption</p> </li> <li> <p>x-amz-server-side-encryption-aws-kms-key-id</p> </li> <li> <p>x-amz-server-side-encryption-context</p> </li> </ul> <note> <p>If you specify <code>x-amz-server-side-encryption:aws:kms</code>, but don't provide <code>x-amz-server-side-encryption-aws-kms-key-id</code>, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data. If you want to use a customer managed AWS KMS CMK, you must provide the <code>x-amz-server-side-encryption-aws-kms-key-id</code> of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and not asymmetric CMKs. For more information, see <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html\">Using Symmetric and Asymmetric Keys</a> in the <i>AWS Key Management Service Developer Guide</i>.</p> </note> <important> <p>All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.</p> </important> <p>For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html\">Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS</a>.</p> </li> <li> <p>Use customer-provided encryption keys – If you want to manage your own encryption keys, provide all the following headers in the request.</p> <note> <p>If you use this feature, the ETag value that Amazon S3 returns in the response is not the MD5 of the object.</p> </note> <ul> <li> <p>x-amz-server-side​-encryption​-customer-algorithm</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key-MD5</p> </li> </ul> <p>For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html\">Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS</a>.</p> </li> </ul> </dd> </dl> <p> <b>Storage Class Options</b> </p> <p>By default, Amazon S3 uses the Standard storage class to store newly created objects. The Standard storage class provides high durability and high availability. You can specify other storage classes depending on the performance needs. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html\">Storage Classes</a> in the Amazon Simple Storage Service Developer Guide.</p> <p> <b>Versioning</b> </p> <p>If you enable versioning for a bucket, Amazon S3 automatically generates a unique version ID for the object being stored. Amazon S3 returns this ID in the response using the <code>x-amz-version-id response</code> header. If versioning is suspended, Amazon S3 always uses null as the version ID for the object stored. For more information about returning the versioning state of a bucket, see <a>GetBucketVersioning</a>. If you enable versioning for a bucket, when Amazon S3 receives multiple write requests for the same object simultaneously, it stores all of the objects.</p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>CopyObject</a> </p> </li> <li> <p> <a>DeleteObject</a> </p> </li> </ul>"
1130 },
1131 "PutObjectAcl": {
1132 "name": "PutObjectAcl",
1133 "http": {
1134 "method": "PUT",
1135 "requestUri": "/{Bucket}/{Key+}?acl"
1136 },
1137 "input": {
1138 "shape": "PutObjectAclRequest"
1139 },
1140 "output": {
1141 "shape": "PutObjectAclOutput"
1142 },
1143 "errors": [
1144 {
1145 "shape": "NoSuchKey"
1146 }
1147 ],
1148 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTObjectPUTacl.html",
1149 "documentation": "<p>Uses the <code>acl</code> subresource to set the access control list (ACL) permissions for an object that already exists in a bucket. You must have <code>WRITE_ACP</code> permission to set the ACL of an object.</p> <p>Depending on your application needs, you can choose to set the ACL on an object using either the request body or the headers. For example, if you have an existing application that updates a bucket ACL using the request body, you can continue to use that approach.</p> <p> <b>Access Permissions</b> </p> <p>You can set access permissions using one of the following methods:</p> <ul> <li> <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. Specify the canned ACL name as the value of <code>x-amz-ac</code>l. If you use this header, you cannot use other access control-specific headers in your request. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned ACL</a>.</p> </li> <li> <p>Specify access permissions explicitly with the <code>x-amz-grant-read</code>, <code>x-amz-grant-read-acp</code>, <code>x-amz-grant-write-acp</code>, and <code>x-amz-grant-full-control</code> headers. When using these headers, you specify explicit access permissions and grantees (AWS accounts or Amazon S3 groups) who will receive the permission. If you use these ACL-specific headers, you cannot use <code>x-amz-acl</code> header to set a canned ACL. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>.</p> <p>You specify each grantee as a type=value pair, where the type is one of the following:</p> <ul> <li> <p> <code>emailAddress</code> – if the value specified is the email address of an AWS account</p> </li> <li> <p> <code>id</code> – if the value specified is the canonical user ID of an AWS account</p> </li> <li> <p> <code>uri</code> – if you are granting permissions to a predefined group</p> </li> </ul> <p>For example, the following <code>x-amz-grant-read</code> header grants list objects permission to the two AWS accounts identified by their email addresses.</p> <p> <code>x-amz-grant-read: emailAddress=\"xyz@amazon.com\", emailAddress=\"abc@amazon.com\" </code> </p> </li> </ul> <p>You can use either a canned ACL or specify access permissions explicitly. You cannot do both.</p> <p> <b>Grantee Values</b> </p> <p>You can specify the person (grantee) to whom you're assigning access rights (using request elements) in the following ways:</p> <ul> <li> <p>By Email address:</p> <p> <code>&lt;Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:type=\"AmazonCustomerByEmail\"&gt;&lt;EmailAddress&gt;&lt;&gt;Grantees@email.com&lt;&gt;&lt;/EmailAddress&gt;lt;/Grantee&gt;</code> </p> <p>The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.</p> </li> <li> <p>By the person's ID:</p> <p> <code>&lt;Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:type=\"CanonicalUser\"&gt;&lt;ID&gt;&lt;&gt;ID&lt;&gt;&lt;/ID&gt;&lt;DisplayName&gt;&lt;&gt;GranteesEmail&lt;&gt;&lt;/DisplayName&gt; &lt;/Grantee&gt;</code> </p> <p>DisplayName is optional and ignored in the request.</p> </li> <li> <p>By URI:</p> <p> <code>&lt;Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:type=\"Group\"&gt;&lt;URI&gt;&lt;&gt;http://acs.amazonaws.com/groups/global/AuthenticatedUsers&lt;&gt;&lt;/URI&gt;&lt;/Grantee&gt;</code> </p> </li> </ul> <p> <b>Versioning</b> </p> <p>The ACL of an object is set at the object version level. By default, PUT sets the ACL of the current version of an object. To set the ACL of a different version, use the <code>versionId</code> subresource.</p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>CopyObject</a> </p> </li> <li> <p> <a>GetObject</a> </p> </li> </ul>"
1150 },
1151 "PutObjectLegalHold": {
1152 "name": "PutObjectLegalHold",
1153 "http": {
1154 "method": "PUT",
1155 "requestUri": "/{Bucket}/{Key+}?legal-hold"
1156 },
1157 "input": {
1158 "shape": "PutObjectLegalHoldRequest"
1159 },
1160 "output": {
1161 "shape": "PutObjectLegalHoldOutput"
1162 },
1163 "documentation": "<p>Applies a Legal Hold configuration to the specified object.</p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking Objects</a> </p> </li> </ul>"
1164 },
1165 "PutObjectLockConfiguration": {
1166 "name": "PutObjectLockConfiguration",
1167 "http": {
1168 "method": "PUT",
1169 "requestUri": "/{Bucket}?object-lock"
1170 },
1171 "input": {
1172 "shape": "PutObjectLockConfigurationRequest"
1173 },
1174 "output": {
1175 "shape": "PutObjectLockConfigurationOutput"
1176 },
1177 "documentation": "<p>Places an Object Lock configuration on the specified bucket. The rule specified in the Object Lock configuration will be applied by default to every new object placed in the specified bucket.</p> <note> <p> <code>DefaultRetention</code> requires either Days or Years. You can't specify both at the same time.</p> </note> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking Objects</a> </p> </li> </ul>"
1178 },
1179 "PutObjectRetention": {
1180 "name": "PutObjectRetention",
1181 "http": {
1182 "method": "PUT",
1183 "requestUri": "/{Bucket}/{Key+}?retention"
1184 },
1185 "input": {
1186 "shape": "PutObjectRetentionRequest"
1187 },
1188 "output": {
1189 "shape": "PutObjectRetentionOutput"
1190 },
1191 "documentation": "<p>Places an Object Retention configuration on an object.</p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking Objects</a> </p> </li> </ul>"
1192 },
1193 "PutObjectTagging": {
1194 "name": "PutObjectTagging",
1195 "http": {
1196 "method": "PUT",
1197 "requestUri": "/{Bucket}/{Key+}?tagging"
1198 },
1199 "input": {
1200 "shape": "PutObjectTaggingRequest"
1201 },
1202 "output": {
1203 "shape": "PutObjectTaggingOutput"
1204 },
1205 "documentation": "<p>Sets the supplied tag-set to an object that already exists in a bucket</p> <p>A tag is a key-value pair. You can associate tags with an object by sending a PUT request against the tagging subresource that is associated with the object. You can retrieve tags by sending a GET request. For more information, see <a>GetObjectTagging</a>.</p> <p>For tagging-related restrictions related to characters and encodings, see <a href=\"https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/allocation-tag-restrictions.html\">Tag Restrictions</a>. Note that Amazon S3 limits the maximum number of tags to 10 tags per object.</p> <p>To use this operation, you must have permission to perform the <code>s3:PutObjectTagging</code> action. By default, the bucket owner has this permission and can grant this permission to others.</p> <p>To put tags of any other version, use the <code>versionId</code> query parameter. You also need permission for the <code>s3:PutObjectVersionTagging</code> action.</p> <p>For information about the Amazon S3 object tagging feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html\">Object Tagging</a>.</p> <p class=\"title\"> <b>Special Errors</b> </p> <ul> <li> <p class=\"title\"> <b/> </p> <ul> <li> <p> <i>Code: InvalidTagError </i> </p> </li> <li> <p> <i>Cause: The tag provided was not a valid tag. This error can occur if the tag did not pass input validation. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html\">Object Tagging</a>.</i> </p> </li> </ul> </li> <li> <p class=\"title\"> <b/> </p> <ul> <li> <p> <i>Code: MalformedXMLError </i> </p> </li> <li> <p> <i>Cause: The XML provided does not match the schema.</i> </p> </li> </ul> </li> <li> <ul> <li> <p> <i>Code: OperationAbortedError </i> </p> </li> <li> <p> <i>Cause: A conflicting conditional operation is currently in progress against this resource. Please try again.</i> </p> </li> </ul> </li> <li> <ul> <li> <p> <i>Code: InternalError</i> </p> </li> <li> <p> <i>Cause: The service was unable to apply the provided tag to the object.</i> </p> </li> </ul> </li> </ul> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>GetObjectTagging</a> </p> </li> </ul>"
1206 },
1207 "PutPublicAccessBlock": {
1208 "name": "PutPublicAccessBlock",
1209 "http": {
1210 "method": "PUT",
1211 "requestUri": "/{Bucket}?publicAccessBlock"
1212 },
1213 "input": {
1214 "shape": "PutPublicAccessBlockRequest"
1215 },
1216 "documentation": "<p>Creates or modifies the <code>PublicAccessBlock</code> configuration for an Amazon S3 bucket. To use this operation, you must have the <code>s3:PutBucketPublicAccessBlock</code> permission. For more information about Amazon S3 permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a Policy</a>.</p> <important> <p>When Amazon S3 evaluates the <code>PublicAccessBlock</code> configuration for a bucket or an object, it checks the <code>PublicAccessBlock</code> configuration for both the bucket (or the bucket that contains the object) and the bucket owner's account. If the <code>PublicAccessBlock</code> configurations are different between the bucket and the account, Amazon S3 uses the most restrictive combination of the bucket-level and account-level settings.</p> </important> <p>For more information about when Amazon S3 considers a bucket or an object public, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status\">The Meaning of \"Public\"</a>.</p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>GetPublicAccessBlock</a> </p> </li> <li> <p> <a>DeletePublicAccessBlock</a> </p> </li> <li> <p> <a>GetBucketPolicyStatus</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html\">Using Amazon S3 Block Public Access</a> </p> </li> </ul>"
1217 },
1218 "RestoreObject": {
1219 "name": "RestoreObject",
1220 "http": {
1221 "method": "POST",
1222 "requestUri": "/{Bucket}/{Key+}?restore"
1223 },
1224 "input": {
1225 "shape": "RestoreObjectRequest"
1226 },
1227 "output": {
1228 "shape": "RestoreObjectOutput"
1229 },
1230 "errors": [
1231 {
1232 "shape": "ObjectAlreadyInActiveTierError"
1233 }
1234 ],
1235 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTObjectRestore.html",
1236 "documentation": "<p>Restores an archived copy of an object back into Amazon S3</p> <p>This operation performs the following types of requests: </p> <ul> <li> <p> <code>select</code> - Perform a select query on an archived object</p> </li> <li> <p> <code>restore an archive</code> - Restore an archived object</p> </li> </ul> <p>To use this operation, you must have permissions to perform the <code>s3:RestoreObject</code> and <code>s3:GetObject</code> actions. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources\">Permissions Related to Bucket Subresource Operations</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html\">Managing Access Permissions to Your Amazon S3 Resources</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p> <b>Querying Archives with Select Requests</b> </p> <p>You use a select type of request to perform SQL queries on archived objects. The archived objects that are being queried by the select request must be formatted as uncompressed comma-separated values (CSV) files. You can run queries and custom analytics on your archived data without having to restore your data to a hotter Amazon S3 tier. For an overview about select requests, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/querying-glacier-archives.html\">Querying Archived Objects</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p>When making a select request, do the following:</p> <ul> <li> <p>Define an output location for the select query's output. This must be an Amazon S3 bucket in the same AWS Region as the bucket that contains the archive object that is being queried. The AWS account that initiates the job must have permissions to write to the S3 bucket. You can specify the storage class and encryption for the output objects stored in the bucket. For more information about output, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/querying-glacier-archives.html\">Querying Archived Objects</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p>For more information about the <code>S3</code> structure in the request body, see the following:</p> <ul> <li> <p> <a>PutObject</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Managing Access with ACLs</a> in the <i>Amazon Simple Storage Service Developer Guide</i> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html\">Protecting Data Using Server-Side Encryption</a> in the <i>Amazon Simple Storage Service Developer Guide</i> </p> </li> </ul> </li> <li> <p>Define the SQL expression for the <code>SELECT</code> type of restoration for your query in the request body's <code>SelectParameters</code> structure. You can use expressions like the following examples.</p> <ul> <li> <p>The following expression returns all records from the specified object.</p> <p> <code>SELECT * FROM Object</code> </p> </li> <li> <p>Assuming that you are not using any headers for data stored in the object, you can specify columns with positional headers.</p> <p> <code>SELECT s._1, s._2 FROM Object s WHERE s._3 &gt; 100</code> </p> </li> <li> <p>If you have headers and you set the <code>fileHeaderInfo</code> in the <code>CSV</code> structure in the request body to <code>USE</code>, you can specify headers in the query. (If you set the <code>fileHeaderInfo</code> field to <code>IGNORE</code>, the first row is skipped for the query.) You cannot mix ordinal positions with header column names. </p> <p> <code>SELECT s.Id, s.FirstName, s.SSN FROM S3Object s</code> </p> </li> </ul> </li> </ul> <p>For more information about using SQL with Glacier Select restore, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-glacier-select-sql-reference.html\">SQL Reference for Amazon S3 Select and Glacier Select</a> in the <i>Amazon Simple Storage Service Developer Guide</i>. </p> <p>When making a select request, you can also do the following:</p> <ul> <li> <p>To expedite your queries, specify the <code>Expedited</code> tier. For more information about tiers, see \"Restoring Archives,\" later in this topic.</p> </li> <li> <p>Specify details about the data serialization format of both the input object that is being queried and the serialization of the CSV-encoded query results.</p> </li> </ul> <p>The following are additional important facts about the select feature:</p> <ul> <li> <p>The output results are new Amazon S3 objects. Unlike archive retrievals, they are stored until explicitly deleted-manually or through a lifecycle policy.</p> </li> <li> <p>You can issue more than one select request on the same Amazon S3 object. Amazon S3 doesn't deduplicate requests, so avoid issuing duplicate requests.</p> </li> <li> <p> Amazon S3 accepts a select request even if the object has already been restored. A select request doesn’t return error response <code>409</code>.</p> </li> </ul> <p> <b>Restoring Archives</b> </p> <p>Objects in the GLACIER and DEEP_ARCHIVE storage classes are archived. To access an archived object, you must first initiate a restore request. This restores a temporary copy of the archived object. In a restore request, you specify the number of days that you want the restored copy to exist. After the specified period, Amazon S3 deletes the temporary copy but the object remains archived in the GLACIER or DEEP_ARCHIVE storage class that object was restored from. </p> <p>To restore a specific object version, you can provide a version ID. If you don't provide a version ID, Amazon S3 restores the current version.</p> <p>The time it takes restore jobs to finish depends on which storage class the object is being restored from and which data access tier you specify. </p> <p>When restoring an archived object (or using a select request), you can specify one of the following data access tier options in the <code>Tier</code> element of the request body: </p> <ul> <li> <p> <b> <code>Expedited</code> </b> - Expedited retrievals allow you to quickly access your data stored in the GLACIER storage class when occasional urgent requests for a subset of archives are required. For all but the largest archived objects (250 MB+), data accessed using Expedited retrievals are typically made available within 1–5 minutes. Provisioned capacity ensures that retrieval capacity for Expedited retrievals is available when you need it. Expedited retrievals and provisioned capacity are not available for the DEEP_ARCHIVE storage class.</p> </li> <li> <p> <b> <code>Standard</code> </b> - Standard retrievals allow you to access any of your archived objects within several hours. This is the default option for the GLACIER and DEEP_ARCHIVE retrieval requests that do not specify the retrieval option. Standard retrievals typically complete within 3-5 hours from the GLACIER storage class and typically complete within 12 hours from the DEEP_ARCHIVE storage class. </p> </li> <li> <p> <b> <code>Bulk</code> </b> - Bulk retrievals are Amazon S3 Glacier’s lowest-cost retrieval option, enabling you to retrieve large amounts, even petabytes, of data inexpensively in a day. Bulk retrievals typically complete within 5-12 hours from the GLACIER storage class and typically complete within 48 hours from the DEEP_ARCHIVE storage class.</p> </li> </ul> <p>For more information about archive retrieval options and provisioned capacity for <code>Expedited</code> data access, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html\">Restoring Archived Objects</a> in the <i>Amazon Simple Storage Service Developer Guide</i>. </p> <p>You can use Amazon S3 restore speed upgrade to change the restore speed to a faster speed while it is in progress. You upgrade the speed of an in-progress restoration by issuing another restore request to the same object, setting a new <code>Tier</code> request element. When issuing a request to upgrade the restore tier, you must choose a tier that is faster than the tier that the in-progress restore is using. You must not change any other parameters, such as the <code>Days</code> request element. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html#restoring-objects-upgrade-tier.title.html\"> Upgrading the Speed of an In-Progress Restore</a> in the <i>Amazon Simple Storage Service Developer Guide</i>. </p> <p>To get the status of object restoration, you can send a <code>HEAD</code> request. Operations return the <code>x-amz-restore</code> header, which provides information about the restoration status, in the response. You can use Amazon S3 event notifications to notify you when a restore is initiated or completed. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html\">Configuring Amazon S3 Event Notifications</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p>After restoring an archived object, you can update the restoration period by reissuing the request with a new period. Amazon S3 updates the restoration period relative to the current time and charges only for the request-there are no data transfer charges. You cannot update the restoration period when Amazon S3 is actively processing your current restore request for the object.</p> <p>If your bucket has a lifecycle configuration with a rule that includes an expiration action, the object expiration overrides the life span that you specify in a restore request. For example, if you restore an object copy for 10 days, but the object is scheduled to expire in 3 days, Amazon S3 deletes the object in 3 days. For more information about lifecycle configuration, see <a>PutBucketLifecycleConfiguration</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html\">Object Lifecycle Management</a> in <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p> <b>Responses</b> </p> <p>A successful operation returns either the <code>200 OK</code> or <code>202 Accepted</code> status code. </p> <ul> <li> <p>If the object copy is not previously restored, then Amazon S3 returns <code>202 Accepted</code> in the response. </p> </li> <li> <p>If the object copy is previously restored, Amazon S3 returns <code>200 OK</code> in the response. </p> </li> </ul> <p class=\"title\"> <b>Special Errors</b> </p> <ul> <li> <p class=\"title\"> <b/> </p> <ul> <li> <p> <i>Code: RestoreAlreadyInProgress</i> </p> </li> <li> <p> <i>Cause: Object restore is already in progress. (This error does not apply to SELECT type requests.)</i> </p> </li> <li> <p> <i>HTTP Status Code: 409 Conflict</i> </p> </li> <li> <p> <i>SOAP Fault Code Prefix: Client</i> </p> </li> </ul> </li> <li> <p class=\"title\"> <b/> </p> <ul> <li> <p> <i>Code: GlacierExpeditedRetrievalNotAvailable</i> </p> </li> <li> <p> <i>Cause: Glacier expedited retrievals are currently not available. Try again later. (Returned if there is insufficient capacity to process the Expedited request. This error applies only to Expedited retrievals and not to Standard or Bulk retrievals.)</i> </p> </li> <li> <p> <i>HTTP Status Code: 503</i> </p> </li> <li> <p> <i>SOAP Fault Code Prefix: N/A</i> </p> </li> </ul> </li> </ul> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>PutBucketLifecycleConfiguration</a> </p> </li> <li> <p> <a>GetBucketNotificationConfiguration</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-glacier-select-sql-reference.html\">SQL Reference for Amazon S3 Select and Glacier Select </a> in the <i>Amazon Simple Storage Service Developer Guide</i> </p> </li> </ul>",
1237 "alias": "PostObjectRestore"
1238 },
1239 "SelectObjectContent": {
1240 "name": "SelectObjectContent",
1241 "http": {
1242 "method": "POST",
1243 "requestUri": "/{Bucket}/{Key+}?select&select-type=2"
1244 },
1245 "input": {
1246 "shape": "SelectObjectContentRequest",
1247 "locationName": "SelectObjectContentRequest",
1248 "xmlNamespace": {
1249 "uri": "http://s3.amazonaws.com/doc/2006-03-01/"
1250 }
1251 },
1252 "output": {
1253 "shape": "SelectObjectContentOutput"
1254 },
1255 "documentation": "<p>This operation filters the contents of an Amazon S3 object based on a simple structured query language (SQL) statement. In the request, along with the SQL expression, you must also specify a data serialization format (JSON, CSV, or Apache Parquet) of the object. Amazon S3 uses this format to parse object data into records, and returns only records that match the specified SQL expression. You must also specify the data serialization format for the response.</p> <p>For more information about Amazon S3 Select, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/selecting-content-from-objects.html\">Selecting Content from Objects</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p>For more information about using SQL with Amazon S3 Select, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-glacier-select-sql-reference.html\"> SQL Reference for Amazon S3 Select and Glacier Select</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p/> <p> <b>Permissions</b> </p> <p>You must have <code>s3:GetObject</code> permission for this operation. Amazon S3 Select does not support anonymous access. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a Policy</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p/> <p> <i>Object Data Formats</i> </p> <p>You can use Amazon S3 Select to query objects that have the following format properties:</p> <ul> <li> <p> <i>CSV, JSON, and Parquet</i> - Objects must be in CSV, JSON, or Parquet format.</p> </li> <li> <p> <i>UTF-8</i> - UTF-8 is the only encoding type Amazon S3 Select supports.</p> </li> <li> <p> <i>GZIP or BZIP2</i> - CSV and JSON files can be compressed using GZIP or BZIP2. GZIP and BZIP2 are the only compression formats that Amazon S3 Select supports for CSV and JSON files. Amazon S3 Select supports columnar compression for Parquet using GZIP or Snappy. Amazon S3 Select does not support whole-object compression for Parquet objects.</p> </li> <li> <p> <i>Server-side encryption</i> - Amazon S3 Select supports querying objects that are protected with server-side encryption.</p> <p>For objects that are encrypted with customer-provided encryption keys (SSE-C), you must use HTTPS, and you must use the headers that are documented in the <a>GetObject</a>. For more information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side Encryption (Using Customer-Provided Encryption Keys)</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p>For objects that are encrypted with Amazon S3 managed encryption keys (SSE-S3) and customer master keys (CMKs) stored in AWS Key Management Service (SSE-KMS), server-side encryption is handled transparently, so you don't need to specify anything. For more information about server-side encryption, including SSE-S3 and SSE-KMS, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html\">Protecting Data Using Server-Side Encryption</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> </li> </ul> <p> <b>Working with the Response Body</b> </p> <p>Given the response size is unknown, Amazon S3 Select streams the response as a series of messages and includes a <code>Transfer-Encoding</code> header with <code>chunked</code> as its value in the response. For more information, see <a>RESTSelectObjectAppendix</a> .</p> <p/> <p> <b>GetObject Support</b> </p> <p>The <code>SelectObjectContent</code> operation does not support the following <code>GetObject</code> functionality. For more information, see <a>GetObject</a>.</p> <ul> <li> <p> <code>Range</code>: While you can specify a scan range for a Amazon S3 Select request, see <a>SelectObjectContentRequest$ScanRange</a> in the request parameters below, you cannot specify the range of bytes of an object to return. </p> </li> <li> <p>GLACIER, DEEP_ARCHIVE and REDUCED_REDUNDANCY storage classes: You cannot specify the GLACIER, DEEP_ARCHIVE, or <code>REDUCED_REDUNDANCY</code> storage classes. For more information, about storage classes see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html#storage-class-intro\">Storage Classes</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> </li> </ul> <p/> <p> <b>Special Errors</b> </p> <p>For a list of special errors for this operation and for general information about Amazon S3 errors and a list of error codes, see <a>ErrorResponses</a> </p> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>GetObject</a> </p> </li> <li> <p> <a>GetBucketLifecycleConfiguration</a> </p> </li> <li> <p> <a>PutBucketLifecycleConfiguration</a> </p> </li> </ul>"
1256 },
1257 "UploadPart": {
1258 "name": "UploadPart",
1259 "http": {
1260 "method": "PUT",
1261 "requestUri": "/{Bucket}/{Key+}"
1262 },
1263 "input": {
1264 "shape": "UploadPartRequest"
1265 },
1266 "output": {
1267 "shape": "UploadPartOutput"
1268 },
1269 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/mpUploadUploadPart.html",
1270 "documentation": "<p>Uploads a part in a multipart upload.</p> <note> <p>In this operation, you provide part data in your request. However, you have an option to specify your existing Amazon S3 object as a data source for the part you are uploading. To upload a part from an existing object, you use the <a>UploadPartCopy</a> operation. </p> </note> <p>You must initiate a multipart upload (see <a>CreateMultipartUpload</a>) before you can upload any part. In response to your initiate request, Amazon S3 returns an upload ID, a unique identifier, that you must include in your upload part request.</p> <p>Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely identifies a part and also defines its position within the object being created. If you upload a new part using the same part number that was used with a previous part, the previously uploaded part is overwritten. Each part must be at least 5 MB in size, except the last part. There is no size limit on the last part of your multipart upload.</p> <p>To ensure that data is not corrupted when traversing the network, specify the <code>Content-MD5</code> header in the upload part request. Amazon S3 checks the part data against the provided MD5 value. If they do not match, Amazon S3 returns an error. </p> <p> <b>Note:</b> After you initiate multipart upload and upload one or more parts, you must either complete or abort multipart upload in order to stop getting charged for storage of the uploaded parts. Only after you either complete or abort multipart upload, Amazon S3 frees up the parts storage and stops charging you for the parts storage.</p> <p>For more information on multipart uploads, go to <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html\">Multipart Upload Overview</a> in the <i>Amazon Simple Storage Service Developer Guide </i>.</p> <p>For information on the permissions required to use the multipart upload API, go to <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload API and Permissions</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p>You can optionally request server-side encryption where Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it for you when you access it. You have the option of providing your own encryption key, or you can use the AWS managed encryption keys. If you choose to provide your own encryption key, the request headers you provide in the request must match the headers you used in the request to initiate the upload by using <a>CreateMultipartUpload</a>. For more information, go to <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html\">Using Server-Side Encryption</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> <p>Server-side encryption is supported by the S3 Multipart Upload actions. Unless you are using a customer-provided encryption key, you don't need to specify the encryption parameters in each UploadPart request. Instead, you only need to specify the server-side encryption parameters in the initial Initiate Multipart request. For more information, see <a>CreateMultipartUpload</a>.</p> <p>If you requested server-side encryption using a customer-provided encryption key in your initiate multipart upload request, you must provide identical encryption information in each part upload using the following headers.</p> <ul> <li> <p>x-amz-server-side​-encryption​-customer-algorithm</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key</p> </li> <li> <p>x-amz-server-side​-encryption​-customer-key-MD5</p> </li> </ul> <p class=\"title\"> <b>Special Errors</b> </p> <ul> <li> <p class=\"title\"> <b/> </p> <ul> <li> <p> <i>Code: NoSuchUpload</i> </p> </li> <li> <p> <i>Cause: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.</i> </p> </li> <li> <p> <i> HTTP Status Code: 404 Not Found </i> </p> </li> <li> <p> <i>SOAP Fault Code Prefix: Client</i> </p> </li> </ul> </li> </ul> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>CreateMultipartUpload</a> </p> </li> <li> <p> <a>CompleteMultipartUpload</a> </p> </li> <li> <p> <a>AbortMultipartUpload</a> </p> </li> <li> <p> <a>ListParts</a> </p> </li> <li> <p> <a>ListMultipartUploads</a> </p> </li> </ul>"
1271 },
1272 "UploadPartCopy": {
1273 "name": "UploadPartCopy",
1274 "http": {
1275 "method": "PUT",
1276 "requestUri": "/{Bucket}/{Key+}"
1277 },
1278 "input": {
1279 "shape": "UploadPartCopyRequest"
1280 },
1281 "output": {
1282 "shape": "UploadPartCopyOutput"
1283 },
1284 "documentationUrl": "http://docs.amazonwebservices.com/AmazonS3/latest/API/mpUploadUploadPartCopy.html",
1285 "documentation": "<p>Uploads a part by copying data from an existing object as data source. You specify the data source by adding the request header <code>x-amz-copy-source</code> in your request and a byte range by adding the request header <code>x-amz-copy-source-range</code> in your request. </p> <p>The minimum allowable part size for a multipart upload is 5 MB. For more information about multipart upload limits, go to <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/qfacts.html\">Quick Facts</a> in the <i>Amazon Simple Storage Service Developer Guide</i>. </p> <note> <p>Instead of using an existing object as part data, you might use the <a>UploadPart</a> operation and provide data in your request.</p> </note> <p>You must initiate a multipart upload before you can upload any part. In response to your initiate request. Amazon S3 returns a unique identifier, the upload ID, that you must include in your upload part request.</p> <p>For more information about using the <code>UploadPartCopy</code> operation, see the following:</p> <ul> <li> <p>For conceptual information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading Objects Using Multipart Upload</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> </li> <li> <p>For information about permissions required to use the multipart upload API, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload API and Permissions</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> </li> <li> <p>For information about copying objects using a single atomic operation vs. the multipart upload, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectOperations.html\">Operations on Objects</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p> </li> <li> <p>For information about using server-side encryption with customer-provided encryption keys with the UploadPartCopy operation, see <a>CopyObject</a> and <a>UploadPart</a>.</p> </li> </ul> <p>Note the following additional considerations about the request headers <code>x-amz-copy-source-if-match</code>, <code>x-amz-copy-source-if-none-match</code>, <code>x-amz-copy-source-if-unmodified-since</code>, and <code>x-amz-copy-source-if-modified-since</code>:</p> <p> </p> <ul> <li> <p> <b>Consideration 1</b> - If both of the <code>x-amz-copy-source-if-match</code> and <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the request as follows:</p> <p> <code>x-amz-copy-source-if-match</code> condition evaluates to <code>true</code>, and;</p> <p> <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to <code>false</code>;</p> <p>Amazon S3 returns <code>200 OK</code> and copies the data. </p> </li> <li> <p> <b>Consideration 2</b> - If both of the <code>x-amz-copy-source-if-none-match</code> and <code>x-amz-copy-source-if-modified-since</code> headers are present in the request as follows:</p> <p> <code>x-amz-copy-source-if-none-match</code> condition evaluates to <code>false</code>, and;</p> <p> <code>x-amz-copy-source-if-modified-since</code> condition evaluates to <code>true</code>;</p> <p>Amazon S3 returns <code>412 Precondition Failed</code> response code. </p> </li> </ul> <p> <b>Versioning</b> </p> <p>If your bucket has versioning enabled, you could have multiple versions of the same object. By default, <code>x-amz-copy-source</code> identifies the current version of the object to copy. If the current version is a delete marker and you don't specify a versionId in the <code>x-amz-copy-source</code>, Amazon S3 returns a 404 error, because the object does not exist. If you specify versionId in the <code>x-amz-copy-source</code> and the versionId is a delete marker, Amazon S3 returns an HTTP 400 error, because you are not allowed to specify a delete marker as a version for the <code>x-amz-copy-source</code>. </p> <p>You can optionally specify a specific version of the source object to copy by adding the <code>versionId</code> subresource as shown in the following example:</p> <p> <code>x-amz-copy-source: /bucket/object?versionId=version id</code> </p> <p class=\"title\"> <b>Special Errors</b> </p> <ul> <li> <p class=\"title\"> <b/> </p> <ul> <li> <p> <i>Code: NoSuchUpload</i> </p> </li> <li> <p> <i>Cause: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.</i> </p> </li> <li> <p> <i>HTTP Status Code: 404 Not Found</i> </p> </li> </ul> </li> <li> <p class=\"title\"> <b/> </p> <ul> <li> <p> <i>Code: InvalidRequest</i> </p> </li> <li> <p> <i>Cause: The specified copy source is not supported as a byte-range copy source.</i> </p> </li> <li> <p> <i>HTTP Status Code: 400 Bad Request</i> </p> </li> </ul> </li> </ul> <p class=\"title\"> <b>Related Resources</b> </p> <ul> <li> <p> <a>CreateMultipartUpload</a> </p> </li> <li> <p> <a>UploadPart</a> </p> </li> <li> <p> <a>CompleteMultipartUpload</a> </p> </li> <li> <p> <a>AbortMultipartUpload</a> </p> </li> <li> <p> <a>ListParts</a> </p> </li> <li> <p> <a>ListMultipartUploads</a> </p> </li> </ul>"
1286 }
1287 },
1288 "shapes": {
1289 "AbortDate": {
1290 "type": "timestamp"
1291 },
1292 "AbortIncompleteMultipartUpload": {
1293 "type": "structure",
1294 "members": {
1295 "DaysAfterInitiation": {
1296 "shape": "DaysAfterInitiation",
1297 "documentation": "<p>Specifies the number of days after which Amazon S3 aborts an incomplete multipart upload.</p>"
1298 }
1299 },
1300 "documentation": "<p>Specifies the days since the initiation of an incomplete multipart upload that Amazon S3 will wait before permanently removing all parts of the upload. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config\"> Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle Policy</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p>"
1301 },
1302 "AbortMultipartUploadOutput": {
1303 "type": "structure",
1304 "members": {
1305 "RequestCharged": {
1306 "shape": "RequestCharged",
1307 "location": "header",
1308 "locationName": "x-amz-request-charged"
1309 }
1310 }
1311 },
1312 "AbortMultipartUploadRequest": {
1313 "type": "structure",
1314 "required": [
1315 "Bucket",
1316 "Key",
1317 "UploadId"
1318 ],
1319 "members": {
1320 "Bucket": {
1321 "shape": "BucketName",
1322 "documentation": "<p>The bucket name to which the upload was taking place. </p> <p>When using this API with an access point, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this operation using an access point through the AWS SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-access-points.html\">Using Access Points</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p>",
1323 "location": "uri",
1324 "locationName": "Bucket"
1325 },
1326 "Key": {
1327 "shape": "ObjectKey",
1328 "documentation": "<p>Key of the object for which the multipart upload was initiated.</p>",
1329 "location": "uri",
1330 "locationName": "Key"
1331 },
1332 "UploadId": {
1333 "shape": "MultipartUploadId",
1334 "documentation": "<p>Upload ID that identifies the multipart upload.</p>",
1335 "location": "querystring",
1336 "locationName": "uploadId"
1337 },
1338 "RequestPayer": {
1339 "shape": "RequestPayer",
1340 "location": "header",
1341 "locationName": "x-amz-request-payer"
1342 }
1343 }
1344 },
1345 "AbortRuleId": {
1346 "type": "string"
1347 },
1348 "AccelerateConfiguration": {
1349 "type": "structure",
1350 "members": {
1351 "Status": {
1352 "shape": "BucketAccelerateStatus",
1353 "documentation": "<p>Specifies the transfer acceleration status of the bucket.</p>"
1354 }
1355 },
1356 "documentation": "<p>Configures the transfer acceleration state for an Amazon S3 bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html\">Amazon S3 Transfer Acceleration</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p>"
1357 },
1358 "AcceptRanges": {
1359 "type": "string"
1360 },
1361 "AccessControlPolicy": {
1362 "type": "structure",
1363 "members": {
1364 "Grants": {
1365 "shape": "Grants",
1366 "documentation": "<p>A list of grants.</p>",
1367 "locationName": "AccessControlList"
1368 },
1369 "Owner": {
1370 "shape": "Owner",
1371 "documentation": "<p>Container for the bucket owner's display name and ID.</p>"
1372 }
1373 },
1374 "documentation": "<p>Contains the elements that set the ACL permissions for an object per grantee.</p>"
1375 },
1376 "AccessControlTranslation": {
1377 "type": "structure",
1378 "required": [
1379 "Owner"
1380 ],
1381 "members": {
1382 "Owner": {
1383 "shape": "OwnerOverride",
1384 "documentation": "<p>Specifies the replica ownership. For default and valid values, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTreplication.html\">PUT bucket replication</a> in the <i>Amazon Simple Storage Service API Reference</i>.</p>"
1385 }
1386 },
1387 "documentation": "<p>A container for information about access control for replicas.</p>"
1388 },
1389 "AccountId": {
1390 "type": "string"
1391 },
1392 "AllowQuotedRecordDelimiter": {
1393 "type": "boolean"
1394 },
1395 "AllowedHeader": {
1396 "type": "string"
1397 },
1398 "AllowedHeaders": {
1399 "type": "list",
1400 "member": {
1401 "shape": "AllowedHeader"
1402 },
1403 "flattened": true
1404 },
1405 "AllowedMethod": {
1406 "type": "string"
1407 },
1408 "AllowedMethods": {
1409 "type": "list",
1410 "member": {
1411 "shape": "AllowedMethod"
1412 },
1413 "flattened": true
1414 },
1415 "AllowedOrigin": {
1416 "type": "string"
1417 },
1418 "AllowedOrigins": {
1419 "type": "list",
1420 "member": {
1421 "shape": "AllowedOrigin"
1422 },
1423 "flattened": true
1424 },
1425 "AnalyticsAndOperator": {
1426 "type": "structure",
1427 "members": {
1428 "Prefix": {
1429 "shape": "Prefix",
1430 "documentation": "<p>The prefix to use when evaluating an AND predicate: The prefix that an object must have to be included in the metrics results.</p>"
1431 },
1432 "Tags": {
1433 "shape": "TagSet",
1434 "documentation": "<p>The list of tags to use when evaluating an AND predicate.</p>",
1435 "flattened": true,
1436 "locationName": "Tag"
1437 }
1438 },
1439 "documentation": "<p>A conjunction (logical AND) of predicates, which is used in evaluating a metrics filter. The operator must have at least two predicates in any combination, and an object must match all of the predicates for the filter to apply.</p>"
1440 },
1441 "AnalyticsConfiguration": {
1442 "type": "structure",
1443 "required": [
1444 "Id",
1445 "StorageClassAnalysis"
1446 ],
1447 "members": {
1448 "Id": {
1449 "shape": "AnalyticsId",
1450 "documentation": "<p>The ID that identifies the analytics configuration.</p>"
1451 },
1452 "Filter": {
1453 "shape": "AnalyticsFilter",
1454 "documentation": "<p>The filter used to describe a set of objects for analyses. A filter must have exactly one prefix, one tag, or one conjunction (AnalyticsAndOperator). If no filter is provided, all objects will be considered in any analysis.</p>"
1455 },
1456 "StorageClassAnalysis": {
1457 "shape": "StorageClassAnalysis",
1458 "documentation": "<p> Contains data related to access patterns to be collected and made available to analyze the tradeoffs between different storage classes. </p>"
1459 }
1460 },
1461 "documentation": "<p> Specifies the configuration and any analyses for the analytics filter of an Amazon S3 bucket.</p>"
1462 },
1463 "AnalyticsConfigurationList": {
1464 "type": "list",
1465 "member": {
1466 "shape": "AnalyticsConfiguration"
1467 },
1468 "flattened": true
1469 },
1470 "AnalyticsExportDestination": {
1471 "type": "structure",
1472 "required": [
1473 "S3BucketDestination"
1474 ],
1475 "members": {
1476 "S3BucketDestination": {
1477 "shape": "AnalyticsS3BucketDestination",
1478 "documentation": "<p>A destination signifying output to an S3 bucket.</p>"
1479 }
1480 },
1481 "documentation": "<p>Where to publish the analytics results.</p>"
1482 },
1483 "AnalyticsFilter": {
1484 "type": "structure",
1485 "members": {
1486 "Prefix": {
1487 "shape": "Prefix",
1488 "documentation": "<p>The prefix to use when evaluating an analytics filter.</p>"
1489 },
1490 "Tag": {
1491 "shape": "Tag",
1492 "documentation": "<p>The tag to use when evaluating an analytics filter.</p>"
1493 },
1494 "And": {
1495 "shape": "AnalyticsAndOperator",
1496 "documentation": "<p>A conjunction (logical AND) of predicates, which is used in evaluating an analytics filter. The operator must have at least two predicates.</p>"
1497 }
1498 },
1499 "documentation": "<p>The filter used to describe a set of objects for analyses. A filter must have exactly one prefix, one tag, or one conjunction (AnalyticsAndOperator). If no filter is provided, all objects will be considered in any analysis.</p>"
1500 },
1501 "AnalyticsId": {
1502 "type": "string"
1503 },
1504 "AnalyticsS3BucketDestination": {
1505 "type": "structure",
1506 "required": [
1507 "Format",
1508 "Bucket"
1509 ],
1510 "members": {
1511 "Format": {
1512 "shape": "AnalyticsS3ExportFileFormat",
1513 "documentation": "<p>Specifies the file format used when exporting data to Amazon S3.</p>"
1514 },
1515 "BucketAccountId": {
1516 "shape": "AccountId",
1517 "documentation": "<p>The account ID that owns the destination bucket. If no account ID is provided, the owner will not be validated prior to exporting data.</p>"
1518 },
1519 "Bucket": {
1520 "shape": "BucketName",
1521 "documentation": "<p>The Amazon Resource Name (ARN) of the bucket to which data is exported.</p>"
1522 },
1523 "Prefix": {
1524 "shape": "Prefix",
1525 "documentation": "<p>The prefix to use when exporting data. The prefix is prepended to all results.</p>"
1526 }
1527 },
1528 "documentation": "<p>Contains information about where to publish the analytics results.</p>"
1529 },
1530 "AnalyticsS3ExportFileFormat": {
1531 "type": "string",
1532 "enum": [
1533 "CSV"
1534 ]
1535 },
1536 "Body": {
1537 "type": "blob"
1538 },
1539 "Bucket": {
1540 "type": "structure",
1541 "members": {
1542 "Name": {
1543 "shape": "BucketName",
1544 "documentation": "<p>The name of the bucket.</p>"
1545 },
1546 "CreationDate": {
1547 "shape": "CreationDate",
1548 "documentation": "<p>Date the bucket was created.</p>"
1549 }
1550 },
1551 "documentation": "<p> In terms of implementation, a Bucket is a resource. An Amazon S3 bucket name is globally unique, and the namespace is shared by all AWS accounts. </p>"
1552 },
1553 "BucketAccelerateStatus": {
1554 "type": "string",
1555 "enum": [
1556 "Enabled",
1557 "Suspended"
1558 ]
1559 },
1560 "BucketCannedACL": {
1561 "type": "string",
1562 "enum": [
1563 "private",
1564 "public-read",
1565 "public-read-write",
1566 "authenticated-read"
1567 ]
1568 },
1569 "BucketLifecycleConfiguration": {
1570 "type": "structure",
1571 "required": [
1572 "Rules"
1573 ],
1574 "members": {
1575 "Rules": {
1576 "shape": "LifecycleRules",
1577 "documentation": "<p>A lifecycle rule for individual objects in an Amazon S3 bucket.</p>",
1578 "locationName": "Rule"
1579 }
1580 },
1581 "documentation": "<p>Specifies the lifecycle configuration for objects in an Amazon S3 bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html\">Object Lifecycle Management</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p>"
1582 },
1583 "BucketLocationConstraint": {
1584 "type": "string",
1585 "enum": [
1586 "EU",
1587 "eu-west-1",
1588 "us-west-1",
1589 "us-west-2",
1590 "ap-south-1",
1591 "ap-southeast-1",
1592 "ap-southeast-2",
1593 "ap-northeast-1",
1594 "sa-east-1",
1595 "cn-north-1",
1596 "eu-central-1"
1597 ]
1598 },
1599 "BucketLoggingStatus": {
1600 "type": "structure",
1601 "members": {
1602 "LoggingEnabled": {
1603 "shape": "LoggingEnabled"
1604 }
1605 },
1606 "documentation": "<p>Container for logging status information.</p>"
1607 },
1608 "BucketLogsPermission": {
1609 "type": "string",
1610 "enum": [
1611 "FULL_CONTROL",
1612 "READ",
1613 "WRITE"
1614 ]
1615 },
1616 "BucketName": {
1617 "type": "string"
1618 },
1619 "BucketVersioningStatus": {
1620 "type": "string",
1621 "enum": [
1622 "Enabled",
1623 "Suspended"
1624 ]
1625 },
1626 "Buckets": {
1627 "type": "list",
1628 "member": {
1629 "shape": "Bucket",
1630 "locationName": "Bucket"
1631 }
1632 },
1633 "BypassGovernanceRetention": {
1634 "type": "boolean"
1635 },
1636 "BytesProcessed": {
1637 "type": "long"
1638 },
1639 "BytesReturned": {
1640 "type": "long"
1641 },
1642 "BytesScanned": {
1643 "type": "long"
1644 },
1645 "CORSConfiguration": {
1646 "type": "structure",
1647 "required": [
1648 "CORSRules"
1649 ],
1650 "members": {
1651 "CORSRules": {
1652 "shape": "CORSRules",
1653 "documentation": "<p>A set of origins and methods (cross-origin access that you want to allow). You can add up to 100 rules to the configuration.</p>",
1654 "locationName": "CORSRule"
1655 }
1656 },
1657 "documentation": "<p>Describes the cross-origin access configuration for objects in an Amazon S3 bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html\">Enabling Cross-Origin Resource Sharing</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p>"
1658 },
1659 "CORSRule": {
1660 "type": "structure",
1661 "required": [
1662 "AllowedMethods",
1663 "AllowedOrigins"
1664 ],
1665 "members": {
1666 "AllowedHeaders": {
1667 "shape": "AllowedHeaders",
1668 "documentation": "<p>Headers that are specified in the <code>Access-Control-Request-Headers</code> header. These headers are allowed in a preflight OPTIONS request. In response to any preflight OPTIONS request, Amazon S3 returns any requested headers that are allowed.</p>",
1669 "locationName": "AllowedHeader"
1670 },
1671 "AllowedMethods": {
1672 "shape": "AllowedMethods",
1673 "documentation": "<p>An HTTP method that you allow the origin to execute. Valid values are <code>GET</code>, <code>PUT</code>, <code>HEAD</code>, <code>POST</code>, and <code>DELETE</code>.</p>",
1674 "locationName": "AllowedMethod"
1675 },
1676 "AllowedOrigins": {
1677 "shape": "AllowedOrigins",
1678 "documentation": "<p>One or more origins you want customers to be able to access the bucket from.</p>",
1679 "locationName": "AllowedOrigin"
1680 },
1681 "ExposeHeaders": {
1682 "shape": "ExposeHeaders",
1683 "documentation": "<p>One or more headers in the response that you want customers to be able to access from their applications (for example, from a JavaScript <code>XMLHttpRequest</code> object).</p>",
1684 "locationName": "ExposeHeader"
1685 },
1686 "MaxAgeSeconds": {
1687 "shape": "MaxAgeSeconds",
1688 "documentation": "<p>The time in seconds that your browser is to cache the preflight response for the specified resource.</p>"
1689 }
1690 },
1691 "documentation": "<p>Specifies a cross-origin access rule for an Amazon S3 bucket.</p>"
1692 },
1693 "CORSRules": {
1694 "type": "list",
1695 "member": {
1696 "shape": "CORSRule"
1697 },
1698 "flattened": true
1699 },
1700 "CSVInput": {
1701 "type": "structure",
1702 "members": {
1703 "FileHeaderInfo": {
1704 "shape": "FileHeaderInfo",
1705 "documentation": "<p>Describes the first line of input. Valid values are:</p> <ul> <li> <p> <code>NONE</code>: First line is not a header.</p> </li> <li> <p> <code>IGNORE</code>: First line is a header, but you can't use the header values to indicate the column in an expression. You can use column position (such as _1, _2, …) to indicate the column (<code>SELECT s._1 FROM OBJECT s</code>).</p> </li> <li> <p> <code>Use</code>: First line is a header, and you can use the header value to identify a column in an expression (<code>SELECT \"name\" FROM OBJECT</code>). </p> </li> </ul>"
1706 },
1707 "Comments": {
1708 "shape": "Comments",
1709 "documentation": "<p>A single character used to indicate that a row should be ignored when the character is present at the start of that row. You can specify any character to indicate a comment line.</p>"
1710 },
1711 "QuoteEscapeCharacter": {
1712 "shape": "QuoteEscapeCharacter",
1713 "documentation": "<p>A single character used for escaping the quotation mark character inside an already escaped value. For example, the value \"\"\" a , b \"\"\" is parsed as \" a , b \".</p>"
1714 },
1715 "RecordDelimiter": {
1716 "shape": "RecordDelimiter",
1717 "documentation": "<p>A single character used to separate individual records in the input. Instead of the default value, you can specify an arbitrary delimiter.</p>"
1718 },
1719 "FieldDelimiter": {
1720 "shape": "FieldDelimiter",
1721 "documentation": "<p>A single character used to separate individual fields in a record. You can specify an arbitrary delimiter.</p>"
1722 },
1723 "QuoteCharacter": {
1724 "shape": "QuoteCharacter",
1725 "documentation": "<p>A single character used for escaping when the field delimiter is part of the value. For example, if the value is <code>a, b</code>, Amazon S3 wraps this field value in quotation marks, as follows: <code>\" a , b \"</code>.</p> <p>Type: String</p> <p>Default: <code>\"</code> </p> <p>Ancestors: <code>CSV</code> </p>"
1726 },
1727 "AllowQuotedRecordDelimiter": {
1728 "shape": "AllowQuotedRecordDelimiter",
1729 "documentation": "<p>Specifies that CSV field values may contain quoted record delimiters and such records should be allowed. Default value is FALSE. Setting this value to TRUE may lower performance.</p>"
1730 }
1731 },
1732 "documentation": "<p>Describes how an uncompressed comma-separated values (CSV)-formatted input object is formatted.</p>"
1733 },
1734 "CSVOutput": {
1735 "type": "structure",
1736 "members": {
1737 "QuoteFields": {
1738 "shape": "QuoteFields",
1739 "documentation": "<p>Indicates whether to use quotation marks around output fields. </p> <ul> <li> <p> <code>ALWAYS</code>: Always use quotation marks for output fields.</p> </li> <li> <p> <code>ASNEEDED</code>: Use quotation marks for output fields when needed.</p> </li> </ul>"
1740 },
1741 "QuoteEscapeCharacter": {
1742 "shape": "QuoteEscapeCharacter",
1743 "documentation": "<p>The single character used for escaping the quote character inside an already escaped value.</p>"
1744 },
1745 "RecordDelimiter": {
1746 "shape": "RecordDelimiter",
1747 "documentation": "<p>A single character used to separate individual records in the output. Instead of the default value, you can specify an arbitrary delimiter.</p>"
1748 },
1749 "FieldDelimiter": {
1750 "shape": "FieldDelimiter",
1751 "documentation": "<p>The value used to separate individual fields in a record. You can specify an arbitrary delimiter.</p>"
1752 },
1753 "QuoteCharacter": {
1754 "shape": "QuoteCharacter",
1755 "documentation": "<p>A single character used for escaping when the field delimiter is part of the value. For example, if the value is <code>a, b</code>, Amazon S3 wraps this field value in quotation marks, as follows: <code>\" a , b \"</code>.</p>"
1756 }
1757 },
1758 "documentation": "<p>Describes how uncompressed comma-separated values (CSV)-formatted results are formatted.</p>"
1759 },
1760 "CacheControl": {
1761 "type": "string"
1762 },
1763 "CloudFunction": {
1764 "type": "string"
1765 },
1766 "CloudFunctionConfiguration": {
1767 "type": "structure",
1768 "members": {
1769 "Id": {
1770 "shape": "NotificationId"
1771 },
1772 "Event": {
1773 "shape": "Event",
1774 "deprecated": true
1775 },
1776 "Events": {
1777 "shape": "EventList",
1778 "documentation": "<p>Bucket events for which to send notifications.</p>",
1779 "locationName": "Event"
1780 },
1781 "CloudFunction": {
1782 "shape": "CloudFunction",
1783 "documentation": "<p>Lambda cloud function ARN that Amazon S3 can invoke when it detects events of the specified type.</p>"
1784 },
1785 "InvocationRole": {
1786 "shape": "CloudFunctionInvocationRole",
1787 "documentation": "<p>The role supporting the invocation of the Lambda function</p>"
1788 }
1789 },
1790 "documentation": "<p>Container for specifying the AWS Lambda notification configuration.</p>"
1791 },
1792 "CloudFunctionInvocationRole": {
1793 "type": "string"
1794 },
1795 "Code": {
1796 "type": "string"
1797 },
1798 "Comments": {
1799 "type": "string"
1800 },
1801 "CommonPrefix": {
1802 "type": "structure",
1803 "members": {
1804 "Prefix": {
1805 "shape": "Prefix",
1806 "documentation": "<p>Container for the specified common prefix.</p>"
1807 }
1808 },
1809 "documentation": "<p>Container for all (if there are any) keys between Prefix and the next occurrence of the string specified by a delimiter. CommonPrefixes lists keys that act like subdirectories in the directory specified by Prefix. For example, if the prefix is notes/ and the delimiter is a slash (/) as in notes/summer/july, the common prefix is notes/summer/. </p>"
1810 },
1811 "CommonPrefixList": {
1812 "type": "list",
1813 "member": {
1814 "shape": "CommonPrefix"
1815 },
1816 "flattened": true
1817 },
1818 "CompleteMultipartUploadOutput": {
1819 "type": "structure",
1820 "members": {
1821 "Location": {
1822 "shape": "Location",
1823 "documentation": "<p>The URI that identifies the newly created object.</p>"
1824 },
1825 "Bucket": {
1826 "shape": "BucketName",
1827 "documentation": "<p>The name of the bucket that contains the newly created object.</p>"
1828 },
1829 "Key": {
1830 "shape": "ObjectKey",
1831 "documentation": "<p>The object key of the newly created object.</p>"
1832 },
1833 "Expiration": {
1834 "shape": "Expiration",
1835 "documentation": "<p>If the object expiration is configured, this will contain the expiration date (expiry-date) and rule ID (rule-id). The value of rule-id is URL encoded.</p>",
1836 "location": "header",
1837 "locationName": "x-amz-expiration"
1838 },
1839 "ETag": {
1840 "shape": "ETag",
1841 "documentation": "<p>Entity tag that identifies the newly created object's data. Objects with different object data will have different entity tags. The entity tag is an opaque string. The entity tag may or may not be an MD5 digest of the object data. If the entity tag is not an MD5 digest of the object data, it will contain one or more nonhexadecimal characters and/or will consist of less than 32 or more than 32 hexadecimal digits.</p>"
1842 },
1843 "ServerSideEncryption": {
1844 "shape": "ServerSideEncryption",
1845 "documentation": "<p>If you specified server-side encryption either with an Amazon S3-managed encryption key or an AWS KMS customer master key (CMK) in your initiate multipart upload request, the response includes this header. It confirms the encryption algorithm that Amazon S3 used to encrypt the object.</p>",
1846 "location": "header",
1847 "locationName": "x-amz-server-side-encryption"
1848 },
1849 "VersionId": {
1850 "shape": "ObjectVersionId",
1851 "documentation": "<p>Version ID of the newly created object, in case the bucket has versioning turned on.</p>",
1852 "location": "header",
1853 "locationName": "x-amz-version-id"
1854 },
1855 "SSEKMSKeyId": {
1856 "shape": "SSEKMSKeyId",
1857 "documentation": "<p>If present, specifies the ID of the AWS Key Management Service (AWS KMS) symmetric customer managed customer master key (CMK) that was used for the object.</p>",
1858 "location": "header",
1859 "locationName": "x-amz-server-side-encryption-aws-kms-key-id"
1860 },
1861 "RequestCharged": {
1862 "shape": "RequestCharged",
1863 "location": "header",
1864 "locationName": "x-amz-request-charged"
1865 }
1866 }
1867 },
1868 "CompleteMultipartUploadRequest": {
1869 "type": "structure",
1870 "required": [
1871 "Bucket",
1872 "Key",
1873 "UploadId"
1874 ],
1875 "members": {
1876 "Bucket": {
1877 "shape": "BucketName",
1878 "documentation": "<p>Name of the bucket to which the multipart upload was initiated.</p>",
1879 "location": "uri",
1880 "locationName": "Bucket"
1881 },
1882 "Key": {
1883 "shape": "ObjectKey",
1884 "documentation": "<p>Object key for which the multipart upload was initiated.</p>",
1885 "location": "uri",
1886 "locationName": "Key"
1887 },
1888 "MultipartUpload": {
1889 "shape": "CompletedMultipartUpload",
1890 "documentation": "<p>The container for the multipart upload request information.</p>",
1891 "locationName": "CompleteMultipartUpload",
1892 "xmlNamespace": {
1893 "uri": "http://s3.amazonaws.com/doc/2006-03-01/"
1894 }
1895 },
1896 "UploadId": {
1897 "shape": "MultipartUploadId",
1898 "documentation": "<p>ID for the initiated multipart upload.</p>",
1899 "location": "querystring",
1900 "locationName": "uploadId"
1901 },
1902 "RequestPayer": {
1903 "shape": "RequestPayer",
1904 "location": "header",
1905 "locationName": "x-amz-request-payer"
1906 }
1907 },
1908 "payload": "MultipartUpload"
1909 },
1910 "CompletedMultipartUpload": {
1911 "type": "structure",
1912 "members": {
1913 "Parts": {
1914 "shape": "CompletedPartList",
1915 "documentation": "<p>Array of CompletedPart data types.</p>",
1916 "locationName": "Part"
1917 }
1918 },
1919 "documentation": "<p>The container for the completed multipart upload details.</p>"
1920 },
1921 "CompletedPart": {
1922 "type": "structure",
1923 "members": {
1924 "ETag": {
1925 "shape": "ETag",
1926 "documentation": "<p>Entity tag returned when the part was uploaded.</p>"
1927 },
1928 "PartNumber": {
1929 "shape": "PartNumber",
1930 "documentation": "<p>Part number that identifies the part. This is a positive integer between 1 and 10,000.</p>"
1931 }
1932 },
1933 "documentation": "<p>Details of the parts that were uploaded.</p>"
1934 },
1935 "CompletedPartList": {
1936 "type": "list",
1937 "member": {
1938 "shape": "CompletedPart"
1939 },
1940 "flattened": true
1941 },
1942 "CompressionType": {
1943 "type": "string",
1944 "enum": [
1945 "NONE",
1946 "GZIP",
1947 "BZIP2"
1948 ]
1949 },
1950 "Condition": {
1951 "type": "structure",
1952 "members": {
1953 "HttpErrorCodeReturnedEquals": {
1954 "shape": "HttpErrorCodeReturnedEquals",
1955 "documentation": "<p>The HTTP error code when the redirect is applied. In the event of an error, if the error code equals this value, then the specified redirect is applied. Required when parent element <code>Condition</code> is specified and sibling <code>KeyPrefixEquals</code> is not specified. If both are specified, then both must be true for the redirect to be applied.</p>"
1956 },
1957 "KeyPrefixEquals": {
1958 "shape": "KeyPrefixEquals",
1959 "documentation": "<p>The object key name prefix when the redirect is applied. For example, to redirect requests for <code>ExamplePage.html</code>, the key prefix will be <code>ExamplePage.html</code>. To redirect request for all pages with the prefix <code>docs/</code>, the key prefix will be <code>/docs</code>, which identifies all objects in the <code>docs/</code> folder. Required when the parent element <code>Condition</code> is specified and sibling <code>HttpErrorCodeReturnedEquals</code> is not specified. If both conditions are specified, both must be true for the redirect to be applied.</p>"
1960 }
1961 },
1962 "documentation": "<p>A container for describing a condition that must be met for the specified redirect to apply. For example, 1. If request is for pages in the <code>/docs</code> folder, redirect to the <code>/documents</code> folder. 2. If request results in HTTP error 4xx, redirect request to another host where you might process the error.</p>"
1963 },
1964 "ConfirmRemoveSelfBucketAccess": {
1965 "type": "boolean"
1966 },
1967 "ContentDisposition": {
1968 "type": "string"
1969 },
1970 "ContentEncoding": {
1971 "type": "string"
1972 },
1973 "ContentLanguage": {
1974 "type": "string"
1975 },
1976 "ContentLength": {
1977 "type": "long"
1978 },
1979 "ContentMD5": {
1980 "type": "string"
1981 },
1982 "ContentRange": {
1983 "type": "string"
1984 },
1985 "ContentType": {
1986 "type": "string"
1987 },
1988 "ContinuationEvent": {
1989 "type": "structure",
1990 "members": {},
1991 "documentation": "<p/>",
1992 "event": true
1993 },
1994 "CopyObjectOutput": {
1995 "type": "structure",
1996 "members": {
1997 "CopyObjectResult": {
1998 "shape": "CopyObjectResult",
1999 "documentation": "<p>Container for all response elements.</p>"
2000 },
2001 "Expiration": {
2002 "shape": "Expiration",
2003 "documentation": "<p>If the object expiration is configured, the response includes this header.</p>",
2004 "location": "header",
2005 "locationName": "x-amz-expiration"
2006 },
2007 "CopySourceVersionId": {
2008 "shape": "CopySourceVersionId",
2009 "documentation": "<p>Version of the copied object in the destination bucket.</p>",
2010 "location": "header",
2011 "locationName": "x-amz-copy-source-version-id"
2012 },
2013 "VersionId": {
2014 "shape": "ObjectVersionId",
2015 "documentation": "<p>Version ID of the newly created copy.</p>",
2016 "location": "header",
2017 "locationName": "x-amz-version-id"
2018 },
2019 "ServerSideEncryption": {
2020 "shape": "ServerSideEncryption",
2021 "documentation": "<p>The server-side encryption algorithm used when storing this object in Amazon S3 (for example, AES256, aws:kms).</p>",
2022 "location": "header",
2023 "locationName": "x-amz-server-side-encryption"
2024 },
2025 "SSECustomerAlgorithm": {
2026 "shape": "SSECustomerAlgorithm",
2027 "documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the response will include this header confirming the encryption algorithm used.</p>",
2028 "location": "header",
2029 "locationName": "x-amz-server-side-encryption-customer-algorithm"
2030 },
2031 "SSECustomerKeyMD5": {
2032 "shape": "SSECustomerKeyMD5",
2033 "documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the response will include this header to provide round-trip message integrity verification of the customer-provided encryption key.</p>",
2034 "location": "header",
2035 "locationName": "x-amz-server-side-encryption-customer-key-MD5"
2036 },
2037 "SSEKMSKeyId": {
2038 "shape": "SSEKMSKeyId",
2039 "documentation": "<p>If present, specifies the ID of the AWS Key Management Service (AWS KMS) symmetric customer managed customer master key (CMK) that was used for the object.</p>",
2040 "location": "header",
2041 "locationName": "x-amz-server-side-encryption-aws-kms-key-id"
2042 },
2043 "SSEKMSEncryptionContext": {
2044 "shape": "SSEKMSEncryptionContext",
2045 "documentation": "<p>If present, specifies the AWS KMS Encryption Context to use for object encryption. The value of this header is a base64-encoded UTF-8 string holding JSON with the encryption context key-value pairs.</p>",
2046 "location": "header",
2047 "locationName": "x-amz-server-side-encryption-context"
2048 },
2049 "RequestCharged": {
2050 "shape": "RequestCharged",
2051 "location": "header",
2052 "locationName": "x-amz-request-charged"
2053 }
2054 },
2055 "payload": "CopyObjectResult"
2056 },
2057 "CopyObjectRequest": {
2058 "type": "structure",
2059 "required": [
2060 "Bucket",
2061 "CopySource",
2062 "Key"
2063 ],
2064 "members": {
2065 "ACL": {
2066 "shape": "ObjectCannedACL",
2067 "documentation": "<p>The canned ACL to apply to the object.</p>",
2068 "location": "header",
2069 "locationName": "x-amz-acl"
2070 },
2071 "Bucket": {
2072 "shape": "BucketName",
2073 "documentation": "<p>The name of the destination bucket.</p>",
2074 "location": "uri",
2075 "locationName": "Bucket"
2076 },
2077 "CacheControl": {
2078 "shape": "CacheControl",
2079 "documentation": "<p>Specifies caching behavior along the request/reply chain.</p>",
2080 "location": "header",
2081 "locationName": "Cache-Control"
2082 },
2083 "ContentDisposition": {
2084 "shape": "ContentDisposition",
2085 "documentation": "<p>Specifies presentational information for the object.</p>",
2086 "location": "header",
2087 "locationName": "Content-Disposition"
2088 },
2089 "ContentEncoding": {
2090 "shape": "ContentEncoding",
2091 "documentation": "<p>Specifies what content encodings have been applied to the object and thus what decoding mechanisms must be applied to obtain the media-type referenced by the Content-Type header field.</p>",
2092 "location": "header",
2093 "locationName": "Content-Encoding"
2094 },
2095 "ContentLanguage": {
2096 "shape": "ContentLanguage",
2097 "documentation": "<p>The language the content is in.</p>",
2098 "location": "header",
2099 "locationName": "Content-Language"
2100 },
2101 "ContentType": {
2102 "shape": "ContentType",
2103 "documentation": "<p>A standard MIME type describing the format of the object data.</p>",
2104 "location": "header",
2105 "locationName": "Content-Type"
2106 },
2107 "CopySource": {
2108 "shape": "CopySource",
2109 "documentation": "<p>The name of the source bucket and key name of the source object, separated by a slash (/). Must be URL-encoded.</p>",
2110 "location": "header",
2111 "locationName": "x-amz-copy-source"
2112 },
2113 "CopySourceIfMatch": {
2114 "shape": "CopySourceIfMatch",
2115 "documentation": "<p>Copies the object if its entity tag (ETag) matches the specified tag.</p>",
2116 "location": "header",
2117 "locationName": "x-amz-copy-source-if-match"
2118 },
2119 "CopySourceIfModifiedSince": {
2120 "shape": "CopySourceIfModifiedSince",
2121 "documentation": "<p>Copies the object if it has been modified since the specified time.</p>",
2122 "location": "header",
2123 "locationName": "x-amz-copy-source-if-modified-since"
2124 },
2125 "CopySourceIfNoneMatch": {
2126 "shape": "CopySourceIfNoneMatch",
2127 "documentation": "<p>Copies the object if its entity tag (ETag) is different than the specified ETag.</p>",
2128 "location": "header",
2129 "locationName": "x-amz-copy-source-if-none-match"
2130 },
2131 "CopySourceIfUnmodifiedSince": {
2132 "shape": "CopySourceIfUnmodifiedSince",
2133 "documentation": "<p>Copies the object if it hasn't been modified since the specified time.</p>",
2134 "location": "header",
2135 "locationName": "x-amz-copy-source-if-unmodified-since"
2136 },
2137 "Expires": {
2138 "shape": "Expires",
2139 "documentation": "<p>The date and time at which the object is no longer cacheable.</p>",
2140 "location": "header",
2141 "locationName": "Expires"
2142 },
2143 "GrantFullControl": {
2144 "shape": "GrantFullControl",
2145 "documentation": "<p>Gives the grantee READ, READ_ACP, and WRITE_ACP permissions on the object.</p>",
2146 "location": "header",
2147 "locationName": "x-amz-grant-full-control"
2148 },
2149 "GrantRead": {
2150 "shape": "GrantRead",
2151 "documentation": "<p>Allows grantee to read the object data and its metadata.</p>",
2152 "location": "header",
2153 "locationName": "x-amz-grant-read"
2154 },
2155 "GrantReadACP": {
2156 "shape": "GrantReadACP",
2157 "documentation": "<p>Allows grantee to read the object ACL.</p>",
2158 "location": "header",
2159 "locationName": "x-amz-grant-read-acp"
2160 },
2161 "GrantWriteACP": {
2162 "shape": "GrantWriteACP",
2163 "documentation": "<p>Allows grantee to write the ACL for the applicable object.</p>",
2164 "location": "header",
2165 "locationName": "x-amz-grant-write-acp"
2166 },
2167 "Key": {
2168 "shape": "ObjectKey",
2169 "documentation": "<p>The key of the destination object.</p>",
2170 "location": "uri",
2171 "locationName": "Key"
2172 },
2173 "Metadata": {
2174 "shape": "Metadata",
2175 "documentation": "<p>A map of metadata to store with the object in S3.</p>",
2176 "location": "headers",
2177 "locationName": "x-amz-meta-"
2178 },
2179 "MetadataDirective": {
2180 "shape": "MetadataDirective",
2181 "documentation": "<p>Specifies whether the metadata is copied from the source object or replaced with metadata provided in the request.</p>",
2182 "location": "header",
2183 "locationName": "x-amz-metadata-directive"
2184 },
2185 "TaggingDirective": {
2186 "shape": "TaggingDirective",
2187 "documentation": "<p>Specifies whether the object tag-set are copied from the source object or replaced with tag-set provided in the request.</p>",
2188 "location": "header",
2189 "locationName": "x-amz-tagging-directive"
2190 },
2191 "ServerSideEncryption": {
2192 "shape": "ServerSideEncryption",
2193 "documentation": "<p>The server-side encryption algorithm used when storing this object in Amazon S3 (for example, AES256, aws:kms).</p>",
2194 "location": "header",
2195 "locationName": "x-amz-server-side-encryption"
2196 },
2197 "StorageClass": {
2198 "shape": "StorageClass",
2199 "documentation": "<p>The type of storage to use for the object. Defaults to 'STANDARD'.</p>",
2200 "location": "header",
2201 "locationName": "x-amz-storage-class"
2202 },
2203 "WebsiteRedirectLocation": {
2204 "shape": "WebsiteRedirectLocation",
2205 "documentation": "<p>If the bucket is configured as a website, redirects requests for this object to another object in the same bucket or to an external URL. Amazon S3 stores the value of this header in the object metadata.</p>",
2206 "location": "header",
2207 "locationName": "x-amz-website-redirect-location"
2208 },
2209 "SSECustomerAlgorithm": {
2210 "shape": "SSECustomerAlgorithm",
2211 "documentation": "<p>Specifies the algorithm to use to when encrypting the object (for example, AES256).</p>",
2212 "location": "header",
2213 "locationName": "x-amz-server-side-encryption-customer-algorithm"
2214 },
2215 "SSECustomerKey": {
2216 "shape": "SSECustomerKey",
2217 "documentation": "<p>Specifies the customer-provided encryption key for Amazon S3 to use in encrypting data. This value is used to store the object and then it is discarded; Amazon S3 does not store the encryption key. The key must be appropriate for use with the algorithm specified in the <code>x-amz-server-side​-encryption​-customer-algorithm</code> header.</p>",
2218 "location": "header",
2219 "locationName": "x-amz-server-side-encryption-customer-key"
2220 },
2221 "SSECustomerKeyMD5": {
2222 "shape": "SSECustomerKeyMD5",
2223 "documentation": "<p>Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header for a message integrity check to ensure that the encryption key was transmitted without error.</p>",
2224 "location": "header",
2225 "locationName": "x-amz-server-side-encryption-customer-key-MD5"
2226 },
2227 "SSEKMSKeyId": {
2228 "shape": "SSEKMSKeyId",
2229 "documentation": "<p>Specifies the AWS KMS key ID to use for object encryption. All GET and PUT requests for an object protected by AWS KMS will fail if not made via SSL or using SigV4. For information about configuring using any of the officially supported AWS SDKs and AWS CLI, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version\">Specifying the Signature Version in Request Authentication</a> in the <i>Amazon S3 Developer Guide</i>.</p>",
2230 "location": "header",
2231 "locationName": "x-amz-server-side-encryption-aws-kms-key-id"
2232 },
2233 "SSEKMSEncryptionContext": {
2234 "shape": "SSEKMSEncryptionContext",
2235 "documentation": "<p>Specifies the AWS KMS Encryption Context to use for object encryption. The value of this header is a base64-encoded UTF-8 string holding JSON with the encryption context key-value pairs.</p>",
2236 "location": "header",
2237 "locationName": "x-amz-server-side-encryption-context"
2238 },
2239 "CopySourceSSECustomerAlgorithm": {
2240 "shape": "CopySourceSSECustomerAlgorithm",
2241 "documentation": "<p>Specifies the algorithm to use when decrypting the source object (for example, AES256).</p>",
2242 "location": "header",
2243 "locationName": "x-amz-copy-source-server-side-encryption-customer-algorithm"
2244 },
2245 "CopySourceSSECustomerKey": {
2246 "shape": "CopySourceSSECustomerKey",
2247 "documentation": "<p>Specifies the customer-provided encryption key for Amazon S3 to use to decrypt the source object. The encryption key provided in this header must be one that was used when the source object was created.</p>",
2248 "location": "header",
2249 "locationName": "x-amz-copy-source-server-side-encryption-customer-key"
2250 },
2251 "CopySourceSSECustomerKeyMD5": {
2252 "shape": "CopySourceSSECustomerKeyMD5",
2253 "documentation": "<p>Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header for a message integrity check to ensure that the encryption key was transmitted without error.</p>",
2254 "location": "header",
2255 "locationName": "x-amz-copy-source-server-side-encryption-customer-key-MD5"
2256 },
2257 "RequestPayer": {
2258 "shape": "RequestPayer",
2259 "location": "header",
2260 "locationName": "x-amz-request-payer"
2261 },
2262 "Tagging": {
2263 "shape": "TaggingHeader",
2264 "documentation": "<p>The tag-set for the object destination object this value must be used in conjunction with the <code>TaggingDirective</code>. The tag-set must be encoded as URL Query parameters.</p>",
2265 "location": "header",
2266 "locationName": "x-amz-tagging"
2267 },
2268 "ObjectLockMode": {
2269 "shape": "ObjectLockMode",
2270 "documentation": "<p>The Object Lock mode that you want to apply to the copied object.</p>",
2271 "location": "header",
2272 "locationName": "x-amz-object-lock-mode"
2273 },
2274 "ObjectLockRetainUntilDate": {
2275 "shape": "ObjectLockRetainUntilDate",
2276 "documentation": "<p>The date and time when you want the copied object's Object Lock to expire.</p>",
2277 "location": "header",
2278 "locationName": "x-amz-object-lock-retain-until-date"
2279 },
2280 "ObjectLockLegalHoldStatus": {
2281 "shape": "ObjectLockLegalHoldStatus",
2282 "documentation": "<p>Specifies whether you want to apply a Legal Hold to the copied object.</p>",
2283 "location": "header",
2284 "locationName": "x-amz-object-lock-legal-hold"
2285 }
2286 }
2287 },
2288 "CopyObjectResult": {
2289 "type": "structure",
2290 "members": {
2291 "ETag": {
2292 "shape": "ETag",
2293 "documentation": "<p>Returns the ETag of the new object. The ETag reflects only changes to the contents of an object, not its metadata. The source and destination ETag is identical for a successfully copied object.</p>"
2294 },
2295 "LastModified": {
2296 "shape": "LastModified",
2297 "documentation": "<p>Returns the date that the object was last modified.</p>"
2298 }
2299 },
2300 "documentation": "<p>Container for all response elements.</p>"
2301 },
2302 "CopyPartResult": {
2303 "type": "structure",
2304 "members": {
2305 "ETag": {
2306 "shape": "ETag",
2307 "documentation": "<p>Entity tag of the object.</p>"
2308 },
2309 "LastModified": {
2310 "shape": "LastModified",
2311 "documentation": "<p>Date and time at which the object was uploaded.</p>"
2312 }
2313 },
2314 "documentation": "<p>Container for all response elements.</p>"
2315 },
2316 "CopySource": {
2317 "type": "string",
2318 "pattern": "\\/.+\\/.+"
2319 },
2320 "CopySourceIfMatch": {
2321 "type": "string"
2322 },
2323 "CopySourceIfModifiedSince": {
2324 "type": "timestamp"
2325 },
2326 "CopySourceIfNoneMatch": {
2327 "type": "string"
2328 },
2329 "CopySourceIfUnmodifiedSince": {
2330 "type": "timestamp"
2331 },
2332 "CopySourceRange": {
2333 "type": "string"
2334 },
2335 "CopySourceSSECustomerAlgorithm": {
2336 "type": "string"
2337 },
2338 "CopySourceSSECustomerKey": {
2339 "type": "blob",
2340 "sensitive": true
2341 },
2342 "CopySourceSSECustomerKeyMD5": {
2343 "type": "string"
2344 },
2345 "CopySourceVersionId": {
2346 "type": "string"
2347 },
2348 "CreateBucketConfiguration": {
2349 "type": "structure",
2350 "members": {
2351 "LocationConstraint": {
2352 "shape": "BucketLocationConstraint",
2353 "documentation": "<p>Specifies the Region where the bucket will be created. If you don't specify a Region, the bucket is created in the US East (N. Virginia) Region (us-east-1).</p>"
2354 }
2355 },
2356 "documentation": "<p>The configuration information for the bucket.</p>"
2357 },
2358 "CreateBucketOutput": {
2359 "type": "structure",
2360 "members": {
2361 "Location": {
2362 "shape": "Location",
2363 "documentation": "<p>Specifies the Region where the bucket will be created. If you are creating a bucket on the US East (N. Virginia) Region (us-east-1), you do not need to specify the location.</p>",
2364 "location": "header",
2365 "locationName": "Location"
2366 }
2367 }
2368 },
2369 "CreateBucketRequest": {
2370 "type": "structure",
2371 "required": [
2372 "Bucket"
2373 ],
2374 "members": {
2375 "ACL": {
2376 "shape": "BucketCannedACL",
2377 "documentation": "<p>The canned ACL to apply to the bucket.</p>",
2378 "location": "header",
2379 "locationName": "x-amz-acl"
2380 },
2381 "Bucket": {
2382 "shape": "BucketName",
2383 "documentation": "<p>The name of the bucket to create.</p>",
2384 "location": "uri",
2385 "locationName": "Bucket"
2386 },
2387 "CreateBucketConfiguration": {
2388 "shape": "CreateBucketConfiguration",
2389 "documentation": "<p>The configuration information for the bucket.</p>",
2390 "locationName": "CreateBucketConfiguration",
2391 "xmlNamespace": {
2392 "uri": "http://s3.amazonaws.com/doc/2006-03-01/"
2393 }
2394 },
2395 "GrantFullControl": {
2396 "shape": "GrantFullControl",
2397 "documentation": "<p>Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.</p>",
2398 "location": "header",
2399 "locationName": "x-amz-grant-full-control"
2400 },
2401 "GrantRead": {
2402 "shape": "GrantRead",
2403 "documentation": "<p>Allows grantee to list the objects in the bucket.</p>",
2404 "location": "header",
2405 "locationName": "x-amz-grant-read"
2406 },
2407 "GrantReadACP": {
2408 "shape": "GrantReadACP",
2409 "documentation": "<p>Allows grantee to read the bucket ACL.</p>",
2410 "location": "header",
2411 "locationName": "x-amz-grant-read-acp"
2412 },
2413 "GrantWrite": {
2414 "shape": "GrantWrite",
2415 "documentation": "<p>Allows grantee to create, overwrite, and delete any object in the bucket.</p>",
2416 "location": "header",
2417 "locationName": "x-amz-grant-write"
2418 },
2419 "GrantWriteACP": {
2420 "shape": "GrantWriteACP",
2421 "documentation": "<p>Allows grantee to write the ACL for the applicable bucket.</p>",
2422 "location": "header",
2423 "locationName": "x-amz-grant-write-acp"
2424 },
2425 "ObjectLockEnabledForBucket": {
2426 "shape": "ObjectLockEnabledForBucket",
2427 "documentation": "<p>Specifies whether you want S3 Object Lock to be enabled for the new bucket.</p>",
2428 "location": "header",
2429 "locationName": "x-amz-bucket-object-lock-enabled"
2430 }
2431 },
2432 "payload": "CreateBucketConfiguration"
2433 },
2434 "CreateMultipartUploadOutput": {
2435 "type": "structure",
2436 "members": {
2437 "AbortDate": {
2438 "shape": "AbortDate",
2439 "documentation": "<p>If the bucket has a lifecycle rule configured with an action to abort incomplete multipart uploads and the prefix in the lifecycle rule matches the object name in the request, the response includes this header. The header indicates when the initiated multipart upload becomes eligible for an abort operation. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config\"> Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle Policy</a>.</p> <p>The response also includes the <code>x-amz-abort-rule-id</code> header that provides the ID of the lifecycle configuration rule that defines this action.</p>",
2440 "location": "header",
2441 "locationName": "x-amz-abort-date"
2442 },
2443 "AbortRuleId": {
2444 "shape": "AbortRuleId",
2445 "documentation": "<p>This header is returned along with the <code>x-amz-abort-date</code> header. It identifies the applicable lifecycle configuration rule that defines the action to abort incomplete multipart uploads.</p>",
2446 "location": "header",
2447 "locationName": "x-amz-abort-rule-id"
2448 },
2449 "Bucket": {
2450 "shape": "BucketName",
2451 "documentation": "<p>Name of the bucket to which the multipart upload was initiated. </p> <p>When using this API with an access point, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this operation using an access point through the AWS SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-access-points.html\">Using Access Points</a> in the <i>Amazon Simple Storage Service Developer Guide</i>.</p>",
2452 "locationName": "Bucket"
2453 },
2454 "Key": {
2455 "shape": "ObjectKey",
2456 "documentation": "<p>Object key for which the multipart upload was initiated.</p>"
2457 },
2458 "UploadId": {
2459 "shape": "MultipartUploadId",
2460 "documentation": "<p>ID for the initiated multipart upload.</p>"
2461 },
2462 "ServerSideEncryption": {
2463 "shape": "ServerSideEncryption",
2464 "documentation": "<p>The server-side encryption algorithm used when storing this object in Amazon S3 (for example, AES256, aws:kms).</p>",
2465 "location": "header",
2466 "locationName": "x-amz-server-side-encryption"
2467 },
2468 "SSECustomerAlgorithm": {
2469 "shape": "SSECustomerAlgorithm",
2470 "documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the response will include this header confirming the encryption algorithm used.</p>",
2471 "location": "header",
2472 "locationName": "x-amz-server-side-encryption-customer-algorithm"
2473 },
2474 "SSECustomerKeyMD5": {
2475 "shape": "SSECustomerKeyMD5",
2476 "documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the response will include this header to provide round-trip message integrity verification of the customer-provided encryption key.</p>",
2477 "location": "header",
2478 "locationName": "x-amz-server-side-encryption-customer-key-MD5"
2479 },
2480 "SSEKMSKeyId": {
2481 "shape": "SSEKMSKeyId",
2482 "documentation": "<p>If present, specifies the ID of the AWS Key Management Service (AWS KMS) symmetric customer managed customer master key (CMK) that was used for the object.</p>",
2483 "location": "header",
2484 "locationName": "x-amz-server-side-encryption-aws-kms-key-id"
2485 },
2486 "SSEKMSEncryptionContext": {
2487 "shape": "SSEKMSEncryptionContext",
2488 "documentation": "<p>If present, specifies the AWS KMS Encryption Context to use for object encryption. The value of this header is a base64-encoded UTF-8 string holding JSON with the encryption context key-value pairs.</p>",
2489 "location": "header",
2490 "locationName": "x-amz-server-side-encryption-context"
2491 },
2492 "RequestCharged": {
2493 "shape": "RequestCharged",
2494 "location": "header",
2495 "locationName": "x-amz-request-charged"
2496 }
2497 }
2498 },
2499 "CreateMultipartUploadRequest": {
2500 "type": "structure",
2501 "required": [
2502 "Bucket",
2503 "Key"
2504 ],
2505 "members": {
2506 "ACL": {
2507 "shape": "ObjectCannedACL",
2508 "documentation": "<p>The canned ACL to apply to the object.</p>",
2509 "location": "header",
2510 "locationName": "x-amz-acl"
2511 },
2512 "Bucket": {
2513 "shape": "BucketName",
2514 "documentation": "<p>The name of the bucket to which to initiate the upload</p>",
2515 "location": "uri",
2516 "locationName": "Bucket"
2517 },
2518 "CacheControl": {
2519 "shape": "CacheControl",
2520 "documentation": "<p>Specifies caching behavior along the request/reply chain.</p>",
2521 "location": "header",
2522 "locationName": "Cache-Control"
2523 },
2524 "ContentDisposition": {
2525 "shape": "ContentDisposition",
2526 "documentation": "<p>Specifies presentational information for the object.</p>",
2527 "location": "header",
2528 "locationName": "Content-Disposition"
2529 },
2530 "ContentEncoding": {
2531 "shape": "ContentEncoding",
2532 "documentation": "<p>Specifies what content encodings have been applied to the object and thus what decoding mechanisms must be applied to obtain the media-type referenced by the Content-Type header field.</p>",
2533 "location": "header",
2534 "locationName": "Content-Encoding"
2535 },
2536 "ContentLanguage": {
2537 "shape": "ContentLanguage",
2538 "documentation": "<p>The language the content is in.</p>",
2539 "location": "header",
2540 "locationName": "Content-Language"
2541 },
2542 "ContentType": {
2543 "shape": "ContentType",
2544 "documentation": "<p>A standard MIME type describing the format of the object data.</p>",
2545 "location": "header",
2546 "locationName": "Content-Type"
2547 },
2548 "Expires": {
2549 "shape": "Expires",
2550 "documentation": "<p>The date and time at which the object is no longer cacheable.</p>",
2551 "location": "header",
2552 "locationName": "Expires"
2553 },
2554 "GrantFullControl": {
2555 "shape": "GrantFullControl",
2556 "documentation": "<p>Gives the grantee READ, READ_ACP, and WRITE_ACP permissions on the object.</p>",
2557 "location": "header",
2558 "locationName": "x-amz-grant-full-control"
2559 },
2560 "GrantRead": {
2561 "shape": "GrantRead",
2562 "documentation": "<p>Allows grantee to read the object data and its metadata.</p>",
2563 "location": "header",
2564 "locationName": "x-amz-grant-read"
2565 },
2566 "GrantReadACP": {
2567 "shape": "GrantReadACP",
2568 "documentation": "<p>Allows grantee to read the object ACL.</p>",
2569 "location": "header",
2570 "locationName": "x-amz-grant-read-acp"
2571 },
2572 "GrantWriteACP": {
2573 "shape": "GrantWriteACP",
2574 "documentation": "<p>Allows grantee to write the ACL for the applicable object.</p>",
2575 "location": "header",
2576 "locationName": "x-amz-grant-write-acp"
2577 },
2578 "Key": {
2579 "shape": "ObjectKey",
2580 "documentation": "<p>Object key for which the multipart upload is to be initiated.</p>",
2581 "location": "uri",
2582 "locationName": "Key"
2583 },
2584 "Metadata": {
2585 "shape": "Metadata",
2586 "documentation": "<p>A map of metadata to store with the object in S3.</p>",
2587 "location": "headers",
2588 "locationName": "x-amz-meta-"
2589 },
2590 "ServerSideEncryption": {
2591 "shape": "ServerSideEncryption",
2592 "documentation": "<p>The server-side encryption algorithm used when storing this object in Amazon S3 (for example, AES256, aws:kms).</p>",
2593 "location": "header",
2594 "locationName": "x-amz-server-side-encryption"
2595 },
2596 "StorageClass": {
2597 "shape": "StorageClass",
2598 "documentation": "<p>The type of storage to use for the object. Defaults to 'STANDARD'.</p>",
2599 "location": "header",
2600 "locationName": "x-amz-storage-class"
2601 },
2602 "WebsiteRedirectLocation": {
2603 "shape": "WebsiteRedirectLocation",
2604 "documentation": "<p>If the bucket is configured as a website, redirects requests for this object to another object in the same bucket or to an external URL. Amazon S3 stores the value of this header in the object metadata.</p>",
2605 "location": "header",
2606 "locationName": "x-amz-website-redirect-location"
2607 },
2608 "SSECustomerAlgorithm": {
2609 "shape": "SSECustomerAlgorithm",
2610 "documentation": "<p>Specifies the algorithm to use to when encrypting the object (for example, AES256).</p>",
2611 "location": "header",
2612 "locationName": "x-amz-server-side-encryption-customer-algorithm"
2613 },
2614 "SSECustomerKey": {
2615 "shape": "SSECustomerKey",
2616 "documentation": "<p>Specifies the customer-provided encryption key for Amazon S3 to use in encrypting data. This value is used to store the object and then it is discarded; Amazon S3 does not store the encryption key. The key must be appropriate for use with the algorithm specified in the <code>x-amz-server-side​-encryption​-customer-algorithm</code> header.</p>",
2617 "location": "header",
2618 "locationName": "x-amz-server-side-encryption-customer-key"
2619 },
2620 "SSECustomerKeyMD5": {
2621 "shape": "SSECustomerKeyMD5",
2622 "documentation": "<p>Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header for a message integrity check to ensure that the encryption key was transmitted without error.</p>",
2623 "location": "header",
2624 "locationName": "x-amz-server-side-encryption-customer-key-MD5"
2625 },
2626 "SSEKMSKeyId": {
2627 "shape": "SSEKMSKeyId",
2628 "documentation": "<p>Specifies the ID of the symmetric customer managed AWS KMS CMK to use for object encryption. All GET and PUT requests for an object protected by AWS KMS will fail if not made via SSL or using SigV4. For information about configuring using any of the officially supported AWS SDKs and AWS CLI, see <a href=\"https://docs.aws.amazon.com/http:/docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version\">Specifying the Signature Version in Request Authentication</a> in the <i>Amazon S3 Developer Guide</i>.</p>",
2629 "location": "header",
2630 "locationName": "x-amz-server-side-encryption-aws-kms-key-id"
2631 },
2632 "SSEKMSEncryptionContext": {
2633 "shape": "SSEKMSEncryptionContext",
2634 "documentation": "<p>Specifies the AWS KMS Encryption Context to use for object encryption. The value of this header is a base64-encoded UTF-8 string holding JSON with the encryption context key-value pairs.</p>",
2635 "location": "header",
2636 "locationName": "x-amz-server-side-encryption-context"
2637 },
2638 "RequestPayer": {
2639 "shape": "RequestPayer",
2640 "location": "header",
2641 "locationName": "x-amz-request-payer"
2642 },
2643 "Tagging": {
2644 "shape": "TaggingHeader",
2645 "documentation": "<p>The tag-set for the object. The tag-set must be encoded as URL Query parameters.</p>",
2646 "location": "header",
2647 "locationName": "x-amz-tagging"
2648 },
2649 "ObjectLockMode": {
2650 "shape": "ObjectLockMode",
2651 "documentation": "<p>Specifies the Object Lock mode that you want to apply to the uploaded object.</p>",
2652 "location": "header",
2653 "locationName": "x-amz-object-lock-mode"
2654 },
2655 "ObjectLockRetainUntilDate": {
2656 "shape": "ObjectLockRetainUntilDate",
2657 "documentation": "<p>Specifies the date and time when you want the Object Lock to expire.</p>",
2658 "location": "header",
2659 "locationName": "x-amz-object-lock-retain-until-date"
2660 },
2661 "ObjectLockLegalHoldStatus": {
2662 "shape": "ObjectLockLegalHoldStatus",
2663 "documentation": "<p>Specifies whether you want to apply a Legal Hold to the uploaded object.</p>",
2664 "location": "header",
2665 "locationName": "x-amz-object-lock-legal-hold"
2666 }
2667 }
2668 },
2669 "CreationDate": {
2670 "type": "timestamp"
2671 },
2672 "Date": {
2673 "type": "timestamp",
2674 "timestampFormat": "iso8601"
2675 },
2676 "Days": {
2677 "type": "integer"
2678 },
2679 "DaysAfterInitiation": {
2680 "type": "integer"
2681 },
2682 "DefaultRetention": {
2683 "type": "structure",
2684 "members": {
2685 "Mode": {
2686 "shape": "ObjectLockRetentionMode",
2687 "documentation": "<p>The default Object Lock retention mode you want to apply to new objects placed in the specified bucket.</p>"
2688 },
2689 "Days": {
2690 "shape": "Days",
2691 "documentation": "<p>The number of days that you want to specify for the default retention period.</p>"
2692 },
2693 "Years": {
2694 "shape": "Years",
2695 "documentation": "<p>The number of years that you want to specify for the default retention period.</p>"
2696 }
2697 },
2698 "documentation": "<p>The container element for specifying the default Object Lock retention settings for new objects placed in the specified bucket.</p>"
2699 },
2700 "Delete": {
2701 "type": "structure",
2702 "required": [
2703 "Objects"
2704 ],
2705 "members": {
2706 "Objects": {
2707 "shape": "ObjectIdentifierList",
2708 "documentation": "<p>The objects to delete.</p>",
2709 "locationName": "Object"
2710 },
2711 "Quiet": {
2712 "shape": "Quiet",
2713 "documentation": "<p>Element to enable quiet mode for the request. When you add this element, you must set its value to true.</p>"
2714 }
2715 },
2716 "documentation": "<p>Container for the objects to delete.</p>"
2717 },
2718 "DeleteBucketAnalyticsConfigurationRequest": {
2719 "type": "structure",
2720 "required": [
2721 "Bucket",
2722 "Id"
2723 ],
2724 "members": {
2725 "Bucket": {
2726 "shape": "BucketName",
2727 "documentation": "<p>The name of the bucket from which an analytics configuration is deleted.</p>",
2728 "location": "uri",
2729 "locationName": "Bucket"
2730 },
2731 "Id": {
2732 "shape": "AnalyticsId",
2733 "documentation": "<p>The ID that identifies the analytics configuration.</p>",
2734 "location": "querystring",
2735 "locationName": "id"
2736 }
2737 }
2738 },
2739 "DeleteBucketCorsRequest": {
2740 "type": "structure",
2741 "required": [
2742 "Bucket"
2743 ],
2744 "members": {
2745 "Bucket": {
2746 "shape": "BucketName",
2747 "documentation": "<p>Specifies the bucket whose <code>cors</code> configuration is being deleted.</p>",
2748 "location": "uri",
2749 "locationName": "Bucket"
2750 }
2751 }
2752 },
2753 "DeleteBucketEncryptionRequest": {
2754 "type": "structure",
2755 "required": [
2756 "Bucket"
2757 ],
2758 "members": {
2759 "Bucket": {
2760 "shape": "BucketName",
2761 "documentation": "<p>The name of the bucket containing the server-side encryption configuration to delete.</p>",
2762 "location": "uri",
2763 "locationName": "Bucket"
2764 }
2765 }
2766 },
2767 "DeleteBucketInventoryConfigurationRequest": {
2768 "type": "structure",
2769 "required": [
2770 "Bucket",
2771 "Id"
2772 ],
2773 "members": {
2774 "Bucket": {
2775 "shape": "BucketName",
2776 "documentation": "<p>The name of the bucket containing the inventory configuration to delete.</p>",
2777 "location": "uri",
2778 "locationName": "Bucket"
2779 },
2780 "Id": {
2781 "shape": "InventoryId",
2782 "documentation": "<p>The ID used to identify the inventory configuration.</p>",
2783 "location": "querystring",
2784 "locationName": "id"
2785 }
2786 }
2787 },
2788 "DeleteBucketLifecycleRequest": {
2789 "type": "structure",
2790 "required": [
2791 "Bucket"
2792 ],
2793 "members": {
2794 "Bucket": {
2795 "shape": "BucketName",
2796 "documentation": "<p>The bucket name of the lifecycle to delete.</p>",
2797 "location": "uri",
2798 "locationName": "Bucket"
2799 }
2800 }
2801 },
2802 "DeleteBucketMetricsConfigurationRequest": {
2803 "type": "structure",
2804 "required": [
2805 "Bucket",
2806 "Id"
2807 ],
2808 "members": {
2809 "Bucket": {
2810 "shape": "BucketName",
2811 "documentation": "<p>The name of the bucket containing the metrics configuration to delete.</p>",
2812 "location": "uri",
2813 "locationName": "Bucket"
2814 },
2815 "Id": {
2816 "shape": "MetricsId",
2817 "documentation": "<p>The ID used to identify the metrics configuration.</p>",
2818 "location": "querystring",
2819 "locationName": "id"
2820 }
2821 }
2822 },
2823 "DeleteBucketPolicyRequest": {
2824 "type": "structure",
2825 "required": [
2826 "Bucket"
2827 ],
2828 "members": {
2829 "Bucket": {
2830 "shape": "BucketName",
2831 "documentation": "<p>The bucket name.</p>",
2832 "location": "uri",
2833 "locationName": "Bucket"
2834 }
2835 }
2836 },
2837 "DeleteBucketReplicationRequest": {
2838 "type": "structure",
2839 "required": [
2840 "Bucket"
2841 ],
2842 "members": {
2843 "Bucket": {
2844 "shape": "BucketName",
2845 "documentation": "<p> The bucket name. </p>",
2846 "location": "uri",
2847 "locationName": "Bucket"
2848 }
2849 }
2850 },
2851 "DeleteBucketRequest": {
2852 "type": "structure",
2853 "required": [
2854 "Bucket"
2855 ],
2856 "members": {
2857 "Bucket": {
2858 "shape": "BucketName",
2859 "documentation": "<p>Specifies the bucket being deleted.</p>",
2860 "location": "uri",
2861 "locationName": "Bucket"
2862 }
2863 }
2864 },
2865 "DeleteBucketTaggingRequest": {
2866 "type": "structure",
2867 "required": [
2868 "Bucket"
2869 ],
2870 "members": {
2871 "Bucket": {
2872 "shape": "BucketName",
2873 "documentation": "<p>The bucket that has the tag set to be removed.</p>",
2874 "location": "uri",
2875 "locationName": "Bucket"
2876 }
2877 }
2878 },
2879 "DeleteBucketWebsiteRequest": {
2880 "type": "structure",
2881 "required": [
2882 "Bucket"
2883 ],
2884 "members": {
2885 "Bucket": {
2886 "shape": "BucketName",
2887 "documentation": "<p>The bucket name for which you want to remove the website configuration. </p>",
2888 "location": "uri",
2889 "locationName": "Bucket"
2890 }
2891 }
2892 },
2893 "DeleteMarker": {
2894 "type": "boolean"
2895 },
2896 "DeleteMarkerEntry": {
2897 "type": "structure",
2898 "members": {
2899 "Owner": {
2900 "shape": "Owner",
2901 "documentation": "<p>The account that created the delete marker.&gt;</p>"
2902 },
2903 "Key": {
2904 "shape": "ObjectKey",
2905 "documentation": "<p>The object key.</p>"
2906 },
2907 "VersionId": {
2908 "shape": "ObjectVersionId",
2909 "documentation": "<p>Version ID of an object.</p>"
2910 },
2911 "IsLatest": {
2912 "shape": "IsLatest",
2913 "documentation": "<p>Specifies whether the object is (true) or is not (false) the latest version of an object.</p>"
2914 },
2915 "LastModified": {
2916 "shape": "LastModified",
2917 "documentation": "<p>Date and time the object was last modified.</p>"
2918 }
2919 },
2920 "documentation": "<p>Information about the delete marker.</p>"
2921 },
2922 "DeleteMarkerReplication": {
2923 "type": "structure",
2924 "members": {
2925 "Status": {
2926 "shape": "DeleteMarkerReplicationStatus",
2927 "documentation": "<p>Indicates whether to replicate delete markers.</p> <note> <p> In the current implementation, Amazon S3 doesn't replicate the delete markers. The status must be <code>Disabled</code>. </p> </note>"
2928 }
2929 },
2930 "documentation": "<p>Specifies whether Amazon S3 replicates the delete markers. If you specify a <code>Filter</code>, you must specify this element. However, in the latest version of replication configuration (when <code>Filter</code> is specified), Amazon S3 doesn't replicate delete markers. Therefore, the <code>DeleteMarkerReplication</code> element can contain only &lt;Status&gt;Disabled&lt;/Status&gt;. For an example configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/replication-add-config.html#replication-config-min-rule-config\">Basic Rule Configuration</a>. </p> <note> <p> If you don't specify the <code>Filter</code> element, Amazon S3 assumes that the replication configuration is the earlier version, V1. In the earlier version, Amazon S3 handled replication of delete markers differently. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/replication-add-config.html#replication-backward-compat-considerations\">Backward Compatibility</a>.</p> </note>"
2931 },
2932 "DeleteMarkerReplicationStatus": {
2933 "type": "string",