From 64a0ea91119fa0733b38b86cefe12d1448cb80d0 Mon Sep 17 00:00:00 2001 From: Robin Beck Date: Wed, 24 Apr 2024 12:41:12 -0600 Subject: [PATCH] updates requirements with bucket considerations --- .../storage-providers/configure-minio.mdx | 16 ++++------------ .../storage-providers/configure-s3.mdx | 18 ++++-------------- 2 files changed, 8 insertions(+), 26 deletions(-) diff --git a/website/content/docs/configuration/session-recording/storage-providers/configure-minio.mdx b/website/content/docs/configuration/session-recording/storage-providers/configure-minio.mdx index 7e55e4377f..19e4bc3bfc 100644 --- a/website/content/docs/configuration/session-recording/storage-providers/configure-minio.mdx +++ b/website/content/docs/configuration/session-recording/storage-providers/configure-minio.mdx @@ -15,20 +15,12 @@ Before you can create a storage bucket in Boundary, you must ensure that your en Session recording requires specific configuration for both the external storage provider and the Boundary worker. -### Storage requirements +Refer to the [Configure workers for storage]to learn about configuring self-managed workers for session recording. -A [BSR](/boundary/docs/concepts/auditing/#bsr-directory-structure) (Boundary Session Recording) captures all the data transmitted between a user and a target during a single session. As a result, the size of a BSR is dependent on useractivity. 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. +When determining storage requirements for the external bucket, you should consider: -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. - -- 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. 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 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. +- [Local worker storage requirements](/boundary/docs/configuration/session-recording/configure-worker-storage#storage-requirements) +- [Storage bucket retention policies](/boundary/docs/configuration/session-recording/configure-storage-policy) ### MinIO requirements diff --git a/website/content/docs/configuration/session-recording/storage-providers/configure-s3.mdx b/website/content/docs/configuration/session-recording/storage-providers/configure-s3.mdx index 8a4abb306a..70379e8414 100644 --- a/website/content/docs/configuration/session-recording/storage-providers/configure-s3.mdx +++ b/website/content/docs/configuration/session-recording/storage-providers/configure-s3.mdx @@ -15,22 +15,12 @@ Before you can create a storage bucket in Boundary, you must ensure that your en Session recording requires specific configuration for both the external storage provider and the Boundary worker. -Refer to the [Configure workers for storage](/boundary/docs/configuration/session-recording/configure-worker-storage) to learn about configuring self-managed workers for session recording. +Refer to the [Configure workers for storage]to learn about configuring self-managed workers for session recording. -### Storage requirements +When determining storage requirements for the external bucket, you should consider: -A [BSR](/boundary/docs/concepts/auditing/#bsr-directory-structure) (Boundary Session Recording) captures all the data transmitted between a user and a target during a single session. As a result, the size of a BSR is dependent on useractivity. 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 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. - -- 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. 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 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. +- [Local worker storage requirements](/boundary/docs/configuration/session-recording/configure-worker-storage#storage-requirements) +- [Storage bucket retention policies](/boundary/docs/configuration/session-recording/configure-storage-policy) ### AWS requirements