S3 Storage Provider Setup

The S3 Storage Provider can be used to allow users to map in their S3 buckets into their container-based Kasm Session. Access is provided via the Rclone Docker volume plugin.

Reference Docs:

• https://rclone.org/s3/

Kasm Storage Provider Config

1. Log into the Kasm UI as an administrator.
2. Select Settings -> Storage -> Add.
3. Update the form with the following entries

Name	S3
Storage Provider Type	S3
Enabled	checked
Default Target	/s3
Volume Config	{ "driver" : "rclone", "driver_opts" : { "type" : "s3", "s3-provider" : "AWS", "s3-env-auth" : "false", "s3-region" : "us-east-1", "uid" : "1000", "gid" : "1000", "allow_other" : "true" } }
Mount Config	{}

note

Many of the storage provider examples include default storage driver options used by Rclone. These options work well with Kasm in its default configuration, and administrators can adjust them as needed. The available options often vary by provider plugin, for example Google Drive compared with OneDrive.

The Rclone Docker plugin is installed by default as part of the standard Workspace install. For more information about Rclone driver options, see the Rclone Docker documentation.

4. Click Save to save the changes.

S3 storage mapping configuration

1. From any page, select the profile icon at the top right.

Edit Profile

2. Select the Cloud Storage section, then Add Storage Mapping.

Add Storage Mapping

3. Select S3 from the drop-down. Enter the S3 Access Key ID, S3 Secret Access Key, and S3 Bucket, then select Next.

Configure Storage

4. On success, Kasm redirects you to the Workspaces dashboard. The new storage mapping appears in the Cloud Storage section of the profile.

Storage Mapping

5. Launch a new container-based session. Confirm that the S3 buckets are mapped inside the session at the /s3 location.

In Session View