// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
#[allow(missing_docs)] // documentation missing in model
#[non_exhaustive]
#[derive(::std::clone::Clone, ::std::cmp::PartialEq, ::std::fmt::Debug)]
pub struct CreateBucketInput {
/// <p>The canned ACL to apply to the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub acl: ::std::option::Option<crate::types::BucketCannedAcl>,
/// <p>The name of the bucket to create.</p>
/// <p><b>General purpose buckets</b> - For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html">Bucket naming rules</a> in the <i>Amazon S3 User Guide</i>.</p>
/// <p><b>Directory buckets </b> - When you use this operation with a directory bucket, you must use path-style requests in the format <code>https://s3express-control.<i>region-code</i>.amazonaws.com/<i>bucket-name</i> </code>. Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format <code> <i>bucket-base-name</i>--<i>zone-id</i>--x-s3</code> (for example, <code> <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html">Directory bucket naming rules</a> in the <i>Amazon S3 User Guide</i></p>
pub bucket: ::std::option::Option<::std::string::String>,
/// <p>The configuration information for the bucket.</p>
pub create_bucket_configuration: ::std::option::Option<crate::types::CreateBucketConfiguration>,
/// <p>Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub grant_full_control: ::std::option::Option<::std::string::String>,
/// <p>Allows grantee to list the objects in the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub grant_read: ::std::option::Option<::std::string::String>,
/// <p>Allows grantee to read the bucket ACL.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub grant_read_acp: ::std::option::Option<::std::string::String>,
/// <p>Allows grantee to create new objects in the bucket.</p>
/// <p>For the bucket and object owners of existing objects, also allows deletions and overwrites of those objects.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub grant_write: ::std::option::Option<::std::string::String>,
/// <p>Allows grantee to write the ACL for the applicable bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub grant_write_acp: ::std::option::Option<::std::string::String>,
/// <p>Specifies whether you want S3 Object Lock to be enabled for the new bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub object_lock_enabled_for_bucket: ::std::option::Option<bool>,
/// <p>The container element for object ownership for a bucket's ownership controls.</p>
/// <p><code>BucketOwnerPreferred</code> - Objects uploaded to the bucket change ownership to the bucket owner if the objects are uploaded with the <code>bucket-owner-full-control</code> canned ACL.</p>
/// <p><code>ObjectWriter</code> - The uploading account will own the object if the object is uploaded with the <code>bucket-owner-full-control</code> canned ACL.</p>
/// <p><code>BucketOwnerEnforced</code> - Access control lists (ACLs) are disabled and no longer affect permissions. The bucket owner automatically owns and has full control over every object in the bucket. The bucket only accepts PUT requests that don't specify an ACL or specify bucket owner full control ACLs (such as the predefined <code>bucket-owner-full-control</code> canned ACL or a custom ACL in XML format that grants the same permissions).</p>
/// <p>By default, <code>ObjectOwnership</code> is set to <code>BucketOwnerEnforced</code> and ACLs are disabled. We recommend keeping ACLs disabled, except in uncommon use cases where you must control access for each object individually. For more information about S3 Object Ownership, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling ownership of objects and disabling ACLs for your bucket</a> in the <i>Amazon S3 User Guide</i>.</p><note>
/// <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>
/// </note>
pub object_ownership: ::std::option::Option<crate::types::ObjectOwnership>,
/// <p>Specifies the namespace where you want to create your general purpose bucket. When you create a general purpose bucket, you can choose to create a bucket in the shared global namespace or you can choose to create a bucket in your account regional namespace. Your account regional namespace is a subdivision of the global namespace that only your account can create buckets in. For more information on bucket namespaces, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/gpbucketnamespaces.html">Namespaces for general purpose buckets</a>.</p>
/// <p>General purpose buckets in your account regional namespace must follow a specific naming convention. These buckets consist of a bucket name prefix that you create, and a suffix that contains your 12-digit Amazon Web Services Account ID, the Amazon Web Services Region code, and ends with <code>-an</code>. Bucket names must follow the format <code>bucket-name-prefix-accountId-region-an</code> (for example, <code>amzn-s3-demo-bucket-111122223333-us-west-2-an</code>). For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html#account-regional-naming-rules">Account regional namespace naming rules</a> in the <i>Amazon S3 User Guide</i>.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub bucket_namespace: ::std::option::Option<crate::types::BucketNamespace>,
}
impl CreateBucketInput {
/// <p>The canned ACL to apply to the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn acl(&self) -> ::std::option::Option<&crate::types::BucketCannedAcl> {
self.acl.as_ref()
}
/// <p>The name of the bucket to create.</p>
/// <p><b>General purpose buckets</b> - For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html">Bucket naming rules</a> in the <i>Amazon S3 User Guide</i>.</p>
/// <p><b>Directory buckets </b> - When you use this operation with a directory bucket, you must use path-style requests in the format <code>https://s3express-control.<i>region-code</i>.amazonaws.com/<i>bucket-name</i> </code>. Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format <code> <i>bucket-base-name</i>--<i>zone-id</i>--x-s3</code> (for example, <code> <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html">Directory bucket naming rules</a> in the <i>Amazon S3 User Guide</i></p>
pub fn bucket(&self) -> ::std::option::Option<&str> {
self.bucket.as_deref()
}
/// <p>The configuration information for the bucket.</p>
pub fn create_bucket_configuration(&self) -> ::std::option::Option<&crate::types::CreateBucketConfiguration> {
self.create_bucket_configuration.as_ref()
}
/// <p>Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn grant_full_control(&self) -> ::std::option::Option<&str> {
self.grant_full_control.as_deref()
}
/// <p>Allows grantee to list the objects in the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn grant_read(&self) -> ::std::option::Option<&str> {
self.grant_read.as_deref()
}
/// <p>Allows grantee to read the bucket ACL.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn grant_read_acp(&self) -> ::std::option::Option<&str> {
self.grant_read_acp.as_deref()
}
/// <p>Allows grantee to create new objects in the bucket.</p>
/// <p>For the bucket and object owners of existing objects, also allows deletions and overwrites of those objects.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn grant_write(&self) -> ::std::option::Option<&str> {
self.grant_write.as_deref()
}
/// <p>Allows grantee to write the ACL for the applicable bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn grant_write_acp(&self) -> ::std::option::Option<&str> {
self.grant_write_acp.as_deref()
}
/// <p>Specifies whether you want S3 Object Lock to be enabled for the new bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn object_lock_enabled_for_bucket(&self) -> ::std::option::Option<bool> {
self.object_lock_enabled_for_bucket
}
/// <p>The container element for object ownership for a bucket's ownership controls.</p>
/// <p><code>BucketOwnerPreferred</code> - Objects uploaded to the bucket change ownership to the bucket owner if the objects are uploaded with the <code>bucket-owner-full-control</code> canned ACL.</p>
/// <p><code>ObjectWriter</code> - The uploading account will own the object if the object is uploaded with the <code>bucket-owner-full-control</code> canned ACL.</p>
/// <p><code>BucketOwnerEnforced</code> - Access control lists (ACLs) are disabled and no longer affect permissions. The bucket owner automatically owns and has full control over every object in the bucket. The bucket only accepts PUT requests that don't specify an ACL or specify bucket owner full control ACLs (such as the predefined <code>bucket-owner-full-control</code> canned ACL or a custom ACL in XML format that grants the same permissions).</p>
/// <p>By default, <code>ObjectOwnership</code> is set to <code>BucketOwnerEnforced</code> and ACLs are disabled. We recommend keeping ACLs disabled, except in uncommon use cases where you must control access for each object individually. For more information about S3 Object Ownership, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling ownership of objects and disabling ACLs for your bucket</a> in the <i>Amazon S3 User Guide</i>.</p><note>
/// <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>
/// </note>
pub fn object_ownership(&self) -> ::std::option::Option<&crate::types::ObjectOwnership> {
self.object_ownership.as_ref()
}
/// <p>Specifies the namespace where you want to create your general purpose bucket. When you create a general purpose bucket, you can choose to create a bucket in the shared global namespace or you can choose to create a bucket in your account regional namespace. Your account regional namespace is a subdivision of the global namespace that only your account can create buckets in. For more information on bucket namespaces, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/gpbucketnamespaces.html">Namespaces for general purpose buckets</a>.</p>
/// <p>General purpose buckets in your account regional namespace must follow a specific naming convention. These buckets consist of a bucket name prefix that you create, and a suffix that contains your 12-digit Amazon Web Services Account ID, the Amazon Web Services Region code, and ends with <code>-an</code>. Bucket names must follow the format <code>bucket-name-prefix-accountId-region-an</code> (for example, <code>amzn-s3-demo-bucket-111122223333-us-west-2-an</code>). For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html#account-regional-naming-rules">Account regional namespace naming rules</a> in the <i>Amazon S3 User Guide</i>.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn bucket_namespace(&self) -> ::std::option::Option<&crate::types::BucketNamespace> {
self.bucket_namespace.as_ref()
}
}
impl CreateBucketInput {
/// Creates a new builder-style object to manufacture [`CreateBucketInput`](crate::operation::create_bucket::CreateBucketInput).
pub fn builder() -> crate::operation::create_bucket::builders::CreateBucketInputBuilder {
crate::operation::create_bucket::builders::CreateBucketInputBuilder::default()
}
}
/// A builder for [`CreateBucketInput`](crate::operation::create_bucket::CreateBucketInput).
#[derive(::std::clone::Clone, ::std::cmp::PartialEq, ::std::default::Default, ::std::fmt::Debug)]
#[non_exhaustive]
pub struct CreateBucketInputBuilder {
pub(crate) acl: ::std::option::Option<crate::types::BucketCannedAcl>,
pub(crate) bucket: ::std::option::Option<::std::string::String>,
pub(crate) create_bucket_configuration: ::std::option::Option<crate::types::CreateBucketConfiguration>,
pub(crate) grant_full_control: ::std::option::Option<::std::string::String>,
pub(crate) grant_read: ::std::option::Option<::std::string::String>,
pub(crate) grant_read_acp: ::std::option::Option<::std::string::String>,
pub(crate) grant_write: ::std::option::Option<::std::string::String>,
pub(crate) grant_write_acp: ::std::option::Option<::std::string::String>,
pub(crate) object_lock_enabled_for_bucket: ::std::option::Option<bool>,
pub(crate) object_ownership: ::std::option::Option<crate::types::ObjectOwnership>,
pub(crate) bucket_namespace: ::std::option::Option<crate::types::BucketNamespace>,
}
impl CreateBucketInputBuilder {
/// <p>The canned ACL to apply to the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn acl(mut self, input: crate::types::BucketCannedAcl) -> Self {
self.acl = ::std::option::Option::Some(input);
self
}
/// <p>The canned ACL to apply to the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn set_acl(mut self, input: ::std::option::Option<crate::types::BucketCannedAcl>) -> Self {
self.acl = input;
self
}
/// <p>The canned ACL to apply to the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn get_acl(&self) -> &::std::option::Option<crate::types::BucketCannedAcl> {
&self.acl
}
/// <p>The name of the bucket to create.</p>
/// <p><b>General purpose buckets</b> - For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html">Bucket naming rules</a> in the <i>Amazon S3 User Guide</i>.</p>
/// <p><b>Directory buckets </b> - When you use this operation with a directory bucket, you must use path-style requests in the format <code>https://s3express-control.<i>region-code</i>.amazonaws.com/<i>bucket-name</i> </code>. Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format <code> <i>bucket-base-name</i>--<i>zone-id</i>--x-s3</code> (for example, <code> <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html">Directory bucket naming rules</a> in the <i>Amazon S3 User Guide</i></p>
/// This field is required.
pub fn bucket(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
self.bucket = ::std::option::Option::Some(input.into());
self
}
/// <p>The name of the bucket to create.</p>
/// <p><b>General purpose buckets</b> - For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html">Bucket naming rules</a> in the <i>Amazon S3 User Guide</i>.</p>
/// <p><b>Directory buckets </b> - When you use this operation with a directory bucket, you must use path-style requests in the format <code>https://s3express-control.<i>region-code</i>.amazonaws.com/<i>bucket-name</i> </code>. Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format <code> <i>bucket-base-name</i>--<i>zone-id</i>--x-s3</code> (for example, <code> <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html">Directory bucket naming rules</a> in the <i>Amazon S3 User Guide</i></p>
pub fn set_bucket(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
self.bucket = input;
self
}
/// <p>The name of the bucket to create.</p>
/// <p><b>General purpose buckets</b> - For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html">Bucket naming rules</a> in the <i>Amazon S3 User Guide</i>.</p>
/// <p><b>Directory buckets </b> - When you use this operation with a directory bucket, you must use path-style requests in the format <code>https://s3express-control.<i>region-code</i>.amazonaws.com/<i>bucket-name</i> </code>. Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format <code> <i>bucket-base-name</i>--<i>zone-id</i>--x-s3</code> (for example, <code> <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html">Directory bucket naming rules</a> in the <i>Amazon S3 User Guide</i></p>
pub fn get_bucket(&self) -> &::std::option::Option<::std::string::String> {
&self.bucket
}
/// <p>The configuration information for the bucket.</p>
pub fn create_bucket_configuration(mut self, input: crate::types::CreateBucketConfiguration) -> Self {
self.create_bucket_configuration = ::std::option::Option::Some(input);
self
}
/// <p>The configuration information for the bucket.</p>
pub fn set_create_bucket_configuration(mut self, input: ::std::option::Option<crate::types::CreateBucketConfiguration>) -> Self {
self.create_bucket_configuration = input;
self
}
/// <p>The configuration information for the bucket.</p>
pub fn get_create_bucket_configuration(&self) -> &::std::option::Option<crate::types::CreateBucketConfiguration> {
&self.create_bucket_configuration
}
/// <p>Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn grant_full_control(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
self.grant_full_control = ::std::option::Option::Some(input.into());
self
}
/// <p>Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn set_grant_full_control(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
self.grant_full_control = input;
self
}
/// <p>Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn get_grant_full_control(&self) -> &::std::option::Option<::std::string::String> {
&self.grant_full_control
}
/// <p>Allows grantee to list the objects in the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn grant_read(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
self.grant_read = ::std::option::Option::Some(input.into());
self
}
/// <p>Allows grantee to list the objects in the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn set_grant_read(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
self.grant_read = input;
self
}
/// <p>Allows grantee to list the objects in the bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn get_grant_read(&self) -> &::std::option::Option<::std::string::String> {
&self.grant_read
}
/// <p>Allows grantee to read the bucket ACL.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn grant_read_acp(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
self.grant_read_acp = ::std::option::Option::Some(input.into());
self
}
/// <p>Allows grantee to read the bucket ACL.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn set_grant_read_acp(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
self.grant_read_acp = input;
self
}
/// <p>Allows grantee to read the bucket ACL.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn get_grant_read_acp(&self) -> &::std::option::Option<::std::string::String> {
&self.grant_read_acp
}
/// <p>Allows grantee to create new objects in the bucket.</p>
/// <p>For the bucket and object owners of existing objects, also allows deletions and overwrites of those objects.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn grant_write(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
self.grant_write = ::std::option::Option::Some(input.into());
self
}
/// <p>Allows grantee to create new objects in the bucket.</p>
/// <p>For the bucket and object owners of existing objects, also allows deletions and overwrites of those objects.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn set_grant_write(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
self.grant_write = input;
self
}
/// <p>Allows grantee to create new objects in the bucket.</p>
/// <p>For the bucket and object owners of existing objects, also allows deletions and overwrites of those objects.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn get_grant_write(&self) -> &::std::option::Option<::std::string::String> {
&self.grant_write
}
/// <p>Allows grantee to write the ACL for the applicable bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn grant_write_acp(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
self.grant_write_acp = ::std::option::Option::Some(input.into());
self
}
/// <p>Allows grantee to write the ACL for the applicable bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn set_grant_write_acp(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
self.grant_write_acp = input;
self
}
/// <p>Allows grantee to write the ACL for the applicable bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn get_grant_write_acp(&self) -> &::std::option::Option<::std::string::String> {
&self.grant_write_acp
}
/// <p>Specifies whether you want S3 Object Lock to be enabled for the new bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn object_lock_enabled_for_bucket(mut self, input: bool) -> Self {
self.object_lock_enabled_for_bucket = ::std::option::Option::Some(input);
self
}
/// <p>Specifies whether you want S3 Object Lock to be enabled for the new bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn set_object_lock_enabled_for_bucket(mut self, input: ::std::option::Option<bool>) -> Self {
self.object_lock_enabled_for_bucket = input;
self
}
/// <p>Specifies whether you want S3 Object Lock to be enabled for the new bucket.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn get_object_lock_enabled_for_bucket(&self) -> &::std::option::Option<bool> {
&self.object_lock_enabled_for_bucket
}
/// <p>The container element for object ownership for a bucket's ownership controls.</p>
/// <p><code>BucketOwnerPreferred</code> - Objects uploaded to the bucket change ownership to the bucket owner if the objects are uploaded with the <code>bucket-owner-full-control</code> canned ACL.</p>
/// <p><code>ObjectWriter</code> - The uploading account will own the object if the object is uploaded with the <code>bucket-owner-full-control</code> canned ACL.</p>
/// <p><code>BucketOwnerEnforced</code> - Access control lists (ACLs) are disabled and no longer affect permissions. The bucket owner automatically owns and has full control over every object in the bucket. The bucket only accepts PUT requests that don't specify an ACL or specify bucket owner full control ACLs (such as the predefined <code>bucket-owner-full-control</code> canned ACL or a custom ACL in XML format that grants the same permissions).</p>
/// <p>By default, <code>ObjectOwnership</code> is set to <code>BucketOwnerEnforced</code> and ACLs are disabled. We recommend keeping ACLs disabled, except in uncommon use cases where you must control access for each object individually. For more information about S3 Object Ownership, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling ownership of objects and disabling ACLs for your bucket</a> in the <i>Amazon S3 User Guide</i>.</p><note>
/// <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>
/// </note>
pub fn object_ownership(mut self, input: crate::types::ObjectOwnership) -> Self {
self.object_ownership = ::std::option::Option::Some(input);
self
}
/// <p>The container element for object ownership for a bucket's ownership controls.</p>
/// <p><code>BucketOwnerPreferred</code> - Objects uploaded to the bucket change ownership to the bucket owner if the objects are uploaded with the <code>bucket-owner-full-control</code> canned ACL.</p>
/// <p><code>ObjectWriter</code> - The uploading account will own the object if the object is uploaded with the <code>bucket-owner-full-control</code> canned ACL.</p>
/// <p><code>BucketOwnerEnforced</code> - Access control lists (ACLs) are disabled and no longer affect permissions. The bucket owner automatically owns and has full control over every object in the bucket. The bucket only accepts PUT requests that don't specify an ACL or specify bucket owner full control ACLs (such as the predefined <code>bucket-owner-full-control</code> canned ACL or a custom ACL in XML format that grants the same permissions).</p>
/// <p>By default, <code>ObjectOwnership</code> is set to <code>BucketOwnerEnforced</code> and ACLs are disabled. We recommend keeping ACLs disabled, except in uncommon use cases where you must control access for each object individually. For more information about S3 Object Ownership, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling ownership of objects and disabling ACLs for your bucket</a> in the <i>Amazon S3 User Guide</i>.</p><note>
/// <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>
/// </note>
pub fn set_object_ownership(mut self, input: ::std::option::Option<crate::types::ObjectOwnership>) -> Self {
self.object_ownership = input;
self
}
/// <p>The container element for object ownership for a bucket's ownership controls.</p>
/// <p><code>BucketOwnerPreferred</code> - Objects uploaded to the bucket change ownership to the bucket owner if the objects are uploaded with the <code>bucket-owner-full-control</code> canned ACL.</p>
/// <p><code>ObjectWriter</code> - The uploading account will own the object if the object is uploaded with the <code>bucket-owner-full-control</code> canned ACL.</p>
/// <p><code>BucketOwnerEnforced</code> - Access control lists (ACLs) are disabled and no longer affect permissions. The bucket owner automatically owns and has full control over every object in the bucket. The bucket only accepts PUT requests that don't specify an ACL or specify bucket owner full control ACLs (such as the predefined <code>bucket-owner-full-control</code> canned ACL or a custom ACL in XML format that grants the same permissions).</p>
/// <p>By default, <code>ObjectOwnership</code> is set to <code>BucketOwnerEnforced</code> and ACLs are disabled. We recommend keeping ACLs disabled, except in uncommon use cases where you must control access for each object individually. For more information about S3 Object Ownership, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling ownership of objects and disabling ACLs for your bucket</a> in the <i>Amazon S3 User Guide</i>.</p><note>
/// <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>
/// </note>
pub fn get_object_ownership(&self) -> &::std::option::Option<crate::types::ObjectOwnership> {
&self.object_ownership
}
/// <p>Specifies the namespace where you want to create your general purpose bucket. When you create a general purpose bucket, you can choose to create a bucket in the shared global namespace or you can choose to create a bucket in your account regional namespace. Your account regional namespace is a subdivision of the global namespace that only your account can create buckets in. For more information on bucket namespaces, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/gpbucketnamespaces.html">Namespaces for general purpose buckets</a>.</p>
/// <p>General purpose buckets in your account regional namespace must follow a specific naming convention. These buckets consist of a bucket name prefix that you create, and a suffix that contains your 12-digit Amazon Web Services Account ID, the Amazon Web Services Region code, and ends with <code>-an</code>. Bucket names must follow the format <code>bucket-name-prefix-accountId-region-an</code> (for example, <code>amzn-s3-demo-bucket-111122223333-us-west-2-an</code>). For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html#account-regional-naming-rules">Account regional namespace naming rules</a> in the <i>Amazon S3 User Guide</i>.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn bucket_namespace(mut self, input: crate::types::BucketNamespace) -> Self {
self.bucket_namespace = ::std::option::Option::Some(input);
self
}
/// <p>Specifies the namespace where you want to create your general purpose bucket. When you create a general purpose bucket, you can choose to create a bucket in the shared global namespace or you can choose to create a bucket in your account regional namespace. Your account regional namespace is a subdivision of the global namespace that only your account can create buckets in. For more information on bucket namespaces, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/gpbucketnamespaces.html">Namespaces for general purpose buckets</a>.</p>
/// <p>General purpose buckets in your account regional namespace must follow a specific naming convention. These buckets consist of a bucket name prefix that you create, and a suffix that contains your 12-digit Amazon Web Services Account ID, the Amazon Web Services Region code, and ends with <code>-an</code>. Bucket names must follow the format <code>bucket-name-prefix-accountId-region-an</code> (for example, <code>amzn-s3-demo-bucket-111122223333-us-west-2-an</code>). For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html#account-regional-naming-rules">Account regional namespace naming rules</a> in the <i>Amazon S3 User Guide</i>.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn set_bucket_namespace(mut self, input: ::std::option::Option<crate::types::BucketNamespace>) -> Self {
self.bucket_namespace = input;
self
}
/// <p>Specifies the namespace where you want to create your general purpose bucket. When you create a general purpose bucket, you can choose to create a bucket in the shared global namespace or you can choose to create a bucket in your account regional namespace. Your account regional namespace is a subdivision of the global namespace that only your account can create buckets in. For more information on bucket namespaces, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/gpbucketnamespaces.html">Namespaces for general purpose buckets</a>.</p>
/// <p>General purpose buckets in your account regional namespace must follow a specific naming convention. These buckets consist of a bucket name prefix that you create, and a suffix that contains your 12-digit Amazon Web Services Account ID, the Amazon Web Services Region code, and ends with <code>-an</code>. Bucket names must follow the format <code>bucket-name-prefix-accountId-region-an</code> (for example, <code>amzn-s3-demo-bucket-111122223333-us-west-2-an</code>). For information about bucket naming restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html#account-regional-naming-rules">Account regional namespace naming rules</a> in the <i>Amazon S3 User Guide</i>.</p><note>
/// <p>This functionality is not supported for directory buckets.</p>
/// </note>
pub fn get_bucket_namespace(&self) -> &::std::option::Option<crate::types::BucketNamespace> {
&self.bucket_namespace
}
/// Consumes the builder and constructs a [`CreateBucketInput`](crate::operation::create_bucket::CreateBucketInput).
pub fn build(
self,
) -> ::std::result::Result<crate::operation::create_bucket::CreateBucketInput, ::aws_smithy_types::error::operation::BuildError> {
::std::result::Result::Ok(crate::operation::create_bucket::CreateBucketInput {
acl: self.acl,
bucket: self.bucket,
create_bucket_configuration: self.create_bucket_configuration,
grant_full_control: self.grant_full_control,
grant_read: self.grant_read,
grant_read_acp: self.grant_read_acp,
grant_write: self.grant_write,
grant_write_acp: self.grant_write_acp,
object_lock_enabled_for_bucket: self.object_lock_enabled_for_bucket,
object_ownership: self.object_ownership,
bucket_namespace: self.bucket_namespace,
})
}
}