#403 error querying S3 Bucket - Setup using Amplify Studio

4 messages · Page 1 of 1 (latest)

oblique hound
#

I setup my data models, cognito / auth, and S3 bucket using Amplify, and now, as a logged in and authenticated user, I keep getting 403 errors when trying to perform a datastore query on my models. Operations that are clearly defined in the IAM policies for Auth users, but it still gives a 403 error.

I am trying to retrieve an image I am using on a component I made in Figma, I basically followed this tutorial: https://www.youtube.com/watch?v=OicGIaHxM-I

These 403 errors are very frustrating as they keep showing up for no reason; I set up everything through Amplify, tell it that Auth users are good to access, but it still doesn't work when logged in. These bugs are killing my development time as it is very difficult to diagnose since Amplify does so much hand wavy magic, I'm scared to do anything outside of Amplify since I don't know what the downstream effects will be.

This must be happening to more people and must be a prevalent bug, are there any current workarounds that don't involve drastic configuration outside of Amplify?

Frontend developers use AWS Amplify to quickly build and deploy web and mobile apps on AWS with a common backend. Amplify’s zero-configuration workflows help developers get started on AWS faster because they can easily configure robust backend capabilities for their apps. Backends can be extended to add capabilities from 175+ AWS services as use...

▶ Play video
oblique hound
#

Just confirmed I can retrieve my image by doing

#

But gives 403 error when using the Collection Component generated by Amplify UI

oblique hound
#

Seems that the request does not include any auth headers, looks like this is a bug or what?