When configuring an external S3-compatible or Azure Blob object store for UiPath Automation Suite, setting up an accurate Cross-Origin Resource Sharing (CORS) policy is mandatory to facilitate secure, direct browser-to-storage and service-to-storage communication. The documented CORS configuration explicitly requires the AllowedMethods parameters to include `GET`, `POST`, `DELETE`, `HEAD`, and `PUT`. These methods correspond directly to essential storage actions executed across the suite's microservices. Specifically, `PUT` and `POST` enable direct multi-part uploads of large automation packages, execution media, and Document Understanding datasets; `GET` enables retrieval of packages and artifacts; `HEAD` allows the service endpoints to verify object presence and metadata headers without downloading payloads; and `DELETE` permits lifecycle cleanup routines to remove deprecated artifacts. Excluding any of these five methods—most notably `PUT` or `HEAD`—results in HTTP 403 Forbidden errors during execution artifact publishing or client downloads in products such as Orchestrator, AI Center, and Data Service. (Reference: UiPath Automation Suite Infrastructure Pre-requisites – Object Store Configuration and CORS Policy Rules).
===============
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit