In terms of NAS and self-hosting it means running those services yourself will almost always be more cost efficient than to buy into a managed cloud service. Not to mention that all cloud providers I know of follow a for profit business model. I would like my users to be able to upload an image, and after displaying the image on the app for everybody to see (very classical), so I'm just looking for the right way to do that, since the big alert on my S3 console seems to tell me that turning a bucket public is dangerous.On one hand cloud services offer convenience, on the other hand companies cash in on customers of those managed services.

I already try to put my users in a group with the access to the S3 bucket, but it was not working (I guess since the user don't really directly interact with my S3 bucket, it's my resolvers who do). So what is the right configuration to make the upload of an image work? I used Amazon Cognito userPool with Appsync and it's inside my resolvers that the image is upload to my S3 bucket if i understood correctly. With that done, everything works fine.īut I don't really understand why it's working, and Amazon show me a big and scary alert on my S3 console now saying 'We don't recommend at all to make a S3 bucket public'. I finally went to my S3 console, selected the right bucket, went to the Authorization tab, and clicked on 'Everyone' and finally selected 'Write Object'. I was stuck for a long time because of an error response 'Access Denied' when my image was uploading into the S3 bucket. I try and succeed to upload a file using AWS Amplify quick start doc and I used this example to set my graphql schema, my resolvers and dataSources correctly.

Syncthing aws s3