From d36f1e6dd8dba27f6d7eba0fd02f5811c00a7303 Mon Sep 17 00:00:00 2001 From: Irena Rindos Date: Fri, 22 Mar 2024 08:13:49 -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 188662373e..f5dbca389f 100644 --- a/website/content/docs/configuration/session-recording/create-storage-bucket.mdx +++ b/website/content/docs/configuration/session-recording/create-storage-bucket.mdx @@ -44,7 +44,7 @@ examples are provided to help with storage estimates: When you estimate worker storage requirements, consider the number of concurrent sessions that will be recorded on that worker. 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) +When you estimate 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. ### AWS requirements