- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- Organization administration
- Troubleshooting
About Storage Buckets
.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 - 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)
- 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-1or for your S3-compatible storage provider, you need to add theAws.UseSignatureVersion4setting to theUiPath.Orchestrator.dll.configfile, with the valuefalse.
To specify which providers can be used in creating storage buckets in Orchestrator you must proceed as follows:
- Open the
UiPath.Orchestrator.dll.configfile in the Orchestrator installation folder. - Specify the desired storage providers
using the
Buckets.AvailableProvidersparameter. For example, add the following key in theUiPath.Orchestrator.dll.configfile 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. -
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 theUiPath.Orchestrator.dll.configfile, and then add the FileSystem paths to an allowlist using the Buckets.FileSystem.Allowlist setting.Considering that creating a FileSystem allowlist via theBuckets.FileSystem.Allowlistsetting has a series of security implications, you are strongly advised to refer to Using the FileSystem Storage Allowlist Securely before proceeding.
Access to and control over storage buckets and their contents is governed by the following permissions:
|
Permission |
Description |
|---|---|
|
Create |
|
|
Edit |
|
|
View |
|
|
Delete |
|
