class Aws::S3::Types::CreateSessionRequest

@see docs.aws.amazon.com/goto/WebAPI/s3-2006-03-01/CreateSessionRequest AWS API Documentation
@return [Boolean]<br>: docs.aws.amazon.com/AmazonS3/latest/userguide/create-import-job<br>[3]: docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-objects-Batch-Ops<br>[2]: docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html<br>[1]: docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html<br><br><br><br>KMS-encrypted object.
makes a call to KMS every time a copy request is made for a<br>Operations], or [the import jobs]. In this case, Amazon S3<br>[1], [UploadPartCopy], [the Copy operation in Batch
general purpose buckets, or between directory buckets, through
purpose buckets to directory buckets, from directory buckets to
supported, when you copy SSE-KMS encrypted objects from general
a directory bucket and can’t be disabled. S3 Bucket Keys aren’t
S3 Bucket Keys are always enabled for ‘GET` and `PUT` operations in
encryption with server-side encryption using KMS keys (SSE-KMS).
Specifies whether Amazon S3 should use an S3 Bucket Key for object
@!attribute [rw] bucket_key_enabled
@return [String]<br>: docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html#encryption-context<br><br><br><br>additional encryption context value is not supported.
encryption context - the bucket Amazon Resource Name (ARN). An
encryption context value. The value must match the default
**Directory buckets** - You can optionally provide an explicit<br><br>context] in the *Amazon S3 User Guide*.
context for your object. For more information, see [Encryption
during `CopyObject` operations if you want an additional encryption
**General purpose buckets** - This value must be explicitly added
object.
to Amazon Web Services KMS for future `GetObject` operations on this
value is stored as object metadata and automatically gets passed on
JSON, which contains the encryption context as key-value pairs. This
value of this header is a Base64 encoded string of a UTF-8 encoded
additional encryption context to use for object encryption. The
Specifies the Amazon Web Services KMS Encryption Context as an
@!attribute [rw] ssekms_encryption_context
@return [String]<br>: docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk<br>[1]: docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk<br><br><br><br>managed key] (`aws/s3`) isn’t supported.<br>key] per directory bucket’s lifetime. The [Amazon Web Services
Your SSE-KMS configuration can only support 1 [customer managed
must use the full Key ARN not the Key ID.
doesn’t exist in the same account that’t issuing the command, you
alias format of the KMS key isn’t supported. Also, if the KMS key
`400 Bad Request` error. Only use the key ID or key ARN. The key
encryption customer managed key to use. Otherwise, you get an HTTP
header with the ID (Key ID or Key ARN) of the KMS symmetric
must specify the ‘ x-amz-server-side-encryption-aws-kms-key-id`
If you specify `x-amz-server-side-encryption` with `aws:kms`, you
@!attribute [rw] ssekms_key_id
@return [String]<br>: docs.aws.amazon.com/AmazonS3/latest/userguide/serv-side-encryption.html<br><br><br><br>encryption][1] in the *Amazon S3 User Guide*.
SSE-S3. For more information, see [Protecting data with server-side
keys (SSE-KMS) (`aws:kms`). By default, Amazon S3 encrypts data with
managed keys (SSE-S3) (`AES256`) and server-side encryption with KMS
server-side encryption: server-side encryption with Amazon S3
For directory buckets, there are only two supported options for
in the directory bucket.
The server-side encryption algorithm to use when you store objects
@!attribute [rw] server_side_encryption
@return [String]
The name of the bucket that you create a session for.
@!attribute [rw] bucket
@return [String]
`GetObjectAttributes`, `ListParts`, and `ListMultipartUploads`.
operations: `GetObject`, `HeadObject`, `ListObjectsV2`,
is constrained to execute the following Zonal endpoint API
endpoint API operations on a directory bucket. A `ReadOnly` session
created. A `ReadWrite` session is capable of executing all the Zonal
`ReadWrite` or `ReadOnly`. By default, a `ReadWrite` session is
Specifies the mode of the session that will be created, either
@!attribute [rw] session_mode