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_output::CreateBucketOutputBuilder;
3
4pub use crate::operation::create_bucket::_create_bucket_input::CreateBucketInputBuilder;
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/// <important>
26/// <p>End of support notice: As of October 1, 2025, Amazon S3 has discontinued support for Email Grantee Access Control Lists (ACLs). If you attempt to use an Email Grantee ACL in a request after October 1, 2025, the request will receive an <code>HTTP 405</code> (Method Not Allowed) error.</p>
27/// <p>This change affects the following Amazon Web Services Regions: US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Ireland), and South America (São Paulo).</p>
28/// </important> <note>
29/// <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>
30/// </note>
31/// <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>
32/// <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><note>
33/// <ul>
34/// <li>
35/// <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>
36/// <li>
37/// <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>
38/// </ul>
39/// </note>
40/// <dl>
41/// <dt>
42/// Permissions
43/// </dt>
44/// <dd>
45/// <ul>
46/// <li>
47/// <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>
48/// <ul>
49/// <li>
50/// <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>
51/// <li>
52/// <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>
53/// <li>
54/// <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>
55/// <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>
56/// <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>
57/// </important></li>
58/// <li>
59/// <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>
60/// </ul></li>
61/// <li>
62/// <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>
63/// <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>
64/// <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>
65/// </important></li>
66/// </ul>
67/// </dd>
68/// <dt>
69/// HTTP Host header syntax
70/// </dt>
71/// <dd>
72/// <p><b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region-code</i>.amazonaws.com</code>.</p>
73/// </dd>
74/// </dl>
75/// <p>The following operations are related to <code>CreateBucket</code>:</p>
76/// <ul>
77/// <li>
78/// <p><a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html">PutObject</a></p></li>
79/// <li>
80/// <p><a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html">DeleteBucket</a></p></li>
81/// </ul><important>
82/// <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>
83/// </important>
84#[derive(::std::clone::Clone, ::std::fmt::Debug)]
85pub struct CreateBucketFluentBuilder {
86 handle: ::std::sync::Arc<crate::client::Handle>,
87 inner: crate::operation::create_bucket::builders::CreateBucketInputBuilder,
88 config_override: ::std::option::Option<crate::config::Builder>,
89}
90impl
91 crate::client::customize::internal::CustomizableSend<
92 crate::operation::create_bucket::CreateBucketOutput,
93 crate::operation::create_bucket::CreateBucketError,
94 > for CreateBucketFluentBuilder
95{
96 fn send(
97 self,
98 config_override: crate::config::Builder,
99 ) -> crate::client::customize::internal::BoxFuture<
100 crate::client::customize::internal::SendResult<
101 crate::operation::create_bucket::CreateBucketOutput,
102 crate::operation::create_bucket::CreateBucketError,
103 >,
104 > {
105 ::std::boxed::Box::pin(async move { self.config_override(config_override).send().await })
106 }
107}
108impl CreateBucketFluentBuilder {
109 /// Creates a new `CreateBucketFluentBuilder`.
110 pub(crate) fn new(handle: ::std::sync::Arc<crate::client::Handle>) -> Self {
111 Self {
112 handle,
113 inner: ::std::default::Default::default(),
114 config_override: ::std::option::Option::None,
115 }
116 }
117 /// Access the CreateBucket as a reference.
118 pub fn as_input(&self) -> &crate::operation::create_bucket::builders::CreateBucketInputBuilder {
119 &self.inner
120 }
121 /// Sends the request and returns the response.
122 ///
123 /// If an error occurs, an `SdkError` will be returned with additional details that
124 /// can be matched against.
125 ///
126 /// By default, any retryable failures will be retried twice. Retry behavior
127 /// is configurable with the [RetryConfig](aws_smithy_types::retry::RetryConfig), which can be
128 /// set when configuring the client.
129 pub async fn send(
130 self,
131 ) -> ::std::result::Result<
132 crate::operation::create_bucket::CreateBucketOutput,
133 ::aws_smithy_runtime_api::client::result::SdkError<
134 crate::operation::create_bucket::CreateBucketError,
135 ::aws_smithy_runtime_api::client::orchestrator::HttpResponse,
136 >,
137 > {
138 let input = self
139 .inner
140 .build()
141 .map_err(::aws_smithy_runtime_api::client::result::SdkError::construction_failure)?;
142 let runtime_plugins = crate::operation::create_bucket::CreateBucket::operation_runtime_plugins(
143 self.handle.runtime_plugins.clone(),
144 &self.handle.conf,
145 self.config_override,
146 );
147 crate::operation::create_bucket::CreateBucket::orchestrate(&runtime_plugins, input).await
148 }
149
150 /// Consumes this builder, creating a customizable operation that can be modified before being sent.
151 pub fn customize(
152 self,
153 ) -> crate::client::customize::CustomizableOperation<
154 crate::operation::create_bucket::CreateBucketOutput,
155 crate::operation::create_bucket::CreateBucketError,
156 Self,
157 > {
158 crate::client::customize::CustomizableOperation::new(self)
159 }
160 pub(crate) fn config_override(mut self, config_override: impl ::std::convert::Into<crate::config::Builder>) -> Self {
161 self.set_config_override(::std::option::Option::Some(config_override.into()));
162 self
163 }
164
165 pub(crate) fn set_config_override(&mut self, config_override: ::std::option::Option<crate::config::Builder>) -> &mut Self {
166 self.config_override = config_override;
167 self
168 }
169 /// <p>The canned ACL to apply to the bucket.</p><note>
170 /// <p>This functionality is not supported for directory buckets.</p>
171 /// </note>
172 pub fn acl(mut self, input: crate::types::BucketCannedAcl) -> Self {
173 self.inner = self.inner.acl(input);
174 self
175 }
176 /// <p>The canned ACL to apply to the bucket.</p><note>
177 /// <p>This functionality is not supported for directory buckets.</p>
178 /// </note>
179 pub fn set_acl(mut self, input: ::std::option::Option<crate::types::BucketCannedAcl>) -> Self {
180 self.inner = self.inner.set_acl(input);
181 self
182 }
183 /// <p>The canned ACL to apply to the bucket.</p><note>
184 /// <p>This functionality is not supported for directory buckets.</p>
185 /// </note>
186 pub fn get_acl(&self) -> &::std::option::Option<crate::types::BucketCannedAcl> {
187 self.inner.get_acl()
188 }
189 /// <p>The name of the bucket to create.</p>
190 /// <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>
191 /// <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>
192 pub fn bucket(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
193 self.inner = self.inner.bucket(input.into());
194 self
195 }
196 /// <p>The name of the bucket to create.</p>
197 /// <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>
198 /// <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>
199 pub fn set_bucket(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
200 self.inner = self.inner.set_bucket(input);
201 self
202 }
203 /// <p>The name of the bucket to create.</p>
204 /// <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>
205 /// <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>
206 pub fn get_bucket(&self) -> &::std::option::Option<::std::string::String> {
207 self.inner.get_bucket()
208 }
209 /// <p>The configuration information for the bucket.</p>
210 pub fn create_bucket_configuration(mut self, input: crate::types::CreateBucketConfiguration) -> Self {
211 self.inner = self.inner.create_bucket_configuration(input);
212 self
213 }
214 /// <p>The configuration information for the bucket.</p>
215 pub fn set_create_bucket_configuration(mut self, input: ::std::option::Option<crate::types::CreateBucketConfiguration>) -> Self {
216 self.inner = self.inner.set_create_bucket_configuration(input);
217 self
218 }
219 /// <p>The configuration information for the bucket.</p>
220 pub fn get_create_bucket_configuration(&self) -> &::std::option::Option<crate::types::CreateBucketConfiguration> {
221 self.inner.get_create_bucket_configuration()
222 }
223 /// <p>Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.</p><note>
224 /// <p>This functionality is not supported for directory buckets.</p>
225 /// </note>
226 pub fn grant_full_control(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
227 self.inner = self.inner.grant_full_control(input.into());
228 self
229 }
230 /// <p>Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.</p><note>
231 /// <p>This functionality is not supported for directory buckets.</p>
232 /// </note>
233 pub fn set_grant_full_control(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
234 self.inner = self.inner.set_grant_full_control(input);
235 self
236 }
237 /// <p>Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.</p><note>
238 /// <p>This functionality is not supported for directory buckets.</p>
239 /// </note>
240 pub fn get_grant_full_control(&self) -> &::std::option::Option<::std::string::String> {
241 self.inner.get_grant_full_control()
242 }
243 /// <p>Allows grantee to list the objects in the bucket.</p><note>
244 /// <p>This functionality is not supported for directory buckets.</p>
245 /// </note>
246 pub fn grant_read(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
247 self.inner = self.inner.grant_read(input.into());
248 self
249 }
250 /// <p>Allows grantee to list the objects in the bucket.</p><note>
251 /// <p>This functionality is not supported for directory buckets.</p>
252 /// </note>
253 pub fn set_grant_read(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
254 self.inner = self.inner.set_grant_read(input);
255 self
256 }
257 /// <p>Allows grantee to list the objects in the bucket.</p><note>
258 /// <p>This functionality is not supported for directory buckets.</p>
259 /// </note>
260 pub fn get_grant_read(&self) -> &::std::option::Option<::std::string::String> {
261 self.inner.get_grant_read()
262 }
263 /// <p>Allows grantee to read the bucket ACL.</p><note>
264 /// <p>This functionality is not supported for directory buckets.</p>
265 /// </note>
266 pub fn grant_read_acp(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
267 self.inner = self.inner.grant_read_acp(input.into());
268 self
269 }
270 /// <p>Allows grantee to read the bucket ACL.</p><note>
271 /// <p>This functionality is not supported for directory buckets.</p>
272 /// </note>
273 pub fn set_grant_read_acp(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
274 self.inner = self.inner.set_grant_read_acp(input);
275 self
276 }
277 /// <p>Allows grantee to read the bucket ACL.</p><note>
278 /// <p>This functionality is not supported for directory buckets.</p>
279 /// </note>
280 pub fn get_grant_read_acp(&self) -> &::std::option::Option<::std::string::String> {
281 self.inner.get_grant_read_acp()
282 }
283 /// <p>Allows grantee to create new objects in the bucket.</p>
284 /// <p>For the bucket and object owners of existing objects, also allows deletions and overwrites of those objects.</p><note>
285 /// <p>This functionality is not supported for directory buckets.</p>
286 /// </note>
287 pub fn grant_write(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
288 self.inner = self.inner.grant_write(input.into());
289 self
290 }
291 /// <p>Allows grantee to create new objects in the bucket.</p>
292 /// <p>For the bucket and object owners of existing objects, also allows deletions and overwrites of those objects.</p><note>
293 /// <p>This functionality is not supported for directory buckets.</p>
294 /// </note>
295 pub fn set_grant_write(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
296 self.inner = self.inner.set_grant_write(input);
297 self
298 }
299 /// <p>Allows grantee to create new objects in the bucket.</p>
300 /// <p>For the bucket and object owners of existing objects, also allows deletions and overwrites of those objects.</p><note>
301 /// <p>This functionality is not supported for directory buckets.</p>
302 /// </note>
303 pub fn get_grant_write(&self) -> &::std::option::Option<::std::string::String> {
304 self.inner.get_grant_write()
305 }
306 /// <p>Allows grantee to write the ACL for the applicable bucket.</p><note>
307 /// <p>This functionality is not supported for directory buckets.</p>
308 /// </note>
309 pub fn grant_write_acp(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
310 self.inner = self.inner.grant_write_acp(input.into());
311 self
312 }
313 /// <p>Allows grantee to write the ACL for the applicable bucket.</p><note>
314 /// <p>This functionality is not supported for directory buckets.</p>
315 /// </note>
316 pub fn set_grant_write_acp(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
317 self.inner = self.inner.set_grant_write_acp(input);
318 self
319 }
320 /// <p>Allows grantee to write the ACL for the applicable bucket.</p><note>
321 /// <p>This functionality is not supported for directory buckets.</p>
322 /// </note>
323 pub fn get_grant_write_acp(&self) -> &::std::option::Option<::std::string::String> {
324 self.inner.get_grant_write_acp()
325 }
326 /// <p>Specifies whether you want S3 Object Lock to be enabled for the new bucket.</p><note>
327 /// <p>This functionality is not supported for directory buckets.</p>
328 /// </note>
329 pub fn object_lock_enabled_for_bucket(mut self, input: bool) -> Self {
330 self.inner = self.inner.object_lock_enabled_for_bucket(input);
331 self
332 }
333 /// <p>Specifies whether you want S3 Object Lock to be enabled for the new bucket.</p><note>
334 /// <p>This functionality is not supported for directory buckets.</p>
335 /// </note>
336 pub fn set_object_lock_enabled_for_bucket(mut self, input: ::std::option::Option<bool>) -> Self {
337 self.inner = self.inner.set_object_lock_enabled_for_bucket(input);
338 self
339 }
340 /// <p>Specifies whether you want S3 Object Lock to be enabled for the new bucket.</p><note>
341 /// <p>This functionality is not supported for directory buckets.</p>
342 /// </note>
343 pub fn get_object_lock_enabled_for_bucket(&self) -> &::std::option::Option<bool> {
344 self.inner.get_object_lock_enabled_for_bucket()
345 }
346 /// <p>The container element for object ownership for a bucket's ownership controls.</p>
347 /// <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>
348 /// <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>
349 /// <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>
350 /// <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>
351 /// <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>
352 /// </note>
353 pub fn object_ownership(mut self, input: crate::types::ObjectOwnership) -> Self {
354 self.inner = self.inner.object_ownership(input);
355 self
356 }
357 /// <p>The container element for object ownership for a bucket's ownership controls.</p>
358 /// <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>
359 /// <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>
360 /// <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>
361 /// <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>
362 /// <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>
363 /// </note>
364 pub fn set_object_ownership(mut self, input: ::std::option::Option<crate::types::ObjectOwnership>) -> Self {
365 self.inner = self.inner.set_object_ownership(input);
366 self
367 }
368 /// <p>The container element for object ownership for a bucket's ownership controls.</p>
369 /// <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>
370 /// <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>
371 /// <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>
372 /// <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>
373 /// <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>
374 /// </note>
375 pub fn get_object_ownership(&self) -> &::std::option::Option<crate::types::ObjectOwnership> {
376 self.inner.get_object_ownership()
377 }
378}