From 2969a720e167c7a593ea2087e57561b68fc59fed Mon Sep 17 00:00:00 2001 From: Robin Beck Date: Fri, 26 Apr 2024 19:53:07 +0000 Subject: [PATCH] backport of commit efc3f20cb0d053f635f7766327be9bd0b7386ef8 --- .../configure-storage-policy.mdx | 18 ++++++++---------- .../enable-session-recording.mdx | 8 ++++---- 2 files changed, 12 insertions(+), 14 deletions(-) diff --git a/website/content/docs/configuration/session-recording/configure-storage-policy.mdx b/website/content/docs/configuration/session-recording/configure-storage-policy.mdx index 9acf1ce54c..ad7e26eb50 100644 --- a/website/content/docs/configuration/session-recording/configure-storage-policy.mdx +++ b/website/content/docs/configuration/session-recording/configure-storage-policy.mdx @@ -22,9 +22,7 @@ For more information about using session recording to audit user sessions, refer ## Requirements -Before you can create a storage bucket in Boundary, you must ensure that your environment meets certain requirements. -Session recording requires specific configuration for both the external store and the Boundary worker. -At this time, the only supported storage is AWS S3. +Before you can create a storage bucket in Boundary, you must ensure that your environment meets certain requirements. Session recording requires specific configuration for both the external storage provider and the Boundary worker. A Boundary worker configured for local storage is also required to set up session recording and configure recording bucket policies. @@ -47,7 +45,7 @@ Complete the following steps to create a storage policy in Boundary for session 1. Log in to Boundary. -1. Select **Storage Policies** in the navigation panel in the `global` scope. +1. Click **Storage Policies** in the navigation panel in the `global` scope. 1. Click **Create a new storage policy**. 1. Complete the following fields to create the Boundary storage policy: - **Name**: (Optional) The name field is optional, but if you enter a name it must be unique. @@ -183,8 +181,8 @@ The following example applies the policy created above to an org named `prod-dat 1. Log in to Boundary. -1. Select **Orgs** in the navigation panel and select the `prod-databases` org. -1. Select **Org Settings** in the navigation panel for the `prod-databases` org. +1. Click **Orgs** in the navigation panel and select the `prod-databases` org. +1. Click **Org Settings** in the navigation panel for the `prod-databases` org. 1. Under **Storage Policy**, click **Add Storage Policy**. 1. Select the `soc2-policy`. 1. Click **Save**. This applies the policy to this scope and its children. @@ -332,8 +330,8 @@ Check that the storage policy was successfully attached to the `prod-databases` 1. Log in to Boundary. -1. Select **Orgs** in the navigation panel and select the `prod-databases` org. -1. Select **Org Settings** in the navigation panel for the `prod-databases` org. +1. Click **Orgs** in the navigation panel and select the `prod-databases` org. +1. Click **Org Settings** in the navigation panel for the `prod-databases` org. 1. Verify that the `soc2-policy` is listed under **Storage Policy**. @@ -474,8 +472,8 @@ New session recordings under the `prod-databases` scope should now show a `retai 1. Create a new session recording on a target within the `prod-databases` org. 1. Log in to Boundary. -1. Select **Session Recordings** in the navigation panel. -1. Select **View** for a new recording that was made after the storage policy was attached to the `prod-databases` scope. +1. Click **Session Recordings** in the navigation panel. +1. Click **View** for a new recording that was made after the storage policy was attached to the `prod-databases` scope. 1. Under **Session details**, verify that the *Retain until* and *Delete after* dates match the durations defined in the `soc2-policy`. diff --git a/website/content/docs/configuration/session-recording/enable-session-recording.mdx b/website/content/docs/configuration/session-recording/enable-session-recording.mdx index cb8710a372..74ed94a142 100644 --- a/website/content/docs/configuration/session-recording/enable-session-recording.mdx +++ b/website/content/docs/configuration/session-recording/enable-session-recording.mdx @@ -58,7 +58,7 @@ Complete the following steps to enable session recording on a target. 1. Log in to Boundary. -1. Select **Orgs** in the navigation pane. +1. Click **Orgs** in the navigation pane. 1. Select the org that contains the target you want to enable for session recording. 1. Select the project that contains the target you want to enable for session recording. 1. Select **Targets** in the navigation pane. @@ -71,8 +71,8 @@ The following setting is required for session recording: - Select **SSH** for the **Type**. -1. Select **Save**. -1. Select **Enable recording**. +1. Click **Save**. +1. Click **Enable recording**. ![Enable session recording](/img/enable-session-recording.png) @@ -81,7 +81,7 @@ The following setting is required for session recording: You can also [create a new storage bucket](/boundary/docs/configuration/session-recording/create-storage-bucket). -1. Select **Save**. +1. Click **Save**.