- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Migrating standalone Test Manager
- Step 9: Deleting the default tenant
- Performing a single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Rotating Blob Storage Credentials
- Disabling use of pre-signed URLs when uploading data to Amazon S3 storage
- Configuring process app security
- Setting up Kerberos authentication with basic MSSQL authentication for Process Mining
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
- EKS backup failure due to Velero version
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC access denied error
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
Disabling use of pre-signed URLs when uploading data to Amazon S3 storage
How pre-signed URL usage for Amazon S3 uploads was handled in Automation Suite versions 2023.10.0 through 2023.10.3 on EKS/AKS.
The information on this page is applicable to versions 2023.10.0, 2023.10.1, 2023.10.2, and 2023.10.3. Starting with version 2023.10.4, disabling the use of pre-signed URLs is handled via the global disable_presigned_url flag. Refer to Pre-signed URL configuration.
If you use Amazon S3 storage objects and you want to prevent users uploading data using a pre-signed URL, you can configure this in the blob_storage_account_use_presigned_uri setting in the cluster_config.json file.
By default, the blob_storage_account_use_presigned_uri setting is set to true. If you do not want users to upload data using a pre-signed URL, you can set the blob_storage_account_use_presigned_uri setting to false.