You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although I don't understand why removing a resource would prevent access-denied errors, I think that specifying the bucket as a resource for the object actions (put/delete/get) doesn't make sense.
The text was updated successfully, but these errors were encountered:
Hello!
Thank you for this wonderful tool.
I set up a restrictive IAM policy as per the docs but when I started litestream I saw these Access Denied errors from S3:
The snapshot and WAL files seemed to be pushed to S3 correctly, as far as I could tell.
Anyway, when I adjusted the policy and restarted litestream, there were no more errors:
Although I don't understand why removing a resource would prevent access-denied errors, I think that specifying the bucket as a resource for the object actions (put/delete/get) doesn't make sense.
The text was updated successfully, but these errors were encountered: