About Storage Buckets

Storage buckets provide a per-folder storage solution for RPA developers to leverage in creating automation projects (e.g. for a .pdf file used across multiple business processes or data sets used for your machine learning models). For details on using storage buckets in your automation projects read about Orchestrator activities in the Activities guide.

As storage buckets are created within the scope of a given folder, this enables you to use the fine-grained permissions and role assignment models of the Folders feature to control access to these storage buckets and their contents only to those accounts that need it. Users with the required permissions can browse the contents of any configured storage bucket, and upload or download files as desired.

The Storage Buckets page displays your currently configured buckets and enables you to create as many additional storage buckets as needed.

Storage buckets can be configured using any of the following providers:

• Orchestrator
• Azure Storage (WASB)
• Amazon S3
• MinIO
• S3 Compatible storage solutions
• FileSystem

Storage Providers

Storage Buckets can be configured using any of the following providers:

• Orchestrator - the same storage location where Orchestrator feed packages are kept (see the Deployment section of the UiPath.Orchestrator.dll.config topic)
• Azure Storage (WASB)
• MinIO
• S3 Compatible storage solutions - support SSE-KMS
• FileSystem - the file system location of your choice (see the Storage Buckets section of the UiPath.Orchestrator.dll.config topic)

Note:

• For connecting to AWS S3 buckets or S3-compatible buckets, Orchestrator uses signature V4 by default, in all configurations. If you want to enable the old behavior, where V2 signatures were used for us-east-1 or for your S3-compatible storage provider, you need to add the Aws.UseSignatureVersion4 setting to the UiPath.Orchestrator.dll.config file, with the value false.

To specify which providers can be used in creating storage buckets in Orchestrator you must proceed as follows:

1. Open the UiPath.Orchestrator.dll.config file in the Orchestrator installation folder.
2. Specify the desired storage providers using the Buckets.AvailableProviders parameter. For example, add the following key in the UiPath.Orchestrator.dll.config file to enable Orchestrator, Amazon, Azure, MinIO and S3 compatible storage providers: <add key="Buckets.AvailableProviders" value="Orchestrator,Amazon,Azure,Minio,S3Compatible" />. See the dedicated Buckets.AvailableProviders section in the Installation and Upgrade guide for details.

3. Restart Orchestrator.

   Important:

   FileSystem is disabled by default on both new installations and upgrades. To enable this provider, you need to explicitly specify it as a Buckets.AvailableProviders value in the UiPath.Orchestrator.dll.config file, and then add the FileSystem paths to an allowlist using the Buckets.FileSystem.Allowlist setting.

   Considering that creating a FileSystem allowlist via the Buckets.FileSystem.Allowlist setting has a series of security implications, you are strongly advised to refer to Using the FileSystem Storage Allowlist Securely before proceeding.

Permissions for Storage Buckets

Access to and control over storage buckets and their contents is governed by the following permissions:

Permission	Description
Create	Storage Buckets - allows the creation of new storage buckets. Storage Files- allows the creation of new files in storage buckets.
Edit	Storage Buckets- allows the editing of existing storage buckets.
View	Storage Buckets- allows access to bucket contents. Required for any file operations within buckets. Storage Files- enables browsing and download of bucket contents.
Delete	Storage Buckets- allows the deletion of existing storage buckets. Storage Files- allows the deletion of files in storage buckets.