From 80e3dde4068e131b33fe31ffe1431f068cbf10f8 Mon Sep 17 00:00:00 2001 From: Irena Rindos Date: Fri, 22 Mar 2024 08:13:27 -0400 Subject: [PATCH] Update website/content/docs/configuration/session-recording/create-storage-bucket.mdx Co-authored-by: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> --- .../configuration/session-recording/create-storage-bucket.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/configuration/session-recording/create-storage-bucket.mdx b/website/content/docs/configuration/session-recording/create-storage-bucket.mdx index aa4e66c5dd..34bb991997 100644 --- a/website/content/docs/configuration/session-recording/create-storage-bucket.mdx +++ b/website/content/docs/configuration/session-recording/create-storage-bucket.mdx @@ -34,7 +34,7 @@ transmitted between a user and a target during a single session. As a result, th activity. At a minimum, a BSR for a session with one connection requires 8KB of space for its files- this is the overhead for BSR keys, checksums, metadata, etc. -Determining how much storage you need to allocate on workers and AWS for recordings will depend on user activity, but the following two +Determining how much storage you need to allocate on workers and AWS for recordings depends on user activity, but the following two examples are provided to help with storage estimates: - For a minute of simple shell activity, a BSR can be around 20KB in size. The storage requirements for 1,000 such sessions would be 20MB.