[aws-s3] Bucket OwnershipControls Support
See original GitHub issueSupport new Bucket Ownership Controls to ensure bucket owner owns all objects in the bucket
Use Case
https://docs.aws.amazon.com/AmazonS3/latest/user-guide/add-object-ownership.html
Ensure proper object ownership after cross account writes
Proposed Solution
cdk.Bucket
to support passing ownershipControls
to CfnBucket
Other
- 👋 I may be able to implement this feature request
- ⚠️ This feature might incur a breaking change
This is a 🚀 Feature Request
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
S3::Bucket OwnershipControls - AWS CloudFormation
Specifies the container element for Object Ownership rules. S3 Object Ownership is an Amazon S3 bucket-level setting that you can use to disable...
Read more >put-bucket-ownership-controls — AWS CLI 2.9.9 Command ...
Creates or modifies OwnershipControls for an Amazon S3 bucket. To use this operation, you must have the s3:PutBucketOwnershipControls permission.
Read more >AWS Amazon S3 Bucket Ownership Controls - Shisho Cloud
AWS Amazon S3 Bucket Ownership Controls is a resource for Amazon S3 of Amazon Web Service. Settings can be wrote in Terraform and...
Read more >aws.s3.BucketOwnershipControls - Pulumi
aws.s3.BucketOwnershipControls. Provides a resource to manage S3 Bucket Ownership Controls. For more information, see the S3 Developer Guide.
Read more >amazon.aws.s3_bucket module – Manage S3 buckets in AWS ...
Bucket Key encryption is only supported if encryption=aws:kms. Choices: false. true. ceph. aliases: rgw. boolean ... Delete bucket's ownership controls.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m not sure of the use case but I’d vote to retain the array to allow for such use cases now or in the future when those uses cases might reveal themselves:
Approach 2 looks cleaner to me
I know CloudFormation supports a list of rules but what is the use case for more than one rule?