AEM Cloud Service brings many new features and possibilities for managing your AEM projects. However there are a number of differences between AEM Sites on premise or in Adobe Managed Service as compared to AEM Cloud Service. This document highlights the important differences.
This document highlights the notable changes to AEM as a whole. For further information and solution-specific changes see:
The main differences are found in the following areas:
Any content and sub-folders in
/libs is read-only. Any feature or custom code that expects to make changes there will fail to do so. An error will be returned that such content is read-only and the write operation wasn’t able to complete. This has an impact in a number of areas of AEM:
/libsare allowed at all.
/libsthat are allowed to be overlaid are are still permitted within
/appscan’t be edited via UI.
The Web Console, used in previous versions of AEM to change OSGi settings, is not available in AEM Cloud Service. Therefore changes to OSGi must be introduced via the CI/CD pipeline.
Direct changes to the publish repository are not allowed on AEM Cloud Service. In prior versions of on-premise AEM or AEM on AMS, code changes could be made directly to the publish repository for example to creates users, update user profile, and create nodes. This is no longer possible and can be mitigated in the following ways:
The following runmodes are provided out-of-the-box for AEM Cloud Service:
Additional or custom run modes are not possible in AEM Cloud Service.
In AEM Cloud Service, content is published using Sling Content Distribution. The replication agents used in previous versions of AEM are no longer used or provided, which might impact the following areas of existing AEM projects:
The Classic UI is no longer available in AEM Cloud Service.
HTTP acceleration including CDN and traffic management for author and publish services are provided by default in AEM Cloud Service.
For project transitioning from AMS or an on-premises installation Adobe strongly recommends leveraging the built-in CDN, because features within AEM Cloud Service are optimized for the CDN provided.
Asset upload, treatment, and download have been optimized in Assets as a Cloud Service to be more efficient enabling better scaling and faster uploads and downloads. However this may impact some existing custom code.