diff --git a/website/content/docs/configuration/session-recording/configure-worker-storage.mdx b/website/content/docs/configuration/session-recording/configure-worker-storage.mdx
index a5b2e7c064..fd2399febc 100644
--- a/website/content/docs/configuration/session-recording/configure-worker-storage.mdx
+++ b/website/content/docs/configuration/session-recording/configure-worker-storage.mdx
@@ -7,6 +7,8 @@ description: |-
 
 # Configure workers for session recording
 
+<EnterpriseAlert product="boundary">This feature requires <a href="https://www.hashicorp.com/products/boundary">HCP Boundary or Boundary Enterprise</a></EnterpriseAlert>
+
 [Session recording](/boundary/docs/configuration/session-recording) requires that you [configure at least one worker for local storage](/boundary/docs/configuration/session-recording/create-storage-bucket#boundary-workers-requirements).
 
 <Note>
@@ -37,7 +39,7 @@ Workers that you configure for storage must:
 - Have an accessible directory defined by `recording_storage_path` for storing session recordings while they are in progress. On session closure, Boundary moves the local session recording to remote storage and deletes the local copy.
    - For HCP Boundary, refer to the [Self-managed worker configuration](/hcp/docs/boundary/self-managed-workers/session-recording) documentation.
    - For Boundary Enterprise, refer to the refer to the [worker configuration](/boundary/docs/configuration/worker/worker-configuration#session-recording) documentation.
-- Have available disk space defined by `recording_storage_minimum_available_capacity`. If you do not configure the minimum available storage capacity, Boundary uses the default value of 500MiB.  
+- Have available disk space defined by `recording_storage_minimum_available_capacity`. If you do not configure the minimum available storage capacity, Boundary uses the default value of 500MiB.
 - Run Darwin, Windows, or Linux. The following binaries are not supported for session recording: NetBSD, OpenBSD, Solaris.
 
 ### Local storage
@@ -55,9 +57,9 @@ The possible storage states determined by the `recording_storage_minimum_availab
 - `Critically low storage`: The worker is below half the storage threshold. Existing sessions that are enabled with session recording will be forcefully closed. The worker is not available to record new sessions or play back existing recordings.
 
 - `Out of storage`: The worker is out of local disk space. It is not available to record new sessions or play back existing recordings. The worker is in a unrecoverable state. An administrator must intervene to remedy the issue.
-   
+
 - `Not configured`: The worker does not have a `recording_storage_path` configured.
-    
+
 - `Unknown`: The default local storage state of a worker. This state indicates that the local storage state of a worker is not yet known. Older workers (< 0.16.0) will be in this state.
 
 If a worker is in an unhealthy local storage state, Boundary does not allow new session recordings or session recording playback until the worker is in an `available` local storage state.
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 1d328c1b9d..94e33c8c39 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
@@ -7,6 +7,8 @@ description: |-
 
 # Configure MinIO as a storage provider
 
+<EnterpriseAlert product="boundary">This feature requires <a href="https://www.hashicorp.com/products/boundary">HCP Boundary or Boundary Enterprise</a></EnterpriseAlert>
+
 This page describes how to configure MinIO as a storage provider for session recording with Boundary.
 
 ## Requirements
@@ -34,7 +36,7 @@ When determining storage requirements for the external bucket, you should consid
 
    Refer to the [MinIO Access Keys](https://min.io/docs/minio/kubernetes/upstream/administration/console/security-and-access.html#access-keys) documentation page to learn how to set up a MinIO service account.
 
-- A MinIO storage bucket must be configured with R/W access. If using a 
+- A MinIO storage bucket must be configured with R/W access. If using a
   restricted IAM user policy, the following policy actions must be allowed at a minimum.
 
    ```json
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 4f281269dc..e9eafb7d3c 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
@@ -7,6 +7,8 @@ description: |-
 
 # Configure Amazon S3 as a storage provider
 
+<EnterpriseAlert product="boundary">This feature requires <a href="https://www.hashicorp.com/products/boundary">HCP Boundary or Boundary Enterprise</a></EnterpriseAlert>
+
 This page describes how to configure Amazon S3 as a storage provider for session recording with Boundary.
 
 ## Requirements
@@ -20,7 +22,7 @@ Refer to the [Configure workers for storage]to learn about configuring self-mana
 When determining storage requirements for the external bucket, you should consider:
 
 - [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) 
+- [Storage bucket retention policies](/boundary/docs/configuration/session-recording/configure-storage-policy)
 
 ### AWS requirements