Notable Changes to Adobe Experience Manager as a Cloud Service notable-changes-aem-cloud
Adobe Experience Manager (AEM) Cloud Service brings many new features and possibilities for managing your AEM Projects. However, there are some differences between AEM Sites on premise or in Adobe Managed Service as compared to AEM Cloud Service. This document highlights the important differences.
- An Introduction to Adobe Experience Manager as a Cloud Service
- What is New and What is Different between Adobe Experience Manager as a Cloud Service and previous versions
- The Architecture of Adobe Experience Manager as a Cloud Service
- Notable changes to AEM Sites as a Cloud Service
- Notable changes to AEM Assets as a Cloud Service
The main differences are found in the following areas:
/apps and /libs are immutable at runtime apps-libs-immutable
Any content and subfolders in /apps and /libs is read-only. Any feature or custom code that expects to make changes there fails to do so. An error is returned that such content is read-only and the write operation was not able to complete. This has an impact in several areas of AEM:
-
No changes in
/libsare allowed at all.- This is not a new rule, however this was not enforced in previous on-premise versions of AEM.
-
Overlays for areas in
/libsthat can be overlaid are still permitted within/apps.- Such overlays must come from Git by way of the CI/CD pipeline.
-
Static Template design information that is stored in
/appscan’t be edited by way of the UI.- It is recommended that you use Editable Templates instead.
- If Static Templates are still required, configuration information must come from Git by way of the CI/CD pipeline.
-
MSM Blueprint and custom MSM roll-out configurations must be installed from Git by way of the CI/CD pipeline.
-
I18n translation changes must come from Git by way of the CI/CD pipeline.
OSGi bundles and configurations must be treated as code osgi
Changes to OSGi bundles and configurations must be introduced by way of the CI/CD pipeline.
- New or updated OSGi bundles must be introduced through Git by way of the CI/CD pipeline.
- Changes to OSGi configurations can only come from Git by way of the CI/CD pipeline.
The Web Console, used in previous versions of AEM to change OSGi bundles and configurations, is not available in AEM Cloud Service.
Changes to publish repository are not allowed changes-to-publish-repo
Aside from changes under the /home folder on the publish tier, 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. Some limitations can be mitigated in the following ways:
- For content and content-based configuration: make your changes on the Author instance and publish them.
- For code and configuration: make your changes in the GIT repository and run the CI/CD pipeline to roll them out.
Custom run modes are not allowed custom-runmodes
Additional or custom run modes are not possible in AEM Cloud Service. For a list of run modes that are provided out-of-the-box for AEM Cloud Service, see Deploying to AEM as a Cloud Service.
Removal of Replication Agents and related changes replication-agents
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:
- Custom workflows that push content to replication agents of preview servers for example.
- Customization to replication agents to transform content.
- Using Reverse Replication to bring content from Publish back to Author.
In addition, the pause and disable buttons are removed from the replication agent administration console.
Removal of Classic UI classic-ui
The Classic UI is no longer available in AEM Cloud Service.
Publish-Side Delivery publish-side-delivery
HTTP acceleration including CDN and traffic management for Author and Publish services are provided by default in AEM Cloud Service.
For projects transitioning from AMS or an on-premises installation, Adobe strongly recommends using the built-in CDN, because features within AEM Cloud Service are optimized for the CDN provided.
Asset Handling and Delivery asset-handling
Asset upload, processing, and download are optimized in Experience Manager Assets as a Cloud Service. AEM Assets is now more efficient, enables more scaling, and lets you upload and download at a faster rate. Also, it impacts the existing custom code and some operations. For a list of changes and for parity with Experience Manager 6.5 features, see the changes to Assets.