I'm trying to setup S3 for a new project and after following as much instructions as I could find the image attachment process still fails. When I try to add an image to a blog post, I select it from my local file system, the image appears for a moment in the perch UI and then just disappears. I understand that the upload to S3 fails. Could be permissions issue but can't be sure. And that's my question: Is there any place to look or any perch way to debug the problem?
I had a look at Amazon's troubleshooting guide and they suggest to check in dev tools. So I did and noticed no request to Amazon when I add images. I understand that the image is not even trying to leave Perch.
Have you added your access key to the runway.php config file?
If so, do you have another method to verify that the access key is working as intended?
I do have added the key.
I had a quick look to testing authentication and could only find some tutorials on doing it with the SDK which is outside my possibilities.
I have created an IAM user and attached the S3 full access policy. Then I use this user's credentials into runway.
I will focus today on testing my user if you don't find anything wrong in the diagnostics. then.
I just tried with the credentials of my original administration account but still same behaviour. I also gave all permissions to everybody in my S3 bucket.
A good test would be to use another S3 client (like a file transfer tool) with the same crews. Permissions on S3 aren't always the simplest thing to get right.
which happens to appear when a bucket is hosted in Frankfurt region. Apparently some extra configuration can solve the issue but in my case I preferred to move the bucket to Ireland and there it just works.