Completely Disabling Image Renditions in AEMaaCS latest version

[skyflakes]

We are attempting to completely disable image renditions in the latest AEMaaCS. Below is a summary of our approach and the challenges we’ve encountered:

1. First Attempt: Configuration Profile on a Folder under AEM Assets

• We went into the properties of the target parent folder in AEM Assets.
• Created a new profile with only one rendition, hoping it would remove the other out-of-the-box renditions.
• Result: This configuration did not remove the additional renditions. Instead, it added a new rendition to the existing out-of-the-box AEM renditions.

2. Second Attempt: Using AEM Workflows

• We explored AEM > Workflows > Launchers and AEM > Workflows > Models to find the DAM Asset Update workflow.
• Result: The DAM Asset Update workflow appears to have been removed in AEMaaCS.

• Current Problem:

  • Despite these attempts, we have not been able to fully remove image renditions from assets.
  • It seems that the AEM Assets Folder (properties) > Auto-startworkflow > System Default cannot be adjusted, which is limiting our options.

Has anyone successfully removed all image renditions from assets in AEMaaCS? If so, could you share the steps or solutions you used?

[SreenivasBr]

Why do you want to disable the default renditions? They are required to display the thumbnail in assets console (card view, list view etc..) and also while previewing the image in asset detail page. Also, this default configuration cannot be changed. It can only be extended. Refer - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/manage/as...

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/manage/as...

[EstebanBustamante]

Hi, 

The way renditions are generated differs between AEMaaCS and the on-premise version. In the on-premise version, the DAM Asset Update Workflow is responsible for generating renditions, and disabling this workflow would have the effect you're looking for (as you tried with option 2). However, in AEMaaCS, there is a new set of asset microservices (the Asset Compute Service) responsible for generating the renditions, and we don't have full control over them.

That being said, you cannot disable rendition generation in AEMaaCS, as some renditions are required for other processing tasks. You can read more about this here:
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/manage/as...

Since renditions in AEMaaCS are generated asynchronously and via an external set of microservices, there is no real drawback to having them, unlike in AEM on-premise where performance and storage were often concerns, requiring careful management and purging of renditions.

Hope this helps