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.

Sign up for GitHub

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

Added S3 storage guidance for Legal Holds #7727

Merged
merged 2 commits into from
Feb 7, 2025
Merged

Added S3 storage guidance for Legal Holds #7727

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0cbbf98
Added S3 storage guidance
cwarnermm Feb 4, 2025
4410037
Incorporated reviewer feedback
cwarnermm Feb 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion source/comply/legal-hold.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,4 +173,11 @@ Legal Hold is an initial step to ensure relevant electronically stored informati
How do I enable e-discovery for Mattermost?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Learn more about extracting data for e-discovery in our :doc:`product documentation </comply/electronic-discovery>`.
Learn more about extracting data for e-discovery in our :doc:`product documentation </comply/electronic-discovery>`.

How do I manage storage costs and version retention in S3?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If you plan to use an existing S3 bucket for Legal Hold data storage, and your existing S3 bucket has versioning enabled, we strongly recommend using a dedicated S3 bucket with versioning disabled.

The Legal Hold plugin frequently modifies files in the ``legalhold`` directory, and when S3 bucket versioning is enabled, each modification creates a new version. This can result in a rapid accumulation of object versions, increased storage costs, potential performance impact, higher S3 API usage, and complicating version management over time. See the `S3 Lifecycle Rules <https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html>`_ documentation for additional details.