You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TASK: Authenticated users can upload images and read any other images uploaded by other users. users from the ADMINS group can delete/add images as well.
The getUrl() generated by owner who uploaded an image works. But other users from the same pool get
<Error>
<Code>AccessDenied</Code>
<Message>User: arn:aws:sts::123**** :assumed-role/amplify-*******/CognitoIdentityCredentials is not authorized to perform: s3:GetObject on resource: "arn:aws:s3:::amplify-******/images/a3dc5a20-b1ee-4a0a-af1c-44181a.jpg" because no identity-based policy allows the s3:GetObject action</Message>
<RequestId>A0MPX9T</RequestId>
<HostId>HzMuVeQTCA=</HostId>
</Error>
The problem might be with the attached to the bucket role, it has only [AWSLambdaBasicExecutionRole] attached. But the DOCs missing this configuration and it is not working by default
The text was updated successfully, but these errors were encountered:
Hey @myendorphin, thank you for reaching out. The issue appears to be similar to #1771 and is currently being tracked.
Closing this issue to prevent any miscommunication between issues, do add any information on your use case to enable us in mitigating this behavior.
Environment information
Description
https://docs.amplify.aws/vue/build-a-backend/storage/authorization/
All basic config as described in the docs
TASK: Authenticated users can upload images and read any other images uploaded by other users. users from the ADMINS group can delete/add images as well.
Config:
The getUrl() generated by owner who uploaded an image works. But other users from the same pool get
The Bucket policy:
The problem might be with the attached to the bucket role, it has only [AWSLambdaBasicExecutionRole] attached. But the DOCs missing this configuration and it is not working by default
The text was updated successfully, but these errors were encountered: