docs: Clarify session recording storage limitation #1467
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Vercel Previews Deployed
|
Contributor
Broken Link CheckerNo broken links found! 🎉 |
irenarindos
reviewed
Dec 5, 2025
content/boundary/v0.20.x/content/docs/session-recording/index.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Irena Rindos <irenarindos@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per SPE-1384, the Storage considerations section in the session recording overview topic mentions a 5GB limit for recorded session files. The documentation makes it sound like this is a limit we impose for Boundary, but it is actually a limit at the Amazon S3 level. The limit does not exist for MinIO or other potential vendors.
This PR clarifies the Warning admonition in the section above to make it clear that the 5GB limitation only applies when using the Amazon S3 backend.
View the update in the preview deployment