Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Abort
Incomplete Multipart Upload Specifies the days since the initiation of an incomplete multipart upload that Amazon S3 will wait before permanently removing all parts of the upload. For more information, see Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration in the Amazon S3 User Guide.
- Accelerate
Configuration Configures the transfer acceleration state for an Amazon S3 bucket. For more information, see Amazon S3 Transfer Acceleration in the Amazon S3 User Guide.
- Access
Control Policy Contains the elements that set the ACL permissions for an object per grantee.
- Access
Control Translation A container for information about access control for replicas.
- Analytics
AndOperator A conjunction (logical AND) of predicates, which is used in evaluating a metrics filter. The operator must have at least two predicates in any combination, and an object must match all of the predicates for the filter to apply.
- Analytics
Configuration Specifies the configuration and any analyses for the analytics filter of an Amazon S3 bucket.
- Analytics
Export Destination Where to publish the analytics results.
- Analytics
S3Bucket Destination Contains information about where to publish the analytics results.
- Bucket
In terms of implementation, a Bucket is a resource.
- Bucket
Info Specifies the information about the bucket that will be created. For more information about directory buckets, see Directory buckets in the Amazon S3 User Guide.
This functionality is only supported by directory buckets.
- Bucket
Lifecycle Configuration Specifies the lifecycle configuration for objects in an Amazon S3 bucket. For more information, see Object Lifecycle Management in the Amazon S3 User Guide.
- Bucket
Logging Status Container for logging status information.
- Checksum
Contains all the possible checksum or digest values for an object.
- Common
Prefix Container for all (if there are any) keys between Prefix and the next occurrence of the string specified by a delimiter. CommonPrefixes lists keys that act like subdirectories in the directory specified by Prefix. For example, if the prefix is notes/ and the delimiter is a slash (/) as in notes/summer/july, the common prefix is notes/summer/.
- Completed
Multipart Upload The container for the completed multipart upload details.
- Completed
Part Details of the parts that were uploaded.
- Condition
A container for describing a condition that must be met for the specified redirect to apply. For example, 1. If request is for pages in the
/docs
folder, redirect to the/documents
folder. 2. If request results in HTTP error 4xx, redirect request to another host where you might process the error.- Continuation
Event - Copy
Object Result Container for all response elements.
- Copy
Part Result Container for all response elements.
- Cors
Configuration Describes the cross-origin access configuration for objects in an Amazon S3 bucket. For more information, see Enabling Cross-Origin Resource Sharing in the Amazon S3 User Guide.
- Cors
Rule Specifies a cross-origin access rule for an Amazon S3 bucket.
- Create
Bucket Configuration The configuration information for the bucket.
- CsvInput
Describes how an uncompressed comma-separated values (CSV)-formatted input object is formatted.
- CsvOutput
Describes how uncompressed comma-separated values (CSV)-formatted results are formatted.
- Default
Retention The container element for optionally specifying the default Object Lock retention settings for new objects placed in the specified bucket.
-
The
DefaultRetention
settings require both a mode and a period. -
The
DefaultRetention
period can be eitherDays
orYears
but you must select one. You cannot specifyDays
andYears
at the same time.
-
- Delete
Container for the objects to delete.
- Delete
Marker Entry Information about the delete marker.
- Delete
Marker Replication Specifies whether Amazon S3 replicates delete markers. If you specify a
Filter
in your replication configuration, you must also include aDeleteMarkerReplication
element. If yourFilter
includes aTag
element, theDeleteMarkerReplication
Status
must be set to Disabled, because Amazon S3 does not support replicating delete markers for tag-based rules. For an example configuration, see Basic Rule Configuration.For more information about delete marker replication, see Basic Rule Configuration.
If you are using an earlier version of the replication configuration, Amazon S3 handles replication of delete markers differently. For more information, see Backward Compatibility.
- Deleted
Object Information about the deleted object.
- Destination
Specifies information about where to publish analysis or configuration results for an Amazon S3 bucket and S3 Replication Time Control (S3 RTC).
- Encryption
Contains the type of server-side encryption used.
- Encryption
Configuration Specifies encryption-related information for an Amazon S3 bucket that is a destination for replicated objects.
If you're specifying a customer managed KMS key, we recommend using a fully qualified KMS key ARN. If you use a KMS key alias instead, then KMS resolves the key within the requester’s account. This behavior can result in data that's encrypted with a KMS key that belongs to the requester, and not the bucket owner.
- EndEvent
A message that indicates the request is complete and no more messages will be sent. You should not assume that the request is complete until the client receives an
EndEvent
.- Error
Container for all error elements.
- Error
Details If the
CreateBucketMetadataTableConfiguration
request succeeds, but S3 Metadata was unable to create the table, this structure contains the error code and error message.- Error
Document The error information.
- Event
Bridge Configuration A container for specifying the configuration for Amazon EventBridge.
- Existing
Object Replication Optional configuration to replicate existing source bucket objects.
This parameter is no longer supported. To replicate existing objects, see Replicating existing objects with S3 Batch Replication in the Amazon S3 User Guide.
- Filter
Rule Specifies the Amazon S3 object key name to filter on. An object key name is the name assigned to an object in your Amazon S3 bucket. You specify whether to filter on the suffix or prefix of the object key name. A prefix is a specific string of characters at the beginning of an object key name, which you can use to organize objects. For example, you can start the key names of related objects with a prefix, such as
2023-
orengineering/
. Then, you can useFilterRule
to find objects in a bucket with key names that have the same prefix. A suffix is similar to a prefix, but it is at the end of the object key name instead of at the beginning.- GetBucket
Metadata Table Configuration Result The metadata table configuration for a general purpose bucket.
- GetObject
Attributes Parts A collection of parts associated with a multipart upload.
- Glacier
JobParameters Container for S3 Glacier job parameters.
- Grant
Container for grant information.
- Grantee
Container for the person being granted permissions.
- Index
Document Container for the
Suffix
element.- Initiator
Container element that identifies who initiated the multipart upload.
- Input
Serialization Describes the serialization format of the object.
- Intelligent
Tiering AndOperator A container for specifying S3 Intelligent-Tiering filters. The filters determine the subset of objects to which the rule applies.
- Intelligent
Tiering Configuration Specifies the S3 Intelligent-Tiering configuration for an Amazon S3 bucket.
For information about the S3 Intelligent-Tiering storage class, see Storage class for automatically optimizing frequently and infrequently accessed objects.
- Intelligent
Tiering Filter The
Filter
is used to identify objects that the S3 Intelligent-Tiering configuration applies to.- Inventory
Configuration Specifies the inventory configuration for an Amazon S3 bucket. For more information, see GET Bucket inventory in the Amazon S3 API Reference.
- Inventory
Destination Specifies the inventory configuration for an Amazon S3 bucket.
- Inventory
Encryption Contains the type of server-side encryption used to encrypt the inventory results.
- Inventory
Filter Specifies an inventory filter. The inventory only includes objects that meet the filter's criteria.
- Inventory
S3Bucket Destination Contains the bucket name, file format, bucket owner (optional), and prefix (optional) where inventory results are published.
- Inventory
Schedule Specifies the schedule for generating inventory results.
- Json
Input Specifies JSON as object's input serialization format.
- Json
Output Specifies JSON as request's output serialization format.
- Lambda
Function Configuration A container for specifying the configuration for Lambda notifications.
- Lifecycle
Expiration Container for the expiration for the lifecycle of the object.
For more information see, Managing your storage lifecycle in the Amazon S3 User Guide.
- Lifecycle
Rule A lifecycle rule for individual objects in an Amazon S3 bucket.
For more information see, Managing your storage lifecycle in the Amazon S3 User Guide.
- Lifecycle
Rule AndOperator This is used in a Lifecycle Rule Filter to apply a logical AND to two or more predicates. The Lifecycle Rule will apply to any object matching all of the predicates configured inside the And operator.
- Lifecycle
Rule Filter The
Filter
is used to identify objects that a Lifecycle Rule applies to. AFilter
can have exactly one ofPrefix
,Tag
,ObjectSizeGreaterThan
,ObjectSizeLessThan
, orAnd
specified. If theFilter
element is left empty, the Lifecycle Rule applies to all objects in the bucket.- Location
Info Specifies the location where the bucket will be created.
For directory buckets, the location type is Availability Zone or Local Zone. For more information about directory buckets, see Working with directory buckets in the Amazon S3 User Guide.
This functionality is only supported by directory buckets.
- Logging
Enabled Describes where logs are stored and the prefix that Amazon S3 assigns to all log object keys for a bucket. For more information, see PUT Bucket logging in the Amazon S3 API Reference.
- Metadata
Entry A metadata key-value pair to store with an object.
- Metadata
Table Configuration The metadata table configuration for a general purpose bucket.
- Metadata
Table Configuration Result The metadata table configuration for a general purpose bucket. The destination table bucket must be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata table name must be unique within the
aws_s3_metadata
namespace in the destination table bucket.- Metrics
A container specifying replication metrics-related settings enabling replication metrics and events.
- Metrics
AndOperator A conjunction (logical AND) of predicates, which is used in evaluating a metrics filter. The operator must have at least two predicates, and an object must match all of the predicates in order for the filter to apply.
- Metrics
Configuration Specifies a metrics configuration for the CloudWatch request metrics (specified by the metrics configuration ID) from an Amazon S3 bucket. If you're updating an existing metrics configuration, note that this is a full replacement of the existing metrics configuration. If you don't include the elements you want to keep, they are erased. For more information, see PutBucketMetricsConfiguration.
- Multipart
Upload Container for the
MultipartUpload
for the Amazon S3 object.- Noncurrent
Version Expiration Specifies when noncurrent object versions expire. Upon expiration, Amazon S3 permanently deletes the noncurrent object versions. You set this lifecycle configuration action on a bucket that has versioning enabled (or suspended) to request that Amazon S3 delete noncurrent object versions at a specific period in the object's lifetime.
This parameter applies to general purpose buckets only. It is not supported for directory bucket lifecycle configurations.
- Noncurrent
Version Transition Container for the transition rule that describes when noncurrent objects transition to the
STANDARD_IA
,ONEZONE_IA
,INTELLIGENT_TIERING
,GLACIER_IR
,GLACIER
, orDEEP_ARCHIVE
storage class. If your bucket is versioning-enabled (or versioning is suspended), you can set this action to request that Amazon S3 transition noncurrent object versions to theSTANDARD_IA
,ONEZONE_IA
,INTELLIGENT_TIERING
,GLACIER_IR
,GLACIER
, orDEEP_ARCHIVE
storage class at a specific period in the object's lifetime.- Notification
Configuration A container for specifying the notification configuration of the bucket. If this element is empty, notifications are turned off for the bucket.
- Notification
Configuration Filter Specifies object key name filtering rules. For information about key name filtering, see Configuring event notifications using object key name filtering in the Amazon S3 User Guide.
- Object
An object consists of data and its descriptive metadata.
- Object
Identifier Object Identifier is unique value to identify objects.
- Object
Lock Configuration The container element for Object Lock configuration parameters.
- Object
Lock Legal Hold A legal hold configuration for an object.
- Object
Lock Retention A Retention configuration for an object.
- Object
Lock Rule The container element for an Object Lock rule.
- Object
Part A container for elements related to an individual part.
- Object
Version The version of an object.
- Output
Location Describes the location where the restore job's output is stored.
- Output
Serialization Describes how results of the Select job are serialized.
- Owner
Container for the owner's display name and ID.
- Ownership
Controls The container element for a bucket's ownership controls.
- Ownership
Controls Rule The container element for an ownership control rule.
- Parquet
Input Container for Parquet.
- Part
Container for elements related to a part.
- Partitioned
Prefix Amazon S3 keys for log objects are partitioned in the following format:
\[DestinationPrefix\]\[SourceAccountId\]/\[SourceRegion\]/\[SourceBucket\]/\[YYYY\]/\[MM\]/\[DD\]/\[YYYY\]-\[MM\]-\[DD\]-\[hh\]-\[mm\]-\[ss\]-\[UniqueString\]
PartitionedPrefix defaults to EventTime delivery when server access logs are delivered.
- Policy
Status The container element for a bucket's policy status.
- Progress
This data type contains information about progress of an operation.
- Progress
Event This data type contains information about the progress event of an operation.
- Public
Access Block Configuration The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can enable the configuration options in any combination. For more information about when Amazon S3 considers a bucket or object public, see The Meaning of "Public" in the Amazon S3 User Guide.
- Queue
Configuration Specifies the configuration for publishing messages to an Amazon Simple Queue Service (Amazon SQS) queue when Amazon S3 detects specified events.
- Records
Event The container for the records event.
- Redirect
Specifies how requests are redirected. In the event of an error, you can specify a different error code to return.
- Redirect
AllRequests To Specifies the redirect behavior of all requests to a website endpoint of an Amazon S3 bucket.
- Replica
Modifications A filter that you can specify for selection for modifications on replicas. Amazon S3 doesn't replicate replica modifications by default. In the latest version of replication configuration (when
Filter
is specified), you can specify this element and set the status toEnabled
to replicate modifications on replicas.If you don't specify the
Filter
element, Amazon S3 assumes that the replication configuration is the earlier version, V1. In the earlier version, this element is not allowed.- Replication
Configuration A container for replication rules. You can add up to 1,000 rules. The maximum size of a replication configuration is 2 MB.
- Replication
Rule Specifies which Amazon S3 objects to replicate and where to store the replicas.
- Replication
Rule AndOperator A container for specifying rule filters. The filters determine the subset of objects to which the rule applies. This element is required only if you specify more than one filter.
For example:
-
If you specify both a
Prefix
and aTag
filter, wrap these filters in anAnd
tag. -
If you specify a filter based on multiple tags, wrap the
Tag
elements in anAnd
tag.
-
- Replication
Rule Filter A filter that identifies the subset of objects to which the replication rule applies. A
Filter
must specify exactly onePrefix
,Tag
, or anAnd
child element.- Replication
Time A container specifying S3 Replication Time Control (S3 RTC) related information, including whether S3 RTC is enabled and the time when all objects and operations on objects must be replicated. Must be specified together with a
Metrics
block.- Replication
Time Value A container specifying the time value for S3 Replication Time Control (S3 RTC) and replication metrics
EventThreshold
.- Request
Payment Configuration Container for Payer.
- Request
Progress Container for specifying if periodic
QueryProgress
messages should be sent.- Restore
Request Container for restore job parameters.
- Restore
Status Specifies the restoration status of an object. Objects in certain storage classes must be restored before they can be retrieved. For more information about these storage classes and how to work with archived objects, see Working with archived objects in the Amazon S3 User Guide.
This functionality is not supported for directory buckets. Only the S3 Express One Zone storage class is supported by directory buckets to store objects.
- Routing
Rule Specifies the redirect behavior and when a redirect is applied. For more information about routing rules, see Configuring advanced conditional redirects in the Amazon S3 User Guide.
- S3Key
Filter A container for object key name prefix and suffix filtering rules.
- S3Location
Describes an Amazon S3 location that will receive the results of the restore request.
- S3Tables
Destination The destination information for the metadata table configuration. The destination table bucket must be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata table name must be unique within the
aws_s3_metadata
namespace in the destination table bucket.- S3Tables
Destination Result The destination information for the metadata table configuration. The destination table bucket must be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata table name must be unique within the
aws_s3_metadata
namespace in the destination table bucket.- Scan
Range Specifies the byte range of the object to get the records from. A record is processed when its first byte is contained by the range. This parameter is optional, but when specified, it must not be empty. See RFC 2616, Section 14.35.1 about how to specify the start and end of the range.
- Select
Parameters Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3 Select can continue to use the feature as usual. Learn more
Describes the parameters for Select job types.
Learn How to optimize querying your data in Amazon S3 using Amazon Athena, S3 Object Lambda, or client-side filtering.
- Server
Side Encryption ByDefault Describes the default server-side encryption to apply to new objects in the bucket. If a PUT Object request doesn't specify any server-side encryption, this default encryption will be applied. For more information, see PutBucketEncryption.
-
General purpose buckets - If you don't specify a customer managed key at configuration, Amazon S3 automatically creates an Amazon Web Services KMS key (
aws/s3
) in your Amazon Web Services account the first time that you add an object encrypted with SSE-KMS to a bucket. By default, Amazon S3 uses this KMS key for SSE-KMS. -
Directory buckets - Your SSE-KMS configuration can only support 1 customer managed key per directory bucket's lifetime. The Amazon Web Services managed key (
aws/s3
) isn't supported. -
Directory buckets - For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS.
-
- Server
Side Encryption Configuration Specifies the default server-side-encryption configuration.
- Server
Side Encryption Rule Specifies the default server-side encryption configuration.
-
General purpose buckets - If you're specifying a customer managed KMS key, we recommend using a fully qualified KMS key ARN. If you use a KMS key alias instead, then KMS resolves the key within the requester’s account. This behavior can result in data that's encrypted with a KMS key that belongs to the requester, and not the bucket owner.
-
Directory buckets - 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.
-
- Session
Credentials The established temporary security credentials of the session.
Directory buckets - These session credentials are only supported for the authentication and authorization of Zonal endpoint API operations on directory buckets.
- Simple
Prefix To use simple format for S3 keys for log objects, set SimplePrefix to an empty object.
\[DestinationPrefix\]\[YYYY\]-\[MM\]-\[DD\]-\[hh\]-\[mm\]-\[ss\]-\[UniqueString\]
- Source
Selection Criteria A container that describes additional filters for identifying the source objects that you want to replicate. You can choose to enable or disable the replication of these objects. Currently, Amazon S3 supports only the filter that you can specify for objects created with server-side encryption using a customer managed key stored in Amazon Web Services Key Management Service (SSE-KMS).
- SseKms
Encrypted Objects A container for filter information for the selection of S3 objects encrypted with Amazon Web Services KMS.
- Ssekms
Specifies the use of SSE-KMS to encrypt delivered inventory reports.
- Sses3
Specifies the use of SSE-S3 to encrypt delivered inventory reports.
- Stats
Container for the stats details.
- Stats
Event Container for the Stats Event.
- Storage
Class Analysis Specifies data related to access patterns to be collected and made available to analyze the tradeoffs between different storage classes for an Amazon S3 bucket.
- Storage
Class Analysis Data Export Container for data related to the storage class analysis for an Amazon S3 bucket for export.
- Tag
A container of a key value name pair.
- Tagging
Container for
TagSet
elements.- Target
Grant Container for granting information.
Buckets that use the bucket owner enforced setting for Object Ownership don't support target grants. For more information, see Permissions server access log delivery in the Amazon S3 User Guide.
- Target
Object KeyFormat Amazon S3 key format for log objects. Only one format, PartitionedPrefix or SimplePrefix, is allowed.
- Tiering
The S3 Intelligent-Tiering storage class is designed to optimize storage costs by automatically moving data to the most cost-effective storage access tier, without additional operational overhead.
- Topic
Configuration A container for specifying the configuration for publication of messages to an Amazon Simple Notification Service (Amazon SNS) topic when Amazon S3 detects specified events.
- Transition
Specifies when an object transitions to a specified storage class. For more information about Amazon S3 lifecycle configuration rules, see Transitioning Objects Using Amazon S3 Lifecycle in the Amazon S3 User Guide.
- Versioning
Configuration Describes the versioning state of an Amazon S3 bucket. For more information, see PUT Bucket versioning in the Amazon S3 API Reference.
- Website
Configuration Specifies website configuration parameters for an Amazon S3 bucket.
Enums§
- Analytics
Filter The filter used to describe a set of objects for analyses. A filter must have exactly one prefix, one tag, or one conjunction (AnalyticsAndOperator). If no filter is provided, all objects will be considered in any analysis.
- Analytics
S3Export File Format - When writing a match expression against
AnalyticsS3ExportFileFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Archive
Status - When writing a match expression against
ArchiveStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Bucket
Accelerate Status - When writing a match expression against
BucketAccelerateStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Bucket
Canned Acl - When writing a match expression against
BucketCannedAcl
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Bucket
Location Constraint - When writing a match expression against
BucketLocationConstraint
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Bucket
Logs Permission - When writing a match expression against
BucketLogsPermission
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Bucket
Type - When writing a match expression against
BucketType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Bucket
Versioning Status - When writing a match expression against
BucketVersioningStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Checksum
Algorithm - When writing a match expression against
ChecksumAlgorithm
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Checksum
Mode - When writing a match expression against
ChecksumMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Checksum
Type - When writing a match expression against
ChecksumType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Compression
Type - When writing a match expression against
CompressionType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Data
Redundancy - When writing a match expression against
DataRedundancy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Delete
Marker Replication Status - When writing a match expression against
DeleteMarkerReplicationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Encoding
Type - When writing a match expression against
EncodingType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Event
- When writing a match expression against
Event
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Existing
Object Replication Status - When writing a match expression against
ExistingObjectReplicationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Expiration
Status - When writing a match expression against
ExpirationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Expression
Type - When writing a match expression against
ExpressionType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - File
Header Info - When writing a match expression against
FileHeaderInfo
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Filter
Rule Name - When writing a match expression against
FilterRuleName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Intelligent
Tiering Access Tier - When writing a match expression against
IntelligentTieringAccessTier
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Intelligent
Tiering Status - When writing a match expression against
IntelligentTieringStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Inventory
Format - When writing a match expression against
InventoryFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Inventory
Frequency - When writing a match expression against
InventoryFrequency
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Inventory
Included Object Versions - When writing a match expression against
InventoryIncludedObjectVersions
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Inventory
Optional Field - When writing a match expression against
InventoryOptionalField
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Json
Type - When writing a match expression against
JsonType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Location
Type - When writing a match expression against
LocationType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Metadata
Directive - When writing a match expression against
MetadataDirective
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Metrics
Filter Specifies a metrics configuration filter. The metrics configuration only includes objects that meet the filter's criteria. A filter must be a prefix, an object tag, an access point ARN, or a conjunction (MetricsAndOperator). For more information, see PutBucketMetricsConfiguration.
- Metrics
Status - When writing a match expression against
MetricsStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - MfaDelete
- When writing a match expression against
MfaDelete
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - MfaDelete
Status - When writing a match expression against
MfaDeleteStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Object
Attributes - When writing a match expression against
ObjectAttributes
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Object
Canned Acl - When writing a match expression against
ObjectCannedAcl
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Object
Lock Enabled - When writing a match expression against
ObjectLockEnabled
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Object
Lock Legal Hold Status - When writing a match expression against
ObjectLockLegalHoldStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Object
Lock Mode - When writing a match expression against
ObjectLockMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Object
Lock Retention Mode - When writing a match expression against
ObjectLockRetentionMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Object
Ownership - When writing a match expression against
ObjectOwnership
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Object
Storage Class - When writing a match expression against
ObjectStorageClass
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Object
Version Storage Class - When writing a match expression against
ObjectVersionStorageClass
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Optional
Object Attributes - When writing a match expression against
OptionalObjectAttributes
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Owner
Override - When writing a match expression against
OwnerOverride
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Partition
Date Source - When writing a match expression against
PartitionDateSource
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Payer
- When writing a match expression against
Payer
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Permission
- When writing a match expression against
Permission
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Protocol
- When writing a match expression against
Protocol
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Quote
Fields - When writing a match expression against
QuoteFields
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Replica
Modifications Status - When writing a match expression against
ReplicaModificationsStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Replication
Rule Status - When writing a match expression against
ReplicationRuleStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Replication
Status - When writing a match expression against
ReplicationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Replication
Time Status - When writing a match expression against
ReplicationTimeStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Request
Charged - When writing a match expression against
RequestCharged
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Request
Payer - When writing a match expression against
RequestPayer
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Restore
Request Type - When writing a match expression against
RestoreRequestType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Select
Object Content Event Stream The container for selecting objects from a content event stream.
- Server
Side Encryption - When writing a match expression against
ServerSideEncryption
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Session
Mode - When writing a match expression against
SessionMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - SseKms
Encrypted Objects Status - When writing a match expression against
SseKmsEncryptedObjectsStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Storage
Class - When writing a match expression against
StorageClass
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Storage
Class Analysis Schema Version - When writing a match expression against
StorageClassAnalysisSchemaVersion
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Tagging
Directive - When writing a match expression against
TaggingDirective
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Tier
- When writing a match expression against
Tier
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transition
Default Minimum Object Size - When writing a match expression against
TransitionDefaultMinimumObjectSize
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transition
Storage Class - When writing a match expression against
TransitionStorageClass
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Type
- When writing a match expression against
Type
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.