-
Notifications
You must be signed in to change notification settings - Fork 51
Document required S3 bucket policy #744
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Doing some trial-and-error, these actions seems to be required:
I've also added these:
I think it would make sense for Barman to utilize mutlipart uploads, but I'm not sure. Perhaps it does its own chunking and never requires large files? * I've not seen a delete operation first-hand, but everyone I've spoken to seems to agree that retention policy can delete objects. |
|
After a few rounds of discussions and comments, and some trial-and-error on my side, I think this is ready for review. I'm still not sure if actions for multi-part uploads are required or not. Maintainers help? |
|
I just ran into an error with multipart upload! It is required. I'll add it. Relevant docs: |
Signed-off-by: Andreas Lindhé <7773090+lindhe@users.noreply.github.com>
Signed-off-by: Andreas Lindhé <7773090+lindhe@users.noreply.github.com>
Signed-off-by: Andreas Lindhé <7773090+lindhe@users.noreply.github.com>
0a79751 to
313b5cc
Compare
|
Strange, I'm still seeing the same errors: EDIT: Oops, I had a typo in the username. 🙈 It works for me now, but I'm not 100% confident if the newly added permissions are strictly required or not anymore. |
This PR attempts to document the required S3 bucket policies required by the Barman Cloud plugin to work as intended.
Relevant documentation: