aws_sdk_s3/operation/create_bucket/builders.rs
1// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
2pub use crate::operation::create_bucket::_create_bucket_input::CreateBucketInputBuilder;
3
4pub use crate::operation::create_bucket::_create_bucket_output::CreateBucketOutputBuilder;
5
6impl crate::operation::create_bucket::builders::CreateBucketInputBuilder {
7 /// Sends a request with this input using the given client.
8 pub async fn send_with(
9 self,
10 client: &crate::Client,
11 ) -> ::std::result::Result<
12 crate::operation::create_bucket::CreateBucketOutput,
13 ::aws_smithy_runtime_api::client::result::SdkError<
14 crate::operation::create_bucket::CreateBucketError,
15 ::aws_smithy_runtime_api::client::orchestrator::HttpResponse,
16 >,
17 > {
18 let mut fluent_builder = client.create_bucket();
19 fluent_builder.inner = self;
20 fluent_builder.send().await
21 }
22}
23/// Fluent builder constructing a request to `CreateBucket`.
24///
25/// <note>
26/// <p>This action creates an Amazon S3 bucket. To create an Amazon S3 on Outposts bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_control_CreateBucket.html"> <code>CreateBucket</code> </a>.</p>
27/// </note>
28/// <p>Creates a new S3 bucket. To create a bucket, you must set up Amazon S3 and have a valid Amazon Web Services Access Key ID to authenticate requests. Anonymous requests are never allowed to create buckets. By creating the bucket, you become the bucket owner.</p>
29/// <p>There are two types of buckets: general purpose buckets and directory buckets. For more information about these bucket types, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html">Creating, configuring, and working with Amazon S3 buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
30/// <p>General purpose buckets exist in a global namespace, which means that each bucket name must be unique across all Amazon Web Services accounts in all the Amazon Web Services Regions within a partition. A partition is a grouping of Regions. Amazon Web Services currently has four partitions: <code>aws</code> (Standard Regions), <code>aws-cn</code> (China Regions), <code>aws-us-gov</code> (Amazon Web Services GovCloud (US)), and <code>aws-eusc</code> (European Sovereign Cloud). 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 account regional namespaces, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/gpbucketnamespaces.html">Namespaces for general purpose buckets</a>.</p><note>
31/// <ul>
32/// <li>
33/// <p><b>General purpose buckets</b> - If you send your <code>CreateBucket</code> request to the <code>s3.amazonaws.com</code> global endpoint, the request goes to the <code>us-east-1</code> Region. So the signature calculations in Signature Version 4 must use <code>us-east-1</code> as the Region, even if the location constraint in the request specifies another Region where the bucket is to be created. If you create a bucket in a Region other than US East (N. Virginia), your application must be able to handle 307 redirect. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html">Virtual hosting of buckets</a> in the <i>Amazon S3 User Guide</i>.</p></li>
34/// <li>
35/// <p><b>Directory buckets </b> - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support 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. For more information about endpoints in Availability Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/endpoint-directory-buckets-AZ.html">Regional and Zonal endpoints for directory buckets in Availability Zones</a> in the <i>Amazon S3 User Guide</i>. For more information about endpoints in Local Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-lzs-for-directory-buckets.html">Concepts for directory buckets in Local Zones</a> in the <i>Amazon S3 User Guide</i>.</p></li>
36/// </ul>
37/// </note>
38/// <dl>
39/// <dt>
40/// Permissions
41/// </dt>
42/// <dd>
43/// <ul>
44/// <li>
45/// <p><b>General purpose bucket permissions</b> - In addition to the <code>s3:CreateBucket</code> permission, the following permissions are required in a policy when your <code>CreateBucket</code> request includes specific headers:</p>
46/// <ul>
47/// <li>
48/// <p><b>Access control lists (ACLs)</b> - In your <code>CreateBucket</code> request, if you specify an access control list (ACL) and set it to <code>public-read</code>, <code>public-read-write</code>, <code>authenticated-read</code>, or if you explicitly specify any other custom ACLs, both <code>s3:CreateBucket</code> and <code>s3:PutBucketAcl</code> permissions are required. In your <code>CreateBucket</code> request, if you set the ACL to <code>private</code>, or if you don't specify any ACLs, only the <code>s3:CreateBucket</code> permission is required.</p></li>
49/// <li>
50/// <p><b>Object Lock</b> - In your <code>CreateBucket</code> request, if you set <code>x-amz-bucket-object-lock-enabled</code> to true, the <code>s3:PutBucketObjectLockConfiguration</code> and <code>s3:PutBucketVersioning</code> permissions are required.</p></li>
51/// <li>
52/// <p><b>S3 Object Ownership</b> - If your <code>CreateBucket</code> request includes the <code>x-amz-object-ownership</code> header, then the <code>s3:PutBucketOwnershipControls</code> permission is required.</p><important>
53/// <p>To set an ACL on a bucket as part of a <code>CreateBucket</code> request, you must explicitly set S3 Object Ownership for the bucket to a different value than the default, <code>BucketOwnerEnforced</code>. Additionally, if your desired bucket ACL grants public access, you must first create the bucket (without the bucket ACL) and then explicitly disable Block Public Access on the bucket before using <code>PutBucketAcl</code> to set the ACL. If you try to create a bucket with a public ACL, the request will fail.</p>
54/// <p>For the majority of modern use cases in S3, we recommend that you keep all Block Public Access settings enabled and keep ACLs disabled. If you would like to share data with users outside of your account, you can use bucket policies as needed. For more information, 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> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html">Blocking public access to your Amazon S3 storage </a> in the <i>Amazon S3 User Guide</i>.</p>
55/// </important></li>
56/// <li>
57/// <p><b>S3 Block Public Access</b> - If your specific use case requires granting public access to your S3 resources, you can disable Block Public Access. Specifically, you can create a new bucket with Block Public Access enabled, then separately call the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeletePublicAccessBlock.html"> <code>DeletePublicAccessBlock</code> </a> API. To use this operation, you must have the <code>s3:PutBucketPublicAccessBlock</code> permission. For more information about S3 Block Public Access, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html">Blocking public access to your Amazon S3 storage </a> in the <i>Amazon S3 User Guide</i>.</p></li>
58/// </ul></li>
59/// <li>
60/// <p><b>Directory bucket permissions</b> - You must have the <code>s3express:CreateBucket</code> permission in an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource. For more information about directory bucket policies and permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam.html">Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p><important>
61/// <p>The permissions for ACLs, Object Lock, S3 Object Ownership, and S3 Block Public Access are not supported for directory buckets. For directory buckets, all Block Public Access settings are enabled at the bucket level and S3 Object Ownership is set to Bucket owner enforced (ACLs disabled). These settings can't be modified.</p>
62/// <p>For more information about permissions for creating and working with directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html">Directory buckets</a> in the <i>Amazon S3 User Guide</i>. For more information about supported S3 features for directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-one-zone.html#s3-express-features">Features of S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
63/// </important></li>
64/// </ul>
65/// </dd>
66/// <dt>
67/// HTTP Host header syntax
68/// </dt>
69/// <dd>
70/// <p><b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region-code</i>.amazonaws.com</code>.</p>
71/// </dd>
72/// </dl>
73/// <p>The following operations are related to <code>CreateBucket</code>:</p>
74/// <ul>
75/// <li>
76/// <p><a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html">PutObject</a></p></li>
77/// <li>
78/// <p><a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html">DeleteBucket</a></p></li>
79/// </ul><important>
80/// <p>You must URL encode any signed header values that contain spaces. For example, if your header value is <code>my file.txt</code>, containing two spaces after <code>my</code>, you must URL encode this value to <code>my%20%20file.txt</code>.</p>
81/// </important>
82#[derive(::std::clone::Clone, ::std::fmt::Debug)]
83pub struct CreateBucketFluentBuilder {
84 handle: ::std::sync::Arc<crate::client::Handle>,
85 inner: crate::operation::create_bucket::builders::CreateBucketInputBuilder,
86 config_override: ::std::option::Option<crate::config::Builder>,
87}
88impl
89 crate::client::customize::internal::CustomizableSend<
90 crate::operation::create_bucket::CreateBucketOutput,
91 crate::operation::create_bucket::CreateBucketError,
92 > for CreateBucketFluentBuilder
93{
94 fn send(
95 self,
96 config_override: crate::config::Builder,
97 ) -> crate::client::customize::internal::BoxFuture<
98 crate::client::customize::internal::SendResult<
99 crate::operation::create_bucket::CreateBucketOutput,
100 crate::operation::create_bucket::CreateBucketError,
101 >,
102 > {
103 ::std::boxed::Box::pin(async move { self.config_override(config_override).send().await })
104 }
105}
106impl CreateBucketFluentBuilder {
107 /// Creates a new `CreateBucketFluentBuilder`.
108 pub(crate) fn new(handle: ::std::sync::Arc<crate::client::Handle>) -> Self {
109 Self {
110 handle,
111 inner: ::std::default::Default::default(),
112 config_override: ::std::option::Option::None,
113 }
114 }
115 /// Access the CreateBucket as a reference.
116 pub fn as_input(&self) -> &crate::operation::create_bucket::builders::CreateBucketInputBuilder {
117 &self.inner
118 }
119 /// Sends the request and returns the response.
120 ///
121 /// If an error occurs, an `SdkError` will be returned with additional details that
122 /// can be matched against.
123 ///
124 /// By default, any retryable failures will be retried twice. Retry behavior
125 /// is configurable with the [RetryConfig](aws_smithy_types::retry::RetryConfig), which can be
126 /// set when configuring the client.
127 pub async fn send(
128 self,
129 ) -> ::std::result::Result<
130 crate::operation::create_bucket::CreateBucketOutput,
131 ::aws_smithy_runtime_api::client::result::SdkError<
132 crate::operation::create_bucket::CreateBucketError,
133 ::aws_smithy_runtime_api::client::orchestrator::HttpResponse,
134 >,
135 > {
136 let input = self
137 .inner
138 .build()
139 .map_err(::aws_smithy_runtime_api::client::result::SdkError::construction_failure)?;
140 let runtime_plugins = crate::operation::create_bucket::CreateBucket::operation_runtime_plugins(
141 self.handle.runtime_plugins.clone(),
142 &self.handle.conf,
143 self.config_override,
144 );
145 crate::operation::create_bucket::CreateBucket::orchestrate(&runtime_plugins, input).await
146 }
147
148 /// Consumes this builder, creating a customizable operation that can be modified before being sent.
149 pub fn customize(
150 self,
151 ) -> crate::client::customize::CustomizableOperation<
152 crate::operation::create_bucket::CreateBucketOutput,
153 crate::operation::create_bucket::CreateBucketError,
154 Self,
155 > {
156 crate::client::customize::CustomizableOperation::new(self)
157 }
158 pub(crate) fn config_override(mut self, config_override: impl ::std::convert::Into<crate::config::Builder>) -> Self {
159 self.set_config_override(::std::option::Option::Some(config_override.into()));
160 self
161 }
162
163 pub(crate) fn set_config_override(&mut self, config_override: ::std::option::Option<crate::config::Builder>) -> &mut Self {
164 self.config_override = config_override;
165 self
166 }
167 /// <p>The canned ACL to apply to the bucket.</p><note>
168 /// <p>This functionality is not supported for directory buckets.</p>
169 /// </note>
170 pub fn acl(mut self, input: crate::types::BucketCannedAcl) -> Self {
171 self.inner = self.inner.acl(input);
172 self
173 }
174 /// <p>The canned ACL to apply to the bucket.</p><note>
175 /// <p>This functionality is not supported for directory buckets.</p>
176 /// </note>
177 pub fn set_acl(mut self, input: ::std::option::Option<crate::types::BucketCannedAcl>) -> Self {
178 self.inner = self.inner.set_acl(input);
179 self
180 }
181 /// <p>The canned ACL to apply to the bucket.</p><note>
182 /// <p>This functionality is not supported for directory buckets.</p>
183 /// </note>
184 pub fn get_acl(&self) -> &::std::option::Option<crate::types::BucketCannedAcl> {
185 self.inner.get_acl()
186 }
187 /// <p>The name of the bucket to create.</p>
188 /// <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>
189 /// <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>
190 pub fn bucket(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
191 self.inner = self.inner.bucket(input.into());
192 self
193 }
194 /// <p>The name of the bucket to create.</p>
195 /// <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>
196 /// <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>
197 pub fn set_bucket(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
198 self.inner = self.inner.set_bucket(input);
199 self
200 }
201 /// <p>The name of the bucket to create.</p>
202 /// <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>
203 /// <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>
204 pub fn get_bucket(&self) -> &::std::option::Option<::std::string::String> {
205 self.inner.get_bucket()
206 }
207 /// <p>The configuration information for the bucket.</p>
208 pub fn create_bucket_configuration(mut self, input: crate::types::CreateBucketConfiguration) -> Self {
209 self.inner = self.inner.create_bucket_configuration(input);
210 self
211 }
212 /// <p>The configuration information for the bucket.</p>
213 pub fn set_create_bucket_configuration(mut self, input: ::std::option::Option<crate::types::CreateBucketConfiguration>) -> Self {
214 self.inner = self.inner.set_create_bucket_configuration(input);
215 self
216 }
217 /// <p>The configuration information for the bucket.</p>
218 pub fn get_create_bucket_configuration(&self) -> &::std::option::Option<crate::types::CreateBucketConfiguration> {
219 self.inner.get_create_bucket_configuration()
220 }
221 /// <p>Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.</p><note>
222 /// <p>This functionality is not supported for directory buckets.</p>
223 /// </note>
224 pub fn grant_full_control(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
225 self.inner = self.inner.grant_full_control(input.into());
226 self
227 }
228 /// <p>Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.</p><note>
229 /// <p>This functionality is not supported for directory buckets.</p>
230 /// </note>
231 pub fn set_grant_full_control(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
232 self.inner = self.inner.set_grant_full_control(input);
233 self
234 }
235 /// <p>Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.</p><note>
236 /// <p>This functionality is not supported for directory buckets.</p>
237 /// </note>
238 pub fn get_grant_full_control(&self) -> &::std::option::Option<::std::string::String> {
239 self.inner.get_grant_full_control()
240 }
241 /// <p>Allows grantee to list the objects in the bucket.</p><note>
242 /// <p>This functionality is not supported for directory buckets.</p>
243 /// </note>
244 pub fn grant_read(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
245 self.inner = self.inner.grant_read(input.into());
246 self
247 }
248 /// <p>Allows grantee to list the objects in the bucket.</p><note>
249 /// <p>This functionality is not supported for directory buckets.</p>
250 /// </note>
251 pub fn set_grant_read(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
252 self.inner = self.inner.set_grant_read(input);
253 self
254 }
255 /// <p>Allows grantee to list the objects in the bucket.</p><note>
256 /// <p>This functionality is not supported for directory buckets.</p>
257 /// </note>
258 pub fn get_grant_read(&self) -> &::std::option::Option<::std::string::String> {
259 self.inner.get_grant_read()
260 }
261 /// <p>Allows grantee to read the bucket ACL.</p><note>
262 /// <p>This functionality is not supported for directory buckets.</p>
263 /// </note>
264 pub fn grant_read_acp(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
265 self.inner = self.inner.grant_read_acp(input.into());
266 self
267 }
268 /// <p>Allows grantee to read the bucket ACL.</p><note>
269 /// <p>This functionality is not supported for directory buckets.</p>
270 /// </note>
271 pub fn set_grant_read_acp(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
272 self.inner = self.inner.set_grant_read_acp(input);
273 self
274 }
275 /// <p>Allows grantee to read the bucket ACL.</p><note>
276 /// <p>This functionality is not supported for directory buckets.</p>
277 /// </note>
278 pub fn get_grant_read_acp(&self) -> &::std::option::Option<::std::string::String> {
279 self.inner.get_grant_read_acp()
280 }
281 /// <p>Allows grantee to create new objects in the bucket.</p>
282 /// <p>For the bucket and object owners of existing objects, also allows deletions and overwrites of those objects.</p><note>
283 /// <p>This functionality is not supported for directory buckets.</p>
284 /// </note>
285 pub fn grant_write(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
286 self.inner = self.inner.grant_write(input.into());
287 self
288 }
289 /// <p>Allows grantee to create new objects in the bucket.</p>
290 /// <p>For the bucket and object owners of existing objects, also allows deletions and overwrites of those objects.</p><note>
291 /// <p>This functionality is not supported for directory buckets.</p>
292 /// </note>
293 pub fn set_grant_write(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
294 self.inner = self.inner.set_grant_write(input);
295 self
296 }
297 /// <p>Allows grantee to create new objects in the bucket.</p>
298 /// <p>For the bucket and object owners of existing objects, also allows deletions and overwrites of those objects.</p><note>
299 /// <p>This functionality is not supported for directory buckets.</p>
300 /// </note>
301 pub fn get_grant_write(&self) -> &::std::option::Option<::std::string::String> {
302 self.inner.get_grant_write()
303 }
304 /// <p>Allows grantee to write the ACL for the applicable bucket.</p><note>
305 /// <p>This functionality is not supported for directory buckets.</p>
306 /// </note>
307 pub fn grant_write_acp(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
308 self.inner = self.inner.grant_write_acp(input.into());
309 self
310 }
311 /// <p>Allows grantee to write the ACL for the applicable bucket.</p><note>
312 /// <p>This functionality is not supported for directory buckets.</p>
313 /// </note>
314 pub fn set_grant_write_acp(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
315 self.inner = self.inner.set_grant_write_acp(input);
316 self
317 }
318 /// <p>Allows grantee to write the ACL for the applicable bucket.</p><note>
319 /// <p>This functionality is not supported for directory buckets.</p>
320 /// </note>
321 pub fn get_grant_write_acp(&self) -> &::std::option::Option<::std::string::String> {
322 self.inner.get_grant_write_acp()
323 }
324 /// <p>Specifies whether you want S3 Object Lock to be enabled for the new bucket.</p><note>
325 /// <p>This functionality is not supported for directory buckets.</p>
326 /// </note>
327 pub fn object_lock_enabled_for_bucket(mut self, input: bool) -> Self {
328 self.inner = self.inner.object_lock_enabled_for_bucket(input);
329 self
330 }
331 /// <p>Specifies whether you want S3 Object Lock to be enabled for the new bucket.</p><note>
332 /// <p>This functionality is not supported for directory buckets.</p>
333 /// </note>
334 pub fn set_object_lock_enabled_for_bucket(mut self, input: ::std::option::Option<bool>) -> Self {
335 self.inner = self.inner.set_object_lock_enabled_for_bucket(input);
336 self
337 }
338 /// <p>Specifies whether you want S3 Object Lock to be enabled for the new bucket.</p><note>
339 /// <p>This functionality is not supported for directory buckets.</p>
340 /// </note>
341 pub fn get_object_lock_enabled_for_bucket(&self) -> &::std::option::Option<bool> {
342 self.inner.get_object_lock_enabled_for_bucket()
343 }
344 /// <p>The container element for object ownership for a bucket's ownership controls.</p>
345 /// <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>
346 /// <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>
347 /// <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>
348 /// <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>
349 /// <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>
350 /// </note>
351 pub fn object_ownership(mut self, input: crate::types::ObjectOwnership) -> Self {
352 self.inner = self.inner.object_ownership(input);
353 self
354 }
355 /// <p>The container element for object ownership for a bucket's ownership controls.</p>
356 /// <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>
357 /// <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>
358 /// <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>
359 /// <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>
360 /// <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>
361 /// </note>
362 pub fn set_object_ownership(mut self, input: ::std::option::Option<crate::types::ObjectOwnership>) -> Self {
363 self.inner = self.inner.set_object_ownership(input);
364 self
365 }
366 /// <p>The container element for object ownership for a bucket's ownership controls.</p>
367 /// <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>
368 /// <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>
369 /// <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>
370 /// <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>
371 /// <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>
372 /// </note>
373 pub fn get_object_ownership(&self) -> &::std::option::Option<crate::types::ObjectOwnership> {
374 self.inner.get_object_ownership()
375 }
376 /// <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>
377 /// <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>
378 /// <p>This functionality is not supported for directory buckets.</p>
379 /// </note>
380 pub fn bucket_namespace(mut self, input: crate::types::BucketNamespace) -> Self {
381 self.inner = self.inner.bucket_namespace(input);
382 self
383 }
384 /// <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>
385 /// <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>
386 /// <p>This functionality is not supported for directory buckets.</p>
387 /// </note>
388 pub fn set_bucket_namespace(mut self, input: ::std::option::Option<crate::types::BucketNamespace>) -> Self {
389 self.inner = self.inner.set_bucket_namespace(input);
390 self
391 }
392 /// <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>
393 /// <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>
394 /// <p>This functionality is not supported for directory buckets.</p>
395 /// </note>
396 pub fn get_bucket_namespace(&self) -> &::std::option::Option<crate::types::BucketNamespace> {
397 self.inner.get_bucket_namespace()
398 }
399}