AbortMultipartUpload:
/// Bad
/// Request error. For more information about transfer acceleration, see Transfer
/// Acceleration.
/// Etag
/// matches or whether the object was modified before or after a specified date, use the
/// request parameters x-amz-copy-source-if-match, x-amz-copy-source-if-none-match,
/// x-amz-copy-source-if-unmodified-since, or x-amz-copy-source-if-modified-since.
/// x-amz- prefix, including x-amz-copy-source,
/// must be signed.
/// StorageClass parameter. For more information,
/// see Storage
/// Classes.
/// 200 OK response. This means that
/// a 200 OK response can contain either a success or an error. Design your
/// application to parse the contents of the response and handle it appropriately.
/// x-amz-copy-source-if-match and x-amz-copy-source-if-unmodified-since
/// headers are present in the request and evaluate as follows, Amazon S3 returns 200
/// OK and copies the data:
/// x-amz-copy-source-if-match condition evaluates to true
/// x-amz-copy-source-if-unmodified-since condition evaluates to false
/// x-amz-copy-source-if-none-match and
/// x-amz-copy-source-if-modified-since headers are present in the request
/// and evaluate as follows, Amazon S3 returns the 412 Precondition Failed
/// response code:
/// x-amz-copy-source-if-none-match condition evaluates to false
/// x-amz-copy-source-if-modified-since condition evaluates to true
/// CopyObject:
/// x-amz-copy-source 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 versionId subresource.
/// x-amz-version-id
/// response header in the response.
/// x-amz-acl request header. For more information,
/// see Canned
/// ACL.
/// x-amz-grant-read, x-amz-grant-read-acp,
/// x-amz-grant-write-acp, and x-amz-grant-full-control headers.
/// These parameters map to the set of permissions that Amazon S3 supports in an ACL.
/// For more information, see Access
/// Control List (ACL) Overview.
/// x-amz-server-side-encryption
/// x-amz-server-side-encryption-aws-kms-key-id
/// x-amz-server-side-encryption-context
/// x-amz-server-side-encryption:aws:kms, but don't provide
/// x-amz-server-side-encryption-aws-kms-key-id, 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 x-amz-server-side-encryption-aws-kms-key-id
/// of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and
/// not asymmetric CMKs. For more information, see Using
/// Symmetric and Asymmetric Keys in the AWS Key Management Service Developer Guide.
/// x-amz-acl) — 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 Canned
/// ACL.
/// emailAddress – if the value specified is the email address of an AWS
/// account
/// id – if the value specified is the canonical user ID of an AWS account
/// uri – if you are granting permissions to a predefined group
/// x-amz-grant-read header grants the AWS accounts
/// identified by email addresses permissions to read object data and its metadata:
/// x-amz-grant-read: emailAddress="xyz@amazon.com", emailAddress="abc@amazon.com"
///
/// CopyObject:
/// Bad
/// Request error. For more information about transfer acceleration, see Transfer
/// Acceleration.
/// Etag
/// matches or whether the object was modified before or after a specified date, use the
/// request parameters x-amz-copy-source-if-match, x-amz-copy-source-if-none-match,
/// x-amz-copy-source-if-unmodified-since, or x-amz-copy-source-if-modified-since.
/// x-amz- prefix, including x-amz-copy-source,
/// must be signed.
/// StorageClass parameter. For more information,
/// see Storage
/// Classes.
/// 200 OK response. This means that
/// a 200 OK response can contain either a success or an error. Design your
/// application to parse the contents of the response and handle it appropriately.
/// x-amz-copy-source-if-match and x-amz-copy-source-if-unmodified-since
/// headers are present in the request and evaluate as follows, Amazon S3 returns 200
/// OK and copies the data:
/// x-amz-copy-source-if-match condition evaluates to true
/// x-amz-copy-source-if-unmodified-since condition evaluates to false
/// x-amz-copy-source-if-none-match and
/// x-amz-copy-source-if-modified-since headers are present in the request
/// and evaluate as follows, Amazon S3 returns the 412 Precondition Failed
/// response code:
/// x-amz-copy-source-if-none-match condition evaluates to false
/// x-amz-copy-source-if-modified-since condition evaluates to true
/// CopyObject:
/// x-amz-copy-source 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 versionId subresource.
/// x-amz-version-id
/// response header in the response.
/// x-amz-acl request header. For more information,
/// see Canned
/// ACL.
/// x-amz-grant-read, x-amz-grant-read-acp,
/// x-amz-grant-write-acp, and x-amz-grant-full-control headers.
/// These parameters map to the set of permissions that Amazon S3 supports in an ACL.
/// For more information, see Access
/// Control List (ACL) Overview.
/// x-amz-server-side-encryption
/// x-amz-server-side-encryption-aws-kms-key-id
/// x-amz-server-side-encryption-context
/// x-amz-server-side-encryption:aws:kms, but don't provide
/// x-amz-server-side-encryption-aws-kms-key-id, 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 x-amz-server-side-encryption-aws-kms-key-id
/// of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and
/// not asymmetric CMKs. For more information, see Using
/// Symmetric and Asymmetric Keys in the AWS Key Management Service Developer Guide.
/// x-amz-acl) — 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 Canned
/// ACL.
/// emailAddress – if the value specified is the email address of an AWS
/// account
/// id – if the value specified is the canonical user ID of an AWS account
/// uri – if you are granting permissions to a predefined group
/// x-amz-grant-read header grants the AWS accounts
/// identified by email addresses permissions to read object data and its metadata:
/// x-amz-grant-read: emailAddress="xyz@amazon.com", emailAddress="abc@amazon.com"
///
/// CopyObject:
/// x-amz-copy-source in your
/// request and a byte range by adding the request header x-amz-copy-source-range
/// in your request.
///
///
/// UploadPartCopy operation, see the
/// following:
/// x-amz-copy-source-if-match,
/// x-amz-copy-source-if-none-match, x-amz-copy-source-if-unmodified-since,
/// and x-amz-copy-source-if-modified-since:
/// x-amz-copy-source-if-match and
/// x-amz-copy-source-if-unmodified-since headers are present in the request
/// as follows:
/// x-amz-copy-source-if-match condition evaluates to true,
/// and;
/// x-amz-copy-source-if-unmodified-since condition evaluates to false;
/// 200 OK and copies the data.
/// x-amz-copy-source-if-none-match
/// and x-amz-copy-source-if-modified-since headers are present in the request
/// as follows:
/// x-amz-copy-source-if-none-match condition evaluates to false,
/// and;
/// x-amz-copy-source-if-modified-since condition evaluates to true;
/// 412 Precondition Failed response code.
/// x-amz-copy-source 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 x-amz-copy-source, Amazon S3 returns a 404 error,
/// because the object does not exist. If you specify versionId in the x-amz-copy-source
/// 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 x-amz-copy-source.
///
/// versionId subresource as shown in the following example:
/// x-amz-copy-source: /bucket/object?versionId=version id
/// Special Errors /// ///
/// ///
/// ///
Related Resources /// ///
x-amz-copy-source in your
/// request and a byte range by adding the request header x-amz-copy-source-range
/// in your request.
///
///
/// UploadPartCopy operation, see the
/// following:
/// x-amz-copy-source-if-match,
/// x-amz-copy-source-if-none-match, x-amz-copy-source-if-unmodified-since,
/// and x-amz-copy-source-if-modified-since:
/// x-amz-copy-source-if-match and
/// x-amz-copy-source-if-unmodified-since headers are present in the request
/// as follows:
/// x-amz-copy-source-if-match condition evaluates to true,
/// and;
/// x-amz-copy-source-if-unmodified-since condition evaluates to false;
/// 200 OK and copies the data.
/// x-amz-copy-source-if-none-match
/// and x-amz-copy-source-if-modified-since headers are present in the request
/// as follows:
/// x-amz-copy-source-if-none-match condition evaluates to false,
/// and;
/// x-amz-copy-source-if-modified-since condition evaluates to true;
/// 412 Precondition Failed response code.
/// x-amz-copy-source 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 x-amz-copy-source, Amazon S3 returns a 404 error,
/// because the object does not exist. If you specify versionId in the x-amz-copy-source
/// 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 x-amz-copy-source.
///
/// versionId subresource as shown in the following example:
/// x-amz-copy-source: /bucket/object?versionId=version id
/// Special Errors /// ///
/// ///
/// ///
Related Resources /// ///
Related Resources /// ///
DeleteBucketPolicy
/// permissions on the specified bucket and belong to the bucket owner's account to use
/// this operation.
///
///
/// DeleteBucketPolicy permissions, Amazon S3 returns a
/// 403 Access Denied 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 405 Method Not Allowed error.
/// DeleteBucketPolicy
/// s3:PutBucketTagging
/// action. By default, the bucket owner has this permission and can grant this permission
/// to others.
/// DeleteBucketTagging:
/// 200 OK response upon successfully deleting a website configuration on
/// the specified bucket. You will get a 200 OK response if the website configuration
/// you are trying to delete does not exist on the bucket. Amazon S3 returns a 404
/// response if the bucket specified in the request does not exist.
///
///
/// S3:DeleteBucketWebsite 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 S3:DeleteBucketWebsite
/// permission.
/// DeleteBucketWebsite:
/// cors configuration information set for the bucket.
///
///
/// s3:PutBucketCORS
/// action. The bucket owner has this permission by default and can grant this permission
/// to others.
/// cors, see Enabling
/// Cross-Origin Resource Sharing in the Amazon Simple Storage Service Developer
/// Guide.
/// Related Resources: /// ///
cors configuration is being deleted.
/// An Action delegate that is invoked when the operation completes.
///
/// A user-defined state object that is passed to the callback procedure. Retrieve this object from within the callback
/// procedure using the AsyncState property.
///
///
/// s3:PutLifecycleConfiguration
/// action. By default, the bucket owner has this permission and the bucket owner can
/// grant this permission to others.
/// x-amz-delete-marker,
/// to true.
/// x-amz-mfa request header
/// in the DELETE versionId request. Requests that include x-amz-mfa
/// must use HTTPS.
/// s3:DeleteObject, s3:DeleteObjectVersion,
/// and s3:PutLifeCycleConfiguration actions.
/// DeleteObject:
/// x-amz-delete-marker,
/// to true.
/// x-amz-mfa request header
/// in the DELETE versionId request. Requests that include x-amz-mfa
/// must use HTTPS.
/// s3:DeleteObject, s3:DeleteObjectVersion,
/// and s3:PutLifeCycleConfiguration actions.
/// DeleteObject:
/// GET operation uses the acl subresource
/// to return the access control list (ACL) of a bucket. To use GET to return
/// the ACL of the bucket, you must have READ_ACP access to the bucket. If
/// READ_ACP permission is granted to the anonymous user, you can return
/// the ACL of the bucket without using an authorization header.
///
/// Related Resources /// ///
accelerate subresource
/// to return the Transfer Acceleration state of a bucket, which is either Enabled
/// or Suspended. Amazon S3 Transfer Acceleration is a bucket-level feature
/// that enables you to perform faster data transfers to and from Amazon S3.
///
///
/// s3:GetAccelerateConfiguration
/// action. The bucket owner has this permission by default. The bucket owner can grant
/// this permission to others. For more information about permissions, see Permissions
/// Related to Bucket Subresource Operations and Managing
/// Access Permissions to your Amazon S3 Resources in the Amazon Simple Storage
/// Service Developer Guide.
/// Enabled
/// or Suspended by using the PutBucketAccelerateConfiguration operation.
///
/// accelerate 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.
/// Related Resources /// ///
LocationConstraint
/// request parameter in a CreateBucket request. For more information, see
/// CreateBucket.
///
///
/// GetBucketLocation:
/// GetBucketLogging:
/// NotificationConfiguration
/// element.
/// s3:GetBucketNotification
/// permission.
/// GetBucketNotification:
/// GetBucketPolicy permissions on the specified bucket and belong to
/// the bucket owner's account in order to use this operation.
///
///
/// GetBucketPolicy permissions, Amazon S3 returns a 403
/// Access Denied 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 405
/// Method Not Allowed error.
/// GetBucketPolicy:
/// GetBucketRequestPayment:
/// enabled, the bucket owner must use an authentication
/// device to change the versioning state of the bucket.
/// GetBucketVersioning:
/// S3:GetBucketWebsite 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 S3:GetBucketWebsite permission.
/// DeleteBucketWebsite:
/// GetBucketCors:
/// s3:GetLifecycleConfiguration
/// action. The bucket owner has this permission, by default. The bucket owner can grant
/// this permission to others. For more information about permissions, see Permissions
/// Related to Bucket Subresource Operations and Managing
/// Access Permissions to Your Amazon S3 Resources.
/// GetBucketLifecycleConfiguration has the following special error:
/// NoSuchLifecycleConfiguration
/// DeleteBucketMetricsConfiguration:
/// GET, you must have READ
/// access to the object. If you grant READ access to the anonymous user,
/// you can return the object without using an authorization header.
///
///
/// sample.jpg, you can name it photos/2006/February/sample.jpg.
/// GET operation. For a virtual hosted-style request example,
/// if you have the object photos/2006/February/sample.jpg, specify the resource
/// as /photos/2006/February/sample.jpg. For a path-style request example,
/// if you have the object photos/2006/February/sample.jpg in the bucket
/// named examplebucket, specify the resource as /examplebucket/photos/2006/February/sample.jpg.
/// For more information about request types, see HTTP
/// Host Header Bucket Specification.
/// InvalidObjectStateError error. For
/// information about restoring archived objects, see Restoring
/// Archived Objects.
/// x-amz-server-side-encryption, 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.
/// s3:GetObjectVersionTagging
/// action), the response also returns the x-amz-tagging-count header that
/// provides the count of number of tags associated with the object. You can use GetObjectTagging
/// to retrieve the tag set associated with an object.
/// s3:GetObject permission for this operation. For more information,
/// see Specifying
/// Permissions in a Policy. If the object you request does not exist, the error Amazon
/// S3 returns depends on whether you also have the s3:ListBucket permission.
/// s3:ListBucket permission on the bucket, Amazon S3 will
/// return an HTTP status code 404 ("no such key") error.
/// s3:ListBucket permission, Amazon S3 will return
/// an HTTP status code 403 ("access denied") error.
/// versionId subresource.
/// x-amz-delete-marker: true in the response.
/// Content-Type,
/// Content-Language, Expires, Cache-Control, Content-Disposition,
/// and Content-Encoding. To override these header values in the GET response,
/// you use the following request parameters.
/// response-content-type
/// response-content-language
/// response-expires
/// response-cache-control
/// response-content-disposition
/// response-content-encoding
/// If-Match and If-Unmodified-Since headers
/// are present in the request as follows: If-Match condition evaluates to
/// true, and; If-Unmodified-Since condition evaluates to false;
/// then, S3 returns 200 OK and the data requested.
/// If-None-Match and If-Modified-Since headers
/// are present in the request as follows: If-None-Match condition evaluates
/// to false, and; If-Modified-Since condition evaluates to
/// true; then, S3 returns 304 Not Modified response code.
/// GetObject:
/// GET, you must have READ
/// access to the object. If you grant READ access to the anonymous user,
/// you can return the object without using an authorization header.
///
///
/// sample.jpg, you can name it photos/2006/February/sample.jpg.
/// GET operation. For a virtual hosted-style request example,
/// if you have the object photos/2006/February/sample.jpg, specify the resource
/// as /photos/2006/February/sample.jpg. For a path-style request example,
/// if you have the object photos/2006/February/sample.jpg in the bucket
/// named examplebucket, specify the resource as /examplebucket/photos/2006/February/sample.jpg.
/// For more information about request types, see HTTP
/// Host Header Bucket Specification.
/// InvalidObjectStateError error. For
/// information about restoring archived objects, see Restoring
/// Archived Objects.
/// x-amz-server-side-encryption, 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.
/// s3:GetObjectVersionTagging
/// action), the response also returns the x-amz-tagging-count header that
/// provides the count of number of tags associated with the object. You can use GetObjectTagging
/// to retrieve the tag set associated with an object.
/// s3:GetObject permission for this operation. For more information,
/// see Specifying
/// Permissions in a Policy. If the object you request does not exist, the error Amazon
/// S3 returns depends on whether you also have the s3:ListBucket permission.
/// s3:ListBucket permission on the bucket, Amazon S3 will
/// return an HTTP status code 404 ("no such key") error.
/// s3:ListBucket permission, Amazon S3 will return
/// an HTTP status code 403 ("access denied") error.
/// versionId subresource.
/// x-amz-delete-marker: true in the response.
/// Content-Type,
/// Content-Language, Expires, Cache-Control, Content-Disposition,
/// and Content-Encoding. To override these header values in the GET response,
/// you use the following request parameters.
/// response-content-type
/// response-content-language
/// response-expires
/// response-cache-control
/// response-content-disposition
/// response-content-encoding
/// If-Match and If-Unmodified-Since headers
/// are present in the request as follows: If-Match condition evaluates to
/// true, and; If-Unmodified-Since condition evaluates to false;
/// then, S3 returns 200 OK and the data requested.
/// If-None-Match and If-Modified-Since headers
/// are present in the request as follows: If-None-Match condition evaluates
/// to false, and; If-Modified-Since condition evaluates to
/// true; then, S3 returns 304 Not Modified response code.
/// GetObject:
/// HEAD request has the same options as a GET operation on
/// an object. The response is identical to the GET response except that
/// there is no response body.
/// x-amz-server-side-encryption, 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.
/// If-Match and If-Unmodified-Since
/// headers are present in the request as follows:
/// If-Match condition evaluates to true, and;
/// If-Unmodified-Since condition evaluates to false;
/// 200 OK and the data requested.
/// If-None-Match and If-Modified-Since
/// headers are present in the request as follows:
/// If-None-Match condition evaluates to false, and;
/// If-Modified-Since condition evaluates to true;
/// 304 Not Modified response code.
/// s3:GetObject permission for this operation. For more information,
/// see Specifying
/// Permissions in a Policy. If the object you request does not exist, the error Amazon
/// S3 returns depends on whether you also have the s3:ListBucket permission.
/// s3:ListBucket permission on the bucket, Amazon S3 returns
/// an HTTP status code 404 ("no such key") error.
/// s3:ListBucket permission, Amazon S3 returns an
/// HTTP status code 403 ("access denied") error.
/// HeadObject:
/// HEAD request has the same options as a GET operation on
/// an object. The response is identical to the GET response except that
/// there is no response body.
/// x-amz-server-side-encryption, 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.
/// If-Match and If-Unmodified-Since
/// headers are present in the request as follows:
/// If-Match condition evaluates to true, and;
/// If-Unmodified-Since condition evaluates to false;
/// 200 OK and the data requested.
/// If-None-Match and If-Modified-Since
/// headers are present in the request as follows:
/// If-None-Match condition evaluates to false, and;
/// If-Modified-Since condition evaluates to true;
/// 304 Not Modified response code.
/// s3:GetObject permission for this operation. For more information,
/// see Specifying
/// Permissions in a Policy. If the object you request does not exist, the error Amazon
/// S3 returns depends on whether you also have the s3:ListBucket permission.
/// s3:ListBucket permission on the bucket, Amazon S3 returns
/// an HTTP status code 404 ("no such key") error.
/// s3:ListBucket permission, Amazon S3 returns an
/// HTTP status code 403 ("access denied") error.
/// HeadObject:
/// GetObjectTorrent:
/// CreateMultipartUpload.
///
/// kms:Encrypt, kms:Decrypt, kms:ReEncrypt*,
/// kms:GenerateDataKey*, and kms:DescribeKey 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.
/// x-amz-acl request header. For more information,
/// see Canned
/// ACL.
/// x-amz-grant-read, x-amz-grant-read-acp,
/// x-amz-grant-write-acp, and x-amz-grant-full-control headers.
/// These parameters map to the set of permissions that Amazon S3 supports in an ACL.
/// For more information, see Access
/// Control List (ACL) Overview.
/// x-amz-server-side-encryption:aws:kms, but don't provide
/// x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the AWS managed
/// CMK in AWS KMS to protect the data.
/// x-amz-acl) — 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 Canned
/// ACL.
/// emailAddress – if the value specified is the email address of an AWS
/// account
/// id – if the value specified is the canonical user ID of an AWS account
/// uri – if you are granting permissions to a predefined group
/// x-amz-grant-read header grants the AWS accounts
/// identified by email addresses permissions to read object data and its metadata:
/// x-amz-grant-read: emailAddress="xyz@amazon.com", emailAddress="abc@amazon.com"
///
/// CreateMultipartUpload:
/// max-uploads parameter in the response. If additional multipart uploads
/// satisfy the list criteria, the response will contain an IsTruncated element
/// with the value true. To list the additional multipart uploads, use the key-marker
/// and upload-id-marker request parameters.
/// ListMultipartUploads:
/// max-uploads parameter in the response. If additional multipart uploads
/// satisfy the list criteria, the response will contain an IsTruncated element
/// with the value true. To list the additional multipart uploads, use the key-marker
/// and upload-id-marker request parameters.
/// ListMultipartUploads:
/// ListObjects.
/// ListObjects:
/// ListObjects.
/// ListObjects:
/// max-parts request parameter.
/// If your multipart upload consists of more than 1,000 parts, the response returns an
/// IsTruncated field with the value of true, and a NextPartNumberMarker
/// element. In subsequent ListParts requests you can include the part-number-marker
/// query string parameter and set its value to the NextPartNumberMarker
/// field value from the previous response.
///
///
/// ListParts:
/// ListObjectVersions:
/// ListObjectVersions:
/// s3.amazonaws.com 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 Virtual
/// Hosting of Buckets.
/// x-amz-acl 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. For more information, see Canned
/// ACL.
/// x-amz-grant-read, x-amz-grant-write,
/// x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control
/// headers. These headers map to the set of permissions Amazon S3 supports in an ACL.
/// For more information, see Access
/// Control List (ACL) Overview.
/// emailAddress – if the value specified is the email address of an AWS
/// account
/// id – if the value specified is the canonical user ID of an AWS account
/// uri – if you are granting permissions to a predefined group
/// x-amz-grant-read header grants the AWS accounts
/// identified by email addresses permissions to read object data and its metadata:
/// x-amz-grant-read: emailAddress="xyz@amazon.com", emailAddress="abc@amazon.com"
///
/// CreateBucket:
/// PutBucketPolicy permissions on the specified bucket and
/// belong to the bucket owner's account in order to use this operation.
///
///
/// PutBucketPolicy permissions, Amazon S3 returns a 403
/// Access Denied 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 405
/// Method Not Allowed error.
/// PutBucketPolicy:
/// PutBucketPolicy permissions on the specified bucket and
/// belong to the bucket owner's account in order to use this operation.
///
///
/// PutBucketPolicy permissions, Amazon S3 returns a 403
/// Access Denied 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 405
/// Method Not Allowed error.
/// PutBucketPolicy:
/// PutBucketRequestPayment:
/// s3:PutBucketTagging
/// action. The bucket owner has this permission by default and can grant this permission
/// to others. For more information about permissions, see Permissions
/// Related to Bucket Subresource Operations and Managing
/// Access Permissions to Your Amazon S3 Resources.
/// PutBucketTagging has the following special errors:
/// InvalidTagError
/// MalformedXMLError
/// OperationAbortedError
/// InternalError
/// PutBucketTagging:
/// website
/// 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 Hosting
/// Websites on Amazon S3.
///
///
/// S3:PutBucketWebsite 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 S3:PutBucketWebsite permission.
/// WebsiteConfiguration
/// RedirectAllRequestsTo
/// HostName
/// Protocol
/// WebsiteConfiguration
/// IndexDocument
/// Suffix
/// ErrorDocument
/// Key
/// RoutingRules
/// RoutingRule
/// Condition
/// HttpErrorCodeReturnedEquals
/// KeyPrefixEquals
/// Redirect
/// Protocol
/// HostName
/// ReplaceKeyPrefixWith
/// ReplaceKeyWith
/// HttpRedirectCode
/// cors configuration for your bucket. If the configuration exists,
/// Amazon S3 replaces it.
///
///
/// s3:PutBucketCORS
/// action. By default, the bucket owner has this permission and can grant it to others.
/// http://www.example.com
/// to access your Amazon S3 bucket at my.example.bucket.com by using the
/// browser's XMLHttpRequest capability.
/// cors
/// subresource to the bucket. The cors 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.
/// cors configuration on the bucket and uses
/// the first CORSRule rule that matches the incoming browser request to
/// enable a cross-origin request. For a rule to match, the following conditions must
/// be met:
/// Origin header must match AllowedOrigin elements.
/// Access-Control-Request-Method
/// header in case of a pre-flight OPTIONS request must be one of the AllowedMethod
/// elements.
/// Access-Control-Request-Headers request
/// header of a pre-flight request must match an AllowedHeader element.
/// Related Resources /// ///
corsconfiguration.
/// Describes the cross-origin access configuration for objects in an Amazon S3 bucket. For more information, see Enabling Cross-Origin Resource Sharing in the Amazon Simple Storage Service Developer Guide.
/// An Action delegate that is invoked when the operation completes.
///
/// A user-defined state object that is passed to the callback procedure. Retrieve this object from within the callback
/// procedure using the AsyncState property.
///
///
/// PutBucketLifecycleConfiguration:
/// select - Perform a select query on an archived object
/// restore an archive - Restore an archived object
/// s3:RestoreObject
/// and s3:GetObject actions. The bucket owner has this permission by default
/// and can grant this permission to others. For more information about permissions, see
/// Permissions
/// Related to Bucket Subresource Operations and Managing
/// Access Permissions to Your Amazon S3 Resources in the Amazon Simple Storage
/// Service Developer Guide.
/// S3 structure in the request body, see
/// the following:
/// SELECT type of restoration for your
/// query in the request body's SelectParameters structure. You can use expressions
/// like the following examples.
/// SELECT * FROM Object
/// SELECT s._1, s._2 FROM Object s WHERE s._3 > 100
/// fileHeaderInfo in the CSV
/// structure in the request body to USE, you can specify headers in the
/// query. (If you set the fileHeaderInfo field to IGNORE, the
/// first row is skipped for the query.) You cannot mix ordinal positions with header
/// column names.
/// SELECT s.Id, s.FirstName, s.SSN FROM S3Object s
/// Expedited tier. For more information
/// about tiers, see "Restoring Archives," later in this topic.
/// 409.
/// Tier element of the
/// request body:
/// Expedited - 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.
/// Standard - 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.
/// Bulk - 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.
/// Expedited data access, see Restoring
/// Archived Objects in the Amazon Simple Storage Service Developer Guide.
///
/// Tier
/// 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 Days request element. For
/// more information, see
/// Upgrading the Speed of an In-Progress Restore in the Amazon Simple Storage
/// Service Developer Guide.
/// HEAD request.
/// Operations return the x-amz-restore 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
/// Configuring
/// Amazon S3 Event Notifications in the Amazon Simple Storage Service Developer
/// Guide.
/// 200 OK or 202 Accepted
/// status code.
/// 202 Accepted
/// in the response.
/// 200 OK in
/// the response.
/// Special Errors /// ///
/// ///
/// ///
Related Resources /// ///
select - Perform a select query on an archived object
/// restore an archive - Restore an archived object
/// s3:RestoreObject
/// and s3:GetObject actions. The bucket owner has this permission by default
/// and can grant this permission to others. For more information about permissions, see
/// Permissions
/// Related to Bucket Subresource Operations and Managing
/// Access Permissions to Your Amazon S3 Resources in the Amazon Simple Storage
/// Service Developer Guide.
/// S3 structure in the request body, see
/// the following:
/// SELECT type of restoration for your
/// query in the request body's SelectParameters structure. You can use expressions
/// like the following examples.
/// SELECT * FROM Object
/// SELECT s._1, s._2 FROM Object s WHERE s._3 > 100
/// fileHeaderInfo in the CSV
/// structure in the request body to USE, you can specify headers in the
/// query. (If you set the fileHeaderInfo field to IGNORE, the
/// first row is skipped for the query.) You cannot mix ordinal positions with header
/// column names.
/// SELECT s.Id, s.FirstName, s.SSN FROM S3Object s
/// Expedited tier. For more information
/// about tiers, see "Restoring Archives," later in this topic.
/// 409.
/// Tier element of the
/// request body:
/// Expedited - 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.
/// Standard - 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.
/// Bulk - 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.
/// Expedited data access, see Restoring
/// Archived Objects in the Amazon Simple Storage Service Developer Guide.
///
/// Tier
/// 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 Days request element. For
/// more information, see
/// Upgrading the Speed of an In-Progress Restore in the Amazon Simple Storage
/// Service Developer Guide.
/// HEAD request.
/// Operations return the x-amz-restore 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
/// Configuring
/// Amazon S3 Event Notifications in the Amazon Simple Storage Service Developer
/// Guide.
/// 200 OK or 202 Accepted
/// status code.
/// 202 Accepted
/// in the response.
/// 200 OK in
/// the response.
/// Special Errors /// ///
/// ///
/// ///
Related Resources /// ///
select - Perform a select query on an archived object
/// restore an archive - Restore an archived object
/// s3:RestoreObject
/// and s3:GetObject actions. The bucket owner has this permission by default
/// and can grant this permission to others. For more information about permissions, see
/// Permissions
/// Related to Bucket Subresource Operations and Managing
/// Access Permissions to Your Amazon S3 Resources in the Amazon Simple Storage
/// Service Developer Guide.
/// S3 structure in the request body, see
/// the following:
/// SELECT type of restoration for your
/// query in the request body's SelectParameters structure. You can use expressions
/// like the following examples.
/// SELECT * FROM Object
/// SELECT s._1, s._2 FROM Object s WHERE s._3 > 100
/// fileHeaderInfo in the CSV
/// structure in the request body to USE, you can specify headers in the
/// query. (If you set the fileHeaderInfo field to IGNORE, the
/// first row is skipped for the query.) You cannot mix ordinal positions with header
/// column names.
/// SELECT s.Id, s.FirstName, s.SSN FROM S3Object s
/// Expedited tier. For more information
/// about tiers, see "Restoring Archives," later in this topic.
/// 409.
/// Tier element of the
/// request body:
/// Expedited - 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.
/// Standard - 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.
/// Bulk - 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.
/// Expedited data access, see Restoring
/// Archived Objects in the Amazon Simple Storage Service Developer Guide.
///
/// Tier
/// 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 Days request element. For
/// more information, see
/// Upgrading the Speed of an In-Progress Restore in the Amazon Simple Storage
/// Service Developer Guide.
/// HEAD request.
/// Operations return the x-amz-restore 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
/// Configuring
/// Amazon S3 Event Notifications in the Amazon Simple Storage Service Developer
/// Guide.
/// 200 OK or 202 Accepted
/// status code.
/// 202 Accepted
/// in the response.
/// 200 OK in
/// the response.
/// Special Errors /// ///
/// ///
/// ///
Related Resources /// ///
select - Perform a select query on an archived object
/// restore an archive - Restore an archived object
/// s3:RestoreObject
/// and s3:GetObject actions. The bucket owner has this permission by default
/// and can grant this permission to others. For more information about permissions, see
/// Permissions
/// Related to Bucket Subresource Operations and Managing
/// Access Permissions to Your Amazon S3 Resources in the Amazon Simple Storage
/// Service Developer Guide.
/// S3 structure in the request body, see
/// the following:
/// SELECT type of restoration for your
/// query in the request body's SelectParameters structure. You can use expressions
/// like the following examples.
/// SELECT * FROM Object
/// SELECT s._1, s._2 FROM Object s WHERE s._3 > 100
/// fileHeaderInfo in the CSV
/// structure in the request body to USE, you can specify headers in the
/// query. (If you set the fileHeaderInfo field to IGNORE, the
/// first row is skipped for the query.) You cannot mix ordinal positions with header
/// column names.
/// SELECT s.Id, s.FirstName, s.SSN FROM S3Object s
/// Expedited tier. For more information
/// about tiers, see "Restoring Archives," later in this topic.
/// 409.
/// Tier element of the
/// request body:
/// Expedited - 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.
/// Standard - 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.
/// Bulk - 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.
/// Expedited data access, see Restoring
/// Archived Objects in the Amazon Simple Storage Service Developer Guide.
///
/// Tier
/// 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 Days request element. For
/// more information, see
/// Upgrading the Speed of an In-Progress Restore in the Amazon Simple Storage
/// Service Developer Guide.
/// HEAD request.
/// Operations return the x-amz-restore 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
/// Configuring
/// Amazon S3 Event Notifications in the Amazon Simple Storage Service Developer
/// Guide.
/// 200 OK or 202 Accepted
/// status code.
/// 202 Accepted
/// in the response.
/// 200 OK in
/// the response.
/// Special Errors /// ///
/// ///
/// ///
Related Resources /// ///