Specifies the number of days after which Amazon S3 aborts an incomplete multipart upload.
" } } }, "traits": { "smithy.api#documentation": "Specifies the days since the initiation of an incomplete multipart upload that Amazon S3 will wait before\n permanently removing all parts of the upload. For more information, see Aborting\n Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration in the\n Amazon S3 User Guide.
" } }, "com.amazonaws.s3#AbortMultipartUpload": { "type": "operation", "input": { "target": "com.amazonaws.s3#AbortMultipartUploadRequest" }, "output": { "target": "com.amazonaws.s3#AbortMultipartUploadOutput" }, "errors": [ { "target": "com.amazonaws.s3#NoSuchUpload" } ], "traits": { "smithy.api#documentation": "This operation aborts a multipart upload. After a multipart upload is aborted, no additional parts\n can be uploaded using that upload ID. The storage consumed by any previously uploaded parts will be\n freed. However, if any part uploads are currently in progress, those part uploads might or might not\n succeed. As a result, it might be necessary to abort a given multipart upload multiple times in order to\n completely free all storage consumed by all parts.
\nTo verify that all parts have been removed and prevent getting charged for the part storage, you\n should call the ListParts API operation and ensure that the parts list is empty.
\n\n Directory buckets - If multipart uploads in a\n directory bucket are in progress, you can't delete the bucket until all the in-progress multipart\n uploads are aborted or completed. To delete these in-progress multipart uploads, use the\n ListMultipartUploads operation to list the in-progress multipart uploads in the\n bucket and use the AbortMultipartUpload operation to abort all the in-progress\n multipart uploads.
\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n General purpose bucket permissions - For information\n about permissions required to use the multipart upload, see Multipart Upload and Permissions in\n the Amazon S3 User Guide.
\n\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following operations are related to AbortMultipartUpload:
\n UploadPart\n
\n\n ListParts\n
\n\n ListMultipartUploads\n
\nThe bucket name to which the upload was taking place.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Key of the object for which the multipart upload was initiated.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Key" } } }, "UploadId": { "target": "com.amazonaws.s3#MultipartUploadId", "traits": { "smithy.api#documentation": "Upload ID that identifies the multipart upload.
", "smithy.api#httpQuery": "uploadId", "smithy.api#required": {} } }, "RequestPayer": { "target": "com.amazonaws.s3#RequestPayer", "traits": { "smithy.api#httpHeader": "x-amz-request-payer" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
If present, this header aborts an in progress multipart upload only if it was initiated on the\n provided timestamp. If the initiated timestamp of the multipart upload does not match the provided\n value, the operation returns a 412 Precondition Failed error. If the initiated timestamp\n matches or if the multipart upload doesn\u2019t exist, the operation returns a 204 Success (No\n Content) response.
This functionality is only supported for directory buckets.
\nSpecifies the transfer acceleration status of the bucket.
" } } }, "traits": { "smithy.api#documentation": "Configures the transfer acceleration state for an Amazon S3 bucket. For more information, see Amazon S3 Transfer\n Acceleration in the Amazon S3 User Guide.
" } }, "com.amazonaws.s3#AcceptRanges": { "type": "string" }, "com.amazonaws.s3#AccessControlPolicy": { "type": "structure", "members": { "Grants": { "target": "com.amazonaws.s3#Grants", "traits": { "smithy.api#documentation": "A list of grants.
", "smithy.api#xmlName": "AccessControlList" } }, "Owner": { "target": "com.amazonaws.s3#Owner", "traits": { "smithy.api#documentation": "Container for the bucket owner's display name and ID.
" } } }, "traits": { "smithy.api#documentation": "Contains the elements that set the ACL permissions for an object per grantee.
" } }, "com.amazonaws.s3#AccessControlTranslation": { "type": "structure", "members": { "Owner": { "target": "com.amazonaws.s3#OwnerOverride", "traits": { "smithy.api#documentation": "Specifies the replica ownership. For default and valid values, see PUT bucket replication in the\n Amazon S3 API Reference.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "A container for information about access control for replicas.
" } }, "com.amazonaws.s3#AccessKeyIdValue": { "type": "string" }, "com.amazonaws.s3#AccessPointAlias": { "type": "boolean" }, "com.amazonaws.s3#AccessPointArn": { "type": "string" }, "com.amazonaws.s3#AccountId": { "type": "string" }, "com.amazonaws.s3#AllowQuotedRecordDelimiter": { "type": "boolean" }, "com.amazonaws.s3#AllowedHeader": { "type": "string" }, "com.amazonaws.s3#AllowedHeaders": { "type": "list", "member": { "target": "com.amazonaws.s3#AllowedHeader" } }, "com.amazonaws.s3#AllowedMethod": { "type": "string" }, "com.amazonaws.s3#AllowedMethods": { "type": "list", "member": { "target": "com.amazonaws.s3#AllowedMethod" } }, "com.amazonaws.s3#AllowedOrigin": { "type": "string" }, "com.amazonaws.s3#AllowedOrigins": { "type": "list", "member": { "target": "com.amazonaws.s3#AllowedOrigin" } }, "com.amazonaws.s3#AmazonS3": { "type": "service", "version": "2006-03-01", "operations": [ { "target": "com.amazonaws.s3#AbortMultipartUpload" }, { "target": "com.amazonaws.s3#CompleteMultipartUpload" }, { "target": "com.amazonaws.s3#CopyObject" }, { "target": "com.amazonaws.s3#CreateBucket" }, { "target": "com.amazonaws.s3#CreateBucketMetadataConfiguration" }, { "target": "com.amazonaws.s3#CreateBucketMetadataTableConfiguration" }, { "target": "com.amazonaws.s3#CreateMultipartUpload" }, { "target": "com.amazonaws.s3#CreateSession" }, { "target": "com.amazonaws.s3#DeleteBucket" }, { "target": "com.amazonaws.s3#DeleteBucketAnalyticsConfiguration" }, { "target": "com.amazonaws.s3#DeleteBucketCors" }, { "target": "com.amazonaws.s3#DeleteBucketEncryption" }, { "target": "com.amazonaws.s3#DeleteBucketIntelligentTieringConfiguration" }, { "target": "com.amazonaws.s3#DeleteBucketInventoryConfiguration" }, { "target": "com.amazonaws.s3#DeleteBucketLifecycle" }, { "target": "com.amazonaws.s3#DeleteBucketMetadataConfiguration" }, { "target": "com.amazonaws.s3#DeleteBucketMetadataTableConfiguration" }, { "target": "com.amazonaws.s3#DeleteBucketMetricsConfiguration" }, { "target": "com.amazonaws.s3#DeleteBucketOwnershipControls" }, { "target": "com.amazonaws.s3#DeleteBucketPolicy" }, { "target": "com.amazonaws.s3#DeleteBucketReplication" }, { "target": "com.amazonaws.s3#DeleteBucketTagging" }, { "target": "com.amazonaws.s3#DeleteBucketWebsite" }, { "target": "com.amazonaws.s3#DeleteObject" }, { "target": "com.amazonaws.s3#DeleteObjects" }, { "target": "com.amazonaws.s3#DeleteObjectTagging" }, { "target": "com.amazonaws.s3#DeletePublicAccessBlock" }, { "target": "com.amazonaws.s3#GetBucketAccelerateConfiguration" }, { "target": "com.amazonaws.s3#GetBucketAcl" }, { "target": "com.amazonaws.s3#GetBucketAnalyticsConfiguration" }, { "target": "com.amazonaws.s3#GetBucketCors" }, { "target": "com.amazonaws.s3#GetBucketEncryption" }, { "target": "com.amazonaws.s3#GetBucketIntelligentTieringConfiguration" }, { "target": "com.amazonaws.s3#GetBucketInventoryConfiguration" }, { "target": "com.amazonaws.s3#GetBucketLifecycleConfiguration" }, { "target": "com.amazonaws.s3#GetBucketLocation" }, { "target": "com.amazonaws.s3#GetBucketLogging" }, { "target": "com.amazonaws.s3#GetBucketMetadataConfiguration" }, { "target": "com.amazonaws.s3#GetBucketMetadataTableConfiguration" }, { "target": "com.amazonaws.s3#GetBucketMetricsConfiguration" }, { "target": "com.amazonaws.s3#GetBucketNotificationConfiguration" }, { "target": "com.amazonaws.s3#GetBucketOwnershipControls" }, { "target": "com.amazonaws.s3#GetBucketPolicy" }, { "target": "com.amazonaws.s3#GetBucketPolicyStatus" }, { "target": "com.amazonaws.s3#GetBucketReplication" }, { "target": "com.amazonaws.s3#GetBucketRequestPayment" }, { "target": "com.amazonaws.s3#GetBucketTagging" }, { "target": "com.amazonaws.s3#GetBucketVersioning" }, { "target": "com.amazonaws.s3#GetBucketWebsite" }, { "target": "com.amazonaws.s3#GetObject" }, { "target": "com.amazonaws.s3#GetObjectAcl" }, { "target": "com.amazonaws.s3#GetObjectAttributes" }, { "target": "com.amazonaws.s3#GetObjectLegalHold" }, { "target": "com.amazonaws.s3#GetObjectLockConfiguration" }, { "target": "com.amazonaws.s3#GetObjectRetention" }, { "target": "com.amazonaws.s3#GetObjectTagging" }, { "target": "com.amazonaws.s3#GetObjectTorrent" }, { "target": "com.amazonaws.s3#GetPublicAccessBlock" }, { "target": "com.amazonaws.s3#HeadBucket" }, { "target": "com.amazonaws.s3#HeadObject" }, { "target": "com.amazonaws.s3#ListBucketAnalyticsConfigurations" }, { "target": "com.amazonaws.s3#ListBucketIntelligentTieringConfigurations" }, { "target": "com.amazonaws.s3#ListBucketInventoryConfigurations" }, { "target": "com.amazonaws.s3#ListBucketMetricsConfigurations" }, { "target": "com.amazonaws.s3#ListBuckets" }, { "target": "com.amazonaws.s3#ListDirectoryBuckets" }, { "target": "com.amazonaws.s3#ListMultipartUploads" }, { "target": "com.amazonaws.s3#ListObjects" }, { "target": "com.amazonaws.s3#ListObjectsV2" }, { "target": "com.amazonaws.s3#ListObjectVersions" }, { "target": "com.amazonaws.s3#ListParts" }, { "target": "com.amazonaws.s3#PutBucketAccelerateConfiguration" }, { "target": "com.amazonaws.s3#PutBucketAcl" }, { "target": "com.amazonaws.s3#PutBucketAnalyticsConfiguration" }, { "target": "com.amazonaws.s3#PutBucketCors" }, { "target": "com.amazonaws.s3#PutBucketEncryption" }, { "target": "com.amazonaws.s3#PutBucketIntelligentTieringConfiguration" }, { "target": "com.amazonaws.s3#PutBucketInventoryConfiguration" }, { "target": "com.amazonaws.s3#PutBucketLifecycleConfiguration" }, { "target": "com.amazonaws.s3#PutBucketLogging" }, { "target": "com.amazonaws.s3#PutBucketMetricsConfiguration" }, { "target": "com.amazonaws.s3#PutBucketNotificationConfiguration" }, { "target": "com.amazonaws.s3#PutBucketOwnershipControls" }, { "target": "com.amazonaws.s3#PutBucketPolicy" }, { "target": "com.amazonaws.s3#PutBucketReplication" }, { "target": "com.amazonaws.s3#PutBucketRequestPayment" }, { "target": "com.amazonaws.s3#PutBucketTagging" }, { "target": "com.amazonaws.s3#PutBucketVersioning" }, { "target": "com.amazonaws.s3#PutBucketWebsite" }, { "target": "com.amazonaws.s3#PutObject" }, { "target": "com.amazonaws.s3#PutObjectAcl" }, { "target": "com.amazonaws.s3#PutObjectLegalHold" }, { "target": "com.amazonaws.s3#PutObjectLockConfiguration" }, { "target": "com.amazonaws.s3#PutObjectRetention" }, { "target": "com.amazonaws.s3#PutObjectTagging" }, { "target": "com.amazonaws.s3#PutPublicAccessBlock" }, { "target": "com.amazonaws.s3#RenameObject" }, { "target": "com.amazonaws.s3#RestoreObject" }, { "target": "com.amazonaws.s3#SelectObjectContent" }, { "target": "com.amazonaws.s3#UpdateBucketMetadataInventoryTableConfiguration" }, { "target": "com.amazonaws.s3#UpdateBucketMetadataJournalTableConfiguration" }, { "target": "com.amazonaws.s3#UploadPart" }, { "target": "com.amazonaws.s3#UploadPartCopy" }, { "target": "com.amazonaws.s3#WriteGetObjectResponse" } ], "traits": { "aws.api#service": { "sdkId": "S3", "arnNamespace": "s3", "cloudFormationName": "S3", "cloudTrailEventSource": "s3.amazonaws.com", "endpointPrefix": "s3" }, "aws.auth#sigv4": { "name": "s3" }, "aws.protocols#restXml": { "noErrorWrapping": true }, "smithy.api#documentation": "", "smithy.api#suppress": [ "RuleSetAuthSchemes" ], "smithy.api#title": "Amazon Simple Storage Service", "smithy.api#xmlNamespace": { "uri": "http://s3.amazonaws.com/doc/2006-03-01/" }, "smithy.rules#clientContextParams": { "ForcePathStyle": { "documentation": "Forces this client to use path-style addressing for buckets.", "type": "boolean" }, "UseArnRegion": { "documentation": "Enables this client to use an ARN's region when constructing an endpoint instead of the client's configured region.", "type": "boolean" }, "DisableMultiRegionAccessPoints": { "documentation": "Disables this client's usage of Multi-Region Access Points.", "type": "boolean" }, "Accelerate": { "documentation": "Enables this client to use S3 Transfer Acceleration endpoints.", "type": "boolean" }, "DisableS3ExpressSessionAuth": { "documentation": "Disables this client's usage of Session Auth for S3Express buckets and reverts to using conventional SigV4 for those.", "type": "boolean" } }, "smithy.rules#endpointRuleSet": { "version": "1.0", "parameters": { "Bucket": { "required": false, "documentation": "The S3 bucket used to send the request. This is an optional parameter that will be set automatically for operations that are scoped to an S3 bucket.", "type": "String" }, "Region": { "builtIn": "AWS::Region", "required": false, "documentation": "The AWS region used to dispatch the request.", "type": "String" }, "UseFIPS": { "builtIn": "AWS::UseFIPS", "required": true, "default": false, "documentation": "When true, send this request to the FIPS-compliant regional endpoint. If the configured endpoint does not have a FIPS compliant endpoint, dispatching the request will return an error.", "type": "Boolean" }, "UseDualStack": { "builtIn": "AWS::UseDualStack", "required": true, "default": false, "documentation": "When true, use the dual-stack endpoint. If the configured endpoint does not support dual-stack, dispatching the request MAY return an error.", "type": "Boolean" }, "Endpoint": { "builtIn": "SDK::Endpoint", "required": false, "documentation": "Override the endpoint used to send this request", "type": "String" }, "ForcePathStyle": { "builtIn": "AWS::S3::ForcePathStyle", "required": true, "default": false, "documentation": "When true, force a path-style endpoint to be used where the bucket name is part of the path.", "type": "Boolean" }, "Accelerate": { "builtIn": "AWS::S3::Accelerate", "required": true, "default": false, "documentation": "When true, use S3 Accelerate. NOTE: Not all regions support S3 accelerate.", "type": "Boolean" }, "UseGlobalEndpoint": { "builtIn": "AWS::S3::UseGlobalEndpoint", "required": true, "default": false, "documentation": "Whether the global endpoint should be used, rather then the regional endpoint for us-east-1.", "type": "Boolean" }, "UseObjectLambdaEndpoint": { "required": false, "documentation": "Internal parameter to use object lambda endpoint for an operation (eg: WriteGetObjectResponse)", "type": "Boolean" }, "Key": { "required": false, "documentation": "The S3 Key used to send the request. This is an optional parameter that will be set automatically for operations that are scoped to an S3 Key.", "type": "String" }, "Prefix": { "required": false, "documentation": "The S3 Prefix used to send the request. This is an optional parameter that will be set automatically for operations that are scoped to an S3 Prefix.", "type": "String" }, "CopySource": { "required": false, "documentation": "The Copy Source used for Copy Object request. This is an optional parameter that will be set automatically for operations that are scoped to Copy Source.", "type": "String" }, "DisableAccessPoints": { "required": false, "documentation": "Internal parameter to disable Access Point Buckets", "type": "Boolean" }, "DisableMultiRegionAccessPoints": { "builtIn": "AWS::S3::DisableMultiRegionAccessPoints", "required": true, "default": false, "documentation": "Whether multi-region access points (MRAP) should be disabled.", "type": "Boolean" }, "UseArnRegion": { "builtIn": "AWS::S3::UseArnRegion", "required": false, "documentation": "When an Access Point ARN is provided and this flag is enabled, the SDK MUST use the ARN's region when constructing the endpoint instead of the client's configured region.", "type": "Boolean" }, "UseS3ExpressControlEndpoint": { "required": false, "documentation": "Internal parameter to indicate whether S3Express operation should use control plane, (ex. CreateBucket)", "type": "Boolean" }, "DisableS3ExpressSessionAuth": { "required": false, "documentation": "Parameter to indicate whether S3Express session auth should be disabled", "type": "Boolean" } }, "rules": [ { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Region" } ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "error": "Accelerate cannot be used with FIPS", "type": "error" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, true ] }, { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ], "error": "Cannot set dual-stack in combination with a custom endpoint.", "type": "error" }, { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "error": "A custom endpoint cannot be combined with FIPS", "type": "error" }, { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, true ] } ], "error": "A custom endpoint cannot be combined with S3 Accelerate", "type": "error" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] }, { "fn": "aws.partition", "argv": [ { "ref": "Region" } ], "assign": "partitionResult" }, { "fn": "stringEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "partitionResult" }, "name" ] }, "aws-cn" ] } ], "error": "Partition does not support FIPS", "type": "error" }, { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Bucket" } ] }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 0, 6, true ], "assign": "bucketSuffix" }, { "fn": "stringEquals", "argv": [ { "ref": "bucketSuffix" }, "--x-s3" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, true ] } ], "error": "S3Express does not support Dual-stack.", "type": "error" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, true ] } ], "error": "S3Express does not support S3 Accelerate.", "type": "error" }, { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ], "assign": "url" } ], "rules": [ { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "DisableS3ExpressSessionAuth" } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "DisableS3ExpressSessionAuth" }, true ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "url" }, "isIp" ] }, true ] } ], "rules": [ { "conditions": [ { "fn": "uriEncode", "argv": [ { "ref": "Bucket" } ], "assign": "uri_encoded_bucket" } ], "rules": [ { "conditions": [], "endpoint": { "url": "{url#scheme}://{url#authority}/{uri_encoded_bucket}{url#path}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" } ], "type": "tree" }, { "conditions": [ { "fn": "aws.isVirtualHostableS3Bucket", "argv": [ { "ref": "Bucket" }, false ] } ], "rules": [ { "conditions": [], "endpoint": { "url": "{url#scheme}://{Bucket}.{url#authority}{url#path}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "error": "S3Express bucket name is not a valid virtual hostable name.", "type": "error" } ], "type": "tree" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "url" }, "isIp" ] }, true ] } ], "rules": [ { "conditions": [ { "fn": "uriEncode", "argv": [ { "ref": "Bucket" } ], "assign": "uri_encoded_bucket" } ], "rules": [ { "conditions": [], "endpoint": { "url": "{url#scheme}://{url#authority}/{uri_encoded_bucket}{url#path}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" } ], "type": "tree" }, { "conditions": [ { "fn": "aws.isVirtualHostableS3Bucket", "argv": [ { "ref": "Bucket" }, false ] } ], "rules": [ { "conditions": [], "endpoint": { "url": "{url#scheme}://{Bucket}.{url#authority}{url#path}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "error": "S3Express bucket name is not a valid virtual hostable name.", "type": "error" } ], "type": "tree" }, { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "UseS3ExpressControlEndpoint" } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseS3ExpressControlEndpoint" }, true ] } ], "rules": [ { "conditions": [ { "fn": "aws.partition", "argv": [ { "ref": "Region" } ], "assign": "partitionResult" } ], "rules": [ { "conditions": [ { "fn": "uriEncode", "argv": [ { "ref": "Bucket" } ], "assign": "uri_encoded_bucket" }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://s3express-control-fips.{Region}.{partitionResult#dnsSuffix}/{uri_encoded_bucket}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://s3express-control.{Region}.{partitionResult#dnsSuffix}/{uri_encoded_bucket}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" } ], "type": "tree" } ], "type": "tree" }, { "conditions": [ { "fn": "aws.isVirtualHostableS3Bucket", "argv": [ { "ref": "Bucket" }, false ] } ], "rules": [ { "conditions": [ { "fn": "aws.partition", "argv": [ { "ref": "Region" } ], "assign": "partitionResult" } ], "rules": [ { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "DisableS3ExpressSessionAuth" } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "DisableS3ExpressSessionAuth" }, true ] } ], "rules": [ { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 6, 14, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 14, 16, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 6, 15, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 15, 17, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 6, 19, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 19, 21, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 6, 20, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 20, 22, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 6, 26, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 26, 28, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "error": "Unrecognized S3Express bucket name format.", "type": "error" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 6, 14, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 14, 16, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 6, 15, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 15, 17, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 6, 19, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 19, 21, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 6, 20, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 20, 22, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 6, 26, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 26, 28, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "error": "Unrecognized S3Express bucket name format.", "type": "error" } ], "type": "tree" } ], "type": "tree" }, { "conditions": [], "error": "S3Express bucket name is not a valid virtual hostable name.", "type": "error" } ], "type": "tree" }, { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Bucket" } ] }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 0, 7, true ], "assign": "accessPointSuffix" }, { "fn": "stringEquals", "argv": [ { "ref": "accessPointSuffix" }, "--xa-s3" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, true ] } ], "error": "S3Express does not support Dual-stack.", "type": "error" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, true ] } ], "error": "S3Express does not support S3 Accelerate.", "type": "error" }, { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ], "assign": "url" } ], "rules": [ { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "DisableS3ExpressSessionAuth" } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "DisableS3ExpressSessionAuth" }, true ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "url" }, "isIp" ] }, true ] } ], "rules": [ { "conditions": [ { "fn": "uriEncode", "argv": [ { "ref": "Bucket" } ], "assign": "uri_encoded_bucket" } ], "rules": [ { "conditions": [], "endpoint": { "url": "{url#scheme}://{url#authority}/{uri_encoded_bucket}{url#path}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" } ], "type": "tree" }, { "conditions": [ { "fn": "aws.isVirtualHostableS3Bucket", "argv": [ { "ref": "Bucket" }, false ] } ], "rules": [ { "conditions": [], "endpoint": { "url": "{url#scheme}://{Bucket}.{url#authority}{url#path}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "error": "S3Express bucket name is not a valid virtual hostable name.", "type": "error" } ], "type": "tree" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "url" }, "isIp" ] }, true ] } ], "rules": [ { "conditions": [ { "fn": "uriEncode", "argv": [ { "ref": "Bucket" } ], "assign": "uri_encoded_bucket" } ], "rules": [ { "conditions": [], "endpoint": { "url": "{url#scheme}://{url#authority}/{uri_encoded_bucket}{url#path}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" } ], "type": "tree" }, { "conditions": [ { "fn": "aws.isVirtualHostableS3Bucket", "argv": [ { "ref": "Bucket" }, false ] } ], "rules": [ { "conditions": [], "endpoint": { "url": "{url#scheme}://{Bucket}.{url#authority}{url#path}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "error": "S3Express bucket name is not a valid virtual hostable name.", "type": "error" } ], "type": "tree" }, { "conditions": [ { "fn": "aws.isVirtualHostableS3Bucket", "argv": [ { "ref": "Bucket" }, false ] } ], "rules": [ { "conditions": [ { "fn": "aws.partition", "argv": [ { "ref": "Region" } ], "assign": "partitionResult" } ], "rules": [ { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "DisableS3ExpressSessionAuth" } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "DisableS3ExpressSessionAuth" }, true ] } ], "rules": [ { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 7, 15, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 15, 17, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 7, 16, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 16, 18, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 7, 20, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 20, 22, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 7, 21, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 21, 23, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 7, 27, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 27, 29, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "error": "Unrecognized S3Express bucket name format.", "type": "error" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 7, 15, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 15, 17, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 7, 16, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 16, 18, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 7, 20, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 20, 22, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 7, 21, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 21, 23, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "substring", "argv": [ { "ref": "Bucket" }, 7, 27, true ], "assign": "s3expressAvailabilityZoneId" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 27, 29, true ], "assign": "s3expressAvailabilityZoneDelim" }, { "fn": "stringEquals", "argv": [ { "ref": "s3expressAvailabilityZoneDelim" }, "--" ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{Bucket}.s3express-fips-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3express-{s3expressAvailabilityZoneId}.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4-s3express", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "error": "Unrecognized S3Express bucket name format.", "type": "error" } ], "type": "tree" } ], "type": "tree" }, { "conditions": [], "error": "S3Express bucket name is not a valid virtual hostable name.", "type": "error" } ], "type": "tree" }, { "conditions": [ { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Bucket" } ] } ] }, { "fn": "isSet", "argv": [ { "ref": "UseS3ExpressControlEndpoint" } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseS3ExpressControlEndpoint" }, true ] } ], "rules": [ { "conditions": [ { "fn": "aws.partition", "argv": [ { "ref": "Region" } ], "assign": "partitionResult" } ], "rules": [ { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ], "assign": "url" } ], "endpoint": { "url": "{url#scheme}://{url#authority}{url#path}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://s3express-control-fips.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://s3express-control.{Region}.{partitionResult#dnsSuffix}", "properties": { "backend": "S3Express", "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3express", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" } ], "type": "tree" }, { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Bucket" } ] }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 49, 50, true ], "assign": "hardwareType" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 8, 12, true ], "assign": "regionPrefix" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 0, 7, true ], "assign": "bucketAliasSuffix" }, { "fn": "substring", "argv": [ { "ref": "Bucket" }, 32, 49, true ], "assign": "outpostId" }, { "fn": "aws.partition", "argv": [ { "ref": "Region" } ], "assign": "regionPartition" }, { "fn": "stringEquals", "argv": [ { "ref": "bucketAliasSuffix" }, "--op-s3" ] } ], "rules": [ { "conditions": [ { "fn": "isValidHostLabel", "argv": [ { "ref": "outpostId" }, false ] } ], "rules": [ { "conditions": [ { "fn": "stringEquals", "argv": [ { "ref": "hardwareType" }, "e" ] } ], "rules": [ { "conditions": [ { "fn": "stringEquals", "argv": [ { "ref": "regionPrefix" }, "beta" ] } ], "rules": [ { "conditions": [ { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] } ], "error": "Expected a endpoint to be specified but no endpoint was found", "type": "error" }, { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ], "assign": "url" } ], "endpoint": { "url": "https://{Bucket}.ec2.{url#authority}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4a", "signingName": "s3-outposts", "signingRegionSet": [ "*" ] }, { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3-outposts", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.ec2.s3-outposts.{Region}.{regionPartition#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4a", "signingName": "s3-outposts", "signingRegionSet": [ "*" ] }, { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3-outposts", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "stringEquals", "argv": [ { "ref": "hardwareType" }, "o" ] } ], "rules": [ { "conditions": [ { "fn": "stringEquals", "argv": [ { "ref": "regionPrefix" }, "beta" ] } ], "rules": [ { "conditions": [ { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] } ], "error": "Expected a endpoint to be specified but no endpoint was found", "type": "error" }, { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ], "assign": "url" } ], "endpoint": { "url": "https://{Bucket}.op-{outpostId}.{url#authority}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4a", "signingName": "s3-outposts", "signingRegionSet": [ "*" ] }, { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3-outposts", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.op-{outpostId}.s3-outposts.{Region}.{regionPartition#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4a", "signingName": "s3-outposts", "signingRegionSet": [ "*" ] }, { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3-outposts", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "error": "Unrecognized hardware type: \"Expected hardware type o or e but got {hardwareType}\"", "type": "error" } ], "type": "tree" }, { "conditions": [], "error": "Invalid ARN: The outpost Id must only contain a-z, A-Z, 0-9 and `-`.", "type": "error" } ], "type": "tree" }, { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Bucket" } ] } ], "rules": [ { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ] } ] } ] } ], "error": "Custom endpoint `{Endpoint}` was not a valid URI", "type": "error" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "ForcePathStyle" }, false ] }, { "fn": "aws.isVirtualHostableS3Bucket", "argv": [ { "ref": "Bucket" }, false ] } ], "rules": [ { "conditions": [ { "fn": "aws.partition", "argv": [ { "ref": "Region" } ], "assign": "partitionResult" } ], "rules": [ { "conditions": [ { "fn": "isValidHostLabel", "argv": [ { "ref": "Region" }, false ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, true ] }, { "fn": "stringEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "partitionResult" }, "name" ] }, "aws-cn" ] } ], "error": "S3 Accelerate cannot be used in this region", "type": "error" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ], "endpoint": { "url": "https://{Bucket}.s3-fips.dualstack.us-east-1.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "us-east-1" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, true ] } ], "rules": [ { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3-fips.dualstack.{Region}.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, false ] } ], "endpoint": { "url": "https://{Bucket}.s3-fips.dualstack.{Region}.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ], "endpoint": { "url": "https://{Bucket}.s3-fips.us-east-1.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "us-east-1" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, true ] } ], "rules": [ { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3-fips.{Region}.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, false ] } ], "endpoint": { "url": "https://{Bucket}.s3-fips.{Region}.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, true ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ], "endpoint": { "url": "https://{Bucket}.s3-accelerate.dualstack.us-east-1.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "us-east-1" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, true ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, true ] } ], "rules": [ { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3-accelerate.dualstack.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, true ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, false ] } ], "endpoint": { "url": "https://{Bucket}.s3-accelerate.dualstack.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ], "endpoint": { "url": "https://{Bucket}.s3.dualstack.us-east-1.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "us-east-1" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, true ] } ], "rules": [ { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3.dualstack.{Region}.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, false ] } ], "endpoint": { "url": "https://{Bucket}.s3.dualstack.{Region}.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ], "assign": "url" }, { "fn": "booleanEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "url" }, "isIp" ] }, true ] }, { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ], "endpoint": { "url": "{url#scheme}://{url#authority}{url#normalizedPath}{Bucket}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "us-east-1" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ], "assign": "url" }, { "fn": "booleanEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "url" }, "isIp" ] }, false ] }, { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ], "endpoint": { "url": "{url#scheme}://{Bucket}.{url#authority}{url#path}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "us-east-1" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ], "assign": "url" }, { "fn": "booleanEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "url" }, "isIp" ] }, true ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, true ] } ], "rules": [ { "conditions": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "us-east-1" ] } ], "endpoint": { "url": "{url#scheme}://{url#authority}{url#normalizedPath}{Bucket}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "{url#scheme}://{url#authority}{url#normalizedPath}{Bucket}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ], "assign": "url" }, { "fn": "booleanEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "url" }, "isIp" ] }, false ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, true ] } ], "rules": [ { "conditions": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "us-east-1" ] } ], "endpoint": { "url": "{url#scheme}://{Bucket}.{url#authority}{url#path}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "{url#scheme}://{Bucket}.{url#authority}{url#path}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ], "assign": "url" }, { "fn": "booleanEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "url" }, "isIp" ] }, true ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, false ] } ], "endpoint": { "url": "{url#scheme}://{url#authority}{url#normalizedPath}{Bucket}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ], "assign": "url" }, { "fn": "booleanEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "url" }, "isIp" ] }, false ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, false ] } ], "endpoint": { "url": "{url#scheme}://{Bucket}.{url#authority}{url#path}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, true ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ], "endpoint": { "url": "https://{Bucket}.s3-accelerate.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "us-east-1" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, true ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, true ] } ], "rules": [ { "conditions": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "us-east-1" ] } ], "endpoint": { "url": "https://{Bucket}.s3-accelerate.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3-accelerate.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, true ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, false ] } ], "endpoint": { "url": "https://{Bucket}.s3-accelerate.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ], "endpoint": { "url": "https://{Bucket}.s3.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "us-east-1" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, true ] } ], "rules": [ { "conditions": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "us-east-1" ] } ], "endpoint": { "url": "https://{Bucket}.s3.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{Bucket}.s3.{Region}.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] }, { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] } ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "Region" }, "aws-global" ] } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseGlobalEndpoint" }, false ] } ], "endpoint": { "url": "https://{Bucket}.s3.{Region}.{partitionResult#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "error": "Invalid region: region was not a valid DNS name.", "type": "error" } ], "type": "tree" } ], "type": "tree" }, { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ], "assign": "url" }, { "fn": "stringEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "url" }, "scheme" ] }, "http" ] }, { "fn": "aws.isVirtualHostableS3Bucket", "argv": [ { "ref": "Bucket" }, true ] }, { "fn": "booleanEquals", "argv": [ { "ref": "ForcePathStyle" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, false ] }, { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, false ] } ], "rules": [ { "conditions": [ { "fn": "aws.partition", "argv": [ { "ref": "Region" } ], "assign": "partitionResult" } ], "rules": [ { "conditions": [ { "fn": "isValidHostLabel", "argv": [ { "ref": "Region" }, false ] } ], "rules": [ { "conditions": [], "endpoint": { "url": "{url#scheme}://{Bucket}.{url#authority}{url#path}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3", "signingRegion": "{Region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "error": "Invalid region: region was not a valid DNS name.", "type": "error" } ], "type": "tree" } ], "type": "tree" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "ForcePathStyle" }, false ] }, { "fn": "aws.parseArn", "argv": [ { "ref": "Bucket" } ], "assign": "bucketArn" } ], "rules": [ { "conditions": [ { "fn": "getAttr", "argv": [ { "ref": "bucketArn" }, "resourceId[0]" ], "assign": "arnType" }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "arnType" }, "" ] } ] } ], "rules": [ { "conditions": [ { "fn": "stringEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "bucketArn" }, "service" ] }, "s3-object-lambda" ] } ], "rules": [ { "conditions": [ { "fn": "stringEquals", "argv": [ { "ref": "arnType" }, "accesspoint" ] } ], "rules": [ { "conditions": [ { "fn": "getAttr", "argv": [ { "ref": "bucketArn" }, "resourceId[1]" ], "assign": "accessPointName" }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "ref": "accessPointName" }, "" ] } ] } ], "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseDualStack" }, true ] } ], "error": "S3 Object Lambda does not support Dual-stack", "type": "error" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "Accelerate" }, true ] } ], "error": "S3 Object Lambda does not support S3 Accelerate", "type": "error" }, { "conditions": [ { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "bucketArn" }, "region" ] }, "" ] } ] } ], "rules": [ { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "DisableAccessPoints" } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "DisableAccessPoints" }, true ] } ], "error": "Access points are not supported for this operation", "type": "error" }, { "conditions": [ { "fn": "not", "argv": [ { "fn": "isSet", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "bucketArn" }, "resourceId[2]" ] } ] } ] } ], "rules": [ { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "UseArnRegion" } ] }, { "fn": "booleanEquals", "argv": [ { "ref": "UseArnRegion" }, false ] }, { "fn": "not", "argv": [ { "fn": "stringEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "bucketArn" }, "region" ] }, "{Region}" ] } ] } ], "error": "Invalid configuration: region from ARN `{bucketArn#region}` does not match client region `{Region}` and UseArnRegion is `false`", "type": "error" }, { "conditions": [ { "fn": "aws.partition", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "bucketArn" }, "region" ] } ], "assign": "bucketPartition" } ], "rules": [ { "conditions": [ { "fn": "aws.partition", "argv": [ { "ref": "Region" } ], "assign": "partitionResult" } ], "rules": [ { "conditions": [ { "fn": "stringEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "bucketPartition" }, "name" ] }, { "fn": "getAttr", "argv": [ { "ref": "partitionResult" }, "name" ] } ] } ], "rules": [ { "conditions": [ { "fn": "isValidHostLabel", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "bucketArn" }, "region" ] }, true ] } ], "rules": [ { "conditions": [ { "fn": "stringEquals", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "bucketArn" }, "accountId" ] }, "" ] } ], "error": "Invalid ARN: Missing account id", "type": "error" }, { "conditions": [ { "fn": "isValidHostLabel", "argv": [ { "fn": "getAttr", "argv": [ { "ref": "bucketArn" }, "accountId" ] }, false ] } ], "rules": [ { "conditions": [ { "fn": "isValidHostLabel", "argv": [ { "ref": "accessPointName" }, false ] } ], "rules": [ { "conditions": [ { "fn": "isSet", "argv": [ { "ref": "Endpoint" } ] }, { "fn": "parseURL", "argv": [ { "ref": "Endpoint" } ], "assign": "url" } ], "endpoint": { "url": "{url#scheme}://{accessPointName}-{bucketArn#accountId}.{url#authority}{url#path}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3-object-lambda", "signingRegion": "{bucketArn#region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [ { "fn": "booleanEquals", "argv": [ { "ref": "UseFIPS" }, true ] } ], "endpoint": { "url": "https://{accessPointName}-{bucketArn#accountId}.s3-object-lambda-fips.{bucketArn#region}.{bucketPartition#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3-object-lambda", "signingRegion": "{bucketArn#region}" } ] }, "headers": {} }, "type": "endpoint" }, { "conditions": [], "endpoint": { "url": "https://{accessPointName}-{bucketArn#accountId}.s3-object-lambda.{bucketArn#region}.{bucketPartition#dnsSuffix}", "properties": { "authSchemes": [ { "disableDoubleEncoding": true, "name": "sigv4", "signingName": "s3-object-lambda", "signingRegion": "{bucketArn#region}" } ] }, "headers": {} }, "type": "endpoint" } ], "type": "tree" }, { "conditions": [], "error": "Invalid ARN: The access point name may only contain a-z, A-Z, 0-9 and `-`. Found: `{accessPointName}`", "type": "error" } ], "type": "tree" }, { "conditions": [], "error": "Invalid ARN: The account id may only contain a-z, A-Z, 0-9 and `-`. Found: `{bucketArn#accountId}`", "type": "error" } ], "type": "tree" }, { "conditions": [], "error": "Invalid region in ARN: `{bucketArn#region}` (invalid DNS name)", "type": "error" } ], "type": "tree" }, { "conditions": [], "error": "Client was configured for partition `{partitionResult#name}` but ARN (`{Bucket}`) has `{bucketPartition#name}`", "type": "error" } ], "type": "tree" } ], "type": "tree" } ], "type": "tree" }, { "conditions": [], "error": "Invalid ARN: The ARN may only contain a single resource component after `accesspoint`.", "type": "error" } ], "type": "tree" }, { "conditions": [], "error": "Invalid ARN: bucket ARN is missing a region", "type": "error" } ], "type": "tree" }, { "conditions": [], "error": "Invalid ARN: Expected a resource of the format `accesspoint:The prefix to use when evaluating an AND predicate: The prefix that an object must have to be\n included in the metrics results.
" } }, "Tags": { "target": "com.amazonaws.s3#TagSet", "traits": { "smithy.api#documentation": "The list of tags to use when evaluating an AND predicate.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Tag" } } }, "traits": { "smithy.api#documentation": "A conjunction (logical AND) of predicates, which is used in evaluating a metrics filter. The\n operator must have at least two predicates in any combination, and an object must match all of the\n predicates for the filter to apply.
" } }, "com.amazonaws.s3#AnalyticsConfiguration": { "type": "structure", "members": { "Id": { "target": "com.amazonaws.s3#AnalyticsId", "traits": { "smithy.api#documentation": "The ID that identifies the analytics configuration.
", "smithy.api#required": {} } }, "Filter": { "target": "com.amazonaws.s3#AnalyticsFilter", "traits": { "smithy.api#documentation": "The filter used to describe a set of objects for analyses. A filter must have exactly one prefix,\n one tag, or one conjunction (AnalyticsAndOperator). If no filter is provided, all objects will be\n considered in any analysis.
" } }, "StorageClassAnalysis": { "target": "com.amazonaws.s3#StorageClassAnalysis", "traits": { "smithy.api#documentation": "Contains data related to access patterns to be collected and made available to analyze the\n tradeoffs between different storage classes.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Specifies the configuration and any analyses for the analytics filter of an Amazon S3 bucket.
" } }, "com.amazonaws.s3#AnalyticsConfigurationList": { "type": "list", "member": { "target": "com.amazonaws.s3#AnalyticsConfiguration" } }, "com.amazonaws.s3#AnalyticsExportDestination": { "type": "structure", "members": { "S3BucketDestination": { "target": "com.amazonaws.s3#AnalyticsS3BucketDestination", "traits": { "smithy.api#documentation": "A destination signifying output to an S3 bucket.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Where to publish the analytics results.
" } }, "com.amazonaws.s3#AnalyticsFilter": { "type": "union", "members": { "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "The prefix to use when evaluating an analytics filter.
" } }, "Tag": { "target": "com.amazonaws.s3#Tag", "traits": { "smithy.api#documentation": "The tag to use when evaluating an analytics filter.
" } }, "And": { "target": "com.amazonaws.s3#AnalyticsAndOperator", "traits": { "smithy.api#documentation": "A conjunction (logical AND) of predicates, which is used in evaluating an analytics filter. The\n operator must have at least two predicates.
" } } }, "traits": { "smithy.api#documentation": "The filter used to describe a set of objects for analyses. A filter must have exactly one prefix,\n one tag, or one conjunction (AnalyticsAndOperator). If no filter is provided, all objects will be\n considered in any analysis.
" } }, "com.amazonaws.s3#AnalyticsId": { "type": "string" }, "com.amazonaws.s3#AnalyticsS3BucketDestination": { "type": "structure", "members": { "Format": { "target": "com.amazonaws.s3#AnalyticsS3ExportFileFormat", "traits": { "smithy.api#documentation": "Specifies the file format used when exporting data to Amazon S3.
", "smithy.api#required": {} } }, "BucketAccountId": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID that owns the destination S3 bucket. If no account ID is provided, the owner is not\n validated before exporting data.
\nAlthough this value is optional, we strongly recommend that you set it to help prevent problems\n if the destination bucket ownership changes.
\nThe Amazon Resource Name (ARN) of the bucket to which data is exported.
", "smithy.api#required": {} } }, "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "The prefix to use when exporting data. The prefix is prepended to all results.
" } } }, "traits": { "smithy.api#documentation": "Contains information about where to publish the analytics results.
" } }, "com.amazonaws.s3#AnalyticsS3ExportFileFormat": { "type": "enum", "members": { "CSV": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "CSV" } } } }, "com.amazonaws.s3#ArchiveStatus": { "type": "enum", "members": { "ARCHIVE_ACCESS": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ARCHIVE_ACCESS" } }, "DEEP_ARCHIVE_ACCESS": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "DEEP_ARCHIVE_ACCESS" } } } }, "com.amazonaws.s3#Body": { "type": "blob" }, "com.amazonaws.s3#Bucket": { "type": "structure", "members": { "Name": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket.
" } }, "CreationDate": { "target": "com.amazonaws.s3#CreationDate", "traits": { "smithy.api#documentation": "Date the bucket was created. This date can change when making changes to your bucket, such as\n editing its bucket policy.
" } }, "BucketRegion": { "target": "com.amazonaws.s3#BucketRegion", "traits": { "smithy.api#documentation": "\n BucketRegion indicates the Amazon Web Services region where the bucket is located. If the request\n contains at least one valid parameter, it is included in the response.
The Amazon Resource Name (ARN) of the S3 bucket. ARNs uniquely identify Amazon Web Services resources across all\n of Amazon Web Services.
\nThis parameter is only supported for S3 directory buckets. For more information, see Using tags with\n directory buckets.
\nIn terms of implementation, a Bucket is a resource.
" } }, "com.amazonaws.s3#BucketAccelerateStatus": { "type": "enum", "members": { "Enabled": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Enabled" } }, "Suspended": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Suspended" } } } }, "com.amazonaws.s3#BucketAlreadyExists": { "type": "structure", "members": {}, "traits": { "smithy.api#documentation": "The requested bucket name is not available. The bucket namespace is shared by all users of the\n system. Select a different name and try again.
", "smithy.api#error": "client", "smithy.api#httpError": 409 } }, "com.amazonaws.s3#BucketAlreadyOwnedByYou": { "type": "structure", "members": {}, "traits": { "smithy.api#documentation": "The bucket you tried to create already exists, and you own it. Amazon S3 returns this error in all Amazon Web Services\n Regions except in the North Virginia Region. For legacy compatibility, if you re-create an existing\n bucket that you already own in the North Virginia Region, Amazon S3 returns 200 OK and resets the bucket\n access control lists (ACLs).
", "smithy.api#error": "client", "smithy.api#httpError": 409 } }, "com.amazonaws.s3#BucketCannedACL": { "type": "enum", "members": { "private": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "private" } }, "public_read": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "public-read" } }, "public_read_write": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "public-read-write" } }, "authenticated_read": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "authenticated-read" } } } }, "com.amazonaws.s3#BucketInfo": { "type": "structure", "members": { "DataRedundancy": { "target": "com.amazonaws.s3#DataRedundancy", "traits": { "smithy.api#documentation": "The number of Zone (Availability Zone or Local Zone) that's used for redundancy for the bucket.
" } }, "Type": { "target": "com.amazonaws.s3#BucketType", "traits": { "smithy.api#documentation": "The type of bucket.
" } } }, "traits": { "smithy.api#documentation": "Specifies the information about the bucket that will be created. For more information about\n directory buckets, see Directory buckets in the\n Amazon S3 User Guide.
\nThis functionality is only supported by directory buckets.
\nA lifecycle rule for individual objects in an Amazon S3 bucket.
", "smithy.api#required": {}, "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Rule" } } }, "traits": { "smithy.api#documentation": "Specifies the lifecycle configuration for objects in an Amazon S3 bucket. For more information, see\n Object Lifecycle\n Management in the Amazon S3 User Guide.
" } }, "com.amazonaws.s3#BucketLocationConstraint": { "type": "enum", "members": { "af_south_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "af-south-1" } }, "ap_east_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ap-east-1" } }, "ap_northeast_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ap-northeast-1" } }, "ap_northeast_2": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ap-northeast-2" } }, "ap_northeast_3": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ap-northeast-3" } }, "ap_south_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ap-south-1" } }, "ap_south_2": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ap-south-2" } }, "ap_southeast_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ap-southeast-1" } }, "ap_southeast_2": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ap-southeast-2" } }, "ap_southeast_3": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ap-southeast-3" } }, "ap_southeast_4": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ap-southeast-4" } }, "ap_southeast_5": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ap-southeast-5" } }, "ca_central_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ca-central-1" } }, "cn_north_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "cn-north-1" } }, "cn_northwest_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "cn-northwest-1" } }, "EU": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "EU" } }, "eu_central_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "eu-central-1" } }, "eu_central_2": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "eu-central-2" } }, "eu_north_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "eu-north-1" } }, "eu_south_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "eu-south-1" } }, "eu_south_2": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "eu-south-2" } }, "eu_west_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "eu-west-1" } }, "eu_west_2": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "eu-west-2" } }, "eu_west_3": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "eu-west-3" } }, "il_central_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "il-central-1" } }, "me_central_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "me-central-1" } }, "me_south_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "me-south-1" } }, "sa_east_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "sa-east-1" } }, "us_east_2": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "us-east-2" } }, "us_gov_east_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "us-gov-east-1" } }, "us_gov_west_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "us-gov-west-1" } }, "us_west_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "us-west-1" } }, "us_west_2": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "us-west-2" } } } }, "com.amazonaws.s3#BucketLocationName": { "type": "string" }, "com.amazonaws.s3#BucketLoggingStatus": { "type": "structure", "members": { "LoggingEnabled": { "target": "com.amazonaws.s3#LoggingEnabled" } }, "traits": { "smithy.api#documentation": "Container for logging status information.
" } }, "com.amazonaws.s3#BucketLogsPermission": { "type": "enum", "members": { "FULL_CONTROL": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "FULL_CONTROL" } }, "READ": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "READ" } }, "WRITE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "WRITE" } } } }, "com.amazonaws.s3#BucketName": { "type": "string" }, "com.amazonaws.s3#BucketRegion": { "type": "string" }, "com.amazonaws.s3#BucketType": { "type": "enum", "members": { "Directory": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Directory" } } } }, "com.amazonaws.s3#BucketVersioningStatus": { "type": "enum", "members": { "Enabled": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Enabled" } }, "Suspended": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Suspended" } } } }, "com.amazonaws.s3#Buckets": { "type": "list", "member": { "target": "com.amazonaws.s3#Bucket", "traits": { "smithy.api#xmlName": "Bucket" } } }, "com.amazonaws.s3#BypassGovernanceRetention": { "type": "boolean" }, "com.amazonaws.s3#BytesProcessed": { "type": "long" }, "com.amazonaws.s3#BytesReturned": { "type": "long" }, "com.amazonaws.s3#BytesScanned": { "type": "long" }, "com.amazonaws.s3#CORSConfiguration": { "type": "structure", "members": { "CORSRules": { "target": "com.amazonaws.s3#CORSRules", "traits": { "smithy.api#documentation": "A set of origins and methods (cross-origin access that you want to allow). You can add up to 100\n rules to the configuration.
", "smithy.api#required": {}, "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "CORSRule" } } }, "traits": { "smithy.api#documentation": "Describes the cross-origin access configuration for objects in an Amazon S3 bucket. For more information,\n see Enabling Cross-Origin Resource\n Sharing in the Amazon S3 User Guide.
" } }, "com.amazonaws.s3#CORSRule": { "type": "structure", "members": { "ID": { "target": "com.amazonaws.s3#ID", "traits": { "smithy.api#documentation": "Unique identifier for the rule. The value cannot be longer than 255 characters.
" } }, "AllowedHeaders": { "target": "com.amazonaws.s3#AllowedHeaders", "traits": { "smithy.api#documentation": "Headers that are specified in the Access-Control-Request-Headers header. These headers\n are allowed in a preflight OPTIONS request. In response to any preflight OPTIONS request, Amazon S3 returns\n any requested headers that are allowed.
An HTTP method that you allow the origin to execute. Valid values are GET,\n PUT, HEAD, POST, and DELETE.
One or more origins you want customers to be able to access the bucket from.
", "smithy.api#required": {}, "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "AllowedOrigin" } }, "ExposeHeaders": { "target": "com.amazonaws.s3#ExposeHeaders", "traits": { "smithy.api#documentation": "One or more headers in the response that you want customers to be able to access from their\n applications (for example, from a JavaScript XMLHttpRequest object).
The time in seconds that your browser is to cache the preflight response for the specified\n resource.
" } } }, "traits": { "smithy.api#documentation": "Specifies a cross-origin access rule for an Amazon S3 bucket.
" } }, "com.amazonaws.s3#CORSRules": { "type": "list", "member": { "target": "com.amazonaws.s3#CORSRule" } }, "com.amazonaws.s3#CSVInput": { "type": "structure", "members": { "FileHeaderInfo": { "target": "com.amazonaws.s3#FileHeaderInfo", "traits": { "smithy.api#documentation": "Describes the first line of input. Valid values are:
\n\n NONE: First line is not a header.
\n IGNORE: First line is a header, but you can't use the header values to indicate the\n column in an expression. You can use column position (such as _1, _2, \u2026) to indicate the column\n (SELECT s._1 FROM OBJECT s).
\n Use: First line is a header, and you can use the header value to identify a column\n in an expression (SELECT \"name\" FROM OBJECT).
A single character used to indicate that a row should be ignored when the character is present at\n the start of that row. You can specify any character to indicate a comment line. The default character\n is #.
Default: #\n
A single character used for escaping the quotation mark character inside an already escaped value.\n For example, the value \"\"\" a , b \"\"\" is parsed as \" a , b \".
A single character used to separate individual records in the input. Instead of the default value,\n you can specify an arbitrary delimiter.
" } }, "FieldDelimiter": { "target": "com.amazonaws.s3#FieldDelimiter", "traits": { "smithy.api#documentation": "A single character used to separate individual fields in a record. You can specify an arbitrary\n delimiter.
" } }, "QuoteCharacter": { "target": "com.amazonaws.s3#QuoteCharacter", "traits": { "smithy.api#documentation": "A single character used for escaping when the field delimiter is part of the value. For example, if\n the value is a, b, Amazon S3 wraps this field value in quotation marks, as follows: \" a ,\n b \".
Type: String
\nDefault: \"\n
Ancestors: CSV\n
Specifies that CSV field values may contain quoted record delimiters and such records should be\n allowed. Default value is FALSE. Setting this value to TRUE may lower performance.
" } } }, "traits": { "smithy.api#documentation": "Describes how an uncompressed comma-separated values (CSV)-formatted input object is\n formatted.
" } }, "com.amazonaws.s3#CSVOutput": { "type": "structure", "members": { "QuoteFields": { "target": "com.amazonaws.s3#QuoteFields", "traits": { "smithy.api#documentation": "Indicates whether to use quotation marks around output fields.
\n\n ALWAYS: Always use quotation marks for output fields.
\n ASNEEDED: Use quotation marks for output fields when needed.
The single character used for escaping the quote character inside an already escaped value.
" } }, "RecordDelimiter": { "target": "com.amazonaws.s3#RecordDelimiter", "traits": { "smithy.api#documentation": "A single character used to separate individual records in the output. Instead of the default value,\n you can specify an arbitrary delimiter.
" } }, "FieldDelimiter": { "target": "com.amazonaws.s3#FieldDelimiter", "traits": { "smithy.api#documentation": "The value used to separate individual fields in a record. You can specify an arbitrary\n delimiter.
" } }, "QuoteCharacter": { "target": "com.amazonaws.s3#QuoteCharacter", "traits": { "smithy.api#documentation": "A single character used for escaping when the field delimiter is part of the value. For example, if\n the value is a, b, Amazon S3 wraps this field value in quotation marks, as follows: \" a ,\n b \".
Describes how uncompressed comma-separated values (CSV)-formatted results are formatted.
" } }, "com.amazonaws.s3#CacheControl": { "type": "string" }, "com.amazonaws.s3#Checksum": { "type": "structure", "members": { "ChecksumCRC32": { "target": "com.amazonaws.s3#ChecksumCRC32", "traits": { "smithy.api#documentation": "The Base64 encoded, 32-bit CRC32 checksum of the object. This checksum is only be present if the checksum was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the object. This checksum is only present if the checksum was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the object. This checksum is present\n if the object was uploaded with the CRC64NVME checksum algorithm, or if the object was\n uploaded without a checksum (and Amazon S3 added the default checksum, CRC64NVME, to the\n uploaded object). For more information, see Checking object integrity in\n the Amazon S3 User Guide.
The Base64 encoded, 160-bit SHA1 digest of the object. This will only be present if the object was uploaded\n with the object. When you use the API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 digest of the object. This will only be present if the object was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The checksum type that is used to calculate the object\u2019s checksum value. For more information, see\n Checking\n object integrity in the Amazon S3 User Guide.
" } } }, "traits": { "smithy.api#documentation": "Contains all the possible checksum or digest values for an object.
" } }, "com.amazonaws.s3#ChecksumAlgorithm": { "type": "enum", "members": { "CRC32": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "CRC32" } }, "CRC32C": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "CRC32C" } }, "SHA1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "SHA1" } }, "SHA256": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "SHA256" } }, "CRC64NVME": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "CRC64NVME" } } } }, "com.amazonaws.s3#ChecksumAlgorithmList": { "type": "list", "member": { "target": "com.amazonaws.s3#ChecksumAlgorithm" } }, "com.amazonaws.s3#ChecksumCRC32": { "type": "string" }, "com.amazonaws.s3#ChecksumCRC32C": { "type": "string" }, "com.amazonaws.s3#ChecksumCRC64NVME": { "type": "string" }, "com.amazonaws.s3#ChecksumMode": { "type": "enum", "members": { "ENABLED": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ENABLED" } } } }, "com.amazonaws.s3#ChecksumSHA1": { "type": "string" }, "com.amazonaws.s3#ChecksumSHA256": { "type": "string" }, "com.amazonaws.s3#ChecksumType": { "type": "enum", "members": { "COMPOSITE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "COMPOSITE" } }, "FULL_OBJECT": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "FULL_OBJECT" } } } }, "com.amazonaws.s3#ClientToken": { "type": "string" }, "com.amazonaws.s3#Code": { "type": "string" }, "com.amazonaws.s3#Comments": { "type": "string" }, "com.amazonaws.s3#CommonPrefix": { "type": "structure", "members": { "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "Container for the specified common prefix.
" } } }, "traits": { "smithy.api#documentation": "Container for all (if there are any) keys between Prefix and the next occurrence of the string\n specified by a delimiter. CommonPrefixes lists keys that act like subdirectories in the directory\n specified by Prefix. For example, if the prefix is notes/ and the delimiter is a slash (/) as in\n notes/summer/july, the common prefix is notes/summer/.
" } }, "com.amazonaws.s3#CommonPrefixList": { "type": "list", "member": { "target": "com.amazonaws.s3#CommonPrefix" } }, "com.amazonaws.s3#CompleteMultipartUpload": { "type": "operation", "input": { "target": "com.amazonaws.s3#CompleteMultipartUploadRequest" }, "output": { "target": "com.amazonaws.s3#CompleteMultipartUploadOutput" }, "traits": { "smithy.api#documentation": "Completes a multipart upload by assembling previously uploaded parts.
\nYou first initiate the multipart upload and then upload all parts using the UploadPart operation or the\n UploadPartCopy\n operation. After successfully uploading all relevant parts of an upload, you call this\n CompleteMultipartUpload operation to complete the upload. Upon receiving this request,\n Amazon S3 concatenates all the parts in ascending order by part number to create a new object. In the\n CompleteMultipartUpload request, you must provide the parts list and ensure that the parts list is\n complete. The CompleteMultipartUpload API operation concatenates the parts that you provide in the list.\n For each part in the list, you must provide the PartNumber value and the ETag\n value that are returned after that part was uploaded.
The processing of a CompleteMultipartUpload request could take several minutes to finalize. After\n Amazon S3 begins processing the request, it sends an HTTP response header that specifies a 200\n OK response. While processing is in progress, Amazon S3 periodically sends white space characters to\n keep the connection from timing out. A request could fail after the initial 200 OK response\n has been sent. This means that a 200 OK response can contain either a success or an error.\n The error response might be embedded in the 200 OK response. If you call this API operation\n directly, make sure to design your application to parse the contents of the response and handle it\n appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition. The SDKs detect the embedded error and\n apply error handling per your configuration settings (including automatically retrying the request as\n appropriate). If the condition persists, the SDKs throw an exception (or, for the SDKs that don't use\n exceptions, they return an error).
Note that if CompleteMultipartUpload fails, applications should be prepared to retry\n any failed requests (including 500 error responses). For more information, see Amazon S3 Error Best\n Practices.
You can't use Content-Type: application/x-www-form-urlencoded for the\n CompleteMultipartUpload requests. Also, if you don't provide a Content-Type header,\n CompleteMultipartUpload can still return a 200 OK response.
For more information about multipart uploads, see Uploading Objects Using Multipart Upload in\n the Amazon S3 User Guide.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n General purpose bucket permissions - For information\n about permissions required to use the multipart upload API, see Multipart Upload and Permissions in\n the Amazon S3 User Guide.
\nIf you provide an additional checksum value in your MultipartUpload requests and the\n object is encrypted with Key Management Service, you must have permission to use the\n kms:Decrypt action for the CompleteMultipartUpload request to\n succeed.
\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
If the object is encrypted with SSE-KMS, you must also have the\n kms:GenerateDataKey and kms:Decrypt permissions in IAM\n identity-based policies and KMS key policies for the KMS key.
Error Code: EntityTooSmall\n
Description: Your proposed upload is smaller than the minimum allowed object size.\n Each part must be at least 5 MB in size, except the last part.
\nHTTP Status Code: 400 Bad Request
\nError Code: InvalidPart\n
Description: One or more of the specified parts could not be found. The part might not\n have been uploaded, or the specified ETag might not have matched the uploaded part's\n ETag.
\nHTTP Status Code: 400 Bad Request
\nError Code: InvalidPartOrder\n
Description: The list of parts was not in ascending order. The parts list must be\n specified in order by part number.
\nHTTP Status Code: 400 Bad Request
\nError Code: NoSuchUpload\n
Description: The specified multipart upload does not exist. The upload ID might be\n invalid, or the multipart upload might have been aborted or completed.
\nHTTP Status Code: 404 Not Found
\n\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following operations are related to CompleteMultipartUpload:
\n UploadPart\n
\n\n AbortMultipartUpload\n
\n\n ListParts\n
\n\n ListMultipartUploads\n
\nThe URI that identifies the newly created object.
" } }, "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket that contains the newly created object. Does not return the access point ARN or access point\n alias if used.
\nAccess points are not supported by directory buckets.
\nThe object key of the newly created object.
" } }, "Expiration": { "target": "com.amazonaws.s3#Expiration", "traits": { "smithy.api#documentation": "If the object expiration is configured, this will contain the expiration date\n (expiry-date) and rule ID (rule-id). The value of rule-id is\n URL-encoded.
This functionality is not supported for directory buckets.
\nEntity tag that identifies the newly created object's data. Objects with different object data will\n have different entity tags. The entity tag is an opaque string. The entity tag may or may not be an MD5\n digest of the object data. If the entity tag is not an MD5 digest of the object data, it will contain\n one or more nonhexadecimal characters and/or will consist of less than 32 or more than 32 hexadecimal\n digits. For more information about how the entity tag is calculated, see Checking object integrity in\n the Amazon S3 User Guide.
" } }, "ChecksumCRC32": { "target": "com.amazonaws.s3#ChecksumCRC32", "traits": { "smithy.api#documentation": "The Base64 encoded, 32-bit CRC32 checksum of the object. This checksum is only be present if the checksum was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the object. This checksum is only present if the checksum was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This header specifies the Base64 encoded, 64-bit CRC64NVME\n checksum of the object. The CRC64NVME checksum is always a full object checksum. For more\n information, see Checking object integrity in the Amazon S3\n User Guide.
The Base64 encoded, 160-bit SHA1 digest of the object. This will only be present if the object was uploaded\n with the object. When you use the API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 digest of the object. This will only be present if the object was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The checksum type, which determines how part-level checksums are combined to create an object-level\n checksum for multipart objects. You can use this header as a data integrity check to verify that the\n checksum type that is received is the same checksum type that was specified during the\n CreateMultipartUpload request. For more information, see Checking object integrity in the Amazon S3\n User Guide.
The server-side encryption algorithm used when storing this object in Amazon S3.
\nWhen accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side\n encryption option is aws:fsx.
Version ID of the newly created object, in case the bucket has versioning turned on.
\nThis functionality is not supported for directory buckets.
\nIf present, indicates the ID of the KMS key that was used for object encryption.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-aws-kms-key-id" } }, "BucketKeyEnabled": { "target": "com.amazonaws.s3#BucketKeyEnabled", "traits": { "smithy.api#documentation": "Indicates whether the multipart upload uses an S3 Bucket Key for server-side encryption with\n Key Management Service (KMS) keys (SSE-KMS).
", "smithy.api#httpHeader": "x-amz-server-side-encryption-bucket-key-enabled" } }, "RequestCharged": { "target": "com.amazonaws.s3#RequestCharged", "traits": { "smithy.api#httpHeader": "x-amz-request-charged" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "CompleteMultipartUploadResult" } }, "com.amazonaws.s3#CompleteMultipartUploadRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "Name of the bucket to which the multipart upload was initiated.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Object key for which the multipart upload was initiated.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Key" } } }, "MultipartUpload": { "target": "com.amazonaws.s3#CompletedMultipartUpload", "traits": { "smithy.api#documentation": "The container for the multipart upload request information.
", "smithy.api#httpPayload": {}, "smithy.api#xmlName": "CompleteMultipartUpload" } }, "UploadId": { "target": "com.amazonaws.s3#MultipartUploadId", "traits": { "smithy.api#documentation": "ID for the initiated multipart upload.
", "smithy.api#httpQuery": "uploadId", "smithy.api#required": {} } }, "ChecksumCRC32": { "target": "com.amazonaws.s3#ChecksumCRC32", "traits": { "smithy.api#documentation": "This header can be used as a data integrity check to verify that the data received is the same data that was originally sent.\n This header specifies the Base64 encoded, 32-bit CRC32 checksum of the object. For more information, see\n Checking object integrity in the\n Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data that was originally sent.\n This header specifies the Base64 encoded, 32-bit CRC32C checksum of the object. For more information, see\n Checking object integrity in the\n Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This header specifies the Base64 encoded, 64-bit CRC64NVME\n checksum of the object. The CRC64NVME checksum is always a full object checksum. For more\n information, see Checking object integrity in the Amazon S3\n User Guide.
This header can be used as a data integrity check to verify that the data received is the same data that was originally sent.\n This header specifies the Base64 encoded, 160-bit SHA1 digest of the object. For more information, see\n Checking object integrity in the\n Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data that was originally sent.\n This header specifies the Base64 encoded, 256-bit SHA256 digest of the object. For more information, see\n Checking object integrity in the\n Amazon S3 User Guide.
This header specifies the checksum type of the object, which determines how part-level checksums are\n combined to create an object-level checksum for multipart objects. You can use this header as a data\n integrity check to verify that the checksum type that is received is the same checksum that was\n specified. If the checksum type doesn\u2019t match the checksum type that was specified for the object during\n the CreateMultipartUpload request, it\u2019ll result in a BadDigest error. For more\n information, see Checking object integrity in the Amazon S3 User Guide.
The expected total object size of the multipart upload request. If there\u2019s a mismatch between the\n specified object size value and the actual object size value, it results in an HTTP 400\n InvalidRequest error.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Uploads the object only if the ETag (entity tag) value provided during the WRITE operation matches\n the ETag of the object in S3. If the ETag values do not match, the operation returns a 412\n Precondition Failed error.
If a conflicting operation occurs during the upload S3 returns a 409\n ConditionalRequestConflict response. On a 409 failure you should fetch the object's ETag,\n re-initiate the multipart upload with CreateMultipartUpload, and re-upload each\n part.
Expects the ETag value as a string.
\nFor more information about conditional requests, see RFC 7232, or Conditional requests in the\n Amazon S3 User Guide.
", "smithy.api#httpHeader": "If-Match" } }, "IfNoneMatch": { "target": "com.amazonaws.s3#IfNoneMatch", "traits": { "smithy.api#documentation": "Uploads the object only if the object key name does not already exist in the bucket specified.\n Otherwise, Amazon S3 returns a 412 Precondition Failed error.
If a conflicting operation occurs during the upload S3 returns a 409\n ConditionalRequestConflict response. On a 409 failure you should re-initiate the multipart\n upload with CreateMultipartUpload and re-upload each part.
Expects the '*' (asterisk) character.
\nFor more information about conditional requests, see RFC 7232, or Conditional requests in the\n Amazon S3 User Guide.
", "smithy.api#httpHeader": "If-None-Match" } }, "SSECustomerAlgorithm": { "target": "com.amazonaws.s3#SSECustomerAlgorithm", "traits": { "smithy.api#documentation": "The server-side encryption (SSE) algorithm used to encrypt the object. This parameter is required\n only when the object was created using a checksum algorithm or if your bucket policy requires the use of\n SSE-C. For more information, see Protecting data using SSE-C keys in the Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\nThe server-side encryption (SSE) customer managed key. This parameter is needed only when the object was created using a checksum algorithm. \n For more information, see\n Protecting data using SSE-C keys in the\n Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\nThe MD5 server-side encryption (SSE) customer managed key. This parameter is needed only when the object was created using a checksum \n algorithm. For more information,\n see Protecting data using SSE-C keys in the\n Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\nArray of CompletedPart data types.
\nIf you do not supply a valid Part with your request, the service sends back an HTTP 400\n response.
The container for the completed multipart upload details.
" } }, "com.amazonaws.s3#CompletedPart": { "type": "structure", "members": { "ETag": { "target": "com.amazonaws.s3#ETag", "traits": { "smithy.api#documentation": "Entity tag returned when the part was uploaded.
" } }, "ChecksumCRC32": { "target": "com.amazonaws.s3#ChecksumCRC32", "traits": { "smithy.api#documentation": "The Base64 encoded, 32-bit CRC32 checksum of the part. This checksum is present if the\n multipart upload request was created with the CRC32 checksum algorithm. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the part. This checksum is present if the\n multipart upload request was created with the CRC32C checksum algorithm. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the part. This checksum is present if\n the multipart upload request was created with the CRC64NVME checksum algorithm to the\n uploaded object). For more information, see Checking object integrity in\n the Amazon S3 User Guide.
The Base64 encoded, 160-bit SHA1 checksum of the part. This checksum is present if the\n multipart upload request was created with the SHA1 checksum algorithm. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 checksum of the part. This checksum is present if\n the multipart upload request was created with the SHA256 checksum algorithm. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
Part number that identifies the part. This is a positive integer between 1 and 10,000.
\n\n General purpose buckets - In\n CompleteMultipartUpload, when a additional checksum (including\n x-amz-checksum-crc32, x-amz-checksum-crc32c,\n x-amz-checksum-sha1, or x-amz-checksum-sha256) is applied to each\n part, the PartNumber must start at 1 and the part numbers must be consecutive.\n Otherwise, Amazon S3 generates an HTTP 400 Bad Request status code and an\n InvalidPartOrder error code.
\n Directory buckets - In\n CompleteMultipartUpload, the PartNumber must start at 1 and the part\n numbers must be consecutive.
Details of the parts that were uploaded.
" } }, "com.amazonaws.s3#CompletedPartList": { "type": "list", "member": { "target": "com.amazonaws.s3#CompletedPart" } }, "com.amazonaws.s3#CompressionType": { "type": "enum", "members": { "NONE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "NONE" } }, "GZIP": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "GZIP" } }, "BZIP2": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "BZIP2" } } } }, "com.amazonaws.s3#Condition": { "type": "structure", "members": { "HttpErrorCodeReturnedEquals": { "target": "com.amazonaws.s3#HttpErrorCodeReturnedEquals", "traits": { "smithy.api#documentation": "The HTTP error code when the redirect is applied. In the event of an error, if the error code equals\n this value, then the specified redirect is applied. Required when parent element Condition\n is specified and sibling KeyPrefixEquals is not specified. If both are specified, then both\n must be true for the redirect to be applied.
The object key name prefix when the redirect is applied. For example, to redirect requests for\n ExamplePage.html, the key prefix will be ExamplePage.html. To redirect\n request for all pages with the prefix docs/, the key prefix will be /docs,\n which identifies all objects in the docs/ folder. Required when the parent element\n Condition is specified and sibling HttpErrorCodeReturnedEquals is not\n specified. If both conditions are specified, both must be true for the redirect to be applied.
Replacement must be made for object keys containing special characters (such as carriage returns) when using \n XML requests. For more information, see \n XML related object key constraints.
\nA container for describing a condition that must be met for the specified redirect to apply. For\n example, 1. If request is for pages in the /docs folder, redirect to the\n /documents folder. 2. If request results in HTTP error 4xx, redirect request to another\n host where you might process the error.
End of support notice: Beginning October 1, 2025, Amazon S3 will discontinue support for creating new Email Grantee Access Control Lists (ACL). \n Email Grantee ACLs created prior to this date will continue to work and remain accessible through the Amazon Web Services Management Console, Command Line Interface (CLI), SDKs, \n and REST API. However, you will no longer be able to create new Email Grantee ACLs.\n
\nThis change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nCreates a copy of an object that is already stored in Amazon S3.
\nYou can store individual objects of up to 5 TB in Amazon S3. You create a copy of your object up to 5\n GB in size in a single atomic action using this API. However, to copy an object greater than 5 GB, you\n must use the multipart upload Upload Part - Copy (UploadPartCopy) API. For more information, see\n Copy Object\n Using the REST Multipart Upload API.
\nYou can copy individual objects between general purpose buckets, between directory buckets, and between\n general purpose buckets and directory buckets.
\nAmazon S3 supports copy operations using Multi-Region Access Points only as a destination when\n using the Multi-Region Access Point ARN.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
VPC endpoints don't support cross-Region requests (including copies). If you're using VPC\n endpoints, your source and destination buckets should be in the same Amazon Web Services Region as your VPC\n endpoint.
\nBoth the Region that you want to copy the object from and the Region that you want to copy the\n object to must be enabled for your account. For more information about how to enable a Region for your\n account, see Enable\n or disable a Region for standalone accounts in the Amazon Web Services Account Management\n Guide.
\nAmazon S3 transfer acceleration does not support cross-Region copies. If you request a cross-Region\n copy using a transfer acceleration endpoint, you get a 400 Bad Request error. For more\n information, see Transfer Acceleration.
All CopyObject requests must be authenticated and signed by using IAM\n credentials (access key ID and secret access key for the IAM identities). All headers with the\n x-amz- prefix, including x-amz-copy-source, must be signed. For more\n information, see REST Authentication.
\n Directory buckets - You must use the IAM\n credentials to authenticate and authorize your access to the CopyObject API\n operation, instead of using the temporary security credentials through the\n CreateSession API operation.
Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.
\nYou must have read access to the source object and\n write access to the destination bucket.
\n\n General purpose bucket permissions - You must have\n permissions in an IAM policy based on the source and destination bucket types in a\n CopyObject operation.
If the source object is in a general purpose bucket, you must have \n s3:GetObject\n permission to read the source object that is\n being copied.
If the destination bucket is a general purpose bucket, you must have \n s3:PutObject\n permission to write the object copy to the\n destination bucket.
\n Directory bucket permissions - You must have\n permissions in a bucket policy or an IAM identity-based policy based on the source and destination bucket types\n in a CopyObject operation.
If the source object that you want to copy is in a directory bucket, you must have\n the \n s3express:CreateSession\n permission in\n the Action element of a policy to read the object. By default, the session is\n in the ReadWrite mode. If you want to restrict the access, you can explicitly\n set the s3express:SessionMode condition key to ReadOnly on the\n copy source bucket.
If the copy destination is a directory bucket, you must have the \n s3express:CreateSession\n permission in the\n Action element of a policy to write the object to the destination. The\n s3express:SessionMode condition key can't be set to ReadOnly\n on the copy destination bucket.
If the object is encrypted with SSE-KMS, you must also have the\n kms:GenerateDataKey and kms:Decrypt permissions in IAM\n identity-based policies and KMS key policies for the KMS key.
For example policies, see Example\n bucket policies for S3 Express One Zone and Amazon Web Services\n Identity and Access Management (IAM) identity-based policies for S3 Express One Zone in the\n Amazon S3 User Guide.
\nWhen the request is an HTTP 1.1 request, the response is chunk encoded. When the request is\n not an HTTP 1.1 request, the response would not contain the Content-Length. You\n always need to read the entire response body to check if the copy succeeds.
If the copy is successful, you receive a response with information about the copied\n object.
\nA copy request might return an error when Amazon S3 receives the copy request or while Amazon S3 is\n copying the files. A 200 OK response can contain either a success or an\n error.
If the error occurs before the copy action starts, you receive a standard Amazon S3\n error.
\nIf the error occurs during the copy operation, the error response is embedded in the\n 200 OK response. For example, in a cross-region copy, you may encounter\n throttling and receive a 200 OK response. For more information, see Resolve the Error\n 200 response when copying objects to Amazon S3. The 200 OK status code\n means the copy was accepted, but it doesn't mean the copy is complete. Another example is\n when you disconnect from Amazon S3 before the copy is complete, Amazon S3 might cancel the copy and\n you may receive a 200 OK response. You must stay connected to Amazon S3 until the\n entire response is successfully received and processed.
If you call this API operation directly, make sure to design your application to parse\n the content of the response and handle it appropriately. If you use Amazon Web Services SDKs, SDKs\n handle this condition. The SDKs detect the embedded error and apply error handling per\n your configuration settings (including automatically retrying the request as appropriate).\n If the condition persists, the SDKs throw an exception (or, for the SDKs that don't use\n exceptions, they return an error).
\nThe copy request charge is based on the storage class and Region that you specify for the\n destination object. The request can also result in a data retrieval charge for the source if the\n source storage class bills for data retrieval. If the copy source is in a different region, the\n data transfer is billed to the copy source account. For pricing information, see Amazon S3 pricing.
\n\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
\n Amazon S3 on Outposts - When you use this action with\n S3 on Outposts through the REST API, you must direct requests to the S3 on Outposts hostname. The\n S3 on Outposts hostname takes the form\n \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com.\n The hostname isn't required when you use the Amazon Web Services CLI or SDKs.
The following operations are related to CopyObject:
Container for all response elements.
", "smithy.api#httpPayload": {} } }, "Expiration": { "target": "com.amazonaws.s3#Expiration", "traits": { "smithy.api#documentation": "If the object expiration is configured, the response includes this header.
\nObject expiration information is not returned in directory buckets and this header returns the\n value \"NotImplemented\" in all responses for directory buckets.
Version ID of the source object that was copied.
\nThis functionality is not supported when the source object is in a directory bucket.
\nVersion ID of the newly created copy.
\nThis functionality is not supported for directory buckets.
\nThe server-side encryption algorithm used when you store this object in Amazon S3 or Amazon FSx.
\nWhen accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side\n encryption option is aws:fsx.
If server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to confirm the encryption algorithm that's used.
\nThis functionality is not supported for directory buckets.
\nIf server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to provide the round-trip message integrity verification of the customer-provided\n encryption key.
\nThis functionality is not supported for directory buckets.
\nIf present, indicates the ID of the KMS key that was used for object encryption.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-aws-kms-key-id" } }, "SSEKMSEncryptionContext": { "target": "com.amazonaws.s3#SSEKMSEncryptionContext", "traits": { "smithy.api#documentation": "If present, indicates the Amazon Web Services KMS Encryption Context to use for object encryption. The value of\n this header is a Base64 encoded UTF-8 string holding JSON with the encryption context key-value\n pairs.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-context" } }, "BucketKeyEnabled": { "target": "com.amazonaws.s3#BucketKeyEnabled", "traits": { "smithy.api#documentation": "Indicates whether the copied object uses an S3 Bucket Key for server-side encryption with Key Management Service\n (KMS) keys (SSE-KMS).
", "smithy.api#httpHeader": "x-amz-server-side-encryption-bucket-key-enabled" } }, "RequestCharged": { "target": "com.amazonaws.s3#RequestCharged", "traits": { "smithy.api#httpHeader": "x-amz-request-charged" } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#CopyObjectRequest": { "type": "structure", "members": { "ACL": { "target": "com.amazonaws.s3#ObjectCannedACL", "traits": { "smithy.api#documentation": "The canned access control list (ACL) to apply to the object.
\nWhen you copy an object, the ACL metadata is not preserved and is set to private by\n default. Only the owner has full access control. To override the default ACL setting, specify a new ACL\n when you generate a copy request. For more information, see Using ACLs.
If the destination bucket that you're copying objects to uses the bucket owner enforced setting for\n S3 Object Ownership, ACLs are disabled and no longer affect permissions. Buckets that use this setting\n only accept PUT requests that don't specify an ACL or PUT requests that\n specify bucket owner full control ACLs, such as the bucket-owner-full-control canned ACL or\n an equivalent form of this ACL expressed in the XML format. For more information, see Controlling ownership\n of objects and disabling ACLs in the Amazon S3 User Guide.
If your destination bucket uses the bucket owner enforced setting for Object Ownership, all\n objects written to the bucket by any account will be owned by the bucket owner.
\nThis functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nThe name of the destination bucket.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
Copying objects across different Amazon Web Services Regions isn't supported when the source or destination\n bucket is in Amazon Web Services Local Zones. The source and destination buckets must have the same parent Amazon Web Services Region.\n Otherwise, you get an HTTP 400 Bad Request error with the error code\n InvalidRequest.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts,\n you must use the Outpost bucket access point ARN or the access point alias for the destination bucket.\n You can only copy objects within the same Outpost bucket. It's not supported to copy objects across\n different Amazon Web Services Outposts, between buckets on the same Outposts, or between Outposts buckets and any\n other bucket types. For more information about S3 on Outposts, see What is S3 on Outposts? in the\n S3 on Outposts guide. When you use this action with S3 on Outposts through the REST\n API, you must direct requests to the S3 on Outposts hostname, in the format\n \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com.\n The hostname isn't required when you use the Amazon Web Services CLI or SDKs.
Specifies the caching behavior along the request/reply chain.
", "smithy.api#httpHeader": "Cache-Control" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm that you want Amazon S3 to use to create the checksum for the object. For more information, see\n Checking object integrity in\n the Amazon S3 User Guide.
\nWhen you copy an object, if the source object has a checksum, that checksum value will be copied to\n the new object by default. If the CopyObject request does not include this\n x-amz-checksum-algorithm header, the checksum algorithm will be copied from the source\n object to the destination object (if it's present on the source object). You can optionally specify a\n different checksum algorithm to use with the x-amz-checksum-algorithm header. Unrecognized\n or unsupported values will respond with the HTTP status code 400 Bad Request.
For directory buckets, when you use Amazon Web Services SDKs, CRC32 is the default checksum algorithm that's used for performance.
Specifies presentational information for the object. Indicates whether an object should be displayed\n in a web browser or downloaded as a file. It allows specifying the desired filename for the downloaded\n file.
", "smithy.api#httpHeader": "Content-Disposition" } }, "ContentEncoding": { "target": "com.amazonaws.s3#ContentEncoding", "traits": { "smithy.api#documentation": "Specifies what content encodings have been applied to the object and thus what decoding mechanisms\n must be applied to obtain the media-type referenced by the Content-Type header field.
\nFor directory buckets, only the aws-chunked value is supported in this header field.
The language the content is in.
", "smithy.api#httpHeader": "Content-Language" } }, "ContentType": { "target": "com.amazonaws.s3#ContentType", "traits": { "smithy.api#documentation": "A standard MIME type that describes the format of the object data.
", "smithy.api#httpHeader": "Content-Type" } }, "CopySource": { "target": "com.amazonaws.s3#CopySource", "traits": { "smithy.api#documentation": "Specifies the source object for the copy operation. The source object can be up to 5 GB. If the\n source object is an object that was uploaded by using a multipart upload, the object copy will be a\n single part object after the source object is copied to the destination bucket.
\nYou specify the value of the copy source in one of two formats, depending on whether you want to\n access the source object through an access point:
\nFor objects not accessed through an access point, specify the name of the source bucket and the key of\n the source object, separated by a slash (/). For example, to copy the object\n reports/january.pdf from the general purpose bucket awsexamplebucket, use\n awsexamplebucket/reports/january.pdf. The value must be URL-encoded. To copy the\n object reports/january.pdf from the directory bucket\n awsexamplebucket--use1-az5--x-s3, use\n awsexamplebucket--use1-az5--x-s3/reports/january.pdf. The value must be\n URL-encoded.
For objects accessed through access points, specify the Amazon Resource Name (ARN) of the object as accessed through the access point, in the format arn:aws:s3:. For example, to copy the object reports/january.pdf through access point my-access-point owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3:us-west-2:123456789012:accesspoint/my-access-point/object/reports/january.pdf. The value must be URL encoded.
Amazon S3 supports copy operations using Access points only when the source and destination buckets are in the same Amazon Web Services Region.
\nAccess points are not supported by directory buckets.
\nAlternatively, for objects accessed through Amazon S3 on Outposts, specify the ARN of the object as accessed in the format arn:aws:s3-outposts:. For example, to copy the object reports/january.pdf through outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/object/reports/january.pdf. The value must be URL-encoded.
If your source bucket versioning is enabled, the x-amz-copy-source header by default\n identifies the current version of an object to copy. If the current version is a delete marker, Amazon S3\n behaves as if the object was deleted. To copy a different version, use the versionId query\n parameter. Specifically, append ?versionId= to the value (for example,\n awsexamplebucket/reports/january.pdf?versionId=QUpfdndhfd8438MNFDN93jdnJFkdmqnh893). If\n you don't specify a version ID, Amazon S3 copies the latest version of the source object.
If you enable versioning on the destination bucket, Amazon S3 generates a unique version ID for the\n copied object. This version ID is different from the version ID of the source object. Amazon S3 returns the\n version ID of the copied object in the x-amz-version-id response header in the\n response.
If you do not enable versioning or suspend it on the destination bucket, the version ID that Amazon S3\n generates in the x-amz-version-id response header is always null.
\n Directory buckets - S3 Versioning isn't enabled and supported for directory buckets.
\nCopies the object if its entity tag (ETag) matches the specified tag.
\n If both the x-amz-copy-source-if-match and\n x-amz-copy-source-if-unmodified-since headers are present in the request and evaluate as\n follows, Amazon S3 returns 200 OK and copies the data:
\n x-amz-copy-source-if-match condition evaluates to true
\n x-amz-copy-source-if-unmodified-since condition evaluates to false
Copies the object if it has been modified since the specified time.
\nIf both the x-amz-copy-source-if-none-match and\n x-amz-copy-source-if-modified-since headers are present in the request and evaluate as\n follows, Amazon S3 returns the 412 Precondition Failed response code:
\n x-amz-copy-source-if-none-match condition evaluates to false
\n x-amz-copy-source-if-modified-since condition evaluates to true
Copies the object if its entity tag (ETag) is different than the specified ETag.
\nIf both the x-amz-copy-source-if-none-match and\n x-amz-copy-source-if-modified-since headers are present in the request and evaluate as\n follows, Amazon S3 returns the 412 Precondition Failed response code:
\n x-amz-copy-source-if-none-match condition evaluates to false
\n x-amz-copy-source-if-modified-since condition evaluates to true
Copies the object if it hasn't been modified since the specified time.
\n If both the x-amz-copy-source-if-match and\n x-amz-copy-source-if-unmodified-since headers are present in the request and evaluate as\n follows, Amazon S3 returns 200 OK and copies the data:
\n x-amz-copy-source-if-match condition evaluates to true
\n x-amz-copy-source-if-unmodified-since condition evaluates to false
The date and time at which the object is no longer cacheable.
", "smithy.api#httpHeader": "Expires" } }, "GrantFullControl": { "target": "com.amazonaws.s3#GrantFullControl", "traits": { "smithy.api#documentation": "Gives the grantee READ, READ_ACP, and WRITE_ACP permissions on the object.
\nThis functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nAllows grantee to read the object data and its metadata.
\nThis functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nAllows grantee to read the object ACL.
\nThis functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nAllows grantee to write the ACL for the applicable object.
\nThis functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nThe key of the destination object.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Key" } } }, "Metadata": { "target": "com.amazonaws.s3#Metadata", "traits": { "smithy.api#documentation": "A map of metadata to store with the object in S3.
", "smithy.api#httpPrefixHeaders": "x-amz-meta-" } }, "MetadataDirective": { "target": "com.amazonaws.s3#MetadataDirective", "traits": { "smithy.api#documentation": "Specifies whether the metadata is copied from the source object or replaced with metadata that's\n provided in the request. When copying an object, you can preserve all metadata (the default) or specify\n new metadata. If this header isn\u2019t specified, COPY is the default behavior.
\n General purpose bucket - For general purpose buckets, when you grant\n permissions, you can use the s3:x-amz-metadata-directive condition key to enforce certain\n metadata behavior when objects are uploaded. For more information, see Amazon S3 condition key examples in the\n Amazon S3 User Guide.
\n x-amz-website-redirect-location is unique to each object and is not copied when using\n the x-amz-metadata-directive header. To copy the value, you must specify\n x-amz-website-redirect-location in the request header.
Specifies whether the object tag-set is copied from the source object or replaced with the tag-set\n that's provided in the request.
\nThe default value is COPY.
\n Directory buckets - For directory buckets in a CopyObject operation, only the empty tag-set is supported. Any requests that attempt to write non-empty tags into directory buckets will receive a 501 Not Implemented status code. \nWhen the destination bucket is a directory bucket, you will receive a 501 Not Implemented response in any of the following situations:
When you attempt to COPY the tag-set from an S3 source object that has non-empty tags.
When you attempt to REPLACE the tag-set of a source object and set a non-empty value to x-amz-tagging.
When you don't set the x-amz-tagging-directive header and the source object has non-empty tags. This is because the default value of x-amz-tagging-directive is COPY.
Because only the empty tag-set is supported for directory buckets in a CopyObject operation, the following situations are allowed:
When you attempt to COPY the tag-set from a directory bucket source object that has no tags to a general purpose bucket. It copies an empty tag-set to the destination object.
When you attempt to REPLACE the tag-set of a directory bucket source object and set the x-amz-tagging value of the directory bucket destination object to empty.
When you attempt to REPLACE the tag-set of a general purpose bucket source object that has non-empty tags and set the x-amz-tagging value of the directory bucket destination object to empty.
When you attempt to REPLACE the tag-set of a directory bucket source object and don't set the x-amz-tagging value of the directory bucket destination object. This is because the default value of x-amz-tagging is the empty value.
The server-side encryption algorithm used when storing this object in Amazon S3. Unrecognized or\n unsupported values won\u2019t write a destination object and will receive a 400 Bad Request\n response.
Amazon S3 automatically encrypts all new objects that are copied to an S3 bucket. When copying an object,\n if you don't specify encryption information in your copy request, the encryption setting of the target\n object is set to the default encryption configuration of the destination bucket. By default, all buckets\n have a base level of encryption configuration that uses server-side encryption with Amazon S3 managed keys\n (SSE-S3). If the destination bucket has a different default encryption configuration, Amazon S3 uses the\n corresponding encryption key to encrypt the target object copy.
\nWith server-side encryption, Amazon S3 encrypts your data as it writes your data to disks in its data\n centers and decrypts the data when you access it. For more information about server-side encryption, see\n Using Server-Side\n Encryption in the Amazon S3 User Guide.
\n\n General purpose buckets \n
\nFor general purpose buckets, there are the following supported options for server-side encryption:\n server-side encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer server-side encryption with\n Amazon Web Services KMS keys (DSSE-KMS), and server-side encryption with customer-provided encryption keys\n (SSE-C). Amazon S3 uses the corresponding KMS key, or a customer-provided key to encrypt the target\n object copy.
\nWhen you perform a CopyObject operation, if you want to use a different type of\n encryption setting for the target object, you can specify appropriate encryption-related headers to\n encrypt the target object with an Amazon S3 managed key, a KMS key, or a customer-provided key. If the\n encryption setting in your request is different from the default encryption configuration of the\n destination bucket, the encryption setting in your request takes precedence.
\n Directory buckets \n
\nFor directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n CreateSession requests or PUT object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n information, see Protecting data with server-side encryption in the Amazon S3 User Guide. For more information about the encryption overriding behaviors in directory buckets, see Specifying server-side encryption with KMS for new object uploads.
To encrypt new object copies to a directory bucket with SSE-KMS, we recommend you specify\n SSE-KMS as the directory bucket's default encryption configuration with a KMS key\n (specifically, a customer managed key). The Amazon Web Services managed key (aws/s3) isn't supported. Your SSE-KMS configuration can\n only support 1 customer managed key per\n directory bucket for the lifetime of the bucket. After you specify a customer managed key for SSE-KMS, you\n can't override the customer managed key for the bucket's SSE-KMS configuration. Then, when you\n perform a CopyObject operation and want to specify server-side encryption settings for\n new object copies with SSE-KMS in the encryption-related request headers, you must ensure the\n encryption key is the same customer managed key that you specified for the directory bucket's default\n encryption configuration.\n
\n S3 access points for Amazon FSx - When accessing data stored in\n Amazon FSx file systems using S3 access points, the only valid server side encryption option is\n aws:fsx. All Amazon FSx file systems have encryption configured by default and are\n encrypted at rest. Data is automatically encrypted before being written to the file system, and\n automatically decrypted as it is read. These processes are handled transparently by Amazon FSx.
If the x-amz-storage-class header is not used, the copied object will be stored in the\n STANDARD Storage Class by default. The STANDARD storage class provides high\n durability and high availability. Depending on performance needs, you can specify a different Storage\n Class.
\n Directory buckets -\n Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones. \nUnsupported storage class values won't write a destination object and will respond with the HTTP status code 400 Bad Request.
\n Amazon S3 on Outposts - S3 on Outposts only uses the\n OUTPOSTS Storage Class.
You can use the CopyObject action to change the storage class of an object that is\n already stored in Amazon S3 by using the x-amz-storage-class header. For more information, see\n Storage Classes\n in the Amazon S3 User Guide.
Before using an object as a source object for the copy operation, you must restore a copy of it if\n it meets any of the following conditions:
\nThe storage class of the source object is GLACIER or\n DEEP_ARCHIVE.
The storage class of the source object is INTELLIGENT_TIERING and it's S3\n Intelligent-Tiering access tier is Archive Access or Deep Archive\n Access.
For more information, see RestoreObject and Copying Objects in the\n Amazon S3 User Guide.
", "smithy.api#httpHeader": "x-amz-storage-class" } }, "WebsiteRedirectLocation": { "target": "com.amazonaws.s3#WebsiteRedirectLocation", "traits": { "smithy.api#documentation": "If the destination bucket is configured as a website, redirects requests for this object copy to\n another object in the same bucket or to an external URL. Amazon S3 stores the value of this header in the\n object metadata. This value is unique to each object and is not copied when using the\n x-amz-metadata-directive header. Instead, you may opt to provide this header in\n combination with the x-amz-metadata-directive header.
This functionality is not supported for directory buckets.
\nSpecifies the algorithm to use when encrypting the object (for example, AES256).
When you perform a CopyObject operation, if you want to use a different type of\n encryption setting for the target object, you can specify appropriate encryption-related headers to\n encrypt the target object with an Amazon S3 managed key, a KMS key, or a customer-provided key. If the\n encryption setting in your request is different from the default encryption configuration of the\n destination bucket, the encryption setting in your request takes precedence.
This functionality is not supported when the destination bucket is a directory bucket.
\nSpecifies the customer-provided encryption key for Amazon S3 to use in encrypting data. This value is\n used to store the object and then it is discarded. Amazon S3 does not store the encryption key. The key must\n be appropriate for use with the algorithm specified in the\n x-amz-server-side-encryption-customer-algorithm header.
This functionality is not supported when the destination bucket is a directory bucket.
\nSpecifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header\n for a message integrity check to ensure that the encryption key was transmitted without error.
\nThis functionality is not supported when the destination bucket is a directory bucket.
\nSpecifies the KMS key ID (Key ID, Key ARN, or Key Alias) to use for object encryption. All GET and\n PUT requests for an object protected by KMS will fail if they're not made via SSL or using SigV4. For\n information about configuring any of the officially supported Amazon Web Services SDKs and Amazon Web Services CLI, see Specifying\n the Signature Version in Request Authentication in the\n Amazon S3 User Guide.
\n\n Directory buckets -\n To encrypt data using SSE-KMS, it's recommended to specify the \nx-amz-server-side-encryption header to aws:kms. Then, the x-amz-server-side-encryption-aws-kms-key-id header implicitly uses \nthe bucket's default KMS customer managed key ID. If you want to explicitly set the \n x-amz-server-side-encryption-aws-kms-key-id header, it must match the bucket's default customer managed key (using key ID or ARN, not alias). Your SSE-KMS configuration can only support 1 customer managed key per directory bucket's lifetime. \nThe Amazon Web Services managed key (aws/s3) isn't supported. \n \n Incorrect key specification results in an HTTP 400 Bad Request error.
Specifies the Amazon Web Services KMS Encryption Context as an additional encryption context to use for the\n destination object encryption. The value of this header is a base64-encoded UTF-8 string holding JSON\n with the encryption context key-value pairs.
\n\n General purpose buckets - This value must be explicitly added to\n specify encryption context for CopyObject requests if you want an additional encryption\n context for your destination object. The additional encryption context of the source object won't be\n copied to the destination object. For more information, see Encryption context\n in the Amazon S3 User Guide.
\n Directory buckets - You can optionally provide an explicit encryption context value. The value must match the default encryption context - the bucket Amazon Resource Name (ARN). An additional encryption context value is not supported.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-context" } }, "BucketKeyEnabled": { "target": "com.amazonaws.s3#BucketKeyEnabled", "traits": { "smithy.api#documentation": "Specifies whether Amazon S3 should use an S3 Bucket Key for object encryption with server-side encryption\n using Key Management Service (KMS) keys (SSE-KMS). If a target object uses SSE-KMS, you can enable an S3 Bucket Key\n for the object.
\nSetting this header to true causes Amazon S3 to use an S3 Bucket Key for object encryption\n with SSE-KMS. Specifying this header with a COPY action doesn\u2019t affect bucket-level settings for S3\n Bucket Key.
For more information, see Amazon S3\n Bucket Keys in the Amazon S3 User Guide.
\n\n Directory buckets -\n S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through CopyObject. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.
\nSpecifies the algorithm to use when decrypting the source object (for example,\n AES256).
If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the necessary\n encryption information in your request so that Amazon S3 can decrypt the object for copying.
\nThis functionality is not supported when the source object is in a directory bucket.
\nSpecifies the customer-provided encryption key for Amazon S3 to use to decrypt the source object. The\n encryption key provided in this header must be the same one that was used when the source object was\n created.
\nIf the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the necessary\n encryption information in your request so that Amazon S3 can decrypt the object for copying.
\nThis functionality is not supported when the source object is in a directory bucket.
\nSpecifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header\n for a message integrity check to ensure that the encryption key was transmitted without error.
\nIf the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the necessary\n encryption information in your request so that Amazon S3 can decrypt the object for copying.
\nThis functionality is not supported when the source object is in a directory bucket.
\nThe tag-set for the object copy in the destination bucket. This value must be used in conjunction\n with the x-amz-tagging-directive if you choose REPLACE for the\n x-amz-tagging-directive. If you choose COPY for the\n x-amz-tagging-directive, you don't need to set the x-amz-tagging header,\n because the tag-set will be copied from the source object directly. The tag-set must be encoded as URL\n Query parameters.
The default value is the empty value.
\n\n Directory buckets - For directory buckets in a CopyObject operation, only the empty tag-set is supported. Any requests that attempt to write non-empty tags into directory buckets will receive a 501 Not Implemented status code. \nWhen the destination bucket is a directory bucket, you will receive a 501 Not Implemented response in any of the following situations:
When you attempt to COPY the tag-set from an S3 source object that has non-empty tags.
When you attempt to REPLACE the tag-set of a source object and set a non-empty value to x-amz-tagging.
When you don't set the x-amz-tagging-directive header and the source object has non-empty tags. This is because the default value of x-amz-tagging-directive is COPY.
Because only the empty tag-set is supported for directory buckets in a CopyObject operation, the following situations are allowed:
When you attempt to COPY the tag-set from a directory bucket source object that has no tags to a general purpose bucket. It copies an empty tag-set to the destination object.
When you attempt to REPLACE the tag-set of a directory bucket source object and set the x-amz-tagging value of the directory bucket destination object to empty.
When you attempt to REPLACE the tag-set of a general purpose bucket source object that has non-empty tags and set the x-amz-tagging value of the directory bucket destination object to empty.
When you attempt to REPLACE the tag-set of a directory bucket source object and don't set the x-amz-tagging value of the directory bucket destination object. This is because the default value of x-amz-tagging is the empty value.
The Object Lock mode that you want to apply to the object copy.
\nThis functionality is not supported for directory buckets.
\nThe date and time when you want the Object Lock of the object copy to expire.
\nThis functionality is not supported for directory buckets.
\nSpecifies whether you want to apply a legal hold to the object copy.
\nThis functionality is not supported for directory buckets.
\nThe account ID of the expected destination bucket owner. If the account ID that you provide does not match the actual owner of the destination bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The account ID of the expected source bucket owner. If the account ID that you provide does not match the actual owner of the source bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Returns the ETag of the new object. The ETag reflects only changes to the contents of an object, not\n its metadata.
" } }, "LastModified": { "target": "com.amazonaws.s3#LastModified", "traits": { "smithy.api#documentation": "Creation date of the object.
" } }, "ChecksumType": { "target": "com.amazonaws.s3#ChecksumType", "traits": { "smithy.api#documentation": "The checksum type that is used to calculate the object\u2019s checksum value. For more information, see\n Checking\n object integrity in the Amazon S3 User Guide.
" } }, "ChecksumCRC32": { "target": "com.amazonaws.s3#ChecksumCRC32", "traits": { "smithy.api#documentation": "The Base64 encoded, 32-bit CRC32 checksum of the object. This checksum is only present if the object was uploaded\n with the object. For more information, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the object. This will only be present if the object was uploaded\n with the object. For more information, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the object. This checksum is present\n if the object being copied was uploaded with the CRC64NVME checksum algorithm, or if the\n object was uploaded without a checksum (and Amazon S3 added the default checksum, CRC64NVME, to\n the uploaded object). For more information, see Checking object integrity in\n the Amazon S3 User Guide.
The Base64 encoded, 160-bit SHA1 digest of the object. This will only be present if the object was uploaded\n with the object. For more information, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 digest of the object. This will only be present if the object was uploaded\n with the object. For more information, see \n Checking object integrity in the Amazon S3 User Guide.
Container for all response elements.
" } }, "com.amazonaws.s3#CopyPartResult": { "type": "structure", "members": { "ETag": { "target": "com.amazonaws.s3#ETag", "traits": { "smithy.api#documentation": "Entity tag of the object.
" } }, "LastModified": { "target": "com.amazonaws.s3#LastModified", "traits": { "smithy.api#documentation": "Date and time at which the object was uploaded.
" } }, "ChecksumCRC32": { "target": "com.amazonaws.s3#ChecksumCRC32", "traits": { "smithy.api#documentation": "This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This header specifies the Base64 encoded, 32-bit CRC32 checksum\n of the part. For more information, see Checking object integrity in\n the Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This header specifies the Base64 encoded, 32-bit CRC32C checksum\n of the part. For more information, see Checking object integrity in\n the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the part. This checksum is present if\n the multipart upload request was created with the CRC64NVME checksum algorithm to the\n uploaded object). For more information, see Checking object integrity in\n the Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This header specifies the Base64 encoded, 160-bit SHA1 checksum\n of the part. For more information, see Checking object integrity in\n the Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This header specifies the Base64 encoded, 256-bit SHA256 checksum\n of the part. For more information, see Checking object integrity in\n the Amazon S3 User Guide.
Container for all response elements.
" } }, "com.amazonaws.s3#CopySource": { "type": "string", "traits": { "smithy.api#pattern": "^\\/?.+\\/.+$" } }, "com.amazonaws.s3#CopySourceIfMatch": { "type": "string" }, "com.amazonaws.s3#CopySourceIfModifiedSince": { "type": "timestamp" }, "com.amazonaws.s3#CopySourceIfNoneMatch": { "type": "string" }, "com.amazonaws.s3#CopySourceIfUnmodifiedSince": { "type": "timestamp" }, "com.amazonaws.s3#CopySourceRange": { "type": "string" }, "com.amazonaws.s3#CopySourceSSECustomerAlgorithm": { "type": "string" }, "com.amazonaws.s3#CopySourceSSECustomerKey": { "type": "string", "traits": { "smithy.api#sensitive": {} } }, "com.amazonaws.s3#CopySourceSSECustomerKeyMD5": { "type": "string" }, "com.amazonaws.s3#CopySourceVersionId": { "type": "string" }, "com.amazonaws.s3#CreateBucket": { "type": "operation", "input": { "target": "com.amazonaws.s3#CreateBucketRequest" }, "output": { "target": "com.amazonaws.s3#CreateBucketOutput" }, "errors": [ { "target": "com.amazonaws.s3#BucketAlreadyExists" }, { "target": "com.amazonaws.s3#BucketAlreadyOwnedByYou" } ], "traits": { "smithy.api#documentation": "End of support notice: Beginning October 1, 2025, Amazon S3 will discontinue support for creating new Email Grantee Access Control Lists (ACL). \n Email Grantee ACLs created prior to this date will continue to work and remain accessible through the Amazon Web Services Management Console, Command Line Interface (CLI), SDKs, \n and REST API. However, you will no longer be able to create new Email Grantee ACLs.\n
\nThis change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nEnd of support notice: Beginning October 1, 2025, Amazon S3 will stop returning DisplayName. Update your applications to use canonical IDs (unique identifier for \n Amazon Web Services accounts), Amazon Web Services account ID (12 digit identifier) or IAM ARNs (full resource naming) as a direct replacement of DisplayName.\n
This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nThis action creates an Amazon S3 bucket. To create an Amazon S3 on Outposts bucket, see \n CreateBucket\n .
Creates a new S3 bucket. To create a bucket, you must set up Amazon S3 and have a valid Amazon Web Services Access Key\n ID to authenticate requests. Anonymous requests are never allowed to create buckets. By creating the\n bucket, you become the bucket owner.
\nThere are two types of buckets: general purpose buckets and directory buckets. For more information about\n these bucket types, see Creating, configuring, and working with Amazon S3\n buckets in the Amazon S3 User Guide.
\n\n General purpose buckets - If you send your\n CreateBucket request to the s3.amazonaws.com global endpoint, the\n request goes to the us-east-1 Region. So the signature calculations in Signature\n Version 4 must use us-east-1 as the Region, even if the location constraint in the\n request specifies another Region where the bucket is to be created. If you create a bucket in a\n Region other than US East (N. Virginia), your application must be able to handle 307 redirect. For\n more information, see Virtual hosting of buckets in the Amazon S3 User Guide.
\n Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. \nFor more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n General purpose bucket permissions - In addition to the\n s3:CreateBucket permission, the following permissions are required in a policy\n when your CreateBucket request includes specific headers:
\n Access control lists (ACLs) - In your\n CreateBucket request, if you specify an access control list (ACL) and set\n it to public-read, public-read-write,\n authenticated-read, or if you explicitly specify any other custom ACLs,\n both s3:CreateBucket and s3:PutBucketAcl permissions are\n required. In your CreateBucket request, if you set the ACL to\n private, or if you don't specify any ACLs, only the\n s3:CreateBucket permission is required.
\n Object Lock - In your\n CreateBucket request, if you set\n x-amz-bucket-object-lock-enabled to true, the\n s3:PutBucketObjectLockConfiguration and s3:PutBucketVersioning\n permissions are required.
\n S3 Object Ownership - If your\n CreateBucket request includes the x-amz-object-ownership\n header, then the s3:PutBucketOwnershipControls permission is required.
To set an ACL on a bucket as part of a CreateBucket request, you must\n explicitly set S3 Object Ownership for the bucket to a different value than the default,\n BucketOwnerEnforced. Additionally, if your desired bucket ACL grants\n public access, you must first create the bucket (without the bucket ACL) and then\n explicitly disable Block Public Access on the bucket before using\n PutBucketAcl to set the ACL. If you try to create a bucket with a public\n ACL, the request will fail.
For the majority of modern use cases in S3, we recommend that you keep all Block\n Public Access settings enabled and keep ACLs disabled. If you would like to share data\n with users outside of your account, you can use bucket policies as needed. For more\n information, see Controlling ownership of\n objects and disabling ACLs for your bucket and Blocking\n public access to your Amazon S3 storage in the\n Amazon S3 User Guide.
\n\n S3 Block Public Access - If your specific use\n case requires granting public access to your S3 resources, you can disable Block Public\n Access. Specifically, you can create a new bucket with Block Public Access enabled, then\n separately call the \n DeletePublicAccessBlock\n API. To use this operation, you must have the\n s3:PutBucketPublicAccessBlock permission. For more information about S3\n Block Public Access, see Blocking public\n access to your Amazon S3 storage in the Amazon S3 User Guide.\n
\n Directory bucket permissions - You must have the\n s3express:CreateBucket permission in an IAM identity-based policy instead of a bucket policy.\n Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource. For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
The permissions for ACLs, Object Lock, S3 Object Ownership, and S3 Block Public Access\n are not supported for directory buckets. For directory buckets, all Block Public Access\n settings are enabled at the bucket level and S3 Object Ownership is set to Bucket owner\n enforced (ACLs disabled). These settings can't be modified.
\nFor more information about permissions for creating and working with directory buckets,\n see Directory buckets\n in the Amazon S3 User Guide. For more information about supported S3\n features for directory buckets, see Features of\n S3 Express One Zone in the Amazon S3 User Guide.
\n\n Directory buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following operations are related to CreateBucket:
\n PutObject\n
\n\n DeleteBucket\n
\nSpecifies the Region where the bucket will be created. You might choose a Region to optimize\n latency, minimize costs, or address regulatory requirements. For example, if you reside in Europe, you\n will probably find it advantageous to create buckets in the Europe (Ireland) Region.
\nIf you don't specify a Region, the bucket is created in the US East (N. Virginia) Region (us-east-1)\n by default. Configurations using the value EU will create a bucket in\n eu-west-1.
For a list of the valid values for all of the Amazon Web Services Regions, see Regions and Endpoints.
\nThis functionality is not supported for directory buckets.
\nSpecifies the location where the bucket will be created.
\n\n Directory buckets - The location type is Availability Zone or Local Zone. To\n use the Local Zone location type, your account must be enabled\n for Local Zones. Otherwise, you get an HTTP 403 Forbidden error with the error code\n AccessDenied. To learn more,\n see Enable\n accounts for Local Zones in the Amazon S3 User Guide.
This functionality is only supported by directory buckets.
\nSpecifies the information about the bucket that will be created.
\nThis functionality is only supported by directory buckets.
\nAn array of tags that you can apply to the bucket that you're creating. Tags are key-value pairs of\n metadata used to categorize and organize your buckets, track costs, and control access.
\nThis parameter is only supported for S3 directory buckets. For more information, see Using tags with\n directory buckets.
\nThe configuration information for the bucket.
" } }, "com.amazonaws.s3#CreateBucketMetadataConfiguration": { "type": "operation", "input": { "target": "com.amazonaws.s3#CreateBucketMetadataConfigurationRequest" }, "output": { "target": "smithy.api#Unit" }, "traits": { "aws.protocols#httpChecksum": { "requestAlgorithmMember": "ChecksumAlgorithm", "requestChecksumRequired": true }, "smithy.api#documentation": "Creates an S3 Metadata V2 metadata configuration for a general purpose bucket. For more information, see\n Accelerating\n data discovery with S3 Metadata in the Amazon S3 User Guide.
\nTo use this operation, you must have the following permissions. For more information, see\n Setting up permissions for configuring metadata tables in the\n Amazon S3 User Guide.
\nIf you want to encrypt your metadata tables with server-side encryption with Key Management Service\n (KMS) keys (SSE-KMS), you need additional permissions in your KMS key policy. For more\n information, see \n Setting up permissions for configuring metadata tables in the\n Amazon S3 User Guide.
\nIf you also want to integrate your table bucket with Amazon Web Services analytics services so that you can\n query your metadata table, you need additional permissions. For more information, see Integrating\n Amazon S3 Tables with Amazon Web Services analytics services in the\n Amazon S3 User Guide.
\nTo query your metadata tables, you need additional permissions. For more information, see \n \n Permissions for querying metadata tables in the Amazon S3 User Guide.
\n\n s3:CreateBucketMetadataTableConfiguration\n
The IAM policy action name is the same for the V1 and V2 API operations.
\n\n s3tables:CreateTableBucket\n
\n s3tables:CreateNamespace\n
\n s3tables:GetTable\n
\n s3tables:CreateTable\n
\n s3tables:PutTablePolicy\n
\n s3tables:PutTableEncryption\n
\n kms:DescribeKey\n
The following operations are related to CreateBucketMetadataConfiguration:
\n The general purpose bucket that you want to create the metadata configuration for.\n
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "\n The Content-MD5 header for the metadata configuration.\n
\n The checksum algorithm to use with your metadata configuration.\n
", "smithy.api#httpHeader": "x-amz-sdk-checksum-algorithm" } }, "MetadataConfiguration": { "target": "com.amazonaws.s3#MetadataConfiguration", "traits": { "smithy.api#documentation": "\n The contents of your metadata configuration.\n
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "MetadataConfiguration" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "\n The expected owner of the general purpose bucket that corresponds to your metadata configuration.\n
", "smithy.api#httpHeader": "x-amz-expected-bucket-owner" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#CreateBucketMetadataTableConfiguration": { "type": "operation", "input": { "target": "com.amazonaws.s3#CreateBucketMetadataTableConfigurationRequest" }, "output": { "target": "smithy.api#Unit" }, "traits": { "aws.protocols#httpChecksum": { "requestAlgorithmMember": "ChecksumAlgorithm", "requestChecksumRequired": true }, "smithy.api#documentation": "\n We recommend that you create your S3 Metadata configurations by using the V2 \n CreateBucketMetadataConfiguration API operation. We no longer recommend using the V1 \n CreateBucketMetadataTableConfiguration API operation.\n
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete \n and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create \n a live inventory table.
\nCreates a V1 S3 Metadata configuration for a general purpose bucket. For more information, see\n Accelerating\n data discovery with S3 Metadata in the Amazon S3 User Guide.
\nTo use this operation, you must have the following permissions. For more information, see\n Setting up permissions for configuring metadata tables in the\n Amazon S3 User Guide.
\nIf you want to encrypt your metadata tables with server-side encryption with Key Management Service\n (KMS) keys (SSE-KMS), you need additional permissions. For more\n information, see \n Setting up permissions for configuring metadata tables in the\n Amazon S3 User Guide.
\nIf you also want to integrate your table bucket with Amazon Web Services analytics services so that you can\n query your metadata table, you need additional permissions. For more information, see Integrating\n Amazon S3 Tables with Amazon Web Services analytics services in the\n Amazon S3 User Guide.
\n\n s3:CreateBucketMetadataTableConfiguration\n
\n s3tables:CreateNamespace\n
\n s3tables:GetTable\n
\n s3tables:CreateTable\n
\n s3tables:PutTablePolicy\n
The following operations are related to CreateBucketMetadataTableConfiguration:
The general purpose bucket that you want to create the metadata table configuration for.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": " The Content-MD5 header for the metadata table configuration.
The checksum algorithm to use with your metadata table configuration.
", "smithy.api#httpHeader": "x-amz-sdk-checksum-algorithm" } }, "MetadataTableConfiguration": { "target": "com.amazonaws.s3#MetadataTableConfiguration", "traits": { "smithy.api#documentation": "The contents of your metadata table configuration.
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "MetadataTableConfiguration" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The expected owner of the general purpose bucket that corresponds to your metadata table configuration.\n
", "smithy.api#httpHeader": "x-amz-expected-bucket-owner" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#CreateBucketOutput": { "type": "structure", "members": { "Location": { "target": "com.amazonaws.s3#Location", "traits": { "smithy.api#documentation": "A forward slash followed by the name of the bucket.
", "smithy.api#httpHeader": "Location" } }, "BucketArn": { "target": "com.amazonaws.s3#S3RegionalOrS3ExpressBucketArnString", "traits": { "smithy.api#documentation": "The Amazon Resource Name (ARN) of the S3 bucket. ARNs uniquely identify Amazon Web Services resources across all\n of Amazon Web Services.
\nThis parameter is only supported for S3 directory buckets. For more information, see Using tags with\n directory buckets.
\nThe canned ACL to apply to the bucket.
\nThis functionality is not supported for directory buckets.
\nThe name of the bucket to create.
\n\n General purpose buckets - For information about bucket naming\n restrictions, see Bucket naming\n rules in the Amazon S3 User Guide.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n DOC-EXAMPLE-BUCKET--usw2-az1--x-s3). For information about bucket naming restrictions, see Directory bucket naming rules in the Amazon S3 User Guide\n
The configuration information for the bucket.
", "smithy.api#httpPayload": {}, "smithy.api#xmlName": "CreateBucketConfiguration" } }, "GrantFullControl": { "target": "com.amazonaws.s3#GrantFullControl", "traits": { "smithy.api#documentation": "Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.
\nThis functionality is not supported for directory buckets.
\nAllows grantee to list the objects in the bucket.
\nThis functionality is not supported for directory buckets.
\nAllows grantee to read the bucket ACL.
\nThis functionality is not supported for directory buckets.
\nAllows grantee to create new objects in the bucket.
\nFor the bucket and object owners of existing objects, also allows deletions and overwrites of those\n objects.
\nThis functionality is not supported for directory buckets.
\nAllows grantee to write the ACL for the applicable bucket.
\nThis functionality is not supported for directory buckets.
\nSpecifies whether you want S3 Object Lock to be enabled for the new bucket.
\nThis functionality is not supported for directory buckets.
\nEnd of support notice: Beginning October 1, 2025, Amazon S3 will discontinue support for creating new Email Grantee Access Control Lists (ACL). \n Email Grantee ACLs created prior to this date will continue to work and remain accessible through the Amazon Web Services Management Console, Command Line Interface (CLI), SDKs, \n and REST API. However, you will no longer be able to create new Email Grantee ACLs.\n
\nThis change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nThis action initiates a multipart upload and returns an upload ID. This upload ID is used to\n associate all of the parts in the specific multipart upload. You specify this upload ID in each of your\n subsequent upload part requests (see UploadPart). You also include this upload ID in\n the final request to either complete or abort the multipart upload request. For more information about\n multipart uploads, see Multipart\n Upload Overview in the Amazon S3 User Guide.
\nAfter you initiate a multipart upload and upload one or more parts, to stop being charged for\n storing the uploaded parts, you must either complete or abort the multipart upload. Amazon S3 frees up the\n space used to store the parts and stops charging you for storing them only after you either complete\n or abort a multipart upload.
\nIf you have configured a lifecycle rule to abort incomplete multipart uploads, the created multipart\n upload must be completed within the number of days specified in the bucket lifecycle configuration.\n Otherwise, the incomplete multipart upload becomes eligible for an abort action and Amazon S3 aborts the\n multipart upload. For more information, see Aborting\n Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration.
\n\n Directory buckets -\n S3 Lifecycle is not supported by directory buckets.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
For request signing, multipart upload is just a series of regular requests. You initiate a\n multipart upload, send one or more requests to upload parts, and then complete the multipart\n upload process. You sign each request individually. There is nothing special about signing\n multipart upload requests. For more information about signing, see Authenticating Requests (Amazon Web Services\n Signature Version 4) in the Amazon S3 User Guide.
\n\n General purpose bucket permissions - To perform a\n multipart upload with encryption using an Key Management Service (KMS) KMS key, the requester must have\n permission to the kms:Decrypt and kms:GenerateDataKey actions on the\n key. The requester must also have permissions for the kms:GenerateDataKey action\n for the CreateMultipartUpload API. Then, the requester needs permissions for the\n kms:Decrypt action on the UploadPart and\n UploadPartCopy APIs. These permissions are required because Amazon S3 must decrypt\n and read data from the encrypted file parts before it completes the multipart upload. For more\n information, see Multipart upload API and\n permissions and Protecting data using server-side\n encryption with Amazon Web Services KMS in the Amazon S3 User Guide.
\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
\n General purpose buckets - Server-side encryption is for\n data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers\n and decrypts it when you access it. Amazon S3 automatically encrypts all new objects that are\n uploaded to an S3 bucket. When doing a multipart upload, if you don't specify encryption\n information in your request, the encryption setting of the uploaded parts is set to the\n default encryption configuration of the destination bucket. By default, all buckets have a\n base level of encryption configuration that uses server-side encryption with Amazon S3 managed keys\n (SSE-S3). If the destination bucket has a default encryption configuration that uses\n server-side encryption with an Key Management Service (KMS) key (SSE-KMS), or a customer-provided\n encryption key (SSE-C), Amazon S3 uses the corresponding KMS key, or a customer-provided key to\n encrypt the uploaded parts. When you perform a CreateMultipartUpload operation, if you want to\n use a different type of encryption setting for the uploaded parts, you can request that Amazon S3\n encrypts the object with a different encryption key (such as an Amazon S3 managed key, a KMS key,\n or a customer-provided key). When the encryption setting in your request is different from the\n default encryption configuration of the destination bucket, the encryption setting in your\n request takes precedence. If you choose to provide your own encryption key, the request\n headers you provide in UploadPart and UploadPartCopy requests must match the headers you used in the\n CreateMultipartUpload request.
Use KMS keys (SSE-KMS) that include the Amazon Web Services managed key (aws/s3) and\n KMS customer managed keys stored in Key Management Service (KMS) \u2013 If you want Amazon Web Services to manage the keys used\n to encrypt data, specify the following headers in the request.
\n x-amz-server-side-encryption\n
\n x-amz-server-side-encryption-aws-kms-key-id\n
\n x-amz-server-side-encryption-context\n
If you specify x-amz-server-side-encryption:aws:kms, but don't\n provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the\n Amazon Web Services managed key (aws/s3 key) in KMS to protect the data.
To perform a multipart upload with encryption by using an Amazon Web Services KMS key, the\n requester must have permission to the kms:Decrypt and\n kms:GenerateDataKey* actions on the key. These permissions are\n required because Amazon S3 must decrypt and read data from the encrypted file parts\n before it completes the multipart upload. For more information, see Multipart\n upload API and permissions and Protecting data using\n server-side encryption with Amazon Web Services KMS in the\n Amazon S3 User Guide.
If your Identity and Access Management (IAM) user or role is in the same Amazon Web Services account as the\n KMS key, then you must have these permissions on the key policy. If your IAM\n user or role is in a different account from the key, then you must have the\n permissions on both the key policy and your IAM user or role.
\nAll GET and PUT requests for an object protected by\n KMS fail if you don't make them by using Secure Sockets Layer (SSL), Transport\n Layer Security (TLS), or Signature Version 4. For information about configuring any\n of the officially supported Amazon Web Services SDKs and Amazon Web Services CLI, see Specifying the Signature Version in Request\n Authentication in the Amazon S3 User Guide.
For more information about server-side encryption with KMS keys (SSE-KMS), see\n Protecting Data Using Server-Side Encryption with KMS keys in the\n Amazon S3 User Guide.
\nUse customer-provided encryption keys (SSE-C) \u2013 If you want to manage your own\n encryption keys, provide all the following headers in the request.
\n\n x-amz-server-side-encryption-customer-algorithm\n
\n x-amz-server-side-encryption-customer-key\n
\n x-amz-server-side-encryption-customer-key-MD5\n
For more information about server-side encryption with customer-provided encryption\n keys (SSE-C), see Protecting data\n using server-side encryption with customer-provided encryption keys (SSE-C) in\n the Amazon S3 User Guide.
\n\n Directory buckets -\n For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n CreateSession requests or PUT object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n information, see Protecting data with server-side encryption in the Amazon S3 User Guide. For more information about the encryption overriding behaviors in directory buckets, see Specifying server-side encryption with KMS for new object uploads.
In the Zonal endpoint API calls (except CopyObject and UploadPartCopy) using the REST API, the encryption request headers must match the encryption settings that are specified in the CreateSession request. \n You can't override the values of the encryption settings (x-amz-server-side-encryption, x-amz-server-side-encryption-aws-kms-key-id, x-amz-server-side-encryption-context, and x-amz-server-side-encryption-bucket-key-enabled) that are specified in the CreateSession request. \n You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and \n Amazon S3 will use the encryption settings values from the CreateSession request to protect new objects in the directory bucket. \n
When you use the CLI or the Amazon Web Services SDKs, for CreateSession, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the \n CreateSession request. It's not supported to override the encryption settings values in the CreateSession request. \n So in the Zonal endpoint API calls (except CopyObject and UploadPartCopy), \n the encryption request headers must match the default encryption configuration of the directory bucket.\n\n
For directory buckets, when you perform a CreateMultipartUpload operation\n and an UploadPartCopy operation, the request headers you provide in the\n CreateMultipartUpload request must match the default encryption configuration\n of the destination bucket.
\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following operations are related to CreateMultipartUpload:
\n UploadPart\n
\n\n AbortMultipartUpload\n
\n\n ListParts\n
\n\n ListMultipartUploads\n
\nIf the bucket has a lifecycle rule configured with an action to abort incomplete multipart uploads\n and the prefix in the lifecycle rule matches the object name in the request, the response includes this\n header. The header indicates when the initiated multipart upload becomes eligible for an abort\n operation. For more information, see Aborting\n Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration in the\n Amazon S3 User Guide.
\nThe response also includes the x-amz-abort-rule-id header that provides the ID of the\n lifecycle configuration rule that defines the abort action.
This functionality is not supported for directory buckets.
\nThis header is returned along with the x-amz-abort-date header. It identifies the\n applicable lifecycle configuration rule that defines the action to abort incomplete multipart\n uploads.
This functionality is not supported for directory buckets.
\nThe name of the bucket to which the multipart upload was initiated. Does not return the access point ARN or\n access point alias if used.
\nAccess points are not supported by directory buckets.
\nObject key for which the multipart upload was initiated.
" } }, "UploadId": { "target": "com.amazonaws.s3#MultipartUploadId", "traits": { "smithy.api#documentation": "ID for the initiated multipart upload.
" } }, "ServerSideEncryption": { "target": "com.amazonaws.s3#ServerSideEncryption", "traits": { "smithy.api#documentation": "The server-side encryption algorithm used when you store this object in Amazon S3 or Amazon FSx.
\nWhen accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side\n encryption option is aws:fsx.
If server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to confirm the encryption algorithm that's used.
\nThis functionality is not supported for directory buckets.
\nIf server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to provide the round-trip message integrity verification of the customer-provided\n encryption key.
\nThis functionality is not supported for directory buckets.
\nIf present, indicates the ID of the KMS key that was used for object encryption.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-aws-kms-key-id" } }, "SSEKMSEncryptionContext": { "target": "com.amazonaws.s3#SSEKMSEncryptionContext", "traits": { "smithy.api#documentation": "If present, indicates the Amazon Web Services KMS Encryption Context to use for object encryption. The value of\n this header is a Base64 encoded string of a UTF-8 encoded JSON, which contains the encryption context as key-value pairs.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-context" } }, "BucketKeyEnabled": { "target": "com.amazonaws.s3#BucketKeyEnabled", "traits": { "smithy.api#documentation": "Indicates whether the multipart upload uses an S3 Bucket Key for server-side encryption with\n Key Management Service (KMS) keys (SSE-KMS).
", "smithy.api#httpHeader": "x-amz-server-side-encryption-bucket-key-enabled" } }, "RequestCharged": { "target": "com.amazonaws.s3#RequestCharged", "traits": { "smithy.api#httpHeader": "x-amz-request-charged" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "The algorithm that was used to create a checksum of the object.
", "smithy.api#httpHeader": "x-amz-checksum-algorithm" } }, "ChecksumType": { "target": "com.amazonaws.s3#ChecksumType", "traits": { "smithy.api#documentation": "Indicates the checksum type that you want Amazon S3 to use to calculate the object\u2019s checksum\n value. For more information, see Checking object integrity in the Amazon S3\n User Guide.
", "smithy.api#httpHeader": "x-amz-checksum-type" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "InitiateMultipartUploadResult" } }, "com.amazonaws.s3#CreateMultipartUploadRequest": { "type": "structure", "members": { "ACL": { "target": "com.amazonaws.s3#ObjectCannedACL", "traits": { "smithy.api#documentation": "The canned ACL to apply to the object. Amazon S3 supports a set of predefined ACLs, known as\n canned ACLs. Each canned ACL has a predefined set of grantees and permissions.\n For more information, see Canned ACL in the\n Amazon S3 User Guide.
\nBy default, all objects are private. Only the owner has full access control. When uploading an\n object, you can grant access permissions to individual Amazon Web Services accounts or to predefined groups defined by\n Amazon S3. These permissions are then added to the access control list (ACL) on the new object. For more\n information, see Using\n ACLs. One way to grant the permissions using the request headers is to specify a canned ACL\n with the x-amz-acl request header.
This functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nThe name of the bucket where the multipart upload is initiated and where the object is\n uploaded.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Specifies caching behavior along the request/reply chain.
", "smithy.api#httpHeader": "Cache-Control" } }, "ContentDisposition": { "target": "com.amazonaws.s3#ContentDisposition", "traits": { "smithy.api#documentation": "Specifies presentational information for the object.
", "smithy.api#httpHeader": "Content-Disposition" } }, "ContentEncoding": { "target": "com.amazonaws.s3#ContentEncoding", "traits": { "smithy.api#documentation": "Specifies what content encodings have been applied to the object and thus what decoding mechanisms\n must be applied to obtain the media-type referenced by the Content-Type header field.
\nFor directory buckets, only the aws-chunked value is supported in this header field.
The language that the content is in.
", "smithy.api#httpHeader": "Content-Language" } }, "ContentType": { "target": "com.amazonaws.s3#ContentType", "traits": { "smithy.api#documentation": "A standard MIME type describing the format of the object data.
", "smithy.api#httpHeader": "Content-Type" } }, "Expires": { "target": "com.amazonaws.s3#Expires", "traits": { "smithy.api#documentation": "The date and time at which the object is no longer cacheable.
", "smithy.api#httpHeader": "Expires" } }, "GrantFullControl": { "target": "com.amazonaws.s3#GrantFullControl", "traits": { "smithy.api#documentation": "Specify access permissions explicitly to give the grantee READ, READ_ACP, and WRITE_ACP permissions\n on the object.
\nBy default, all objects are private. Only the owner has full access control. When uploading an\n object, you can use this header to explicitly grant access permissions to specific Amazon Web Services accounts or\n groups. This header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see\n Access Control List (ACL)\n Overview in the Amazon S3 User Guide.
\nYou specify each grantee as a type=value pair, where the type is one of the following:
\n\n id \u2013 if the value specified is the canonical user ID of an Amazon Web Services account
\n uri \u2013 if you are granting permissions to a predefined group
\n emailAddress \u2013 if the value specified is the email address of an\n Amazon Web Services account
Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:
\nUS East (N. Virginia)
\nUS West (N. California)
\nUS West (Oregon)
\nAsia Pacific (Singapore)
\nAsia Pacific (Sydney)
\nAsia Pacific (Tokyo)
\nEurope (Ireland)
\nSouth America (S\u00e3o Paulo)
\nFor a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the Amazon Web Services General Reference.
\nFor example, the following x-amz-grant-read header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:
\n x-amz-grant-read: id=\"11112222333\", id=\"444455556666\" \n
This functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nSpecify access permissions explicitly to allow grantee to read the object data and its\n metadata.
\nBy default, all objects are private. Only the owner has full access control. When uploading an\n object, you can use this header to explicitly grant access permissions to specific Amazon Web Services accounts or\n groups. This header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see\n Access Control List (ACL)\n Overview in the Amazon S3 User Guide.
\nYou specify each grantee as a type=value pair, where the type is one of the following:
\n\n id \u2013 if the value specified is the canonical user ID of an Amazon Web Services account
\n uri \u2013 if you are granting permissions to a predefined group
\n emailAddress \u2013 if the value specified is the email address of an\n Amazon Web Services account
Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:
\nUS East (N. Virginia)
\nUS West (N. California)
\nUS West (Oregon)
\nAsia Pacific (Singapore)
\nAsia Pacific (Sydney)
\nAsia Pacific (Tokyo)
\nEurope (Ireland)
\nSouth America (S\u00e3o Paulo)
\nFor a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the Amazon Web Services General Reference.
\nFor example, the following x-amz-grant-read header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:
\n x-amz-grant-read: id=\"11112222333\", id=\"444455556666\" \n
This functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nSpecify access permissions explicitly to allows grantee to read the object ACL.
\nBy default, all objects are private. Only the owner has full access control. When uploading an\n object, you can use this header to explicitly grant access permissions to specific Amazon Web Services accounts or\n groups. This header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see\n Access Control List (ACL)\n Overview in the Amazon S3 User Guide.
\nYou specify each grantee as a type=value pair, where the type is one of the following:
\n\n id \u2013 if the value specified is the canonical user ID of an Amazon Web Services account
\n uri \u2013 if you are granting permissions to a predefined group
\n emailAddress \u2013 if the value specified is the email address of an\n Amazon Web Services account
Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:
\nUS East (N. Virginia)
\nUS West (N. California)
\nUS West (Oregon)
\nAsia Pacific (Singapore)
\nAsia Pacific (Sydney)
\nAsia Pacific (Tokyo)
\nEurope (Ireland)
\nSouth America (S\u00e3o Paulo)
\nFor a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the Amazon Web Services General Reference.
\nFor example, the following x-amz-grant-read header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:
\n x-amz-grant-read: id=\"11112222333\", id=\"444455556666\" \n
This functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nSpecify access permissions explicitly to allows grantee to allow grantee to write the ACL for the\n applicable object.
\nBy default, all objects are private. Only the owner has full access control. When uploading an\n object, you can use this header to explicitly grant access permissions to specific Amazon Web Services accounts or\n groups. This header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see\n Access Control List (ACL)\n Overview in the Amazon S3 User Guide.
\nYou specify each grantee as a type=value pair, where the type is one of the following:
\n\n id \u2013 if the value specified is the canonical user ID of an Amazon Web Services account
\n uri \u2013 if you are granting permissions to a predefined group
\n emailAddress \u2013 if the value specified is the email address of an\n Amazon Web Services account
Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:
\nUS East (N. Virginia)
\nUS West (N. California)
\nUS West (Oregon)
\nAsia Pacific (Singapore)
\nAsia Pacific (Sydney)
\nAsia Pacific (Tokyo)
\nEurope (Ireland)
\nSouth America (S\u00e3o Paulo)
\nFor a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the Amazon Web Services General Reference.
\nFor example, the following x-amz-grant-read header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:
\n x-amz-grant-read: id=\"11112222333\", id=\"444455556666\" \n
This functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nObject key for which the multipart upload is to be initiated.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Key" } } }, "Metadata": { "target": "com.amazonaws.s3#Metadata", "traits": { "smithy.api#documentation": "A map of metadata to store with the object in S3.
", "smithy.api#httpPrefixHeaders": "x-amz-meta-" } }, "ServerSideEncryption": { "target": "com.amazonaws.s3#ServerSideEncryption", "traits": { "smithy.api#documentation": "The server-side encryption algorithm used when you store this object in Amazon S3 or Amazon FSx.
\n\n Directory buckets -\n For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n CreateSession requests or PUT object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n information, see Protecting data with server-side encryption in the Amazon S3 User Guide. For more information about the encryption overriding behaviors in directory buckets, see Specifying server-side encryption with KMS for new object uploads.
In the Zonal endpoint API calls (except CopyObject and UploadPartCopy) using the REST API, the encryption request headers must match the encryption settings that are specified in the CreateSession request. \n You can't override the values of the encryption settings (x-amz-server-side-encryption, x-amz-server-side-encryption-aws-kms-key-id, x-amz-server-side-encryption-context, and x-amz-server-side-encryption-bucket-key-enabled) that are specified in the CreateSession request. \n You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and \n Amazon S3 will use the encryption settings values from the CreateSession request to protect new objects in the directory bucket. \n
When you use the CLI or the Amazon Web Services SDKs, for CreateSession, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the \n CreateSession request. It's not supported to override the encryption settings values in the CreateSession request. \n So in the Zonal endpoint API calls (except CopyObject and UploadPartCopy), \n the encryption request headers must match the default encryption configuration of the directory bucket.\n\n
\n S3 access points for Amazon FSx - When accessing data stored in\n Amazon FSx file systems using S3 access points, the only valid server side encryption option is\n aws:fsx. All Amazon FSx file systems have encryption configured by default and are\n encrypted at rest. Data is automatically encrypted before being written to the file system, and\n automatically decrypted as it is read. These processes are handled transparently by Amazon FSx.
By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The STANDARD\n storage class provides high durability and high availability. Depending on performance needs, you can\n specify a different Storage Class. For more information, see Storage Classes in the\n Amazon S3 User Guide.
\nDirectory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in\n Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in\n Dedicated Local Zones.
Amazon S3 on Outposts only uses the OUTPOSTS Storage Class.
\nIf the bucket is configured as a website, redirects requests for this object to another object in\n the same bucket or to an external URL. Amazon S3 stores the value of this header in the object\n metadata.
\nThis functionality is not supported for directory buckets.
\nSpecifies the algorithm to use when encrypting the object (for example, AES256).
\nThis functionality is not supported for directory buckets.
\nSpecifies the customer-provided encryption key for Amazon S3 to use in encrypting data. This value is\n used to store the object and then it is discarded; Amazon S3 does not store the encryption key. The key must\n be appropriate for use with the algorithm specified in the\n x-amz-server-side-encryption-customer-algorithm header.
This functionality is not supported for directory buckets.
\nSpecifies the 128-bit MD5 digest of the customer-provided encryption key according to RFC 1321. Amazon S3\n uses this header for a message integrity check to ensure that the encryption key was transmitted without\n error.
\nThis functionality is not supported for directory buckets.
\nSpecifies the KMS key ID (Key ID, Key ARN, or Key Alias) to use for object encryption. If the KMS key doesn't exist in the same\n account that's issuing the command, you must use the full Key ARN not the Key ID.
\n\n General purpose buckets - If you specify x-amz-server-side-encryption with aws:kms or aws:kms:dsse, this header specifies the ID (Key ID, Key ARN, or Key Alias) of the KMS \n key to use. If you specify\n x-amz-server-side-encryption:aws:kms or\n x-amz-server-side-encryption:aws:kms:dsse, but do not provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the Amazon Web Services managed key\n (aws/s3) to protect the data.
\n Directory buckets - To encrypt data using SSE-KMS, it's recommended to specify the \nx-amz-server-side-encryption header to aws:kms. Then, the x-amz-server-side-encryption-aws-kms-key-id header implicitly uses \nthe bucket's default KMS customer managed key ID. If you want to explicitly set the \n x-amz-server-side-encryption-aws-kms-key-id header, it must match the bucket's default customer managed key (using key ID or ARN, not alias). Your SSE-KMS configuration can only support 1 customer managed key per directory bucket's lifetime. \nThe Amazon Web Services managed key (aws/s3) isn't supported. \n \n Incorrect key specification results in an HTTP 400 Bad Request error.
Specifies the Amazon Web Services KMS Encryption Context to use for object encryption. The value of\n this header is a Base64 encoded string of a UTF-8 encoded JSON, which contains the encryption context as key-value pairs.
\n\n Directory buckets - You can optionally provide an explicit encryption context value. The value must match the default encryption context - the bucket Amazon Resource Name (ARN). An additional encryption context value is not supported.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-context" } }, "BucketKeyEnabled": { "target": "com.amazonaws.s3#BucketKeyEnabled", "traits": { "smithy.api#documentation": "Specifies whether Amazon S3 should use an S3 Bucket Key for object encryption with\n server-side encryption using Key Management Service (KMS) keys (SSE-KMS).
\n\n General purpose buckets - Setting this header to\n true causes Amazon S3 to use an S3 Bucket Key for object encryption with\n SSE-KMS. Also, specifying this header with a PUT action doesn't affect bucket-level settings for S3\n Bucket Key.
\n Directory buckets - S3 Bucket Keys are always enabled for GET and PUT operations in a directory bucket and can\u2019t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through CopyObject, UploadPartCopy, the Copy operation in Batch Operations, or \n the import jobs. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.
The tag-set for the object. The tag-set must be encoded as URL Query parameters.
\nThis functionality is not supported for directory buckets.
\nSpecifies the Object Lock mode that you want to apply to the uploaded object.
\nThis functionality is not supported for directory buckets.
\nSpecifies the date and time when you want the Object Lock to expire.
\nThis functionality is not supported for directory buckets.
\nSpecifies whether you want to apply a legal hold to the uploaded object.
\nThis functionality is not supported for directory buckets.
\nThe account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Indicates the algorithm that you want Amazon S3 to use to create the checksum for the object. For more information, see\n Checking object integrity in\n the Amazon S3 User Guide.
", "smithy.api#httpHeader": "x-amz-checksum-algorithm" } }, "ChecksumType": { "target": "com.amazonaws.s3#ChecksumType", "traits": { "smithy.api#documentation": "Indicates the checksum type that you want Amazon S3 to use to calculate the object\u2019s checksum value. For\n more information, see Checking object integrity in the Amazon S3\n User Guide.
", "smithy.api#httpHeader": "x-amz-checksum-type" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#CreateSession": { "type": "operation", "input": { "target": "com.amazonaws.s3#CreateSessionRequest" }, "output": { "target": "com.amazonaws.s3#CreateSessionOutput" }, "errors": [ { "target": "com.amazonaws.s3#NoSuchBucket" } ], "traits": { "smithy.api#documentation": "Creates a session that establishes temporary security credentials to support fast authentication and\n authorization for the Zonal endpoint API operations on directory buckets. For more information about Zonal endpoint API operations that\n include the Availability Zone in the request endpoint, see S3 Express One Zone APIs in the\n Amazon S3 User Guide.
\nTo make Zonal endpoint API requests on a directory bucket, use the CreateSession API\n operation. Specifically, you grant s3express:CreateSession permission to a bucket in\n a bucket policy or an IAM identity-based policy. Then, you use IAM credentials to make the CreateSession\n API request on the bucket, which returns temporary security credentials that include the access key ID,\n secret access key, session token, and expiration. These credentials have associated permissions to\n access the Zonal endpoint API operations. After the session is created, you don\u2019t need to use other policies to grant\n permissions to each Zonal endpoint API individually. Instead, in your Zonal endpoint API requests, you sign your\n requests by applying the temporary security credentials of the session to the request headers and\n following the SigV4 protocol for authentication. You also apply the session token to the\n x-amz-s3session-token request header for authorization. Temporary security credentials\n are scoped to the bucket and expire after 5 minutes. After the expiration time, any calls that you make\n with those credentials will fail. You must use IAM credentials again to make a\n CreateSession API request that generates a new set of temporary credentials for use.\n Temporary credentials cannot be extended or refreshed beyond the original specified interval.
If you use Amazon Web Services SDKs, SDKs handle the session token refreshes automatically to avoid service\n interruptions when a session expires. We recommend that you use the Amazon Web Services SDKs to initiate and manage\n requests to the CreateSession API. For more information, see Performance guidelines and design patterns in the\n Amazon S3 User Guide.
\nYou must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n \n CopyObject API operation - Unlike other\n Zonal endpoint API operations, the CopyObject API operation doesn't use the temporary security\n credentials returned from the CreateSession API operation for authentication and\n authorization. For information about authentication and authorization of the\n CopyObject API operation on directory buckets, see CopyObject.
\n \n HeadBucket API operation - Unlike other\n Zonal endpoint API operations, the HeadBucket API operation doesn't use the temporary security\n credentials returned from the CreateSession API operation for authentication and\n authorization. For information about authentication and authorization of the\n HeadBucket API operation on directory buckets, see HeadBucket.
To obtain temporary security credentials, you must create a bucket policy or an IAM identity-based policy that\n grants s3express:CreateSession permission to the bucket. In a policy, you can have\n the s3express:SessionMode condition key to control who can create a\n ReadWrite or ReadOnly session. For more information about\n ReadWrite or ReadOnly sessions, see \n x-amz-create-session-mode\n . For example policies, see Example\n bucket policies for S3 Express One Zone and Amazon Web Services Identity\n and Access Management (IAM) identity-based policies for S3 Express One Zone in the\n Amazon S3 User Guide.
To grant cross-account access to Zonal endpoint API operations, the bucket policy should also grant both\n accounts the s3express:CreateSession permission.
If you want to encrypt objects with SSE-KMS, you must also have the\n kms:GenerateDataKey and the kms:Decrypt permissions in IAM\n identity-based policies and KMS key policies for the target KMS key.
For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n CreateSession requests or PUT object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n information, see Protecting data with server-side encryption in the Amazon S3 User Guide. For more information about the encryption overriding behaviors in directory buckets, see Specifying server-side encryption with KMS for new object uploads.
For Zonal endpoint (object-level) API operations except CopyObject and UploadPartCopy, \nyou authenticate and authorize requests through CreateSession for low latency. \n To encrypt new objects in a directory bucket with SSE-KMS, you must specify SSE-KMS as the directory bucket's default encryption configuration with a KMS key (specifically, a customer managed key). Then, when a session is created for Zonal endpoint API operations, new objects are automatically encrypted and decrypted with SSE-KMS and S3 Bucket Keys during the session.
\n\n Only 1 customer managed key is supported per directory bucket for the lifetime of the bucket. The Amazon Web Services managed key (aws/s3) isn't supported. \n After you specify SSE-KMS as your bucket's default encryption configuration with a customer managed key, you can't change the customer managed key for the bucket's SSE-KMS configuration.\n
In the Zonal endpoint API calls (except CopyObject and UploadPartCopy) using the REST API, \n you can't override the values of the encryption settings (x-amz-server-side-encryption, x-amz-server-side-encryption-aws-kms-key-id, x-amz-server-side-encryption-context, and x-amz-server-side-encryption-bucket-key-enabled) from the CreateSession request. \n You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and \n Amazon S3 will use the encryption settings values from the CreateSession request to protect new objects in the directory bucket. \n
When you use the CLI or the Amazon Web Services SDKs, for CreateSession, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the \n CreateSession request. It's not supported to override the encryption settings values in the CreateSession request. \n Also, in the Zonal endpoint API calls (except CopyObject and UploadPartCopy), \n it's not supported to override the values of the encryption settings from the CreateSession request. \n\n
\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The server-side encryption algorithm used when you store objects in the directory bucket.
\nWhen accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side\n encryption option is aws:fsx.
If you specify x-amz-server-side-encryption with aws:kms, this header indicates the ID of the KMS \n symmetric encryption customer managed key that was used for object encryption.
If present, indicates the Amazon Web Services KMS Encryption Context to use for object encryption. The value of\n this header is a Base64 encoded string of a UTF-8 encoded JSON, which contains the encryption context as key-value pairs. \n This value is stored as object metadata and automatically gets\n passed on to Amazon Web Services KMS for future GetObject \n operations on this object.
Indicates whether to use an S3 Bucket Key for server-side encryption\n with KMS keys (SSE-KMS).
", "smithy.api#httpHeader": "x-amz-server-side-encryption-bucket-key-enabled" } }, "Credentials": { "target": "com.amazonaws.s3#SessionCredentials", "traits": { "smithy.api#documentation": "The established temporary security credentials for the created session.
", "smithy.api#required": {}, "smithy.api#xmlName": "Credentials" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "CreateSessionResult" } }, "com.amazonaws.s3#CreateSessionRequest": { "type": "structure", "members": { "SessionMode": { "target": "com.amazonaws.s3#SessionMode", "traits": { "smithy.api#documentation": "Specifies the mode of the session that will be created, either ReadWrite or\n ReadOnly. By default, a ReadWrite session is created. A\n ReadWrite session is capable of executing all the Zonal endpoint API operations on a directory bucket. A\n ReadOnly session is constrained to execute the following Zonal endpoint API operations:\n GetObject, HeadObject, ListObjectsV2,\n GetObjectAttributes, ListParts, and\n ListMultipartUploads.
The name of the bucket that you create a session for.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ServerSideEncryption": { "target": "com.amazonaws.s3#ServerSideEncryption", "traits": { "smithy.api#documentation": "The server-side encryption algorithm to use when you store objects in the directory bucket.
\nFor directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). By default, Amazon S3 encrypts data with SSE-S3. \n For more\n information, see Protecting data with server-side encryption in the Amazon S3 User Guide.
\n S3 access points for Amazon FSx - When accessing data stored in Amazon FSx\n file systems using S3 access points, the only valid server side encryption option is aws:fsx. All\n Amazon FSx file systems have encryption configured by default and are encrypted at rest. Data is\n automatically encrypted before being written to the file system, and automatically decrypted as it is\n read. These processes are handled transparently by Amazon FSx.
If you specify x-amz-server-side-encryption with aws:kms, you must specify the \n x-amz-server-side-encryption-aws-kms-key-id header with the ID (Key ID or Key ARN) of the KMS \n symmetric encryption customer managed key to use. Otherwise, you get an HTTP 400 Bad Request error. Only use the key ID or key ARN. The key alias format of the KMS key isn't supported. Also, if the KMS key doesn't exist in the same\n account that't issuing the command, you must use the full Key ARN not the Key ID.
Your SSE-KMS configuration can only support 1 customer managed key per directory bucket's lifetime. \nThe Amazon Web Services managed key (aws/s3) isn't supported. \n
Specifies the Amazon Web Services KMS Encryption Context as an additional encryption context to use for object encryption. The value of\n this header is a Base64 encoded string of a UTF-8 encoded JSON, which contains the encryption context as key-value pairs. \n This value is stored as object metadata and automatically gets passed on\n to Amazon Web Services KMS for future GetObject operations on\n this object.
\n General purpose buckets - This value must be explicitly added during CopyObject operations if you want an additional encryption context for your object. For more information, see Encryption context in the Amazon S3 User Guide.
\n Directory buckets - You can optionally provide an explicit encryption context value. The value must match the default encryption context - the bucket Amazon Resource Name (ARN). An additional encryption context value is not supported.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-context" } }, "BucketKeyEnabled": { "target": "com.amazonaws.s3#BucketKeyEnabled", "traits": { "smithy.api#documentation": "Specifies whether Amazon S3 should use an S3 Bucket Key for object encryption with\n server-side encryption using KMS keys (SSE-KMS).
\nS3 Bucket Keys are always enabled for GET and PUT operations in a directory bucket and can\u2019t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through CopyObject, UploadPartCopy, the Copy operation in Batch Operations, or \n the import jobs. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.
The default Object Lock retention mode you want to apply to new objects placed in the specified\n bucket. Must be used with either Days or Years.
The number of days that you want to specify for the default retention period. Must be used with\n Mode.
The number of years that you want to specify for the default retention period. Must be used with\n Mode.
The container element for optionally specifying the default Object Lock retention settings for new\n objects placed in the specified bucket.
\nThe DefaultRetention settings require both a mode and a period.
The DefaultRetention period can be either Days or Years\n but you must select one. You cannot specify Days and Years at the same\n time.
The object to delete.
\n\n Directory buckets - For directory buckets, an object\n that's composed entirely of whitespace characters is not supported by the DeleteObjects\n API operation. The request will receive a 400 Bad Request error and none of the objects\n in the request will be deleted.
Element to enable quiet mode for the request. When you add this element, you must set its value to\n true.
Container for the objects to delete.
" } }, "com.amazonaws.s3#DeleteBucket": { "type": "operation", "input": { "target": "com.amazonaws.s3#DeleteBucketRequest" }, "output": { "target": "smithy.api#Unit" }, "traits": { "smithy.api#documentation": "Deletes the S3 bucket. All objects (including all object versions and delete markers) in the bucket\n must be deleted before the bucket itself can be deleted.
\n\n Directory buckets - If multipart uploads in a\n directory bucket are in progress, you can't delete the bucket until all the in-progress multipart\n uploads are aborted or completed.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. \nFor more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n General purpose bucket permissions - You must have the\n s3:DeleteBucket permission on the specified bucket in a policy.
\n Directory bucket permissions - You must have the\n s3express:DeleteBucket permission in an IAM identity-based policy instead of a bucket policy.\n Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource. For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
\n Directory buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following operations are related to DeleteBucket:
\n CreateBucket\n
\n\n DeleteObject\n
\nThis operation is not supported for directory buckets.
\nDeletes an analytics configuration for the bucket (specified by the analytics configuration\n ID).
\nTo use this operation, you must have permissions to perform the\n s3:PutAnalyticsConfiguration action. The bucket owner has this permission by default. The\n 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\n Resources.
For information about the Amazon S3 analytics feature, see Amazon S3 Analytics \u2013 Storage Class\n Analysis.
\nThe following operations are related to DeleteBucketAnalyticsConfiguration:
The name of the bucket from which an analytics configuration is deleted.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Id": { "target": "com.amazonaws.s3#AnalyticsId", "traits": { "smithy.api#documentation": "The ID that identifies the analytics configuration.
", "smithy.api#httpQuery": "id", "smithy.api#required": {} } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nDeletes the cors configuration information set for the bucket.
To use this operation, you must have permission to perform the s3:PutBucketCORS action.\n The bucket owner has this permission by default and can grant this permission to others.
For information about cors, see Enabling Cross-Origin Resource Sharing in the\n Amazon S3 User Guide.
\n Related Resources\n
\n\n PutBucketCors\n
\n\n RESTOPTIONSobject\n
\nSpecifies the bucket whose cors configuration is being deleted.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This implementation of the DELETE action resets the default encryption for the bucket as server-side\n encryption with Amazon S3 managed keys (SSE-S3).
\n\n General purpose buckets - For information about the bucket\n default encryption feature, see Amazon S3 Bucket Default Encryption in the\n Amazon S3 User Guide.
\n\n Directory buckets -\n For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. For information about the default encryption configuration in\n directory buckets, see Setting default server-side\n encryption behavior for directory buckets.
\n\n General purpose bucket permissions - The\n s3:PutEncryptionConfiguration permission is required in a policy. The bucket\n owner has this permission by default. The bucket owner can grant this permission to others.\n For more information about permissions, see Permissions Related to Bucket Operations and Managing Access Permissions to Your\n Amazon S3 Resources.
\n Directory bucket permissions - To grant access to\n this API operation, you must have the s3express:PutEncryptionConfiguration\n permission in an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.\n For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
\n Directory buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following operations are related to DeleteBucketEncryption:
\n PutBucketEncryption\n
\n\n GetBucketEncryption\n
\nThe name of the bucket containing the server-side encryption configuration to delete.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n DOC-EXAMPLE-BUCKET--usw2-az1--x-s3). For information about bucket naming restrictions, see Directory bucket naming rules in the Amazon S3 User Guide\n
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
For directory buckets, this header is not supported in this API operation. If you specify this header, the request fails with the HTTP status code \n501 Not Implemented.
This operation is not supported for directory buckets.
\nDeletes the S3 Intelligent-Tiering configuration from the specified bucket.
\nThe S3 Intelligent-Tiering storage class is designed to optimize storage costs by automatically moving data to the most cost-effective storage access tier, without performance impact or operational overhead. S3 Intelligent-Tiering delivers automatic cost savings in three low latency and high throughput access tiers. To get the lowest storage cost on data that can be accessed in minutes to hours, you can choose to activate additional archiving capabilities.
\nThe S3 Intelligent-Tiering storage class is the ideal storage class for data with unknown, changing, or unpredictable access patterns, independent of object size or retention period. If the size of an object is less than 128 KB, it is not monitored and not eligible for auto-tiering. Smaller objects can be stored, but they are always charged at the Frequent Access tier rates in the S3 Intelligent-Tiering storage class.
\nFor more information, see Storage class for automatically optimizing frequently and infrequently accessed objects.
\nOperations related to DeleteBucketIntelligentTieringConfiguration include:
The name of the Amazon S3 bucket whose configuration you want to modify or retrieve.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Id": { "target": "com.amazonaws.s3#IntelligentTieringId", "traits": { "smithy.api#documentation": "The ID used to identify the S3 Intelligent-Tiering configuration.
", "smithy.api#httpQuery": "id", "smithy.api#required": {} } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nDeletes an S3 Inventory configuration (identified by the inventory ID) from the bucket.
\nTo use this operation, you must have permissions to perform the\n s3:PutInventoryConfiguration action. The bucket owner has this permission by default. The\n 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\n Resources.
For information about the Amazon S3 inventory feature, see Amazon S3 Inventory.
\nOperations related to DeleteBucketInventoryConfiguration include:
The name of the bucket containing the inventory configuration to delete.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Id": { "target": "com.amazonaws.s3#InventoryId", "traits": { "smithy.api#documentation": "The ID used to identify the inventory configuration.
", "smithy.api#httpQuery": "id", "smithy.api#required": {} } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Deletes the lifecycle configuration from the specified bucket. Amazon S3 removes all the lifecycle\n configuration rules in the lifecycle subresource associated with the bucket. Your objects never expire,\n and Amazon S3 no longer automatically deletes any objects on the basis of rules contained in the deleted\n lifecycle configuration.
\n\n General purpose bucket permissions - By default, all Amazon S3\n resources are private, including buckets, objects, and related subresources (for example,\n lifecycle configuration and website configuration). Only the resource owner (that is, the\n Amazon Web Services account that created it) can access the resource. The resource owner can optionally\n grant access permissions to others by writing an access policy. For this operation, a user\n must have the s3:PutLifecycleConfiguration permission.
For more information about permissions, see Managing Access Permissions to Your\n Amazon S3 Resources.
\n\n Directory bucket permissions - You must have the\n s3express:PutLifecycleConfiguration permission in an IAM identity-based policy\n to use this operation. Cross-account access to this API operation isn't supported. The\n resource owner can optionally grant access permissions to others by creating a role or user\n for them as long as they are within the same account as the owner and resource.
For more information about directory bucket policies and permissions, see Authorizing Regional endpoint APIs with IAM in the Amazon S3 User\n Guide.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. \nFor more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n Directory buckets - The HTTP Host header syntax is\n s3express-control.region.amazonaws.com.
For more information about the object expiration, see Elements to\n Describe Lifecycle Actions.
\nRelated actions include:
\nThe bucket name of the lifecycle to delete.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This parameter applies to general purpose buckets only. It is not supported for directory bucket\n lifecycle configurations.
\nDeletes an S3 Metadata configuration from a general purpose bucket. For more information, see\n Accelerating\n data discovery with S3 Metadata in the Amazon S3 User Guide.
\nYou can use the V2 DeleteBucketMetadataConfiguration API operation with V1 or V2 \n metadata configurations. However, if you try to use the V1 \n DeleteBucketMetadataTableConfiguration API operation with V2 configurations, you\n will receive an HTTP 405 Method Not Allowed error.
To use this operation, you must have the\n s3:DeleteBucketMetadataTableConfiguration permission. For more information, see\n Setting up permissions for configuring metadata tables in the\n Amazon S3 User Guide.
The IAM policy action name is the same for the V1 and V2 API operations.
\nThe following operations are related to DeleteBucketMetadataConfiguration:
\n The general purpose bucket that you want to remove the metadata configuration from.\n
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "\n The expected bucket owner of the general purpose bucket that you want to remove the metadata table\n configuration from.\n
", "smithy.api#httpHeader": "x-amz-expected-bucket-owner" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#DeleteBucketMetadataTableConfiguration": { "type": "operation", "input": { "target": "com.amazonaws.s3#DeleteBucketMetadataTableConfigurationRequest" }, "output": { "target": "smithy.api#Unit" }, "traits": { "smithy.api#documentation": "\n We recommend that you delete your S3 Metadata configurations by using the V2 \n DeleteBucketMetadataTableConfiguration API operation. We no longer recommend using \n the V1 DeleteBucketMetadataTableConfiguration API operation.\n
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete \n and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create \n a live inventory table.
\nDeletes a V1 S3 Metadata configuration from a general purpose bucket. For more information, see\n Accelerating\n data discovery with S3 Metadata in the Amazon S3 User Guide.
\nYou can use the V2 DeleteBucketMetadataConfiguration API operation with V1 or V2 \n metadata table configurations. However, if you try to use the V1 \n DeleteBucketMetadataTableConfiguration API operation with V2 configurations, you\n will receive an HTTP 405 Method Not Allowed error.
Make sure that you update your processes to use the new V2 API operations\n (CreateBucketMetadataConfiguration, GetBucketMetadataConfiguration, and\n DeleteBucketMetadataConfiguration) instead of the V1 API operations.
To use this operation, you must have the\n s3:DeleteBucketMetadataTableConfiguration permission. For more information, see\n Setting up permissions for configuring metadata tables in the\n Amazon S3 User Guide.
The following operations are related to DeleteBucketMetadataTableConfiguration:
The general purpose bucket that you want to remove the metadata table configuration from.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The expected bucket owner of the general purpose bucket that you want to remove the metadata table\n configuration from.
", "smithy.api#httpHeader": "x-amz-expected-bucket-owner" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#DeleteBucketMetricsConfiguration": { "type": "operation", "input": { "target": "com.amazonaws.s3#DeleteBucketMetricsConfigurationRequest" }, "output": { "target": "smithy.api#Unit" }, "traits": { "smithy.api#documentation": "This operation is not supported for directory buckets.
\nDeletes a metrics configuration for the Amazon CloudWatch request metrics (specified by the metrics\n configuration ID) from the bucket. Note that this doesn't include the daily storage metrics.
\n To use this operation, you must have permissions to perform the\n s3:PutMetricsConfiguration action. The bucket owner has this permission by default. The\n 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\n Resources.
For information about CloudWatch request metrics for Amazon S3, see Monitoring Metrics with Amazon CloudWatch.
\nThe following operations are related to DeleteBucketMetricsConfiguration:
The name of the bucket containing the metrics configuration to delete.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Id": { "target": "com.amazonaws.s3#MetricsId", "traits": { "smithy.api#documentation": "The ID used to identify the metrics configuration. The ID has a 64 character limit and can only\n contain letters, numbers, periods, dashes, and underscores.
", "smithy.api#httpQuery": "id", "smithy.api#required": {} } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nRemoves OwnershipControls for an Amazon S3 bucket. To use this operation, you must have the\n s3:PutBucketOwnershipControls permission. For more information about Amazon S3 permissions,\n see Specifying\n Permissions in a Policy.
For information about Amazon S3 Object Ownership, see Using Object Ownership.
\nThe following operations are related to DeleteBucketOwnershipControls:
The Amazon S3 bucket whose OwnershipControls you want to delete.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Deletes the policy of a specified bucket.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. \nFor more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
If you are using an identity other than the root user of the Amazon Web Services account that owns the\n bucket, the calling identity must both have the DeleteBucketPolicy permissions on the\n specified bucket and belong to the bucket owner's account in order to use this operation.
If you don't have DeleteBucketPolicy permissions, Amazon S3 returns a 403 Access\n Denied error. If you have the correct permissions, but you're not using an identity that\n belongs to the bucket owner's account, Amazon S3 returns a 405 Method Not Allowed\n error.
To ensure that bucket owners don't inadvertently lock themselves out of their own buckets,\n the root principal in a bucket owner's Amazon Web Services account can perform the\n GetBucketPolicy, PutBucketPolicy, and\n DeleteBucketPolicy API actions, even if their bucket policy explicitly denies the\n root principal's access. Bucket owner root principals can only be blocked from performing these\n API actions by VPC endpoint policies and Amazon Web Services Organizations policies.
\n General purpose bucket permissions - The\n s3:DeleteBucketPolicy permission is required in a policy. For more information\n about general purpose buckets bucket policies, see Using Bucket Policies and User\n Policies in the Amazon S3 User Guide.
\n Directory bucket permissions - To grant access to\n this API operation, you must have the s3express:DeleteBucketPolicy permission in\n an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.\n For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
\n Directory buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following operations are related to DeleteBucketPolicy\n
\n CreateBucket\n
\n\n DeleteObject\n
\nThe bucket name.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n DOC-EXAMPLE-BUCKET--usw2-az1--x-s3). For information about bucket naming restrictions, see Directory bucket naming rules in the Amazon S3 User Guide\n
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
For directory buckets, this header is not supported in this API operation. If you specify this header, the request fails with the HTTP status code \n501 Not Implemented.
This operation is not supported for directory buckets.
\nDeletes the replication configuration from the bucket.
\nTo use this operation, you must have permissions to perform the\n s3:PutReplicationConfiguration action. The bucket owner has these permissions by default\n and can grant it to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3\n Resources.
It can take a while for the deletion of a replication configuration to fully propagate.
\nFor information about replication configuration, see Replication in the\n Amazon S3 User Guide.
\nThe following operations are related to DeleteBucketReplication:
\n PutBucketReplication\n
\n\n GetBucketReplication\n
\nThe bucket name.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Specifies the bucket being deleted.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n DOC-EXAMPLE-BUCKET--usw2-az1--x-s3). For information about bucket naming restrictions, see Directory bucket naming rules in the Amazon S3 User Guide\n
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
For directory buckets, this header is not supported in this API operation. If you specify this header, the request fails with the HTTP status code \n501 Not Implemented.
This operation is not supported for directory buckets.
\nDeletes the tags from the bucket.
\nTo use this operation, you must have permission to perform the s3:PutBucketTagging\n action. By default, the bucket owner has this permission and can grant this permission to others.
The following operations are related to DeleteBucketTagging:
\n GetBucketTagging\n
\n\n PutBucketTagging\n
\nThe bucket that has the tag set to be removed.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nThis action removes the website configuration for a bucket. Amazon S3 returns a 200 OK\n response upon successfully deleting a website configuration on the specified bucket. You will get a\n 200 OK response if the website configuration you are trying to delete does not exist on\n the bucket. Amazon S3 returns a 404 response if the bucket specified in the request does not\n exist.
This DELETE action requires the S3:DeleteBucketWebsite permission. By default, only the\n bucket owner can delete the website configuration attached to a bucket. However, bucket owners can grant\n other users permission to delete the website configuration by writing a bucket policy granting them the\n S3:DeleteBucketWebsite permission.
For more information about hosting websites, see Hosting Websites on Amazon S3.
\nThe following operations are related to DeleteBucketWebsite:
\n GetBucketWebsite\n
\n\n PutBucketWebsite\n
\nThe bucket name for which you want to remove the website configuration.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The account that created the delete marker.
" } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "The object key.
" } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "Version ID of an object.
" } }, "IsLatest": { "target": "com.amazonaws.s3#IsLatest", "traits": { "smithy.api#documentation": "Specifies whether the object is (true) or is not (false) the latest version of an object.
" } }, "LastModified": { "target": "com.amazonaws.s3#LastModified", "traits": { "smithy.api#documentation": "Date and time when the object was last modified.
" } } }, "traits": { "smithy.api#documentation": "Information about the delete marker.
" } }, "com.amazonaws.s3#DeleteMarkerReplication": { "type": "structure", "members": { "Status": { "target": "com.amazonaws.s3#DeleteMarkerReplicationStatus", "traits": { "smithy.api#documentation": "Indicates whether to replicate delete markers.
\nIndicates whether to replicate delete markers.
\nSpecifies whether Amazon S3 replicates delete markers. If you specify a Filter in your\n replication configuration, you must also include a DeleteMarkerReplication element. If your\n Filter includes a Tag element, the DeleteMarkerReplication\n Status must be set to Disabled, because Amazon S3 does not support replicating delete markers\n for tag-based rules. For an example configuration, see Basic Rule\n Configuration.
For more information about delete marker replication, see Basic Rule Configuration.
\nIf you are using an earlier version of the replication configuration, Amazon S3 handles replication of\n delete markers differently. For more information, see Backward Compatibility.
\nRemoves an object from a bucket. The behavior depends on the bucket's versioning state:
\nIf bucket versioning is not enabled, the operation permanently deletes the object.
\nIf bucket versioning is enabled, the operation inserts a delete marker, which becomes the\n current version of the object. To permanently delete an object in a versioned bucket, you must\n include the object\u2019s versionId in the request. For more information about\n versioning-enabled buckets, see Deleting object versions from a\n versioning-enabled bucket.
If bucket versioning is suspended, the operation removes the object that has a null\n versionId, if there is one, and inserts a delete marker that becomes the current\n version of the object. If there isn't an object with a null versionId, and all versions\n of the object have a versionId, Amazon S3 does not remove the object and only inserts a\n delete marker. To permanently delete an object that has a versionId, you must include\n the object\u2019s versionId in the request. For more information about versioning-suspended\n buckets, see Deleting\n objects from versioning-suspended buckets.
\n Directory buckets - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets.\n You can only specify null to the versionId query parameter in the\n request.
\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
To remove a specific version, you must use the versionId query parameter. Using this\n query parameter permanently deletes the version. If the object deleted is a delete marker, Amazon S3 sets the\n response header x-amz-delete-marker to true.
If the object you want to delete is in a bucket where the bucket versioning configuration is MFA\n Delete enabled, you must include the x-amz-mfa request header in the DELETE\n versionId request. Requests that include x-amz-mfa must use HTTPS. For more\n information about MFA Delete, see Using MFA Delete in the Amazon S3 User\n Guide. To see sample requests that use versioning, see Sample Request.
\n Directory buckets - MFA delete is not supported by directory buckets.
\nYou can delete objects by explicitly calling DELETE Object or calling (PutBucketLifecycle) to enable Amazon S3 to\n remove them for you. If you want to block users or accounts from removing or deleting objects from your\n bucket, you must deny them the s3:DeleteObject, s3:DeleteObjectVersion, and\n s3:PutLifeCycleConfiguration actions.
\n Directory buckets -\n S3 Lifecycle is not supported by directory buckets.
\n\n General purpose bucket permissions - The following\n permissions are required in your policies when your DeleteObjects request\n includes specific headers.
\n \n s3:DeleteObject\n - To delete an\n object from a bucket, you must always have the s3:DeleteObject\n permission.
\n \n s3:DeleteObjectVersion\n - To delete a specific version of an object from a versioning-enabled\n bucket, you must have the s3:DeleteObjectVersion permission.
\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following action is related to DeleteObject:
\n PutObject\n
\nIndicates whether the specified object version that was permanently deleted was (true) or was not\n (false) a delete marker before deletion. In a simple DELETE, this header indicates whether (true) or not\n (false) the current version of the object is a delete marker. To learn more about delete markers, see\n Working with delete\n markers.
\nThis functionality is not supported for directory buckets.
\nReturns the version ID of the delete marker created as a result of the DELETE operation.
\nThis functionality is not supported for directory buckets.
\nThe bucket name of the bucket containing the object.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Key name of the object to delete.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Key" } } }, "MFA": { "target": "com.amazonaws.s3#MFA", "traits": { "smithy.api#documentation": "The concatenation of the authentication device's serial number, a space, and the value that is\n displayed on your authentication device. Required to permanently delete a versioned object if versioning\n is configured with MFA delete enabled.
\nThis functionality is not supported for directory buckets.
\nVersion ID used to reference a specific version of the object.
\nFor directory buckets in this API operation, only the null value of the version ID is supported.
Indicates whether S3 Object Lock should bypass Governance-mode restrictions to process this\n operation. To use this header, you must have the s3:BypassGovernanceRetention\n permission.
This functionality is not supported for directory buckets.
\nThe account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The If-Match header field makes the request method conditional on ETags. If the ETag\n value does not match, the operation returns a 412 Precondition Failed error. If the ETag\n matches or if the object doesn't exist, the operation will return a 204 Success (No Content)\n response.
For more information about conditional requests, see RFC 7232.
\nThis functionality is only supported for directory buckets.
\nIf present, the object is deleted only if its modification times matches the provided\n Timestamp. If the Timestamp values do not match, the operation returns a\n 412 Precondition Failed error. If the Timestamp matches or if the object\n doesn\u2019t exist, the operation returns a 204 Success (No Content) response.
This functionality is only supported for directory buckets.
\nIf present, the object is deleted only if its size matches the provided size in bytes. If the\n Size value does not match, the operation returns a 412 Precondition Failed\n error. If the Size matches or if the object doesn\u2019t exist, the operation returns a\n 204 Success (No Content) response.
This functionality is only supported for directory buckets.
\nYou can use the If-Match, x-amz-if-match-last-modified-time and\n x-amz-if-match-size conditional headers in conjunction with each-other or\n individually.
This operation is not supported for directory buckets.
\nRemoves the entire tag set from the specified object. For more information about managing object\n tags, see Object\n Tagging.
\nTo use this operation, you must have permission to perform the s3:DeleteObjectTagging\n action.
To delete tags of a specific object version, add the versionId query parameter in the\n request. You will need permission for the s3:DeleteObjectVersionTagging action.
The following operations are related to DeleteObjectTagging:
\n PutObjectTagging\n
\n\n GetObjectTagging\n
\nThe versionId of the object the tag-set was removed from.
", "smithy.api#httpHeader": "x-amz-version-id" } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#DeleteObjectTaggingRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name containing the objects from which to remove the tags.
\n\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
The key that identifies the object in the bucket from which to remove all tags.
", "smithy.api#httpLabel": {}, "smithy.api#required": {} } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "The versionId of the object that the tag-set will be removed from.
", "smithy.api#httpQuery": "versionId" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation enables you to delete multiple objects from a bucket using a single HTTP request. If\n you know the object keys that you want to delete, then this operation provides a suitable alternative to\n sending individual delete requests, reducing per-request overhead.
\nThe request can contain a list of up to 1,000 keys that you want to delete. In the XML, you provide\n the object key names, and optionally, version IDs if you want to delete a specific version of the object\n from a versioning-enabled bucket. For each key, Amazon S3 performs a delete operation and returns the result\n of that delete, success or failure, in the response. If the object specified in the request isn't found,\n Amazon S3 confirms the deletion by returning the result as deleted.
\n\n Directory buckets -\n S3 Versioning isn't enabled and supported for directory buckets.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
The operation supports two modes for the response: verbose and quiet. By default, the operation uses\n verbose mode in which the response includes the result of deletion of each key in your request. In quiet\n mode the response includes only keys where the delete operation encountered an error. For a successful\n deletion in a quiet mode, the operation does not return any information about the delete in the response\n body.
\nWhen performing this action on an MFA Delete enabled bucket, that attempts to delete any versioned\n objects, you must include an MFA token. If you do not provide one, the entire request will fail, even if\n there are non-versioned objects you are trying to delete. If you provide an invalid token, whether there\n are versioned keys in the request or not, the entire Multi-Object Delete request will fail. For\n information about MFA Delete, see MFA Delete in the\n Amazon S3 User Guide.
\n\n Directory buckets - MFA delete is not supported by directory buckets.
\n\n General purpose bucket permissions - The following\n permissions are required in your policies when your DeleteObjects request\n includes specific headers.
\n \n s3:DeleteObject\n - To delete an\n object from a bucket, you must always specify the s3:DeleteObject\n permission.
\n \n s3:DeleteObjectVersion\n - To delete a specific version of an object from a versioning-enabled\n bucket, you must specify the s3:DeleteObjectVersion permission.
\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
\n General purpose bucket - The Content-MD5 request header\n is required for all Multi-Object Delete requests. Amazon S3 uses the header value to ensure that\n your request body has not been altered in transit.
\n\n Directory bucket - The Content-MD5 request header\n or a additional checksum request header (including x-amz-checksum-crc32,\n x-amz-checksum-crc32c, x-amz-checksum-sha1, or\n x-amz-checksum-sha256) is required for all Multi-Object Delete requests.
\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following operations are related to DeleteObjects:
\n UploadPart\n
\n\n ListParts\n
\n\n AbortMultipartUpload\n
\nContainer element for a successful delete. It identifies the object that was successfully\n deleted.
", "smithy.api#xmlFlattened": {} } }, "RequestCharged": { "target": "com.amazonaws.s3#RequestCharged", "traits": { "smithy.api#httpHeader": "x-amz-request-charged" } }, "Errors": { "target": "com.amazonaws.s3#Errors", "traits": { "smithy.api#documentation": "Container for a failed delete action that describes the object that Amazon S3 attempted to delete and the\n error it encountered.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Error" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "DeleteResult" } }, "com.amazonaws.s3#DeleteObjectsRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name containing the objects to delete.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Container for the request.
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "Delete" } }, "MFA": { "target": "com.amazonaws.s3#MFA", "traits": { "smithy.api#documentation": "The concatenation of the authentication device's serial number, a space, and the value that is\n displayed on your authentication device. Required to permanently delete a versioned object if versioning\n is configured with MFA delete enabled.
\nWhen performing the DeleteObjects operation on an MFA delete enabled bucket, which\n attempts to delete the specified versioned objects, you must include an MFA token. If you don't provide\n an MFA token, the entire request will fail, even if there are non-versioned objects that you are trying\n to delete. If you provide an invalid token, whether there are versioned object keys in the request or\n not, the entire Multi-Object Delete request will fail. For information about MFA Delete, see MFA\n Delete in the Amazon S3 User Guide.
This functionality is not supported for directory buckets.
\nSpecifies whether you want to delete this object even if it has a Governance-type Object Lock in\n place. To use this header, you must have the s3:BypassGovernanceRetention\n permission.
This functionality is not supported for directory buckets.
\nThe account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum-algorithm\n or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request.
For the x-amz-checksum-algorithm\n header, replace \n algorithm\n with the supported algorithm from the following list:
\n CRC32\n
\n CRC32C\n
\n CRC64NVME\n
\n SHA1\n
\n SHA256\n
For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
\nIf the individual checksum value you provide through x-amz-checksum-algorithm\n doesn't match the checksum algorithm you set through x-amz-sdk-checksum-algorithm, Amazon S3 fails the request with a BadDigest error.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
This operation is not supported for directory buckets.
\nRemoves the PublicAccessBlock configuration for an Amazon S3 bucket. To use this operation,\n you must have the s3:PutBucketPublicAccessBlock permission. For more information about\n permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3\n Resources.
The following operations are related to DeletePublicAccessBlock:
\n GetPublicAccessBlock\n
\n\n PutPublicAccessBlock\n
\nThe Amazon S3 bucket whose PublicAccessBlock configuration you want to delete.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The name of the deleted object.
" } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "The version ID of the deleted object.
\nThis functionality is not supported for directory buckets.
\nIndicates whether the specified object version that was permanently deleted was (true) or was not\n (false) a delete marker before deletion. In a simple DELETE, this header indicates whether (true) or not\n (false) the current version of the object is a delete marker. To learn more about delete markers, see\n Working with delete\n markers.
\nThis functionality is not supported for directory buckets.
\nThe version ID of the delete marker created as a result of the DELETE operation. If you delete a\n specific object version, the value returned by this header is the version ID of the object version\n deleted.
\nThis functionality is not supported for directory buckets.
\nInformation about the deleted object.
" } }, "com.amazonaws.s3#DeletedObjects": { "type": "list", "member": { "target": "com.amazonaws.s3#DeletedObject" } }, "com.amazonaws.s3#Delimiter": { "type": "string" }, "com.amazonaws.s3#Description": { "type": "string" }, "com.amazonaws.s3#Destination": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The Amazon Resource Name (ARN) of the bucket where you want Amazon S3 to store the results.
", "smithy.api#required": {} } }, "Account": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "Destination bucket owner account ID. In a cross-account scenario, if you direct Amazon S3 to change\n replica ownership to the Amazon Web Services account that owns the destination bucket by specifying the\n AccessControlTranslation property, this is the account ID of the destination bucket\n owner. For more information, see Replication Additional Configuration: Changing\n the Replica Owner in the Amazon S3 User Guide.
The storage class to use when replicating objects, such as S3 Standard or reduced redundancy. By\n default, Amazon S3 uses the storage class of the source object to create the object replica.
\nFor valid values, see the StorageClass element of the PUT Bucket replication action in the\n Amazon S3 API Reference.
\n FSX_OPENZFS is not an accepted value when replicating objects.
Specify this only in a cross-account scenario (where source and destination bucket owners are not\n the same), and you want to change replica ownership to the Amazon Web Services account that owns the destination\n bucket. If this is not specified in the replication configuration, the replicas are owned by same\n Amazon Web Services account that owns the source object.
" } }, "EncryptionConfiguration": { "target": "com.amazonaws.s3#EncryptionConfiguration", "traits": { "smithy.api#documentation": "A container that provides information about encryption. If SourceSelectionCriteria is\n specified, you must specify this element.
A container specifying S3 Replication Time Control (S3 RTC), including whether S3 RTC is enabled and the time when all\n objects and operations on objects must be replicated. Must be specified together with a\n Metrics block.
A container specifying replication metrics-related settings enabling replication metrics and\n events.
" } } }, "traits": { "smithy.api#documentation": "Specifies information about where to publish analysis or configuration results for an Amazon S3 bucket\n and S3 Replication Time Control (S3 RTC).
" } }, "com.amazonaws.s3#DestinationResult": { "type": "structure", "members": { "TableBucketType": { "target": "com.amazonaws.s3#S3TablesBucketType", "traits": { "smithy.api#documentation": "\n The type of the table bucket where the metadata configuration is stored. The aws \n value indicates an Amazon Web Services managed table bucket, and the customer value indicates a \n customer-managed table bucket. V2 metadata configurations are stored in Amazon Web Services managed table \n buckets, and V1 metadata configurations are stored in customer-managed table buckets. \n
\n The Amazon Resource Name (ARN) of the table bucket where the metadata configuration is stored.\n
" } }, "TableNamespace": { "target": "com.amazonaws.s3#S3TablesNamespace", "traits": { "smithy.api#documentation": "\n The namespace in the table bucket where the metadata tables for a metadata configuration are \n stored.\n
" } } }, "traits": { "smithy.api#documentation": "\n The destination information for the S3 Metadata configuration.\n
" } }, "com.amazonaws.s3#DirectoryBucketToken": { "type": "string", "traits": { "smithy.api#length": { "min": 0, "max": 1024 } } }, "com.amazonaws.s3#DisplayName": { "type": "string" }, "com.amazonaws.s3#ETag": { "type": "string" }, "com.amazonaws.s3#EmailAddress": { "type": "string" }, "com.amazonaws.s3#EnableRequestProgress": { "type": "boolean" }, "com.amazonaws.s3#EncodingType": { "type": "enum", "members": { "url": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "url" } } }, "traits": { "smithy.api#documentation": "Encoding type used by Amazon S3 to encode the object keys in the response. Responses are\n encoded only in UTF-8. An object key can contain any Unicode character. However, the XML 1.0 parser\n can't parse certain characters, such as characters with an ASCII value from 0 to 10. For characters that\n aren't supported in XML 1.0, you can add this parameter to request that Amazon S3 encode the keys in the\n response. For more information about characters to avoid in object key names, see Object key\n naming guidelines.
\nWhen using the URL encoding type, non-ASCII characters that are used in an object's key name will\n be percent-encoded according to UTF-8 code values. For example, the object\n test_file(3).png will appear as test_file%283%29.png.
The server-side encryption algorithm used when storing job results in Amazon S3 (for example, AES256,\n aws:kms).
If the encryption type is aws:kms, this optional value specifies the ID of the\n symmetric encryption customer managed key to use for encryption of job results. Amazon S3 only supports symmetric\n encryption KMS keys. For more information, see Asymmetric keys in KMS in the\n Amazon Web Services Key Management Service Developer Guide.
If the encryption type is aws:kms, this optional value can be used to specify the\n encryption context for the restore results.
Contains the type of server-side encryption used.
" } }, "com.amazonaws.s3#EncryptionConfiguration": { "type": "structure", "members": { "ReplicaKmsKeyID": { "target": "com.amazonaws.s3#ReplicaKmsKeyID", "traits": { "smithy.api#documentation": "Specifies the ID (Key ARN or Alias ARN) of the customer managed Amazon Web Services KMS key stored in Amazon Web Services Key\n Management Service (KMS) for the destination bucket. Amazon S3 uses this key to encrypt replica objects. Amazon S3\n only supports symmetric encryption KMS keys. For more information, see Asymmetric keys in Amazon Web Services KMS in the\n Amazon Web Services Key Management Service Developer Guide.
" } } }, "traits": { "smithy.api#documentation": "Specifies encryption-related information for an Amazon S3 bucket that is a destination for replicated\n objects.
\nIf you're specifying a customer managed KMS key, we recommend using a fully qualified KMS key\n ARN. If you use a KMS key alias instead, then KMS resolves the key within the requester\u2019s account.\n This behavior can result in data that's encrypted with a KMS key that belongs to the requester, and\n not the bucket owner.
\nThe existing object was created with a different encryption type. Subsequent write requests must\n include the appropriate encryption parameters in the request or while creating the session.
", "smithy.api#error": "client", "smithy.api#httpError": 400 } }, "com.amazonaws.s3#End": { "type": "long" }, "com.amazonaws.s3#EndEvent": { "type": "structure", "members": {}, "traits": { "smithy.api#documentation": "A message that indicates the request is complete and no more messages will be sent. You should not\n assume that the request is complete until the client receives an EndEvent.
The error key.
" } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "The version ID of the error.
\nThis functionality is not supported for directory buckets.
\nThe error code is a string that uniquely identifies an error condition. It is meant to be read and\n understood by programs that detect and handle errors by type. The following is a list of Amazon S3 error\n codes. For more information, see Error responses.
\n\n Code: AccessDenied
\n\n Description: Access Denied
\n\n HTTP Status Code: 403 Forbidden
\n\n SOAP Fault Code Prefix: Client
\n\n Code: AccountProblem
\n\n Description: There is a problem with your Amazon Web Services account that prevents\n the action from completing successfully. Contact Amazon Web Services Support for further assistance.
\n\n HTTP Status Code: 403 Forbidden
\n\n SOAP Fault Code Prefix: Client
\n\n Code: AllAccessDisabled
\n\n Description: All access to this Amazon S3 resource has been disabled.\n Contact Amazon Web Services Support for further assistance.
\n\n HTTP Status Code: 403 Forbidden
\n\n SOAP Fault Code Prefix: Client
\n\n Code: AmbiguousGrantByEmailAddress
\n\n Description: The email address you provided is associated with more\n than one account.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: AuthorizationHeaderMalformed
\n\n Description: The authorization header you provided is invalid.
\n\n HTTP Status Code: 400 Bad Request
\n\n HTTP Status Code: N/A
\n\n Code: BadDigest
\n\n Description: The Content-MD5 you specified did not match what we\n received.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: BucketAlreadyExists
\n\n Description: The requested bucket name is not available. The bucket\n namespace is shared by all users of the system. Please select a different name and try\n again.
\n\n HTTP Status Code: 409 Conflict
\n\n SOAP Fault Code Prefix: Client
\n\n Code: BucketAlreadyOwnedByYou
\n\n Description: The bucket you tried to create already exists, and you own\n it. Amazon S3 returns this error in all Amazon Web Services Regions except in the North Virginia Region. For legacy\n compatibility, if you re-create an existing bucket that you already own in the North Virginia\n Region, Amazon S3 returns 200 OK and resets the bucket access control lists (ACLs).
\n\n Code: 409 Conflict (in all Regions except the North Virginia Region)\n
\n\n SOAP Fault Code Prefix: Client
\n\n Code: BucketNotEmpty
\n\n Description: The bucket you tried to delete is not empty.
\n\n HTTP Status Code: 409 Conflict
\n\n SOAP Fault Code Prefix: Client
\n\n Code: CredentialsNotSupported
\n\n Description: This request does not support credentials.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: CrossLocationLoggingProhibited
\n\n Description: Cross-location logging not allowed. Buckets in one\n geographic location cannot log information to a bucket in another location.
\n\n HTTP Status Code: 403 Forbidden
\n\n SOAP Fault Code Prefix: Client
\n\n Code: EntityTooSmall
\n\n Description: Your proposed upload is smaller than the minimum allowed\n object size.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: EntityTooLarge
\n\n Description: Your proposed upload exceeds the maximum allowed object\n size.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: ExpiredToken
\n\n Description: The provided token has expired.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: IllegalVersioningConfigurationException
\n\n Description: Indicates that the versioning configuration specified in\n the request is invalid.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: IncompleteBody
\n\n Description: You did not provide the number of bytes specified by the\n Content-Length HTTP header
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: IncorrectNumberOfFilesInPostRequest
\n\n Description: POST requires exactly one file upload per request.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InlineDataTooLarge
\n\n Description: Inline data exceeds the maximum allowed size.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InternalError
\n\n Description: We encountered an internal error. Please try again.
\n\n HTTP Status Code: 500 Internal Server Error
\n\n SOAP Fault Code Prefix: Server
\n\n Code: InvalidAccessKeyId
\n\n Description: The Amazon Web Services access key ID you provided does not exist in our\n records.
\n\n HTTP Status Code: 403 Forbidden
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidAddressingHeader
\n\n Description: You must specify the Anonymous role.
\n\n HTTP Status Code: N/A
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidArgument
\n\n Description: Invalid Argument
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidBucketName
\n\n Description: The specified bucket is not valid.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidBucketState
\n\n Description: The request is not valid with the current state of the\n bucket.
\n\n HTTP Status Code: 409 Conflict
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidDigest
\n\n Description: The Content-MD5 you specified is not valid.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidEncryptionAlgorithmError
\n\n Description: The encryption request you specified is not valid. The\n valid value is AES256.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidLocationConstraint
\n\n Description: The specified location constraint is not valid. For more\n information about Regions, see How to Select a Region for Your\n Buckets.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidObjectState
\n\n Description: The action is not valid for the current state of the\n object.
\n\n HTTP Status Code: 403 Forbidden
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidPart
\n\n Description: One or more of the specified parts could not be found. The\n part might not have been uploaded, or the specified entity tag might not have matched the part's\n entity tag.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidPartOrder
\n\n Description: The list of parts was not in ascending order. Parts list\n must be specified in order by part number.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidPayer
\n\n Description: All access to this object has been disabled. Please\n contact Amazon Web Services Support for further assistance.
\n\n HTTP Status Code: 403 Forbidden
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidPolicyDocument
\n\n Description: The content of the form does not meet the conditions\n specified in the policy document.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidRange
\n\n Description: The requested range cannot be satisfied.
\n\n HTTP Status Code: 416 Requested Range Not Satisfiable
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidRequest
\n\n Description: Please use AWS4-HMAC-SHA256.
\n HTTP Status Code: 400 Bad Request
\n\n Code: N/A
\n\n Code: InvalidRequest
\n\n Description: SOAP requests must be made over an HTTPS\n connection.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidRequest
\n\n Description: Amazon S3 Transfer Acceleration is not supported for buckets\n with non-DNS compliant names.
\n\n HTTP Status Code: 400 Bad Request
\n\n Code: N/A
\n\n Code: InvalidRequest
\n\n Description: Amazon S3 Transfer Acceleration is not supported for buckets\n with periods (.) in their names.
\n\n HTTP Status Code: 400 Bad Request
\n\n Code: N/A
\n\n Code: InvalidRequest
\n\n Description: Amazon S3 Transfer Accelerate endpoint only supports virtual\n style requests.
\n\n HTTP Status Code: 400 Bad Request
\n\n Code: N/A
\n\n Code: InvalidRequest
\n\n Description: Amazon S3 Transfer Accelerate is not configured on this\n bucket.
\n\n HTTP Status Code: 400 Bad Request
\n\n Code: N/A
\n\n Code: InvalidRequest
\n\n Description: Amazon S3 Transfer Accelerate is disabled on this\n bucket.
\n\n HTTP Status Code: 400 Bad Request
\n\n Code: N/A
\n\n Code: InvalidRequest
\n\n Description: Amazon S3 Transfer Acceleration is not supported on this\n bucket. Contact Amazon Web Services Support for more information.
\n\n HTTP Status Code: 400 Bad Request
\n\n Code: N/A
\n\n Code: InvalidRequest
\n\n Description: Amazon S3 Transfer Acceleration cannot be enabled on this\n bucket. Contact Amazon Web Services Support for more information.
\n\n HTTP Status Code: 400 Bad Request
\n\n Code: N/A
\n\n Code: InvalidSecurity
\n\n Description: The provided security credentials are not valid.
\n\n HTTP Status Code: 403 Forbidden
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidSOAPRequest
\n\n Description: The SOAP request body is invalid.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidStorageClass
\n\n Description: The storage class you specified is not valid.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidTargetBucketForLogging
\n\n Description: The target bucket for logging does not exist, is not owned\n by you, or does not have the appropriate grants for the log-delivery group.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidToken
\n\n Description: The provided token is malformed or otherwise\n invalid.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: InvalidURI
\n\n Description: Couldn't parse the specified URI.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: KeyTooLongError
\n\n Description: Your key is too long.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: MalformedACLError
\n\n Description: The XML you provided was not well-formed or did not\n validate against our published schema.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: MalformedPOSTRequest
\n\n Description: The body of your POST request is not well-formed\n multipart/form-data.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: MalformedXML
\n\n Description: This happens when the user sends malformed XML (XML that\n doesn't conform to the published XSD) for the configuration. The error message is, \"The XML you\n provided was not well-formed or did not validate against our published schema.\"
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: MaxMessageLengthExceeded
\n\n Description: Your request was too big.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: MaxPostPreDataLengthExceededError
\n\n Description: Your POST request fields preceding the upload file were\n too large.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: MetadataTooLarge
\n\n Description: Your metadata headers exceed the maximum allowed metadata\n size.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: MethodNotAllowed
\n\n Description: The specified method is not allowed against this\n resource.
\n\n HTTP Status Code: 405 Method Not Allowed
\n\n SOAP Fault Code Prefix: Client
\n\n Code: MissingAttachment
\n\n Description: A SOAP attachment was expected, but none were\n found.
\n\n HTTP Status Code: N/A
\n\n SOAP Fault Code Prefix: Client
\n\n Code: MissingContentLength
\n\n Description: You must provide the Content-Length HTTP header.
\n\n HTTP Status Code: 411 Length Required
\n\n SOAP Fault Code Prefix: Client
\n\n Code: MissingRequestBodyError
\n\n Description: This happens when the user sends an empty XML document as\n a request. The error message is, \"Request body is empty.\"
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: MissingSecurityElement
\n\n Description: The SOAP 1.1 request is missing a security element.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: MissingSecurityHeader
\n\n Description: Your request is missing a required header.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: NoLoggingStatusForKey
\n\n Description: There is no such thing as a logging status subresource for\n a key.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: NoSuchBucket
\n\n Description: The specified bucket does not exist.
\n\n HTTP Status Code: 404 Not Found
\n\n SOAP Fault Code Prefix: Client
\n\n Code: NoSuchBucketPolicy
\n\n Description: The specified bucket does not have a bucket policy.
\n\n HTTP Status Code: 404 Not Found
\n\n SOAP Fault Code Prefix: Client
\n\n Code: NoSuchKey
\n\n Description: The specified key does not exist.
\n\n HTTP Status Code: 404 Not Found
\n\n SOAP Fault Code Prefix: Client
\n\n Code: NoSuchLifecycleConfiguration
\n\n Description: The lifecycle configuration does not exist.
\n\n HTTP Status Code: 404 Not Found
\n\n SOAP Fault Code Prefix: Client
\n\n Code: NoSuchUpload
\n\n Description: The specified multipart upload does not exist. The upload\n ID might be invalid, or the multipart upload might have been aborted or completed.
\n\n HTTP Status Code: 404 Not Found
\n\n SOAP Fault Code Prefix: Client
\n\n Code: NoSuchVersion
\n\n Description: Indicates that the version ID specified in the request\n does not match an existing version.
\n\n HTTP Status Code: 404 Not Found
\n\n SOAP Fault Code Prefix: Client
\n\n Code: NotImplemented
\n\n Description: A header you provided implies functionality that is not\n implemented.
\n\n HTTP Status Code: 501 Not Implemented
\n\n SOAP Fault Code Prefix: Server
\n\n Code: NotSignedUp
\n\n Description: Your account is not signed up for the Amazon S3 service. You\n must sign up before you can use Amazon S3. You can sign up at the following URL: Amazon S3\n
\n\n HTTP Status Code: 403 Forbidden
\n\n SOAP Fault Code Prefix: Client
\n\n Code: OperationAborted
\n\n Description: A conflicting conditional action is currently in progress\n against this resource. Try again.
\n\n HTTP Status Code: 409 Conflict
\n\n SOAP Fault Code Prefix: Client
\n\n Code: PermanentRedirect
\n\n Description: The bucket you are attempting to access must be addressed\n using the specified endpoint. Send all future requests to this endpoint.
\n\n HTTP Status Code: 301 Moved Permanently
\n\n SOAP Fault Code Prefix: Client
\n\n Code: PreconditionFailed
\n\n Description: At least one of the preconditions you specified did not\n hold.
\n\n HTTP Status Code: 412 Precondition Failed
\n\n SOAP Fault Code Prefix: Client
\n\n Code: Redirect
\n\n Description: Temporary redirect.
\n\n HTTP Status Code: 307 Moved Temporarily
\n\n SOAP Fault Code Prefix: Client
\n\n Code: RestoreAlreadyInProgress
\n\n Description: Object restore is already in progress.
\n\n HTTP Status Code: 409 Conflict
\n\n SOAP Fault Code Prefix: Client
\n\n Code: RequestIsNotMultiPartContent
\n\n Description: Bucket POST must be of the enclosure-type\n multipart/form-data.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: RequestTimeout
\n\n Description: Your socket connection to the server was not read from or\n written to within the timeout period.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: RequestTimeTooSkewed
\n\n Description: The difference between the request time and the server's\n time is too large.
\n\n HTTP Status Code: 403 Forbidden
\n\n SOAP Fault Code Prefix: Client
\n\n Code: RequestTorrentOfBucketError
\n\n Description: Requesting the torrent file of a bucket is not\n permitted.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: SignatureDoesNotMatch
\n\n Description: The request signature we calculated does not match the\n signature you provided. Check your Amazon Web Services secret access key and signing method. For more\n information, see REST Authentication and SOAP Authentication for\n details.
\n\n HTTP Status Code: 403 Forbidden
\n\n SOAP Fault Code Prefix: Client
\n\n Code: ServiceUnavailable
\n\n Description: Service is unable to handle request.
\n\n HTTP Status Code: 503 Service Unavailable
\n\n SOAP Fault Code Prefix: Server
\n\n Code: SlowDown
\n\n Description: Reduce your request rate.
\n\n HTTP Status Code: 503 Slow Down
\n\n SOAP Fault Code Prefix: Server
\n\n Code: TemporaryRedirect
\n\n Description: You are being redirected to the bucket while DNS\n updates.
\n\n HTTP Status Code: 307 Moved Temporarily
\n\n SOAP Fault Code Prefix: Client
\n\n Code: TokenRefreshRequired
\n\n Description: The provided token must be refreshed.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: TooManyBuckets
\n\n Description: You have attempted to create more buckets than\n allowed.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: UnexpectedContent
\n\n Description: This request does not support content.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: UnresolvableGrantByEmailAddress
\n\n Description: The email address you provided does not match any account\n on record.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\n\n Code: UserKeyMustBeSpecified
\n\n Description: The bucket POST must contain the specified field name. If\n it is specified, check the order of the fields.
\n\n HTTP Status Code: 400 Bad Request
\n\n SOAP Fault Code Prefix: Client
\nThe error message contains a generic description of the error condition in English. It is intended\n for a human audience. Simple programs display the message directly to the end user if they encounter an\n error condition they don't know how or don't care to handle. Sophisticated programs with more exhaustive\n error handling and proper internationalization are more likely to ignore the error message.
" } } }, "traits": { "smithy.api#documentation": "Container for all error elements.
" } }, "com.amazonaws.s3#ErrorCode": { "type": "string" }, "com.amazonaws.s3#ErrorDetails": { "type": "structure", "members": { "ErrorCode": { "target": "com.amazonaws.s3#ErrorCode", "traits": { "smithy.api#documentation": " If the V1 CreateBucketMetadataTableConfiguration request succeeds, but S3 Metadata was\n unable to create the table, this structure contains the error code. The possible error codes and error\n messages are as follows:
\n AccessDeniedCreatingResources - You don't have sufficient permissions to create the\n required resources. Make sure that you have s3tables:CreateNamespace,\n s3tables:CreateTable, s3tables:GetTable and\n s3tables:PutTablePolicy permissions, and then try again. To create a new metadata\n table, you must delete the metadata configuration for this bucket, and then create a new metadata\n configuration.
\n AccessDeniedWritingToTable - Unable to write to the metadata table because of\n missing resource permissions. To fix the resource policy, Amazon S3 needs to create a new metadata\n table. To create a new metadata table, you must delete the metadata configuration for this bucket,\n and then create a new metadata configuration.
\n DestinationTableNotFound - The destination table doesn't exist. To create a new\n metadata table, you must delete the metadata configuration for this bucket, and then create a new\n metadata configuration.
\n ServerInternalError - An internal error has occurred. To create a new metadata\n table, you must delete the metadata configuration for this bucket, and then create a new metadata\n configuration.
\n TableAlreadyExists - The table that you specified already exists in the table\n bucket's namespace. Specify a different table name. To create a new metadata table, you must delete\n the metadata configuration for this bucket, and then create a new metadata configuration.
\n TableBucketNotFound - The table bucket that you specified doesn't exist in this\n Amazon Web Services Region and account. Create or choose a different table bucket. To create a new metadata table,\n you must delete the metadata configuration for this bucket, and then create a new metadata\n configuration.
If the V2 CreateBucketMetadataConfiguration request succeeds, but S3 Metadata was\n unable to create the table, this structure contains the error code. The possible error codes and error\n messages are as follows:
\n AccessDeniedCreatingResources - You don't have sufficient permissions to create \n the required resources. Make sure that you have s3tables:CreateTableBucket, \n s3tables:CreateNamespace, s3tables:CreateTable, \n s3tables:GetTable, s3tables:PutTablePolicy, \n kms:DescribeKey, and s3tables:PutTableEncryption permissions. \n Additionally, ensure that the KMS key used to encrypt the table still exists, is active and \n has a resource policy granting access to the S3 service principals \n 'maintenance.s3tables.amazonaws.com' and 'metadata.s3.amazonaws.com'. \n To create a new metadata table, you must delete the metadata configuration for this bucket, and \n then create a new metadata configuration.
\n AccessDeniedWritingToTable - Unable to write to the metadata table because of\n missing resource permissions. To fix the resource policy, Amazon S3 needs to create a new metadata\n table. To create a new metadata table, you must delete the metadata configuration for this bucket,\n and then create a new metadata configuration.
\n DestinationTableNotFound - The destination table doesn't exist. To create a new\n metadata table, you must delete the metadata configuration for this bucket, and then create a new\n metadata configuration.
\n ServerInternalError - An internal error has occurred. To create a new metadata\n table, you must delete the metadata configuration for this bucket, and then create a new metadata\n configuration.
\n JournalTableAlreadyExists - A journal table already exists in the Amazon Web Services managed table bucket's \n namespace. Delete the journal table, and then try again. To create a new metadata table, you must delete\n the metadata configuration for this bucket, and then create a new metadata configuration.
\n InventoryTableAlreadyExists - An inventory table already exists in the Amazon Web Services managed table \n bucket's namespace. Delete the inventory table, and then try again. To create a new metadata table, you must delete\n the metadata configuration for this bucket, and then create a new metadata configuration.
\n JournalTableNotAvailable - The journal table that the inventory table relies on \n has a FAILED status. An inventory table requires a journal table with an \n ACTIVE status. To create a new journal or inventory table, you must delete the metadata \n configuration for this bucket, along with any journal or inventory tables, and then create a new \n metadata configuration.
\n NoSuchBucket - The specified general purpose bucket does not exist.
If the V1 CreateBucketMetadataTableConfiguration request succeeds, but S3 Metadata was\n unable to create the table, this structure contains the error message. The possible error codes and\n error messages are as follows:
\n AccessDeniedCreatingResources - You don't have sufficient permissions to create the\n required resources. Make sure that you have s3tables:CreateNamespace,\n s3tables:CreateTable, s3tables:GetTable and\n s3tables:PutTablePolicy permissions, and then try again. To create a new metadata\n table, you must delete the metadata configuration for this bucket, and then create a new metadata\n configuration.
\n AccessDeniedWritingToTable - Unable to write to the metadata table because of\n missing resource permissions. To fix the resource policy, Amazon S3 needs to create a new metadata\n table. To create a new metadata table, you must delete the metadata configuration for this bucket,\n and then create a new metadata configuration.
\n DestinationTableNotFound - The destination table doesn't exist. To create a new\n metadata table, you must delete the metadata configuration for this bucket, and then create a new\n metadata configuration.
\n ServerInternalError - An internal error has occurred. To create a new metadata\n table, you must delete the metadata configuration for this bucket, and then create a new metadata\n configuration.
\n TableAlreadyExists - The table that you specified already exists in the table\n bucket's namespace. Specify a different table name. To create a new metadata table, you must delete\n the metadata configuration for this bucket, and then create a new metadata configuration.
\n TableBucketNotFound - The table bucket that you specified doesn't exist in this\n Amazon Web Services Region and account. Create or choose a different table bucket. To create a new metadata table,\n you must delete the metadata configuration for this bucket, and then create a new metadata\n configuration.
If the V2 CreateBucketMetadataConfiguration request succeeds, but S3 Metadata was\n unable to create the table, this structure contains the error code. The possible error codes and error\n messages are as follows:
\n AccessDeniedCreatingResources - You don't have sufficient permissions to create \n the required resources. Make sure that you have s3tables:CreateTableBucket, \n s3tables:CreateNamespace, s3tables:CreateTable, \n s3tables:GetTable, s3tables:PutTablePolicy, \n kms:DescribeKey, and s3tables:PutTableEncryption permissions. \n Additionally, ensure that the KMS key used to encrypt the table still exists, is active and \n has a resource policy granting access to the S3 service principals \n 'maintenance.s3tables.amazonaws.com' and 'metadata.s3.amazonaws.com'. \n To create a new metadata table, you must delete the metadata configuration for this bucket, and \n then create a new metadata configuration.
\n AccessDeniedWritingToTable - Unable to write to the metadata table because of\n missing resource permissions. To fix the resource policy, Amazon S3 needs to create a new metadata\n table. To create a new metadata table, you must delete the metadata configuration for this bucket,\n and then create a new metadata configuration.
\n DestinationTableNotFound - The destination table doesn't exist. To create a new\n metadata table, you must delete the metadata configuration for this bucket, and then create a new\n metadata configuration.
\n ServerInternalError - An internal error has occurred. To create a new metadata\n table, you must delete the metadata configuration for this bucket, and then create a new metadata\n configuration.
\n JournalTableAlreadyExists - A journal table already exists in the Amazon Web Services managed table bucket's \n namespace. Delete the journal table, and then try again. To create a new metadata table, you must delete\n the metadata configuration for this bucket, and then create a new metadata configuration.
\n InventoryTableAlreadyExists - An inventory table already exists in the Amazon Web Services managed table \n bucket's namespace. Delete the inventory table, and then try again. To create a new metadata table, you must delete\n the metadata configuration for this bucket, and then create a new metadata configuration.
\n JournalTableNotAvailable - The journal table that the inventory table relies on \n has a FAILED status. An inventory table requires a journal table with an \n ACTIVE status. To create a new journal or inventory table, you must delete the metadata \n configuration for this bucket, along with any journal or inventory tables, and then create a new \n metadata configuration.
\n NoSuchBucket - The specified general purpose bucket does not exist.
If an S3 Metadata V1 CreateBucketMetadataTableConfiguration or V2 \n CreateBucketMetadataConfiguration request succeeds, but S3 Metadata was\n unable to create the table, this structure contains the error code and error message.
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete \n and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create \n a live inventory table.
\nThe object key name to use when a 4XX class error occurs.
\nReplacement must be made for object keys containing special characters (such as carriage returns) when using \n XML requests. For more information, see \n XML related object key constraints.
\nThe error information.
" } }, "com.amazonaws.s3#ErrorMessage": { "type": "string" }, "com.amazonaws.s3#Errors": { "type": "list", "member": { "target": "com.amazonaws.s3#Error" } }, "com.amazonaws.s3#Event": { "type": "enum", "members": { "s3_ReducedRedundancyLostObject": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ReducedRedundancyLostObject" } }, "s3_ObjectCreated_": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectCreated:*" } }, "s3_ObjectCreated_Put": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectCreated:Put" } }, "s3_ObjectCreated_Post": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectCreated:Post" } }, "s3_ObjectCreated_Copy": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectCreated:Copy" } }, "s3_ObjectCreated_CompleteMultipartUpload": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectCreated:CompleteMultipartUpload" } }, "s3_ObjectRemoved_": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectRemoved:*" } }, "s3_ObjectRemoved_Delete": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectRemoved:Delete" } }, "s3_ObjectRemoved_DeleteMarkerCreated": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectRemoved:DeleteMarkerCreated" } }, "s3_ObjectRestore_": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectRestore:*" } }, "s3_ObjectRestore_Post": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectRestore:Post" } }, "s3_ObjectRestore_Completed": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectRestore:Completed" } }, "s3_Replication_": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:Replication:*" } }, "s3_Replication_OperationFailedReplication": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:Replication:OperationFailedReplication" } }, "s3_Replication_OperationNotTracked": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:Replication:OperationNotTracked" } }, "s3_Replication_OperationMissedThreshold": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:Replication:OperationMissedThreshold" } }, "s3_Replication_OperationReplicatedAfterThreshold": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:Replication:OperationReplicatedAfterThreshold" } }, "s3_ObjectRestore_Delete": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectRestore:Delete" } }, "s3_LifecycleTransition": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:LifecycleTransition" } }, "s3_IntelligentTiering": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:IntelligentTiering" } }, "s3_ObjectAcl_Put": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectAcl:Put" } }, "s3_LifecycleExpiration_": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:LifecycleExpiration:*" } }, "s3_LifecycleExpiration_Delete": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:LifecycleExpiration:Delete" } }, "s3_LifecycleExpiration_DeleteMarkerCreated": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:LifecycleExpiration:DeleteMarkerCreated" } }, "s3_ObjectTagging_": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectTagging:*" } }, "s3_ObjectTagging_Put": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectTagging:Put" } }, "s3_ObjectTagging_Delete": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "s3:ObjectTagging:Delete" } } }, "traits": { "smithy.api#documentation": "The bucket event for which to send notifications.
" } }, "com.amazonaws.s3#EventBridgeConfiguration": { "type": "structure", "members": {}, "traits": { "smithy.api#documentation": "A container for specifying the configuration for Amazon EventBridge.
" } }, "com.amazonaws.s3#EventList": { "type": "list", "member": { "target": "com.amazonaws.s3#Event" } }, "com.amazonaws.s3#ExistingObjectReplication": { "type": "structure", "members": { "Status": { "target": "com.amazonaws.s3#ExistingObjectReplicationStatus", "traits": { "smithy.api#documentation": "Specifies whether Amazon S3 replicates existing source bucket objects.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Optional configuration to replicate existing source bucket objects.
\nThis parameter is no longer supported. To replicate existing objects, see Replicating\n existing objects with S3 Batch Replication in the\n Amazon S3 User Guide.
\nThe object key name prefix or suffix identifying one or more objects to which the filtering rule\n applies. The maximum length is 1,024 characters. Overlapping prefixes and suffixes are not supported.\n For more information, see Configuring Event Notifications in the Amazon S3 User Guide.
" } }, "Value": { "target": "com.amazonaws.s3#FilterRuleValue", "traits": { "smithy.api#documentation": "The value that the filter searches for in object key names.
" } } }, "traits": { "smithy.api#documentation": "Specifies the Amazon S3 object key name to filter on. An object key name is the name assigned to an\n object in your Amazon S3 bucket. You specify whether to filter on the suffix or prefix of the object key\n name. A prefix is a specific string of characters at the beginning of an object key name, which you can\n use to organize objects. For example, you can start the key names of related objects with a prefix, such\n as 2023- or engineering/. Then, you can use FilterRule to find\n objects in a bucket with key names that have the same prefix. A suffix is similar to a prefix, but it is\n at the end of the object key name instead of at the beginning.
A list of containers for the key-value pair that defines the criteria for the filter rule.
" } }, "com.amazonaws.s3#FilterRuleName": { "type": "enum", "members": { "prefix": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "prefix" } }, "suffix": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "suffix" } } } }, "com.amazonaws.s3#FilterRuleValue": { "type": "string" }, "com.amazonaws.s3#GetBucketAccelerateConfiguration": { "type": "operation", "input": { "target": "com.amazonaws.s3#GetBucketAccelerateConfigurationRequest" }, "output": { "target": "com.amazonaws.s3#GetBucketAccelerateConfigurationOutput" }, "traits": { "smithy.api#documentation": "This operation is not supported for directory buckets.
\nThis implementation of the GET action uses the accelerate subresource to return the\n Transfer Acceleration state of a bucket, which is either Enabled or Suspended.\n Amazon S3 Transfer Acceleration is a bucket-level feature that enables you to perform faster data transfers\n to and from Amazon S3.
To use this operation, you must have permission to perform the\n s3:GetAccelerateConfiguration action. The bucket owner has this permission by default.\n 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\n Resources in the Amazon S3 User Guide.
You set the Transfer Acceleration state of an existing bucket to Enabled or\n Suspended by using the PutBucketAccelerateConfiguration operation.
A GET accelerate request does not return a state value for a bucket that has no\n transfer acceleration state. A bucket has no Transfer Acceleration state if a state has never been set\n on the bucket.
For more information about transfer acceleration, see Transfer Acceleration in the\n Amazon S3 User Guide.
\nThe following operations are related to GetBucketAccelerateConfiguration:
The accelerate configuration of the bucket.
" } }, "RequestCharged": { "target": "com.amazonaws.s3#RequestCharged", "traits": { "smithy.api#httpHeader": "x-amz-request-charged" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "AccelerateConfiguration" } }, "com.amazonaws.s3#GetBucketAccelerateConfigurationRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket for which the accelerate configuration is retrieved.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
End of support notice: Beginning October 1, 2025, Amazon S3 will stop returning DisplayName. Update your applications to use canonical IDs (unique identifier for \n Amazon Web Services accounts), Amazon Web Services account ID (12 digit identifier) or IAM ARNs (full resource naming) as a direct replacement of DisplayName.\n
This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nThis operation is not supported for directory buckets.
\nThis implementation of the GET action uses the acl subresource to return\n the access control list (ACL) of a bucket. To use GET to return the ACL of the bucket, you\n must have the READ_ACP access to the bucket. If READ_ACP permission is granted\n to the anonymous user, you can return the ACL of the bucket without using an authorization\n header.
When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.
\nWhen you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned. \nFor more information about InvalidAccessPointAliasError, see List of\n Error Codes.
If your bucket uses the bucket owner enforced setting for S3 Object Ownership, requests to read\n ACLs are still supported and return the bucket-owner-full-control ACL with the owner\n being the account that created the bucket. For more information, see Controlling object ownership and\n disabling ACLs in the Amazon S3 User Guide.
The following operations are related to GetBucketAcl:
\n ListObjects\n
\nContainer for the bucket owner's display name and ID.
" } }, "Grants": { "target": "com.amazonaws.s3#Grants", "traits": { "smithy.api#documentation": "A list of grants.
", "smithy.api#xmlName": "AccessControlList" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "AccessControlPolicy" } }, "com.amazonaws.s3#GetBucketAclRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "Specifies the S3 bucket whose ACL is being requested.
\nWhen you use this API operation with an access point, provide the alias of the access point in place of the bucket name.
\nWhen you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned. \nFor more information about InvalidAccessPointAliasError, see List of\n Error Codes.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nThis implementation of the GET action returns an analytics configuration (identified by the\n analytics configuration ID) from the bucket.
\nTo use this operation, you must have permissions to perform the\n s3:GetAnalyticsConfiguration action. The bucket owner has this permission by default. The\n 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\n Resources in the Amazon S3 User Guide.
For information about Amazon S3 analytics feature, see Amazon S3 Analytics \u2013 Storage Class Analysis\n in the Amazon S3 User Guide.
\nThe following operations are related to GetBucketAnalyticsConfiguration:
The configuration and any analyses for the analytics filter.
", "smithy.api#httpPayload": {} } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#GetBucketAnalyticsConfigurationRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket from which an analytics configuration is retrieved.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Id": { "target": "com.amazonaws.s3#AnalyticsId", "traits": { "smithy.api#documentation": "The ID that identifies the analytics configuration.
", "smithy.api#httpQuery": "id", "smithy.api#required": {} } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nReturns the Cross-Origin Resource Sharing (CORS) configuration information set for the\n bucket.
\n To use this operation, you must have permission to perform the s3:GetBucketCORS\n action. By default, the bucket owner has this permission and can grant it to others.
When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.
\nWhen you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned. \nFor more information about InvalidAccessPointAliasError, see List of\n Error Codes.
For more information about CORS, see Enabling Cross-Origin Resource Sharing.
\nThe following operations are related to GetBucketCors:
\n PutBucketCors\n
\n\n DeleteBucketCors\n
\nA set of origins and methods (cross-origin access that you want to allow). You can add up to 100\n rules to the configuration.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "CORSRule" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "CORSConfiguration" } }, "com.amazonaws.s3#GetBucketCorsRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name for which to get the cors configuration.
\nWhen you use this API operation with an access point, provide the alias of the access point in place of the bucket name.
\nWhen you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned. \nFor more information about InvalidAccessPointAliasError, see List of\n Error Codes.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Returns the default encryption configuration for an Amazon S3 bucket. By default, all buckets have a\n default encryption configuration that uses server-side encryption with Amazon S3 managed keys (SSE-S3).
\n\n General purpose buckets - For information about the bucket\n default encryption feature, see Amazon S3 Bucket Default Encryption in the\n Amazon S3 User Guide.
\n\n Directory buckets -\n For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. For information about the default encryption configuration in\n directory buckets, see Setting default server-side\n encryption behavior for directory buckets.
\n\n General purpose bucket permissions - The\n s3:GetEncryptionConfiguration permission is required in a policy. The bucket\n owner has this permission by default. The bucket owner can grant this permission to others.\n For more information about permissions, see Permissions Related to Bucket Operations and Managing Access Permissions to Your\n Amazon S3 Resources.
\n Directory bucket permissions - To grant access to\n this API operation, you must have the s3express:GetEncryptionConfiguration\n permission in an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.\n For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
\n Directory buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following operations are related to GetBucketEncryption:
\n PutBucketEncryption\n
\nThe name of the bucket from which the server-side encryption configuration is retrieved.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n DOC-EXAMPLE-BUCKET--usw2-az1--x-s3). For information about bucket naming restrictions, see Directory bucket naming rules in the Amazon S3 User Guide\n
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
For directory buckets, this header is not supported in this API operation. If you specify this header, the request fails with the HTTP status code \n501 Not Implemented.
This operation is not supported for directory buckets.
\nGets the S3 Intelligent-Tiering configuration from the specified bucket.
\nThe S3 Intelligent-Tiering storage class is designed to optimize storage costs by automatically moving data to the most cost-effective storage access tier, without performance impact or operational overhead. S3 Intelligent-Tiering delivers automatic cost savings in three low latency and high throughput access tiers. To get the lowest storage cost on data that can be accessed in minutes to hours, you can choose to activate additional archiving capabilities.
\nThe S3 Intelligent-Tiering storage class is the ideal storage class for data with unknown, changing, or unpredictable access patterns, independent of object size or retention period. If the size of an object is less than 128 KB, it is not monitored and not eligible for auto-tiering. Smaller objects can be stored, but they are always charged at the Frequent Access tier rates in the S3 Intelligent-Tiering storage class.
\nFor more information, see Storage class for automatically optimizing frequently and infrequently accessed objects.
\nOperations related to GetBucketIntelligentTieringConfiguration include:
Container for S3 Intelligent-Tiering configuration.
", "smithy.api#httpPayload": {} } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#GetBucketIntelligentTieringConfigurationRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the Amazon S3 bucket whose configuration you want to modify or retrieve.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Id": { "target": "com.amazonaws.s3#IntelligentTieringId", "traits": { "smithy.api#documentation": "The ID used to identify the S3 Intelligent-Tiering configuration.
", "smithy.api#httpQuery": "id", "smithy.api#required": {} } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nReturns an S3 Inventory configuration (identified by the inventory configuration ID) from the\n bucket.
\nTo use this operation, you must have permissions to perform the\n s3:GetInventoryConfiguration action. The bucket owner has this permission by default and\n 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\n Resources.
For information about the Amazon S3 inventory feature, see Amazon S3 Inventory.
\nThe following operations are related to GetBucketInventoryConfiguration:
Specifies the inventory configuration.
", "smithy.api#httpPayload": {} } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#GetBucketInventoryConfigurationRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket containing the inventory configuration to retrieve.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Id": { "target": "com.amazonaws.s3#InventoryId", "traits": { "smithy.api#documentation": "The ID used to identify the inventory configuration.
", "smithy.api#httpQuery": "id", "smithy.api#required": {} } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Returns the lifecycle configuration information set on the bucket. For information about lifecycle\n configuration, see Object Lifecycle Management.
\nBucket lifecycle configuration now supports specifying a lifecycle rule using an object key name\n prefix, one or more object tags, object size, or any combination of these. Accordingly, this section\n describes the latest API, which is compatible with the new functionality. The previous version of the\n API supported filtering based only on an object key name prefix, which is supported for general purpose\n buckets for backward compatibility. For the related API description, see GetBucketLifecycle.
\nLifecyle configurations for directory buckets only support expiring objects and cancelling\n multipart uploads. Expiring of versioned objects, transitions and tag filters are not\n supported.
\n\n General purpose bucket permissions - By default, all Amazon S3\n resources are private, including buckets, objects, and related subresources (for example,\n lifecycle configuration and website configuration). Only the resource owner (that is, the\n Amazon Web Services account that created it) can access the resource. The resource owner can optionally\n grant access permissions to others by writing an access policy. For this operation, a user\n must have the s3:GetLifecycleConfiguration permission.
For more information about permissions, see Managing Access Permissions to Your\n Amazon S3 Resources.
\n\n Directory bucket permissions - You must have the\n s3express:GetLifecycleConfiguration permission in an IAM identity-based policy\n to use this operation. Cross-account access to this API operation isn't supported. The\n resource owner can optionally grant access permissions to others by creating a role or user\n for them as long as they are within the same account as the owner and resource.
For more information about directory bucket policies and permissions, see Authorizing Regional endpoint APIs with IAM in the Amazon S3 User\n Guide.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. \nFor more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n Directory buckets - The HTTP Host header syntax is\n s3express-control.region.amazonaws.com.
\n GetBucketLifecycleConfiguration has the following special error:
Error code: NoSuchLifecycleConfiguration\n
Description: The lifecycle configuration does not exist.
\nHTTP Status Code: 404 Not Found
\nSOAP Fault Code Prefix: Client
\nThe following operations are related to GetBucketLifecycleConfiguration:
\n GetBucketLifecycle\n
\n\n PutBucketLifecycle\n
\nContainer for a lifecycle rule.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Rule" } }, "TransitionDefaultMinimumObjectSize": { "target": "com.amazonaws.s3#TransitionDefaultMinimumObjectSize", "traits": { "smithy.api#documentation": "Indicates which default minimum object size behavior is applied to the lifecycle\n configuration.
\nThis parameter applies to general purpose buckets only. It isn't supported for directory bucket\n lifecycle configurations.
\n\n all_storage_classes_128K - Objects smaller than 128 KB will not transition to\n any storage class by default.
\n varies_by_storage_class - Objects smaller than 128 KB will transition to Glacier\n Flexible Retrieval or Glacier Deep Archive storage classes. By default, all other storage classes\n will prevent transitions smaller than 128 KB.
To customize the minimum object size for any transition you can add a filter that specifies a custom\n ObjectSizeGreaterThan or ObjectSizeLessThan in the body of your transition\n rule. Custom filters always take precedence over the default transition behavior.
The name of the bucket for which to get the lifecycle information.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This parameter applies to general purpose buckets only. It is not supported for directory bucket\n lifecycle configurations.
\nThis operation is not supported for directory buckets.
\nReturns the Region the bucket resides in. You set the bucket's Region using the\n LocationConstraint request parameter in a CreateBucket request. For more\n information, see CreateBucket.
When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.
\nWhen you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned. \nFor more information about InvalidAccessPointAliasError, see List of\n Error Codes.
We recommend that you use HeadBucket to return the Region that a bucket\n resides in. For backward compatibility, Amazon S3 continues to support GetBucketLocation.
\nThe following operations are related to GetBucketLocation:
\n GetObject\n
\n\n CreateBucket\n
\nSpecifies the Region where the bucket resides. For a list of all the Amazon S3 supported location\n constraints by Region, see Regions and Endpoints.
\nBuckets in Region us-east-1 have a LocationConstraint of null. Buckets\n with a LocationConstraint of EU reside in eu-west-1.
The name of the bucket for which to get the location.
\nWhen you use this API operation with an access point, provide the alias of the access point in place of the bucket name.
\nWhen you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned. \nFor more information about InvalidAccessPointAliasError, see List of\n Error Codes.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
End of support notice: Beginning October 1, 2025, Amazon S3 will stop returning DisplayName. Update your applications to use canonical IDs (unique identifier for \n Amazon Web Services accounts), Amazon Web Services account ID (12 digit identifier) or IAM ARNs (full resource naming) as a direct replacement of DisplayName.\n
This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nThis operation is not supported for directory buckets.
\nReturns the logging status of a bucket and the permissions users have to view and modify that\n status.
\nThe following operations are related to GetBucketLogging:
\n CreateBucket\n
\n\n PutBucketLogging\n
\nThe bucket name for which to get the logging information.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Retrieves the S3 Metadata configuration for a general purpose bucket. For more information, see\n Accelerating\n data discovery with S3 Metadata in the Amazon S3 User Guide.
\nYou can use the V2 GetBucketMetadataConfiguration API operation with V1 or V2 \n metadata configurations. However, if you try to use the V1 \n GetBucketMetadataTableConfiguration API operation with V2 configurations, you\n will receive an HTTP 405 Method Not Allowed error.
To use this operation, you must have the s3:GetBucketMetadataTableConfiguration\n permission. For more information, see Setting up permissions for\n configuring metadata tables in the Amazon S3 User Guide.
The IAM policy action name is the same for the V1 and V2 API operations.
\nThe following operations are related to GetBucketMetadataConfiguration:
\n The metadata configuration for the general purpose bucket.\n
", "smithy.api#httpPayload": {} } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#GetBucketMetadataConfigurationRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "\n The general purpose bucket that corresponds to the metadata configuration that you want to\n retrieve.\n
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "\n The expected owner of the general purpose bucket that you want to retrieve the metadata table\n configuration for.\n
", "smithy.api#httpHeader": "x-amz-expected-bucket-owner" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#GetBucketMetadataConfigurationResult": { "type": "structure", "members": { "MetadataConfigurationResult": { "target": "com.amazonaws.s3#MetadataConfigurationResult", "traits": { "smithy.api#documentation": "\n The metadata configuration for a general purpose bucket.\n
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "\n The S3 Metadata configuration for a general purpose bucket.\n
" } }, "com.amazonaws.s3#GetBucketMetadataTableConfiguration": { "type": "operation", "input": { "target": "com.amazonaws.s3#GetBucketMetadataTableConfigurationRequest" }, "output": { "target": "com.amazonaws.s3#GetBucketMetadataTableConfigurationOutput" }, "traits": { "smithy.api#documentation": "\n We recommend that you retrieve your S3 Metadata configurations by using the V2 \n GetBucketMetadataTableConfiguration API operation. We no longer recommend using the V1 \n GetBucketMetadataTableConfiguration API operation.\n
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete \n and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create \n a live inventory table.
\nRetrieves the V1 S3 Metadata configuration for a general purpose bucket. For more information, see\n Accelerating\n data discovery with S3 Metadata in the Amazon S3 User Guide.
\nYou can use the V2 GetBucketMetadataConfiguration API operation with V1 or V2 \n metadata table configurations. However, if you try to use the V1 \n GetBucketMetadataTableConfiguration API operation with V2 configurations, you\n will receive an HTTP 405 Method Not Allowed error.
Make sure that you update your processes to use the new V2 API operations\n (CreateBucketMetadataConfiguration, GetBucketMetadataConfiguration, and\n DeleteBucketMetadataConfiguration) instead of the V1 API operations.
To use this operation, you must have the s3:GetBucketMetadataTableConfiguration\n permission. For more information, see Setting up permissions for\n configuring metadata tables in the Amazon S3 User Guide.
The following operations are related to GetBucketMetadataTableConfiguration:
The metadata table configuration for the general purpose bucket.
", "smithy.api#httpPayload": {} } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#GetBucketMetadataTableConfigurationRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The general purpose bucket that corresponds to the metadata table configuration that you want to\n retrieve.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The expected owner of the general purpose bucket that you want to retrieve the metadata table\n configuration for.
", "smithy.api#httpHeader": "x-amz-expected-bucket-owner" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#GetBucketMetadataTableConfigurationResult": { "type": "structure", "members": { "MetadataTableConfigurationResult": { "target": "com.amazonaws.s3#MetadataTableConfigurationResult", "traits": { "smithy.api#documentation": "The V1 S3 Metadata configuration for a general purpose bucket.
", "smithy.api#required": {} } }, "Status": { "target": "com.amazonaws.s3#MetadataTableStatus", "traits": { "smithy.api#documentation": "The status of the metadata table. The status values are:
\n\n CREATING - The metadata table is in the process of being created in the specified\n table bucket.
\n ACTIVE - The metadata table has been created successfully, and records are being\n delivered to the table.
\n FAILED - Amazon S3 is unable to create the metadata table, or Amazon S3 is unable to deliver\n records. See ErrorDetails for details.
If the CreateBucketMetadataTableConfiguration request succeeds, but S3 Metadata was\n unable to create the table, this structure contains the error code and error message.
The V1 S3 Metadata configuration for a general purpose bucket.
\nIf you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete \n and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create \n a live inventory table.
\nThis operation is not supported for directory buckets.
\nGets a metrics configuration (specified by the metrics configuration ID) from the bucket. Note that\n this doesn't include the daily storage metrics.
\n To use this operation, you must have permissions to perform the\n s3:GetMetricsConfiguration action. The bucket owner has this permission by default. The\n 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\n Resources.
For information about CloudWatch request metrics for Amazon S3, see Monitoring Metrics with Amazon\n CloudWatch.
\nThe following operations are related to GetBucketMetricsConfiguration:
Specifies the metrics configuration.
", "smithy.api#httpPayload": {} } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#GetBucketMetricsConfigurationRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket containing the metrics configuration to retrieve.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Id": { "target": "com.amazonaws.s3#MetricsId", "traits": { "smithy.api#documentation": "The ID used to identify the metrics configuration. The ID has a 64 character limit and can only\n contain letters, numbers, periods, dashes, and underscores.
", "smithy.api#httpQuery": "id", "smithy.api#required": {} } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nReturns the notification configuration of a bucket.
\nIf notifications are not enabled on the bucket, the action returns an empty\n NotificationConfiguration element.
By default, you must be the bucket owner to read the notification configuration of a bucket.\n However, the bucket owner can use a bucket policy to grant permission to other users to read this\n configuration with the s3:GetBucketNotification permission.
When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.
\nWhen you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned. \nFor more information about InvalidAccessPointAliasError, see List of\n Error Codes.
For more information about setting and reading the notification configuration on a bucket, see\n Setting Up Notification\n of Bucket Events. For more information about bucket policies, see Using Bucket Policies.
\nThe following action is related to GetBucketNotification:
The name of the bucket for which to get the notification configuration.
\nWhen you use this API operation with an access point, provide the alias of the access point in place of the bucket name.
\nWhen you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned. \nFor more information about InvalidAccessPointAliasError, see List of\n Error Codes.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nRetrieves OwnershipControls for an Amazon S3 bucket. To use this operation, you must have\n the s3:GetBucketOwnershipControls permission. For more information about Amazon S3 permissions,\n see Specifying\n permissions in a policy.
A bucket doesn't have OwnershipControls settings in the following cases:
The bucket was created before the BucketOwnerEnforced ownership setting was\n introduced and you've never explicitly applied this value
You've manually deleted the bucket ownership control value using the\n DeleteBucketOwnershipControls API operation.
By default, Amazon S3 sets OwnershipControls for all newly created buckets.
For information about Amazon S3 Object Ownership, see Using Object Ownership.
\nThe following operations are related to GetBucketOwnershipControls:
The OwnershipControls (BucketOwnerEnforced, BucketOwnerPreferred, or ObjectWriter)\n currently in effect for this Amazon S3 bucket.
The name of the Amazon S3 bucket whose OwnershipControls you want to retrieve.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Returns the policy of a specified bucket.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. \nFor more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
If you are using an identity other than the root user of the Amazon Web Services account that owns the\n bucket, the calling identity must both have the GetBucketPolicy permissions on the\n specified bucket and belong to the bucket owner's account in order to use this operation.
If you don't have GetBucketPolicy permissions, Amazon S3 returns a 403 Access\n Denied error. If you have the correct permissions, but you're not using an identity that\n belongs to the bucket owner's account, Amazon S3 returns a 405 Method Not Allowed\n error.
To ensure that bucket owners don't inadvertently lock themselves out of their own buckets,\n the root principal in a bucket owner's Amazon Web Services account can perform the\n GetBucketPolicy, PutBucketPolicy, and\n DeleteBucketPolicy API actions, even if their bucket policy explicitly denies the\n root principal's access. Bucket owner root principals can only be blocked from performing these\n API actions by VPC endpoint policies and Amazon Web Services Organizations policies.
\n General purpose bucket permissions - The\n s3:GetBucketPolicy permission is required in a policy. For more information\n about general purpose buckets bucket policies, see Using Bucket Policies and User\n Policies in the Amazon S3 User Guide.
\n Directory bucket permissions - To grant access to\n this API operation, you must have the s3express:GetBucketPolicy permission in\n an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.\n For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
\n General purpose buckets example bucket policies - See Bucket policy\n examples in the Amazon S3 User Guide.
\n\n Directory bucket example bucket policies - See Example\n bucket policies for S3 Express One Zone in the Amazon S3 User Guide.
\n\n Directory buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following action is related to GetBucketPolicy:
\n GetObject\n
\nThe bucket policy as a JSON document.
", "smithy.api#httpPayload": {} } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#GetBucketPolicyRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name to get the bucket policy for.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n DOC-EXAMPLE-BUCKET--usw2-az1--x-s3). For information about bucket naming restrictions, see Directory bucket naming rules in the Amazon S3 User Guide\n
\n Access points - When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.
\n\n Object Lambda access points - When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned. \nFor more information about InvalidAccessPointAliasError, see List of\n Error Codes.
Object Lambda access points are not supported by directory buckets.
\nThe account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
For directory buckets, this header is not supported in this API operation. If you specify this header, the request fails with the HTTP status code \n501 Not Implemented.
This operation is not supported for directory buckets.
\nRetrieves the policy status for an Amazon S3 bucket, indicating whether the bucket is public. In order to\n use this operation, you must have the s3:GetBucketPolicyStatus permission. For more\n information about Amazon S3 permissions, see Specifying Permissions in a\n Policy.
For more information about when Amazon S3 considers a bucket public, see The Meaning of \"Public\".
\nThe following operations are related to GetBucketPolicyStatus:
\n GetPublicAccessBlock\n
\n\n PutPublicAccessBlock\n
\nThe policy status for the specified bucket.
", "smithy.api#httpPayload": {} } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#GetBucketPolicyStatusRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the Amazon S3 bucket whose policy status you want to retrieve.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nReturns the replication configuration of a bucket.
\nIt can take a while to propagate the put or delete a replication configuration to all Amazon S3\n systems. Therefore, a get request soon after put or delete can return a wrong result.
\nFor information about replication configuration, see Replication in the\n Amazon S3 User Guide.
\nThis action requires permissions for the s3:GetReplicationConfiguration action. For\n more information about permissions, see Using Bucket Policies and User\n Policies.
If you include the Filter element in a replication configuration, you must also include\n the DeleteMarkerReplication and Priority elements. The response also returns\n those elements.
For information about GetBucketReplication errors, see List of replication-related\n error codes\n
The following operations are related to GetBucketReplication:
\n PutBucketReplication\n
\nThe bucket name for which to get the replication information.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nReturns the request payment configuration of a bucket. To use this version of the operation, you\n must be the bucket owner. For more information, see Requester Pays Buckets.
\nThe following operations are related to GetBucketRequestPayment:
\n ListObjects\n
\nSpecifies who pays for the download and request fees.
" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "RequestPaymentConfiguration" } }, "com.amazonaws.s3#GetBucketRequestPaymentRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket for which to get the payment request configuration
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nReturns the tag set associated with the bucket.
\nTo use this operation, you must have permission to perform the s3:GetBucketTagging\n action. By default, the bucket owner has this permission and can grant this permission to others.
\n GetBucketTagging has the following special error:
Error code: NoSuchTagSet\n
Description: There is no tag set associated with the bucket.
\nThe following operations are related to GetBucketTagging:
\n PutBucketTagging\n
\n\n DeleteBucketTagging\n
\nContains the tag set.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "Tagging" } }, "com.amazonaws.s3#GetBucketTaggingRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket for which to get the tagging information.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nReturns the versioning state of a bucket.
\nTo retrieve the versioning state of a bucket, you must be the bucket owner.
\nThis implementation also returns the MFA Delete status of the versioning state. If the MFA Delete\n status is enabled, the bucket owner must use an authentication device to change the\n versioning state of the bucket.
The following operations are related to GetBucketVersioning:
\n GetObject\n
\n\n PutObject\n
\n\n DeleteObject\n
\nThe versioning state of the bucket.
" } }, "MFADelete": { "target": "com.amazonaws.s3#MFADeleteStatus", "traits": { "smithy.api#documentation": "Specifies whether MFA delete is enabled in the bucket versioning configuration. This element is only\n returned if the bucket has been configured with MFA delete. If the bucket has never been so configured,\n this element is not returned.
", "smithy.api#xmlName": "MfaDelete" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "VersioningConfiguration" } }, "com.amazonaws.s3#GetBucketVersioningRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket for which to get the versioning information.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nReturns the website configuration for a bucket. To host website on Amazon S3, you can configure a bucket\n as website by adding a website configuration. For more information about hosting websites, see Hosting Websites on Amazon S3.
\nThis GET action requires the S3:GetBucketWebsite permission. By default, only the\n bucket owner can read the bucket website configuration. However, bucket owners can allow other users to\n read the website configuration by writing a bucket policy granting them the\n S3:GetBucketWebsite permission.
The following operations are related to GetBucketWebsite:
\n DeleteBucketWebsite\n
\n\n PutBucketWebsite\n
\nSpecifies the redirect behavior of all requests to a website endpoint of an Amazon S3 bucket.
" } }, "IndexDocument": { "target": "com.amazonaws.s3#IndexDocument", "traits": { "smithy.api#documentation": "The name of the index document for the website (for example index.html).
The object key name of the website error document to use for 4XX class errors.
" } }, "RoutingRules": { "target": "com.amazonaws.s3#RoutingRules", "traits": { "smithy.api#documentation": "Rules that define when a redirect is applied and the redirect behavior.
" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "WebsiteConfiguration" } }, "com.amazonaws.s3#GetBucketWebsiteRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name for which to get the website configuration.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Retrieves an object from Amazon S3.
\nIn the GetObject request, specify the full key name for the object.
\n General purpose buckets - Both the virtual-hosted-style requests\n and the path-style requests are supported. For a virtual hosted-style request example, if you have the\n object photos/2006/February/sample.jpg, specify the object key name as\n /photos/2006/February/sample.jpg. For a path-style request example, if you have the\n object photos/2006/February/sample.jpg in the bucket named examplebucket,\n specify the object key name as /examplebucket/photos/2006/February/sample.jpg. For more\n information about request types, see HTTP Host Header Bucket\n Specification in the Amazon S3 User Guide.
\n Directory buckets -\n Only virtual-hosted-style requests are supported. For a virtual hosted-style request example, if you have the object photos/2006/February/sample.jpg in the bucket named amzn-s3-demo-bucket--usw2-az1--x-s3, specify the object key name as /photos/2006/February/sample.jpg. Also, when you make requests to this API operation, your requests are sent to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://bucket-name.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n General purpose bucket permissions - You must have the\n required permissions in a policy. To use GetObject, you must have the\n READ access to the object (or version). If you grant READ access\n to the anonymous user, the GetObject operation returns the object without using\n an authorization header. For more information, see Specifying permissions in a\n policy in the Amazon S3 User Guide.
If you include a versionId in your request header, you must have the\n s3:GetObjectVersion permission to access a specific version of an object. The\n s3:GetObject permission is not required in this scenario.
If you request the current version of an object without a specific versionId\n in the request header, only the s3:GetObject permission is required. The\n s3:GetObjectVersion permission is not required in this scenario.
If the object that you request doesn\u2019t exist, the error that Amazon S3 returns depends on\n whether you also have the s3:ListBucket permission.
If you have the s3:ListBucket permission on the bucket, Amazon S3 returns an\n HTTP status code 404 Not Found error.
If you don\u2019t have the s3:ListBucket permission, Amazon S3 returns an HTTP\n status code 403 Access Denied error.
\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
If the object is\n encrypted using SSE-KMS, you must also have the kms:GenerateDataKey and\n kms:Decrypt permissions in IAM identity-based policies and KMS key policies\n for the KMS key.
If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage class,\n the S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access tier, or the\n S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you must first restore a\n copy using RestoreObject. Otherwise, this operation returns an InvalidObjectState\n error. For information about restoring archived objects, see Restoring Archived Objects in the\n Amazon S3 User Guide.
\n Directory buckets -\n Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones. \nUnsupported storage class values won't write a destination object and will respond with the HTTP status code 400 Bad Request.
Encryption request headers, like x-amz-server-side-encryption, should not be sent\n for the GetObject requests, if your object uses server-side encryption with Amazon S3\n managed encryption keys (SSE-S3), server-side encryption with Key Management Service (KMS) keys (SSE-KMS), or\n dual-layer server-side encryption with Amazon Web Services KMS keys (DSSE-KMS). If you include the header in\n your GetObject requests for the object that uses these types of keys, you\u2019ll get an\n HTTP 400 Bad Request error.
\n Directory buckets -\n For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more\n information, see Protecting data with server-side encryption in the Amazon S3 User Guide.
\nThere are times when you want to override certain response header values of a\n GetObject response. For example, you might override the\n Content-Disposition response header value through your GetObject\n request.
You can override values for a set of response headers. These modified response header values\n are included only in a successful response, that is, when the HTTP status code 200 OK\n is returned. The headers you can override using the following query parameters in the request are\n a subset of the headers that Amazon S3 accepts when you create an object.
The response headers that you can override for the GetObject response are\n Cache-Control, Content-Disposition, Content-Encoding,\n Content-Language, Content-Type, and Expires.
To override values for a set of response headers in the GetObject response, you\n can use the following query parameters in the request.
\n response-cache-control\n
\n response-content-disposition\n
\n response-content-encoding\n
\n response-content-language\n
\n response-content-type\n
\n response-expires\n
When you use these parameters, you must sign the request by using either an Authorization\n header or a presigned URL. These parameters cannot be used with an unsigned (anonymous)\n request.
\n\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following operations are related to GetObject:
\n ListBuckets\n
\n\n GetObjectAcl\n
\nThis operation is not supported for directory buckets.
\nReturns the access control list (ACL) of an object. To use this operation, you must have\n s3:GetObjectAcl permissions or READ_ACP access to the object. For more\n information, see Mapping of ACL\n permissions and access policy permissions in the Amazon S3 User Guide\n
This functionality is not supported for Amazon S3 on Outposts.
\nBy default, GET returns ACL information about the current version of an object. To return ACL\n information about a different version, use the versionId subresource.
\nIf your bucket uses the bucket owner enforced setting for S3 Object Ownership, requests to read\n ACLs are still supported and return the bucket-owner-full-control ACL with the owner\n being the account that created the bucket. For more information, see Controlling object ownership and\n disabling ACLs in the Amazon S3 User Guide.
The following operations are related to GetObjectAcl:
\n GetObject\n
\n\n GetObjectAttributes\n
\n\n DeleteObject\n
\n\n PutObject\n
\nContainer for the bucket owner's display name and ID.
" } }, "Grants": { "target": "com.amazonaws.s3#Grants", "traits": { "smithy.api#documentation": "A list of grants.
", "smithy.api#xmlName": "AccessControlList" } }, "RequestCharged": { "target": "com.amazonaws.s3#RequestCharged", "traits": { "smithy.api#httpHeader": "x-amz-request-charged" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "AccessControlPolicy" } }, "com.amazonaws.s3#GetObjectAclRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name that contains the object for which to get the ACL information.
\n\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "The key of the object for which to get the ACL information.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Key" } } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "Version ID used to reference a specific version of the object.
\nThis functionality is not supported for directory buckets.
\nThe account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Retrieves all of the metadata from an object without returning the object itself. This operation is\n useful if you're interested only in an object's metadata.
\n\n GetObjectAttributes combines the functionality of HeadObject and\n ListParts. All of the data returned with both of those individual calls can be returned\n with a single call to GetObjectAttributes.
\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n General purpose bucket permissions - To use\n GetObjectAttributes, you must have READ access to the object.
The other permissions that you need to use this operation depend on whether the bucket is\n versioned and if a version ID is passed in the GetObjectAttributes request.
If you pass a version ID in your request, you need both the\n s3:GetObjectVersion and s3:GetObjectVersionAttributes\n permissions.
If you do not pass a version ID in your request, you need the\n s3:GetObject and s3:GetObjectAttributes permissions.
For more information, see Specifying Permissions in a\n Policy in the Amazon S3 User Guide.
\nIf the object that you request does not exist, the error Amazon S3 returns depends on whether\n you also have the s3:ListBucket permission.
If you have the s3:ListBucket permission on the bucket, Amazon S3 returns an\n HTTP status code 404 Not Found (\"no such key\") error.
If you don't have the s3:ListBucket permission, Amazon S3 returns an HTTP\n status code 403 Forbidden (\"access denied\") error.
\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
If\n the\n object is encrypted with SSE-KMS, you must also have the kms:GenerateDataKey and\n kms:Decrypt permissions in IAM identity-based policies and KMS key policies\n for the KMS key.
Encryption request headers, like x-amz-server-side-encryption, should not be\n sent for HEAD requests if your object uses server-side encryption with Key Management Service\n (KMS) keys (SSE-KMS), dual-layer server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), or\n server-side encryption with Amazon S3 managed encryption keys (SSE-S3). The\n x-amz-server-side-encryption header is used when you PUT an object\n to S3 and want to specify the encryption method. If you include this header in a\n GET request for an object that uses these types of keys, you\u2019ll get an HTTP\n 400 Bad Request error. It's because the encryption method can't be changed when\n you retrieve the object.
If you encrypted an object when you stored the object in Amazon S3 by using server-side encryption\n with customer-provided encryption keys (SSE-C), then when you retrieve the metadata from the\n object, you must use the following headers. These headers provide the server with the encryption\n key required to retrieve the object's metadata. The headers are:
\n\n x-amz-server-side-encryption-customer-algorithm\n
\n x-amz-server-side-encryption-customer-key\n
\n x-amz-server-side-encryption-customer-key-MD5\n
For more information about SSE-C, see Server-Side Encryption (Using\n Customer-Provided Encryption Keys) in the Amazon S3 User Guide.
\n\n Directory bucket permissions -\n For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n CreateSession requests or PUT object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n information, see Protecting data with server-side encryption in the Amazon S3 User Guide. For more information about the encryption overriding behaviors in directory buckets, see Specifying server-side encryption with KMS for new object uploads.
\n Directory buckets - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets.\n You can only specify null to the versionId query parameter in the\n request.
Consider the following when using request headers:
\nIf both of the If-Match and If-Unmodified-Since headers are\n present in the request as follows, then Amazon S3 returns the HTTP status code 200 OK\n and the data requested:
\n If-Match condition evaluates to true.
\n If-Unmodified-Since condition evaluates to false.
For more information about conditional requests, see RFC 7232.
\nIf both of the If-None-Match and If-Modified-Since headers are\n present in the request as follows, then Amazon S3 returns the HTTP status code 304 Not\n Modified:
\n If-None-Match condition evaluates to false.
\n If-Modified-Since condition evaluates to true.
For more information about conditional requests, see RFC 7232.
\n\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following actions are related to GetObjectAttributes:
\n GetObject\n
\n\n GetObjectAcl\n
\n\n GetObjectLegalHold\n
\n\n GetObjectRetention\n
\n\n GetObjectTagging\n
\n\n HeadObject\n
\n\n ListParts\n
\nSpecifies whether the object retrieved was (true) or was not (false) a\n delete marker. If false, this response header does not appear in the response. To learn\n more about delete markers, see Working with delete markers.
This functionality is not supported for directory buckets.
\nDate and time when the object was last modified.
", "smithy.api#httpHeader": "Last-Modified" } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "The version ID of the object.
\nThis functionality is not supported for directory buckets.
\nAn ETag is an opaque identifier assigned by a web server to a specific version of a resource found\n at a URL.
" } }, "Checksum": { "target": "com.amazonaws.s3#Checksum", "traits": { "smithy.api#documentation": "The checksum or digest of the object.
" } }, "ObjectParts": { "target": "com.amazonaws.s3#GetObjectAttributesParts", "traits": { "smithy.api#documentation": "A collection of parts associated with a multipart upload.
" } }, "StorageClass": { "target": "com.amazonaws.s3#StorageClass", "traits": { "smithy.api#documentation": "Provides the storage class information of the object. Amazon S3 returns this header for all objects\n except for S3 Standard storage class objects.
\nFor more information, see Storage Classes.
\n\n Directory buckets -\n Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
The size of the object in bytes.
" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "GetObjectAttributesResponse" } }, "com.amazonaws.s3#GetObjectAttributesParts": { "type": "structure", "members": { "TotalPartsCount": { "target": "com.amazonaws.s3#PartsCount", "traits": { "smithy.api#documentation": "The total number of parts.
", "smithy.api#xmlName": "PartsCount" } }, "PartNumberMarker": { "target": "com.amazonaws.s3#PartNumberMarker", "traits": { "smithy.api#documentation": "The marker for the current part.
" } }, "NextPartNumberMarker": { "target": "com.amazonaws.s3#NextPartNumberMarker", "traits": { "smithy.api#documentation": "When a list is truncated, this element specifies the last part in the list, as well as the value to\n use for the PartNumberMarker request parameter in a subsequent request.
The maximum number of parts allowed in the response.
" } }, "IsTruncated": { "target": "com.amazonaws.s3#IsTruncated", "traits": { "smithy.api#documentation": "Indicates whether the returned list of parts is truncated. A value of true indicates\n that the list was truncated. A list can be truncated if the number of parts exceeds the limit returned\n in the MaxParts element.
A container for elements related to a particular part. A response can contain zero or more\n Parts elements.
\n General purpose buckets - For\n GetObjectAttributes, if an additional checksum (including\n x-amz-checksum-crc32, x-amz-checksum-crc32c,\n x-amz-checksum-sha1, or x-amz-checksum-sha256) isn't applied to the\n object specified in the request, the response doesn't return the Part element.
\n Directory buckets - For\n GetObjectAttributes, regardless of whether an additional checksum is applied to the\n object specified in the request, the response returns the Part element.
A collection of parts associated with a multipart upload.
" } }, "com.amazonaws.s3#GetObjectAttributesRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket that contains the object.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
The object key.
", "smithy.api#httpLabel": {}, "smithy.api#required": {} } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "The version ID used to reference a specific version of the object.
\nS3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets. You can only specify null to the\n versionId query parameter in the request.
Sets the maximum number of parts to return. For more information, see Uploading and copying objects using multipart upload\n in Amazon S3 in the Amazon Simple Storage Service user guide.
", "smithy.api#httpHeader": "x-amz-max-parts" } }, "PartNumberMarker": { "target": "com.amazonaws.s3#PartNumberMarker", "traits": { "smithy.api#documentation": "Specifies the part after which listing should begin. Only parts with higher part numbers will be\n listed. For more information, see Uploading and copying objects using multipart upload\n in Amazon S3 in the Amazon Simple Storage Service user guide.
", "smithy.api#httpHeader": "x-amz-part-number-marker" } }, "SSECustomerAlgorithm": { "target": "com.amazonaws.s3#SSECustomerAlgorithm", "traits": { "smithy.api#documentation": "Specifies the algorithm to use when encrypting the object (for example, AES256).
\nThis functionality is not supported for directory buckets.
\nSpecifies the customer-provided encryption key for Amazon S3 to use in encrypting data. This value is\n used to store the object and then it is discarded; Amazon S3 does not store the encryption key. The key must\n be appropriate for use with the algorithm specified in the\n x-amz-server-side-encryption-customer-algorithm header.
This functionality is not supported for directory buckets.
\nSpecifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header\n for a message integrity check to ensure that the encryption key was transmitted without error.
\nThis functionality is not supported for directory buckets.
\nThe account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Specifies the fields at the root level that you want returned in the response. Fields that you do\n not specify are not returned.
", "smithy.api#httpHeader": "x-amz-object-attributes", "smithy.api#required": {} } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#GetObjectLegalHold": { "type": "operation", "input": { "target": "com.amazonaws.s3#GetObjectLegalHoldRequest" }, "output": { "target": "com.amazonaws.s3#GetObjectLegalHoldOutput" }, "traits": { "smithy.api#documentation": "This operation is not supported for directory buckets.
\nGets an object's current legal hold status. For more information, see Locking Objects.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nThe following action is related to GetObjectLegalHold:
\n GetObjectAttributes\n
\nThe current legal hold status for the specified object.
", "smithy.api#httpPayload": {}, "smithy.api#xmlName": "LegalHold" } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#GetObjectLegalHoldRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name containing the object whose legal hold status you want to retrieve.
\n\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "The key name for the object whose legal hold status you want to retrieve.
", "smithy.api#httpLabel": {}, "smithy.api#required": {} } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "The version ID of the object whose legal hold status you want to retrieve.
", "smithy.api#httpQuery": "versionId" } }, "RequestPayer": { "target": "com.amazonaws.s3#RequestPayer", "traits": { "smithy.api#httpHeader": "x-amz-request-payer" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nGets the Object Lock configuration for a bucket. The rule specified in the Object Lock configuration\n will be applied by default to every new object placed in the specified bucket. For more information, see\n Locking Objects.
\nThe following action is related to GetObjectLockConfiguration:
\n GetObjectAttributes\n
\nThe specified bucket's Object Lock configuration.
", "smithy.api#httpPayload": {} } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#GetObjectLockConfigurationRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket whose Object Lock configuration you want to retrieve.
\n\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Object data.
", "smithy.api#httpPayload": {} } }, "DeleteMarker": { "target": "com.amazonaws.s3#DeleteMarker", "traits": { "smithy.api#documentation": "Indicates whether the object retrieved was (true) or was not (false) a Delete Marker. If false, this\n response header does not appear in the response.
\nIf the current version of the object is a delete marker, Amazon S3 behaves as if the object was\n deleted and includes x-amz-delete-marker: true in the response.
If the specified version in the request is a delete marker, the response returns a 405\n Method Not Allowed error and the Last-Modified: timestamp response\n header.
Indicates that a range of bytes was specified in the request.
", "smithy.api#httpHeader": "accept-ranges" } }, "Expiration": { "target": "com.amazonaws.s3#Expiration", "traits": { "smithy.api#documentation": "If the object expiration is configured (see \n PutBucketLifecycleConfiguration\n ), the response includes this header. It\n includes the expiry-date and rule-id key-value pairs providing object\n expiration information. The value of the rule-id is URL-encoded.
Object expiration information is not returned in directory buckets and this header returns the\n value \"NotImplemented\" in all responses for directory buckets.
Provides information about object restoration action and expiration time of the restored object\n copy.
\nThis functionality is not supported for directory buckets. Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
Date and time when the object was last modified.
\n\n General purpose buckets - When you specify a\n versionId of the object in your request, if the specified version in the request is a\n delete marker, the response returns a 405 Method Not Allowed error and the\n Last-Modified: timestamp response header.
Size of the body in bytes.
", "smithy.api#httpHeader": "Content-Length" } }, "ETag": { "target": "com.amazonaws.s3#ETag", "traits": { "smithy.api#documentation": "An entity tag (ETag) is an opaque identifier assigned by a web server to a specific version of a\n resource found at a URL.
", "smithy.api#httpHeader": "ETag" } }, "ChecksumCRC32": { "target": "com.amazonaws.s3#ChecksumCRC32", "traits": { "smithy.api#documentation": "The Base64 encoded, 32-bit CRC32 checksum of the object. This checksum is only present if the object was uploaded\n with the object. For more information, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the object. This will only be present if the object was uploaded\n with the object. For more information, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the object. For more information, see\n Checking\n object integrity in the Amazon S3 User Guide.
The Base64 encoded, 160-bit SHA1 digest of the object. This will only be present if the object was uploaded\n with the object. For more information, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 digest of the object. This will only be present if the object was uploaded\n with the object. For more information, see \n Checking object integrity in the Amazon S3 User Guide.
The checksum type, which determines how part-level checksums are combined to create an object-level\n checksum for multipart objects. You can use this header response to verify that the checksum type that\n is received is the same checksum type that was specified in the CreateMultipartUpload\n request. For more information, see Checking object integrity in\n the Amazon S3 User Guide.
This is set to the number of metadata entries not returned in the headers that are prefixed with\n x-amz-meta-. This can happen if you create metadata using an API like SOAP that supports\n more flexible metadata than the REST API. For example, using SOAP, you can create metadata whose values\n are not legal HTTP headers.
This functionality is not supported for directory buckets.
\nVersion ID of the object.
\nThis functionality is not supported for directory buckets.
\nSpecifies caching behavior along the request/reply chain.
", "smithy.api#httpHeader": "Cache-Control" } }, "ContentDisposition": { "target": "com.amazonaws.s3#ContentDisposition", "traits": { "smithy.api#documentation": "Specifies presentational information for the object.
", "smithy.api#httpHeader": "Content-Disposition" } }, "ContentEncoding": { "target": "com.amazonaws.s3#ContentEncoding", "traits": { "smithy.api#documentation": "Indicates what content encodings have been applied to the object and thus what decoding mechanisms\n must be applied to obtain the media-type referenced by the Content-Type header field.
", "smithy.api#httpHeader": "Content-Encoding" } }, "ContentLanguage": { "target": "com.amazonaws.s3#ContentLanguage", "traits": { "smithy.api#documentation": "The language the content is in.
", "smithy.api#httpHeader": "Content-Language" } }, "ContentRange": { "target": "com.amazonaws.s3#ContentRange", "traits": { "smithy.api#documentation": "The portion of the object returned in the response.
", "smithy.api#httpHeader": "Content-Range" } }, "ContentType": { "target": "com.amazonaws.s3#ContentType", "traits": { "smithy.api#documentation": "A standard MIME type describing the format of the object data.
", "smithy.api#httpHeader": "Content-Type" } }, "Expires": { "target": "com.amazonaws.s3#Expires", "traits": { "smithy.api#documentation": "The date and time at which the object is no longer cacheable.
", "smithy.api#httpHeader": "Expires" } }, "WebsiteRedirectLocation": { "target": "com.amazonaws.s3#WebsiteRedirectLocation", "traits": { "smithy.api#documentation": "If the bucket is configured as a website, redirects requests for this object to another object in\n the same bucket or to an external URL. Amazon S3 stores the value of this header in the object\n metadata.
\nThis functionality is not supported for directory buckets.
\nThe server-side encryption algorithm used when you store this object in Amazon S3 or Amazon FSx.
\nWhen accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side\n encryption option is aws:fsx.
A map of metadata to store with the object in S3.
", "smithy.api#httpPrefixHeaders": "x-amz-meta-" } }, "SSECustomerAlgorithm": { "target": "com.amazonaws.s3#SSECustomerAlgorithm", "traits": { "smithy.api#documentation": "If server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to confirm the encryption algorithm that's used.
\nThis functionality is not supported for directory buckets.
\nIf server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to provide the round-trip message integrity verification of the customer-provided\n encryption key.
\nThis functionality is not supported for directory buckets.
\nIf present, indicates the ID of the KMS key that was used for object encryption.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-aws-kms-key-id" } }, "BucketKeyEnabled": { "target": "com.amazonaws.s3#BucketKeyEnabled", "traits": { "smithy.api#documentation": "Indicates whether the object uses an S3 Bucket Key for server-side encryption with Key Management Service (KMS)\n keys (SSE-KMS).
", "smithy.api#httpHeader": "x-amz-server-side-encryption-bucket-key-enabled" } }, "StorageClass": { "target": "com.amazonaws.s3#StorageClass", "traits": { "smithy.api#documentation": "Provides storage class information of the object. Amazon S3 returns this header for all objects except\n for S3 Standard storage class objects.
\n\n Directory buckets -\n Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
Amazon S3 can return this if your request involves a bucket that is either a source or destination in a\n replication rule.
\nThis functionality is not supported for directory buckets.
\nThe count of parts this object has. This value is only returned if you specify\n partNumber in your request and the object was uploaded as a multipart upload.
The number of tags, if any, on the object, when you have the relevant permission to read object\n tags.
\nYou can use GetObjectTagging to retrieve the tag set associated with an object.
\nThis functionality is not supported for directory buckets.
\nThe Object Lock mode that's currently in place for this object.
\nThis functionality is not supported for directory buckets.
\nThe date and time when this object's Object Lock will expire.
\nThis functionality is not supported for directory buckets.
\nIndicates whether this object has an active legal hold. This field is only returned if you have\n permission to view an object's legal hold status.
\nThis functionality is not supported for directory buckets.
\nThe bucket name containing the object.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\n\n Object Lambda access points - When you use this action with an Object Lambda access point, you must direct requests to the Object Lambda access point hostname. The Object Lambda access point hostname takes the form AccessPointName-AccountId.s3-object-lambda.Region.amazonaws.com.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Return the object only if its entity tag (ETag) is the same as the one specified in this header;\n otherwise, return a 412 Precondition Failed error.
If both of the If-Match and If-Unmodified-Since headers are present in the\n request as follows: If-Match condition evaluates to true, and;\n If-Unmodified-Since condition evaluates to false; then, S3 returns 200\n OK and the data requested.
For more information about conditional requests, see RFC 7232.
", "smithy.api#httpHeader": "If-Match" } }, "IfModifiedSince": { "target": "com.amazonaws.s3#IfModifiedSince", "traits": { "smithy.api#documentation": "Return the object only if it has been modified since the specified time; otherwise, return a\n 304 Not Modified error.
If both of the If-None-Match and If-Modified-Since headers are present in\n the request as follows: If-None-Match condition evaluates to false, and;\n If-Modified-Since condition evaluates to true; then, S3 returns 304\n Not Modified status code.
For more information about conditional requests, see RFC 7232.
", "smithy.api#httpHeader": "If-Modified-Since" } }, "IfNoneMatch": { "target": "com.amazonaws.s3#IfNoneMatch", "traits": { "smithy.api#documentation": "Return the object only if its entity tag (ETag) is different from the one specified in this header;\n otherwise, return a 304 Not Modified error.
If both of the If-None-Match and If-Modified-Since headers are present in\n the request as follows: If-None-Match condition evaluates to false, and;\n If-Modified-Since condition evaluates to true; then, S3 returns 304\n Not Modified HTTP status code.
For more information about conditional requests, see RFC 7232.
", "smithy.api#httpHeader": "If-None-Match" } }, "IfUnmodifiedSince": { "target": "com.amazonaws.s3#IfUnmodifiedSince", "traits": { "smithy.api#documentation": "Return the object only if it has not been modified since the specified time; otherwise, return a\n 412 Precondition Failed error.
If both of the If-Match and If-Unmodified-Since headers are present in the\n request as follows: If-Match condition evaluates to true, and;\n If-Unmodified-Since condition evaluates to false; then, S3 returns 200\n OK and the data requested.
For more information about conditional requests, see RFC 7232.
", "smithy.api#httpHeader": "If-Unmodified-Since" } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "Key of the object to get.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Key" } } }, "Range": { "target": "com.amazonaws.s3#Range", "traits": { "smithy.api#documentation": "Downloads the specified byte range of an object. For more information about the HTTP Range header,\n see https://www.rfc-editor.org/rfc/rfc9110.html#name-range.
\nAmazon S3 doesn't support retrieving multiple ranges of data per GET request.
Sets the Cache-Control header of the response.
Sets the Content-Disposition header of the response.
Sets the Content-Encoding header of the response.
Sets the Content-Language header of the response.
Sets the Content-Type header of the response.
Sets the Expires header of the response.
Version ID used to reference a specific version of the object.
\nBy default, the GetObject operation returns the current version of an object. To return\n a different version, use the versionId subresource.
If you include a versionId in your request header, you must have the\n s3:GetObjectVersion permission to access a specific version of an object. The\n s3:GetObject permission is not required in this scenario.
If you request the current version of an object without a specific versionId in\n the request header, only the s3:GetObject permission is required. The\n s3:GetObjectVersion permission is not required in this scenario.
\n Directory buckets - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets.\n You can only specify null to the versionId query parameter in the\n request.
For more information about versioning, see PutBucketVersioning.
", "smithy.api#httpQuery": "versionId" } }, "SSECustomerAlgorithm": { "target": "com.amazonaws.s3#SSECustomerAlgorithm", "traits": { "smithy.api#documentation": "Specifies the algorithm to use when decrypting the object (for example, AES256).
If you encrypt an object by using server-side encryption with customer-provided encryption keys\n (SSE-C) when you store the object in Amazon S3, then when you GET the object, you must use the following\n headers:
\n\n x-amz-server-side-encryption-customer-algorithm\n
\n x-amz-server-side-encryption-customer-key\n
\n x-amz-server-side-encryption-customer-key-MD5\n
For more information about SSE-C, see Server-Side Encryption (Using\n Customer-Provided Encryption Keys) in the Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\nSpecifies the customer-provided encryption key that you originally provided for Amazon S3 to encrypt the\n data before storing it. This value is used to decrypt the object when recovering it and must match the\n one used when storing the data. The key must be appropriate for use with the algorithm specified in the\n x-amz-server-side-encryption-customer-algorithm header.
If you encrypt an object by using server-side encryption with customer-provided encryption keys\n (SSE-C) when you store the object in Amazon S3, then when you GET the object, you must use the following\n headers:
\n\n x-amz-server-side-encryption-customer-algorithm\n
\n x-amz-server-side-encryption-customer-key\n
\n x-amz-server-side-encryption-customer-key-MD5\n
For more information about SSE-C, see Server-Side Encryption (Using\n Customer-Provided Encryption Keys) in the Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\nSpecifies the 128-bit MD5 digest of the customer-provided encryption key according to RFC 1321. Amazon S3\n uses this header for a message integrity check to ensure that the encryption key was transmitted without\n error.
\nIf you encrypt an object by using server-side encryption with customer-provided encryption keys\n (SSE-C) when you store the object in Amazon S3, then when you GET the object, you must use the following\n headers:
\n\n x-amz-server-side-encryption-customer-algorithm\n
\n x-amz-server-side-encryption-customer-key\n
\n x-amz-server-side-encryption-customer-key-MD5\n
For more information about SSE-C, see Server-Side Encryption (Using\n Customer-Provided Encryption Keys) in the Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\nPart number of the object being read. This is a positive integer between 1 and 10,000. Effectively\n performs a 'ranged' GET request for the part specified. Useful for downloading just a part of an\n object.
", "smithy.api#httpQuery": "partNumber" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
To retrieve the checksum, this mode must be enabled.
", "smithy.api#httpHeader": "x-amz-checksum-mode" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#GetObjectResponseStatusCode": { "type": "integer" }, "com.amazonaws.s3#GetObjectRetention": { "type": "operation", "input": { "target": "com.amazonaws.s3#GetObjectRetentionRequest" }, "output": { "target": "com.amazonaws.s3#GetObjectRetentionOutput" }, "traits": { "smithy.api#documentation": "This operation is not supported for directory buckets.
\nRetrieves an object's retention settings. For more information, see Locking Objects.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nThe following action is related to GetObjectRetention:
\n GetObjectAttributes\n
\nThe container element for an object's retention settings.
", "smithy.api#httpPayload": {}, "smithy.api#xmlName": "Retention" } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#GetObjectRetentionRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name containing the object whose retention settings you want to retrieve.
\n\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "The key name for the object whose retention settings you want to retrieve.
", "smithy.api#httpLabel": {}, "smithy.api#required": {} } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "The version ID for the object whose retention settings you want to retrieve.
", "smithy.api#httpQuery": "versionId" } }, "RequestPayer": { "target": "com.amazonaws.s3#RequestPayer", "traits": { "smithy.api#httpHeader": "x-amz-request-payer" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nReturns the tag-set of an object. You send the GET request against the tagging subresource\n associated with the object.
\nTo use this operation, you must have permission to perform the s3:GetObjectTagging\n action. By default, the GET action returns information about current version of an object. For a\n versioned bucket, you can have multiple versions of an object in your bucket. To retrieve tags of any\n other version, use the versionId query parameter. You also need permission for the\n s3:GetObjectVersionTagging action.
By default, the bucket owner has this permission and can grant this permission to others.
\nFor information about the Amazon S3 object tagging feature, see Object Tagging.
\nThe following actions are related to GetObjectTagging:
\n DeleteObjectTagging\n
\n\n GetObjectAttributes\n
\n\n PutObjectTagging\n
\nThe versionId of the object for which you got the tagging information.
", "smithy.api#httpHeader": "x-amz-version-id" } }, "TagSet": { "target": "com.amazonaws.s3#TagSet", "traits": { "smithy.api#documentation": "Contains the tag set.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "Tagging" } }, "com.amazonaws.s3#GetObjectTaggingRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name containing the object for which to get the tagging information.
\n\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Object key for which to get the tagging information.
", "smithy.api#httpLabel": {}, "smithy.api#required": {} } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "The versionId of the object for which to get the tagging information.
", "smithy.api#httpQuery": "versionId" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nReturns torrent files from a bucket. BitTorrent can save you bandwidth when you're distributing\n large files.
\nYou can get torrent only for objects that are less than 5 GB in size, and that are not encrypted\n using server-side encryption with a customer-provided encryption key.
\nTo use GET, you must have READ access to the object.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nThe following action is related to GetObjectTorrent:
\n GetObject\n
\nA Bencoded dictionary as defined by the BitTorrent specification
", "smithy.api#httpPayload": {} } }, "RequestCharged": { "target": "com.amazonaws.s3#RequestCharged", "traits": { "smithy.api#httpHeader": "x-amz-request-charged" } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#GetObjectTorrentRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket containing the object for which to get the torrent files.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "The object key for which to get the information.
", "smithy.api#httpLabel": {}, "smithy.api#required": {} } }, "RequestPayer": { "target": "com.amazonaws.s3#RequestPayer", "traits": { "smithy.api#httpHeader": "x-amz-request-payer" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nRetrieves the PublicAccessBlock configuration for an Amazon S3 bucket. To use this\n operation, you must have the s3:GetBucketPublicAccessBlock permission. For more information\n about Amazon S3 permissions, see Specifying Permissions in a\n Policy.
When Amazon S3 evaluates the PublicAccessBlock configuration for a bucket or an object, it\n checks the PublicAccessBlock configuration for both the bucket (or the bucket that\n contains the object) and the bucket owner's account. If the PublicAccessBlock settings\n are different between the bucket and the account, Amazon S3 uses the most restrictive combination of the\n bucket-level and account-level settings.
For more information about when Amazon S3 considers a bucket or an object public, see The Meaning of \"Public\".
\nThe following operations are related to GetPublicAccessBlock:
\n PutPublicAccessBlock\n
\n\n GetPublicAccessBlock\n
\nThe PublicAccessBlock configuration currently in effect for this Amazon S3 bucket.
The name of the Amazon S3 bucket whose PublicAccessBlock configuration you want to retrieve.\n
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Retrieval tier at which the restore will be processed.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Container for S3 Glacier job parameters.
" } }, "com.amazonaws.s3#Grant": { "type": "structure", "members": { "Grantee": { "target": "com.amazonaws.s3#Grantee", "traits": { "smithy.api#documentation": "The person being granted permissions.
", "smithy.api#xmlNamespace": { "uri": "http://www.w3.org/2001/XMLSchema-instance", "prefix": "xsi" } } }, "Permission": { "target": "com.amazonaws.s3#Permission", "traits": { "smithy.api#documentation": "Specifies the permission given to the grantee.
" } } }, "traits": { "smithy.api#documentation": "Container for grant information.
" } }, "com.amazonaws.s3#GrantFullControl": { "type": "string" }, "com.amazonaws.s3#GrantRead": { "type": "string" }, "com.amazonaws.s3#GrantReadACP": { "type": "string" }, "com.amazonaws.s3#GrantWrite": { "type": "string" }, "com.amazonaws.s3#GrantWriteACP": { "type": "string" }, "com.amazonaws.s3#Grantee": { "type": "structure", "members": { "DisplayName": { "target": "com.amazonaws.s3#DisplayName", "traits": { "smithy.api#documentation": "Screen name of the grantee.
" } }, "EmailAddress": { "target": "com.amazonaws.s3#EmailAddress", "traits": { "smithy.api#documentation": "Email address of the grantee.
\nUsing email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:
\nUS East (N. Virginia)
\nUS West (N. California)
\nUS West (Oregon)
\nAsia Pacific (Singapore)
\nAsia Pacific (Sydney)
\nAsia Pacific (Tokyo)
\nEurope (Ireland)
\nSouth America (S\u00e3o Paulo)
\nFor a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the Amazon Web Services General Reference.
\nThe canonical user ID of the grantee.
" } }, "URI": { "target": "com.amazonaws.s3#URI", "traits": { "smithy.api#documentation": "URI of the grantee group.
" } }, "Type": { "target": "com.amazonaws.s3#Type", "traits": { "smithy.api#documentation": "Type of grantee
", "smithy.api#required": {}, "smithy.api#xmlAttribute": {}, "smithy.api#xmlName": "xsi:type" } } }, "traits": { "smithy.api#documentation": "Container for the person being granted permissions.
" } }, "com.amazonaws.s3#Grants": { "type": "list", "member": { "target": "com.amazonaws.s3#Grant", "traits": { "smithy.api#xmlName": "Grant" } } }, "com.amazonaws.s3#HeadBucket": { "type": "operation", "input": { "target": "com.amazonaws.s3#HeadBucketRequest" }, "output": { "target": "com.amazonaws.s3#HeadBucketOutput" }, "errors": [ { "target": "com.amazonaws.s3#NotFound" } ], "traits": { "smithy.api#documentation": "You can use this operation to determine if a bucket exists and if you have permission to access it.\n The action returns a 200 OK if the bucket exists and you have permission to access\n it.
If the bucket does not exist or you do not have permission to access it, the HEAD\n request returns a generic 400 Bad Request, 403 Forbidden or 404 Not\n Found code. A message body is not included, so you cannot determine the exception beyond\n these HTTP response codes.
\n General purpose buckets - Request to public buckets that\n grant the s3:ListBucket permission publicly do not need to be signed. All other\n HeadBucket requests must be authenticated and signed by using IAM credentials\n (access key ID and secret access key for the IAM identities). All headers with the\n x-amz- prefix, including x-amz-copy-source, must be signed. For more\n information, see REST Authentication.
\n Directory buckets - You must use IAM credentials to\n authenticate and authorize your access to the HeadBucket API operation, instead of\n using the temporary security credentials through the CreateSession API\n operation.
Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.
\n\n General purpose bucket permissions - To use this\n operation, you must have permissions to perform the s3:ListBucket action. The\n bucket owner has this permission by default and can grant this permission to others. For more\n information about permissions, see Managing access permissions to your\n Amazon S3 resources in the Amazon S3 User Guide.
\n Directory bucket permissions - You must have the\n \n s3express:CreateSession\n permission in the\n Action element of a policy. By default, the session is in the\n ReadWrite mode. If you want to restrict the access, you can explicitly set the\n s3express:SessionMode condition key to ReadOnly on the\n bucket.
For more information about example bucket policies, see Example\n bucket policies for S3 Express One Zone and Amazon Web Services\n Identity and Access Management (IAM) identity-based policies for S3 Express One Zone in the\n Amazon S3 User Guide.
\n\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
You must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
The Amazon Resource Name (ARN) of the S3 bucket. ARNs uniquely identify Amazon Web Services resources across all\n of Amazon Web Services.
\nThis parameter is only supported for S3 directory buckets. For more information, see Using tags with\n directory buckets.
\nThe type of location where the bucket is created.
\nThis functionality is only supported by directory buckets.
\nThe name of the location where the bucket will be created.
\nFor directory buckets, the Zone ID of the Availability Zone or the Local Zone where the bucket is created. An example\n Zone ID value for an Availability Zone is usw2-az1.
This functionality is only supported by directory buckets.
\nThe Region that the bucket is located.
", "smithy.api#httpHeader": "x-amz-bucket-region" } }, "AccessPointAlias": { "target": "com.amazonaws.s3#AccessPointAlias", "traits": { "smithy.api#documentation": "Indicates whether the bucket name used in the request is an access point alias.
\nFor directory buckets, the value of this field is false.
The bucket name.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\n\n Object Lambda access points - When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned. \nFor more information about InvalidAccessPointAliasError, see List of\n Error Codes.
Object Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The HEAD operation retrieves metadata from an object without returning the object\n itself. This operation is useful if you're interested only in an object's metadata.
A HEAD request has the same options as a GET operation on an object. The\n response is identical to the GET response except that there is no response body. Because\n of this, if the HEAD request generates an error, it returns a generic code, such as\n 400 Bad Request, 403 Forbidden, 404 Not Found, 405\n Method Not Allowed, 412 Precondition Failed, or 304 Not Modified.\n It's not possible to retrieve the exact exception of these error codes.
Request headers are limited to 8 KB in size. For more information, see Common Request Headers.
\n\n General purpose bucket permissions - To use\n HEAD, you must have the s3:GetObject permission. You need the\n relevant read object (or version) permission for this operation. For more information, see\n Actions, resources,\n and condition keys for Amazon S3 in the Amazon S3 User Guide. For more\n information about the permissions to S3 API operations by S3 resource types, see Required permissions for\n Amazon S3 API operations in the Amazon S3 User Guide.
If the object you request doesn't exist, the error that Amazon S3 returns depends on whether\n you also have the s3:ListBucket permission.
If you have the s3:ListBucket permission on the bucket, Amazon S3 returns an\n HTTP status code 404 Not Found error.
If you don\u2019t have the s3:ListBucket permission, Amazon S3 returns an HTTP\n status code 403 Forbidden error.
\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
If you enable x-amz-checksum-mode in the request and the object is encrypted\n with Amazon Web Services Key Management Service (Amazon Web Services KMS), you must also have the\n kms:GenerateDataKey and kms:Decrypt permissions in IAM\n identity-based policies and KMS key policies for the KMS key to retrieve the checksum of\n the object.
Encryption request headers, like x-amz-server-side-encryption, should not be\n sent for HEAD requests if your object uses server-side encryption with Key Management Service\n (KMS) keys (SSE-KMS), dual-layer server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), or\n server-side encryption with Amazon S3 managed encryption keys (SSE-S3). The\n x-amz-server-side-encryption header is used when you PUT an object\n to S3 and want to specify the encryption method. If you include this header in a\n HEAD request for an object that uses these types of keys, you\u2019ll get an HTTP\n 400 Bad Request error. It's because the encryption method can't be changed when\n you retrieve the object.
If you encrypt an object by using server-side encryption with customer-provided encryption\n keys (SSE-C) when you store the object in Amazon S3, then when you retrieve the metadata from the\n object, you must use the following headers to provide the encryption key for the server to be able\n to retrieve the object's metadata. The headers are:
\n\n x-amz-server-side-encryption-customer-algorithm\n
\n x-amz-server-side-encryption-customer-key\n
\n x-amz-server-side-encryption-customer-key-MD5\n
For more information about SSE-C, see Server-Side Encryption (Using\n Customer-Provided Encryption Keys) in the Amazon S3 User Guide.
\n\n Directory bucket -\n For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more\n information, see Protecting data with server-side encryption in the Amazon S3 User Guide.
\nIf the current version of the object is a delete marker, Amazon S3 behaves as if the object was\n deleted and includes x-amz-delete-marker: true in the response.
If the specified version is a delete marker, the response returns a 405 Method Not\n Allowed error and the Last-Modified: timestamp response header.
\n Directory buckets -\n Delete marker is not supported for directory buckets.
\n\n Directory buckets -\n S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets. You can only specify null to the\n versionId query parameter in the request.
\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
The following actions are related to HeadObject:
\n GetObject\n
\n\n GetObjectAttributes\n
\nSpecifies whether the object retrieved was (true) or was not (false) a Delete Marker. If false, this\n response header does not appear in the response.
\nThis functionality is not supported for directory buckets.
\nIndicates that a range of bytes was specified.
", "smithy.api#httpHeader": "accept-ranges" } }, "Expiration": { "target": "com.amazonaws.s3#Expiration", "traits": { "smithy.api#documentation": "If the object expiration is configured (see \n PutBucketLifecycleConfiguration\n ), the response includes this header. It\n includes the expiry-date and rule-id key-value pairs providing object\n expiration information. The value of the rule-id is URL-encoded.
Object expiration information is not returned in directory buckets and this header returns the\n value \"NotImplemented\" in all responses for directory buckets.
If the object is an archived object (an object whose storage class is GLACIER), the response\n includes this header if either the archive restoration is in progress (see RestoreObject or an archive copy is already\n restored.
\nIf an archive copy is already restored, the header value indicates when Amazon S3 is scheduled to delete\n the object copy. For example:
\n\n x-amz-restore: ongoing-request=\"false\", expiry-date=\"Fri, 21 Dec 2012 00:00:00\n GMT\"\n
If the object restoration is in progress, the header returns the value\n ongoing-request=\"true\".
For more information about archiving objects, see Transitioning Objects: General Considerations.
\nThis functionality is not supported for directory buckets. Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
The archive state of the head object.
\nThis functionality is not supported for directory buckets.
\nDate and time when the object was last modified.
", "smithy.api#httpHeader": "Last-Modified" } }, "ContentLength": { "target": "com.amazonaws.s3#ContentLength", "traits": { "smithy.api#documentation": "Size of the body in bytes.
", "smithy.api#httpHeader": "Content-Length" } }, "ChecksumCRC32": { "target": "com.amazonaws.s3#ChecksumCRC32", "traits": { "smithy.api#documentation": "The Base64 encoded, 32-bit CRC32 checksum of the object. This checksum is only be present if the checksum was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the object. This checksum is only present if the checksum was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the object. For more information, see\n Checking\n object integrity in the Amazon S3 User Guide.
The Base64 encoded, 160-bit SHA1 digest of the object. This will only be present if the object was uploaded\n with the object. When you use the API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 digest of the object. This will only be present if the object was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The checksum type, which determines how part-level checksums are combined to create an object-level\n checksum for multipart objects. You can use this header response to verify that the checksum type that\n is received is the same checksum type that was specified in CreateMultipartUpload request.\n For more information, see Checking object integrity in the Amazon S3\n User Guide.
An entity tag (ETag) is an opaque identifier assigned by a web server to a specific version of a\n resource found at a URL.
", "smithy.api#httpHeader": "ETag" } }, "MissingMeta": { "target": "com.amazonaws.s3#MissingMeta", "traits": { "smithy.api#documentation": "This is set to the number of metadata entries not returned in x-amz-meta headers. This\n can happen if you create metadata using an API like SOAP that supports more flexible metadata than the\n REST API. For example, using SOAP, you can create metadata whose values are not legal HTTP\n headers.
This functionality is not supported for directory buckets.
\nVersion ID of the object.
\nThis functionality is not supported for directory buckets.
\nSpecifies caching behavior along the request/reply chain.
", "smithy.api#httpHeader": "Cache-Control" } }, "ContentDisposition": { "target": "com.amazonaws.s3#ContentDisposition", "traits": { "smithy.api#documentation": "Specifies presentational information for the object.
", "smithy.api#httpHeader": "Content-Disposition" } }, "ContentEncoding": { "target": "com.amazonaws.s3#ContentEncoding", "traits": { "smithy.api#documentation": "Indicates what content encodings have been applied to the object and thus what decoding mechanisms\n must be applied to obtain the media-type referenced by the Content-Type header field.
", "smithy.api#httpHeader": "Content-Encoding" } }, "ContentLanguage": { "target": "com.amazonaws.s3#ContentLanguage", "traits": { "smithy.api#documentation": "The language the content is in.
", "smithy.api#httpHeader": "Content-Language" } }, "ContentType": { "target": "com.amazonaws.s3#ContentType", "traits": { "smithy.api#documentation": "A standard MIME type describing the format of the object data.
", "smithy.api#httpHeader": "Content-Type" } }, "ContentRange": { "target": "com.amazonaws.s3#ContentRange", "traits": { "smithy.api#documentation": "The portion of the object returned in the response for a GET request.
The date and time at which the object is no longer cacheable.
", "smithy.api#httpHeader": "Expires" } }, "WebsiteRedirectLocation": { "target": "com.amazonaws.s3#WebsiteRedirectLocation", "traits": { "smithy.api#documentation": "If the bucket is configured as a website, redirects requests for this object to another object in\n the same bucket or to an external URL. Amazon S3 stores the value of this header in the object\n metadata.
\nThis functionality is not supported for directory buckets.
\nThe server-side encryption algorithm used when you store this object in Amazon S3 or Amazon FSx.
\nWhen accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side\n encryption option is aws:fsx.
A map of metadata to store with the object in S3.
", "smithy.api#httpPrefixHeaders": "x-amz-meta-" } }, "SSECustomerAlgorithm": { "target": "com.amazonaws.s3#SSECustomerAlgorithm", "traits": { "smithy.api#documentation": "If server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to confirm the encryption algorithm that's used.
\nThis functionality is not supported for directory buckets.
\nIf server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to provide the round-trip message integrity verification of the customer-provided\n encryption key.
\nThis functionality is not supported for directory buckets.
\nIf present, indicates the ID of the KMS key that was used for object encryption.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-aws-kms-key-id" } }, "BucketKeyEnabled": { "target": "com.amazonaws.s3#BucketKeyEnabled", "traits": { "smithy.api#documentation": "Indicates whether the object uses an S3 Bucket Key for server-side encryption with Key Management Service (KMS)\n keys (SSE-KMS).
", "smithy.api#httpHeader": "x-amz-server-side-encryption-bucket-key-enabled" } }, "StorageClass": { "target": "com.amazonaws.s3#StorageClass", "traits": { "smithy.api#documentation": "Provides storage class information of the object. Amazon S3 returns this header for all objects except\n for S3 Standard storage class objects.
\nFor more information, see Storage Classes.
\n\n Directory buckets -\n Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
Amazon S3 can return this header if your request involves a bucket that is either a source or a\n destination in a replication rule.
\nIn replication, you have a source bucket on which you configure replication and destination bucket\n or buckets where Amazon S3 stores object replicas. When you request an object (GetObject) or\n object metadata (HeadObject) from these buckets, Amazon S3 will return the\n x-amz-replication-status header in the response as follows:
\n If requesting an object from the source bucket, Amazon S3 will\n return the x-amz-replication-status header if the object in your request is eligible\n for replication.
For example, suppose that in your replication configuration, you specify object prefix\n TaxDocs requesting Amazon S3 to replicate objects with key prefix TaxDocs.\n Any objects you upload with this key name prefix, for example TaxDocs/document1.pdf,\n are eligible for replication. For any object request with this key name prefix, Amazon S3 will return the\n x-amz-replication-status header with value PENDING, COMPLETED or FAILED indicating\n object replication status.
\n If requesting an object from a destination bucket, Amazon S3 will\n return the x-amz-replication-status header with value REPLICA if the object in your\n request is a replica that Amazon S3 created and there is no replica modification replication in\n progress.
\n When replicating objects to multiple destination buckets, the\n x-amz-replication-status header acts differently. The header of the source object\n will only return a value of COMPLETED when replication is successful to all destinations. The header\n will remain at value PENDING until replication has completed for all destinations. If one or more\n destinations fails replication the header will return FAILED.
For more information, see Replication.
\nThis functionality is not supported for directory buckets.
\nThe count of parts this object has. This value is only returned if you specify\n partNumber in your request and the object was uploaded as a multipart upload.
The number of tags, if any, on the object, when you have the relevant permission to read object\n tags.
\nYou can use GetObjectTagging to retrieve the tag set associated with an object.
\nThis functionality is not supported for directory buckets.
\nThe Object Lock mode, if any, that's in effect for this object. This header is only returned if the\n requester has the s3:GetObjectRetention permission. For more information about S3 Object\n Lock, see Object Lock.
This functionality is not supported for directory buckets.
\nThe date and time when the Object Lock retention period expires. This header is only returned if the\n requester has the s3:GetObjectRetention permission.
This functionality is not supported for directory buckets.
\nSpecifies whether a legal hold is in effect for this object. This header is only returned if the\n requester has the s3:GetObjectLegalHold permission. This header is not returned if the\n specified version of this object has never had a legal hold applied. For more information about S3\n Object Lock, see Object\n Lock.
This functionality is not supported for directory buckets.
\nThe name of the bucket that contains the object.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Return the object only if its entity tag (ETag) is the same as the one specified; otherwise, return\n a 412 (precondition failed) error.
\nIf both of the If-Match and If-Unmodified-Since headers are present in the\n request as follows:
\n If-Match condition evaluates to true, and;
\n If-Unmodified-Since condition evaluates to false;
Then Amazon S3 returns 200 OK and the data requested.
For more information about conditional requests, see RFC 7232.
", "smithy.api#httpHeader": "If-Match" } }, "IfModifiedSince": { "target": "com.amazonaws.s3#IfModifiedSince", "traits": { "smithy.api#documentation": "Return the object only if it has been modified since the specified time; otherwise, return a 304\n (not modified) error.
\nIf both of the If-None-Match and If-Modified-Since headers are present in\n the request as follows:
\n If-None-Match condition evaluates to false, and;
\n If-Modified-Since condition evaluates to true;
Then Amazon S3 returns the 304 Not Modified response code.
For more information about conditional requests, see RFC 7232.
", "smithy.api#httpHeader": "If-Modified-Since" } }, "IfNoneMatch": { "target": "com.amazonaws.s3#IfNoneMatch", "traits": { "smithy.api#documentation": "Return the object only if its entity tag (ETag) is different from the one specified; otherwise,\n return a 304 (not modified) error.
\nIf both of the If-None-Match and If-Modified-Since headers are present in\n the request as follows:
\n If-None-Match condition evaluates to false, and;
\n If-Modified-Since condition evaluates to true;
Then Amazon S3 returns the 304 Not Modified response code.
For more information about conditional requests, see RFC 7232.
", "smithy.api#httpHeader": "If-None-Match" } }, "IfUnmodifiedSince": { "target": "com.amazonaws.s3#IfUnmodifiedSince", "traits": { "smithy.api#documentation": "Return the object only if it has not been modified since the specified time; otherwise, return a 412\n (precondition failed) error.
\nIf both of the If-Match and If-Unmodified-Since headers are present in the\n request as follows:
\n If-Match condition evaluates to true, and;
\n If-Unmodified-Since condition evaluates to false;
Then Amazon S3 returns 200 OK and the data requested.
For more information about conditional requests, see RFC 7232.
", "smithy.api#httpHeader": "If-Unmodified-Since" } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "The object key.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Key" } } }, "Range": { "target": "com.amazonaws.s3#Range", "traits": { "smithy.api#documentation": "HeadObject returns only the metadata for an object. If the Range is satisfiable, only the\n ContentLength is affected in the response. If the Range is not satisfiable, S3 returns a\n 416 - Requested Range Not Satisfiable error.
Sets the Cache-Control header of the response.
Sets the Content-Disposition header of the response.
Sets the Content-Encoding header of the response.
Sets the Content-Language header of the response.
Sets the Content-Type header of the response.
Sets the Expires header of the response.
Version ID used to reference a specific version of the object.
\nFor directory buckets in this API operation, only the null value of the version ID is supported.
Specifies the algorithm to use when encrypting the object (for example, AES256).
\nThis functionality is not supported for directory buckets.
\nSpecifies the customer-provided encryption key for Amazon S3 to use in encrypting data. This value is\n used to store the object and then it is discarded; Amazon S3 does not store the encryption key. The key must\n be appropriate for use with the algorithm specified in the\n x-amz-server-side-encryption-customer-algorithm header.
This functionality is not supported for directory buckets.
\nSpecifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header\n for a message integrity check to ensure that the encryption key was transmitted without error.
\nThis functionality is not supported for directory buckets.
\nPart number of the object being read. This is a positive integer between 1 and 10,000. Effectively\n performs a 'ranged' HEAD request for the part specified. Useful querying about the size of the part and\n the number of parts in this object.
", "smithy.api#httpQuery": "partNumber" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
To retrieve the checksum, this parameter must be enabled.
\n\n General purpose buckets -\n If you enable checksum mode and the object is uploaded with a checksum and encrypted with\n an Key Management Service (KMS) key, you must have permission to use the kms:Decrypt action to\n retrieve the checksum.
\n Directory buckets - If you enable ChecksumMode\n and the object is encrypted with Amazon Web Services Key Management Service (Amazon Web Services KMS), you must also have the\n kms:GenerateDataKey and kms:Decrypt permissions in IAM identity-based\n policies and KMS key policies for the KMS key to retrieve the checksum of the object.
Parameters on this idempotent request are inconsistent with parameters used in previous request(s).
\nFor a list of error codes and more information on Amazon S3 errors, see Error codes.
\nIdempotency ensures that an API request completes no more than one time. With an idempotent\n request, if the original request completes successfully, any subsequent retries complete successfully\n without performing any further actions.
\nA suffix that is appended to a request that is for a directory on the website endpoint. (For\n example, if the suffix is index.html and you make a request to\n samplebucket/images/, the data that is returned will be for the object with the key name\n images/index.html.) The suffix must not be empty and must not include a slash\n character.
Replacement must be made for object keys containing special characters (such as carriage returns) when using \n XML requests. For more information, see \n XML related object key constraints.
\nContainer for the Suffix element.
If the principal is an Amazon Web Services account, it provides the Canonical User ID. If the principal is an\n IAM User, it provides a user ARN value.
\n\n Directory buckets - If the principal is an Amazon Web Services account,\n it provides the Amazon Web Services account ID. If the principal is an IAM User, it provides a user ARN\n value.
\nName of the Principal.
\nThis functionality is not supported for directory buckets.
\nContainer element that identifies who initiated the multipart upload.
" } }, "com.amazonaws.s3#InputSerialization": { "type": "structure", "members": { "CSV": { "target": "com.amazonaws.s3#CSVInput", "traits": { "smithy.api#documentation": "Describes the serialization of a CSV-encoded object.
" } }, "CompressionType": { "target": "com.amazonaws.s3#CompressionType", "traits": { "smithy.api#documentation": "Specifies object's compression format. Valid values: NONE, GZIP, BZIP2. Default Value: NONE.
" } }, "JSON": { "target": "com.amazonaws.s3#JSONInput", "traits": { "smithy.api#documentation": "Specifies JSON as object's input serialization format.
" } }, "Parquet": { "target": "com.amazonaws.s3#ParquetInput", "traits": { "smithy.api#documentation": "Specifies Parquet as object's input serialization format.
" } } }, "traits": { "smithy.api#documentation": "Describes the serialization format of the object.
" } }, "com.amazonaws.s3#IntelligentTieringAccessTier": { "type": "enum", "members": { "ARCHIVE_ACCESS": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ARCHIVE_ACCESS" } }, "DEEP_ARCHIVE_ACCESS": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "DEEP_ARCHIVE_ACCESS" } } } }, "com.amazonaws.s3#IntelligentTieringAndOperator": { "type": "structure", "members": { "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "An object key name prefix that identifies the subset of objects to which the configuration\n applies.
" } }, "Tags": { "target": "com.amazonaws.s3#TagSet", "traits": { "smithy.api#documentation": "All of these tags must exist in the object's tag set in order for the configuration to apply.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Tag" } } }, "traits": { "smithy.api#documentation": "A container for specifying S3 Intelligent-Tiering filters. The filters determine the subset of\n objects to which the rule applies.
" } }, "com.amazonaws.s3#IntelligentTieringConfiguration": { "type": "structure", "members": { "Id": { "target": "com.amazonaws.s3#IntelligentTieringId", "traits": { "smithy.api#documentation": "The ID used to identify the S3 Intelligent-Tiering configuration.
", "smithy.api#required": {} } }, "Filter": { "target": "com.amazonaws.s3#IntelligentTieringFilter", "traits": { "smithy.api#documentation": "Specifies a bucket filter. The configuration only includes objects that meet the filter's\n criteria.
" } }, "Status": { "target": "com.amazonaws.s3#IntelligentTieringStatus", "traits": { "smithy.api#documentation": "Specifies the status of the configuration.
", "smithy.api#required": {} } }, "Tierings": { "target": "com.amazonaws.s3#TieringList", "traits": { "smithy.api#documentation": "Specifies the S3 Intelligent-Tiering storage class tier of the configuration.
", "smithy.api#required": {}, "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Tiering" } } }, "traits": { "smithy.api#documentation": "Specifies the S3 Intelligent-Tiering configuration for an Amazon S3 bucket.
\nFor information about the S3 Intelligent-Tiering storage class, see Storage class for\n automatically optimizing frequently and infrequently accessed objects.
" } }, "com.amazonaws.s3#IntelligentTieringConfigurationList": { "type": "list", "member": { "target": "com.amazonaws.s3#IntelligentTieringConfiguration" } }, "com.amazonaws.s3#IntelligentTieringDays": { "type": "integer" }, "com.amazonaws.s3#IntelligentTieringFilter": { "type": "structure", "members": { "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "An object key name prefix that identifies the subset of objects to which the rule applies.
\nReplacement must be made for object keys containing special characters (such as carriage returns) when using \n XML requests. For more information, see \n XML related object key constraints.
\nA conjunction (logical AND) of predicates, which is used in evaluating a metrics filter. The\n operator must have at least two predicates, and an object must match all of the predicates in order for\n the filter to apply.
" } } }, "traits": { "smithy.api#documentation": "The Filter is used to identify objects that the S3 Intelligent-Tiering configuration\n applies to.
Object is archived and inaccessible until restored.
\nIf the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage class, the\n S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access tier, or the\n S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you must first restore a copy\n using RestoreObject. Otherwise, this operation returns an InvalidObjectState error. For\n information about restoring archived objects, see Restoring Archived Objects in the\n Amazon S3 User Guide.
You may receive this error in multiple cases. Depending on the reason for the error, you may receive\n one of the messages below:
\nCannot specify both a write offset value and user-defined object metadata for existing\n objects.
\nChecksum Type mismatch occurred, expected checksum Type: sha1, actual checksum Type:\n crc32c.
\nRequest body cannot be empty when 'write offset' is specified.
\nThe write offset value that you specified does not match the current object size.
", "smithy.api#error": "client", "smithy.api#httpError": 400 } }, "com.amazonaws.s3#InventoryConfiguration": { "type": "structure", "members": { "Destination": { "target": "com.amazonaws.s3#InventoryDestination", "traits": { "smithy.api#documentation": "Contains information about where to publish the inventory results.
", "smithy.api#required": {} } }, "IsEnabled": { "target": "com.amazonaws.s3#IsEnabled", "traits": { "smithy.api#documentation": "Specifies whether the inventory is enabled or disabled. If set to True, an inventory\n list is generated. If set to False, no inventory list is generated.
Specifies an inventory filter. The inventory only includes objects that meet the filter's\n criteria.
" } }, "Id": { "target": "com.amazonaws.s3#InventoryId", "traits": { "smithy.api#documentation": "The ID used to identify the inventory configuration.
", "smithy.api#required": {} } }, "IncludedObjectVersions": { "target": "com.amazonaws.s3#InventoryIncludedObjectVersions", "traits": { "smithy.api#documentation": "Object versions to include in the inventory list. If set to All, the list includes all\n the object versions, which adds the version-related fields VersionId,\n IsLatest, and DeleteMarker to the list. If set to Current, the\n list does not contain these version-related fields.
Contains the optional fields that are included in the inventory results.
" } }, "Schedule": { "target": "com.amazonaws.s3#InventorySchedule", "traits": { "smithy.api#documentation": "Specifies the schedule for generating inventory results.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Specifies the S3 Inventory configuration for an Amazon S3 bucket. For more information, see GET Bucket\n inventory in the Amazon S3 API Reference.
" } }, "com.amazonaws.s3#InventoryConfigurationList": { "type": "list", "member": { "target": "com.amazonaws.s3#InventoryConfiguration" } }, "com.amazonaws.s3#InventoryConfigurationState": { "type": "enum", "members": { "ENABLED": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ENABLED" } }, "DISABLED": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "DISABLED" } } } }, "com.amazonaws.s3#InventoryDestination": { "type": "structure", "members": { "S3BucketDestination": { "target": "com.amazonaws.s3#InventoryS3BucketDestination", "traits": { "smithy.api#documentation": "Contains the bucket name, file format, bucket owner (optional), and prefix (optional) where\n inventory results are published.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Specifies the S3 Inventory configuration for an Amazon S3 bucket.
" } }, "com.amazonaws.s3#InventoryEncryption": { "type": "structure", "members": { "SSES3": { "target": "com.amazonaws.s3#SSES3", "traits": { "smithy.api#documentation": "Specifies the use of SSE-S3 to encrypt delivered inventory reports.
", "smithy.api#xmlName": "SSE-S3" } }, "SSEKMS": { "target": "com.amazonaws.s3#SSEKMS", "traits": { "smithy.api#documentation": "Specifies the use of SSE-KMS to encrypt delivered inventory reports.
", "smithy.api#xmlName": "SSE-KMS" } } }, "traits": { "smithy.api#documentation": "Contains the type of server-side encryption used to encrypt the S3 Inventory results.
" } }, "com.amazonaws.s3#InventoryFilter": { "type": "structure", "members": { "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "The prefix that an object must have to be included in the inventory results.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Specifies an S3 Inventory filter. The inventory only includes objects that meet the filter's\n criteria.
" } }, "com.amazonaws.s3#InventoryFormat": { "type": "enum", "members": { "CSV": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "CSV" } }, "ORC": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ORC" } }, "Parquet": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Parquet" } } } }, "com.amazonaws.s3#InventoryFrequency": { "type": "enum", "members": { "Daily": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Daily" } }, "Weekly": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Weekly" } } } }, "com.amazonaws.s3#InventoryId": { "type": "string" }, "com.amazonaws.s3#InventoryIncludedObjectVersions": { "type": "enum", "members": { "All": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "All" } }, "Current": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Current" } } } }, "com.amazonaws.s3#InventoryOptionalField": { "type": "enum", "members": { "Size": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Size" } }, "LastModifiedDate": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "LastModifiedDate" } }, "StorageClass": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "StorageClass" } }, "ETag": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ETag" } }, "IsMultipartUploaded": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "IsMultipartUploaded" } }, "ReplicationStatus": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ReplicationStatus" } }, "EncryptionStatus": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "EncryptionStatus" } }, "ObjectLockRetainUntilDate": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ObjectLockRetainUntilDate" } }, "ObjectLockMode": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ObjectLockMode" } }, "ObjectLockLegalHoldStatus": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ObjectLockLegalHoldStatus" } }, "IntelligentTieringAccessTier": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "IntelligentTieringAccessTier" } }, "BucketKeyStatus": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "BucketKeyStatus" } }, "ChecksumAlgorithm": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ChecksumAlgorithm" } }, "ObjectAccessControlList": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ObjectAccessControlList" } }, "ObjectOwner": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ObjectOwner" } } } }, "com.amazonaws.s3#InventoryOptionalFields": { "type": "list", "member": { "target": "com.amazonaws.s3#InventoryOptionalField", "traits": { "smithy.api#xmlName": "Field" } } }, "com.amazonaws.s3#InventoryS3BucketDestination": { "type": "structure", "members": { "AccountId": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID that owns the destination S3 bucket. If no account ID is provided, the owner is not\n validated before exporting data.
\nAlthough this value is optional, we strongly recommend that you set it to help prevent problems\n if the destination bucket ownership changes.
\nThe Amazon Resource Name (ARN) of the bucket where inventory results will be published.
", "smithy.api#required": {} } }, "Format": { "target": "com.amazonaws.s3#InventoryFormat", "traits": { "smithy.api#documentation": "Specifies the output format of the inventory results.
", "smithy.api#required": {} } }, "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "The prefix that is prepended to all inventory results.
" } }, "Encryption": { "target": "com.amazonaws.s3#InventoryEncryption", "traits": { "smithy.api#documentation": "Contains the type of server-side encryption used to encrypt the inventory results.
" } } }, "traits": { "smithy.api#documentation": "Contains the bucket name, file format, bucket owner (optional), and prefix (optional) where\n S3 Inventory results are published.
" } }, "com.amazonaws.s3#InventorySchedule": { "type": "structure", "members": { "Frequency": { "target": "com.amazonaws.s3#InventoryFrequency", "traits": { "smithy.api#documentation": "Specifies how frequently inventory results are produced.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Specifies the schedule for generating S3 Inventory results.
" } }, "com.amazonaws.s3#InventoryTableConfiguration": { "type": "structure", "members": { "ConfigurationState": { "target": "com.amazonaws.s3#InventoryConfigurationState", "traits": { "smithy.api#documentation": "\n The configuration state of the inventory table, indicating whether the inventory table is enabled \n or disabled.\n
", "smithy.api#required": {} } }, "EncryptionConfiguration": { "target": "com.amazonaws.s3#MetadataTableEncryptionConfiguration", "traits": { "smithy.api#documentation": "\n The encryption configuration for the inventory table.\n
" } } }, "traits": { "smithy.api#documentation": "\n The inventory table configuration for an S3 Metadata configuration.\n
" } }, "com.amazonaws.s3#InventoryTableConfigurationResult": { "type": "structure", "members": { "ConfigurationState": { "target": "com.amazonaws.s3#InventoryConfigurationState", "traits": { "smithy.api#documentation": "\n The configuration state of the inventory table, indicating whether the inventory table is enabled \n or disabled.\n
", "smithy.api#required": {} } }, "TableStatus": { "target": "com.amazonaws.s3#MetadataTableStatus", "traits": { "smithy.api#documentation": "The status of the inventory table. The status values are:
\n\n CREATING - The inventory table is in the process of being created in the specified\n Amazon Web Services managed table bucket.
\n BACKFILLING - The inventory table is in the process of being backfilled. When \n you enable the inventory table for your metadata configuration, the table goes through a \n process known as backfilling, during which Amazon S3 scans your general purpose bucket to retrieve \n the initial metadata for all objects in the bucket. Depending on the number of objects in your \n bucket, this process can take several hours. When the backfilling process is finished, the \n status of your inventory table changes from BACKFILLING to ACTIVE. \n After backfilling is completed, updates to your objects are reflected in the inventory table \n within one hour.
\n ACTIVE - The inventory table has been created successfully, and records are being\n delivered to the table.
\n FAILED - Amazon S3 is unable to create the inventory table, or Amazon S3 is unable to deliver\n records.
\n The name of the inventory table.\n
" } }, "TableArn": { "target": "com.amazonaws.s3#S3TablesArn", "traits": { "smithy.api#documentation": "\n The Amazon Resource Name (ARN) for the inventory table.\n
" } } }, "traits": { "smithy.api#documentation": "\n The inventory table configuration for an S3 Metadata configuration.\n
" } }, "com.amazonaws.s3#InventoryTableConfigurationUpdates": { "type": "structure", "members": { "ConfigurationState": { "target": "com.amazonaws.s3#InventoryConfigurationState", "traits": { "smithy.api#documentation": "\n The configuration state of the inventory table, indicating whether the inventory table is enabled \n or disabled.\n
", "smithy.api#required": {} } }, "EncryptionConfiguration": { "target": "com.amazonaws.s3#MetadataTableEncryptionConfiguration", "traits": { "smithy.api#documentation": "\n The encryption configuration for the inventory table.\n
" } } }, "traits": { "smithy.api#documentation": "\n The specified updates to the S3 Metadata inventory table configuration.\n
" } }, "com.amazonaws.s3#IsEnabled": { "type": "boolean" }, "com.amazonaws.s3#IsLatest": { "type": "boolean" }, "com.amazonaws.s3#IsPublic": { "type": "boolean" }, "com.amazonaws.s3#IsRestoreInProgress": { "type": "boolean" }, "com.amazonaws.s3#IsTruncated": { "type": "boolean" }, "com.amazonaws.s3#JSONInput": { "type": "structure", "members": { "Type": { "target": "com.amazonaws.s3#JSONType", "traits": { "smithy.api#documentation": "The type of JSON. Valid values: Document, Lines.
" } } }, "traits": { "smithy.api#documentation": "Specifies JSON as object's input serialization format.
" } }, "com.amazonaws.s3#JSONOutput": { "type": "structure", "members": { "RecordDelimiter": { "target": "com.amazonaws.s3#RecordDelimiter", "traits": { "smithy.api#documentation": "The value used to separate individual records in the output. If no value is specified, Amazon S3 uses a\n newline character ('\\n').
" } } }, "traits": { "smithy.api#documentation": "Specifies JSON as request's output serialization format.
" } }, "com.amazonaws.s3#JSONType": { "type": "enum", "members": { "DOCUMENT": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "DOCUMENT" } }, "LINES": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "LINES" } } } }, "com.amazonaws.s3#JournalTableConfiguration": { "type": "structure", "members": { "RecordExpiration": { "target": "com.amazonaws.s3#RecordExpiration", "traits": { "smithy.api#documentation": "\n The journal table record expiration settings for the journal table.\n
", "smithy.api#required": {} } }, "EncryptionConfiguration": { "target": "com.amazonaws.s3#MetadataTableEncryptionConfiguration", "traits": { "smithy.api#documentation": "\n The encryption configuration for the journal table.\n
" } } }, "traits": { "smithy.api#documentation": "\n The journal table configuration for an S3 Metadata configuration.\n
" } }, "com.amazonaws.s3#JournalTableConfigurationResult": { "type": "structure", "members": { "TableStatus": { "target": "com.amazonaws.s3#MetadataTableStatus", "traits": { "smithy.api#documentation": "The status of the journal table. The status values are:
\n\n CREATING - The journal table is in the process of being created in the specified\n table bucket.
\n ACTIVE - The journal table has been created successfully, and records are being\n delivered to the table.
\n FAILED - Amazon S3 is unable to create the journal table, or Amazon S3 is unable to deliver\n records.
\n The name of the journal table.\n
", "smithy.api#required": {} } }, "TableArn": { "target": "com.amazonaws.s3#S3TablesArn", "traits": { "smithy.api#documentation": "\n The Amazon Resource Name (ARN) for the journal table.\n
" } }, "RecordExpiration": { "target": "com.amazonaws.s3#RecordExpiration", "traits": { "smithy.api#documentation": "\n The journal table record expiration settings for the journal table.\n
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "\n The journal table configuration for the S3 Metadata configuration.\n
" } }, "com.amazonaws.s3#JournalTableConfigurationUpdates": { "type": "structure", "members": { "RecordExpiration": { "target": "com.amazonaws.s3#RecordExpiration", "traits": { "smithy.api#documentation": "\n The journal table record expiration settings for the journal table.\n
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "\n The specified updates to the S3 Metadata journal table configuration.\n
" } }, "com.amazonaws.s3#KMSContext": { "type": "string" }, "com.amazonaws.s3#KeyCount": { "type": "integer" }, "com.amazonaws.s3#KeyMarker": { "type": "string" }, "com.amazonaws.s3#KeyPrefixEquals": { "type": "string" }, "com.amazonaws.s3#KmsKeyArn": { "type": "string" }, "com.amazonaws.s3#LambdaFunctionArn": { "type": "string" }, "com.amazonaws.s3#LambdaFunctionConfiguration": { "type": "structure", "members": { "Id": { "target": "com.amazonaws.s3#NotificationId" }, "LambdaFunctionArn": { "target": "com.amazonaws.s3#LambdaFunctionArn", "traits": { "smithy.api#documentation": "The Amazon Resource Name (ARN) of the Lambda function that Amazon S3 invokes when the specified event\n type occurs.
", "smithy.api#required": {}, "smithy.api#xmlName": "CloudFunction" } }, "Events": { "target": "com.amazonaws.s3#EventList", "traits": { "smithy.api#documentation": "The Amazon S3 bucket event for which to invoke the Lambda function. For more information, see Supported Event Types in\n the Amazon S3 User Guide.
", "smithy.api#required": {}, "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Event" } }, "Filter": { "target": "com.amazonaws.s3#NotificationConfigurationFilter" } }, "traits": { "smithy.api#documentation": "A container for specifying the configuration for Lambda notifications.
" } }, "com.amazonaws.s3#LambdaFunctionConfigurationList": { "type": "list", "member": { "target": "com.amazonaws.s3#LambdaFunctionConfiguration" } }, "com.amazonaws.s3#LastModified": { "type": "timestamp" }, "com.amazonaws.s3#LastModifiedTime": { "type": "timestamp", "traits": { "smithy.api#timestampFormat": "http-date" } }, "com.amazonaws.s3#LifecycleExpiration": { "type": "structure", "members": { "Date": { "target": "com.amazonaws.s3#Date", "traits": { "smithy.api#documentation": "Indicates at what date the object is to be moved or deleted. The date value must conform to the ISO\n 8601 format. The time is always midnight UTC.
\nThis parameter applies to general purpose buckets only. It is not supported for directory bucket\n lifecycle configurations.
\nIndicates the lifetime, in days, of the objects that are subject to the rule. The value must be a\n non-zero positive integer.
" } }, "ExpiredObjectDeleteMarker": { "target": "com.amazonaws.s3#ExpiredObjectDeleteMarker", "traits": { "smithy.api#documentation": "Indicates whether Amazon S3 will remove a delete marker with no noncurrent versions. If set to true, the\n delete marker will be expired; if set to false the policy takes no action. This cannot be specified with\n Days or Date in a Lifecycle Expiration Policy.
\nThis parameter applies to general purpose buckets only. It is not supported for directory bucket\n lifecycle configurations.
\nContainer for the expiration for the lifecycle of the object.
\nFor more information see, Managing your storage lifecycle in\n the Amazon S3 User Guide.
" } }, "com.amazonaws.s3#LifecycleRule": { "type": "structure", "members": { "Expiration": { "target": "com.amazonaws.s3#LifecycleExpiration", "traits": { "smithy.api#documentation": "Specifies the expiration for the lifecycle of the object in the form of date, days and, whether the\n object has a delete marker.
" } }, "ID": { "target": "com.amazonaws.s3#ID", "traits": { "smithy.api#documentation": "Unique identifier for the rule. The value cannot be longer than 255 characters.
" } }, "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#deprecated": {}, "smithy.api#documentation": "Prefix identifying one or more objects to which the rule applies. This is no\n longer used; use Filter instead.
Replacement must be made for object keys containing special characters (such as carriage returns) when using \n XML requests. For more information, see \n XML related object key constraints.
\nThe Filter is used to identify objects that a Lifecycle Rule applies to. A\n Filter must have exactly one of Prefix, Tag,\n ObjectSizeGreaterThan, ObjectSizeLessThan, or And specified.\n Filter is required if the LifecycleRule does not contain a\n Prefix element.
For more information about Tag filters, see Adding filters to Lifecycle rules\n in the Amazon S3 User Guide.
\n Tag filters are not supported for directory buckets.
If 'Enabled', the rule is currently being applied. If 'Disabled', the rule is not currently being\n applied.
", "smithy.api#required": {} } }, "Transitions": { "target": "com.amazonaws.s3#TransitionList", "traits": { "smithy.api#documentation": "Specifies when an Amazon S3 object transitions to a specified storage class.
\nThis parameter applies to general purpose buckets only. It is not supported for directory bucket\n lifecycle configurations.
\nSpecifies the transition rule for the lifecycle rule that describes when noncurrent objects\n transition to a specific storage class. If your bucket is versioning-enabled (or versioning is\n suspended), you can set this action to request that Amazon S3 transition noncurrent object versions to a\n specific storage class at a set period in the object's lifetime.
\nThis parameter applies to general purpose buckets only. It is not supported for directory bucket\n lifecycle configurations.
\nA lifecycle rule for individual objects in an Amazon S3 bucket.
\nFor more information see, Managing your storage lifecycle in\n the Amazon S3 User Guide.
" } }, "com.amazonaws.s3#LifecycleRuleAndOperator": { "type": "structure", "members": { "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "Prefix identifying one or more objects to which the rule applies.
" } }, "Tags": { "target": "com.amazonaws.s3#TagSet", "traits": { "smithy.api#documentation": "All of these tags must exist in the object's tag set in order for the rule to apply.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Tag" } }, "ObjectSizeGreaterThan": { "target": "com.amazonaws.s3#ObjectSizeGreaterThanBytes", "traits": { "smithy.api#documentation": "Minimum object size to which the rule applies.
" } }, "ObjectSizeLessThan": { "target": "com.amazonaws.s3#ObjectSizeLessThanBytes", "traits": { "smithy.api#documentation": "Maximum object size to which the rule applies.
" } } }, "traits": { "smithy.api#documentation": "This is used in a Lifecycle Rule Filter to apply a logical AND to two or more predicates. The\n Lifecycle Rule will apply to any object matching all of the predicates configured inside the And\n operator.
" } }, "com.amazonaws.s3#LifecycleRuleFilter": { "type": "structure", "members": { "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "Prefix identifying one or more objects to which the rule applies.
\nReplacement must be made for object keys containing special characters (such as carriage returns) when using \n XML requests. For more information, see \n XML related object key constraints.
\nThis tag must exist in the object's tag set in order for the rule to apply.
\nThis parameter applies to general purpose buckets only. It is not supported for directory bucket\n lifecycle configurations.
\nMinimum object size to which the rule applies.
" } }, "ObjectSizeLessThan": { "target": "com.amazonaws.s3#ObjectSizeLessThanBytes", "traits": { "smithy.api#documentation": "Maximum object size to which the rule applies.
" } }, "And": { "target": "com.amazonaws.s3#LifecycleRuleAndOperator" } }, "traits": { "smithy.api#documentation": "The Filter is used to identify objects that a Lifecycle Rule applies to. A\n Filter can have exactly one of Prefix, Tag,\n ObjectSizeGreaterThan, ObjectSizeLessThan, or And specified. If\n the Filter element is left empty, the Lifecycle Rule applies to all objects in the\n bucket.
This operation is not supported for directory buckets.
\nLists the analytics configurations for the bucket. You can have up to 1,000 analytics configurations\n per bucket.
\nThis action supports list pagination and does not return more than 100 configurations at a time. You\n should always check the IsTruncated element in the response. If there are no more\n configurations to list, IsTruncated is set to false. If there are more configurations to\n list, IsTruncated is set to true, and there will be a value in\n NextContinuationToken. You use the NextContinuationToken value to continue\n the pagination of the list by passing the value in continuation-token in the request to GET\n the next page.
To use this operation, you must have permissions to perform the\n s3:GetAnalyticsConfiguration action. The bucket owner has this permission by default. The\n 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\n Resources.
For information about Amazon S3 analytics feature, see Amazon S3 Analytics \u2013 Storage Class\n Analysis.
\nThe following operations are related to ListBucketAnalyticsConfigurations:
Indicates whether the returned list of analytics configurations is complete. A value of true\n indicates that the list is not complete and the NextContinuationToken will be provided for a subsequent\n request.
" } }, "ContinuationToken": { "target": "com.amazonaws.s3#Token", "traits": { "smithy.api#documentation": "The marker that is used as a starting point for this analytics configuration list response. This\n value is present if it was sent in the request.
" } }, "NextContinuationToken": { "target": "com.amazonaws.s3#NextToken", "traits": { "smithy.api#documentation": "\n NextContinuationToken is sent when isTruncated is true, which indicates\n that there are more analytics configurations to list. The next request must include this\n NextContinuationToken. The token is obfuscated and is not a usable value.
The list of analytics configurations for a bucket.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "AnalyticsConfiguration" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "ListBucketAnalyticsConfigurationResult" } }, "com.amazonaws.s3#ListBucketAnalyticsConfigurationsRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket from which analytics configurations are retrieved.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContinuationToken": { "target": "com.amazonaws.s3#Token", "traits": { "smithy.api#documentation": "The ContinuationToken that represents a placeholder from where this request should\n begin.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nLists the S3 Intelligent-Tiering configuration from the specified bucket.
\nThe S3 Intelligent-Tiering storage class is designed to optimize storage costs by automatically moving data to the most cost-effective storage access tier, without performance impact or operational overhead. S3 Intelligent-Tiering delivers automatic cost savings in three low latency and high throughput access tiers. To get the lowest storage cost on data that can be accessed in minutes to hours, you can choose to activate additional archiving capabilities.
\nThe S3 Intelligent-Tiering storage class is the ideal storage class for data with unknown, changing, or unpredictable access patterns, independent of object size or retention period. If the size of an object is less than 128 KB, it is not monitored and not eligible for auto-tiering. Smaller objects can be stored, but they are always charged at the Frequent Access tier rates in the S3 Intelligent-Tiering storage class.
\nFor more information, see Storage class for automatically optimizing frequently and infrequently accessed objects.
\nOperations related to ListBucketIntelligentTieringConfigurations include:
Indicates whether the returned list of analytics configurations is complete. A value of\n true indicates that the list is not complete and the NextContinuationToken\n will be provided for a subsequent request.
The ContinuationToken that represents a placeholder from where this request should\n begin.
The marker used to continue this inventory configuration listing. Use the\n NextContinuationToken from this response to continue the listing in a subsequent request.\n The continuation token is an opaque value that Amazon S3 understands.
The list of S3 Intelligent-Tiering configurations for a bucket.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "IntelligentTieringConfiguration" } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#ListBucketIntelligentTieringConfigurationsRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the Amazon S3 bucket whose configuration you want to modify or retrieve.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContinuationToken": { "target": "com.amazonaws.s3#Token", "traits": { "smithy.api#documentation": "The ContinuationToken that represents a placeholder from where this request should\n begin.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nReturns a list of S3 Inventory configurations for the bucket. You can have up to 1,000 analytics\n configurations per bucket.
\nThis action supports list pagination and does not return more than 100 configurations at a time.\n Always check the IsTruncated element in the response. If there are no more configurations\n to list, IsTruncated is set to false. If there are more configurations to list,\n IsTruncated is set to true, and there is a value in NextContinuationToken.\n You use the NextContinuationToken value to continue the pagination of the list by passing\n the value in continuation-token in the request to GET the next page.
To use this operation, you must have permissions to perform the\n s3:GetInventoryConfiguration action. The bucket owner has this permission by default. The\n 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\n Resources.
For information about the Amazon S3 inventory feature, see Amazon S3 Inventory\n
\nThe following operations are related to ListBucketInventoryConfigurations:
If sent in the request, the marker that is used as a starting point for this inventory configuration\n list response.
" } }, "InventoryConfigurationList": { "target": "com.amazonaws.s3#InventoryConfigurationList", "traits": { "smithy.api#documentation": "The list of inventory configurations for a bucket.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "InventoryConfiguration" } }, "IsTruncated": { "target": "com.amazonaws.s3#IsTruncated", "traits": { "smithy.api#documentation": "Tells whether the returned list of inventory configurations is complete. A value of true indicates\n that the list is not complete and the NextContinuationToken is provided for a subsequent request.
" } }, "NextContinuationToken": { "target": "com.amazonaws.s3#NextToken", "traits": { "smithy.api#documentation": "The marker used to continue this inventory configuration listing. Use the\n NextContinuationToken from this response to continue the listing in a subsequent request.\n The continuation token is an opaque value that Amazon S3 understands.
The name of the bucket containing the inventory configurations to retrieve.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContinuationToken": { "target": "com.amazonaws.s3#Token", "traits": { "smithy.api#documentation": "The marker used to continue an inventory configuration listing that has been truncated. Use the\n NextContinuationToken from a previously truncated list response to continue the listing.\n The continuation token is an opaque value that Amazon S3 understands.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nLists the metrics configurations for the bucket. The metrics configurations are only for the request\n metrics of the bucket and do not provide information on daily storage metrics. You can have up to 1,000\n configurations per bucket.
\nThis action supports list pagination and does not return more than 100 configurations at a time.\n Always check the IsTruncated element in the response. If there are no more configurations\n to list, IsTruncated is set to false. If there are more configurations to list,\n IsTruncated is set to true, and there is a value in NextContinuationToken.\n You use the NextContinuationToken value to continue the pagination of the list by passing\n the value in continuation-token in the request to GET the next page.
To use this operation, you must have permissions to perform the\n s3:GetMetricsConfiguration action. The bucket owner has this permission by default. The\n 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\n Resources.
For more information about metrics configurations and CloudWatch request metrics, see Monitoring Metrics with\n Amazon CloudWatch.
\nThe following operations are related to ListBucketMetricsConfigurations:
Indicates whether the returned list of metrics configurations is complete. A value of true indicates\n that the list is not complete and the NextContinuationToken will be provided for a subsequent\n request.
" } }, "ContinuationToken": { "target": "com.amazonaws.s3#Token", "traits": { "smithy.api#documentation": "The marker that is used as a starting point for this metrics configuration list response. This value\n is present if it was sent in the request.
" } }, "NextContinuationToken": { "target": "com.amazonaws.s3#NextToken", "traits": { "smithy.api#documentation": "The marker used to continue a metrics configuration listing that has been truncated. Use the\n NextContinuationToken from a previously truncated list response to continue the listing.\n The continuation token is an opaque value that Amazon S3 understands.
The list of metrics configurations for a bucket.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "MetricsConfiguration" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "ListMetricsConfigurationsResult" } }, "com.amazonaws.s3#ListBucketMetricsConfigurationsRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket containing the metrics configurations to retrieve.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContinuationToken": { "target": "com.amazonaws.s3#Token", "traits": { "smithy.api#documentation": "The marker that is used to continue a metrics configuration listing that has been truncated. Use the\n NextContinuationToken from a previously truncated list response to continue the listing.\n The continuation token is an opaque value that Amazon S3 understands.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
End of support notice: Beginning October 1, 2025, Amazon S3 will stop returning DisplayName. Update your applications to use canonical IDs (unique identifier for \n Amazon Web Services accounts), Amazon Web Services account ID (12 digit identifier) or IAM ARNs (full resource naming) as a direct replacement of DisplayName.\n
This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nThis operation is not supported for directory buckets.
\nReturns a list of all buckets owned by the authenticated sender of the request. To grant IAM\n permission to use this operation, you must add the s3:ListAllMyBuckets policy action.
For information about Amazon S3 buckets, see Creating, configuring, and working with Amazon S3\n buckets.
\nWe strongly recommend using only paginated ListBuckets requests. Unpaginated\n ListBuckets requests are only supported for Amazon Web Services accounts set to the default general\n purpose bucket quota of 10,000. If you have an approved general purpose bucket quota above 10,000, you\n must send paginated ListBuckets requests to list your account\u2019s buckets. All unpaginated\n ListBuckets requests will be rejected for Amazon Web Services accounts with a general purpose bucket\n quota greater than 10,000.
The list of buckets owned by the requester.
" } }, "Owner": { "target": "com.amazonaws.s3#Owner", "traits": { "smithy.api#documentation": "The owner of the buckets listed.
" } }, "ContinuationToken": { "target": "com.amazonaws.s3#NextToken", "traits": { "smithy.api#documentation": "\n ContinuationToken is included in the response when there are more buckets that can be\n listed with pagination. The next ListBuckets request to Amazon S3 can be continued with this\n ContinuationToken. ContinuationToken is obfuscated and is not a real\n bucket.
If Prefix was sent with the request, it is included in the response.
All bucket names in the response begin with the specified bucket name prefix.
" } } }, "traits": { "smithy.api#output": {}, "smithy.api#xmlName": "ListAllMyBucketsResult" } }, "com.amazonaws.s3#ListBucketsRequest": { "type": "structure", "members": { "MaxBuckets": { "target": "com.amazonaws.s3#MaxBuckets", "traits": { "smithy.api#documentation": "Maximum number of buckets to be returned in response. When the number is more than the count of\n buckets that are owned by an Amazon Web Services account, return all the buckets in response.
", "smithy.api#httpQuery": "max-buckets" } }, "ContinuationToken": { "target": "com.amazonaws.s3#Token", "traits": { "smithy.api#documentation": "\n ContinuationToken indicates to Amazon S3 that the list is being continued on this bucket\n with a token. ContinuationToken is obfuscated and is not a real key. You can use this\n ContinuationToken for pagination of the list results.
Length Constraints: Minimum length of 0. Maximum length of 1024.
\nRequired: No.
\nIf you specify the bucket-region, prefix, or\n continuation-token query parameters without using max-buckets to set the\n maximum number of buckets returned in the response, Amazon S3 applies a default page size of 10,000 and\n provides a continuation token if there are more buckets.
Limits the response to bucket names that begin with the specified bucket name prefix.
", "smithy.api#httpQuery": "prefix" } }, "BucketRegion": { "target": "com.amazonaws.s3#BucketRegion", "traits": { "smithy.api#documentation": "Limits the response to buckets that are located in the specified Amazon Web Services Region. The Amazon Web Services Region must\n be expressed according to the Amazon Web Services Region code, such as us-west-2 for the US West (Oregon)\n Region. For a list of the valid values for all of the Amazon Web Services Regions, see Regions and Endpoints.
Requests made to a Regional endpoint that is different from the bucket-region\n parameter are not supported. For example, if you want to limit the response to your buckets in Region\n us-west-2, the request must be made to an endpoint in Region\n us-west-2.
Returns a list of all Amazon S3 directory buckets owned by the authenticated sender of the request. For\n more information about directory buckets, see Directory buckets in the\n Amazon S3 User Guide.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. \nFor more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
You must have the s3express:ListAllMyDirectoryBuckets permission in\n an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.\n For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
\n Directory buckets - The HTTP Host header syntax is\n s3express-control.region.amazonaws.com.
The BucketRegion response element is not part of the\n ListDirectoryBuckets Response Syntax.
The list of buckets owned by the requester.
" } }, "ContinuationToken": { "target": "com.amazonaws.s3#DirectoryBucketToken", "traits": { "smithy.api#documentation": "If ContinuationToken was sent with the request, it is included in the response. You can\n use the returned ContinuationToken for pagination of the list response.
\n ContinuationToken indicates to Amazon S3 that the list is being continued on buckets in this\n account with a token. ContinuationToken is obfuscated and is not a real bucket name. You\n can use this ContinuationToken for the pagination of the list results.
Maximum number of buckets to be returned in response. When the number is more than the count of\n buckets that are owned by an Amazon Web Services account, return all the buckets in response.
", "smithy.api#httpQuery": "max-directory-buckets" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#ListMultipartUploads": { "type": "operation", "input": { "target": "com.amazonaws.s3#ListMultipartUploadsRequest" }, "output": { "target": "com.amazonaws.s3#ListMultipartUploadsOutput" }, "traits": { "smithy.api#documentation": "End of support notice: Beginning October 1, 2025, Amazon S3 will stop returning DisplayName. Update your applications to use canonical IDs (unique identifier for \n Amazon Web Services accounts), Amazon Web Services account ID (12 digit identifier) or IAM ARNs (full resource naming) as a direct replacement of DisplayName.\n
This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nThis operation lists in-progress multipart uploads in a bucket. An in-progress multipart upload is a\n multipart upload that has been initiated by the CreateMultipartUpload request, but has not\n yet been completed or aborted.
\n Directory buckets - If multipart uploads in a\n directory bucket are in progress, you can't delete the bucket until all the in-progress multipart\n uploads are aborted or completed. To delete these in-progress multipart uploads, use the\n ListMultipartUploads operation to list the in-progress multipart uploads in the bucket\n and use the AbortMultipartUpload operation to abort all the in-progress multipart\n uploads.
The ListMultipartUploads operation returns a maximum of 1,000 multipart uploads in the\n response. The limit of 1,000 multipart uploads is also the default value. You can further limit the\n number of uploads in a response by specifying the max-uploads request parameter. If there\n are more than 1,000 multipart uploads that satisfy your ListMultipartUploads request, the\n response returns an IsTruncated element with the value of true, a\n NextKeyMarker element, and a NextUploadIdMarker element. To list the\n remaining multipart uploads, you need to make subsequent ListMultipartUploads requests. In\n these requests, include two query parameters: key-marker and upload-id-marker.\n Set the value of key-marker to the NextKeyMarker value from the previous\n response. Similarly, set the value of upload-id-marker to the\n NextUploadIdMarker value from the previous response.
\n Directory buckets - The upload-id-marker\n element and the NextUploadIdMarker element aren't supported by directory buckets. To\n list the additional multipart uploads, you only need to set the value of key-marker to\n the NextKeyMarker value from the previous response.
For more information about multipart uploads, see Uploading Objects Using Multipart Upload in\n the Amazon S3 User Guide.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n General purpose bucket permissions - For information\n about permissions required to use the multipart upload API, see Multipart Upload and Permissions in\n the Amazon S3 User Guide.
\n\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
\n General purpose bucket - In the\n ListMultipartUploads response, the multipart uploads are sorted based on two\n criteria:
Key-based sorting - Multipart uploads are initially sorted in ascending order\n based on their object keys.
\nTime-based sorting - For uploads that share the same object key, they are\n further sorted in ascending order based on the upload initiation time. Among uploads with\n the same key, the one that was initiated first will appear before the ones that were\n initiated later.
\n\n Directory bucket - In the\n ListMultipartUploads response, the multipart uploads aren't sorted\n lexicographically based on the object keys.\n \n
\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following operations are related to ListMultipartUploads:
\n UploadPart\n
\n\n ListParts\n
\n\n AbortMultipartUpload\n
\nThe name of the bucket to which the multipart upload was initiated. Does not return the access point ARN or\n access point alias if used.
" } }, "KeyMarker": { "target": "com.amazonaws.s3#KeyMarker", "traits": { "smithy.api#documentation": "The key at or after which the listing began.
" } }, "UploadIdMarker": { "target": "com.amazonaws.s3#UploadIdMarker", "traits": { "smithy.api#documentation": "Together with key-marker, specifies the multipart upload after which listing should begin. If\n key-marker is not specified, the upload-id-marker parameter is ignored. Otherwise, any multipart uploads\n for a key equal to the key-marker might be included in the list only if they have an upload ID\n lexicographically greater than the specified upload-id-marker.
This functionality is not supported for directory buckets.
\nWhen a list is truncated, this element specifies the value that should be used for the key-marker\n request parameter in a subsequent request.
" } }, "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "When a prefix is provided in the request, this field contains the specified prefix. The result\n contains only keys starting with the specified prefix.
\n\n Directory buckets - For directory buckets, only prefixes that end in a delimiter (/) are supported.
Contains the delimiter you specified in the request. If you don't specify a delimiter in your\n request, this element is absent from the response.
\n\n Directory buckets - For directory buckets, / is the only supported delimiter.
When a list is truncated, this element specifies the value that should be used for the\n upload-id-marker request parameter in a subsequent request.
This functionality is not supported for directory buckets.
\nMaximum number of multipart uploads that could have been included in the response.
" } }, "IsTruncated": { "target": "com.amazonaws.s3#IsTruncated", "traits": { "smithy.api#documentation": "Indicates whether the returned list of multipart uploads is truncated. A value of true indicates\n that the list was truncated. The list can be truncated if the number of multipart uploads exceeds the\n limit allowed or specified by max uploads.
" } }, "Uploads": { "target": "com.amazonaws.s3#MultipartUploadList", "traits": { "smithy.api#documentation": "Container for elements related to a particular multipart upload. A response can contain zero or more\n Upload elements.
If you specify a delimiter in the request, then the result returns each distinct key prefix\n containing the delimiter in a CommonPrefixes element. The distinct key prefixes are\n returned in the Prefix child element.
\n Directory buckets - For directory buckets, only prefixes that end in a delimiter (/) are supported.
Encoding type used by Amazon S3 to encode object keys in the response.
\nIf you specify the encoding-type request parameter, Amazon S3 includes this element in the\n response, and returns encoded key name values in the following response elements:
\n Delimiter, KeyMarker, Prefix, NextKeyMarker,\n Key.
The name of the bucket to which the multipart upload was initiated.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Character you use to group keys.
\nAll keys that contain the same string between the prefix, if specified, and the first occurrence of\n the delimiter after the prefix are grouped under a single result element, CommonPrefixes.\n If you don't specify the prefix parameter, then the substring starts at the beginning of the key. The\n keys that are grouped under CommonPrefixes result element are not returned elsewhere in the\n response.
\n CommonPrefixes is filtered out from results if it is not lexicographically greater than\n the key-marker.
\n Directory buckets - For directory buckets, / is the only supported delimiter.
Specifies the multipart upload after which listing should begin.
\n\n General purpose buckets - For general purpose buckets,\n key-marker is an object key. Together with upload-id-marker, this\n parameter specifies the multipart upload after which listing should begin.
If upload-id-marker is not specified, only the keys lexicographically greater\n than the specified key-marker will be included in the list.
If upload-id-marker is specified, any multipart uploads for a key equal to the\n key-marker might also be included, provided those multipart uploads have upload IDs\n lexicographically greater than the specified upload-id-marker.
\n Directory buckets - For directory buckets,\n key-marker is obfuscated and isn't a real object key. The\n upload-id-marker parameter isn't supported by directory buckets. To list the\n additional multipart uploads, you only need to set the value of key-marker to the\n NextKeyMarker value from the previous response.
In the ListMultipartUploads response, the multipart uploads aren't sorted\n lexicographically based on the object keys.\n \n
Sets the maximum number of multipart uploads, from 1 to 1,000, to return in the response body. 1,000\n is the maximum number of uploads that can be returned in a response.
", "smithy.api#httpQuery": "max-uploads" } }, "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "Lists in-progress uploads only for those keys that begin with the specified prefix. You can use\n prefixes to separate a bucket into different grouping of keys. (You can think of using\n prefix to make groups in the same way that you'd use a folder in a file system.)
\n Directory buckets - For directory buckets, only prefixes that end in a delimiter (/) are supported.
Together with key-marker, specifies the multipart upload after which listing should begin. If\n key-marker is not specified, the upload-id-marker parameter is ignored. Otherwise, any multipart uploads\n for a key equal to the key-marker might be included in the list only if they have an upload ID\n lexicographically greater than the specified upload-id-marker.
This functionality is not supported for directory buckets.
\nThe account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
End of support notice: Beginning October 1, 2025, Amazon S3 will stop returning DisplayName. Update your applications to use canonical IDs (unique identifier for \n Amazon Web Services accounts), Amazon Web Services account ID (12 digit identifier) or IAM ARNs (full resource naming) as a direct replacement of DisplayName.\n
This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nThis operation is not supported for directory buckets.
\nReturns metadata about all versions of the objects in a bucket. You can also use request parameters\n as selection criteria to return metadata about a subset of all the object versions.
\n To use this operation, you must have permission to perform the s3:ListBucketVersions\n action. Be aware of the name difference.
A 200 OK response can contain valid or invalid XML. Make sure to design your\n application to parse the contents of the response and handle it appropriately.
To use this operation, you must have READ access to the bucket.
\nThe following operations are related to ListObjectVersions:
\n ListObjectsV2\n
\n\n GetObject\n
\n\n PutObject\n
\n\n DeleteObject\n
\nA flag that indicates whether Amazon S3 returned all of the results that satisfied the search criteria.\n If your results were truncated, you can make a follow-up paginated request by using the\n NextKeyMarker and NextVersionIdMarker response parameters as a starting\n place in another request to return the rest of the results.
Marks the last key returned in a truncated response.
" } }, "VersionIdMarker": { "target": "com.amazonaws.s3#VersionIdMarker", "traits": { "smithy.api#documentation": "Marks the last version of the key returned in a truncated response.
" } }, "NextKeyMarker": { "target": "com.amazonaws.s3#NextKeyMarker", "traits": { "smithy.api#documentation": "When the number of responses exceeds the value of MaxKeys, NextKeyMarker\n specifies the first key not returned that satisfies the search criteria. Use this value for the\n key-marker request parameter in a subsequent request.
When the number of responses exceeds the value of MaxKeys,\n NextVersionIdMarker specifies the first object version not returned that satisfies the\n search criteria. Use this value for the version-id-marker request parameter in a subsequent\n request.
Container for version information.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Version" } }, "DeleteMarkers": { "target": "com.amazonaws.s3#DeleteMarkers", "traits": { "smithy.api#documentation": "Container for an object that is a delete marker. To learn more about delete markers, see Working with delete\n markers.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "DeleteMarker" } }, "Name": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name.
" } }, "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "Selects objects that start with the value supplied by this parameter.
" } }, "Delimiter": { "target": "com.amazonaws.s3#Delimiter", "traits": { "smithy.api#documentation": "The delimiter grouping the included keys. A delimiter is a character that you specify to group keys.\n All keys that contain the same string between the prefix and the first occurrence of the delimiter are\n grouped under a single result element in CommonPrefixes. These groups are counted as one\n result against the max-keys limitation. These keys are not returned elsewhere in the\n response.
Specifies the maximum number of objects to return.
" } }, "CommonPrefixes": { "target": "com.amazonaws.s3#CommonPrefixList", "traits": { "smithy.api#documentation": "All of the keys rolled up into a common prefix count as a single return when calculating the number\n of returns.
", "smithy.api#xmlFlattened": {} } }, "EncodingType": { "target": "com.amazonaws.s3#EncodingType", "traits": { "smithy.api#documentation": "Encoding type used by Amazon S3 to encode object key names in the XML response.
\nIf you specify the encoding-type request parameter, Amazon S3 includes this element in the\n response, and returns encoded key name values in the following response elements:
\n KeyMarker, NextKeyMarker, Prefix, Key, and Delimiter.
The bucket name that contains the objects.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Delimiter": { "target": "com.amazonaws.s3#Delimiter", "traits": { "smithy.api#documentation": "A delimiter is a character that you specify to group keys. All keys that contain the same string\n between the prefix and the first occurrence of the delimiter are grouped under a single\n result element in CommonPrefixes. These groups are counted as one result against the\n max-keys limitation. These keys are not returned elsewhere in the response.
\n CommonPrefixes is filtered out from results if it is not lexicographically greater than\n the key-marker.
Specifies the key to start with when listing objects in a bucket.
", "smithy.api#httpQuery": "key-marker" } }, "MaxKeys": { "target": "com.amazonaws.s3#MaxKeys", "traits": { "smithy.api#documentation": "Sets the maximum number of keys returned in the response. By default, the action returns up to 1,000\n key names. The response might contain fewer keys but will never contain more. If additional keys satisfy\n the search criteria, but were not returned because max-keys was exceeded, the response\n contains key-marker and version-id-marker.
Use this parameter to select only those keys that begin with the specified prefix. You can use\n prefixes to separate a bucket into different groupings of keys. (You can think of using\n prefix to make groups in the same way that you'd use a folder in a file system.) You can\n use prefix with delimiter to roll up numerous objects into a single result\n under CommonPrefixes.
Specifies the object version you want to start listing from.
", "smithy.api#httpQuery": "version-id-marker" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Specifies the optional fields that you want returned in the response. Fields that you do not specify\n are not returned.
", "smithy.api#httpHeader": "x-amz-optional-object-attributes" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#ListObjects": { "type": "operation", "input": { "target": "com.amazonaws.s3#ListObjectsRequest" }, "output": { "target": "com.amazonaws.s3#ListObjectsOutput" }, "errors": [ { "target": "com.amazonaws.s3#NoSuchBucket" } ], "traits": { "smithy.api#documentation": "End of support notice: Beginning October 1, 2025, Amazon S3 will stop returning DisplayName. Update your applications to use canonical IDs (unique identifier for \n Amazon Web Services accounts), Amazon Web Services account ID (12 digit identifier) or IAM ARNs (full resource naming) as a direct replacement of DisplayName.\n
This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nThis operation is not supported for directory buckets.
\nReturns some or all (up to 1,000) of the objects in a bucket. You can use the request parameters as\n selection criteria to return a subset of the objects in a bucket. A 200 OK response can contain valid or\n invalid XML. Be sure to design your application to parse the contents of the response and handle it\n appropriately.
\nThis action has been revised. We recommend that you use the newer version, ListObjectsV2, when\n developing applications. For backward compatibility, Amazon S3 continues to support\n ListObjects.
The following operations are related to ListObjects:
\n ListObjectsV2\n
\n\n GetObject\n
\n\n PutObject\n
\n\n CreateBucket\n
\n\n ListBuckets\n
\nA flag that indicates whether Amazon S3 returned all of the results that satisfied the search\n criteria.
" } }, "Marker": { "target": "com.amazonaws.s3#Marker", "traits": { "smithy.api#documentation": "Indicates where in the bucket listing begins. Marker is included in the response if it was sent with\n the request.
" } }, "NextMarker": { "target": "com.amazonaws.s3#NextMarker", "traits": { "smithy.api#documentation": "When the response is truncated (the IsTruncated element value in the response is\n true), you can use the key name in this field as the marker parameter in the\n subsequent request to get the next set of objects. Amazon S3 lists objects in alphabetical order.
This element is returned only if you have the delimiter request parameter specified.\n If the response does not include the NextMarker element and it is truncated, you can use\n the value of the last Key element in the response as the marker parameter in\n the subsequent request to get the next set of object keys.
Metadata about each object returned.
", "smithy.api#xmlFlattened": {} } }, "Name": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name.
" } }, "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "Keys that begin with the indicated prefix.
" } }, "Delimiter": { "target": "com.amazonaws.s3#Delimiter", "traits": { "smithy.api#documentation": "Causes keys that contain the same string between the prefix and the first occurrence of the\n delimiter to be rolled up into a single result element in the CommonPrefixes collection.\n These rolled-up keys are not returned elsewhere in the response. Each rolled-up result counts as only\n one return against the MaxKeys value.
The maximum number of keys returned in the response body.
" } }, "CommonPrefixes": { "target": "com.amazonaws.s3#CommonPrefixList", "traits": { "smithy.api#documentation": "All of the keys (up to 1,000) rolled up in a common prefix count as a single return when calculating\n the number of returns.
\nA response can contain CommonPrefixes only if you specify a delimiter.
\n CommonPrefixes contains all (if there are any) keys between Prefix and the\n next occurrence of the string specified by the delimiter.
\n CommonPrefixes lists keys that act like subdirectories in the directory specified by\n Prefix.
For example, if the prefix is notes/ and the delimiter is a slash (/), as\n in notes/summer/july, the common prefix is notes/summer/. All of the keys that\n roll up into a common prefix count as a single return when calculating the number of returns.
Encoding type used by Amazon S3 to encode the object keys in the response. Responses are\n encoded only in UTF-8. An object key can contain any Unicode character. However, the XML 1.0 parser\n can't parse certain characters, such as characters with an ASCII value from 0 to 10. For characters that\n aren't supported in XML 1.0, you can add this parameter to request that Amazon S3 encode the keys in the\n response. For more information about characters to avoid in object key names, see Object key\n naming guidelines.
\nWhen using the URL encoding type, non-ASCII characters that are used in an object's key name will\n be percent-encoded according to UTF-8 code values. For example, the object\n test_file(3).png will appear as test_file%283%29.png.
The name of the bucket containing the objects.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
A delimiter is a character that you use to group keys.
\n\n CommonPrefixes is filtered out from results if it is not lexicographically greater than\n the key-marker.
Marker is where you want Amazon S3 to start listing from. Amazon S3 starts listing after this specified\n key. Marker can be any key in the bucket.
", "smithy.api#httpQuery": "marker" } }, "MaxKeys": { "target": "com.amazonaws.s3#MaxKeys", "traits": { "smithy.api#documentation": "Sets the maximum number of keys returned in the response. By default, the action returns up to 1,000\n key names. The response might contain fewer keys but will never contain more.
", "smithy.api#httpQuery": "max-keys" } }, "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "Limits the response to keys that begin with the specified prefix.
", "smithy.api#httpQuery": "prefix", "smithy.rules#contextParam": { "name": "Prefix" } } }, "RequestPayer": { "target": "com.amazonaws.s3#RequestPayer", "traits": { "smithy.api#documentation": "Confirms that the requester knows that she or he will be charged for the list objects request.\n Bucket owners need not specify this parameter in their requests.
", "smithy.api#httpHeader": "x-amz-request-payer" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Specifies the optional fields that you want returned in the response. Fields that you do not specify\n are not returned.
", "smithy.api#httpHeader": "x-amz-optional-object-attributes" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#ListObjectsV2": { "type": "operation", "input": { "target": "com.amazonaws.s3#ListObjectsV2Request" }, "output": { "target": "com.amazonaws.s3#ListObjectsV2Output" }, "errors": [ { "target": "com.amazonaws.s3#NoSuchBucket" } ], "traits": { "smithy.api#documentation": "Returns some or all (up to 1,000) of the objects in a bucket with each request. You can use the\n request parameters as selection criteria to return a subset of the objects in a bucket. A 200\n OK response can contain valid or invalid XML. Make sure to design your application to parse the\n contents of the response and handle it appropriately. For more information about listing objects, see\n Listing object\n keys programmatically in the Amazon S3 User Guide. To get a list of your\n buckets, see ListBuckets.
\n General purpose bucket - For general purpose buckets,\n ListObjectsV2 doesn't return prefixes that are related only to in-progress\n multipart uploads.
\n Directory buckets - For directory buckets,\n ListObjectsV2 response includes the prefixes that are related only to in-progress\n multipart uploads.
\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n General purpose bucket permissions - To use this\n operation, you must have READ access to the bucket. You must have permission to perform the\n s3:ListBucket action. The bucket owner has this permission by default and can\n grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access\n Permissions to Your Amazon S3 Resources in the\n Amazon S3 User Guide.
\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
\n General purpose bucket - For general purpose buckets,\n ListObjectsV2 returns objects in lexicographical order based on their key\n names.
\n Directory bucket - For directory buckets,\n ListObjectsV2 does not return objects in lexicographical order.
\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
This section describes the latest revision of this action. We recommend that you use this revised\n API operation for application development. For backward compatibility, Amazon S3 continues to support the\n prior version of this API operation, ListObjects.
\nThe following operations are related to ListObjectsV2:
\n GetObject\n
\n\n PutObject\n
\n\n CreateBucket\n
\nSet to false if all of the results were returned. Set to true if more keys\n are available to return. If the number of results exceeds that specified by MaxKeys, all of\n the results might not be returned.
Metadata about each object returned.
", "smithy.api#xmlFlattened": {} } }, "Name": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name.
" } }, "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "Keys that begin with the indicated prefix.
\n\n Directory buckets - For directory buckets, only prefixes that end in a delimiter (/) are supported.
Causes keys that contain the same string between the prefix and the first occurrence of\n the delimiter to be rolled up into a single result element in the CommonPrefixes\n collection. These rolled-up keys are not returned elsewhere in the response. Each rolled-up result\n counts as only one return against the MaxKeys value.
\n Directory buckets - For directory buckets, / is the only supported delimiter.
Sets the maximum number of keys returned in the response. By default, the action returns up to 1,000\n key names. The response might contain fewer keys but will never contain more.
" } }, "CommonPrefixes": { "target": "com.amazonaws.s3#CommonPrefixList", "traits": { "smithy.api#documentation": "All of the keys (up to 1,000) that share the same prefix are grouped together. When counting the\n total numbers of returns by this API operation, this group of keys is considered as one item.
\nA response can contain CommonPrefixes only if you specify a delimiter.
\n CommonPrefixes contains all (if there are any) keys between Prefix and the\n next occurrence of the string specified by a delimiter.
\n CommonPrefixes lists keys that act like subdirectories in the directory specified by\n Prefix.
For example, if the prefix is notes/ and the delimiter is a slash (/) as\n in notes/summer/july, the common prefix is notes/summer/. All of the keys that\n roll up into a common prefix count as a single return when calculating the number of returns.
\n Directory buckets - For directory buckets, only prefixes that end in a delimiter (/) are supported.
\n Directory buckets - When you query\n ListObjectsV2 with a delimiter during in-progress multipart uploads, the\n CommonPrefixes response parameter contains the prefixes that are associated with\n the in-progress multipart uploads. For more information about multipart uploads, see Multipart Upload\n Overview in the Amazon S3 User Guide.
Encoding type used by Amazon S3 to encode object key names in the XML response.
\nIf you specify the encoding-type request parameter, Amazon S3 includes this element in the\n response, and returns encoded key name values in the following response elements:
\n Delimiter, Prefix, Key, and StartAfter.
\n KeyCount is the number of keys returned with this request. KeyCount will\n always be less than or equal to the MaxKeys field. For example, if you ask for 50 keys,\n your result will include 50 keys or fewer.
If ContinuationToken was sent with the request, it is included in the response. You\n can use the returned ContinuationToken for pagination of the list response.
\n NextContinuationToken is sent when isTruncated is true, which means there\n are more keys in the bucket that can be listed. The next list requests to Amazon S3 can be continued with\n this NextContinuationToken. NextContinuationToken is obfuscated and is not a\n real key
If StartAfter was sent with the request, it is included in the response.
\nThis functionality is not supported for directory buckets.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
A delimiter is a character that you use to group keys.
\n\n CommonPrefixes is filtered out from results if it is not lexicographically greater than\n the StartAfter value.
\n Directory buckets - For directory buckets, / is the only supported delimiter.
\n Directory buckets - When you query\n ListObjectsV2 with a delimiter during in-progress multipart uploads, the\n CommonPrefixes response parameter contains the prefixes that are associated with\n the in-progress multipart uploads. For more information about multipart uploads, see Multipart Upload\n Overview in the Amazon S3 User Guide.
Encoding type used by Amazon S3 to encode the object keys in the response. Responses are\n encoded only in UTF-8. An object key can contain any Unicode character. However, the XML 1.0 parser\n can't parse certain characters, such as characters with an ASCII value from 0 to 10. For characters that\n aren't supported in XML 1.0, you can add this parameter to request that Amazon S3 encode the keys in the\n response. For more information about characters to avoid in object key names, see Object key\n naming guidelines.
\nWhen using the URL encoding type, non-ASCII characters that are used in an object's key name will\n be percent-encoded according to UTF-8 code values. For example, the object\n test_file(3).png will appear as test_file%283%29.png.
Sets the maximum number of keys returned in the response. By default, the action returns up to 1,000\n key names. The response might contain fewer keys but will never contain more.
", "smithy.api#httpQuery": "max-keys" } }, "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "Limits the response to keys that begin with the specified prefix.
\n\n Directory buckets - For directory buckets, only prefixes that end in a delimiter (/) are supported.
\n ContinuationToken indicates to Amazon S3 that the list is being continued on this bucket\n with a token. ContinuationToken is obfuscated and is not a real key. You can use this\n ContinuationToken for pagination of the list results.
The owner field is not present in ListObjectsV2 by default. If you want to return the\n owner field with each key in the result, then set the FetchOwner field to\n true.
\n Directory buckets - For directory buckets, the bucket\n owner is returned as the object owner for all objects.
\nStartAfter is where you want Amazon S3 to start listing from. Amazon S3 starts listing after this specified\n key. StartAfter can be any key in the bucket.
\nThis functionality is not supported for directory buckets.
\nConfirms that the requester knows that she or he will be charged for the list objects request in V2\n style. Bucket owners need not specify this parameter in their requests.
\nThis functionality is not supported for directory buckets.
\nThe account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Specifies the optional fields that you want returned in the response. Fields that you do not specify\n are not returned.
\nThis functionality is not supported for directory buckets.
\nEnd of support notice: Beginning October 1, 2025, Amazon S3 will stop returning DisplayName. Update your applications to use canonical IDs (unique identifier for \n Amazon Web Services accounts), Amazon Web Services account ID (12 digit identifier) or IAM ARNs (full resource naming) as a direct replacement of DisplayName.\n
This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nLists the parts that have been uploaded for a specific multipart upload.
\nTo use this operation, you must provide the upload ID in the request. You obtain this\n uploadID by sending the initiate multipart upload request through CreateMultipartUpload.
The ListParts request returns a maximum of 1,000 uploaded parts. The limit of 1,000\n parts is also the default value. You can restrict the number of parts in a response by specifying the\n max-parts request parameter. If your multipart upload consists of more than 1,000 parts,\n the response returns an IsTruncated field with the value of true, and a\n NextPartNumberMarker element. To list remaining uploaded parts, in subsequent\n ListParts requests, include the part-number-marker query string parameter\n and set its value to the NextPartNumberMarker field value from the previous\n response.
For more information on multipart uploads, see Uploading Objects Using Multipart Upload in\n the Amazon S3 User Guide.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n General purpose bucket permissions - For information\n about permissions required to use the multipart upload API, see Multipart Upload and Permissions in\n the Amazon S3 User Guide.
\nIf the upload was created using server-side encryption with Key Management Service (KMS) keys\n (SSE-KMS) or dual-layer server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), you must have\n permission to the kms:Decrypt action for the ListParts request to\n succeed.
\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following operations are related to ListParts:
\n UploadPart\n
\n\n AbortMultipartUpload\n
\n\n GetObjectAttributes\n
\n\n ListMultipartUploads\n
\nIf the bucket has a lifecycle rule configured with an action to abort incomplete multipart uploads\n and the prefix in the lifecycle rule matches the object name in the request, then the response includes\n this header indicating when the initiated multipart upload will become eligible for abort operation. For\n more information, see Aborting\n Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration.
\nThe response will also include the x-amz-abort-rule-id header that will provide the ID\n of the lifecycle configuration rule that defines this action.
This functionality is not supported for directory buckets.
\nThis header is returned along with the x-amz-abort-date header. It identifies\n applicable lifecycle configuration rule that defines the action to abort incomplete multipart\n uploads.
This functionality is not supported for directory buckets.
\nThe name of the bucket to which the multipart upload was initiated. Does not return the access point ARN or\n access point alias if used.
" } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "Object key for which the multipart upload was initiated.
" } }, "UploadId": { "target": "com.amazonaws.s3#MultipartUploadId", "traits": { "smithy.api#documentation": "Upload ID identifying the multipart upload whose parts are being listed.
" } }, "PartNumberMarker": { "target": "com.amazonaws.s3#PartNumberMarker", "traits": { "smithy.api#documentation": "Specifies the part after which listing should begin. Only parts with higher part numbers will be\n listed.
" } }, "NextPartNumberMarker": { "target": "com.amazonaws.s3#NextPartNumberMarker", "traits": { "smithy.api#documentation": "When a list is truncated, this element specifies the last part in the list, as well as the value to\n use for the part-number-marker request parameter in a subsequent request.
Maximum number of parts that were allowed in the response.
" } }, "IsTruncated": { "target": "com.amazonaws.s3#IsTruncated", "traits": { "smithy.api#documentation": "Indicates whether the returned list of parts is truncated. A true value indicates that the list was\n truncated. A list can be truncated if the number of parts exceeds the limit returned in the MaxParts\n element.
" } }, "Parts": { "target": "com.amazonaws.s3#Parts", "traits": { "smithy.api#documentation": "Container for elements related to a particular part. A response can contain zero or more\n Part elements.
Container element that identifies who initiated the multipart upload. If the initiator is an\n Amazon Web Services account, this element provides the same information as the Owner element. If the\n initiator is an IAM User, this element provides the user ARN and display name.
Container element that identifies the object owner, after the object is created. If multipart upload\n is initiated by an IAM user, this element provides the parent account ID and display name.
\n\n Directory buckets - The bucket owner is returned as the\n object owner for all the parts.
\nThe class of storage used to store the uploaded object.
\n\n Directory buckets -\n Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
The algorithm that was used to create a checksum of the object.
" } }, "ChecksumType": { "target": "com.amazonaws.s3#ChecksumType", "traits": { "smithy.api#documentation": "The checksum type, which determines how part-level checksums are combined to create an object-level\n checksum for multipart objects. You can use this header response to verify that the checksum type that\n is received is the same checksum type that was specified in CreateMultipartUpload request.\n For more information, see Checking object integrity in the Amazon S3\n User Guide.
The name of the bucket to which the parts are being uploaded.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Object key for which the multipart upload was initiated.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Key" } } }, "MaxParts": { "target": "com.amazonaws.s3#MaxParts", "traits": { "smithy.api#documentation": "Sets the maximum number of parts to return.
", "smithy.api#httpQuery": "max-parts" } }, "PartNumberMarker": { "target": "com.amazonaws.s3#PartNumberMarker", "traits": { "smithy.api#documentation": "Specifies the part after which listing should begin. Only parts with higher part numbers will be\n listed.
", "smithy.api#httpQuery": "part-number-marker" } }, "UploadId": { "target": "com.amazonaws.s3#MultipartUploadId", "traits": { "smithy.api#documentation": "Upload ID identifying the multipart upload whose parts are being listed.
", "smithy.api#httpQuery": "uploadId", "smithy.api#required": {} } }, "RequestPayer": { "target": "com.amazonaws.s3#RequestPayer", "traits": { "smithy.api#httpHeader": "x-amz-request-payer" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The server-side encryption (SSE) algorithm used to encrypt the object. This parameter is needed only when the object was created \n using a checksum algorithm. For more information,\n see Protecting data using SSE-C keys in the\n Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\nThe server-side encryption (SSE) customer managed key. This parameter is needed only when the object was created using a checksum algorithm. \n For more information, see\n Protecting data using SSE-C keys in the\n Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\nThe MD5 server-side encryption (SSE) customer managed key. This parameter is needed only when the object was created using a checksum \n algorithm. For more information,\n see Protecting data using SSE-C keys in the\n Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\nThe type of location where the bucket will be created.
" } }, "Name": { "target": "com.amazonaws.s3#LocationNameAsString", "traits": { "smithy.api#documentation": "The name of the location where the bucket will be created.
\nFor directory buckets, the name of the location is the Zone ID of the Availability Zone (AZ) or Local Zone (LZ) where\n the bucket will be created. An example AZ ID value is usw2-az1.
Specifies the location where the bucket will be created.
\nFor directory buckets, the location type is Availability Zone or Local Zone. For more information about\n directory buckets, see Working with\n directory buckets in the Amazon S3 User Guide.
\nThis functionality is only supported by directory buckets.
\nSpecifies the bucket where you want Amazon S3 to store server access logs. You can have your logs\n delivered to any bucket that you own, including the same bucket that is being logged. You can also\n configure multiple buckets to deliver their logs to the same target bucket. In this case, you should\n choose a different TargetPrefix for each source bucket so that the delivered log files can\n be distinguished by key.
Container for granting information.
\nBuckets that use the bucket owner enforced setting for Object Ownership don't support target grants.\n For more information, see Permissions for server access log delivery in the\n Amazon S3 User Guide.
" } }, "TargetPrefix": { "target": "com.amazonaws.s3#TargetPrefix", "traits": { "smithy.api#documentation": "A prefix for all log object keys. If you store log files from multiple Amazon S3 buckets in a single\n bucket, you can use a prefix to distinguish which log files came from which bucket.
", "smithy.api#required": {} } }, "TargetObjectKeyFormat": { "target": "com.amazonaws.s3#TargetObjectKeyFormat", "traits": { "smithy.api#documentation": "Amazon S3 key format for log objects.
" } } }, "traits": { "smithy.api#documentation": "Describes where logs are stored and the prefix that Amazon S3 assigns to all log object keys for a\n bucket. For more information, see PUT Bucket logging in the\n Amazon S3 API Reference.
" } }, "com.amazonaws.s3#MFA": { "type": "string" }, "com.amazonaws.s3#MFADelete": { "type": "enum", "members": { "Enabled": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Enabled" } }, "Disabled": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Disabled" } } } }, "com.amazonaws.s3#MFADeleteStatus": { "type": "enum", "members": { "Enabled": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Enabled" } }, "Disabled": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Disabled" } } } }, "com.amazonaws.s3#Marker": { "type": "string" }, "com.amazonaws.s3#MaxAgeSeconds": { "type": "integer" }, "com.amazonaws.s3#MaxBuckets": { "type": "integer", "traits": { "smithy.api#range": { "min": 1, "max": 10000 } } }, "com.amazonaws.s3#MaxDirectoryBuckets": { "type": "integer", "traits": { "smithy.api#range": { "min": 0, "max": 1000 } } }, "com.amazonaws.s3#MaxKeys": { "type": "integer" }, "com.amazonaws.s3#MaxParts": { "type": "integer" }, "com.amazonaws.s3#MaxUploads": { "type": "integer" }, "com.amazonaws.s3#Message": { "type": "string" }, "com.amazonaws.s3#Metadata": { "type": "map", "key": { "target": "com.amazonaws.s3#MetadataKey" }, "value": { "target": "com.amazonaws.s3#MetadataValue" } }, "com.amazonaws.s3#MetadataConfiguration": { "type": "structure", "members": { "JournalTableConfiguration": { "target": "com.amazonaws.s3#JournalTableConfiguration", "traits": { "smithy.api#documentation": "\n The journal table configuration for a metadata configuration.\n
", "smithy.api#required": {} } }, "InventoryTableConfiguration": { "target": "com.amazonaws.s3#InventoryTableConfiguration", "traits": { "smithy.api#documentation": "\n The inventory table configuration for a metadata configuration.\n
" } } }, "traits": { "smithy.api#documentation": "\n The S3 Metadata configuration for a general purpose bucket.\n
" } }, "com.amazonaws.s3#MetadataConfigurationResult": { "type": "structure", "members": { "DestinationResult": { "target": "com.amazonaws.s3#DestinationResult", "traits": { "smithy.api#documentation": "\n The destination settings for a metadata configuration.\n
", "smithy.api#required": {} } }, "JournalTableConfigurationResult": { "target": "com.amazonaws.s3#JournalTableConfigurationResult", "traits": { "smithy.api#documentation": "\n The journal table configuration for a metadata configuration.\n
" } }, "InventoryTableConfigurationResult": { "target": "com.amazonaws.s3#InventoryTableConfigurationResult", "traits": { "smithy.api#documentation": "\n The inventory table configuration for a metadata configuration.\n
" } } }, "traits": { "smithy.api#documentation": "\n The S3 Metadata configuration for a general purpose bucket.\n
" } }, "com.amazonaws.s3#MetadataDirective": { "type": "enum", "members": { "COPY": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "COPY" } }, "REPLACE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "REPLACE" } } } }, "com.amazonaws.s3#MetadataEntry": { "type": "structure", "members": { "Name": { "target": "com.amazonaws.s3#MetadataKey", "traits": { "smithy.api#documentation": "Name of the object.
" } }, "Value": { "target": "com.amazonaws.s3#MetadataValue", "traits": { "smithy.api#documentation": "Value of the object.
" } } }, "traits": { "smithy.api#documentation": "A metadata key-value pair to store with an object.
" } }, "com.amazonaws.s3#MetadataKey": { "type": "string" }, "com.amazonaws.s3#MetadataTableConfiguration": { "type": "structure", "members": { "S3TablesDestination": { "target": "com.amazonaws.s3#S3TablesDestination", "traits": { "smithy.api#documentation": " The destination information for the metadata table configuration. The destination table bucket must\n be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata table name\n must be unique within the aws_s3_metadata namespace in the destination table bucket.\n
The V1 S3 Metadata configuration for a general purpose bucket.
\nIf you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete \n and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create \n a live inventory table.
\n The destination information for the metadata table configuration. The destination table bucket must\n be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata table name\n must be unique within the aws_s3_metadata namespace in the destination table bucket.\n
The V1 S3 Metadata configuration for a general purpose bucket. The destination table bucket must be\n in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata table name\n must be unique within the aws_s3_metadata namespace in the destination table bucket.\n
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete \n and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create \n a live inventory table.
\n\n The encryption type specified for a metadata table. To specify server-side encryption with \n Key Management Service (KMS) keys (SSE-KMS), use the aws:kms value. To specify server-side \n encryption with Amazon S3 managed keys (SSE-S3), use the AES256 value. \n
\n If server-side encryption with Key Management Service (KMS) keys (SSE-KMS) is specified, you must also\n specify the KMS key Amazon Resource Name (ARN). You must specify a customer-managed KMS key \n that's located in the same Region as the general purpose bucket that corresponds to the metadata \n table configuration.\n
" } } }, "traits": { "smithy.api#documentation": "\n The encryption settings for an S3 Metadata journal table or inventory table configuration.\n
" } }, "com.amazonaws.s3#MetadataTableStatus": { "type": "string" }, "com.amazonaws.s3#MetadataValue": { "type": "string" }, "com.amazonaws.s3#Metrics": { "type": "structure", "members": { "Status": { "target": "com.amazonaws.s3#MetricsStatus", "traits": { "smithy.api#documentation": "Specifies whether the replication metrics are enabled.
", "smithy.api#required": {} } }, "EventThreshold": { "target": "com.amazonaws.s3#ReplicationTimeValue", "traits": { "smithy.api#documentation": " A container specifying the time threshold for emitting the\n s3:Replication:OperationMissedThreshold event.
A container specifying replication metrics-related settings enabling replication metrics and\n events.
" } }, "com.amazonaws.s3#MetricsAndOperator": { "type": "structure", "members": { "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "The prefix used when evaluating an AND predicate.
" } }, "Tags": { "target": "com.amazonaws.s3#TagSet", "traits": { "smithy.api#documentation": "The list of tags used when evaluating an AND predicate.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Tag" } }, "AccessPointArn": { "target": "com.amazonaws.s3#AccessPointArn", "traits": { "smithy.api#documentation": "The access point ARN used when evaluating an AND predicate.
A conjunction (logical AND) of predicates, which is used in evaluating a metrics filter. The\n operator must have at least two predicates, and an object must match all of the predicates in order for\n the filter to apply.
" } }, "com.amazonaws.s3#MetricsConfiguration": { "type": "structure", "members": { "Id": { "target": "com.amazonaws.s3#MetricsId", "traits": { "smithy.api#documentation": "The ID used to identify the metrics configuration. The ID has a 64 character limit and can only\n contain letters, numbers, periods, dashes, and underscores.
", "smithy.api#required": {} } }, "Filter": { "target": "com.amazonaws.s3#MetricsFilter", "traits": { "smithy.api#documentation": "Specifies a metrics configuration filter. The metrics configuration will only include objects that\n meet the filter's criteria. A filter must be a prefix, an object tag, an access point ARN, or a\n conjunction (MetricsAndOperator).
" } } }, "traits": { "smithy.api#documentation": "Specifies a metrics configuration for the CloudWatch request metrics (specified by the metrics\n configuration ID) from an Amazon S3 bucket. If you're updating an existing metrics configuration, note that\n this is a full replacement of the existing metrics configuration. If you don't include the elements you\n want to keep, they are erased. For more information, see PutBucketMetricsConfiguration.
" } }, "com.amazonaws.s3#MetricsConfigurationList": { "type": "list", "member": { "target": "com.amazonaws.s3#MetricsConfiguration" } }, "com.amazonaws.s3#MetricsFilter": { "type": "union", "members": { "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "The prefix used when evaluating a metrics filter.
" } }, "Tag": { "target": "com.amazonaws.s3#Tag", "traits": { "smithy.api#documentation": "The tag used when evaluating a metrics filter.
" } }, "AccessPointArn": { "target": "com.amazonaws.s3#AccessPointArn", "traits": { "smithy.api#documentation": "The access point ARN used when evaluating a metrics filter.
" } }, "And": { "target": "com.amazonaws.s3#MetricsAndOperator", "traits": { "smithy.api#documentation": "A conjunction (logical AND) of predicates, which is used in evaluating a metrics filter. The\n operator must have at least two predicates, and an object must match all of the predicates in order for\n the filter to apply.
" } } }, "traits": { "smithy.api#documentation": "Specifies a metrics configuration filter. The metrics configuration only includes objects that meet\n the filter's criteria. A filter must be a prefix, an object tag, an access point ARN, or a conjunction\n (MetricsAndOperator). For more information, see PutBucketMetricsConfiguration.
" } }, "com.amazonaws.s3#MetricsId": { "type": "string" }, "com.amazonaws.s3#MetricsStatus": { "type": "enum", "members": { "Enabled": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Enabled" } }, "Disabled": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Disabled" } } } }, "com.amazonaws.s3#Minutes": { "type": "integer" }, "com.amazonaws.s3#MissingMeta": { "type": "integer" }, "com.amazonaws.s3#MpuObjectSize": { "type": "long" }, "com.amazonaws.s3#MultipartUpload": { "type": "structure", "members": { "UploadId": { "target": "com.amazonaws.s3#MultipartUploadId", "traits": { "smithy.api#documentation": "Upload ID that identifies the multipart upload.
" } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "Key of the object for which the multipart upload was initiated.
" } }, "Initiated": { "target": "com.amazonaws.s3#Initiated", "traits": { "smithy.api#documentation": "Date and time at which the multipart upload was initiated.
" } }, "StorageClass": { "target": "com.amazonaws.s3#StorageClass", "traits": { "smithy.api#documentation": "The class of storage used to store the object.
\n\n Directory buckets -\n Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
Specifies the owner of the object that is part of the multipart upload.
\n\n Directory buckets - The bucket owner is returned as the\n object owner for all the objects.
\nIdentifies who initiated the multipart upload.
" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "The algorithm that was used to create a checksum of the object.
" } }, "ChecksumType": { "target": "com.amazonaws.s3#ChecksumType", "traits": { "smithy.api#documentation": "The checksum type that is used to calculate the object\u2019s checksum value. For more information, see\n Checking\n object integrity in the Amazon S3 User Guide.
" } } }, "traits": { "smithy.api#documentation": "Container for the MultipartUpload for the Amazon S3 object.
The specified bucket does not exist.
", "smithy.api#error": "client", "smithy.api#httpError": 404 } }, "com.amazonaws.s3#NoSuchKey": { "type": "structure", "members": {}, "traits": { "smithy.api#documentation": "The specified key does not exist.
", "smithy.api#error": "client", "smithy.api#httpError": 404 } }, "com.amazonaws.s3#NoSuchUpload": { "type": "structure", "members": {}, "traits": { "smithy.api#documentation": "The specified multipart upload does not exist.
", "smithy.api#error": "client", "smithy.api#httpError": 404 } }, "com.amazonaws.s3#NoncurrentVersionExpiration": { "type": "structure", "members": { "NoncurrentDays": { "target": "com.amazonaws.s3#Days", "traits": { "smithy.api#documentation": "Specifies the number of days an object is noncurrent before Amazon S3 can perform the associated action.\n The value must be a non-zero positive integer. For information about the noncurrent days calculations,\n see How Amazon S3 Calculates\n When an Object Became Noncurrent in the Amazon S3 User Guide.
\nThis parameter applies to general purpose buckets only. It is not supported for directory bucket\n lifecycle configurations.
\nSpecifies how many noncurrent versions Amazon S3 will retain. You can specify up to 100 noncurrent\n versions to retain. Amazon S3 will permanently delete any additional noncurrent versions beyond the specified\n number to retain. For more information about noncurrent versions, see Lifecycle configuration elements in\n the Amazon S3 User Guide.
\nThis parameter applies to general purpose buckets only. It is not supported for directory bucket\n lifecycle configurations.
\nSpecifies when noncurrent object versions expire. Upon expiration, Amazon S3 permanently deletes the\n noncurrent object versions. You set this lifecycle configuration action on a bucket that has versioning\n enabled (or suspended) to request that Amazon S3 delete noncurrent object versions at a specific period in\n the object's lifetime.
\nThis parameter applies to general purpose buckets only. It is not supported for directory bucket\n lifecycle configurations.
\nSpecifies the number of days an object is noncurrent before Amazon S3 can perform the associated action.\n For information about the noncurrent days calculations, see How Amazon S3 Calculates\n How Long an Object Has Been Noncurrent in the Amazon S3 User Guide.
" } }, "StorageClass": { "target": "com.amazonaws.s3#TransitionStorageClass", "traits": { "smithy.api#documentation": "The class of storage used to store the object.
" } }, "NewerNoncurrentVersions": { "target": "com.amazonaws.s3#VersionCount", "traits": { "smithy.api#documentation": "Specifies how many noncurrent versions Amazon S3 will retain in the same storage class before\n transitioning objects. You can specify up to 100 noncurrent versions to retain. Amazon S3 will transition any\n additional noncurrent versions beyond the specified number to retain. For more information about\n noncurrent versions, see Lifecycle configuration elements in\n the Amazon S3 User Guide.
" } } }, "traits": { "smithy.api#documentation": "Container for the transition rule that describes when noncurrent objects transition to the\n STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING,\n GLACIER_IR, GLACIER, or DEEP_ARCHIVE storage class. If your\n bucket is versioning-enabled (or versioning is suspended), you can set this action to request that Amazon S3\n transition noncurrent object versions to the STANDARD_IA, ONEZONE_IA,\n INTELLIGENT_TIERING, GLACIER_IR, GLACIER, or\n DEEP_ARCHIVE storage class at a specific period in the object's lifetime.
The specified content does not exist.
", "smithy.api#error": "client" } }, "com.amazonaws.s3#NotificationConfiguration": { "type": "structure", "members": { "TopicConfigurations": { "target": "com.amazonaws.s3#TopicConfigurationList", "traits": { "smithy.api#documentation": "The topic to which notifications are sent and the events for which notifications are\n generated.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "TopicConfiguration" } }, "QueueConfigurations": { "target": "com.amazonaws.s3#QueueConfigurationList", "traits": { "smithy.api#documentation": "The Amazon Simple Queue Service queues to publish messages to and the events for which to publish\n messages.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "QueueConfiguration" } }, "LambdaFunctionConfigurations": { "target": "com.amazonaws.s3#LambdaFunctionConfigurationList", "traits": { "smithy.api#documentation": "Describes the Lambda functions to invoke and the events for which to invoke them.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "CloudFunctionConfiguration" } }, "EventBridgeConfiguration": { "target": "com.amazonaws.s3#EventBridgeConfiguration", "traits": { "smithy.api#documentation": "Enables delivery of events to Amazon EventBridge.
" } } }, "traits": { "smithy.api#documentation": "A container for specifying the notification configuration of the bucket. If this element is empty,\n notifications are turned off for the bucket.
" } }, "com.amazonaws.s3#NotificationConfigurationFilter": { "type": "structure", "members": { "Key": { "target": "com.amazonaws.s3#S3KeyFilter", "traits": { "smithy.api#xmlName": "S3Key" } } }, "traits": { "smithy.api#documentation": "Specifies object key name filtering rules. For information about key name filtering, see Configuring\n event notifications using object key name filtering in the\n Amazon S3 User Guide.
" } }, "com.amazonaws.s3#NotificationId": { "type": "string", "traits": { "smithy.api#documentation": "An optional unique identifier for configurations in a notification configuration. If you don't\n provide one, Amazon S3 will assign an ID.
" } }, "com.amazonaws.s3#Object": { "type": "structure", "members": { "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "The name that you assign to an object. You use the object key to retrieve the object.
" } }, "LastModified": { "target": "com.amazonaws.s3#LastModified", "traits": { "smithy.api#documentation": "Creation date of the object.
" } }, "ETag": { "target": "com.amazonaws.s3#ETag", "traits": { "smithy.api#documentation": "The entity tag is a hash of the object. The ETag reflects changes only to the contents of an object,\n not its metadata. The ETag may or may not be an MD5 digest of the object data. Whether or not it is\n depends on how the object was created and how it is encrypted as described below:
\nObjects created by the PUT Object, POST Object, or Copy operation, or through the Amazon Web Services\n Management Console, and are encrypted by SSE-S3 or plaintext, have ETags that are an MD5 digest of\n their object data.
\nObjects created by the PUT Object, POST Object, or Copy operation, or through the Amazon Web Services\n Management Console, and are encrypted by SSE-C or SSE-KMS, have ETags that are not an MD5 digest of\n their object data.
\nIf an object is created by either the Multipart Upload or Part Copy operation, the ETag is not\n an MD5 digest, regardless of the method of encryption. If an object is larger than 16 MB, the Amazon Web Services\n Management Console will upload or copy that object as a Multipart Upload, and therefore the ETag\n will not be an MD5 digest.
\n\n Directory buckets - MD5 is not supported by directory buckets.
\nThe algorithm that was used to create a checksum of the object.
", "smithy.api#xmlFlattened": {} } }, "ChecksumType": { "target": "com.amazonaws.s3#ChecksumType", "traits": { "smithy.api#documentation": "The checksum type that is used to calculate the object\u2019s checksum value. For more information, see\n Checking\n object integrity in the Amazon S3 User Guide.
" } }, "Size": { "target": "com.amazonaws.s3#Size", "traits": { "smithy.api#documentation": "Size in bytes of the object
" } }, "StorageClass": { "target": "com.amazonaws.s3#ObjectStorageClass", "traits": { "smithy.api#documentation": "The class of storage used to store the object.
\n\n Directory buckets -\n Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
The owner of the object
\n\n Directory buckets - The bucket owner is returned as the\n object owner.
\nSpecifies the restoration status of an object. Objects in certain storage classes must be restored\n before they can be retrieved. For more information about these storage classes and how to work with\n archived objects, see \n Working with archived objects in the Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets. Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
An object consists of data and its descriptive metadata.
" } }, "com.amazonaws.s3#ObjectAlreadyInActiveTierError": { "type": "structure", "members": {}, "traits": { "smithy.api#documentation": "This action is not allowed against this storage tier.
", "smithy.api#error": "client", "smithy.api#httpError": 403 } }, "com.amazonaws.s3#ObjectAttributes": { "type": "enum", "members": { "ETAG": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ETag" } }, "CHECKSUM": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Checksum" } }, "OBJECT_PARTS": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ObjectParts" } }, "STORAGE_CLASS": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "StorageClass" } }, "OBJECT_SIZE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ObjectSize" } } } }, "com.amazonaws.s3#ObjectAttributesList": { "type": "list", "member": { "target": "com.amazonaws.s3#ObjectAttributes" } }, "com.amazonaws.s3#ObjectCannedACL": { "type": "enum", "members": { "private": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "private" } }, "public_read": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "public-read" } }, "public_read_write": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "public-read-write" } }, "authenticated_read": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "authenticated-read" } }, "aws_exec_read": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "aws-exec-read" } }, "bucket_owner_read": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "bucket-owner-read" } }, "bucket_owner_full_control": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "bucket-owner-full-control" } } } }, "com.amazonaws.s3#ObjectIdentifier": { "type": "structure", "members": { "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "Key name of the object.
\nReplacement must be made for object keys containing special characters (such as carriage returns) when using \n XML requests. For more information, see \n XML related object key constraints.
\nVersion ID for the specific version of the object to delete.
\nThis functionality is not supported for directory buckets.
\nAn entity tag (ETag) is an identifier assigned by a web server to a specific version of a resource\n found at a URL. This header field makes the request method conditional on ETags.
Entity tags (ETags) for S3 Express One Zone are random alphanumeric strings unique to the object.\n
\nIf present, the objects are deleted only if its modification times matches the provided\n Timestamp.
This functionality is only supported for directory buckets.
\nIf present, the objects are deleted only if its size matches the provided size in bytes.
\nThis functionality is only supported for directory buckets.
\nObject Identifier is unique value to identify objects.
" } }, "com.amazonaws.s3#ObjectIdentifierList": { "type": "list", "member": { "target": "com.amazonaws.s3#ObjectIdentifier" } }, "com.amazonaws.s3#ObjectKey": { "type": "string", "traits": { "smithy.api#length": { "min": 1 } } }, "com.amazonaws.s3#ObjectList": { "type": "list", "member": { "target": "com.amazonaws.s3#Object" } }, "com.amazonaws.s3#ObjectLockConfiguration": { "type": "structure", "members": { "ObjectLockEnabled": { "target": "com.amazonaws.s3#ObjectLockEnabled", "traits": { "smithy.api#documentation": "Indicates whether this bucket has an Object Lock configuration enabled. Enable\n ObjectLockEnabled when you apply ObjectLockConfiguration to a bucket.\n
Specifies the Object Lock rule for the specified object. Enable the this rule when you apply\n ObjectLockConfiguration to a bucket. Bucket settings require both a mode and a period.\n The period can be either Days or Years but you must select one. You cannot\n specify Days and Years at the same time.
The container element for Object Lock configuration parameters.
" } }, "com.amazonaws.s3#ObjectLockEnabled": { "type": "enum", "members": { "Enabled": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Enabled" } } } }, "com.amazonaws.s3#ObjectLockEnabledForBucket": { "type": "boolean" }, "com.amazonaws.s3#ObjectLockLegalHold": { "type": "structure", "members": { "Status": { "target": "com.amazonaws.s3#ObjectLockLegalHoldStatus", "traits": { "smithy.api#documentation": "Indicates whether the specified object has a legal hold in place.
" } } }, "traits": { "smithy.api#documentation": "A legal hold configuration for an object.
" } }, "com.amazonaws.s3#ObjectLockLegalHoldStatus": { "type": "enum", "members": { "ON": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ON" } }, "OFF": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "OFF" } } } }, "com.amazonaws.s3#ObjectLockMode": { "type": "enum", "members": { "GOVERNANCE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "GOVERNANCE" } }, "COMPLIANCE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "COMPLIANCE" } } } }, "com.amazonaws.s3#ObjectLockRetainUntilDate": { "type": "timestamp", "traits": { "smithy.api#timestampFormat": "date-time" } }, "com.amazonaws.s3#ObjectLockRetention": { "type": "structure", "members": { "Mode": { "target": "com.amazonaws.s3#ObjectLockRetentionMode", "traits": { "smithy.api#documentation": "Indicates the Retention mode for the specified object.
" } }, "RetainUntilDate": { "target": "com.amazonaws.s3#Date", "traits": { "smithy.api#documentation": "The date on which this Object Lock Retention will expire.
" } } }, "traits": { "smithy.api#documentation": "A Retention configuration for an object.
" } }, "com.amazonaws.s3#ObjectLockRetentionMode": { "type": "enum", "members": { "GOVERNANCE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "GOVERNANCE" } }, "COMPLIANCE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "COMPLIANCE" } } } }, "com.amazonaws.s3#ObjectLockRule": { "type": "structure", "members": { "DefaultRetention": { "target": "com.amazonaws.s3#DefaultRetention", "traits": { "smithy.api#documentation": "The default Object Lock retention mode and period that you want to apply to new objects placed in\n the specified bucket. Bucket settings require both a mode and a period. The period can be either\n Days or Years but you must select one. You cannot specify Days\n and Years at the same time.
The container element for an Object Lock rule.
" } }, "com.amazonaws.s3#ObjectLockToken": { "type": "string" }, "com.amazonaws.s3#ObjectNotInActiveTierError": { "type": "structure", "members": {}, "traits": { "smithy.api#documentation": "The source object of the COPY action is not in the active tier and is only stored in Amazon S3\n Glacier.
", "smithy.api#error": "client", "smithy.api#httpError": 403 } }, "com.amazonaws.s3#ObjectOwnership": { "type": "enum", "members": { "BucketOwnerPreferred": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "BucketOwnerPreferred" } }, "ObjectWriter": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ObjectWriter" } }, "BucketOwnerEnforced": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "BucketOwnerEnforced" } } }, "traits": { "smithy.api#documentation": "The container element for object ownership for a bucket's ownership controls.
\n\n BucketOwnerPreferred - Objects uploaded to the bucket change ownership to the bucket\n owner if the objects are uploaded with the bucket-owner-full-control canned ACL.
\n ObjectWriter - The uploading account will own the object if the object is uploaded with\n the bucket-owner-full-control canned ACL.
\n BucketOwnerEnforced - Access control lists (ACLs) are disabled and no longer affect\n permissions. The bucket owner automatically owns and has full control over every object in the bucket.\n The bucket only accepts PUT requests that don't specify an ACL or specify bucket owner full control ACLs\n (such as the predefined bucket-owner-full-control canned ACL or a custom ACL in XML format\n that grants the same permissions).
By default, ObjectOwnership is set to BucketOwnerEnforced and ACLs are\n disabled. We recommend keeping ACLs disabled, except in uncommon use cases where you must control access\n for each object individually. For more information about S3 Object Ownership, see Controlling\n ownership of objects and disabling ACLs for your bucket in the\n Amazon S3 User Guide.
This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.
\nThe part number identifying the part. This value is a positive integer between 1 and 10,000.
" } }, "Size": { "target": "com.amazonaws.s3#Size", "traits": { "smithy.api#documentation": "The size of the uploaded part in bytes.
" } }, "ChecksumCRC32": { "target": "com.amazonaws.s3#ChecksumCRC32", "traits": { "smithy.api#documentation": "The Base64 encoded, 32-bit CRC32 checksum of the part. This checksum is present if the\n multipart upload request was created with the CRC32 checksum algorithm. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the part. This checksum is present if the\n multipart upload request was created with the CRC32C checksum algorithm. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the part. This checksum is present if\n the multipart upload request was created with the CRC64NVME checksum algorithm, or if the\n object was uploaded without a checksum (and Amazon S3 added the default checksum, CRC64NVME, to\n the uploaded object). For more information, see Checking object integrity in\n the Amazon S3 User Guide.
The Base64 encoded, 160-bit SHA1 checksum of the part. This checksum is present if the\n multipart upload request was created with the SHA1 checksum algorithm. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 checksum of the part. This checksum is present if\n the multipart upload request was created with the SHA256 checksum algorithm. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
A container for elements related to an individual part.
" } }, "com.amazonaws.s3#ObjectSize": { "type": "long" }, "com.amazonaws.s3#ObjectSizeGreaterThanBytes": { "type": "long" }, "com.amazonaws.s3#ObjectSizeLessThanBytes": { "type": "long" }, "com.amazonaws.s3#ObjectStorageClass": { "type": "enum", "members": { "STANDARD": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "STANDARD" } }, "REDUCED_REDUNDANCY": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "REDUCED_REDUNDANCY" } }, "GLACIER": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "GLACIER" } }, "STANDARD_IA": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "STANDARD_IA" } }, "ONEZONE_IA": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ONEZONE_IA" } }, "INTELLIGENT_TIERING": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "INTELLIGENT_TIERING" } }, "DEEP_ARCHIVE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "DEEP_ARCHIVE" } }, "OUTPOSTS": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "OUTPOSTS" } }, "GLACIER_IR": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "GLACIER_IR" } }, "SNOW": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "SNOW" } }, "EXPRESS_ONEZONE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "EXPRESS_ONEZONE" } }, "FSX_OPENZFS": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "FSX_OPENZFS" } } } }, "com.amazonaws.s3#ObjectVersion": { "type": "structure", "members": { "ETag": { "target": "com.amazonaws.s3#ETag", "traits": { "smithy.api#documentation": "The entity tag is an MD5 hash of that version of the object.
" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithmList", "traits": { "smithy.api#documentation": "The algorithm that was used to create a checksum of the object.
", "smithy.api#xmlFlattened": {} } }, "ChecksumType": { "target": "com.amazonaws.s3#ChecksumType", "traits": { "smithy.api#documentation": "The checksum type that is used to calculate the object\u2019s checksum value. For more information, see\n Checking\n object integrity in the Amazon S3 User Guide.
" } }, "Size": { "target": "com.amazonaws.s3#Size", "traits": { "smithy.api#documentation": "Size in bytes of the object.
" } }, "StorageClass": { "target": "com.amazonaws.s3#ObjectVersionStorageClass", "traits": { "smithy.api#documentation": "The class of storage used to store the object.
" } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "The object key.
" } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "Version ID of an object.
" } }, "IsLatest": { "target": "com.amazonaws.s3#IsLatest", "traits": { "smithy.api#documentation": "Specifies whether the object is (true) or is not (false) the latest version of an object.
" } }, "LastModified": { "target": "com.amazonaws.s3#LastModified", "traits": { "smithy.api#documentation": "Date and time when the object was last modified.
" } }, "Owner": { "target": "com.amazonaws.s3#Owner", "traits": { "smithy.api#documentation": "Specifies the owner of the object.
" } }, "RestoreStatus": { "target": "com.amazonaws.s3#RestoreStatus", "traits": { "smithy.api#documentation": "Specifies the restoration status of an object. Objects in certain storage classes must be restored\n before they can be retrieved. For more information about these storage classes and how to work with\n archived objects, see \n Working with archived objects in the Amazon S3 User Guide.
" } } }, "traits": { "smithy.api#documentation": "The version of an object.
" } }, "com.amazonaws.s3#ObjectVersionId": { "type": "string" }, "com.amazonaws.s3#ObjectVersionList": { "type": "list", "member": { "target": "com.amazonaws.s3#ObjectVersion" } }, "com.amazonaws.s3#ObjectVersionStorageClass": { "type": "enum", "members": { "STANDARD": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "STANDARD" } } } }, "com.amazonaws.s3#OptionalObjectAttributes": { "type": "enum", "members": { "RESTORE_STATUS": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "RestoreStatus" } } } }, "com.amazonaws.s3#OptionalObjectAttributesList": { "type": "list", "member": { "target": "com.amazonaws.s3#OptionalObjectAttributes" } }, "com.amazonaws.s3#OutputLocation": { "type": "structure", "members": { "S3": { "target": "com.amazonaws.s3#S3Location", "traits": { "smithy.api#documentation": "Describes an S3 location that will receive the results of the restore request.
" } } }, "traits": { "smithy.api#documentation": "Describes the location where the restore job's output is stored.
" } }, "com.amazonaws.s3#OutputSerialization": { "type": "structure", "members": { "CSV": { "target": "com.amazonaws.s3#CSVOutput", "traits": { "smithy.api#documentation": "Describes the serialization of CSV-encoded Select results.
" } }, "JSON": { "target": "com.amazonaws.s3#JSONOutput", "traits": { "smithy.api#documentation": "Specifies JSON as request's output serialization format.
" } } }, "traits": { "smithy.api#documentation": "Describes how results of the Select job are serialized.
" } }, "com.amazonaws.s3#Owner": { "type": "structure", "members": { "DisplayName": { "target": "com.amazonaws.s3#DisplayName", "traits": { "smithy.api#documentation": "Container for the display name of the owner. This value is only supported in the following Amazon Web Services\n Regions:
\nUS East (N. Virginia)
\nUS West (N. California)
\nUS West (Oregon)
\nAsia Pacific (Singapore)
\nAsia Pacific (Sydney)
\nAsia Pacific (Tokyo)
\nEurope (Ireland)
\nSouth America (S\u00e3o Paulo)
\nThis functionality is not supported for directory buckets.
\nContainer for the ID of the owner.
" } } }, "traits": { "smithy.api#documentation": "End of support notice: Beginning October 1, 2025, Amazon S3 will stop returning DisplayName. Update your applications to use canonical IDs (unique identifier for \n Amazon Web Services accounts), Amazon Web Services account ID (12 digit identifier) or IAM ARNs (full resource naming) as a direct replacement of DisplayName.\n
This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nContainer for the owner's display name and ID.
" } }, "com.amazonaws.s3#OwnerOverride": { "type": "enum", "members": { "Destination": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Destination" } } } }, "com.amazonaws.s3#OwnershipControls": { "type": "structure", "members": { "Rules": { "target": "com.amazonaws.s3#OwnershipControlsRules", "traits": { "smithy.api#documentation": "The container element for an ownership control rule.
", "smithy.api#required": {}, "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Rule" } } }, "traits": { "smithy.api#documentation": "The container element for a bucket's ownership controls.
" } }, "com.amazonaws.s3#OwnershipControlsRule": { "type": "structure", "members": { "ObjectOwnership": { "target": "com.amazonaws.s3#ObjectOwnership", "traits": { "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "The container element for an ownership control rule.
" } }, "com.amazonaws.s3#OwnershipControlsRules": { "type": "list", "member": { "target": "com.amazonaws.s3#OwnershipControlsRule" } }, "com.amazonaws.s3#ParquetInput": { "type": "structure", "members": {}, "traits": { "smithy.api#documentation": "Container for Parquet.
" } }, "com.amazonaws.s3#Part": { "type": "structure", "members": { "PartNumber": { "target": "com.amazonaws.s3#PartNumber", "traits": { "smithy.api#documentation": "Part number identifying the part. This is a positive integer between 1 and 10,000.
" } }, "LastModified": { "target": "com.amazonaws.s3#LastModified", "traits": { "smithy.api#documentation": "Date and time at which the part was uploaded.
" } }, "ETag": { "target": "com.amazonaws.s3#ETag", "traits": { "smithy.api#documentation": "Entity tag returned when the part was uploaded.
" } }, "Size": { "target": "com.amazonaws.s3#Size", "traits": { "smithy.api#documentation": "Size in bytes of the uploaded part data.
" } }, "ChecksumCRC32": { "target": "com.amazonaws.s3#ChecksumCRC32", "traits": { "smithy.api#documentation": "The Base64 encoded, 32-bit CRC32 checksum of the part. This checksum is present if the\n object was uploaded with the CRC32 checksum algorithm. For more information, see Checking object\n integrity in the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the part. This checksum is present if the\n object was uploaded with the CRC32C checksum algorithm. For more information, see Checking object\n integrity in the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the part. This checksum is present if\n the multipart upload request was created with the CRC64NVME checksum algorithm, or if the\n object was uploaded without a checksum (and Amazon S3 added the default checksum, CRC64NVME, to\n the uploaded object). For more information, see Checking object integrity in\n the Amazon S3 User Guide.
The Base64 encoded, 160-bit SHA1 checksum of the part. This checksum is present if the\n object was uploaded with the SHA1 checksum algorithm. For more information, see Checking object\n integrity in the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 checksum of the part. This checksum is present if\n the object was uploaded with the SHA256 checksum algorithm. For more information, see\n Checking\n object integrity in the Amazon S3 User Guide.
Container for elements related to a part.
" } }, "com.amazonaws.s3#PartNumber": { "type": "integer" }, "com.amazonaws.s3#PartNumberMarker": { "type": "string" }, "com.amazonaws.s3#PartitionDateSource": { "type": "enum", "members": { "EventTime": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "EventTime" } }, "DeliveryTime": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "DeliveryTime" } } } }, "com.amazonaws.s3#PartitionedPrefix": { "type": "structure", "members": { "PartitionDateSource": { "target": "com.amazonaws.s3#PartitionDateSource", "traits": { "smithy.api#documentation": "Specifies the partition date source for the partitioned prefix. PartitionDateSource can\n be EventTime or DeliveryTime.
For DeliveryTime, the time in the log file names corresponds to the delivery time for\n the log files.
For EventTime, The logs delivered are for a specific day only. The year, month, and\n day correspond to the day on which the event occurred, and the hour, minutes and seconds are set to 00\n in the key.
Amazon S3 keys for log objects are partitioned in the following format:
\n\n [DestinationPrefix][SourceAccountId]/[SourceRegion]/[SourceBucket]/[YYYY]/[MM]/[DD]/[YYYY]-[MM]-[DD]-[hh]-[mm]-[ss]-[UniqueString]\n
PartitionedPrefix defaults to EventTime delivery when server access logs are delivered.
", "smithy.api#xmlName": "PartitionedPrefix" } }, "com.amazonaws.s3#Parts": { "type": "list", "member": { "target": "com.amazonaws.s3#Part" } }, "com.amazonaws.s3#PartsCount": { "type": "integer" }, "com.amazonaws.s3#PartsList": { "type": "list", "member": { "target": "com.amazonaws.s3#ObjectPart" } }, "com.amazonaws.s3#Payer": { "type": "enum", "members": { "Requester": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Requester" } }, "BucketOwner": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "BucketOwner" } } } }, "com.amazonaws.s3#Permission": { "type": "enum", "members": { "FULL_CONTROL": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "FULL_CONTROL" } }, "WRITE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "WRITE" } }, "WRITE_ACP": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "WRITE_ACP" } }, "READ": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "READ" } }, "READ_ACP": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "READ_ACP" } } } }, "com.amazonaws.s3#Policy": { "type": "string" }, "com.amazonaws.s3#PolicyStatus": { "type": "structure", "members": { "IsPublic": { "target": "com.amazonaws.s3#IsPublic", "traits": { "smithy.api#documentation": "The policy status for this bucket. TRUE indicates that this bucket is public.\n FALSE indicates that the bucket is not public.
The container element for a bucket's policy status.
" } }, "com.amazonaws.s3#Prefix": { "type": "string" }, "com.amazonaws.s3#Priority": { "type": "integer" }, "com.amazonaws.s3#Progress": { "type": "structure", "members": { "BytesScanned": { "target": "com.amazonaws.s3#BytesScanned", "traits": { "smithy.api#documentation": "The current number of object bytes scanned.
" } }, "BytesProcessed": { "target": "com.amazonaws.s3#BytesProcessed", "traits": { "smithy.api#documentation": "The current number of uncompressed object bytes processed.
" } }, "BytesReturned": { "target": "com.amazonaws.s3#BytesReturned", "traits": { "smithy.api#documentation": "The current number of bytes of records payload data returned.
" } } }, "traits": { "smithy.api#documentation": "This data type contains information about progress of an operation.
" } }, "com.amazonaws.s3#ProgressEvent": { "type": "structure", "members": { "Details": { "target": "com.amazonaws.s3#Progress", "traits": { "smithy.api#documentation": "The Progress event details.
", "smithy.api#eventPayload": {} } } }, "traits": { "smithy.api#documentation": "This data type contains information about the progress event of an operation.
" } }, "com.amazonaws.s3#Protocol": { "type": "enum", "members": { "http": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "http" } }, "https": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "https" } } } }, "com.amazonaws.s3#PublicAccessBlockConfiguration": { "type": "structure", "members": { "BlockPublicAcls": { "target": "com.amazonaws.s3#Setting", "traits": { "smithy.api#documentation": "Specifies whether Amazon S3 should block public access control lists (ACLs) for this bucket and objects\n in this bucket. Setting this element to TRUE causes the following behavior:
PUT Bucket ACL and PUT Object ACL calls fail if the specified ACL is public.
\nPUT Object calls fail if the request includes a public ACL.
\nPUT Bucket calls fail if the request includes a public ACL.
\nEnabling this setting doesn't affect existing policies or ACLs.
", "smithy.api#xmlName": "BlockPublicAcls" } }, "IgnorePublicAcls": { "target": "com.amazonaws.s3#Setting", "traits": { "smithy.api#documentation": "Specifies whether Amazon S3 should ignore public ACLs for this bucket and objects in this bucket. Setting\n this element to TRUE causes Amazon S3 to ignore all public ACLs on this bucket and objects in\n this bucket.
Enabling this setting doesn't affect the persistence of any existing ACLs and doesn't prevent new\n public ACLs from being set.
", "smithy.api#xmlName": "IgnorePublicAcls" } }, "BlockPublicPolicy": { "target": "com.amazonaws.s3#Setting", "traits": { "smithy.api#documentation": "Specifies whether Amazon S3 should block public bucket policies for this bucket. Setting this element to\n TRUE causes Amazon S3 to reject calls to PUT Bucket policy if the specified bucket policy\n allows public access.
Enabling this setting doesn't affect existing bucket policies.
", "smithy.api#xmlName": "BlockPublicPolicy" } }, "RestrictPublicBuckets": { "target": "com.amazonaws.s3#Setting", "traits": { "smithy.api#documentation": "Specifies whether Amazon S3 should restrict public bucket policies for this bucket. Setting this element\n to TRUE restricts access to this bucket to only Amazon Web Services service principals and\n authorized users within this account if the bucket has a public policy.
Enabling this setting doesn't affect previously stored bucket policies, except that public and\n cross-account access within any public bucket policy, including non-public delegation to specific\n accounts, is blocked.
", "smithy.api#xmlName": "RestrictPublicBuckets" } } }, "traits": { "smithy.api#documentation": "The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can enable the\n configuration options in any combination. For more information about when Amazon S3 considers a bucket or\n object public, see The Meaning of \"Public\" in the Amazon S3 User Guide.
" } }, "com.amazonaws.s3#PutBucketAccelerateConfiguration": { "type": "operation", "input": { "target": "com.amazonaws.s3#PutBucketAccelerateConfigurationRequest" }, "output": { "target": "smithy.api#Unit" }, "traits": { "aws.protocols#httpChecksum": { "requestAlgorithmMember": "ChecksumAlgorithm" }, "smithy.api#documentation": "This operation is not supported for directory buckets.
\nSets the accelerate configuration of an existing bucket. Amazon S3 Transfer Acceleration is a\n bucket-level feature that enables you to perform faster data transfers to Amazon S3.
\n To use this operation, you must have permission to perform the\n s3:PutAccelerateConfiguration action. The bucket owner has this permission by default.\n 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\n Resources.
The Transfer Acceleration state of a bucket can be set to one of the following two values:
\nEnabled \u2013 Enables accelerated data transfers to the bucket.
\nSuspended \u2013 Disables accelerated data transfers to the bucket.
\nThe GetBucketAccelerateConfiguration action returns the transfer acceleration state of a\n bucket.
\nAfter setting the Transfer Acceleration state of a bucket to Enabled, it might take up to thirty\n minutes before the data transfer rates to the bucket increase.
\nThe name of the bucket used for Transfer Acceleration must be DNS-compliant and must not contain\n periods (\".\").
\nFor more information about transfer acceleration, see Transfer Acceleration.
\nThe following operations are related to PutBucketAccelerateConfiguration:
\n CreateBucket\n
\nThe name of the bucket for which the accelerate configuration is set.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "AccelerateConfiguration": { "target": "com.amazonaws.s3#AccelerateConfiguration", "traits": { "smithy.api#documentation": "Container for setting the transfer acceleration state.
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "AccelerateConfiguration" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
End of support notice: Beginning October 1, 2025, Amazon S3 will discontinue support for creating new Email Grantee Access Control Lists (ACL). \n Email Grantee ACLs created prior to this date will continue to work and remain accessible through the Amazon Web Services Management Console, Command Line Interface (CLI), SDKs, \n and REST API. However, you will no longer be able to create new Email Grantee ACLs.\n
\nThis change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nThis operation is not supported for directory buckets.
\nSets the permissions on an existing bucket using access control lists (ACL). For more information,\n see Using ACLs. To\n set the ACL of a bucket, you must have the WRITE_ACP permission.
You can use one of the following two ways to set a bucket's permissions:
\nSpecify the ACL in the request body
\nSpecify permissions using request headers
\nYou cannot specify access permission using both the body and the request headers.
\nDepending on your application needs, you may choose to set the ACL on a bucket using either the\n request body or the headers. For example, if you have an existing application that updates a bucket ACL\n using the request body, then you can continue to use that approach.
\nIf your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs are disabled\n and no longer affect permissions. You must use policies to grant access to your bucket and the objects\n in it. Requests to set ACLs or update ACLs fail and return the\n AccessControlListNotSupported error code. Requests to read ACLs are still supported.\n For more information, see Controlling object ownership in\n the Amazon S3 User Guide.
You can set access permissions by using one of the following methods:
\nSpecify a canned ACL with the x-amz-acl request header. Amazon S3 supports a set\n of predefined ACLs, known as canned ACLs. Each canned ACL has a\n predefined set of grantees and permissions. Specify the canned ACL name as the value of\n x-amz-acl. If you use this header, you cannot use other access control-specific\n headers in your request. For more information, see Canned ACL.
Specify access permissions explicitly with the x-amz-grant-read,\n x-amz-grant-read-acp, x-amz-grant-write-acp, and\n x-amz-grant-full-control headers. When using these headers, you specify\n explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3 groups) who will receive the\n permission. If you use these ACL-specific headers, you cannot use the x-amz-acl\n header to set a canned ACL. These parameters map to the set of permissions that Amazon S3 supports\n in an ACL. For more information, see Access Control List (ACL)\n Overview.
You specify each grantee as a type=value pair, where the type is one of the\n following:
\n\n id \u2013 if the value specified is the canonical user ID of an\n Amazon Web Services account
\n uri \u2013 if you are granting permissions to a predefined group
\n emailAddress \u2013 if the value specified is the email address of an\n Amazon Web Services account
Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:
\nUS East (N. Virginia)
\nUS West (N. California)
\nUS West (Oregon)
\nAsia Pacific (Singapore)
\nAsia Pacific (Sydney)
\nAsia Pacific (Tokyo)
\nEurope (Ireland)
\nSouth America (S\u00e3o Paulo)
\nFor a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the Amazon Web Services General Reference.
\nFor example, the following x-amz-grant-write header grants create, overwrite,\n and delete objects permission to LogDelivery group predefined by Amazon S3 and two Amazon Web Services accounts\n identified by their email addresses.
\n x-amz-grant-write: uri=\"http://acs.amazonaws.com/groups/s3/LogDelivery\",\n id=\"111122223333\", id=\"555566667777\" \n
You can use either a canned ACL or specify access permissions explicitly. You cannot do\n both.
\nYou can specify the person (grantee) to whom you're assigning access rights (using request\n elements) in the following ways. For examples of how to specify these grantee values in JSON\n format, see the Amazon Web Services CLI example in Enabling Amazon S3 server\n access logging in the Amazon S3 User Guide.
\nBy the person's ID:
\n\n
DisplayName is optional and ignored in the request
\nBy URI:
\n\n
By Email address:
\n\n
The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl\n request, appears as the CanonicalUser.
\nUsing email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:
\nUS East (N. Virginia)
\nUS West (N. California)
\nUS West (Oregon)
\nAsia Pacific (Singapore)
\nAsia Pacific (Sydney)
\nAsia Pacific (Tokyo)
\nEurope (Ireland)
\nSouth America (S\u00e3o Paulo)
\nFor a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the Amazon Web Services General Reference.
\nThe following operations are related to PutBucketAcl:
\n CreateBucket\n
\n\n DeleteBucket\n
\n\n GetObjectAcl\n
\nThe canned ACL to apply to the bucket.
", "smithy.api#httpHeader": "x-amz-acl" } }, "AccessControlPolicy": { "target": "com.amazonaws.s3#AccessControlPolicy", "traits": { "smithy.api#documentation": "Contains the elements that set the ACL permissions for an object per grantee.
", "smithy.api#httpPayload": {}, "smithy.api#xmlName": "AccessControlPolicy" } }, "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket to which to apply the ACL.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "The Base64 encoded 128-bit MD5 digest of the data. This header must be used as a\n message integrity check to verify that the request body was not corrupted in transit. For more\n information, go to RFC 1864.\n
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.
", "smithy.api#httpHeader": "x-amz-grant-full-control" } }, "GrantRead": { "target": "com.amazonaws.s3#GrantRead", "traits": { "smithy.api#documentation": "Allows grantee to list the objects in the bucket.
", "smithy.api#httpHeader": "x-amz-grant-read" } }, "GrantReadACP": { "target": "com.amazonaws.s3#GrantReadACP", "traits": { "smithy.api#documentation": "Allows grantee to read the bucket ACL.
", "smithy.api#httpHeader": "x-amz-grant-read-acp" } }, "GrantWrite": { "target": "com.amazonaws.s3#GrantWrite", "traits": { "smithy.api#documentation": "Allows grantee to create new objects in the bucket.
\nFor the bucket and object owners of existing objects, also allows deletions and overwrites of those\n objects.
", "smithy.api#httpHeader": "x-amz-grant-write" } }, "GrantWriteACP": { "target": "com.amazonaws.s3#GrantWriteACP", "traits": { "smithy.api#documentation": "Allows grantee to write the ACL for the applicable bucket.
", "smithy.api#httpHeader": "x-amz-grant-write-acp" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nSets an analytics configuration for the bucket (specified by the analytics configuration ID). You\n can have up to 1,000 analytics configurations per bucket.
\nYou can choose to have storage class analysis export analysis reports sent to a comma-separated\n values (CSV) flat file. See the DataExport request element. Reports are updated daily and\n are based on the object filters that you configure. When selecting data export, you specify a\n destination bucket and an optional destination prefix where the file is written. You can export the data\n to a destination bucket in a different account. However, the destination bucket must be in the same\n Region as the bucket that you are making the PUT analytics configuration to. For more information, see\n Amazon S3 Analytics \u2013\n Storage Class Analysis.
You must create a bucket policy on the destination bucket where the exported file is written to\n grant permissions to Amazon S3 to write objects to the bucket. For an example policy, see Granting\n Permissions for Amazon S3 Inventory and Storage Class Analysis.
\nTo use this operation, you must have permissions to perform the\n s3:PutAnalyticsConfiguration action. The bucket owner has this permission by default. The\n 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\n Resources.
\n PutBucketAnalyticsConfiguration has the following special errors:
\n HTTP Error: HTTP 400 Bad Request\n
\n\n Code: InvalidArgument\n
\n\n Cause: Invalid argument.\n
\n\n HTTP Error: HTTP 400 Bad Request\n
\n\n Code: TooManyConfigurations\n
\n\n Cause: You are attempting to create a new configuration but have already reached\n the 1,000-configuration limit.\n
\n\n HTTP Error: HTTP 403 Forbidden\n
\n\n Code: AccessDenied\n
\n\n Cause: You are not the owner of the specified bucket, or you do not have the\n s3:PutAnalyticsConfiguration bucket permission to set the configuration on the\n bucket.\n
\nThe following operations are related to PutBucketAnalyticsConfiguration:
The name of the bucket to which an analytics configuration is stored.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Id": { "target": "com.amazonaws.s3#AnalyticsId", "traits": { "smithy.api#documentation": "The ID that identifies the analytics configuration.
", "smithy.api#httpQuery": "id", "smithy.api#required": {} } }, "AnalyticsConfiguration": { "target": "com.amazonaws.s3#AnalyticsConfiguration", "traits": { "smithy.api#documentation": "The configuration and any analyses for the analytics filter.
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "AnalyticsConfiguration" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nSets the cors configuration for your bucket. If the configuration exists, Amazon S3 replaces\n it.
To use this operation, you must be allowed to perform the s3:PutBucketCORS action. By\n default, the bucket owner has this permission and can grant it to others.
You set this configuration on a bucket so that the bucket can service cross-origin requests. For\n example, you might want to enable a request whose origin is http://www.example.com to\n access your Amazon S3 bucket at my.example.bucket.com by using the browser's\n XMLHttpRequest capability.
To enable cross-origin resource sharing (CORS) on a bucket, you add the cors\n subresource to the bucket. The cors subresource is an XML document in which you configure\n rules that identify origins and the HTTP methods that can be executed on your bucket. The document is\n limited to 64 KB in size.
When Amazon S3 receives a cross-origin request (or a pre-flight OPTIONS request) against a bucket, it\n evaluates the cors configuration on the bucket and uses the first CORSRule\n rule that matches the incoming browser request to enable a cross-origin request. For a rule to match,\n the following conditions must be met:
The request's Origin header must match AllowedOrigin elements.
The request method (for example, GET, PUT, HEAD, and so on) or the\n Access-Control-Request-Method header in case of a pre-flight OPTIONS\n request must be one of the AllowedMethod elements.
Every header specified in the Access-Control-Request-Headers request header of a\n pre-flight request must match an AllowedHeader element.
For more information about CORS, go to Enabling Cross-Origin Resource Sharing in the\n Amazon S3 User Guide.
\nThe following operations are related to PutBucketCors:
\n GetBucketCors\n
\n\n DeleteBucketCors\n
\n\n RESTOPTIONSobject\n
\nSpecifies the bucket impacted by the corsconfiguration.
Describes the cross-origin access configuration for objects in an Amazon S3 bucket. For more information,\n see Enabling Cross-Origin Resource\n Sharing in the Amazon S3 User Guide.
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "CORSConfiguration" } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "The Base64 encoded 128-bit MD5 digest of the data. This header must be used as a\n message integrity check to verify that the request body was not corrupted in transit. For more\n information, go to RFC 1864.\n
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation configures default encryption and Amazon S3 Bucket Keys for an existing bucket.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. \nFor more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
By default, all buckets have a default encryption configuration that uses server-side encryption\n with Amazon S3 managed keys (SSE-S3).
\n\n General purpose buckets\n
\nYou can optionally configure default encryption for a bucket by using server-side\n encryption with Key Management Service (KMS) keys (SSE-KMS) or dual-layer server-side encryption with\n Amazon Web Services KMS keys (DSSE-KMS). If you specify default encryption by using SSE-KMS, you can also\n configure Amazon S3 Bucket\n Keys. For information about the bucket default encryption feature, see Amazon S3 Bucket Default\n Encryption in the Amazon S3 User Guide.
\nIf you use PutBucketEncryption to set your default bucket encryption to\n SSE-KMS, you should verify that your KMS key ID is correct. Amazon S3 doesn't validate the\n KMS key ID provided in PutBucketEncryption requests.
\n\n Directory buckets - You can optionally configure\n default encryption for a bucket by using server-side encryption with Key Management Service (KMS) keys\n (SSE-KMS).
\nWe recommend that the bucket's default encryption uses the desired encryption\n configuration and you don't override the bucket default encryption in your\n CreateSession requests or PUT object requests. Then, new objects\n are automatically encrypted with the desired encryption settings.\n For more information about the encryption overriding behaviors in directory buckets, see Specifying server-side encryption with KMS for new object uploads.
Your SSE-KMS configuration can only support 1 customer managed key per directory bucket's lifetime. \nThe Amazon Web Services managed key (aws/s3) isn't supported. \n
S3 Bucket Keys are always enabled for GET and PUT operations in a directory bucket and can\u2019t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through CopyObject, UploadPartCopy, the Copy operation in Batch Operations, or \n the import jobs. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.
When you specify an KMS customer managed key for encryption in your directory bucket, only use the key ID or key ARN. The key alias format of the KMS key isn't supported.
\nFor directory buckets, if you use PutBucketEncryption to set your default bucket\n encryption to SSE-KMS, Amazon S3 validates the KMS key ID provided in\n PutBucketEncryption requests.
\nIf you're specifying a customer managed KMS key, we recommend using a fully qualified KMS key\n ARN. If you use a KMS key alias instead, then KMS resolves the key within the requester\u2019s account.\n This behavior can result in data that's encrypted with a KMS key that belongs to the requester, and\n not the bucket owner.
\nAlso, this action requires Amazon Web Services Signature Version 4. For more information, see Authenticating\n Requests (Amazon Web Services Signature Version 4).
\n\n General purpose bucket permissions - The\n s3:PutEncryptionConfiguration permission is required in a policy. The bucket\n owner has this permission by default. The bucket owner can grant this permission to others.\n For more information about permissions, see Permissions Related to Bucket Operations and Managing Access Permissions to Your\n Amazon S3 Resources in the Amazon S3 User Guide.
\n Directory bucket permissions - To grant access to\n this API operation, you must have the s3express:PutEncryptionConfiguration\n permission in an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.\n For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
To set a directory bucket default encryption with SSE-KMS, you must also have the\n kms:GenerateDataKey and the kms:Decrypt permissions in IAM\n identity-based policies and KMS key policies for the target KMS key.
\n Directory buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following operations are related to PutBucketEncryption:
\n GetBucketEncryption\n
\nSpecifies default encryption for a bucket using server-side encryption with different key\n options.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n DOC-EXAMPLE-BUCKET--usw2-az1--x-s3). For information about bucket naming restrictions, see Directory bucket naming rules in the Amazon S3 User Guide\n
The Base64 encoded 128-bit MD5 digest of the server-side encryption\n configuration.
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
\nThis functionality is not supported for directory buckets.
\nIndicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
For directory buckets, when you use Amazon Web Services SDKs, CRC32 is the default checksum algorithm that's used for performance.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
For directory buckets, this header is not supported in this API operation. If you specify this header, the request fails with the HTTP status code \n501 Not Implemented.
This operation is not supported for directory buckets.
\nPuts a S3 Intelligent-Tiering configuration to the specified bucket. You can have up to 1,000\n S3 Intelligent-Tiering configurations per bucket.
\nThe S3 Intelligent-Tiering storage class is designed to optimize storage costs by automatically moving data to the most cost-effective storage access tier, without performance impact or operational overhead. S3 Intelligent-Tiering delivers automatic cost savings in three low latency and high throughput access tiers. To get the lowest storage cost on data that can be accessed in minutes to hours, you can choose to activate additional archiving capabilities.
\nThe S3 Intelligent-Tiering storage class is the ideal storage class for data with unknown, changing, or unpredictable access patterns, independent of object size or retention period. If the size of an object is less than 128 KB, it is not monitored and not eligible for auto-tiering. Smaller objects can be stored, but they are always charged at the Frequent Access tier rates in the S3 Intelligent-Tiering storage class.
\nFor more information, see Storage class for automatically optimizing frequently and infrequently accessed objects.
\nOperations related to PutBucketIntelligentTieringConfiguration include:
You only need S3 Intelligent-Tiering enabled on a bucket if you want to automatically move objects\n stored in the S3 Intelligent-Tiering storage class to the Archive Access or Deep Archive Access\n tier.
\n\n PutBucketIntelligentTieringConfiguration has the following special errors:
\n Code: InvalidArgument
\n\n Cause: Invalid Argument
\n\n Code: TooManyConfigurations
\n\n Cause: You are attempting to create a new configuration but have already\n reached the 1,000-configuration limit.
\n\n Cause: You are not the owner of the specified bucket, or you do not have\n the s3:PutIntelligentTieringConfiguration bucket permission to set the configuration\n on the bucket.
The name of the Amazon S3 bucket whose configuration you want to modify or retrieve.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Id": { "target": "com.amazonaws.s3#IntelligentTieringId", "traits": { "smithy.api#documentation": "The ID used to identify the S3 Intelligent-Tiering configuration.
", "smithy.api#httpQuery": "id", "smithy.api#required": {} } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Container for S3 Intelligent-Tiering configuration.
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "IntelligentTieringConfiguration" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#PutBucketInventoryConfiguration": { "type": "operation", "input": { "target": "com.amazonaws.s3#PutBucketInventoryConfigurationRequest" }, "output": { "target": "smithy.api#Unit" }, "traits": { "smithy.api#documentation": "This operation is not supported for directory buckets.
\nThis implementation of the PUT action adds an S3 Inventory configuration (identified by\n the inventory ID) to the bucket. You can have up to 1,000 inventory configurations per bucket.
Amazon S3 inventory generates inventories of the objects in the bucket on a daily or weekly basis, and\n the results are published to a flat file. The bucket that is inventoried is called the\n source bucket, and the bucket where the inventory flat file is stored is called\n the destination bucket. The destination bucket must be in the\n same Amazon Web Services Region as the source bucket.
\nWhen you configure an inventory for a source bucket, you specify the\n destination bucket where you want the inventory to be stored, and whether to\n generate the inventory daily or weekly. You can also configure what object metadata to include and\n whether to inventory all object versions or only current versions. For more information, see Amazon S3 Inventory in the\n Amazon S3 User Guide.
\nYou must create a bucket policy on the destination bucket to grant\n permissions to Amazon S3 to write objects to the bucket in the defined location. For an example policy, see\n Granting\n Permissions for Amazon S3 Inventory and Storage Class Analysis.
\nTo use this operation, you must have permission to perform the\n s3:PutInventoryConfiguration action. The bucket owner has this permission by\n default and can grant this permission to others.
The s3:PutInventoryConfiguration permission allows a user to create an S3 Inventory\n report that includes all object metadata fields available and to specify the destination bucket to\n store the inventory. A user with read access to objects in the destination bucket can also access\n all object metadata fields that are available in the inventory report.
To restrict access to an inventory report, see Restricting access to an Amazon S3 Inventory report in the\n Amazon S3 User Guide. For more information about the metadata fields available\n in S3 Inventory, see Amazon S3 Inventory\n lists in the Amazon S3 User Guide. For more information about\n permissions, see Permissions related to bucket subresource operations and Identity and access management in\n Amazon S3 in the Amazon S3 User Guide.
\n\n PutBucketInventoryConfiguration has the following special errors:
\n Code: InvalidArgument
\n\n Cause: Invalid Argument
\n\n Code: TooManyConfigurations
\n\n Cause: You are attempting to create a new configuration but have already\n reached the 1,000-configuration limit.
\n\n Cause: You are not the owner of the specified bucket, or you do not have\n the s3:PutInventoryConfiguration bucket permission to set the configuration on the\n bucket.
The following operations are related to PutBucketInventoryConfiguration:
The name of the bucket where the inventory configuration will be stored.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Id": { "target": "com.amazonaws.s3#InventoryId", "traits": { "smithy.api#documentation": "The ID used to identify the inventory configuration.
", "smithy.api#httpQuery": "id", "smithy.api#required": {} } }, "InventoryConfiguration": { "target": "com.amazonaws.s3#InventoryConfiguration", "traits": { "smithy.api#documentation": "Specifies the inventory configuration.
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "InventoryConfiguration" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle\n configuration. Keep in mind that this will overwrite an existing lifecycle configuration, so if you want\n to retain any configuration details, they must be included in the new lifecycle configuration. For\n information about lifecycle configuration, see Managing your storage\n lifecycle.
\nBucket lifecycle configuration now supports specifying a lifecycle rule using an object key name\n prefix, one or more object tags, object size, or any combination of these. Accordingly, this section\n describes the latest API. The previous version of the API supported filtering based only on an object\n key name prefix, which is supported for backward compatibility. For the related API description, see\n PutBucketLifecycle.
\nYou specify the lifecycle configuration in your request body. The lifecycle configuration is\n specified as XML consisting of one or more rules. An Amazon S3 Lifecycle configuration can have up to\n 1,000 rules. This limit is not adjustable.
\nBucket lifecycle configuration supports specifying a lifecycle rule using an object key name\n prefix, one or more object tags, object size, or any combination of these. Accordingly, this\n section describes the latest API. The previous version of the API supported filtering based only\n on an object key name prefix, which is supported for backward compatibility for general purpose\n buckets. For the related API description, see PutBucketLifecycle.
\nLifecyle configurations for directory buckets only support expiring objects and cancelling\n multipart uploads. Expiring of versioned objects,transitions and tag filters are not\n supported.
\nA lifecycle rule consists of the following:
\nA filter identifying a subset of objects to which the rule applies. The filter can be\n based on a key name prefix, object tags, object size, or any combination of these.
\nA status indicating whether the rule is in effect.
\nOne or more lifecycle transition and expiration actions that you want Amazon S3 to perform on\n the objects identified by the filter. If the state of your bucket is versioning-enabled or\n versioning-suspended, you can have many versions of the same object (one current version and\n zero or more noncurrent versions). Amazon S3 provides predefined actions that you can specify for\n current and noncurrent object versions.
\nFor more information, see Object Lifecycle Management and\n Lifecycle\n Configuration Elements.
\n\n General purpose bucket permissions - By default, all Amazon S3\n resources are private, including buckets, objects, and related subresources (for example,\n lifecycle configuration and website configuration). Only the resource owner (that is, the\n Amazon Web Services account that created it) can access the resource. The resource owner can optionally\n grant access permissions to others by writing an access policy. For this operation, a user\n must have the s3:PutLifecycleConfiguration permission.
You can also explicitly deny permissions. An explicit deny also supersedes any other\n permissions. If you want to block users or accounts from removing or deleting objects from\n your bucket, you must deny them permissions for the following actions:
\n\n s3:DeleteObject\n
\n s3:DeleteObjectVersion\n
\n s3:PutLifecycleConfiguration\n
For more information about permissions, see Managing Access Permissions to\n Your Amazon S3 Resources.
\n\n Directory bucket permissions - You must have the\n s3express:PutLifecycleConfiguration permission in an IAM identity-based policy\n to use this operation. Cross-account access to this API operation isn't supported. The\n resource owner can optionally grant access permissions to others by creating a role or user\n for them as long as they are within the same account as the owner and resource.
For more information about directory bucket policies and permissions, see Authorizing Regional endpoint APIs with IAM in the Amazon S3 User\n Guide.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. \nFor more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n Directory buckets - The HTTP Host header syntax is\n s3express-control.region.amazonaws.com.
The following operations are related to PutBucketLifecycleConfiguration:
Indicates which default minimum object size behavior is applied to the lifecycle\n configuration.
\nThis parameter applies to general purpose buckets only. It is not supported for directory bucket\n lifecycle configurations.
\n\n all_storage_classes_128K - Objects smaller than 128 KB will not transition to\n any storage class by default.
\n varies_by_storage_class - Objects smaller than 128 KB will transition to Glacier\n Flexible Retrieval or Glacier Deep Archive storage classes. By default, all other storage classes\n will prevent transitions smaller than 128 KB.
To customize the minimum object size for any transition you can add a filter that specifies a custom\n ObjectSizeGreaterThan or ObjectSizeLessThan in the body of your transition\n rule. Custom filters always take precedence over the default transition behavior.
The name of the bucket for which to set the configuration.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
Container for lifecycle rules. You can add as many as 1,000 rules.
", "smithy.api#httpPayload": {}, "smithy.api#xmlName": "LifecycleConfiguration" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This parameter applies to general purpose buckets only. It is not supported for directory bucket\n lifecycle configurations.
\nIndicates which default minimum object size behavior is applied to the lifecycle\n configuration.
\nThis parameter applies to general purpose buckets only. It is not supported for directory bucket\n lifecycle configurations.
\n\n all_storage_classes_128K - Objects smaller than 128 KB will not transition to\n any storage class by default.
\n varies_by_storage_class - Objects smaller than 128 KB will transition to Glacier\n Flexible Retrieval or Glacier Deep Archive storage classes. By default, all other storage classes\n will prevent transitions smaller than 128 KB.
To customize the minimum object size for any transition you can add a filter that specifies a custom\n ObjectSizeGreaterThan or ObjectSizeLessThan in the body of your transition\n rule. Custom filters always take precedence over the default transition behavior.
End of support notice: Beginning October 1, 2025, Amazon S3 will discontinue support for creating new Email Grantee Access Control Lists (ACL). \n Email Grantee ACLs created prior to this date will continue to work and remain accessible through the Amazon Web Services Management Console, Command Line Interface (CLI), SDKs, \n and REST API. However, you will no longer be able to create new Email Grantee ACLs.\n
\nThis change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nThis operation is not supported for directory buckets.
\nSet the logging parameters for a bucket and to specify permissions for who can view and modify the\n logging parameters. All logs are saved to buckets in the same Amazon Web Services Region as the source bucket. To set\n the logging status of a bucket, you must be the bucket owner.
\nThe bucket owner is automatically granted FULL_CONTROL to all logs. You use the Grantee\n request element to grant access to other people. The Permissions request element specifies\n the kind of access the grantee has to the logs.
If the target bucket for log delivery uses the bucket owner enforced setting for S3 Object\n Ownership, you can't use the Grantee request element to grant access to others.\n Permissions can only be granted using policies. For more information, see Permissions for server access log delivery in the\n Amazon S3 User Guide.
You can specify the person (grantee) to whom you're assigning access rights (by using request\n elements) in the following ways. For examples of how to specify these grantee values in JSON\n format, see the Amazon Web Services CLI example in Enabling Amazon S3 server\n access logging in the Amazon S3 User Guide.
\nBy the person's ID:
\n\n
\n DisplayName is optional and ignored in the request.
By Email address:
\n\n \n
The grantee is resolved to the CanonicalUser and, in a response to a\n GETObjectAcl request, appears as the CanonicalUser.
By URI:
\n\n
To enable logging, you use LoggingEnabled and its children request elements. To disable\n logging, you use an empty BucketLoggingStatus request element:
\n
For more information about server access logging, see Server Access Logging in the\n Amazon S3 User Guide.
\nFor more information about creating a bucket, see CreateBucket. For more information about\n returning the logging status of a bucket, see GetBucketLogging.
\nThe following operations are related to PutBucketLogging:
\n PutObject\n
\n\n DeleteBucket\n
\n\n CreateBucket\n
\n\n GetBucketLogging\n
\nThe name of the bucket for which to set the logging parameters.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "BucketLoggingStatus": { "target": "com.amazonaws.s3#BucketLoggingStatus", "traits": { "smithy.api#documentation": "Container for logging status information.
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "BucketLoggingStatus" } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "The MD5 hash of the PutBucketLogging request body.
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nSets a metrics configuration (specified by the metrics configuration ID) for the bucket. You can\n have up to 1,000 metrics configurations per bucket. If you're updating an existing metrics\n configuration, note that this is a full replacement of the existing metrics configuration. If you don't\n include the elements you want to keep, they are erased.
\nTo use this operation, you must have permissions to perform the\n s3:PutMetricsConfiguration action. The bucket owner has this permission by default. The\n 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\n Resources.
For information about CloudWatch request metrics for Amazon S3, see Monitoring Metrics with Amazon\n CloudWatch.
\nThe following operations are related to PutBucketMetricsConfiguration:
\n PutBucketMetricsConfiguration has the following special error:
Error code: TooManyConfigurations\n
Description: You are attempting to create a new configuration but have already reached the\n 1,000-configuration limit.
\nHTTP Status Code: HTTP 400 Bad Request
\nThe name of the bucket for which the metrics configuration is set.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Id": { "target": "com.amazonaws.s3#MetricsId", "traits": { "smithy.api#documentation": "The ID used to identify the metrics configuration. The ID has a 64 character limit and can only\n contain letters, numbers, periods, dashes, and underscores.
", "smithy.api#httpQuery": "id", "smithy.api#required": {} } }, "MetricsConfiguration": { "target": "com.amazonaws.s3#MetricsConfiguration", "traits": { "smithy.api#documentation": "Specifies the metrics configuration.
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "MetricsConfiguration" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nEnables notifications of specified events for a bucket. For more information about event\n notifications, see Configuring Event Notifications.
\nUsing this API, you can replace an existing notification configuration. The configuration is an XML\n file that defines the event types that you want Amazon S3 to publish and the destination where you want Amazon S3\n to publish an event notification when it detects an event of the specified type.
\nBy default, your bucket has no event notifications configured. That is, the notification\n configuration will be an empty NotificationConfiguration.
\n
\n \n
This action replaces the existing notification configuration with the configuration you include in\n the request body.
\nAfter Amazon S3 receives this request, it first verifies that any Amazon Simple Notification Service\n (Amazon SNS) or Amazon Simple Queue Service (Amazon SQS) destination exists, and that the bucket owner\n has permission to publish to it by sending a test notification. In the case of Lambda destinations,\n Amazon S3 verifies that the Lambda function permissions grant Amazon S3 permission to invoke the function from the\n Amazon S3 bucket. For more information, see Configuring Notifications for Amazon S3\n Events.
\nYou can disable notifications by adding the empty NotificationConfiguration element.
\nFor more information about the number of event notification configurations that you can create per\n bucket, see Amazon S3 service\n quotas in Amazon Web Services General Reference.
\nBy default, only the bucket owner can configure notifications on a bucket. However, bucket owners\n can use a bucket policy to grant permission to other users to set this configuration with the required\n s3:PutBucketNotification permission.
The PUT notification is an atomic operation. For example, suppose your notification configuration\n includes SNS topic, SQS queue, and Lambda function configurations. When you send a PUT request with\n this configuration, Amazon S3 sends test messages to your SNS topic. If the message fails, the entire PUT\n action will fail, and Amazon S3 will not add the configuration to your bucket.
\nIf the configuration in the request body includes only one TopicConfiguration\n specifying only the s3:ReducedRedundancyLostObject event type, the response will also\n include the x-amz-sns-test-message-id header containing the message ID of the test\n notification sent to the topic.
The following action is related to PutBucketNotificationConfiguration:
The name of the bucket.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "NotificationConfiguration": { "target": "com.amazonaws.s3#NotificationConfiguration", "traits": { "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "NotificationConfiguration" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Skips validation of Amazon SQS, Amazon SNS, and Lambda destinations.\n True or false value.
", "smithy.api#httpHeader": "x-amz-skip-destination-validation" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#PutBucketOwnershipControls": { "type": "operation", "input": { "target": "com.amazonaws.s3#PutBucketOwnershipControlsRequest" }, "output": { "target": "smithy.api#Unit" }, "traits": { "aws.protocols#httpChecksum": { "requestAlgorithmMember": "ChecksumAlgorithm", "requestChecksumRequired": true }, "smithy.api#documentation": "This operation is not supported for directory buckets.
\nCreates or modifies OwnershipControls for an Amazon S3 bucket. To use this operation, you\n must have the s3:PutBucketOwnershipControls permission. For more information about Amazon S3\n permissions, see Specifying permissions in a policy.
For information about Amazon S3 Object Ownership, see Using object ownership.
\nThe following operations are related to PutBucketOwnershipControls:
The name of the Amazon S3 bucket whose OwnershipControls you want to set.
The MD5 hash of the OwnershipControls request body.
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The OwnershipControls (BucketOwnerEnforced, BucketOwnerPreferred, or ObjectWriter) that\n you want to apply to this Amazon S3 bucket.
Indicates the algorithm used to create the checksum for the object when you use the SDK. This\n header will not provide any additional functionality if you don't use the SDK. When you send this\n header, there must be a corresponding x-amz-checksum-algorithm\n header\n sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
Applies an Amazon S3 bucket policy to an Amazon S3 bucket.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. \nFor more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
If you are using an identity other than the root user of the Amazon Web Services account that owns the\n bucket, the calling identity must both have the PutBucketPolicy permissions on the\n specified bucket and belong to the bucket owner's account in order to use this operation.
If you don't have PutBucketPolicy permissions, Amazon S3 returns a 403 Access\n Denied error. If you have the correct permissions, but you're not using an identity that\n belongs to the bucket owner's account, Amazon S3 returns a 405 Method Not Allowed\n error.
To ensure that bucket owners don't inadvertently lock themselves out of their own buckets,\n the root principal in a bucket owner's Amazon Web Services account can perform the\n GetBucketPolicy, PutBucketPolicy, and\n DeleteBucketPolicy API actions, even if their bucket policy explicitly denies the\n root principal's access. Bucket owner root principals can only be blocked from performing these\n API actions by VPC endpoint policies and Amazon Web Services Organizations policies.
\n General purpose bucket permissions - The\n s3:PutBucketPolicy permission is required in a policy. For more information\n about general purpose buckets bucket policies, see Using Bucket Policies and User\n Policies in the Amazon S3 User Guide.
\n Directory bucket permissions - To grant access to\n this API operation, you must have the s3express:PutBucketPolicy permission in\n an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.\n For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
\n General purpose buckets example bucket policies - See Bucket policy\n examples in the Amazon S3 User Guide.
\n\n Directory bucket example bucket policies - See Example\n bucket policies for S3 Express One Zone in the Amazon S3 User Guide.
\n\n Directory buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following operations are related to PutBucketPolicy:
\n CreateBucket\n
\n\n DeleteBucket\n
\nThe name of the bucket.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n DOC-EXAMPLE-BUCKET--usw2-az1--x-s3). For information about bucket naming restrictions, see Directory bucket naming rules in the Amazon S3 User Guide\n
The MD5 hash of the request body.
\nFor requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
\nThis functionality is not supported for directory buckets.
\nIndicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum-algorithm\n or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request.
For the x-amz-checksum-algorithm\n header, replace \n algorithm\n with the supported algorithm from the following list:
\n CRC32\n
\n CRC32C\n
\n CRC64NVME\n
\n SHA1\n
\n SHA256\n
For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
\nIf the individual checksum value you provide through x-amz-checksum-algorithm\n doesn't match the checksum algorithm you set through x-amz-sdk-checksum-algorithm, Amazon S3 fails the request with a BadDigest error.
For directory buckets, when you use Amazon Web Services SDKs, CRC32 is the default checksum algorithm that's used for performance.
Set this parameter to true to confirm that you want to remove your permissions to change this bucket\n policy in the future.
\nThis functionality is not supported for directory buckets.
\nThe bucket policy as a JSON document.
\nFor directory buckets, the only IAM action supported in the bucket policy is\n s3express:CreateSession.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
For directory buckets, this header is not supported in this API operation. If you specify this header, the request fails with the HTTP status code \n501 Not Implemented.
This operation is not supported for directory buckets.
\nCreates a replication configuration or replaces an existing one. For more information, see Replication in the\n Amazon S3 User Guide.
\nSpecify the replication configuration in the request body. In the replication configuration, you\n provide the name of the destination bucket or buckets where you want Amazon S3 to replicate objects, the\n IAM role that Amazon S3 can assume to replicate objects on your behalf, and other relevant information. You\n can invoke this request for a specific Amazon Web Services Region by using the \n aws:RequestedRegion\n condition key.
A replication configuration must include at least one rule, and can contain a maximum of 1,000. Each\n rule identifies a subset of objects to replicate by filtering the objects in the source bucket. To\n choose additional subsets of objects to replicate, add a rule for each subset.
\nTo specify a subset of the objects in the source bucket to apply a replication rule to, add the\n Filter element as a child of the Rule element. You can filter objects based on an object key prefix, one\n or more object tags, or both. When you add the Filter element in the configuration, you must also add\n the following elements: DeleteMarkerReplication, Status, and\n Priority.
If you are using an earlier version of the replication configuration, Amazon S3 handles replication of\n delete markers differently. For more information, see Backward Compatibility.
\nFor information about enabling versioning on a bucket, see Using Versioning.
\nBy default, Amazon S3 doesn't replicate objects that are stored at rest using server-side\n encryption with KMS keys. To replicate Amazon Web Services KMS-encrypted objects, add the following:\n SourceSelectionCriteria, SseKmsEncryptedObjects, Status,\n EncryptionConfiguration, and ReplicaKmsKeyID. For information about\n replication configuration, see Replicating Objects Created\n with SSE Using KMS keys.
For information on PutBucketReplication errors, see List of\n replication-related error codes\n
To create a PutBucketReplication request, you must have\n s3:PutReplicationConfiguration permissions for the bucket.\n \n
By default, a resource owner, in this case the Amazon Web Services account that created the bucket, can\n perform this operation. The resource owner can also grant others permissions to perform the\n operation. For more information about permissions, see Specifying Permissions in a Policy\n and Managing\n Access Permissions to Your Amazon S3 Resources.
\nTo perform this operation, the user or role performing the action must have the iam:PassRole permission.
\nThe following operations are related to PutBucketReplication:
\n GetBucketReplication\n
\nThe name of the bucket
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a\n message integrity check to verify that the request body was not corrupted in transit. For more\n information, see RFC 1864.
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
A token to allow Object Lock to be enabled for an existing bucket.
", "smithy.api#httpHeader": "x-amz-bucket-object-lock-token" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nSets the request payment configuration for a bucket. By default, the bucket owner pays for downloads\n from the bucket. This configuration parameter enables the bucket owner (only) to specify that the person\n requesting the download will be charged for the download. For more information, see Requester Pays\n Buckets.
\nThe following operations are related to PutBucketRequestPayment:
\n CreateBucket\n
\nThe bucket name.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a\n message integrity check to verify that the request body was not corrupted in transit. For more\n information, see RFC 1864.
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
Container for Payer.
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "RequestPaymentConfiguration" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nSets the tags for a bucket.
\nUse tags to organize your Amazon Web Services bill to reflect your own cost structure. To do this, sign up to get\n your Amazon Web Services account bill with tag key values included. Then, to see the cost of combined resources,\n organize your billing information according to resources with the same tag key values. For example, you\n can tag several resources with a specific application name, and then organize your billing information\n to see the total cost of that application across several services. For more information, see Cost Allocation and\n Tagging and Using Cost Allocation in Amazon S3 Bucket Tags.
\nWhen this operation sets the tags for a bucket, it will overwrite any current tags the bucket\n already has. You cannot use this operation to add tags to an existing list of tags.
\nTo use this operation, you must have permissions to perform the s3:PutBucketTagging\n action. The bucket owner has this permission by default and can grant this permission to others. For\n more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3\n Resources.
\n PutBucketTagging has the following special errors. For more Amazon S3 errors see, Error Responses.
\n InvalidTag - The tag provided was not a valid tag. This error can occur if\n the tag did not pass input validation. For more information, see Using Cost Allocation in Amazon S3 Bucket\n Tags.
\n MalformedXML - The XML provided does not match the schema.
\n OperationAborted - A conflicting conditional action is currently in progress\n against this resource. Please try again.
\n InternalError - The service was unable to apply the provided tag to the\n bucket.
The following operations are related to PutBucketTagging:
\n GetBucketTagging\n
\n\n DeleteBucketTagging\n
\nThe bucket name.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a\n message integrity check to verify that the request body was not corrupted in transit. For more\n information, see RFC 1864.
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
Container for the TagSet and Tag elements.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nWhen you enable versioning on a bucket for the first time, it might take a short amount of time\n for the change to be fully propagated. While this change is propagating, you might encounter\n intermittent HTTP 404 NoSuchKey errors for requests to objects created or updated after\n enabling versioning. We recommend that you wait for 15 minutes after enabling versioning before\n issuing write operations (PUT or DELETE) on objects in the bucket.
Sets the versioning state of an existing bucket.
\nYou can set the versioning state with one of the following values:
\n\n Enabled\u2014Enables versioning for the objects in the bucket. All\n objects added to the bucket receive a unique version ID.
\n\n Suspended\u2014Disables versioning for the objects in the bucket. All\n objects added to the bucket receive the version ID null.
\nIf the versioning state has never been set on a bucket, it has no versioning state; a GetBucketVersioning request does not return a versioning state value.
\nIn order to enable MFA Delete, you must be the bucket owner. If you are the bucket owner and want to\n enable MFA Delete in the bucket versioning configuration, you must include the x-amz-mfa\n request header and the Status and the MfaDelete request elements in a\n request to set the versioning state of the bucket.
If you have an object expiration lifecycle configuration in your non-versioned bucket and you want\n to maintain the same permanent delete behavior when you enable versioning, you must add a noncurrent\n expiration policy. The noncurrent expiration lifecycle configuration will manage the deletes of the\n noncurrent object versions in the version-enabled bucket. (A version-enabled bucket maintains one\n current and zero or more noncurrent object versions.) For more information, see Lifecycle and\n Versioning.
\nThe following operations are related to PutBucketVersioning:
\n CreateBucket\n
\n\n DeleteBucket\n
\n\n GetBucketVersioning\n
\nThe bucket name.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": ">The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a\n message integrity check to verify that the request body was not corrupted in transit. For more\n information, see RFC 1864.
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
The concatenation of the authentication device's serial number, a space, and the value that is\n displayed on your authentication device.
", "smithy.api#httpHeader": "x-amz-mfa" } }, "VersioningConfiguration": { "target": "com.amazonaws.s3#VersioningConfiguration", "traits": { "smithy.api#documentation": "Container for setting the versioning state.
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "VersioningConfiguration" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nSets the configuration of the website that is specified in the website subresource. To\n configure a bucket as a website, you can add this subresource on the bucket with website configuration\n information such as the file name of the index document and any redirect rules. For more information,\n see Hosting Websites on\n Amazon S3.
This PUT action requires the S3:PutBucketWebsite permission. By default, only the\n bucket owner can configure the website attached to a bucket; however, bucket owners can allow other\n users to set the website configuration by writing a bucket policy that grants them the\n S3:PutBucketWebsite permission.
To redirect all website requests sent to the bucket's website endpoint, you add a website\n configuration with the following elements. Because all requests are sent to another website, you don't\n need to provide index document name for the bucket.
\n\n WebsiteConfiguration\n
\n RedirectAllRequestsTo\n
\n HostName\n
\n Protocol\n
If you want granular control over redirects, you can use the following elements to add routing rules\n that describe conditions for redirecting requests and information about the redirect destination. In\n this case, the website configuration must provide an index document for the bucket, because some\n requests might not be redirected.
\n\n WebsiteConfiguration\n
\n IndexDocument\n
\n Suffix\n
\n ErrorDocument\n
\n Key\n
\n RoutingRules\n
\n RoutingRule\n
\n Condition\n
\n HttpErrorCodeReturnedEquals\n
\n KeyPrefixEquals\n
\n Redirect\n
\n Protocol\n
\n HostName\n
\n ReplaceKeyPrefixWith\n
\n ReplaceKeyWith\n
\n HttpRedirectCode\n
Amazon S3 has a limitation of 50 routing rules per website configuration. If you require more than 50\n routing rules, you can use object redirect. For more information, see Configuring an Object Redirect in the\n Amazon S3 User Guide.
\nThe maximum request length is limited to 128 KB.
", "smithy.api#examples": [ { "title": "Set website configuration on a bucket", "documentation": "The following example adds website configuration to a bucket.", "input": { "Bucket": "examplebucket", "ContentMD5": "", "WebsiteConfiguration": { "IndexDocument": { "Suffix": "index.html" }, "ErrorDocument": { "Key": "error.html" } } } } ], "smithy.api#http": { "method": "PUT", "uri": "/{Bucket}?website", "code": 200 }, "smithy.rules#staticContextParams": { "UseS3ExpressControlEndpoint": { "value": true } } } }, "com.amazonaws.s3#PutBucketWebsiteRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a\n message integrity check to verify that the request body was not corrupted in transit. For more\n information, see RFC 1864.
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
Container for the request.
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "WebsiteConfiguration" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
End of support notice: Beginning October 1, 2025, Amazon S3 will discontinue support for creating new Email Grantee Access Control Lists (ACL). \n Email Grantee ACLs created prior to this date will continue to work and remain accessible through the Amazon Web Services Management Console, Command Line Interface (CLI), SDKs, \n and REST API. However, you will no longer be able to create new Email Grantee ACLs.\n
\nThis change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region, \n Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (S\u00e3o Paulo) Region.
\nAdds an object to a bucket.
\nAmazon S3 never adds partial objects; if you receive a success response, Amazon S3 added the entire\n object to the bucket. You cannot use PutObject to only update a single piece of\n metadata for an existing object. You must put the entire object with updated metadata if you want\n to update some values.
If your bucket uses the bucket owner enforced setting for Object Ownership, ACLs are disabled\n and no longer affect permissions. All objects written to the bucket by any account will be owned\n by the bucket owner.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
Amazon S3 is a distributed system. If it receives multiple write requests for the same object\n simultaneously, it overwrites all but the last object written. However, Amazon S3 provides features that can\n modify this behavior:
\n\n S3 Object Lock - To prevent objects from being deleted\n or overwritten, you can use Amazon S3 Object Lock in the Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\n\n If-None-Match - Uploads the object only if the object\n key name does not already exist in the specified bucket. Otherwise, Amazon S3 returns a 412\n Precondition Failed error. If a conflicting operation occurs during the upload, S3 returns\n a 409 ConditionalRequestConflict response. On a 409 failure, retry the upload.
Expects the * character (asterisk).
\nFor more information, see Add preconditions to S3 operations with\n conditional requests in the Amazon S3 User Guide or RFC 7232.
\nThis functionality is not supported for S3 on Outposts.
\n\n S3 Versioning - When you enable versioning for a bucket,\n if Amazon S3 receives multiple write requests for the same object simultaneously, it stores all versions\n of the objects. For each write request that is made to the same object, Amazon S3 automatically generates\n a unique version ID of that object being stored in Amazon S3. You can retrieve, replace, or delete any\n version of the object. For more information about versioning, see Adding Objects to\n Versioning-Enabled Buckets in the Amazon S3 User Guide. For information\n about returning the versioning state of a bucket, see GetBucketVersioning.
\nThis functionality is not supported for directory buckets.
\n\n General purpose bucket permissions - The following\n permissions are required in your policies when your PutObject request includes\n specific headers.
\n \n s3:PutObject\n - To successfully\n complete the PutObject request, you must always have the\n s3:PutObject permission on a bucket to add an object to it.
\n \n s3:PutObjectAcl\n - To successfully change the objects ACL of your PutObject\n request, you must have the s3:PutObjectAcl.
\n \n s3:PutObjectTagging\n - To successfully set the tag-set with your PutObject\n request, you must have the s3:PutObjectTagging.
\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
If the object is encrypted with SSE-KMS, you must also have the\n kms:GenerateDataKey and kms:Decrypt permissions in IAM\n identity-based policies and KMS key policies for the KMS key.
\n General purpose bucket - To ensure that data is not\n corrupted traversing the network, use the Content-MD5 header. When you use this\n header, Amazon S3 checks the object against the provided MD5 value and, if they do not match, Amazon S3\n returns an error. Alternatively, when the object's ETag is its MD5 digest, you can calculate\n the MD5 while putting the object to Amazon S3 and compare the returned ETag to the calculated MD5\n value.
\n Directory bucket -\n This functionality is not supported for directory buckets.
\n\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
For more information about related Amazon S3 APIs, see the following:
\n\n CopyObject\n
\n\n DeleteObject\n
\nThis operation is not supported for directory buckets.
\nUses the acl subresource to set the access control list (ACL) permissions for a new or\n existing object in an S3 bucket. You must have the WRITE_ACP permission to set the ACL of\n an object. For more information, see What permissions can I grant? in the\n Amazon S3 User Guide.
This functionality is not supported for Amazon S3 on Outposts.
\nDepending on your application needs, you can choose to set the ACL on an object using either the\n request body or the headers. For example, if you have an existing application that updates a bucket ACL\n using the request body, you can continue to use that approach. For more information, see Access Control List (ACL)\n Overview in the Amazon S3 User Guide.
\nIf your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs are disabled\n and no longer affect permissions. You must use policies to grant access to your bucket and the objects\n in it. Requests to set ACLs or update ACLs fail and return the\n AccessControlListNotSupported error code. Requests to read ACLs are still supported.\n For more information, see Controlling object ownership in\n the Amazon S3 User Guide.
You can set access permissions using one of the following methods:
\nSpecify a canned ACL with the x-amz-acl request header. Amazon S3 supports a set\n of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and\n permissions. Specify the canned ACL name as the value of x-amz-acl. If you use\n this header, you cannot use other access control-specific headers in your request. For more\n information, see Canned ACL.
Specify access permissions explicitly with the x-amz-grant-read,\n x-amz-grant-read-acp, x-amz-grant-write-acp, and\n x-amz-grant-full-control headers. When using these headers, you specify\n explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3 groups) who will receive the\n permission. If you use these ACL-specific headers, you cannot use x-amz-acl\n header to set a canned ACL. These parameters map to the set of permissions that Amazon S3 supports\n in an ACL. For more information, see Access Control List (ACL)\n Overview.
You specify each grantee as a type=value pair, where the type is one of the\n following:
\n\n id \u2013 if the value specified is the canonical user ID of an\n Amazon Web Services account
\n uri \u2013 if you are granting permissions to a predefined group
\n emailAddress \u2013 if the value specified is the email address of an\n Amazon Web Services account
Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:
\nUS East (N. Virginia)
\nUS West (N. California)
\nUS West (Oregon)
\nAsia Pacific (Singapore)
\nAsia Pacific (Sydney)
\nAsia Pacific (Tokyo)
\nEurope (Ireland)
\nSouth America (S\u00e3o Paulo)
\nFor a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the Amazon Web Services General Reference.
\nFor example, the following x-amz-grant-read header grants list objects\n permission to the two Amazon Web Services accounts identified by their email addresses.
\n x-amz-grant-read: emailAddress=\"xyz@amazon.com\", emailAddress=\"abc@amazon.com\"\n \n
You can use either a canned ACL or specify access permissions explicitly. You cannot do\n both.
\nYou can specify the person (grantee) to whom you're assigning access rights (using request\n elements) in the following ways. For examples of how to specify these grantee values in JSON\n format, see the Amazon Web Services CLI example in Enabling Amazon S3 server\n access logging in the Amazon S3 User Guide.
\nBy the person's ID:
\n\n
DisplayName is optional and ignored in the request.
\nBy URI:
\n\n
By Email address:
\n\n
The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl\n request, appears as the CanonicalUser.
\nUsing email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:
\nUS East (N. Virginia)
\nUS West (N. California)
\nUS West (Oregon)
\nAsia Pacific (Singapore)
\nAsia Pacific (Sydney)
\nAsia Pacific (Tokyo)
\nEurope (Ireland)
\nSouth America (S\u00e3o Paulo)
\nFor a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the Amazon Web Services General Reference.
\nThe ACL of an object is set at the object version level. By default, PUT sets the ACL of the\n current version of an object. To set the ACL of a different version, use the\n versionId subresource.
The following operations are related to PutObjectAcl:
\n CopyObject\n
\n\n GetObject\n
\nThe canned ACL to apply to the object. For more information, see Canned ACL.
", "smithy.api#httpHeader": "x-amz-acl" } }, "AccessControlPolicy": { "target": "com.amazonaws.s3#AccessControlPolicy", "traits": { "smithy.api#documentation": "Contains the elements that set the ACL permissions for an object per grantee.
", "smithy.api#httpPayload": {}, "smithy.api#xmlName": "AccessControlPolicy" } }, "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name that contains the object to which you want to attach the ACL.
\n\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
The Base64 encoded 128-bit MD5 digest of the data. This header must be used as a\n message integrity check to verify that the request body was not corrupted in transit. For more\n information, go to RFC 1864.>\n
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.
\nThis functionality is not supported for Amazon S3 on Outposts.
", "smithy.api#httpHeader": "x-amz-grant-full-control" } }, "GrantRead": { "target": "com.amazonaws.s3#GrantRead", "traits": { "smithy.api#documentation": "Allows grantee to list the objects in the bucket.
\nThis functionality is not supported for Amazon S3 on Outposts.
", "smithy.api#httpHeader": "x-amz-grant-read" } }, "GrantReadACP": { "target": "com.amazonaws.s3#GrantReadACP", "traits": { "smithy.api#documentation": "Allows grantee to read the bucket ACL.
\nThis functionality is not supported for Amazon S3 on Outposts.
", "smithy.api#httpHeader": "x-amz-grant-read-acp" } }, "GrantWrite": { "target": "com.amazonaws.s3#GrantWrite", "traits": { "smithy.api#documentation": "Allows grantee to create new objects in the bucket.
\nFor the bucket and object owners of existing objects, also allows deletions and overwrites of those\n objects.
", "smithy.api#httpHeader": "x-amz-grant-write" } }, "GrantWriteACP": { "target": "com.amazonaws.s3#GrantWriteACP", "traits": { "smithy.api#documentation": "Allows grantee to write the ACL for the applicable bucket.
\nThis functionality is not supported for Amazon S3 on Outposts.
", "smithy.api#httpHeader": "x-amz-grant-write-acp" } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "Key for which the PUT action was initiated.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Key" } } }, "RequestPayer": { "target": "com.amazonaws.s3#RequestPayer", "traits": { "smithy.api#httpHeader": "x-amz-request-payer" } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "Version ID used to reference a specific version of the object.
\nThis functionality is not supported for directory buckets.
\nThe account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nApplies a legal hold configuration to the specified object. For more information, see Locking Objects.
\nThis functionality is not supported for Amazon S3 on Outposts.
", "smithy.api#http": { "method": "PUT", "uri": "/{Bucket}/{Key+}?legal-hold", "code": 200 } } }, "com.amazonaws.s3#PutObjectLegalHoldOutput": { "type": "structure", "members": { "RequestCharged": { "target": "com.amazonaws.s3#RequestCharged", "traits": { "smithy.api#httpHeader": "x-amz-request-charged" } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#PutObjectLegalHoldRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name containing the object that you want to place a legal hold on.
\n\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "The key name for the object that you want to place a legal hold on.
", "smithy.api#httpLabel": {}, "smithy.api#required": {} } }, "LegalHold": { "target": "com.amazonaws.s3#ObjectLockLegalHold", "traits": { "smithy.api#documentation": "Container element for the legal hold configuration you want to apply to the specified object.
", "smithy.api#httpPayload": {}, "smithy.api#xmlName": "LegalHold" } }, "RequestPayer": { "target": "com.amazonaws.s3#RequestPayer", "traits": { "smithy.api#httpHeader": "x-amz-request-payer" } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "The version ID of the object that you want to place a legal hold on.
", "smithy.api#httpQuery": "versionId" } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "The MD5 hash for the request body.
\nFor requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nPlaces an Object Lock configuration on the specified bucket. The rule specified in the Object Lock\n configuration will be applied by default to every new object placed in the specified bucket. For more\n information, see Locking\n Objects.
\nThe DefaultRetention settings require both a mode and a period.
The DefaultRetention period can be either Days or Years\n but you must select one. You cannot specify Days and Years at the same\n time.
You can enable Object Lock for new or existing buckets. For more information, see Configuring\n Object Lock.
\nThe bucket whose Object Lock configuration you want to create or replace.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ObjectLockConfiguration": { "target": "com.amazonaws.s3#ObjectLockConfiguration", "traits": { "smithy.api#documentation": "The Object Lock configuration that you want to apply to the specified bucket.
", "smithy.api#httpPayload": {}, "smithy.api#xmlName": "ObjectLockConfiguration" } }, "RequestPayer": { "target": "com.amazonaws.s3#RequestPayer", "traits": { "smithy.api#httpHeader": "x-amz-request-payer" } }, "Token": { "target": "com.amazonaws.s3#ObjectLockToken", "traits": { "smithy.api#documentation": "A token to allow Object Lock to be enabled for an existing bucket.
", "smithy.api#httpHeader": "x-amz-bucket-object-lock-token" } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "The MD5 hash for the request body.
\nFor requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
If the expiration is configured for the object (see PutBucketLifecycleConfiguration) in the Amazon S3 User Guide, the response\n includes this header. It includes the expiry-date and rule-id key-value pairs\n that provide information about object expiration. The value of the rule-id is\n URL-encoded.
Object expiration information is not returned in directory buckets and this header returns the\n value \"NotImplemented\" in all responses for directory buckets.
Entity tag for the uploaded object.
\n\n General purpose buckets - To ensure that data is not corrupted\n traversing the network, for objects where the ETag is the MD5 digest of the object, you can calculate\n the MD5 while putting an object to Amazon S3 and compare the returned ETag to the calculated MD5\n value.
\n\n Directory buckets - The ETag for the object in a\n directory bucket isn't the MD5 digest of the object.
", "smithy.api#httpHeader": "ETag" } }, "ChecksumCRC32": { "target": "com.amazonaws.s3#ChecksumCRC32", "traits": { "smithy.api#documentation": "The Base64 encoded, 32-bit CRC32 checksum of the object. This checksum is only be present if the checksum was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the object. This checksum is only present if the checksum was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the object. This header is present if\n the object was uploaded with the CRC64NVME checksum algorithm, or if it was uploaded\n without a checksum (and Amazon S3 added the default checksum, CRC64NVME, to the uploaded\n object). For more information about how checksums are calculated with multipart uploads, see Checking object\n integrity in the Amazon S3 User Guide.
The Base64 encoded, 160-bit SHA1 digest of the object. This will only be present if the object was uploaded\n with the object. When you use the API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 digest of the object. This will only be present if the object was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
This header specifies the checksum type of the object, which determines how part-level checksums are\n combined to create an object-level checksum for multipart objects. For PutObject uploads,\n the checksum type is always FULL_OBJECT. You can use this header as a data integrity check\n to verify that the checksum type that is received is the same checksum that was specified. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
The server-side encryption algorithm used when you store this object in Amazon S3 or Amazon FSx.
\nWhen accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side\n encryption option is aws:fsx.
Version ID of the object.
\nIf you enable versioning for a bucket, Amazon S3 automatically generates a unique version ID for the\n object being stored. Amazon S3 returns this ID in the response. When you enable versioning for a bucket, if\n Amazon S3 receives multiple write requests for the same object simultaneously, it stores all of the objects.\n For more information about versioning, see Adding Objects to\n Versioning-Enabled Buckets in the Amazon S3 User Guide. For information about\n returning the versioning state of a bucket, see GetBucketVersioning.
\nThis functionality is not supported for directory buckets.
\nIf server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to confirm the encryption algorithm that's used.
\nThis functionality is not supported for directory buckets.
\nIf server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to provide the round-trip message integrity verification of the customer-provided\n encryption key.
\nThis functionality is not supported for directory buckets.
\nIf present, indicates the ID of the KMS key that was used for object encryption.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-aws-kms-key-id" } }, "SSEKMSEncryptionContext": { "target": "com.amazonaws.s3#SSEKMSEncryptionContext", "traits": { "smithy.api#documentation": "If present, indicates the Amazon Web Services KMS Encryption Context to use for object encryption. The value of\n this header is a Base64 encoded string of a UTF-8 encoded JSON, which contains the encryption context as key-value pairs. \n This value is stored as object metadata and automatically gets\n passed on to Amazon Web Services KMS for future GetObject \n operations on this object.
Indicates whether the uploaded object uses an S3 Bucket Key for server-side encryption with\n Key Management Service (KMS) keys (SSE-KMS).
", "smithy.api#httpHeader": "x-amz-server-side-encryption-bucket-key-enabled" } }, "Size": { "target": "com.amazonaws.s3#Size", "traits": { "smithy.api#documentation": "The size of the object in bytes. This value is only be present if you append to an object.
\nThis functionality is only supported for objects in the Amazon S3 Express One Zone storage class in\n directory buckets.
\nThe canned ACL to apply to the object. For more information, see Canned ACL in the\n Amazon S3 User Guide.
\nWhen adding a new object, you can use headers to grant ACL-based permissions to individual\n Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are then added to the ACL on\n the object. By default, all objects are private. Only the owner has full access control. For more\n information, see Access Control\n List (ACL) Overview and Managing ACLs Using the REST API in the\n Amazon S3 User Guide.
\nIf the bucket that you're uploading objects to uses the bucket owner enforced setting for S3 Object\n Ownership, ACLs are disabled and no longer affect permissions. Buckets that use this setting only accept\n PUT requests that don't specify an ACL or PUT requests that specify bucket owner full control ACLs, such\n as the bucket-owner-full-control canned ACL or an equivalent form of this ACL expressed in\n the XML format. PUT requests that contain other ACLs (for example, custom grants to certain\n Amazon Web Services accounts) fail and return a 400 error with the error code\n AccessControlListNotSupported. For more information, see Controlling ownership of objects and\n disabling ACLs in the Amazon S3 User Guide.
This functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nObject data.
", "smithy.api#httpPayload": {} } }, "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name to which the PUT action was initiated.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Can be used to specify caching behavior along the request/reply chain. For more information, see\n http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.
", "smithy.api#httpHeader": "Cache-Control" } }, "ContentDisposition": { "target": "com.amazonaws.s3#ContentDisposition", "traits": { "smithy.api#documentation": "Specifies presentational information for the object. For more information, see https://www.rfc-editor.org/rfc/rfc6266#section-4.
", "smithy.api#httpHeader": "Content-Disposition" } }, "ContentEncoding": { "target": "com.amazonaws.s3#ContentEncoding", "traits": { "smithy.api#documentation": "Specifies what content encodings have been applied to the object and thus what decoding mechanisms\n must be applied to obtain the media-type referenced by the Content-Type header field. For more\n information, see https://www.rfc-editor.org/rfc/rfc9110.html#field.content-encoding.
", "smithy.api#httpHeader": "Content-Encoding" } }, "ContentLanguage": { "target": "com.amazonaws.s3#ContentLanguage", "traits": { "smithy.api#documentation": "The language the content is in.
", "smithy.api#httpHeader": "Content-Language" } }, "ContentLength": { "target": "com.amazonaws.s3#ContentLength", "traits": { "smithy.api#documentation": "Size of the body in bytes. This parameter is useful when the size of the body cannot be determined\n automatically. For more information, see https://www.rfc-editor.org/rfc/rfc9110.html#name-content-length.
", "smithy.api#httpHeader": "Content-Length" } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "The Base64 encoded 128-bit MD5 digest of the message (without the headers) according to\n RFC 1864. This header can be used as a message integrity check to verify that the data is the same data\n that was originally sent. Although it is optional, we recommend using the Content-MD5 mechanism as an\n end-to-end integrity check. For more information about REST request authentication, see REST\n Authentication.
The Content-MD5 or x-amz-sdk-checksum-algorithm header is required for\n any request to upload an object with a retention period configured using Amazon S3 Object Lock. For more\n information, see Uploading objects\n to an Object Lock enabled bucket in the Amazon S3 User Guide.
This functionality is not supported for directory buckets.
\nA standard MIME type describing the format of the contents. For more information, see https://www.rfc-editor.org/rfc/rfc9110.html#name-content-type.
", "smithy.api#httpHeader": "Content-Type" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum-algorithm\n or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request.
For the x-amz-checksum-algorithm\n header, replace \n algorithm\n with the supported algorithm from the following list:
\n CRC32\n
\n CRC32C\n
\n CRC64NVME\n
\n SHA1\n
\n SHA256\n
For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
\nIf the individual checksum value you provide through x-amz-checksum-algorithm\n doesn't match the checksum algorithm you set through x-amz-sdk-checksum-algorithm, Amazon S3 fails the request with a BadDigest error.
The Content-MD5 or x-amz-sdk-checksum-algorithm header is required for\n any request to upload an object with a retention period configured using Amazon S3 Object Lock. For more\n information, see Uploading objects\n to an Object Lock enabled bucket in the Amazon S3 User Guide.
For directory buckets, when you use Amazon Web Services SDKs, CRC32 is the default checksum algorithm that's used for performance.
This header can be used as a data integrity check to verify that the data received is the same data that was originally sent.\n This header specifies the Base64 encoded, 32-bit CRC32 checksum of the object. For more information, see\n Checking object integrity in the\n Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data that was originally sent.\n This header specifies the Base64 encoded, 32-bit CRC32C checksum of the object. For more information, see\n Checking object integrity in the\n Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This header specifies the Base64 encoded, 64-bit CRC64NVME\n checksum of the object. The CRC64NVME checksum is always a full object checksum. For more\n information, see Checking object integrity in the Amazon S3\n User Guide.
This header can be used as a data integrity check to verify that the data received is the same data that was originally sent.\n This header specifies the Base64 encoded, 160-bit SHA1 digest of the object. For more information, see\n Checking object integrity in the\n Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data that was originally sent.\n This header specifies the Base64 encoded, 256-bit SHA256 digest of the object. For more information, see\n Checking object integrity in the\n Amazon S3 User Guide.
The date and time at which the object is no longer cacheable. For more information, see https://www.rfc-editor.org/rfc/rfc7234#section-5.3.
", "smithy.api#httpHeader": "Expires" } }, "IfMatch": { "target": "com.amazonaws.s3#IfMatch", "traits": { "smithy.api#documentation": "Uploads the object only if the ETag (entity tag) value provided during the WRITE operation matches\n the ETag of the object in S3. If the ETag values do not match, the operation returns a 412\n Precondition Failed error.
If a conflicting operation occurs during the upload S3 returns a 409\n ConditionalRequestConflict response. On a 409 failure you should fetch the object's ETag and\n retry the upload.
Expects the ETag value as a string.
\nFor more information about conditional requests, see RFC 7232, or Conditional requests in the\n Amazon S3 User Guide.
", "smithy.api#httpHeader": "If-Match" } }, "IfNoneMatch": { "target": "com.amazonaws.s3#IfNoneMatch", "traits": { "smithy.api#documentation": "Uploads the object only if the object key name does not already exist in the bucket specified.\n Otherwise, Amazon S3 returns a 412 Precondition Failed error.
If a conflicting operation occurs during the upload S3 returns a 409\n ConditionalRequestConflict response. On a 409 failure you should retry the upload.
Expects the '*' (asterisk) character.
\nFor more information about conditional requests, see RFC 7232, or Conditional requests in the\n Amazon S3 User Guide.
", "smithy.api#httpHeader": "If-None-Match" } }, "GrantFullControl": { "target": "com.amazonaws.s3#GrantFullControl", "traits": { "smithy.api#documentation": "Gives the grantee READ, READ_ACP, and WRITE_ACP permissions on the object.
\nThis functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nAllows grantee to read the object data and its metadata.
\nThis functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nAllows grantee to read the object ACL.
\nThis functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nAllows grantee to write the ACL for the applicable object.
\nThis functionality is not supported for directory buckets.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nObject key for which the PUT action was initiated.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Key" } } }, "WriteOffsetBytes": { "target": "com.amazonaws.s3#WriteOffsetBytes", "traits": { "smithy.api#documentation": "Specifies the offset for appending data to existing objects in bytes. The offset must be equal to\n the size of the existing object being appended to. If no object exists, setting this header to 0 will\n create a new object.
\nThis functionality is only supported for objects in the Amazon S3 Express One Zone storage class in\n directory buckets.
\nA map of metadata to store with the object in S3.
", "smithy.api#httpPrefixHeaders": "x-amz-meta-" } }, "ServerSideEncryption": { "target": "com.amazonaws.s3#ServerSideEncryption", "traits": { "smithy.api#documentation": "The server-side encryption algorithm that was used when you store this object in Amazon S3 or\n Amazon FSx.
\n\n General purpose buckets - You have four mutually exclusive\n options to protect data using server-side encryption in Amazon S3, depending on how you choose to manage\n the encryption keys. Specifically, the encryption key options are Amazon S3 managed keys (SSE-S3),\n Amazon Web Services KMS keys (SSE-KMS or DSSE-KMS), and customer-provided keys (SSE-C). Amazon S3 encrypts data with\n server-side encryption by using Amazon S3 managed keys (SSE-S3) by default. You can optionally tell Amazon S3\n to encrypt data at rest by using server-side encryption with other key options. For more\n information, see Using Server-Side Encryption in\n the Amazon S3 User Guide.
\n\n Directory buckets -\n For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n CreateSession requests or PUT object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n information, see Protecting data with server-side encryption in the Amazon S3 User Guide. For more information about the encryption overriding behaviors in directory buckets, see Specifying server-side encryption with KMS for new object uploads.
In the Zonal endpoint API calls (except CopyObject and UploadPartCopy) using the REST API, the encryption request headers must match the encryption settings that are specified in the CreateSession request. \n You can't override the values of the encryption settings (x-amz-server-side-encryption, x-amz-server-side-encryption-aws-kms-key-id, x-amz-server-side-encryption-context, and x-amz-server-side-encryption-bucket-key-enabled) that are specified in the CreateSession request. \n You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and \n Amazon S3 will use the encryption settings values from the CreateSession request to protect new objects in the directory bucket. \n
When you use the CLI or the Amazon Web Services SDKs, for CreateSession, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the \n CreateSession request. It's not supported to override the encryption settings values in the CreateSession request. \n So in the Zonal endpoint API calls (except CopyObject and UploadPartCopy), \n the encryption request headers must match the default encryption configuration of the directory bucket.\n\n
\n S3 access points for Amazon FSx - When accessing data stored in\n Amazon FSx file systems using S3 access points, the only valid server side encryption option is\n aws:fsx. All Amazon FSx file systems have encryption configured by default and are\n encrypted at rest. Data is automatically encrypted before being written to the file system, and\n automatically decrypted as it is read. These processes are handled transparently by Amazon FSx.
By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The STANDARD\n storage class provides high durability and high availability. Depending on performance needs, you can\n specify a different Storage Class. For more information, see Storage Classes in the\n Amazon S3 User Guide.
\nDirectory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in\n Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in\n Dedicated Local Zones.
Amazon S3 on Outposts only uses the OUTPOSTS Storage Class.
\nIf the bucket is configured as a website, redirects requests for this object to another object in\n the same bucket or to an external URL. Amazon S3 stores the value of this header in the object metadata. For\n information about object metadata, see Object Key and Metadata in the Amazon S3\n User Guide.
\nIn the following example, the request header sets the redirect to an object (anotherPage.html) in\n the same bucket:
\n\n x-amz-website-redirect-location: /anotherPage.html\n
In the following example, the request header sets the object redirect to another website:
\n\n x-amz-website-redirect-location: http://www.example.com/\n
For more information about website hosting in Amazon S3, see Hosting Websites on Amazon S3 and How to Configure Website Page\n Redirects in the Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\nSpecifies the algorithm to use when encrypting the object (for example, AES256).
This functionality is not supported for directory buckets.
\nSpecifies the customer-provided encryption key for Amazon S3 to use in encrypting data. This value is\n used to store the object and then it is discarded; Amazon S3 does not store the encryption key. The key must\n be appropriate for use with the algorithm specified in the\n x-amz-server-side-encryption-customer-algorithm header.
This functionality is not supported for directory buckets.
\nSpecifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header\n for a message integrity check to ensure that the encryption key was transmitted without error.
\nThis functionality is not supported for directory buckets.
\nSpecifies the KMS key ID (Key ID, Key ARN, or Key Alias) to use for object encryption. If the KMS key doesn't exist in the same\n account that's issuing the command, you must use the full Key ARN not the Key ID.
\n\n General purpose buckets - If you specify x-amz-server-side-encryption with aws:kms or aws:kms:dsse, this header specifies the ID (Key ID, Key ARN, or Key Alias) of the KMS \n key to use. If you specify\n x-amz-server-side-encryption:aws:kms or\n x-amz-server-side-encryption:aws:kms:dsse, but do not provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the Amazon Web Services managed key\n (aws/s3) to protect the data.
\n Directory buckets - To encrypt data using SSE-KMS, it's recommended to specify the \nx-amz-server-side-encryption header to aws:kms. Then, the x-amz-server-side-encryption-aws-kms-key-id header implicitly uses \nthe bucket's default KMS customer managed key ID. If you want to explicitly set the \n x-amz-server-side-encryption-aws-kms-key-id header, it must match the bucket's default customer managed key (using key ID or ARN, not alias). Your SSE-KMS configuration can only support 1 customer managed key per directory bucket's lifetime. \nThe Amazon Web Services managed key (aws/s3) isn't supported. \n \n Incorrect key specification results in an HTTP 400 Bad Request error.
Specifies the Amazon Web Services KMS Encryption Context as an additional encryption context to use for object encryption. The value of\n this header is a Base64 encoded string of a UTF-8 encoded JSON, which contains the encryption context as key-value pairs. \n This value is stored as object metadata and automatically gets passed on\n to Amazon Web Services KMS for future GetObject operations on\n this object.
\n General purpose buckets - This value must be explicitly added during CopyObject operations if you want an additional encryption context for your object. For more information, see Encryption context in the Amazon S3 User Guide.
\n Directory buckets - You can optionally provide an explicit encryption context value. The value must match the default encryption context - the bucket Amazon Resource Name (ARN). An additional encryption context value is not supported.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-context" } }, "BucketKeyEnabled": { "target": "com.amazonaws.s3#BucketKeyEnabled", "traits": { "smithy.api#documentation": "Specifies whether Amazon S3 should use an S3 Bucket Key for object encryption with\n server-side encryption using Key Management Service (KMS) keys (SSE-KMS).
\n\n General purpose buckets - Setting this header to\n true causes Amazon S3 to use an S3 Bucket Key for object encryption with\n SSE-KMS. Also, specifying this header with a PUT action doesn't affect bucket-level settings for S3\n Bucket Key.
\n Directory buckets - S3 Bucket Keys are always enabled for GET and PUT operations in a directory bucket and can\u2019t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through CopyObject, UploadPartCopy, the Copy operation in Batch Operations, or \n the import jobs. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.
The tag-set for the object. The tag-set must be encoded as URL Query parameters. (For example,\n \"Key1=Value1\")
\nThis functionality is not supported for directory buckets.
\nThe Object Lock mode that you want to apply to this object.
\nThis functionality is not supported for directory buckets.
\nThe date and time when you want this object's Object Lock to expire. Must be formatted as a\n timestamp parameter.
\nThis functionality is not supported for directory buckets.
\nSpecifies whether a legal hold will be applied to this object. For more information about S3 Object\n Lock, see Object Lock in\n the Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\nThe account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nPlaces an Object Retention configuration on an object. For more information, see Locking Objects. Users or\n accounts require the s3:PutObjectRetention permission in order to place an Object Retention\n configuration on objects. Bypassing a Governance Retention configuration requires the\n s3:BypassGovernanceRetention permission.
This functionality is not supported for Amazon S3 on Outposts.
", "smithy.api#http": { "method": "PUT", "uri": "/{Bucket}/{Key+}?retention", "code": 200 } } }, "com.amazonaws.s3#PutObjectRetentionOutput": { "type": "structure", "members": { "RequestCharged": { "target": "com.amazonaws.s3#RequestCharged", "traits": { "smithy.api#httpHeader": "x-amz-request-charged" } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#PutObjectRetentionRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name that contains the object you want to apply this Object Retention configuration to.
\n\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "The key name for the object that you want to apply this Object Retention configuration to.
", "smithy.api#httpLabel": {}, "smithy.api#required": {} } }, "Retention": { "target": "com.amazonaws.s3#ObjectLockRetention", "traits": { "smithy.api#documentation": "The container element for the Object Retention configuration.
", "smithy.api#httpPayload": {}, "smithy.api#xmlName": "Retention" } }, "RequestPayer": { "target": "com.amazonaws.s3#RequestPayer", "traits": { "smithy.api#httpHeader": "x-amz-request-payer" } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "The version ID for the object that you want to apply this Object Retention configuration to.
", "smithy.api#httpQuery": "versionId" } }, "BypassGovernanceRetention": { "target": "com.amazonaws.s3#BypassGovernanceRetention", "traits": { "smithy.api#documentation": "Indicates whether this action should bypass Governance-mode restrictions.
", "smithy.api#httpHeader": "x-amz-bypass-governance-retention" } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "The MD5 hash for the request body.
\nFor requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nSets the supplied tag-set to an object that already exists in a bucket. A tag is a key-value pair.\n For more information, see Object Tagging.
\nYou can associate tags with an object by sending a PUT request against the tagging subresource that\n is associated with the object. You can retrieve tags by sending a GET request. For more information, see\n GetObjectTagging.
\nFor tagging-related restrictions related to characters and encodings, see Tag\n Restrictions. Note that Amazon S3 limits the maximum number of tags to 10 tags per object.
\nTo use this operation, you must have permission to perform the s3:PutObjectTagging\n action. By default, the bucket owner has this permission and can grant this permission to others.
To put tags of any other version, use the versionId query parameter. You also need\n permission for the s3:PutObjectVersionTagging action.
\n PutObjectTagging has the following special errors. For more Amazon S3 errors see, Error Responses.
\n InvalidTag - The tag provided was not a valid tag. This error can occur if\n the tag did not pass input validation. For more information, see Object Tagging.
\n MalformedXML - The XML provided does not match the schema.
\n OperationAborted - A conflicting conditional action is currently in progress\n against this resource. Please try again.
\n InternalError - The service was unable to apply the provided tag to the\n object.
The following operations are related to PutObjectTagging:
\n GetObjectTagging\n
\n\n DeleteObjectTagging\n
\nThe versionId of the object the tag-set was added to.
", "smithy.api#httpHeader": "x-amz-version-id" } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#PutObjectTaggingRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name containing the object.
\n\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Name of the object key.
", "smithy.api#httpLabel": {}, "smithy.api#required": {} } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "The versionId of the object that the tag-set will be added to.
", "smithy.api#httpQuery": "versionId" } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "The MD5 hash for the request body.
\nFor requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
Container for the TagSet and Tag elements
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
This operation is not supported for directory buckets.
\nCreates or modifies the PublicAccessBlock configuration for an Amazon S3 bucket. To use this\n operation, you must have the s3:PutBucketPublicAccessBlock permission. For more information\n about Amazon S3 permissions, see Specifying Permissions in a\n Policy.
When Amazon S3 evaluates the PublicAccessBlock configuration for a bucket or an object, it\n checks the PublicAccessBlock configuration for both the bucket (or the bucket that\n contains the object) and the bucket owner's account. If the PublicAccessBlock\n configurations are different between the bucket and the account, Amazon S3 uses the most restrictive\n combination of the bucket-level and account-level settings.
For more information about when Amazon S3 considers a bucket or an object public, see The Meaning of \"Public\".
\nThe following operations are related to PutPublicAccessBlock:
\n GetPublicAccessBlock\n
\nThe name of the Amazon S3 bucket whose PublicAccessBlock configuration you want to\n set.
The MD5 hash of the PutPublicAccessBlock request body.
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
", "smithy.api#httpHeader": "Content-MD5" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can\n enable the configuration options in any combination. For more information about when Amazon S3 considers a\n bucket or object public, see The Meaning of \"Public\" in the Amazon S3 User Guide.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The Amazon Resource Name (ARN) of the Amazon SQS queue to which Amazon S3 publishes a message when it\n detects events of the specified type.
", "smithy.api#required": {}, "smithy.api#xmlName": "Queue" } }, "Events": { "target": "com.amazonaws.s3#EventList", "traits": { "smithy.api#documentation": "A collection of bucket events for which to send notifications
", "smithy.api#required": {}, "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Event" } }, "Filter": { "target": "com.amazonaws.s3#NotificationConfigurationFilter" } }, "traits": { "smithy.api#documentation": "Specifies the configuration for publishing messages to an Amazon Simple Queue Service (Amazon SQS)\n queue when Amazon S3 detects specified events.
" } }, "com.amazonaws.s3#QueueConfigurationList": { "type": "list", "member": { "target": "com.amazonaws.s3#QueueConfiguration" } }, "com.amazonaws.s3#Quiet": { "type": "boolean" }, "com.amazonaws.s3#QuoteCharacter": { "type": "string" }, "com.amazonaws.s3#QuoteEscapeCharacter": { "type": "string" }, "com.amazonaws.s3#QuoteFields": { "type": "enum", "members": { "ALWAYS": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ALWAYS" } }, "ASNEEDED": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ASNEEDED" } } } }, "com.amazonaws.s3#Range": { "type": "string" }, "com.amazonaws.s3#RecordDelimiter": { "type": "string" }, "com.amazonaws.s3#RecordExpiration": { "type": "structure", "members": { "Expiration": { "target": "com.amazonaws.s3#ExpirationState", "traits": { "smithy.api#documentation": "\n Specifies whether journal table record expiration is enabled or disabled.\n
", "smithy.api#required": {} } }, "Days": { "target": "com.amazonaws.s3#RecordExpirationDays", "traits": { "smithy.api#documentation": "\n If you enable journal table record expiration, you can set the number of days to retain your \n journal table records. Journal table records must be retained for a minimum of 7 days. To set \n this value, specify any whole number from 7 to 2147483647. For example, \n to retain your journal table records for one year, set this value to 365.\n
\n The journal table record expiration settings for a journal table in an S3 Metadata configuration.\n
" } }, "com.amazonaws.s3#RecordExpirationDays": { "type": "integer" }, "com.amazonaws.s3#RecordsEvent": { "type": "structure", "members": { "Payload": { "target": "com.amazonaws.s3#Body", "traits": { "smithy.api#documentation": "The byte array of partial, one or more result records. S3 Select doesn't guarantee that a record\n will be self-contained in one record frame. To ensure continuous streaming of data, S3 Select might\n split the same record across multiple record frames instead of aggregating the results in memory. Some\n S3 clients (for example, the SDK for Java) handle this behavior by creating a\n ByteStream out of the response by default. Other clients might not handle this behavior\n by default. In those cases, you must aggregate the results on the client side and parse the\n response.
The container for the records event.
" } }, "com.amazonaws.s3#Redirect": { "type": "structure", "members": { "HostName": { "target": "com.amazonaws.s3#HostName", "traits": { "smithy.api#documentation": "The host name to use in the redirect request.
" } }, "HttpRedirectCode": { "target": "com.amazonaws.s3#HttpRedirectCode", "traits": { "smithy.api#documentation": "The HTTP redirect code to use on the response. Not required if one of the siblings is\n present.
" } }, "Protocol": { "target": "com.amazonaws.s3#Protocol", "traits": { "smithy.api#documentation": "Protocol to use when redirecting requests. The default is the protocol that is used in the original\n request.
" } }, "ReplaceKeyPrefixWith": { "target": "com.amazonaws.s3#ReplaceKeyPrefixWith", "traits": { "smithy.api#documentation": "The object key prefix to use in the redirect request. For example, to redirect requests for all\n pages with prefix docs/ (objects in the docs/ folder) to\n documents/, you can set a condition block with KeyPrefixEquals set to\n docs/ and in the Redirect set ReplaceKeyPrefixWith to\n /documents. Not required if one of the siblings is present. Can be present only if\n ReplaceKeyWith is not provided.
Replacement must be made for object keys containing special characters (such as carriage returns) when using \n XML requests. For more information, see \n XML related object key constraints.
\nThe specific object key to use in the redirect request. For example, redirect request to\n error.html. Not required if one of the siblings is present. Can be present only if\n ReplaceKeyPrefixWith is not provided.
Replacement must be made for object keys containing special characters (such as carriage returns) when using \n XML requests. For more information, see \n XML related object key constraints.
\nSpecifies how requests are redirected. In the event of an error, you can specify a different error\n code to return.
" } }, "com.amazonaws.s3#RedirectAllRequestsTo": { "type": "structure", "members": { "HostName": { "target": "com.amazonaws.s3#HostName", "traits": { "smithy.api#documentation": "Name of the host where requests are redirected.
", "smithy.api#required": {} } }, "Protocol": { "target": "com.amazonaws.s3#Protocol", "traits": { "smithy.api#documentation": "Protocol to use when redirecting requests. The default is the protocol that is used in the original\n request.
" } } }, "traits": { "smithy.api#documentation": "Specifies the redirect behavior of all requests to a website endpoint of an Amazon S3 bucket.
" } }, "com.amazonaws.s3#Region": { "type": "string", "traits": { "smithy.api#length": { "min": 0, "max": 20 } } }, "com.amazonaws.s3#RenameObject": { "type": "operation", "input": { "target": "com.amazonaws.s3#RenameObjectRequest" }, "output": { "target": "com.amazonaws.s3#RenameObjectOutput" }, "errors": [ { "target": "com.amazonaws.s3#IdempotencyParameterMismatch" } ], "traits": { "smithy.api#documentation": "Renames an existing object in a directory bucket that uses the S3 Express One Zone storage class.\n You can use RenameObject by specifying an existing object\u2019s name as the source and the new\n name of the object as the destination within the same directory bucket.
\n RenameObject is only supported for objects stored in the S3 Express One Zone storage\n class.
To prevent overwriting an object, you can use the If-None-Match conditional\n header.
\n If-None-Match - Renames the object only if an object\n with the specified name does not already exist in the directory bucket. If you don't want to\n overwrite an existing object, you can add the If-None-Match conditional header with the\n value \u2018*\u2019 in the RenameObject request. Amazon S3 then returns a 412\n Precondition Failed error if the object with the specified name already exists. For more\n information, see RFC 7232.
To grant access to the RenameObject operation on a directory bucket, we\n recommend that you use the CreateSession operation for session-based authorization.\n Specifically, you grant the s3express:CreateSession permission to the directory\n bucket in a bucket policy or an IAM identity-based policy. Then, you make the\n CreateSession API call on the directory bucket to obtain a session token. With the\n session token in your request header, you can make API requests to this operation. After the\n session token expires, you make another CreateSession API call to generate a new\n session token for use. The Amazon Web Services CLI and SDKs will create and manage your session including\n refreshing the session token automatically to avoid service interruptions when a session expires.\n In your bucket policy, you can specify the s3express:SessionMode condition key to\n control who can create a ReadWrite or ReadOnly session. A\n ReadWrite session is required for executing all the Zonal endpoint API operations,\n including RenameObject. For more information about authorization, see \n CreateSession\n . To learn more about Zonal endpoint API operations, see\n Authorizing Zonal endpoint API operations with CreateSession in the Amazon S3 User\n Guide.
\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The bucket name of the directory bucket containing the object.
\n You must use virtual-hosted-style requests in the format\n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not\n supported. Directory bucket names must be unique in the chosen Availability Zone. Bucket names must\n follow the format bucket-base-name--zone-id--x-s3 (for example,\n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming restrictions, see\n Directory bucket naming rules in the Amazon S3 User Guide.
Key name of the object to rename.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Key" } } }, "RenameSource": { "target": "com.amazonaws.s3#RenameSource", "traits": { "smithy.api#documentation": "Specifies the source for the rename operation. The value must be URL encoded.
", "smithy.api#httpHeader": "x-amz-rename-source", "smithy.api#required": {} } }, "DestinationIfMatch": { "target": "com.amazonaws.s3#IfMatch", "traits": { "smithy.api#documentation": "Renames the object only if the ETag (entity tag) value provided during the operation matches the\n ETag of the object in S3. The If-Match header field makes the request method conditional on\n ETags. If the ETag values do not match, the operation returns a 412 Precondition Failed\n error.
Expects the ETag value as a string.
", "smithy.api#httpHeader": "If-Match" } }, "DestinationIfNoneMatch": { "target": "com.amazonaws.s3#IfNoneMatch", "traits": { "smithy.api#documentation": " Renames the object only if the destination does not already exist in the specified directory\n bucket. If the object does exist when you send a request with If-None-Match:*, the S3 API\n will return a 412 Precondition Failed error, preventing an overwrite. The\n If-None-Match header prevents overwrites of existing data by validating that there's not\n an object with the same key name already in your directory bucket.
Expects the * character (asterisk).
Renames the object if the destination exists and if it has been modified since the specified\n time.
", "smithy.api#httpHeader": "If-Modified-Since" } }, "DestinationIfUnmodifiedSince": { "target": "com.amazonaws.s3#IfUnmodifiedSince", "traits": { "smithy.api#documentation": "Renames the object if it hasn't been modified since the specified time.
", "smithy.api#httpHeader": "If-Unmodified-Since" } }, "SourceIfMatch": { "target": "com.amazonaws.s3#RenameSourceIfMatch", "traits": { "smithy.api#documentation": "Renames the object if the source exists and if its entity tag (ETag) matches the specified ETag.\n
", "smithy.api#httpHeader": "x-amz-rename-source-if-match" } }, "SourceIfNoneMatch": { "target": "com.amazonaws.s3#RenameSourceIfNoneMatch", "traits": { "smithy.api#documentation": "Renames the object if the source exists and if its entity tag (ETag) is different than the specified\n ETag. If an asterisk (*) character is provided, the operation will fail and return a\n 412 Precondition Failed error.
Renames the object if the source exists and if it has been modified since the specified time.
", "smithy.api#httpHeader": "x-amz-rename-source-if-modified-since" } }, "SourceIfUnmodifiedSince": { "target": "com.amazonaws.s3#RenameSourceIfUnmodifiedSince", "traits": { "smithy.api#documentation": "Renames the object if the source exists and hasn't been modified since the specified time.
", "smithy.api#httpHeader": "x-amz-rename-source-if-unmodified-since" } }, "ClientToken": { "target": "com.amazonaws.s3#ClientToken", "traits": { "smithy.api#documentation": "A unique string with a max of 64 ASCII characters in the ASCII range of 33 - 126.
\n\n RenameObject supports idempotency using a client token. To make an idempotent API request\n using RenameObject, specify a client token in the request. You should not reuse the same\n client token for other API requests. If you retry a request that completed successfully using the same\n client token and the same parameters, the retry succeeds without performing any further actions. If\n you retry a successful request using the same client token, but one or more of the parameters are\n different, the retry fails and an IdempotentParameterMismatch error is returned.
Specifies whether Amazon S3 replicates modifications on replicas.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "A filter that you can specify for selection for modifications on replicas. Amazon S3 doesn't replicate\n replica modifications by default. In the latest version of replication configuration (when\n Filter is specified), you can specify this element and set the status to\n Enabled to replicate modifications on replicas.
If you don't specify the Filter element, Amazon S3 assumes that the replication\n configuration is the earlier version, V1. In the earlier version, this element is not allowed.
The Amazon Resource Name (ARN) of the Identity and Access Management (IAM) role that Amazon S3 assumes when replicating\n objects. For more information, see How to Set Up Replication in the\n Amazon S3 User Guide.
", "smithy.api#required": {} } }, "Rules": { "target": "com.amazonaws.s3#ReplicationRules", "traits": { "smithy.api#documentation": "A container for one or more replication rules. A replication configuration must have at least one\n rule and can contain a maximum of 1,000 rules.
", "smithy.api#required": {}, "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Rule" } } }, "traits": { "smithy.api#documentation": "A container for replication rules. You can add up to 1,000 rules. The maximum size of a replication\n configuration is 2 MB.
" } }, "com.amazonaws.s3#ReplicationRule": { "type": "structure", "members": { "ID": { "target": "com.amazonaws.s3#ID", "traits": { "smithy.api#documentation": "A unique identifier for the rule. The maximum value is 255 characters.
" } }, "Priority": { "target": "com.amazonaws.s3#Priority", "traits": { "smithy.api#documentation": "The priority indicates which rule has precedence whenever two or more replication rules conflict.\n Amazon S3 will attempt to replicate objects according to all replication rules. However, if there are two or\n more rules with the same destination bucket, then objects will be replicated according to the rule with\n the highest priority. The higher the number, the higher the priority.
\nFor more information, see Replication in the Amazon S3 User Guide.
" } }, "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#deprecated": {}, "smithy.api#documentation": "An object key name prefix that identifies the object or objects to which the rule applies. The\n maximum prefix length is 1,024 characters. To include all objects in a bucket, specify an empty string.\n
\nReplacement must be made for object keys containing special characters (such as carriage returns) when using \n XML requests. For more information, see \n XML related object key constraints.
\nSpecifies whether the rule is enabled.
", "smithy.api#required": {} } }, "SourceSelectionCriteria": { "target": "com.amazonaws.s3#SourceSelectionCriteria", "traits": { "smithy.api#documentation": "A container that describes additional filters for identifying the source objects that you want to\n replicate. You can choose to enable or disable the replication of these objects. Currently, Amazon S3\n supports only the filter that you can specify for objects created with server-side encryption using a\n customer managed key stored in Amazon Web Services Key Management Service (SSE-KMS).
" } }, "ExistingObjectReplication": { "target": "com.amazonaws.s3#ExistingObjectReplication", "traits": { "smithy.api#documentation": "Optional configuration to replicate existing source bucket objects.
\nThis parameter is no longer supported. To replicate existing objects, see Replicating\n existing objects with S3 Batch Replication in the\n Amazon S3 User Guide.
\nA container for information about the replication destination and its configurations including\n enabling the S3 Replication Time Control (S3 RTC).
", "smithy.api#required": {} } }, "DeleteMarkerReplication": { "target": "com.amazonaws.s3#DeleteMarkerReplication" } }, "traits": { "smithy.api#documentation": "Specifies which Amazon S3 objects to replicate and where to store the replicas.
" } }, "com.amazonaws.s3#ReplicationRuleAndOperator": { "type": "structure", "members": { "Prefix": { "target": "com.amazonaws.s3#Prefix", "traits": { "smithy.api#documentation": "An object key name prefix that identifies the subset of objects to which the rule applies.
" } }, "Tags": { "target": "com.amazonaws.s3#TagSet", "traits": { "smithy.api#documentation": "An array of tags containing key and value pairs.
", "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Tag" } } }, "traits": { "smithy.api#documentation": "A container for specifying rule filters. The filters determine the subset of objects to which the\n rule applies. This element is required only if you specify more than one filter.
\nFor example:
\nIf you specify both a Prefix and a Tag filter, wrap these filters in\n an And tag.
If you specify a filter based on multiple tags, wrap the Tag elements in an\n And tag.
An object key name prefix that identifies the subset of objects to which the rule applies.
\nReplacement must be made for object keys containing special characters (such as carriage returns) when using \n XML requests. For more information, see \n XML related object key constraints.
\nA container for specifying a tag key and value.
\nThe rule applies only to objects that have the tag in their tag set.
" } }, "And": { "target": "com.amazonaws.s3#ReplicationRuleAndOperator", "traits": { "smithy.api#documentation": "A container for specifying rule filters. The filters determine the subset of objects to which the\n rule applies. This element is required only if you specify more than one filter. For example:
\nIf you specify both a Prefix and a Tag filter, wrap these filters in\n an And tag.
If you specify a filter based on multiple tags, wrap the Tag elements in an\n And tag.
A filter that identifies the subset of objects to which the replication rule applies. A\n Filter must specify exactly one Prefix, Tag, or an\n And child element.
Specifies whether the replication time is enabled.
", "smithy.api#required": {} } }, "Time": { "target": "com.amazonaws.s3#ReplicationTimeValue", "traits": { "smithy.api#documentation": "A container specifying the time by which replication should be complete for all objects and\n operations on objects.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": " A container specifying S3 Replication Time Control (S3 RTC) related information, including whether S3 RTC is enabled and\n the time when all objects and operations on objects must be replicated. Must be specified together with\n a Metrics block.
Contains an integer specifying time in minutes.
\nValid value: 15
" } } }, "traits": { "smithy.api#documentation": " A container specifying the time value for S3 Replication Time Control (S3 RTC) and replication metrics\n EventThreshold.
If present, indicates that the requester was successfully charged for the request. For more\n information, see Using Requester Pays buckets for storage transfers and usage in the Amazon Simple\n Storage Service user guide.
\nThis functionality is not supported for directory buckets.
\nConfirms that the requester knows that they will be charged for the request. Bucket owners need not\n specify this parameter in their requests. If either the source or destination S3 bucket has Requester\n Pays enabled, the requester will pay for corresponding charges to copy the object. For information about\n downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays\n Buckets in the Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\nSpecifies who pays for the download and request fees.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Container for Payer.
" } }, "com.amazonaws.s3#RequestProgress": { "type": "structure", "members": { "Enabled": { "target": "com.amazonaws.s3#EnableRequestProgress", "traits": { "smithy.api#documentation": "Specifies whether periodic QueryProgress frames should be sent. Valid values: TRUE, FALSE. Default\n value: FALSE.
" } } }, "traits": { "smithy.api#documentation": "Container for specifying if periodic QueryProgress messages should be sent.
This operation is not supported for directory buckets.
\nRestores an archived copy of an object back into Amazon S3
\nThis functionality is not supported for Amazon S3 on Outposts.
\nThis action performs the following types of requests:
\n\n restore an archive - Restore an archived object
For more information about the S3 structure in the request body, see the\n following:
\n PutObject\n
\n\n Managing Access\n with ACLs in the Amazon S3 User Guide\n
\n\n Protecting Data\n Using Server-Side Encryption in the Amazon S3 User Guide\n
\nTo use this operation, you must have permissions to perform the s3:RestoreObject\n action. The bucket owner has this permission by default and can grant this permission to others.\n For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3\n Resources in the Amazon S3 User Guide.
Objects that you archive to the S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive\n storage class, and S3 Intelligent-Tiering Archive or S3 Intelligent-Tiering Deep Archive tiers, are not accessible in\n real time. For objects in the S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive\n storage classes, you must first initiate a restore request, and then wait until a temporary copy\n of the object is available. If you want a permanent copy of the object, create a copy of it in the\n Amazon S3 Standard storage class in your S3 bucket. To access an archived object, you must restore the\n object for the duration (number of days) that you specify. For objects in the Archive Access or\n Deep Archive Access tiers of S3 Intelligent-Tiering, you must first initiate a restore request, and\n then wait until the object is moved into the Frequent Access tier.
\nTo restore a specific object version, you can provide a version ID. If you don't provide a\n version ID, Amazon S3 restores the current version.
\nWhen restoring an archived object, you can specify one of the following data access tier\n options in the Tier element of the request body:
\n Expedited - Expedited retrievals allow you to quickly access your data stored\n in the S3 Glacier Flexible Retrieval storage class or S3 Intelligent-Tiering Archive tier when occasional\n urgent requests for restoring archives are required. For all but the largest archived objects\n (250 MB+), data accessed using Expedited retrievals is typically made available within 1\u20135\n minutes. Provisioned capacity ensures that retrieval capacity for Expedited retrievals is\n available when you need it. Expedited retrievals and provisioned capacity are not available\n for objects stored in the S3 Glacier Deep Archive storage class or\n S3 Intelligent-Tiering Deep Archive tier.
\n Standard - Standard retrievals allow you to access any of your archived\n objects within several hours. This is the default option for retrieval requests that do not\n specify the retrieval option. Standard retrievals typically finish within 3\u20135 hours for\n objects stored in the S3 Glacier Flexible Retrieval storage class or S3 Intelligent-Tiering Archive tier.\n They typically finish within 12 hours for objects stored in the\n S3 Glacier Deep Archive storage class or S3 Intelligent-Tiering Deep Archive tier. Standard\n retrievals are free for objects stored in S3 Intelligent-Tiering.
\n Bulk - Bulk retrievals free for objects stored in the S3 Glacier Flexible\n Retrieval and S3 Intelligent-Tiering storage classes, enabling you to retrieve large amounts,\n even petabytes, of data at no cost. Bulk retrievals typically finish within 5\u201312 hours for\n objects stored in the S3 Glacier Flexible Retrieval storage class or S3 Intelligent-Tiering Archive tier.\n Bulk retrievals are also the lowest-cost retrieval option when restoring objects from\n S3 Glacier Deep Archive. They typically finish within 48 hours for objects stored in\n the S3 Glacier Deep Archive storage class or S3 Intelligent-Tiering Deep Archive tier.
For more information about archive retrieval options and provisioned capacity for\n Expedited data access, see Restoring Archived Objects in the\n Amazon S3 User Guide.
You can use Amazon S3 restore speed upgrade to change the restore speed to a faster speed while it\n is in progress. For more information, see \n Upgrading the speed of an in-progress restore in the\n Amazon S3 User Guide.
\nTo get the status of object restoration, you can send a HEAD request. Operations\n return the x-amz-restore header, which provides information about the restoration\n status, in the response. You can use Amazon S3 event notifications to notify you when a restore is\n initiated or completed. For more information, see Configuring Amazon S3 Event Notifications in\n the Amazon S3 User Guide.
After restoring an archived object, you can update the restoration period by reissuing the\n request with a new period. Amazon S3 updates the restoration period relative to the current time and\n charges only for the request-there are no data transfer charges. You cannot update the\n restoration period when Amazon S3 is actively processing your current restore request for the\n object.
\nIf your bucket has a lifecycle configuration with a rule that includes an expiration action,\n the object expiration overrides the life span that you specify in a restore request. For example,\n if you restore an object copy for 10 days, but the object is scheduled to expire in 3 days, Amazon S3\n deletes the object in 3 days. For more information about lifecycle configuration, see PutBucketLifecycleConfiguration and Object Lifecycle Management in\n Amazon S3 User Guide.
\nA successful action returns either the 200 OK or 202 Accepted status\n code.
If the object is not previously restored, then Amazon S3 returns 202 Accepted in\n the response.
If the object is previously restored, Amazon S3 returns 200 OK in the response.\n
Special errors:
\n\n Code: RestoreAlreadyInProgress\n
\n\n Cause: Object restore is already in progress.\n
\n\n HTTP Status Code: 409 Conflict\n
\n\n SOAP Fault Code Prefix: Client\n
\n\n Code: GlacierExpeditedRetrievalNotAvailable\n
\n\n Cause: expedited retrievals are currently not available. Try again later.\n (Returned if there is insufficient capacity to process the Expedited request. This error\n applies only to Expedited retrievals and not to S3 Standard or Bulk\n retrievals.)\n
\n\n HTTP Status Code: 503\n
\n\n SOAP Fault Code Prefix: N/A\n
\nThe following operations are related to RestoreObject:
Indicates the path in the provided S3 output location where Select results will be restored\n to.
", "smithy.api#httpHeader": "x-amz-restore-output-path" } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#RestoreObjectRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name containing the object to restore.
\n\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Object key for which the action was initiated.
", "smithy.api#httpLabel": {}, "smithy.api#required": {} } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "VersionId used to reference a specific version of the object.
", "smithy.api#httpQuery": "versionId" } }, "RestoreRequest": { "target": "com.amazonaws.s3#RestoreRequest", "traits": { "smithy.api#httpPayload": {}, "smithy.api#xmlName": "RestoreRequest" } }, "RequestPayer": { "target": "com.amazonaws.s3#RequestPayer", "traits": { "smithy.api#httpHeader": "x-amz-request-payer" } }, "ChecksumAlgorithm": { "target": "com.amazonaws.s3#ChecksumAlgorithm", "traits": { "smithy.api#documentation": "Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Lifetime of the active copy in days. Do not use with restores that specify\n OutputLocation.
The Days element is required for regular restores, and must not be provided for select\n requests.
" } }, "GlacierJobParameters": { "target": "com.amazonaws.s3#GlacierJobParameters", "traits": { "smithy.api#documentation": "S3 Glacier related parameters pertaining to this job. Do not use with restores that specify\n OutputLocation.
Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3 Select can\n continue to use the feature as usual. Learn more\n
\nType of restore request.
" } }, "Tier": { "target": "com.amazonaws.s3#Tier", "traits": { "smithy.api#documentation": "Retrieval tier at which the restore will be processed.
" } }, "Description": { "target": "com.amazonaws.s3#Description", "traits": { "smithy.api#documentation": "The optional description for the job.
" } }, "SelectParameters": { "target": "com.amazonaws.s3#SelectParameters", "traits": { "smithy.api#documentation": "Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3 Select can\n continue to use the feature as usual. Learn more\n
\nDescribes the parameters for Select job types.
" } }, "OutputLocation": { "target": "com.amazonaws.s3#OutputLocation", "traits": { "smithy.api#documentation": "Describes the location where the restore job's output is stored.
" } } }, "traits": { "smithy.api#documentation": "Container for restore job parameters.
" } }, "com.amazonaws.s3#RestoreRequestType": { "type": "enum", "members": { "SELECT": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "SELECT" } } } }, "com.amazonaws.s3#RestoreStatus": { "type": "structure", "members": { "IsRestoreInProgress": { "target": "com.amazonaws.s3#IsRestoreInProgress", "traits": { "smithy.api#documentation": "Specifies whether the object is currently being restored. If the object restoration is in progress,\n the header returns the value TRUE. For example:
\n x-amz-optional-object-attributes: IsRestoreInProgress=\"true\"\n
If the object restoration has completed, the header returns the value FALSE. For\n example:
\n x-amz-optional-object-attributes: IsRestoreInProgress=\"false\",\n RestoreExpiryDate=\"2012-12-21T00:00:00.000Z\"\n
If the object hasn't been restored, there is no header response.
" } }, "RestoreExpiryDate": { "target": "com.amazonaws.s3#RestoreExpiryDate", "traits": { "smithy.api#documentation": "Indicates when the restored copy will expire. This value is populated only if the object has already\n been restored. For example:
\n\n x-amz-optional-object-attributes: IsRestoreInProgress=\"false\",\n RestoreExpiryDate=\"2012-12-21T00:00:00.000Z\"\n
Specifies the restoration status of an object. Objects in certain storage classes must be restored\n before they can be retrieved. For more information about these storage classes and how to work with\n archived objects, see \n Working with archived objects in the Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets. Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
A container for describing a condition that must be met for the specified redirect to apply. For\n example, 1. If request is for pages in the /docs folder, redirect to the\n /documents folder. 2. If request results in HTTP error 4xx, redirect request to another\n host where you might process the error.
Container for redirect information. You can redirect requests to another host, to another page, or\n with another protocol. In the event of an error, you can specify a different error code to\n return.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Specifies the redirect behavior and when a redirect is applied. For more information about routing\n rules, see Configuring\n advanced conditional redirects in the Amazon S3 User Guide.
" } }, "com.amazonaws.s3#RoutingRules": { "type": "list", "member": { "target": "com.amazonaws.s3#RoutingRule", "traits": { "smithy.api#xmlName": "RoutingRule" } } }, "com.amazonaws.s3#S3KeyFilter": { "type": "structure", "members": { "FilterRules": { "target": "com.amazonaws.s3#FilterRuleList", "traits": { "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "FilterRule" } } }, "traits": { "smithy.api#documentation": "A container for object key name prefix and suffix filtering rules.
" } }, "com.amazonaws.s3#S3Location": { "type": "structure", "members": { "BucketName": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket where the restore results will be placed.
", "smithy.api#required": {} } }, "Prefix": { "target": "com.amazonaws.s3#LocationPrefix", "traits": { "smithy.api#documentation": "The prefix that is prepended to the restore results for this request.
", "smithy.api#required": {} } }, "Encryption": { "target": "com.amazonaws.s3#Encryption" }, "CannedACL": { "target": "com.amazonaws.s3#ObjectCannedACL", "traits": { "smithy.api#documentation": "The canned ACL to apply to the restore results.
" } }, "AccessControlList": { "target": "com.amazonaws.s3#Grants", "traits": { "smithy.api#documentation": "A list of grants that control access to the staged results.
" } }, "Tagging": { "target": "com.amazonaws.s3#Tagging", "traits": { "smithy.api#documentation": "The tag-set that is applied to the restore results.
" } }, "UserMetadata": { "target": "com.amazonaws.s3#UserMetadata", "traits": { "smithy.api#documentation": "A list of metadata to store with the restore results in S3.
" } }, "StorageClass": { "target": "com.amazonaws.s3#StorageClass", "traits": { "smithy.api#documentation": "The class of storage used to store the restore results.
" } } }, "traits": { "smithy.api#documentation": "Describes an Amazon S3 location that will receive the results of the restore request.
" } }, "com.amazonaws.s3#S3RegionalOrS3ExpressBucketArnString": { "type": "string", "traits": { "smithy.api#length": { "min": 1, "max": 128 }, "smithy.api#pattern": "^arn:[^:]+:(s3|s3express):" } }, "com.amazonaws.s3#S3TablesArn": { "type": "string" }, "com.amazonaws.s3#S3TablesBucketArn": { "type": "string" }, "com.amazonaws.s3#S3TablesBucketType": { "type": "enum", "members": { "aws": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "aws" } }, "customer": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "customer" } } } }, "com.amazonaws.s3#S3TablesDestination": { "type": "structure", "members": { "TableBucketArn": { "target": "com.amazonaws.s3#S3TablesBucketArn", "traits": { "smithy.api#documentation": "The Amazon Resource Name (ARN) for the table bucket that's specified as the destination in the\n metadata table configuration. The destination table bucket must be in the same Region and Amazon Web Services account\n as the general purpose bucket.
", "smithy.api#required": {} } }, "TableName": { "target": "com.amazonaws.s3#S3TablesName", "traits": { "smithy.api#documentation": " The name for the metadata table in your metadata table configuration. The specified metadata table\n name must be unique within the aws_s3_metadata namespace in the destination table bucket.\n
The destination information for a V1 S3 Metadata configuration. The destination table bucket must\n be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata table name\n must be unique within the aws_s3_metadata namespace in the destination table bucket.\n
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete \n and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create \n a live inventory table.
\nThe Amazon Resource Name (ARN) for the table bucket that's specified as the destination in the\n metadata table configuration. The destination table bucket must be in the same Region and Amazon Web Services account\n as the general purpose bucket.
", "smithy.api#required": {} } }, "TableName": { "target": "com.amazonaws.s3#S3TablesName", "traits": { "smithy.api#documentation": " The name for the metadata table in your metadata table configuration. The specified metadata table\n name must be unique within the aws_s3_metadata namespace in the destination table bucket.\n
The Amazon Resource Name (ARN) for the metadata table in the metadata table configuration. The\n specified metadata table name must be unique within the aws_s3_metadata namespace in the\n destination table bucket.
The table bucket namespace for the metadata table in your metadata table configuration. This value\n is always aws_s3_metadata.
The destination information for a V1 S3 Metadata configuration. The destination table bucket must\n be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata table name\n must be unique within the aws_s3_metadata namespace in the destination table bucket.\n
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete \n and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create \n a live inventory table.
\nSpecifies the ID of the Key Management Service (KMS) symmetric encryption customer managed key to use for encrypting\n inventory reports.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Specifies the use of SSE-KMS to encrypt delivered inventory reports.
", "smithy.api#xmlName": "SSE-KMS" } }, "com.amazonaws.s3#SSEKMSEncryptionContext": { "type": "string", "traits": { "smithy.api#sensitive": {} } }, "com.amazonaws.s3#SSEKMSKeyId": { "type": "string", "traits": { "smithy.api#sensitive": {} } }, "com.amazonaws.s3#SSES3": { "type": "structure", "members": {}, "traits": { "smithy.api#documentation": "Specifies the use of SSE-S3 to encrypt delivered inventory reports.
", "smithy.api#xmlName": "SSE-S3" } }, "com.amazonaws.s3#ScanRange": { "type": "structure", "members": { "Start": { "target": "com.amazonaws.s3#Start", "traits": { "smithy.api#documentation": "Specifies the start of the byte range. This parameter is optional. Valid values: non-negative\n integers. The default value is 0. If only start is supplied, it means scan from that point\n to the end of the file. For example,\n
Specifies the end of the byte range. This parameter is optional. Valid values: non-negative\n integers. The default value is one less than the size of the object being queried. If only the End\n parameter is supplied, it is interpreted to mean scan the last N bytes of the file. For example,\n
Specifies the byte range of the object to get the records from. A record is processed when its first\n byte is contained by the range. This parameter is optional, but when specified, it must not be empty.\n See RFC 2616, Section 14.35.1 about how to specify the start and end of the range.
" } }, "com.amazonaws.s3#SelectObjectContent": { "type": "operation", "input": { "target": "com.amazonaws.s3#SelectObjectContentRequest" }, "output": { "target": "com.amazonaws.s3#SelectObjectContentOutput" }, "traits": { "smithy.api#documentation": "This operation is not supported for directory buckets.
\nThis action filters the contents of an Amazon S3 object based on a simple structured query language (SQL)\n statement. In the request, along with the SQL expression, you must also specify a data serialization\n format (JSON, CSV, or Apache Parquet) of the object. Amazon S3 uses this format to parse object data into\n records, and returns only records that match the specified SQL expression. You must also specify the\n data serialization format for the response.
\nThis functionality is not supported for Amazon S3 on Outposts.
\nFor more information about Amazon S3 Select, see Selecting Content from Objects\n and SELECT Command in\n the Amazon S3 User Guide.
\n \nYou must have the s3:GetObject permission for this operation.\u00a0Amazon S3 Select does\n not support anonymous access. For more information about permissions, see Specifying Permissions\n in a Policy in the Amazon S3 User Guide.
You can use Amazon S3 Select to query objects that have the following format properties:
\n\n CSV, JSON, and Parquet - Objects must be in CSV, JSON, or Parquet\n format.
\n\n UTF-8 - UTF-8 is the only encoding type Amazon S3 Select supports.
\n\n GZIP or BZIP2 - CSV and JSON files can be compressed using GZIP or\n BZIP2. GZIP and BZIP2 are the only compression formats that Amazon S3 Select supports for CSV and\n JSON files. Amazon S3 Select supports columnar compression for Parquet using GZIP or Snappy. Amazon S3\n Select does not support whole-object compression for Parquet objects.
\n\n Server-side encryption - Amazon S3 Select supports querying objects that\n are protected with server-side encryption.
\nFor objects that are encrypted with customer-provided encryption keys (SSE-C), you must\n use HTTPS, and you must use the headers that are documented in the GetObject. For more information about\n SSE-C, see Server-Side Encryption\n (Using Customer-Provided Encryption Keys) in the\n Amazon S3 User Guide.
\nFor objects that are encrypted with Amazon S3 managed keys (SSE-S3) and Amazon Web Services KMS keys\n (SSE-KMS), server-side encryption is handled transparently, so you don't need to specify\n anything. For more information about server-side encryption, including SSE-S3 and SSE-KMS, see\n Protecting\n Data Using Server-Side Encryption in the\n Amazon S3 User Guide.
\nGiven the response size is unknown, Amazon S3 Select streams the response as a series of messages\n and includes a Transfer-Encoding header with chunked as its value in the\n response. For more information, see Appendix: SelectObjectContent\n Response.
The SelectObjectContent action does not support the following\n GetObject functionality. For more information, see GetObject.
\n Range: Although you can specify a scan range for an Amazon S3 Select request (see\n SelectObjectContentRequest - ScanRange in the request parameters), you\n cannot specify the range of bytes of an object to return.
The GLACIER, DEEP_ARCHIVE, and REDUCED_REDUNDANCY\n storage classes, or the ARCHIVE_ACCESS and DEEP_ARCHIVE_ACCESS\n access tiers of the INTELLIGENT_TIERING storage class: You cannot query objects\n in the GLACIER, DEEP_ARCHIVE, or REDUCED_REDUNDANCY\n storage classes, nor objects in the ARCHIVE_ACCESS or\n DEEP_ARCHIVE_ACCESS access tiers of the INTELLIGENT_TIERING\n storage class. For more information about storage classes, see Using Amazon S3 storage classes\n in the Amazon S3 User Guide.
For a list of special errors for this operation, see List of SELECT\n Object Content Error Codes\n
\nThe following operations are related to SelectObjectContent:
\n GetObject\n
\nThe Records Event.
" } }, "Stats": { "target": "com.amazonaws.s3#StatsEvent", "traits": { "smithy.api#documentation": "The Stats Event.
" } }, "Progress": { "target": "com.amazonaws.s3#ProgressEvent", "traits": { "smithy.api#documentation": "The Progress Event.
" } }, "Cont": { "target": "com.amazonaws.s3#ContinuationEvent", "traits": { "smithy.api#documentation": "The Continuation Event.
" } }, "End": { "target": "com.amazonaws.s3#EndEvent", "traits": { "smithy.api#documentation": "The End Event.
" } } }, "traits": { "smithy.api#documentation": "The container for selecting objects from a content event stream.
", "smithy.api#streaming": {} } }, "com.amazonaws.s3#SelectObjectContentOutput": { "type": "structure", "members": { "Payload": { "target": "com.amazonaws.s3#SelectObjectContentEventStream", "traits": { "smithy.api#documentation": "The array of results.
", "smithy.api#httpPayload": {} } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#SelectObjectContentRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The S3 bucket.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "The object key.
", "smithy.api#httpLabel": {}, "smithy.api#required": {} } }, "SSECustomerAlgorithm": { "target": "com.amazonaws.s3#SSECustomerAlgorithm", "traits": { "smithy.api#documentation": "The server-side encryption (SSE) algorithm used to encrypt the object. This parameter is needed only when the object was created \n using a checksum algorithm. For more information,\n see Protecting data using SSE-C keys in the\n Amazon S3 User Guide.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-algorithm" } }, "SSECustomerKey": { "target": "com.amazonaws.s3#SSECustomerKey", "traits": { "smithy.api#documentation": "The server-side encryption (SSE) customer managed key. This parameter is needed only when the object was created using a checksum algorithm. \n For more information, see\n Protecting data using SSE-C keys in the\n Amazon S3 User Guide.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-key" } }, "SSECustomerKeyMD5": { "target": "com.amazonaws.s3#SSECustomerKeyMD5", "traits": { "smithy.api#documentation": "The MD5 server-side encryption (SSE) customer managed key. This parameter is needed only when the object was created using a checksum \n algorithm. For more information,\n see Protecting data using SSE-C keys in the\n Amazon S3 User Guide.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-key-MD5" } }, "Expression": { "target": "com.amazonaws.s3#Expression", "traits": { "smithy.api#documentation": "The expression that is used to query the object.
", "smithy.api#required": {} } }, "ExpressionType": { "target": "com.amazonaws.s3#ExpressionType", "traits": { "smithy.api#documentation": "The type of the provided expression (for example, SQL).
", "smithy.api#required": {} } }, "RequestProgress": { "target": "com.amazonaws.s3#RequestProgress", "traits": { "smithy.api#documentation": "Specifies if periodic request progress information should be enabled.
" } }, "InputSerialization": { "target": "com.amazonaws.s3#InputSerialization", "traits": { "smithy.api#documentation": "Describes the format of the data in the object that is being queried.
", "smithy.api#required": {} } }, "OutputSerialization": { "target": "com.amazonaws.s3#OutputSerialization", "traits": { "smithy.api#documentation": "Describes the format of the data that you want Amazon S3 to return in response.
", "smithy.api#required": {} } }, "ScanRange": { "target": "com.amazonaws.s3#ScanRange", "traits": { "smithy.api#documentation": "Specifies the byte range of the object to get the records from. A record is processed when its first\n byte is contained by the range. This parameter is optional, but when specified, it must not be empty.\n See RFC 2616, Section 14.35.1 about how to specify the start and end of the range.
\n\n ScanRangemay be used in the following ways:
\n
\n
\n
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Learn Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3\n Select can continue to use the feature as usual. Learn more\n
\nRequest to filter the contents of an Amazon S3 object based on a simple Structured Query Language (SQL)\n statement. In the request, along with the SQL expression, you must specify a data serialization format\n (JSON or CSV) of the object. Amazon S3 uses this to parse object data into records. It returns only records\n that match the specified SQL expression. You must also specify the data serialization format for the\n response. For more information, see S3Select API Documentation.
", "smithy.api#input": {} } }, "com.amazonaws.s3#SelectParameters": { "type": "structure", "members": { "InputSerialization": { "target": "com.amazonaws.s3#InputSerialization", "traits": { "smithy.api#documentation": "Describes the serialization format of the object.
", "smithy.api#required": {} } }, "ExpressionType": { "target": "com.amazonaws.s3#ExpressionType", "traits": { "smithy.api#documentation": "The type of the provided expression (for example, SQL).
", "smithy.api#required": {} } }, "Expression": { "target": "com.amazonaws.s3#Expression", "traits": { "smithy.api#documentation": "Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3 Select can\n continue to use the feature as usual. Learn more\n
\nThe expression that is used to query the object.
", "smithy.api#required": {} } }, "OutputSerialization": { "target": "com.amazonaws.s3#OutputSerialization", "traits": { "smithy.api#documentation": "Describes how the results of the Select job are serialized.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3 Select can\n continue to use the feature as usual. Learn more\n
\nDescribes the parameters for Select job types.
\nLearn How to\n optimize querying your data in Amazon S3 using Amazon Athena, S3 Object Lambda, or client-side\n filtering.
" } }, "com.amazonaws.s3#ServerSideEncryption": { "type": "enum", "members": { "AES256": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "AES256" } }, "aws_fsx": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "aws:fsx" } }, "aws_kms": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "aws:kms" } }, "aws_kms_dsse": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "aws:kms:dsse" } } } }, "com.amazonaws.s3#ServerSideEncryptionByDefault": { "type": "structure", "members": { "SSEAlgorithm": { "target": "com.amazonaws.s3#ServerSideEncryption", "traits": { "smithy.api#documentation": "Server-side encryption algorithm to use for the default encryption.
\nFor directory buckets, there are only two supported values for server-side encryption: AES256 and aws:kms.
Amazon Web Services Key Management Service (KMS) customer managed key ID to use for the default encryption.
\n\n General purpose buckets - This parameter is allowed if and\n only if SSEAlgorithm is set to aws:kms or\n aws:kms:dsse.
\n Directory buckets - This parameter is allowed if and\n only if SSEAlgorithm is set to aws:kms.
You can specify the key ID, key alias, or the Amazon Resource Name (ARN) of the KMS key.
\nKey ID: 1234abcd-12ab-34cd-56ef-1234567890ab\n
Key ARN:\n arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab\n
Key Alias: alias/alias-name\n
If you are using encryption with cross-account or Amazon Web Services service operations, you must use a fully\n qualified KMS key ARN. For more information, see Using\n encryption for cross-account operations.
\n\n General purpose buckets - If you're specifying a customer\n managed KMS key, we recommend using a fully qualified KMS key ARN. If you use a KMS key\n alias instead, then KMS resolves the key within the requester\u2019s account. This behavior can\n result in data that's encrypted with a KMS key that belongs to the requester, and not the bucket\n owner. Also, if you use a key ID, you can run into a LogDestination undeliverable error when\n creating a VPC flow log.
\n\n Directory buckets -\n When you specify an KMS customer managed key for encryption in your directory bucket, only use the key ID or key ARN. The key alias format of the KMS key isn't supported.
\nAmazon S3 only supports symmetric encryption KMS keys. For more information, see Asymmetric keys in\n Amazon Web Services KMS in the Amazon Web Services Key Management Service Developer Guide.
\nDescribes the default server-side encryption to apply to new objects in the bucket. If a PUT Object\n request doesn't specify any server-side encryption, this default encryption will be applied. For more\n information, see PutBucketEncryption.
\n\n General purpose buckets - If you don't specify a customer managed key\n at configuration, Amazon S3 automatically creates an Amazon Web Services KMS key (aws/s3) in your Amazon Web Services\n account the first time that you add an object encrypted with SSE-KMS to a bucket. By default, Amazon S3\n uses this KMS key for SSE-KMS.
\n Directory buckets -\n Your SSE-KMS configuration can only support 1 customer managed key per directory bucket's lifetime. \nThe Amazon Web Services managed key (aws/s3) isn't supported. \n
\n Directory buckets -\n For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS.
\nContainer for information about a particular server-side encryption configuration rule.
", "smithy.api#required": {}, "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Rule" } } }, "traits": { "smithy.api#documentation": "Specifies the default server-side-encryption configuration.
" } }, "com.amazonaws.s3#ServerSideEncryptionRule": { "type": "structure", "members": { "ApplyServerSideEncryptionByDefault": { "target": "com.amazonaws.s3#ServerSideEncryptionByDefault", "traits": { "smithy.api#documentation": "Specifies the default server-side encryption to apply to new objects in the bucket. If a PUT Object\n request doesn't specify any server-side encryption, this default encryption will be applied.
" } }, "BucketKeyEnabled": { "target": "com.amazonaws.s3#BucketKeyEnabled", "traits": { "smithy.api#documentation": "Specifies whether Amazon S3 should use an S3 Bucket Key with server-side encryption using KMS (SSE-KMS)\n for new objects in the bucket. Existing objects are not affected. Setting the\n BucketKeyEnabled element to true causes Amazon S3 to use an S3 Bucket Key.
\n General purpose buckets - By default, S3 Bucket Key is not\n enabled. For more information, see Amazon S3 Bucket Keys in the\n Amazon S3 User Guide.
\n\n Directory buckets -\n S3 Bucket Keys are always enabled for GET and PUT operations in a directory bucket and can\u2019t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through CopyObject, UploadPartCopy, the Copy operation in Batch Operations, or \n the import jobs. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.
Specifies the default server-side encryption configuration.
\n\n General purpose buckets - If you're specifying a customer\n managed KMS key, we recommend using a fully qualified KMS key ARN. If you use a KMS key\n alias instead, then KMS resolves the key within the requester\u2019s account. This behavior can\n result in data that's encrypted with a KMS key that belongs to the requester, and not the bucket\n owner.
\n\n Directory buckets -\n When you specify an KMS customer managed key for encryption in your directory bucket, only use the key ID or key ARN. The key alias format of the KMS key isn't supported.
\nA unique identifier that's associated with a secret access key. The access key ID and the secret\n access key are used together to sign programmatic Amazon Web Services requests cryptographically.
", "smithy.api#required": {}, "smithy.api#xmlName": "AccessKeyId" } }, "SecretAccessKey": { "target": "com.amazonaws.s3#SessionCredentialValue", "traits": { "smithy.api#documentation": "A key that's used with the access key ID to cryptographically sign programmatic Amazon Web Services requests.\n Signing a request identifies the sender and prevents the request from being altered.
", "smithy.api#required": {}, "smithy.api#xmlName": "SecretAccessKey" } }, "SessionToken": { "target": "com.amazonaws.s3#SessionCredentialValue", "traits": { "smithy.api#documentation": "A part of the temporary security credentials. The session token is used to validate the temporary\n security credentials.\n \n
", "smithy.api#required": {}, "smithy.api#xmlName": "SessionToken" } }, "Expiration": { "target": "com.amazonaws.s3#SessionExpiration", "traits": { "smithy.api#documentation": "Temporary security credentials expire after a specified interval. After temporary credentials\n expire, any calls that you make with those credentials will fail. So you must generate a new set of\n temporary credentials. Temporary credentials cannot be extended or refreshed beyond the original\n specified interval.
", "smithy.api#required": {}, "smithy.api#xmlName": "Expiration" } } }, "traits": { "smithy.api#documentation": "The established temporary security credentials of the session.
\n\n Directory buckets - These session credentials are only\n supported for the authentication and authorization of Zonal endpoint API operations on directory buckets.
\nTo use simple format for S3 keys for log objects, set SimplePrefix to an empty object.
\n\n [DestinationPrefix][YYYY]-[MM]-[DD]-[hh]-[mm]-[ss]-[UniqueString]\n
A container for filter information for the selection of Amazon S3 objects encrypted with Amazon Web Services KMS. If\n you include SourceSelectionCriteria in the replication configuration, this element is\n required.
A filter that you can specify for selections for modifications on replicas. Amazon S3 doesn't replicate\n replica modifications by default. In the latest version of replication configuration (when\n Filter is specified), you can specify this element and set the status to\n Enabled to replicate modifications on replicas.
If you don't specify the Filter element, Amazon S3 assumes that the replication\n configuration is the earlier version, V1. In the earlier version, this element is not allowed
A container that describes additional filters for identifying the source objects that you want to\n replicate. You can choose to enable or disable the replication of these objects. Currently, Amazon S3\n supports only the filter that you can specify for objects created with server-side encryption using a\n customer managed key stored in Amazon Web Services Key Management Service (SSE-KMS).
" } }, "com.amazonaws.s3#SseKmsEncryptedObjects": { "type": "structure", "members": { "Status": { "target": "com.amazonaws.s3#SseKmsEncryptedObjectsStatus", "traits": { "smithy.api#documentation": "Specifies whether Amazon S3 replicates objects created with server-side encryption using an Amazon Web Services KMS key\n stored in Amazon Web Services Key Management Service.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "A container for filter information for the selection of S3 objects encrypted with Amazon Web Services KMS.
" } }, "com.amazonaws.s3#SseKmsEncryptedObjectsStatus": { "type": "enum", "members": { "Enabled": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Enabled" } }, "Disabled": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Disabled" } } } }, "com.amazonaws.s3#Start": { "type": "long" }, "com.amazonaws.s3#StartAfter": { "type": "string" }, "com.amazonaws.s3#Stats": { "type": "structure", "members": { "BytesScanned": { "target": "com.amazonaws.s3#BytesScanned", "traits": { "smithy.api#documentation": "The total number of object bytes scanned.
" } }, "BytesProcessed": { "target": "com.amazonaws.s3#BytesProcessed", "traits": { "smithy.api#documentation": "The total number of uncompressed object bytes processed.
" } }, "BytesReturned": { "target": "com.amazonaws.s3#BytesReturned", "traits": { "smithy.api#documentation": "The total number of bytes of records payload data returned.
" } } }, "traits": { "smithy.api#documentation": "Container for the stats details.
" } }, "com.amazonaws.s3#StatsEvent": { "type": "structure", "members": { "Details": { "target": "com.amazonaws.s3#Stats", "traits": { "smithy.api#documentation": "The Stats event details.
", "smithy.api#eventPayload": {} } } }, "traits": { "smithy.api#documentation": "Container for the Stats Event.
" } }, "com.amazonaws.s3#StorageClass": { "type": "enum", "members": { "STANDARD": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "STANDARD" } }, "REDUCED_REDUNDANCY": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "REDUCED_REDUNDANCY" } }, "STANDARD_IA": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "STANDARD_IA" } }, "ONEZONE_IA": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ONEZONE_IA" } }, "INTELLIGENT_TIERING": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "INTELLIGENT_TIERING" } }, "GLACIER": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "GLACIER" } }, "DEEP_ARCHIVE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "DEEP_ARCHIVE" } }, "OUTPOSTS": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "OUTPOSTS" } }, "GLACIER_IR": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "GLACIER_IR" } }, "SNOW": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "SNOW" } }, "EXPRESS_ONEZONE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "EXPRESS_ONEZONE" } }, "FSX_OPENZFS": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "FSX_OPENZFS" } } } }, "com.amazonaws.s3#StorageClassAnalysis": { "type": "structure", "members": { "DataExport": { "target": "com.amazonaws.s3#StorageClassAnalysisDataExport", "traits": { "smithy.api#documentation": "Specifies how data related to the storage class analysis for an Amazon S3 bucket should be\n exported.
" } } }, "traits": { "smithy.api#documentation": "Specifies data related to access patterns to be collected and made available to analyze the\n tradeoffs between different storage classes for an Amazon S3 bucket.
" } }, "com.amazonaws.s3#StorageClassAnalysisDataExport": { "type": "structure", "members": { "OutputSchemaVersion": { "target": "com.amazonaws.s3#StorageClassAnalysisSchemaVersion", "traits": { "smithy.api#documentation": "The version of the output schema to use when exporting data. Must be V_1.
The place to store the data for an analysis.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Container for data related to the storage class analysis for an Amazon S3 bucket for export.
" } }, "com.amazonaws.s3#StorageClassAnalysisSchemaVersion": { "type": "enum", "members": { "V_1": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "V_1" } } } }, "com.amazonaws.s3#StreamingBlob": { "type": "blob", "traits": { "smithy.api#streaming": {} } }, "com.amazonaws.s3#Suffix": { "type": "string" }, "com.amazonaws.s3#TableSseAlgorithm": { "type": "enum", "members": { "aws_kms": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "aws:kms" } }, "AES256": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "AES256" } } } }, "com.amazonaws.s3#Tag": { "type": "structure", "members": { "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "Name of the object key.
", "smithy.api#required": {} } }, "Value": { "target": "com.amazonaws.s3#Value", "traits": { "smithy.api#documentation": "Value of the tag.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "A container of a key value name pair.
" } }, "com.amazonaws.s3#TagCount": { "type": "integer" }, "com.amazonaws.s3#TagSet": { "type": "list", "member": { "target": "com.amazonaws.s3#Tag", "traits": { "smithy.api#xmlName": "Tag" } } }, "com.amazonaws.s3#Tagging": { "type": "structure", "members": { "TagSet": { "target": "com.amazonaws.s3#TagSet", "traits": { "smithy.api#documentation": "A collection for a set of tags
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "Container for TagSet elements.
Container for the person being granted permissions.
", "smithy.api#xmlNamespace": { "uri": "http://www.w3.org/2001/XMLSchema-instance", "prefix": "xsi" } } }, "Permission": { "target": "com.amazonaws.s3#BucketLogsPermission", "traits": { "smithy.api#documentation": "Logging permissions assigned to the grantee for the bucket.
" } } }, "traits": { "smithy.api#documentation": "Container for granting information.
\nBuckets that use the bucket owner enforced setting for Object Ownership don't support target grants.\n For more information, see Permissions server access log delivery in the Amazon S3 User Guide.
" } }, "com.amazonaws.s3#TargetGrants": { "type": "list", "member": { "target": "com.amazonaws.s3#TargetGrant", "traits": { "smithy.api#xmlName": "Grant" } } }, "com.amazonaws.s3#TargetObjectKeyFormat": { "type": "structure", "members": { "SimplePrefix": { "target": "com.amazonaws.s3#SimplePrefix", "traits": { "smithy.api#documentation": "To use the simple format for S3 keys for log objects. To specify SimplePrefix format, set\n SimplePrefix to {}.
", "smithy.api#xmlName": "SimplePrefix" } }, "PartitionedPrefix": { "target": "com.amazonaws.s3#PartitionedPrefix", "traits": { "smithy.api#documentation": "Partitioned S3 key for log objects.
", "smithy.api#xmlName": "PartitionedPrefix" } } }, "traits": { "smithy.api#documentation": "Amazon S3 key format for log objects. Only one format, PartitionedPrefix or SimplePrefix, is\n allowed.
" } }, "com.amazonaws.s3#TargetPrefix": { "type": "string" }, "com.amazonaws.s3#Tier": { "type": "enum", "members": { "Standard": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Standard" } }, "Bulk": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Bulk" } }, "Expedited": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Expedited" } } } }, "com.amazonaws.s3#Tiering": { "type": "structure", "members": { "Days": { "target": "com.amazonaws.s3#IntelligentTieringDays", "traits": { "smithy.api#documentation": "The number of consecutive days of no access after which an object will be eligible to be\n transitioned to the corresponding tier. The minimum number of days specified for Archive Access tier\n must be at least 90 days and Deep Archive Access tier must be at least 180 days. The maximum can be up to\n 2 years (730 days).
", "smithy.api#required": {} } }, "AccessTier": { "target": "com.amazonaws.s3#IntelligentTieringAccessTier", "traits": { "smithy.api#documentation": "S3 Intelligent-Tiering access tier. See Storage class for\n automatically optimizing frequently and infrequently accessed objects for a list of access\n tiers in the S3 Intelligent-Tiering storage class.
", "smithy.api#required": {} } } }, "traits": { "smithy.api#documentation": "The S3 Intelligent-Tiering storage class is designed to optimize storage costs by automatically\n moving data to the most cost-effective storage access tier, without additional operational\n overhead.
" } }, "com.amazonaws.s3#TieringList": { "type": "list", "member": { "target": "com.amazonaws.s3#Tiering" } }, "com.amazonaws.s3#Token": { "type": "string" }, "com.amazonaws.s3#TooManyParts": { "type": "structure", "members": {}, "traits": { "smithy.api#documentation": "You have attempted to add more parts than the maximum of 10000 that are allowed for this object.\n You can use the CopyObject operation to copy this object to another and then add more data to the newly\n copied object.
", "smithy.api#error": "client", "smithy.api#httpError": 400 } }, "com.amazonaws.s3#TopicArn": { "type": "string" }, "com.amazonaws.s3#TopicConfiguration": { "type": "structure", "members": { "Id": { "target": "com.amazonaws.s3#NotificationId" }, "TopicArn": { "target": "com.amazonaws.s3#TopicArn", "traits": { "smithy.api#documentation": "The Amazon Resource Name (ARN) of the Amazon SNS topic to which Amazon S3 publishes a message when it\n detects events of the specified type.
", "smithy.api#required": {}, "smithy.api#xmlName": "Topic" } }, "Events": { "target": "com.amazonaws.s3#EventList", "traits": { "smithy.api#documentation": "The Amazon S3 bucket event about which to send notifications. For more information, see Supported Event Types in\n the Amazon S3 User Guide.
", "smithy.api#required": {}, "smithy.api#xmlFlattened": {}, "smithy.api#xmlName": "Event" } }, "Filter": { "target": "com.amazonaws.s3#NotificationConfigurationFilter" } }, "traits": { "smithy.api#documentation": "A container for specifying the configuration for publication of messages to an Amazon Simple\n Notification Service (Amazon SNS) topic when Amazon S3 detects specified events.
" } }, "com.amazonaws.s3#TopicConfigurationList": { "type": "list", "member": { "target": "com.amazonaws.s3#TopicConfiguration" } }, "com.amazonaws.s3#Transition": { "type": "structure", "members": { "Date": { "target": "com.amazonaws.s3#Date", "traits": { "smithy.api#documentation": "Indicates when objects are transitioned to the specified storage class. The date value must be in\n ISO 8601 format. The time is always midnight UTC.
" } }, "Days": { "target": "com.amazonaws.s3#Days", "traits": { "smithy.api#documentation": "Indicates the number of days after creation when objects are transitioned to the specified storage\n class. If the specified storage class is INTELLIGENT_TIERING, GLACIER_IR,\n GLACIER, or DEEP_ARCHIVE, valid values are 0 or positive\n integers. If the specified storage class is STANDARD_IA or ONEZONE_IA, valid\n values are positive integers greater than 30. Be aware that some storage classes have a\n minimum storage duration and that you're charged for transitioning objects before their minimum storage\n duration. For more information, see Constraints and considerations for transitions in the Amazon S3 User\n Guide.
The storage class to which you want the object to transition.
" } } }, "traits": { "smithy.api#documentation": "Specifies when an object transitions to a specified storage class. For more information about Amazon S3\n lifecycle configuration rules, see Transitioning Objects Using\n Amazon S3 Lifecycle in the Amazon S3 User Guide.
" } }, "com.amazonaws.s3#TransitionDefaultMinimumObjectSize": { "type": "enum", "members": { "varies_by_storage_class": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "varies_by_storage_class" } }, "all_storage_classes_128K": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "all_storage_classes_128K" } } } }, "com.amazonaws.s3#TransitionList": { "type": "list", "member": { "target": "com.amazonaws.s3#Transition" } }, "com.amazonaws.s3#TransitionStorageClass": { "type": "enum", "members": { "GLACIER": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "GLACIER" } }, "STANDARD_IA": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "STANDARD_IA" } }, "ONEZONE_IA": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "ONEZONE_IA" } }, "INTELLIGENT_TIERING": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "INTELLIGENT_TIERING" } }, "DEEP_ARCHIVE": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "DEEP_ARCHIVE" } }, "GLACIER_IR": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "GLACIER_IR" } } } }, "com.amazonaws.s3#Type": { "type": "enum", "members": { "CanonicalUser": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "CanonicalUser" } }, "AmazonCustomerByEmail": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "AmazonCustomerByEmail" } }, "Group": { "target": "smithy.api#Unit", "traits": { "smithy.api#enumValue": "Group" } } } }, "com.amazonaws.s3#URI": { "type": "string" }, "com.amazonaws.s3#UpdateBucketMetadataInventoryTableConfiguration": { "type": "operation", "input": { "target": "com.amazonaws.s3#UpdateBucketMetadataInventoryTableConfigurationRequest" }, "output": { "target": "smithy.api#Unit" }, "traits": { "aws.protocols#httpChecksum": { "requestAlgorithmMember": "ChecksumAlgorithm", "requestChecksumRequired": true }, "smithy.api#documentation": "Enables or disables a live inventory table for an S3 Metadata configuration on a general \n purpose bucket. For more information, see\n Accelerating\n data discovery with S3 Metadata in the Amazon S3 User Guide.
\nTo use this operation, you must have the following permissions. For more information, see\n Setting up permissions for configuring metadata tables in the\n Amazon S3 User Guide.
\nIf you want to encrypt your inventory table with server-side encryption with Key Management Service\n (KMS) keys (SSE-KMS), you need additional permissions in your KMS key policy. For more\n information, see \n Setting up permissions for configuring metadata tables in the\n Amazon S3 User Guide.
\n\n s3:UpdateBucketMetadataInventoryTableConfiguration\n
\n s3tables:CreateTableBucket\n
\n s3tables:CreateNamespace\n
\n s3tables:GetTable\n
\n s3tables:CreateTable\n
\n s3tables:PutTablePolicy\n
\n s3tables:PutTableEncryption\n
\n kms:DescribeKey\n
The following operations are related to UpdateBucketMetadataInventoryTableConfiguration:
\n The general purpose bucket that corresponds to the metadata configuration that you want to \n enable or disable an inventory table for.\n
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "\n The Content-MD5 header for the inventory table configuration.\n
\n The checksum algorithm to use with your inventory table configuration.\n
", "smithy.api#httpHeader": "x-amz-sdk-checksum-algorithm" } }, "InventoryTableConfiguration": { "target": "com.amazonaws.s3#InventoryTableConfigurationUpdates", "traits": { "smithy.api#documentation": "\n The contents of your inventory table configuration. \n
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "InventoryTableConfiguration" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "\n The expected owner of the general purpose bucket that corresponds to the metadata table \n configuration that you want to enable or disable an inventory table for.\n
", "smithy.api#httpHeader": "x-amz-expected-bucket-owner" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#UpdateBucketMetadataJournalTableConfiguration": { "type": "operation", "input": { "target": "com.amazonaws.s3#UpdateBucketMetadataJournalTableConfigurationRequest" }, "output": { "target": "smithy.api#Unit" }, "traits": { "aws.protocols#httpChecksum": { "requestAlgorithmMember": "ChecksumAlgorithm", "requestChecksumRequired": true }, "smithy.api#documentation": "Enables or disables journal table record expiration for an S3 Metadata configuration on a general \n purpose bucket. For more information, see\n Accelerating\n data discovery with S3 Metadata in the Amazon S3 User Guide.
\nTo use this operation, you must have the s3:UpdateBucketMetadataJournalTableConfiguration\n permission. For more information, see Setting up permissions for\n configuring metadata tables in the Amazon S3 User Guide.
The following operations are related to UpdateBucketMetadataJournalTableConfiguration:
\n The general purpose bucket that corresponds to the metadata configuration that you want to \n enable or disable journal table record expiration for.\n
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Bucket" } } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "\n The Content-MD5 header for the journal table configuration.\n
\n The checksum algorithm to use with your journal table configuration.\n
", "smithy.api#httpHeader": "x-amz-sdk-checksum-algorithm" } }, "JournalTableConfiguration": { "target": "com.amazonaws.s3#JournalTableConfigurationUpdates", "traits": { "smithy.api#documentation": "\n The contents of your journal table configuration.\n
", "smithy.api#httpPayload": {}, "smithy.api#required": {}, "smithy.api#xmlName": "JournalTableConfiguration" } }, "ExpectedBucketOwner": { "target": "com.amazonaws.s3#AccountId", "traits": { "smithy.api#documentation": "\n The expected owner of the general purpose bucket that corresponds to the metadata table \n configuration that you want to enable or disable journal table record expiration for. \n
", "smithy.api#httpHeader": "x-amz-expected-bucket-owner" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#UploadIdMarker": { "type": "string" }, "com.amazonaws.s3#UploadPart": { "type": "operation", "input": { "target": "com.amazonaws.s3#UploadPartRequest" }, "output": { "target": "com.amazonaws.s3#UploadPartOutput" }, "traits": { "aws.protocols#httpChecksum": { "requestAlgorithmMember": "ChecksumAlgorithm" }, "smithy.api#documentation": "Uploads a part in a multipart upload.
\nIn this operation, you provide new data as a part of an object in your request. However, you have\n an option to specify your existing Amazon S3 object as a data source for the part you are uploading. To\n upload a part from an existing object, you use the UploadPartCopy operation.
\nYou must initiate a multipart upload (see CreateMultipartUpload) before you can\n upload any part. In response to your initiate request, Amazon S3 returns an upload ID, a unique identifier\n that you must include in your upload part request.
\nPart numbers can be any number from 1 to 10,000, inclusive. A part number uniquely identifies a part\n and also defines its position within the object being created. If you upload a new part using the same\n part number that was used with a previous part, the previously uploaded part is overwritten.
\nFor information about maximum and minimum part sizes and other multipart upload specifications, see\n Multipart upload\n limits in the Amazon S3 User Guide.
\nAfter you initiate multipart upload and upload one or more parts, you must either complete or\n abort multipart upload in order to stop getting charged for storage of the uploaded parts. Only after\n you either complete or abort multipart upload, Amazon S3 frees up the parts storage and stops charging you\n for the parts storage.
\nFor more information on multipart uploads, go to Multipart Upload Overview in the\n Amazon S3 User Guide .
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
\n General purpose bucket permissions - To perform a\n multipart upload with encryption using an Key Management Service key, the requester must have permission to\n the kms:Decrypt and kms:GenerateDataKey actions on the key. The\n requester must also have permissions for the kms:GenerateDataKey action for the\n CreateMultipartUpload API. Then, the requester needs permissions for the\n kms:Decrypt action on the UploadPart and\n UploadPartCopy APIs.
These permissions are required because Amazon S3 must decrypt and read data from the encrypted\n file parts before it completes the multipart upload. For more information about KMS\n permissions, see Protecting data using server-side\n encryption with KMS in the Amazon S3 User Guide. For information\n about the permissions required to use the multipart upload API, see Multipart upload and\n permissions and Multipart upload API and\n permissions in the Amazon S3 User Guide.
\n\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
If the object is encrypted with SSE-KMS, you must also have the\n kms:GenerateDataKey and kms:Decrypt permissions in IAM\n identity-based policies and KMS key policies for the KMS key.
\n General purpose bucket - To ensure that data is not corrupted\n traversing the network, specify the Content-MD5 header in the upload part request.\n Amazon S3 checks the part data against the provided MD5 value. If they do not match, Amazon S3 returns an\n error. If the upload request is signed with Signature Version 4, then Amazon Web Services S3 uses the\n x-amz-content-sha256 header as a checksum instead of Content-MD5. For\n more information see Authenticating Requests:\n Using the Authorization Header (Amazon Web Services Signature Version 4).
\n Directory buckets - MD5 is not supported by directory buckets. You can use checksum algorithms to check object integrity.
\n\n General purpose bucket - Server-side encryption is for\n data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers\n and decrypts it when you access it. You have mutually exclusive options to protect data using\n server-side encryption in Amazon S3, depending on how you choose to manage the encryption keys.\n Specifically, the encryption key options are Amazon S3 managed keys (SSE-S3), Amazon Web Services KMS keys\n (SSE-KMS), and Customer-Provided Keys (SSE-C). Amazon S3 encrypts data with server-side encryption\n using Amazon S3 managed keys (SSE-S3) by default. You can optionally tell Amazon S3 to encrypt data at\n rest using server-side encryption with other key options. The option you use depends on\n whether you want to use KMS keys (SSE-KMS) or provide your own encryption key\n (SSE-C).
\nServer-side encryption is supported by the S3 Multipart Upload operations. Unless you are\n using a customer-provided encryption key (SSE-C), you don't need to specify the encryption\n parameters in each UploadPart request. Instead, you only need to specify the server-side\n encryption parameters in the initial Initiate Multipart request. For more information, see\n CreateMultipartUpload.
\nIf you request server-side encryption using a customer-provided encryption key (SSE-C) in\n your initiate multipart upload request, you must provide identical encryption information in\n each part upload using the following request headers.
\nx-amz-server-side-encryption-customer-algorithm
\nx-amz-server-side-encryption-customer-key
\nx-amz-server-side-encryption-customer-key-MD5
\nFor more information, see Using Server-Side\n Encryption in the Amazon S3 User Guide.
\n\n Directory buckets -\n For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms).
Error Code: NoSuchUpload\n
Description: The specified multipart upload does not exist. The upload ID might be\n invalid, or the multipart upload might have been aborted or completed.
\nHTTP Status Code: 404 Not Found
\nSOAP Fault Code Prefix: Client
\n\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following operations are related to UploadPart:
\n AbortMultipartUpload\n
\n\n ListParts\n
\n\n ListMultipartUploads\n
\nUploads a part by copying data from an existing object as data source. To specify the data source,\n you add the request header x-amz-copy-source in your request. To specify a byte range, you\n add the request header x-amz-copy-source-range in your request.
For information about maximum and minimum part sizes and other multipart upload specifications, see\n Multipart upload\n limits in the Amazon S3 User Guide.
\nInstead of copying data from an existing object as part data, you might use the UploadPart action to\n upload new data as a part of an object in your request.
\nYou must initiate a multipart upload before you can upload any part. In response to your initiate\n request, Amazon S3 returns the upload ID, a unique identifier that you must include in your upload part\n request.
\nFor conceptual information about multipart uploads, see Uploading Objects Using Multipart Upload in\n the Amazon S3 User Guide. For information about copying objects using a single atomic\n action vs. a multipart upload, see Operations on Objects in the\n Amazon S3 User Guide.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name\n . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the\n Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the\n Amazon S3 User Guide.
All UploadPartCopy requests must be authenticated and signed by using IAM\n credentials (access key ID and secret access key for the IAM identities). All headers with the\n x-amz- prefix, including x-amz-copy-source, must be signed. For more\n information, see REST Authentication.
\n Directory buckets - You must use IAM credentials to\n authenticate and authorize your access to the UploadPartCopy API operation, instead\n of using the temporary security credentials through the CreateSession API\n operation.
Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.
\nYou must have READ access to the source object and WRITE access to\n the destination bucket.
\n General purpose bucket permissions - You must have the\n permissions in a policy based on the bucket types of your source bucket and destination bucket\n in an UploadPartCopy operation.
If the source object is in a general purpose bucket, you must have the \n s3:GetObject\n permission to read the source object that is\n being copied.
If the destination bucket is a general purpose bucket, you must have the \n s3:PutObject\n permission to write the object copy to\n the destination bucket.
To perform a multipart upload with encryption using an Key Management Service key, the requester\n must have permission to the kms:Decrypt and kms:GenerateDataKey\n actions on the key. The requester must also have permissions for the\n kms:GenerateDataKey action for the CreateMultipartUpload API.\n Then, the requester needs permissions for the kms:Decrypt action on the\n UploadPart and UploadPartCopy APIs. These permissions are\n required because Amazon S3 must decrypt and read data from the encrypted file parts before it\n completes the multipart upload. For more information about KMS permissions, see Protecting\n data using server-side encryption with KMS in the\n Amazon S3 User Guide. For information about the permissions required to\n use the multipart upload API, see Multipart upload and\n permissions and Multipart upload API\n and permissions in the Amazon S3 User Guide.
\n Directory bucket permissions - You must have\n permissions in a bucket policy or an IAM identity-based policy based on the source and destination bucket types\n in an UploadPartCopy operation.
If the source object that you want to copy is in a directory bucket, you must have\n the \n s3express:CreateSession\n permission in\n the Action element of a policy to read the object. By default, the session is\n in the ReadWrite mode. If you want to restrict the access, you can explicitly\n set the s3express:SessionMode condition key to ReadOnly on the\n copy source bucket.
If the copy destination is a directory bucket, you must have the \n s3express:CreateSession\n permission in the\n Action element of a policy to write the object to the destination. The\n s3express:SessionMode condition key cannot be set to ReadOnly\n on the copy destination.
If the object is encrypted with SSE-KMS, you must also have the\n kms:GenerateDataKey and kms:Decrypt permissions in IAM\n identity-based policies and KMS key policies for the KMS key.
For example policies, see Example\n bucket policies for S3 Express One Zone and Amazon Web Services\n Identity and Access Management (IAM) identity-based policies for S3 Express One Zone in the\n Amazon S3 User Guide.
\n\n General purpose buckets -\n For information about using server-side encryption with\n customer-provided encryption keys with the UploadPartCopy operation, see CopyObject and\n UploadPart.
\n Directory buckets -\n For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). For more\n information, see Protecting data with server-side encryption in the Amazon S3 User Guide.
For directory buckets, when you perform a CreateMultipartUpload operation\n and an UploadPartCopy operation, the request headers you provide in the\n CreateMultipartUpload request must match the default encryption configuration\n of the destination bucket.
S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through UploadPartCopy. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.
\nError Code: NoSuchUpload\n
Description: The specified multipart upload does not exist. The upload ID might be\n invalid, or the multipart upload might have been aborted or completed.
\nHTTP Status Code: 404 Not Found
\nError Code: InvalidRequest\n
Description: The specified copy source is not supported as a byte-range copy\n source.
\nHTTP Status Code: 400 Bad Request
\n\n Directory buckets - The HTTP Host header syntax is \n Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following operations are related to UploadPartCopy:
\n UploadPart\n
\n\n AbortMultipartUpload\n
\n\n ListParts\n
\n\n ListMultipartUploads\n
\nThe version of the source object that was copied, if you have enabled versioning on the source\n bucket.
\nThis functionality is not supported when the source object is in a directory bucket.
\nContainer for all response elements.
", "smithy.api#httpPayload": {} } }, "ServerSideEncryption": { "target": "com.amazonaws.s3#ServerSideEncryption", "traits": { "smithy.api#documentation": "The server-side encryption algorithm used when you store this object in Amazon S3 or Amazon FSx.
\nWhen accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side\n encryption option is aws:fsx.
If server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to confirm the encryption algorithm that's used.
\nThis functionality is not supported for directory buckets.
\nIf server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to provide the round-trip message integrity verification of the customer-provided\n encryption key.
\nThis functionality is not supported for directory buckets.
\nIf present, indicates the ID of the KMS key that was used for object encryption.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-aws-kms-key-id" } }, "BucketKeyEnabled": { "target": "com.amazonaws.s3#BucketKeyEnabled", "traits": { "smithy.api#documentation": "Indicates whether the multipart upload uses an S3 Bucket Key for server-side encryption with\n Key Management Service (KMS) keys (SSE-KMS).
", "smithy.api#httpHeader": "x-amz-server-side-encryption-bucket-key-enabled" } }, "RequestCharged": { "target": "com.amazonaws.s3#RequestCharged", "traits": { "smithy.api#httpHeader": "x-amz-request-charged" } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#UploadPartCopyRequest": { "type": "structure", "members": { "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The bucket name.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
Copying objects across different Amazon Web Services Regions isn't supported when the source or destination\n bucket is in Amazon Web Services Local Zones. The source and destination buckets must have the same parent Amazon Web Services Region.\n Otherwise, you get an HTTP 400 Bad Request error with the error code\n InvalidRequest.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Specifies the source object for the copy operation. You specify the value in one of two formats,\n depending on whether you want to access the source object through an access point:
\nFor objects not accessed through an access point, specify the name of the source bucket and key of the\n source object, separated by a slash (/). For example, to copy the object\n reports/january.pdf from the bucket awsexamplebucket, use\n awsexamplebucket/reports/january.pdf. The value must be URL-encoded.
For objects accessed through access points, specify the Amazon Resource Name (ARN) of the object as accessed through the access point, in the format arn:aws:s3:. For example, to copy the object reports/january.pdf through access point my-access-point owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3:us-west-2:123456789012:accesspoint/my-access-point/object/reports/january.pdf. The value must be URL encoded.
Amazon S3 supports copy operations using Access points only when the source and destination buckets are in the same Amazon Web Services Region.
\nAccess points are not supported by directory buckets.
\nAlternatively, for objects accessed through Amazon S3 on Outposts, specify the ARN of the object as accessed in the format arn:aws:s3-outposts:. For example, to copy the object reports/january.pdf through outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/object/reports/january.pdf. The value must be URL-encoded.
If your bucket has versioning enabled, you could have multiple versions of the same object. By\n default, x-amz-copy-source identifies the current version of the source object to copy. To\n copy a specific version of the source object to copy, append ?versionId= to\n the x-amz-copy-source request header (for example, x-amz-copy-source:\n /awsexamplebucket/reports/january.pdf?versionId=QUpfdndhfd8438MNFDN93jdnJFkdmqnh893).
If the current version is a delete marker and you don't specify a versionId in the\n x-amz-copy-source request header, Amazon S3 returns a 404 Not Found error,\n because the object does not exist. If you specify versionId in the x-amz-copy-source and\n the versionId is a delete marker, Amazon S3 returns an HTTP 400 Bad Request error, because you\n are not allowed to specify a delete marker as a version for the x-amz-copy-source.
\n Directory buckets - S3 Versioning isn't enabled and supported for directory buckets.
\nCopies the object if its entity tag (ETag) matches the specified tag.
\nIf both of the x-amz-copy-source-if-match and\n x-amz-copy-source-if-unmodified-since headers are present in the request as\n follows:
\n x-amz-copy-source-if-match condition evaluates to true, and;
\n x-amz-copy-source-if-unmodified-since condition evaluates to false;
Amazon S3 returns 200 OK and copies the data.\n
Copies the object if it has been modified since the specified time.
\nIf both of the x-amz-copy-source-if-none-match and\n x-amz-copy-source-if-modified-since headers are present in the request as follows:
\n x-amz-copy-source-if-none-match condition evaluates to false, and;
\n x-amz-copy-source-if-modified-since condition evaluates to true;
Amazon S3 returns 412 Precondition Failed response code.\n
Copies the object if its entity tag (ETag) is different than the specified ETag.
\nIf both of the x-amz-copy-source-if-none-match and\n x-amz-copy-source-if-modified-since headers are present in the request as follows:
\n x-amz-copy-source-if-none-match condition evaluates to false, and;
\n x-amz-copy-source-if-modified-since condition evaluates to true;
Amazon S3 returns 412 Precondition Failed response code.\n
Copies the object if it hasn't been modified since the specified time.
\nIf both of the x-amz-copy-source-if-match and\n x-amz-copy-source-if-unmodified-since headers are present in the request as\n follows:
\n x-amz-copy-source-if-match condition evaluates to true, and;
\n x-amz-copy-source-if-unmodified-since condition evaluates to false;
Amazon S3 returns 200 OK and copies the data.\n
The range of bytes to copy from the source object. The range value must use the form\n bytes=first-last, where the first and last are the zero-based byte offsets to copy. For example,\n bytes=0-9 indicates that you want to copy the first 10 bytes of the source. You can copy a range only if\n the source object is greater than 5 MB.
", "smithy.api#httpHeader": "x-amz-copy-source-range" } }, "Key": { "target": "com.amazonaws.s3#ObjectKey", "traits": { "smithy.api#documentation": "Object key for which the multipart upload was initiated.
", "smithy.api#httpLabel": {}, "smithy.api#required": {} } }, "PartNumber": { "target": "com.amazonaws.s3#PartNumber", "traits": { "smithy.api#documentation": "Part number of part being copied. This is a positive integer between 1 and 10,000.
", "smithy.api#httpQuery": "partNumber", "smithy.api#required": {} } }, "UploadId": { "target": "com.amazonaws.s3#MultipartUploadId", "traits": { "smithy.api#documentation": "Upload ID identifying the multipart upload whose part is being copied.
", "smithy.api#httpQuery": "uploadId", "smithy.api#required": {} } }, "SSECustomerAlgorithm": { "target": "com.amazonaws.s3#SSECustomerAlgorithm", "traits": { "smithy.api#documentation": "Specifies the algorithm to use when encrypting the object (for example, AES256).
\nThis functionality is not supported when the destination bucket is a directory bucket.
\nSpecifies the customer-provided encryption key for Amazon S3 to use in encrypting data. This value is\n used to store the object and then it is discarded; Amazon S3 does not store the encryption key. The key must\n be appropriate for use with the algorithm specified in the\n x-amz-server-side-encryption-customer-algorithm header. This must be the same encryption\n key specified in the initiate multipart upload request.
This functionality is not supported when the destination bucket is a directory bucket.
\nSpecifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header\n for a message integrity check to ensure that the encryption key was transmitted without error.
\nThis functionality is not supported when the destination bucket is a directory bucket.
\nSpecifies the algorithm to use when decrypting the source object (for example,\n AES256).
This functionality is not supported when the source object is in a directory bucket.
\nSpecifies the customer-provided encryption key for Amazon S3 to use to decrypt the source object. The\n encryption key provided in this header must be one that was used when the source object was\n created.
\nThis functionality is not supported when the source object is in a directory bucket.
\nSpecifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header\n for a message integrity check to ensure that the encryption key was transmitted without error.
\nThis functionality is not supported when the source object is in a directory bucket.
\nThe account ID of the expected destination bucket owner. If the account ID that you provide does not match the actual owner of the destination bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The account ID of the expected source bucket owner. If the account ID that you provide does not match the actual owner of the source bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The server-side encryption algorithm used when you store this object in Amazon S3 or Amazon FSx.
\nWhen accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side\n encryption option is aws:fsx.
Entity tag for the uploaded object.
", "smithy.api#httpHeader": "ETag" } }, "ChecksumCRC32": { "target": "com.amazonaws.s3#ChecksumCRC32", "traits": { "smithy.api#documentation": "The Base64 encoded, 32-bit CRC32 checksum of the object. This checksum is only be present if the checksum was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the object. This checksum is only present if the checksum was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This header specifies the Base64 encoded, 64-bit CRC64NVME\n checksum of the part. For more information, see Checking object integrity in\n the Amazon S3 User Guide.
The Base64 encoded, 160-bit SHA1 digest of the object. This will only be present if the object was uploaded\n with the object. When you use the API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 digest of the object. This will only be present if the object was uploaded\n with the object. When you use an API operation on an object that was uploaded using multipart uploads, this value may not be a direct checksum value of the full object. Instead, it's a calculation based on the checksum values of each individual part. For more information about how checksums are calculated\n with multipart uploads, see \n Checking object integrity in the Amazon S3 User Guide.
If server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to confirm the encryption algorithm that's used.
\nThis functionality is not supported for directory buckets.
\nIf server-side encryption with a customer-provided encryption key was requested, the response will\n include this header to provide the round-trip message integrity verification of the customer-provided\n encryption key.
\nThis functionality is not supported for directory buckets.
\nIf present, indicates the ID of the KMS key that was used for object encryption.
", "smithy.api#httpHeader": "x-amz-server-side-encryption-aws-kms-key-id" } }, "BucketKeyEnabled": { "target": "com.amazonaws.s3#BucketKeyEnabled", "traits": { "smithy.api#documentation": "Indicates whether the multipart upload uses an S3 Bucket Key for server-side encryption with\n Key Management Service (KMS) keys (SSE-KMS).
", "smithy.api#httpHeader": "x-amz-server-side-encryption-bucket-key-enabled" } }, "RequestCharged": { "target": "com.amazonaws.s3#RequestCharged", "traits": { "smithy.api#httpHeader": "x-amz-request-charged" } } }, "traits": { "smithy.api#output": {} } }, "com.amazonaws.s3#UploadPartRequest": { "type": "structure", "members": { "Body": { "target": "com.amazonaws.s3#StreamingBlob", "traits": { "smithy.api#default": "", "smithy.api#documentation": "Object data.
", "smithy.api#httpPayload": {} } }, "Bucket": { "target": "com.amazonaws.s3#BucketName", "traits": { "smithy.api#documentation": "The name of the bucket to which the multipart upload was initiated.
\n\n Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format \n Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format \n bucket-base-name--zone-id--x-s3 (for example, \n amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming\n restrictions, see Directory bucket naming\n rules in the Amazon S3 User Guide.
\n Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see Using access points in the Amazon S3 User Guide.
\nObject Lambda access points are not supported by directory buckets.
\n\n S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the \n form \n AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
Size of the body in bytes. This parameter is useful when the size of the body cannot be determined\n automatically.
", "smithy.api#httpHeader": "Content-Length" } }, "ContentMD5": { "target": "com.amazonaws.s3#ContentMD5", "traits": { "smithy.api#documentation": "The Base64 encoded 128-bit MD5 digest of the part data. This parameter is auto-populated when using\n the command from the CLI. This parameter is required if object lock parameters are specified.
\nThis functionality is not supported for directory buckets.
\nIndicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any\n additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or\n x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more\n information, see Checking object integrity in\n the Amazon S3 User Guide.
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm\n parameter.
This checksum algorithm must be the same for all parts and it match the checksum value supplied in\n the CreateMultipartUpload request.
This header can be used as a data integrity check to verify that the data received is the same data that was originally sent.\n This header specifies the Base64 encoded, 32-bit CRC32 checksum of the object. For more information, see\n Checking object integrity in the\n Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data that was originally sent.\n This header specifies the Base64 encoded, 32-bit CRC32C checksum of the object. For more information, see\n Checking object integrity in the\n Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This header specifies the Base64 encoded, 64-bit CRC64NVME\n checksum of the part. For more information, see Checking object integrity in\n the Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data that was originally sent.\n This header specifies the Base64 encoded, 160-bit SHA1 digest of the object. For more information, see\n Checking object integrity in the\n Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data that was originally sent.\n This header specifies the Base64 encoded, 256-bit SHA256 digest of the object. For more information, see\n Checking object integrity in the\n Amazon S3 User Guide.
Object key for which the multipart upload was initiated.
", "smithy.api#httpLabel": {}, "smithy.api#required": {}, "smithy.rules#contextParam": { "name": "Key" } } }, "PartNumber": { "target": "com.amazonaws.s3#PartNumber", "traits": { "smithy.api#documentation": "Part number of part being uploaded. This is a positive integer between 1 and 10,000.
", "smithy.api#httpQuery": "partNumber", "smithy.api#required": {} } }, "UploadId": { "target": "com.amazonaws.s3#MultipartUploadId", "traits": { "smithy.api#documentation": "Upload ID identifying the multipart upload whose part is being uploaded.
", "smithy.api#httpQuery": "uploadId", "smithy.api#required": {} } }, "SSECustomerAlgorithm": { "target": "com.amazonaws.s3#SSECustomerAlgorithm", "traits": { "smithy.api#documentation": "Specifies the algorithm to use when encrypting the object (for example, AES256).
\nThis functionality is not supported for directory buckets.
\nSpecifies the customer-provided encryption key for Amazon S3 to use in encrypting data. This value is\n used to store the object and then it is discarded; Amazon S3 does not store the encryption key. The key must\n be appropriate for use with the algorithm specified in the\n x-amz-server-side-encryption-customer-algorithm header. This must be the same encryption\n key specified in the initiate multipart upload request.
This functionality is not supported for directory buckets.
\nSpecifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header\n for a message integrity check to ensure that the encryption key was transmitted without error.
\nThis functionality is not supported for directory buckets.
\nThe account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Specifies whether MFA delete is enabled in the bucket versioning configuration. This element is only\n returned if the bucket has been configured with MFA delete. If the bucket has never been so configured,\n this element is not returned.
", "smithy.api#xmlName": "MfaDelete" } }, "Status": { "target": "com.amazonaws.s3#BucketVersioningStatus", "traits": { "smithy.api#documentation": "The versioning state of the bucket.
" } } }, "traits": { "smithy.api#documentation": "Describes the versioning state of an Amazon S3 bucket. For more information, see PUT Bucket\n versioning in the Amazon S3 API Reference.
" } }, "com.amazonaws.s3#WebsiteConfiguration": { "type": "structure", "members": { "ErrorDocument": { "target": "com.amazonaws.s3#ErrorDocument", "traits": { "smithy.api#documentation": "The name of the error document for the website.
" } }, "IndexDocument": { "target": "com.amazonaws.s3#IndexDocument", "traits": { "smithy.api#documentation": "The name of the index document for the website.
" } }, "RedirectAllRequestsTo": { "target": "com.amazonaws.s3#RedirectAllRequestsTo", "traits": { "smithy.api#documentation": "The redirect behavior for every request to this bucket's website endpoint.
\nIf you specify this property, you can't specify any other property.
\nRules that define when a redirect is applied and the redirect behavior.
" } } }, "traits": { "smithy.api#documentation": "Specifies website configuration parameters for an Amazon S3 bucket.
" } }, "com.amazonaws.s3#WebsiteRedirectLocation": { "type": "string" }, "com.amazonaws.s3#WriteGetObjectResponse": { "type": "operation", "input": { "target": "com.amazonaws.s3#WriteGetObjectResponseRequest" }, "output": { "target": "smithy.api#Unit" }, "traits": { "aws.auth#unsignedPayload": {}, "smithy.api#auth": [ "aws.auth#sigv4" ], "smithy.api#documentation": "This operation is not supported for directory buckets.
\nPasses transformed objects to a GetObject operation when using Object Lambda access points. For information\n about Object Lambda access points, see Transforming objects with Object Lambda access points in the Amazon S3 User Guide.
This operation supports metadata that can be returned by GetObject, in addition to\n RequestRoute, RequestToken, StatusCode, ErrorCode,\n and ErrorMessage. The GetObject response metadata is supported so that the\n WriteGetObjectResponse caller, typically an Lambda function, can provide the same\n metadata when it internally invokes GetObject. When WriteGetObjectResponse is\n called by a customer-owned Lambda function, the metadata returned to the end user GetObject\n call might differ from what Amazon S3 would normally return.
You can include any number of metadata headers. When including a metadata header, it should be\n prefaced with x-amz-meta. For example, x-amz-meta-my-custom-header:\n MyCustomValue. The primary use case for this is to forward GetObject\n metadata.
Amazon Web Services provides some prebuilt Lambda functions that you can use with S3 Object Lambda to detect and\n redact personally identifiable information (PII) and decompress S3 objects. These Lambda functions are\n available in the Amazon Web Services Serverless Application Repository, and can be selected through the Amazon Web Services\n Management Console when you create your Object Lambda access point.
\nExample 1: PII Access Control - This Lambda function uses Amazon Comprehend, a natural\n language processing (NLP) service using machine learning to find insights and relationships in text. It\n automatically detects personally identifiable information (PII) such as names, addresses, dates, credit\n card numbers, and social security numbers from documents in your Amazon S3 bucket.
\nExample 2: PII Redaction - This Lambda function uses Amazon Comprehend, a natural language\n processing (NLP) service using machine learning to find insights and relationships in text. It\n automatically redacts personally identifiable information (PII) such as names, addresses, dates, credit\n card numbers, and social security numbers from documents in your Amazon S3 bucket.
\nExample 3: Decompression - The Lambda function S3ObjectLambdaDecompression, is equipped to\n decompress objects stored in S3 in one of six compressed file formats including bzip2, gzip, snappy,\n zlib, zstandard and ZIP.
\nFor information on how to view and use these functions, see Using Amazon Web Services built Lambda functions in the\n Amazon S3 User Guide.
", "smithy.api#endpoint": { "hostPrefix": "{RequestRoute}." }, "smithy.api#http": { "method": "POST", "uri": "/WriteGetObjectResponse", "code": 200 }, "smithy.rules#staticContextParams": { "UseObjectLambdaEndpoint": { "value": true } } } }, "com.amazonaws.s3#WriteGetObjectResponseRequest": { "type": "structure", "members": { "RequestRoute": { "target": "com.amazonaws.s3#RequestRoute", "traits": { "smithy.api#documentation": "Route prefix to the HTTP URL generated.
", "smithy.api#hostLabel": {}, "smithy.api#httpHeader": "x-amz-request-route", "smithy.api#required": {} } }, "RequestToken": { "target": "com.amazonaws.s3#RequestToken", "traits": { "smithy.api#documentation": "A single use encrypted token that maps WriteGetObjectResponse to the end user\n GetObject request.
The object data.
", "smithy.api#httpPayload": {} } }, "StatusCode": { "target": "com.amazonaws.s3#GetObjectResponseStatusCode", "traits": { "smithy.api#documentation": "The integer status code for an HTTP response of a corresponding GetObject request. The\n following is a list of status codes.
\n 200 - OK\n
\n 206 - Partial Content\n
\n 304 - Not Modified\n
\n 400 - Bad Request\n
\n 401 - Unauthorized\n
\n 403 - Forbidden\n
\n 404 - Not Found\n
\n 405 - Method Not Allowed\n
\n 409 - Conflict\n
\n 411 - Length Required\n
\n 412 - Precondition Failed\n
\n 416 - Range Not Satisfiable\n
\n 500 - Internal Server Error\n
\n 503 - Service Unavailable\n
A string that uniquely identifies an error condition. Returned in the tag of the error\n XML response for a corresponding GetObject call. Cannot be used with a successful\n StatusCode header or when the transformed object is provided in the body. All error codes\n from S3 are sentence-cased. The regular expression (regex) value is\n \"^[A-Z][a-zA-Z]+$\".
Contains a generic description of the error condition. Returned in the GetObject call. Cannot be used with a successful\n StatusCode header or when the transformed object is provided in body.
Indicates that a range of bytes was specified.
", "smithy.api#httpHeader": "x-amz-fwd-header-accept-ranges" } }, "CacheControl": { "target": "com.amazonaws.s3#CacheControl", "traits": { "smithy.api#documentation": "Specifies caching behavior along the request/reply chain.
", "smithy.api#httpHeader": "x-amz-fwd-header-Cache-Control" } }, "ContentDisposition": { "target": "com.amazonaws.s3#ContentDisposition", "traits": { "smithy.api#documentation": "Specifies presentational information for the object.
", "smithy.api#httpHeader": "x-amz-fwd-header-Content-Disposition" } }, "ContentEncoding": { "target": "com.amazonaws.s3#ContentEncoding", "traits": { "smithy.api#documentation": "Specifies what content encodings have been applied to the object and thus what decoding mechanisms\n must be applied to obtain the media-type referenced by the Content-Type header field.
", "smithy.api#httpHeader": "x-amz-fwd-header-Content-Encoding" } }, "ContentLanguage": { "target": "com.amazonaws.s3#ContentLanguage", "traits": { "smithy.api#documentation": "The language the content is in.
", "smithy.api#httpHeader": "x-amz-fwd-header-Content-Language" } }, "ContentLength": { "target": "com.amazonaws.s3#ContentLength", "traits": { "smithy.api#documentation": "The size of the content body in bytes.
", "smithy.api#httpHeader": "Content-Length" } }, "ContentRange": { "target": "com.amazonaws.s3#ContentRange", "traits": { "smithy.api#documentation": "The portion of the object returned in the response.
", "smithy.api#httpHeader": "x-amz-fwd-header-Content-Range" } }, "ContentType": { "target": "com.amazonaws.s3#ContentType", "traits": { "smithy.api#documentation": "A standard MIME type describing the format of the object data.
", "smithy.api#httpHeader": "x-amz-fwd-header-Content-Type" } }, "ChecksumCRC32": { "target": "com.amazonaws.s3#ChecksumCRC32", "traits": { "smithy.api#documentation": "This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This specifies the Base64 encoded, 32-bit CRC32 checksum of the\n object returned by the Object Lambda function. This may not match the checksum for the object stored in\n Amazon S3. Amazon S3 will perform validation of the checksum values only when the original GetObject\n request required checksum validation. For more information about checksums, see Checking object\n integrity in the Amazon S3 User Guide.
Only one checksum header can be specified at a time. If you supply multiple checksum headers, this\n request will fail.
\n ", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-checksum-crc32" } }, "ChecksumCRC32C": { "target": "com.amazonaws.s3#ChecksumCRC32C", "traits": { "smithy.api#documentation": "This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This specifies the Base64 encoded, 32-bit CRC32C checksum of the\n object returned by the Object Lambda function. This may not match the checksum for the object stored in\n Amazon S3. Amazon S3 will perform validation of the checksum values only when the original GetObject\n request required checksum validation. For more information about checksums, see Checking object\n integrity in the Amazon S3 User Guide.
Only one checksum header can be specified at a time. If you supply multiple checksum headers, this\n request will fail.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-checksum-crc32c" } }, "ChecksumCRC64NVME": { "target": "com.amazonaws.s3#ChecksumCRC64NVME", "traits": { "smithy.api#documentation": "This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This header specifies the Base64 encoded, 64-bit CRC64NVME\n checksum of the part. For more information, see Checking object integrity in\n the Amazon S3 User Guide.
This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This specifies the Base64 encoded, 160-bit SHA1 digest of the\n object returned by the Object Lambda function. This may not match the checksum for the object stored in\n Amazon S3. Amazon S3 will perform validation of the checksum values only when the original GetObject\n request required checksum validation. For more information about checksums, see Checking object\n integrity in the Amazon S3 User Guide.
Only one checksum header can be specified at a time. If you supply multiple checksum headers, this\n request will fail.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-checksum-sha1" } }, "ChecksumSHA256": { "target": "com.amazonaws.s3#ChecksumSHA256", "traits": { "smithy.api#documentation": "This header can be used as a data integrity check to verify that the data received is the same data\n that was originally sent. This specifies the Base64 encoded, 256-bit SHA256 digest of the\n object returned by the Object Lambda function. This may not match the checksum for the object stored in\n Amazon S3. Amazon S3 will perform validation of the checksum values only when the original GetObject\n request required checksum validation. For more information about checksums, see Checking object\n integrity in the Amazon S3 User Guide.
Only one checksum header can be specified at a time. If you supply multiple checksum headers, this\n request will fail.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-checksum-sha256" } }, "DeleteMarker": { "target": "com.amazonaws.s3#DeleteMarker", "traits": { "smithy.api#documentation": "Specifies whether an object stored in Amazon S3 is (true) or is not (false) a\n delete marker. To learn more about delete markers, see Working with delete markers.
An opaque identifier assigned by a web server to a specific version of a resource found at a URL.\n
", "smithy.api#httpHeader": "x-amz-fwd-header-ETag" } }, "Expires": { "target": "com.amazonaws.s3#Expires", "traits": { "smithy.api#documentation": "The date and time at which the object is no longer cacheable.
", "smithy.api#httpHeader": "x-amz-fwd-header-Expires" } }, "Expiration": { "target": "com.amazonaws.s3#Expiration", "traits": { "smithy.api#documentation": "If the object expiration is configured (see PUT Bucket lifecycle), the response includes this\n header. It includes the expiry-date and rule-id key-value pairs that provide\n the object expiration information. The value of the rule-id is URL-encoded.
The date and time that the object was last modified.
", "smithy.api#httpHeader": "x-amz-fwd-header-Last-Modified" } }, "MissingMeta": { "target": "com.amazonaws.s3#MissingMeta", "traits": { "smithy.api#documentation": "Set to the number of metadata entries not returned in x-amz-meta headers. This can\n happen if you create metadata using an API like SOAP that supports more flexible metadata than the REST\n API. For example, using SOAP, you can create metadata whose values are not legal HTTP headers.
A map of metadata to store with the object in S3.
", "smithy.api#httpPrefixHeaders": "x-amz-meta-" } }, "ObjectLockMode": { "target": "com.amazonaws.s3#ObjectLockMode", "traits": { "smithy.api#documentation": "Indicates whether an object stored in Amazon S3 has Object Lock enabled. For more information about S3\n Object Lock, see Object\n Lock.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-object-lock-mode" } }, "ObjectLockLegalHoldStatus": { "target": "com.amazonaws.s3#ObjectLockLegalHoldStatus", "traits": { "smithy.api#documentation": "Indicates whether an object stored in Amazon S3 has an active legal hold.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-object-lock-legal-hold" } }, "ObjectLockRetainUntilDate": { "target": "com.amazonaws.s3#ObjectLockRetainUntilDate", "traits": { "smithy.api#documentation": "The date and time when Object Lock is configured to expire.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-object-lock-retain-until-date" } }, "PartsCount": { "target": "com.amazonaws.s3#PartsCount", "traits": { "smithy.api#documentation": "The count of parts this object has.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-mp-parts-count" } }, "ReplicationStatus": { "target": "com.amazonaws.s3#ReplicationStatus", "traits": { "smithy.api#documentation": "Indicates if request involves bucket that is either a source or destination in a Replication rule.\n For more information about S3 Replication, see Replication.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-replication-status" } }, "RequestCharged": { "target": "com.amazonaws.s3#RequestCharged", "traits": { "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-request-charged" } }, "Restore": { "target": "com.amazonaws.s3#Restore", "traits": { "smithy.api#documentation": "Provides information about object restoration operation and expiration time of the restored object\n copy.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-restore" } }, "ServerSideEncryption": { "target": "com.amazonaws.s3#ServerSideEncryption", "traits": { "smithy.api#documentation": "The server-side encryption algorithm used when storing requested object in Amazon S3 or Amazon FSx.
\nWhen accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side\n encryption option is aws:fsx.
Encryption algorithm used if server-side encryption with a customer-provided encryption key was\n specified for object stored in Amazon S3.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-server-side-encryption-customer-algorithm" } }, "SSEKMSKeyId": { "target": "com.amazonaws.s3#SSEKMSKeyId", "traits": { "smithy.api#documentation": "If present, specifies the ID (Key ID, Key ARN, or Key Alias) of the Amazon Web Services Key Management Service\n (Amazon Web Services KMS) symmetric encryption customer managed key that was used for stored in Amazon S3 object.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-server-side-encryption-aws-kms-key-id" } }, "SSECustomerKeyMD5": { "target": "com.amazonaws.s3#SSECustomerKeyMD5", "traits": { "smithy.api#documentation": "128-bit MD5 digest of customer-provided encryption key used in Amazon S3 to encrypt data stored in S3.\n For more information, see Protecting data using\n server-side encryption with customer-provided encryption keys (SSE-C).
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-server-side-encryption-customer-key-MD5" } }, "StorageClass": { "target": "com.amazonaws.s3#StorageClass", "traits": { "smithy.api#documentation": "Provides storage class information of the object. Amazon S3 returns this header for all objects except\n for S3 Standard storage class objects.
\nFor more information, see Storage Classes.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-storage-class" } }, "TagCount": { "target": "com.amazonaws.s3#TagCount", "traits": { "smithy.api#documentation": "The number of tags, if any, on the object.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-tagging-count" } }, "VersionId": { "target": "com.amazonaws.s3#ObjectVersionId", "traits": { "smithy.api#documentation": "An ID used to reference a specific version of the object.
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-version-id" } }, "BucketKeyEnabled": { "target": "com.amazonaws.s3#BucketKeyEnabled", "traits": { "smithy.api#documentation": "Indicates whether the object stored in Amazon S3 uses an S3 bucket key for server-side encryption with\n Amazon Web Services KMS (SSE-KMS).
", "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-server-side-encryption-bucket-key-enabled" } } }, "traits": { "smithy.api#input": {} } }, "com.amazonaws.s3#WriteOffsetBytes": { "type": "long" }, "com.amazonaws.s3#Years": { "type": "integer" } } }