[Bug]: Incorrect AWS S3 permissions causes opaque error
codebutler opened this issue · comments
What happened?
Preevy failed with "403: UnknownError" with no indication the problem was related to AWS/S3.
Add screenshots
Steps to reproduce the behavior
Use an AWS role that is missing required permissions.
Expected behavior
The error message should mention the problem happened when trying to access a preevy profile on S3, and should specifically say which S3 API failed.
In my case the role did have access to s3.GetObject, but was missing s3.HeadBucket.
What OS are you seeing the problem on?
Linux
Additional context
No response
Record
- I agree to follow this project's Code of Conduct