From 30d5c23a61cfbc41fb020ad13d4f360d911a5e80 Mon Sep 17 00:00:00 2001 From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> Date: Tue, 30 Apr 2024 18:06:07 +0000 Subject: [PATCH] backport of commit f6161fd5e0f1d717b7823b84ca91fee758376310 --- .../session-recording/storage-providers/configure-minio.mdx | 4 ++++ 1 file changed, 4 insertions(+) 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 e5110249e1..781139d3c5 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 @@ -30,8 +30,12 @@ When you determine storage requirements for the external bucket, you should cons You must associate the Boundary storage bucket with a MinIO storage bucket. A Boundary MinIO storage bucket contains the bucket name, endpoint URL, optional region, optional prefix, and the service account credentials needed to access the bucket. To enable credential rotation, you cannot add a Boundary storage bucket without a MinIO service account. You can disable credential rotation when you create the Boundary storage bucket. + + At this time, the NetBSD operating system is not supported for the MinIO storage bucket. + + - A MinIO service account and access keys You must provide service account access keys when you configure a Boundary storage bucket later on.