Wasn't able to reproduce this. ACL disabled + bucket owner enforced bucket is supposed to work in AWS console without any issues. How are you accessing the AWS console to account A's bucket? Is the URL "https://s3.console.aws.amazon.com/s3/buckets/BUCKET_NAME" ?
Correct, I use that URL to access it, btw I did some diging in CloudTrail and it shows that the successful API call from aws cli uses this header on the request: x-amz-acl:“bucket-owner-full-control”, but when I do it through the console on the browser that header is missing. Thanks.
I had this same issue. I found that having "s3:GetBucketOwnershipControls" permissions on the bucket allowed the console upload to work. I assume that by allowing the console to see that bucket owner ownership is enforced it doesn't try to use an ACL, which previously caused the upload failures.
S3 upload issues through the AWS consoleasked 9 months ago
Allowing permission to Generate a policy based on CloudTrail events where the selected Trail logs events in an S3 bucket in another accountAccepted Answerasked 4 months ago
Make object that upload by account-b role public in account-a bucketAccepted Answerasked 3 years ago
Can i still upload files to S3 using the AWS SDK when i restrict access with an CloudFront distribution?Accepted Answerasked a year ago
Where can I found the uri of my Bucket to connect my Symfony application with S3 and upload files?asked 8 months ago
AWS: s3 bucket policy does not give IAM user access to upload to bucket, throws 403 errorasked 10 months ago
S3 bucket ownerasked 3 years ago
Multi-account CloudTrail S3 object ownershipAccepted Answerasked 2 years ago
Access denied when trying to GET objects uploaded to s3 bucket via aws sdk using cloudfrontAccepted Answerasked a year ago
S3 Static Website Objects 403 Forbidden when Uploaded from Different Accountasked 7 months ago