Yes, like what you said @KiranEd , by default, AEM periodically cleans up old asset versions based on rules set in the Version Manager configuration.
This process is controlled by the service com.day.cq.wcm.core.impl.VersionManagerImpl. The cleanup rules determine how many versions are kept and for how long, which is why older versions like the original supplier upload (version 1.0) can eventually be deleted.
To ensure that the original version is always retained, you need to adjust the OSGi configuration for this service. Specifically, you should set the property minNumberVersions to 1. This guarantees that at least one version, which will be the very first one created, is always preserved. You can then still control how many newer versions to keep by setting maxNumberVersions, and how long to keep versions based on their age with maxAgeDays.
Because this is AEM as a Cloud Service, you cannot edit the configuration directly in the Felix console. Instead, you must deploy the configuration as code through your Cloud Manager Git repository. You would add an OSGi configuration file under the /apps folder of your project, for example:
/apps/myproject/config/com.day.cq.wcm.core.impl.VersionManagerImpl.cfg.json
Inside that configuration file, you could set properties like:
{
"versionmanager.maxNumberVersions": 5,
"versionmanager.minNumberVersions": 1,
"versionmanager.maxAgeDays": 30,
"versionmanager.purgingEnabled": true
}
more details on the configuration options can be found here: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/conf...
After committing this file and deploying through Cloud Manager, the cleanup process will retain the original version permanently while continuing to purge unnecessary intermediate versions.
This approach ensures that the first uploaded supplier version is always available, while still keeping storage manageable by cleaning up later edits according to your retention policy.
