Append-only bucket permissions #1002
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind/experimental
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
admin-sdk
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#1002
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'd like to be able to issue "append-only" access tokens to a bucket where only non-destructive write options are allowed. For example DeleteObject requests would be denied and PutObject requests which overwrite existing objects would fail. The usecase is for a shared content-addressed backup storage where machines can backup independently in parallel to the same bucket, but if one machine is compromised it shouldn't be able to delete or overwrite any existing blocks. Backup pruning then takes place on the same machine hosting garage, reducing attack surface to the minimum. Object versioning would also solve this usecase, but that feature has a larger scope.