Skip to content
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

Document S3 retention levels/required permissions #199

Open
1 task
mdedetrich opened this issue Apr 14, 2022 · 0 comments
Open
1 task

Document S3 retention levels/required permissions #199

mdedetrich opened this issue Apr 14, 2022 · 0 comments
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers s3 Specifically related to Amazon's S3 storage backend

Comments

@mdedetrich
Copy link
Collaborator

mdedetrich commented Apr 14, 2022

What is currently missing?

When using the S3 storage engine we should document what permissions are needed for S3 accounts that Guardian.

How could this be improved?

Since Guardian uses non typical parts of the S3 API which need extra permissions, i.e. ListParts) this needs to be documented since it can come off as a surprise.

Also retention levels for uploaded parts with multipart uploads also need to be documented, i.e. if the retention level of your multipart upload is lower than the configured timeslice you will get problems since the parts will disappear before they get completed.

Is this a feature you would work on yourself?

  • I plan to open a pull request for this feature
@mdedetrich mdedetrich added documentation Improvements or additions to documentation good first issue Good for newcomers labels Apr 14, 2022
@mdedetrich mdedetrich added the s3 Specifically related to Amazon's S3 storage backend label May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers s3 Specifically related to Amazon's S3 storage backend
Projects
None yet
Development

No branches or pull requests

1 participant