From 2170f2faeb9382df62143d56a493690b24e75559 Mon Sep 17 00:00:00 2001 From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> Date: Tue, 30 Apr 2024 17:54:20 +0000 Subject: [PATCH] backport of commit 6be62acc995739547d3d10a7eb6843bf1d35d64e --- .../session-recording/storage-providers/configure-minio.mdx | 2 ++ 1 file changed, 2 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 986ac04c7d..e5110249e1 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,6 +30,8 @@ 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.