Cannot set a BucketPolicy for storage

[AndreasEK]

How did you install the Amplify CLI?

No response

If applicable, what version of Node.js are you using?

v14.16.1

Amplify CLI Version

12.10.0

What operating system are you using?

Mac

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

I've added a BucketPolicy manually in the dev enviroment to see if this solves our problem. It does.

{
    "Version": "2012-10-17",
    "Id": "Policy1708334814278",
    "Statement": [
        {
            "Sid": "Stmt1708334806707",
            "Effect": "Allow",
            "Principal": "*",
            "Action": "s3:GetObject",
            "Resource": "arn:aws:s3:::solinger-sportbund-images-bucket-dev/*"
        }
    ]
}

Now I would like to transform that into the amplify backend

Describe the bug

We were using ACLs previously in order to manage access to objects. Since amplify-js v6 doesn't support ACLs any longer, I was expecting that BucketPolicies are supported. But they're not.

See:

• How to modify acl policy of a S3 file using v6? amplify-js#12626
• https://docs.aws.amazon.com/de_de/AWSCloudFormation/latest/UserGuide/aws-resource-s3-bucketpolicy.html

• amplify-cli/packages/amplify-cli-extensibility-helper/src/types/storage/types.ts

  Line 27 in d326176

  export interface AmplifyS3ResourceTemplate extends AmplifyCDKL1 {

Expected behavior

Either ACLs can be managed or a BucketPolicy can be set

Reproduction steps

…

Project Identifier

No response

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

[AndreasEK]

I was able to resolve this with an override as explained in the comment here:
aws-amplify/amplify-js#12626 (comment)

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.