[
https://issues.apache.org/jira/browse/HADOOP-18685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707295#comment-17707295
]
Daniel Carl Jones commented on HADOOP-18685:
--------------------------------------------
# When it fails, I believe we get some kind of bad request or no permission
test failure. I don't have a result handy ATM.
# You can make a call to GetBucketOwnershipControls, although its not plumbed
into S3A at the moment. Are you thinking to auto-skip the tests or something
along the lines of a path capability probe?
https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketOwnershipControls.html#API_GetBucketOwnershipControls_ResponseSyntax
> Amazon S3 disabling ACLs on all new buckets
> -------------------------------------------
>
> Key: HADOOP-18685
> URL: https://issues.apache.org/jira/browse/HADOOP-18685
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Daniel Carl Jones
> Priority: Minor
>
> In April 2023, Amazon S3 will be disabling ACLs by default on *all* new
> buckets.
> [https://aws.amazon.com/blogs/aws/heads-up-amazon-s3-security-changes-are-coming-in-april-of-2023/.|https://aws.amazon.com/blogs/aws/heads-up-amazon-s3-security-changes-are-coming-in-april-of-2023/]
> Note, buckets created using the AWS Console are already created with ACLs
> disabled by default.
> In S3A, we have tests that rely on ACLs being enabled. We should either
> update test documentation to tell developers to enable ACLs on buckets, or we
> should make the ACL tests opt-in if they are used infrequently by S3A users.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
