From 58a46ae2a3a368ab80c15348ef55ff0d39427007 Mon Sep 17 00:00:00 2001 From: Irena Rindos Date: Fri, 22 Mar 2024 12:13:43 +0000 Subject: [PATCH] backport of commit d17356e1f74cf9d7e317a7add876c11a8967d2a8 --- .../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 35e7c78c17..188662373e 100644 --- a/website/content/docs/configuration/session-recording/create-storage-bucket.mdx +++ b/website/content/docs/configuration/session-recording/create-storage-bucket.mdx @@ -42,7 +42,7 @@ examples are provided to help with storage estimates: - Sending 50MB of data results in a BSR around 50.1MB in size. The storage requirements for 1,000 such sessions would be 50.1 GB. When you estimate worker storage requirements, consider the number of concurrent sessions that will be recorded on that worker. -A BSR is written to the worker's local storage while the session is active, and then moved to the remote storage bucket when the session is closed. +Boundary writes the BSR to the worker's local storage while the session is active, and then moves it to the remote storage bucket when the session is closed. When determining AWS storage requirements, consider your [storage policy](/boundary/docs/concepts/domain-model/storage-policy) and how long a BSR will be retained in the storage bucket.