Module types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that Amazon Simple Storage Service can respond with.

Structs

• AbortIncompleteMultipartUpload

  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.

• AccelerateConfiguration

  Configures the transfer acceleration state for an Amazon S3 bucket. For more information, see Amazon S3 Transfer Acceleration in the Amazon S3 User Guide.

• AccessControlPolicy

  Contains the elements that set the ACL permissions for an object per grantee.

• AccessControlTranslation

  A container for information about access control for replicas.

• AnalyticsAndOperator

  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.

• AnalyticsConfiguration

  Specifies the configuration and any analyses for the analytics filter of an Amazon S3 bucket.

• AnalyticsExportDestination

  Where to publish the analytics results.

• AnalyticsS3BucketDestination

  Contains information about where to publish the analytics results.

• Bucket

  In terms of implementation, a Bucket is a resource.

• BucketInfo

  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.

• BucketLifecycleConfiguration

  Specifies the lifecycle configuration for objects in an Amazon S3 bucket. For more information, see Object Lifecycle Management in the Amazon S3 User Guide.

• BucketLoggingStatus

  Container for logging status information.

• Checksum

  Contains all the possible checksum or digest values for an object.

• CommonPrefix

  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/.

• CompletedMultipartUpload

  The container for the completed multipart upload details.

• CompletedPart

  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.

• ContinuationEvent

• CopyObjectResult

  Container for all response elements.

• CopyPartResult

  Container for all response elements.

• CorsConfiguration

  Describes the cross-origin access configuration for objects in an Amazon S3 bucket. For more information, see Enabling Cross-Origin Resource Sharing in the Amazon S3 User Guide.

• CorsRule

  Specifies a cross-origin access rule for an Amazon S3 bucket.

• CreateBucketConfiguration

  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.

• DefaultRetention

  The container element for 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 either Days or Years but you must select one. You cannot specify Days and Years at the same time.

• Delete

  Container for the objects to delete.

• DeleteMarkerEntry

  Information about the delete marker.

• DeleteMarkerReplication

  Specifies whether Amazon S3 replicates delete markers. If you specify a Filter in your replication configuration, you must also include a DeleteMarkerReplication element. If your Filter includes a Tag element, the DeleteMarkerReplication 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.

• DeletedObject

  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.

• EncryptionConfiguration

  Specifies encryption-related information for an Amazon S3 bucket that is a destination for replicated objects.

• 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.

• ErrorDocument

  The error information.

• EventBridgeConfiguration

  A container for specifying the configuration for Amazon EventBridge.

• ExistingObjectReplication

  Optional configuration to replicate existing source bucket objects. For more information, see Replicating Existing Objects in the Amazon S3 User Guide.

• FilterRule

  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- or engineering/. Then, you can use FilterRule 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.

• GetObjectAttributesParts

  A collection of parts associated with a multipart upload.

• GlacierJobParameters

  Container for S3 Glacier job parameters.

• Grant

  Container for grant information.

• Grantee

  Container for the person being granted permissions.

• IndexDocument

  Container for the Suffix element.

• Initiator

  Container element that identifies who initiated the multipart upload.

• InputSerialization

  Describes the serialization format of the object.

• IntelligentTieringAndOperator

  A container for specifying S3 Intelligent-Tiering filters. The filters determine the subset of objects to which the rule applies.

• IntelligentTieringConfiguration

  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.

• IntelligentTieringFilter

  The Filter is used to identify objects that the S3 Intelligent-Tiering configuration applies to.

• InventoryConfiguration

  Specifies the inventory configuration for an Amazon S3 bucket. For more information, see GET Bucket inventory in the Amazon S3 API Reference.

• InventoryDestination

  Specifies the inventory configuration for an Amazon S3 bucket.

• InventoryEncryption

  Contains the type of server-side encryption used to encrypt the inventory results.

• InventoryFilter

  Specifies an inventory filter. The inventory only includes objects that meet the filter's criteria.

• InventoryS3BucketDestination

  Contains the bucket name, file format, bucket owner (optional), and prefix (optional) where inventory results are published.

• InventorySchedule

  Specifies the schedule for generating inventory results.

• JsonInput

  Specifies JSON as object's input serialization format.

• JsonOutput

  Specifies JSON as request's output serialization format.

• LambdaFunctionConfiguration

  A container for specifying the configuration for Lambda notifications.

• LifecycleExpiration

  Container for the expiration for the lifecycle of the object.

  For more information see, Managing your storage lifecycle in the Amazon S3 User Guide.

• LifecycleRule

  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.

• LifecycleRuleAndOperator

  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.

• LocationInfo

  Specifies the location where the bucket will be created.

  For directory buckets, the location type is Availability Zone. For more information about directory buckets, see Directory buckets in the Amazon S3 User Guide.

  This functionality is only supported by directory buckets.

• LoggingEnabled

  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.

• MetadataEntry

  A metadata key-value pair to store with an object.

• Metrics

  A container specifying replication metrics-related settings enabling replication metrics and events.

• MetricsAndOperator

  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.

• MetricsConfiguration

  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.

• MultipartUpload

  Container for the MultipartUpload for the Amazon S3 object.

• NoncurrentVersionExpiration

  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.

• NoncurrentVersionTransition

  Container for the transition rule that describes when noncurrent objects transition to the STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER_IR, GLACIER, or DEEP_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 the STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER_IR, GLACIER, or DEEP_ARCHIVE storage class at a specific period in the object's lifetime.

• NotificationConfiguration

  A container for specifying the notification configuration of the bucket. If this element is empty, notifications are turned off for the bucket.

• NotificationConfigurationFilter

  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.

• ObjectIdentifier

  Object Identifier is unique value to identify objects.

• ObjectLockConfiguration

  The container element for Object Lock configuration parameters.

• ObjectLockLegalHold

  A legal hold configuration for an object.

• ObjectLockRetention

  A Retention configuration for an object.

• ObjectLockRule

  The container element for an Object Lock rule.

• ObjectPart

  A container for elements related to an individual part.

• ObjectVersion

  The version of an object.

• OutputLocation

  Describes the location where the restore job's output is stored.

• OutputSerialization

  Describes how results of the Select job are serialized.

• Owner

  Container for the owner's display name and ID.

• OwnershipControls

  The container element for a bucket's ownership controls.

• OwnershipControlsRule

  The container element for an ownership control rule.

• ParquetInput

  Container for Parquet.

• Part

  Container for elements related to a part.

• PartitionedPrefix

  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.

• PolicyStatus

  The container element for a bucket's policy status.

• Progress

  This data type contains information about progress of an operation.

• ProgressEvent

  This data type contains information about the progress event of an operation.

• PublicAccessBlockConfiguration

  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.

• QueueConfiguration

  Specifies the configuration for publishing messages to an Amazon Simple Queue Service (Amazon SQS) queue when Amazon S3 detects specified events.

• RecordsEvent

  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.

• RedirectAllRequestsTo

  Specifies the redirect behavior of all requests to a website endpoint of an Amazon S3 bucket.

• ReplicaModifications

  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 to Enabled 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.

• ReplicationConfiguration

  A container for replication rules. You can add up to 1,000 rules. The maximum size of a replication configuration is 2 MB.

• ReplicationRule

  Specifies which Amazon S3 objects to replicate and where to store the replicas.

• ReplicationRuleAndOperator

  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 a Tag filter, wrap these filters in an And tag.

  • If you specify a filter based on multiple tags, wrap the Tag elements in an And tag.

• ReplicationTime

  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.

• ReplicationTimeValue

  A container specifying the time value for S3 Replication Time Control (S3 RTC) and replication metrics EventThreshold.

• RequestPaymentConfiguration

  Container for Payer.

• RequestProgress

  Container for specifying if periodic QueryProgress messages should be sent.

• RestoreRequest

  Container for restore job parameters.

• RestoreStatus

  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.

• RoutingRule

  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.

• S3KeyFilter

  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.

• ScanRange

  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.

• SelectParameters

  Describes the parameters for Select job types.

• ServerSideEncryptionByDefault

  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. If you don't specify a customer managed key at configuration, Amazon S3 automatically creates an Amazon Web Services KMS key 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. For more information, see PUT Bucket encryption in the Amazon S3 API Reference.

• ServerSideEncryptionConfiguration

  Specifies the default server-side-encryption configuration.

• ServerSideEncryptionRule

  Specifies the default server-side encryption configuration.

• SessionCredentials

  The established temporary security credentials of the session.

  Directory buckets - These session credentials are only supported for the authentication and authorization of Zonal endpoint APIs on directory buckets.

• SimplePrefix

  To use simple format for S3 keys for log objects, set SimplePrefix to an empty object.

  [DestinationPrefix][YYYY]-[MM]-[DD]-[hh]-[mm]-[ss]-[UniqueString]

• SourceSelectionCriteria

  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).

• SseKmsEncryptedObjects

  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.

• StatsEvent

  Container for the Stats Event.

• StorageClassAnalysis

  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.

• StorageClassAnalysisDataExport

  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.

• TargetGrant

  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.

• TargetObjectKeyFormat

  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.

• TopicConfiguration

  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.

• VersioningConfiguration

  Describes the versioning state of an Amazon S3 bucket. For more information, see PUT Bucket versioning in the Amazon S3 API Reference.

• WebsiteConfiguration

  Specifies website configuration parameters for an Amazon S3 bucket.

Enums

• AnalyticsFilter

  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.

• AnalyticsS3ExportFileFormat
  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.
• ArchiveStatus
  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.
• BucketAccelerateStatus
  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.
• BucketCannedAcl
  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.
• BucketLocationConstraint
  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.
• BucketLogsPermission
  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.
• BucketType
  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.
• BucketVersioningStatus
  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.
• ChecksumAlgorithm
  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.
• ChecksumMode
  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.
• CompressionType
  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.
• DataRedundancy
  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.
• DeleteMarkerReplicationStatus
  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.
• EncodingType
  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.
• ExistingObjectReplicationStatus
  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.
• ExpirationStatus
  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.
• ExpressionType
  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.
• FileHeaderInfo
  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.
• FilterRuleName
  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.
• IntelligentTieringAccessTier
  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.
• IntelligentTieringStatus
  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.
• InventoryFormat
  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.
• InventoryFrequency
  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.
• InventoryIncludedObjectVersions
  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.
• InventoryOptionalField
  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.
• JsonType
  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.
• LifecycleRuleFilter

  The Filter is used to identify objects that a Lifecycle Rule applies to. A Filter can have exactly one of Prefix, Tag, ObjectSizeGreaterThan, ObjectSizeLessThan, or And specified. If the Filter element is left empty, the Lifecycle Rule applies to all objects in the bucket.

• LocationType
  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.
• MetadataDirective
  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.
• MetricsFilter

  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.

• MetricsStatus
  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.
• MfaDeleteStatus
  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.
• ObjectAttributes
  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.
• ObjectCannedAcl
  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.
• ObjectLockEnabled
  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.
• ObjectLockLegalHoldStatus
  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.
• ObjectLockMode
  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.
• ObjectLockRetentionMode
  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.
• ObjectOwnership
  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.
• ObjectStorageClass
  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.
• ObjectVersionStorageClass
  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.
• OptionalObjectAttributes
  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.
• OwnerOverride
  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.
• PartitionDateSource
  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.
• QuoteFields
  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.
• ReplicaModificationsStatus
  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.
• ReplicationRuleFilter

  A filter that identifies the subset of objects to which the replication rule applies. A Filter must specify exactly one Prefix, Tag, or an And child element.

• ReplicationRuleStatus
  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.
• ReplicationStatus
  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.
• ReplicationTimeStatus
  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.
• RequestCharged
  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.
• RequestPayer
  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.
• RestoreRequestType
  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.
• SelectObjectContentEventStream

  The container for selecting objects from a content event stream.

• ServerSideEncryption
  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.
• SessionMode
  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.
• SseKmsEncryptedObjectsStatus
  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.
• StorageClass
  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.
• StorageClassAnalysisSchemaVersion
  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.
• TaggingDirective
  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.
• TransitionStorageClass
  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.