pepie

It would be nice to be able to pass an auth token, for secured remote content. is this possible?

Thanks @Jordan-Nelson , That's what my actual code looks like. I simplified it for the sake of the ticket, because I get the same error regardless of my configuration. Upload...

Thanks for your patience, @Jordan-Nelson . I had four policies created. The first three were had a type of 'Customer Managed' and followed this naming convention `amplify--sandbox-< ID > -...

Here's the bucket policy that was generated ```{ "Version": "2012-10-17", "Statement": [ { "Effect": "Deny", "Principal": { "AWS": "*" }, "Action": "s3:*", "Resource": [ "arn:aws:s3:::amplify-backend-kio-sandbox-kiomediabucket< ID >", "arn:aws:s3:::amplify-backend-kio-sandbox-kiomediabucket< ID >/*"...

Yes, I mentioned this in the post. I changed "kio-media" to "media" to simplify the GitHub post, but all the paths configurations are set to 'kio-media'. I also noticed that...

Also, can you confirm your flutter amplify library version? I am using the latest version (2.2.0) for all, except for amplify_authenticator. ``` variables: amplify_version: &amplify_version 2.2.0 amplify_api: *amplify_version amplify_authenticator: ^2.1.0...

Lastly, the Sandbox deployment is successful. However, I do get the following warnings: ```current credentials could not be used to assume 'arn:aws:iam:::role/cdk--deploy-role--us-east-1', but are for the right account. Proceeding anyway....

> @pepie Okay, let me know if you still face issues after redeploying. > > I had used amplify flutter v2.1.0 as that was the latest available at the time....

Hey @Jordan-Nelson, I created a cleaned project and was able to upload an image successfully. I'll have to review my project to see the differences, but it seems this issue...

I finally figured out the issue, so adding some notes here in case others face similar issues. Summary: Uploads worked for unauthenticated users, but failed for authenticated users. The issue...