Increasing single part asset upload limit for Photoshop Firefly API Integration
This article addresses the challenge of uploading assets larger than 100 MB from Photoshop Firefly to Adobe Experience Manager as a Cloud Service (AEMaaCS). AEMaaCS enforces a 100 MB limit for single part uploads, while Photoshop Firefly does not support multipart uploads. To resolve this, the article suggests designing an intermediary service or revising the integration mechanism to enable successful uploads of large assets.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS) - Assets
Issue/Symptoms
Adobe Experience Manager as a Cloud Service enforces a maximum size limit of 100 MB for single part asset uploads. The Photoshop Firefly API does not support multipart uploads, creating a conflict when attempting to upload assets larger than 100 MB directly from Photoshop Firefly to AEMaaCS. As a result, assets up to 300 MB cannot be uploaded in their entirety due to these constraints.
Resolution resolution
Note: Overriding or increasing the maxPartSize value beyond 100 MB is not supported within AEMaaCS’s current design framework. Any file larger than this limit must be split into chunks during upload.
To address the issue of uploading assets larger than 100 MB from Photoshop Firefly to AEMaaCS, consider implementing one of the following approaches:
-
Design an intermediary service using tools like Adobe AppBuilder or Node.js. Configure the service to:
- Retrieve the asset from Photoshop Firefly.
- Handle necessary in-memory buffering or chunking.
- Utilize the AEM’s standard direct binary upload procedure, which automatically splits large files into chunks based on the
initiateUploadresponse.
-
Modify the integration flow between Photoshop Firefly and AEM to enable support for multipart uploads by performing chunking before initiating the upload process.
-
Alternatively, create an adapter that bridges between single-part upload expectations and AEMaaCS’s multipart requirements.