PrivateAIM · brucetony · Jul 15, 2026 · Jul 15, 2026
diff --git a/src/guide/admin/bucket-setup-for-data-store.md b/src/guide/admin/bucket-setup-for-data-store.md
@@ -1,20 +1,97 @@
 # Bucket Setup for Data Store
 
 Before an analysis can be executed in FLAME, the required data must be made accessible through a configured data store.
-In this context, a bucket refers to a storage location—such as an S3 or MinIO bucket—that contains the dataset to be
+In this context, a bucket refers to a storage location, such as an S3 or SeaweedFS bucket, that contains the dataset to
+be
 analyzed.
 Creating a bucket is the first step in making data available to FLAME.
 The bucket will later be referenced by a data store configuration, which connects the FLAME project to the actual data.
 
 The examples shown below use the included MinIO object store, but these steps can be applied to other S3 stores.
 
+::: info Migration to SeaweedFS+
+As of v0.1.1 of the `flame-node` helm chart, SeaweedFS replaced MinIO as the included default S3 storage
+when `dataStore` is enabled.
+:::
+
+## Adding a User
+
+Buckets can be restricted to specific users and users can furthermore have permissions set for managing the data.
+To add a user in SeaweedFS, click on "Users" in the sidebar and then on "Create User" in the top right of the window.
+Enter a username and (optionally) an email address for the new user, then assign them specific permissions and bucket
+access. Users with the "Admin (Full Access)" permission can modify and add anything they want. For executing analyses,
+the "Read" and "List" permissions are required.
+
+### Access and Secret Keys
+
+When the user is created, they will have a pair of access and secret keys generated for them, and they will be shown on
+the screen. You should keep a record of these for later use. If the window disappears too quickly, you can view them
+again (or generate a new pair) by clicking on the key symbol in the Users overview table for that user.
+
+## Creating a Bucket
+
+Buckets are where data for the analyses are stored. It is recommended that each project has its own bucket. To create a
+new one, click on "Buckets" in the sidebar and then on "Create Bucket" in the top right of the window. Give the bucket
+name (e.g. the project's name) and then optionally, assign an owner. If no owner is specified, only users with the
+"Admin (Full Access)" permission will be able to access or modify the data within the bucket.
+
+[![SeaweedFS Bucket Creation](/images/seaweedfs/bucket_create.png)](/images/seaweedfs/bucket_create.png)
+
+## Generating Access and Secret Keys
+
+By default, S3 buckets are set to "Private", and accessing the data they contain requires the use of an **access key**
+and **secret key**. These keys are also required when creating a data store in the Node UI for this bucket. In
+SeaweedFS, only keys for users with the "Admin (Full Access)" permission or the bucket owner can access the data.
+Administrators and data stewards can generate a new key pair for these users by following these steps:
+
+1. Click on "Users" in the sidebar and then click on the key symbol for the user you want to generate a key pair for
+2. Click on "Create New Key" in the top right of the window
+3. Optionally, set the "Access Key" and "Secret Key" to your own specified values, or simply click on "Create" to
+   auto-generate values for the keys
+4. Record the generated key pair
+
+## Uploading Data into a Bucket
+
+To upload files or a directory into a bucket, navigate to "Buckets" in the sidebar and select the desired
+bucket. Click the "Upload" button in the top-right corner select one or multiple files from your local
+computer to upload.
+
+[![Upload to Bucket](/images/seaweedfs/bucket_upload.png)](/images/seaweedfs/bucket_upload.png)
+
+Click "Upload Files" to upload them into the bucket.
+
+## Deleting a Bucket
+
+A bucket can only be deleted after all its contents have been removed. To do this, go to the "Buckets" tab in the
+sidebar, select the bucket you want to delete, and then click the red trashcan button in the bucket's row.
+
+## Integrate a Bucket in the Node
+
+To make data from a bucket available for an analysis within FLAME, a corresponding data store must be created for the
+associated project that intends to use the data.
+
+This process is explained in detail in
+the [Creating a Data Store](/guide/admin/data-store-management#creating-a-data-store) section. When configuring a data
+store for a bucket in the included SeaweedFS instance, the following parameters must be provided:
+
+[![Data Store Creator](/images/seaweedfs/bucket_node.png)](/images/seaweedfs/bucket_node.png)
+
+* **Data Store Type:** `S3`
+* **Hostname:**  `node-datastore-seaweedfs-all-in-one`
+* **Bucket Name:** `<bucket name>`
+* **Access Key:** Generated access key for the listed, private S3 bucket
+* **Secret Key:** Generated secret key for the listed, private S3 bucket
+* **Port:** `8333`
+
+## MinIO (Deprecated)
+
 ::: info FLAME Node <0.0.10
-As of flame-node v0.0.10, private buckets are supported and are set as the default. If you have flame-node <0.0.10 
-deployed, consider upgrading to the latest version, otherwise, only S3 buckets set to "Public" will work and any 
+As of flame-node v0.0.10, private buckets are supported and are set as the default. If you have flame-node <0.0.10
+deployed, consider upgrading to the latest version, otherwise, only S3 buckets set to "Public" will work and any
 instructions on this page mentioning "keys" are not applicable.
 :::
 
-## Creating a Bucket
+### Creating a Bucket
 
 To create a new bucket, go to the "Buckets" tab in the Administrator Area on the left side of the page and click "Create
 Bucket".
@@ -23,7 +100,7 @@ Bucket" in the lower-right corner under the Features section.
 
 [![Data Store Creator](/images/minio_images/bucket_create.png)](/images/minio_images/bucket_create.png)
 
-### Generating Access and Secret Keys
+#### Generating Access and Secret Keys
 
 By default, S3 buckets are set to "Private", and accessing the data they contain requires the use of an **access key**
 and **secret key**. These keys are also required when creating a data store in the Node UI for this bucket. In MinIO,
@@ -43,7 +120,7 @@ them when creating a data store
 
 [![MinIO Access Key Generation](/images/minio_images/access_key_creation.png)](/images/minio_images/access_key_creation.png)
 
-#### Modifying Access Key Permissions
+##### Modifying Access Key Permissions
 
 Access keys have the same policies as the user who created them by default, however, it is advisable to limit the
 permissions of the access keys used for data store creation. FLAME analyses only require the following permissions:
@@ -86,7 +163,7 @@ with the name of the appropriate bucket) for additional security:
 
 This policy can be applied either during access key creation or afterward by editing the access key settings.
 
-### Uploading Data into a Bucket
+#### Uploading Data into a Bucket
 
 To upload files or a directory into a bucket, navigate to "Object Browser" in the User Area and select the desired
 bucket.
@@ -98,13 +175,13 @@ select a file or folder from your local computer to upload.
 If the upload starts successfully, a "Downloads/Uploads" tab will appear in the top-right corner, displaying the upload
 progress as a percentage.
 
-### Deleting a Bucket
+#### Deleting a Bucket
 
 A bucket can only be deleted after all its contents have been removed. To do this, go to the "Buckets" tab in the
 Administrator Area, select the bucket you want to delete, and then click the "Delete Bucket" button in the top-right
 corner.
 
-## Integrate a Bucket in the Node
+### Integrate a Bucket in the Node
 
 To make data from a bucket available for analysis within FLAME, a corresponding data store must be created for the
 project that intends to use the data.

diff --git a/src/guide/admin/data-store-management.md b/src/guide/admin/data-store-management.md
@@ -26,19 +26,19 @@ A description of the fields in the table can be found below.
 
 ### Field Descriptions
 
-| **Field**               | **Description**                                                                                                                                                             |
-|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Project                 | Select from the currently approved list of projects for your node                                                                                                           |
-| Data Store              | This field is automatically populated using the UUID of the selected project. This identifier is used as the name of the data store when it is created in the node software |
-| Data Store Type         | Type of repository in which the data is stored. Currently, only FHIR and S3 are supported                                                                                   |
-| Data Path (FHIR only)   | The absolute directory path where the requested data is located                                                                                                             |
-| Bucket Name (S3 only)   | The name of the S3 bucket in which the data is located                                                                                                                      |
-| Bucket Access (S3 only) | Whether the S3 bucket is "Private" or "Public". It is highly recommended to keep all S3 buckets set to private                                                              |
-| Access Key (S3 only)    | Generated access key used for accessing the listed, private S3 bucket                                                                                                       |
-| Secret Key (S3 only)    | Generated secret key used for accessing the listed, private S3 bucket                                                                                                       |
-| Hostname                | Name of the server on which the data is located                                                                                                                             |
-| Port                    | Connection endpoint for accessing the server. Use 80 for HTTP and 443 for HTTPS. If a different protocol is used, please verify which port is accessible. Use port 9000 for the bundled MinIO instance.                     |
-| Protocol                | Protocol used for transferring files                                                                                                                                        |
+| **Field**               | **Description**                                                                                                                                                                                             |
+|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Project                 | Select from the currently approved list of projects for your node                                                                                                                                           |
+| Data Store              | This field is automatically populated using the UUID of the selected project. This identifier is used as the name of the data store when it is created in the node software                                 |
+| Data Store Type         | Type of repository in which the data is stored. Currently, only FHIR and S3 are supported                                                                                                                   |
+| Data Path (FHIR only)   | The absolute directory path where the requested data is located                                                                                                                                             |
+| Bucket Name (S3 only)   | The name of the S3 bucket in which the data is located                                                                                                                                                      |
+| Bucket Access (S3 only) | Whether the S3 bucket is "Private" or "Public". It is highly recommended to keep all S3 buckets set to private                                                                                              |
+| Access Key (S3 only)    | Generated access key used for accessing the listed, private S3 bucket                                                                                                                                       |
+| Secret Key (S3 only)    | Generated secret key used for accessing the listed, private S3 bucket                                                                                                                                       |
+| Hostname                | Name of the server on which the data is located                                                                                                                                                             |
+| Port                    | Connection endpoint for accessing the server. Use 80 for HTTP and 443 for HTTPS. If a different protocol is used, please verify which port is accessible. Use port 8333 for the bundled SeaweedFS instance. |
+| Protocol                | Protocol used for transferring files                                                                                                                                                                        |
 
 ## Managing Data Access
 

diff --git a/src/public/images/seaweedfs/bucket_create.png b/src/public/images/seaweedfs/bucket_create.png
diff --git a/src/public/images/seaweedfs/bucket_node.png b/src/public/images/seaweedfs/bucket_node.png
diff --git a/src/public/images/seaweedfs/bucket_upload.png b/src/public/images/seaweedfs/bucket_upload.png