class Aws::S3::Types::PutObjectOutput
@see docs.aws.amazon.com/goto/WebAPI/s3-2006-03-01/PutObjectOutput AWS API Documentation
@return [String]
</note>
<note markdown=“1”> This functionality is not supported for directory buckets.
for the request.
If present, indicates that the requester was successfully charged
@!attribute [rw] request_charged
@return [Integer]
</note>
Express One Zone storage class in directory buckets.
<note markdown=“1”> This functionality is only supported for objects in the Amazon S3
you append to an object.
The size of the object in bytes. This value is only be present if
@!attribute [rw] size
@return [Boolean]
(SSE-KMS).
server-side encryption with Key Management Service (KMS) keys
Indicates whether the uploaded object uses an S3 Bucket Key for
@!attribute [rw] bucket_key_enabled
@return [String]
Services KMS for future ‘GetObject` operations on this object.
object metadata and automatically gets passed on to Amazon Web
encryption context as key-value pairs. This value is stored as
encoded string of a UTF-8 encoded JSON, which contains the
to use for object encryption. The value of this header is a Base64
If present, indicates the Amazon Web Services KMS Encryption Context
@!attribute [rw] ssekms_encryption_context
@return [String]
encryption.
If present, indicates the ID of the KMS key that was used for object
@!attribute [rw] ssekms_key_id
@return [String]
</note>
<note markdown=“1”> This functionality is not supported for directory buckets.
encryption key.
round-trip message integrity verification of the customer-provided
was requested, the response will include this header to provide the
If server-side encryption with a customer-provided encryption key
@!attribute [rw] sse_customer_key_md5
@return [String]
</note>
<note markdown=“1”> This functionality is not supported for directory buckets.
encryption algorithm that’s used.
was requested, the response will include this header to confirm the
If server-side encryption with a customer-provided encryption key
@!attribute [rw] sse_customer_algorithm
@return [String]<br>: docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html<br>[1]: docs.aws.amazon.com/AmazonS3/latest/dev/AddingObjectstoVersioningEnabledBuckets.html<br><br><br><br></note>
<note markdown=“1”> This functionality is not supported for directory buckets.<br><br>[2].
information about returning the versioning state of a bucket, see
Versioning-Enabled Buckets] in the *Amazon S3 User Guide*. For
information about versioning, see [Adding Objects to
object simultaneously, it stores all of the objects. For more
bucket, if Amazon S3 receives multiple write requests for the same
returns this ID in the response. When you enable versioning for a
generates a unique version ID for the object being stored. Amazon S3
If you enable versioning for a bucket, Amazon S3 automatically
Version ID of the object.
@!attribute [rw] version_id
@return [String]
in Amazon S3.
The server-side encryption algorithm used when you store this object
@!attribute [rw] server_side_encryption
@return [String]<br>: docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html<br><br><br><br>User Guide*.
information, see [Checking object integrity] in the *Amazon S3
that is received is the same checksum that was specified. For more
header as a data integrity check to verify that the checksum type
uploads, the checksum type is always ‘FULL_OBJECT`. You can use this
object-level checksum for multipart objects. For `PutObject`
determines how part-level checksums are combined to create an
This header specifies the checksum type of the object, which
@!attribute [rw] checksum_type
@return [String]<br>: docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html#large-object-checksums<br><br><br><br>integrity][1] in the *Amazon S3 User Guide*.
calculated with multipart uploads, see [ Checking object
each individual part. For more information about how checksums are
object. Instead, it’s a calculation based on the checksum values of
uploads, this value may not be a direct checksum value of the full
use an API operation on an object that was uploaded using multipart
only be present if the object was uploaded with the object. When you
The Base64 encoded, 256-bit ‘SHA256` digest of the object. This will
@!attribute [rw] checksum_sha256
@return [String]<br>: docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html#large-object-checksums<br><br><br><br>integrity][1] in the *Amazon S3 User Guide*.
calculated with multipart uploads, see [ Checking object
each individual part. For more information about how checksums are
object. Instead, it’s a calculation based on the checksum values of
uploads, this value may not be a direct checksum value of the full
use the API operation on an object that was uploaded using multipart
only be present if the object was uploaded with the object. When you
The Base64 encoded, 160-bit ‘SHA1` digest of the object. This will
@!attribute [rw] checksum_sha1
@return [String]<br>: docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html<br><br><br><br>S3 User Guide].
with multipart uploads, see [Checking object integrity in the Amazon
object). For more information about how checksums are calculated
Amazon S3 added the default checksum, `CRC64NVME`, to the uploaded
checksum algorithm, or if it was uploaded without a checksum (and
header is present if the object was uploaded with the `CRC64NVME`
The Base64 encoded, 64-bit `CRC64NVME` checksum of the object. This
@!attribute [rw] checksum_crc64nvme
@return [String]<br>: docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html#large-object-checksums<br><br><br><br>object integrity] in the *Amazon S3 User Guide*.
how checksums are calculated with multipart uploads, see [ Checking
checksum values of each individual part. For more information about
value of the full object. Instead, it’s a calculation based on the
using multipart uploads, this value may not be a direct checksum
object. When you use an API operation on an object that was uploaded
checksum is only present if the checksum was uploaded with the
The Base64 encoded, 32-bit ‘CRC32C` checksum of the object. This
@!attribute [rw] checksum_crc32c
@return [String]<br>: docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html#large-object-checksums<br><br><br><br>object integrity] in the *Amazon S3 User Guide*.
how checksums are calculated with multipart uploads, see [ Checking
checksum values of each individual part. For more information about
value of the full object. Instead, it’s a calculation based on the
using multipart uploads, this value may not be a direct checksum
object. When you use an API operation on an object that was uploaded
checksum is only be present if the checksum was uploaded with the
The Base64 encoded, 32-bit ‘CRC32 checksum` of the object. This
@!attribute [rw] checksum_crc32
@return [String]
bucket isn’t the MD5 digest of the object.
Directory buckets - The ETag for the object in a directory
MD5 value.
object to Amazon S3 and compare the returned ETag to the calculated
MD5 digest of the object, you can calculate the MD5 while putting an
corrupted traversing the network, for objects where the ETag is the
General purpose buckets - To ensure that data is not
Entity tag for the uploaded object.
@!attribute [rw] etag
@return [String]<br>: docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html<br><br><br><br></note>
responses for directory buckets.
and this header returns the value “‘NotImplemented`” in all
<note markdown=“1”> Object expiration information is not returned in directory buckets
expiration. The value of the `rule-id` is URL-encoded.
`rule-id` key-value pairs that provide information about object
the response includes this header. It includes the `expiry-date` and<br>[1]) in the *Amazon S3 User Guide*,
If the expiration is configured for the object (see
@!attribute [rw] expiration