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

Use S3 "object lock" for objects in published versions #1862

Open
waxlamp opened this issue Feb 8, 2024 · 0 comments
Open

Use S3 "object lock" for objects in published versions #1862

waxlamp opened this issue Feb 8, 2024 · 0 comments
Labels
maintenance Action to maintain the system (neither a bugfix nor an enhancement)

Comments

@waxlamp
Copy link
Member

waxlamp commented Feb 8, 2024

This would be an S3-level protection against accidental deletion of objects that are part of published version (and thus generally should not be deleted).

https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html

The "legal hold" mechanism seems to be what we would want:

You can use Legal Hold when you are not sure for how long you want your objects to stay immutable. This could be because you have an upcoming external audit of your data and want to keep objects immutable till the audit is complete. Alternately, you may have an ongoing project utilizing a dataset that you want to keep immutable until the project is complete.

@waxlamp waxlamp added the maintenance Action to maintain the system (neither a bugfix nor an enhancement) label Feb 21, 2024
@waxlamp waxlamp changed the title Evaluate S3 "object lock" for objects in published versions Use S3 "object lock" for objects in published versions Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Action to maintain the system (neither a bugfix nor an enhancement)
Projects
None yet
Development

No branches or pull requests

1 participant