Skip to content

Advise on bucket versioning #598

Open

Description

@miabonardi

We have bucket versioning disabled for some and enabled for others. Disabled is the default. What is the recommended selection here? I think this should be added to these notes. There is also the category of "default encryption" which is separate from "Block Public Access settings for this bucket" and might be helpful to say "stick to defaults except for ..."

https://github.com/SuffolkLITLab/legal-tech-class/blob/97b9d017241eab6aa82045ea77a2fd7810b40f46/docs/practical-guide-docassemble/setup-server.md?plain=1#L111-L121

Activity

  1. BryceStevenWilley commented on Oct 2, 2025

    @BryceStevenWilley
    Contributor

    i spent a lot of time this past month setting up S3 buckets, and my experience is that we should recommend bucket versioning, as long as they have a corresponding Lifecycle management rule that limits the number of older versions that S3 will save.

    Versioning is very helpful when starting and stopping the docker containers, in case an old or corrupted object is uploaded to S3, you can switch back to the last good version. The lifecycle rule is needed so the number of versions don't grow indefinitely.

  2. BryceStevenWilley commented on Mar 27, 2026

    @BryceStevenWilley
    Contributor

    This is in https://github.com/SuffolkLITLab/docassemble-AssemblyLine-documentation/blob/main/docs/admin_guide_docassemble/setup-server.md now. The suggestion to turn on bucket versioning is present now, but the instructions on Lifecycle management isn't yet. Still need to add that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

advancedGood issue for advanced DAL developers

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions