What is a difference between AEM as a Adobe Managed Service (AMS) and AEM as a cloud service.

Gearing up for your next AEM interview? If you're an Adobe Experience Manager (AEM) Author, developer or a architect, chances are you've come across the terms "AEM as a Managed Service" and "AEM as a Cloud Service." These two offering models by Adobe are hot topics in AEM interviews and understanding their differences is crucial for showcasing your expertise. 

In this blog post, we'll dive into a comparison of AEM as a Managed Service vs. AEM as a Cloud Service, exploring their Instance configurations, architecture, benefits, drawbacks, and ideal use cases in a aspect-wise manner. By the end, you'll be equipped with the knowledge to confidently answer interview questions and make informed decisions about the best AEM offering for your projects. Let's unravel the nuances of these two powerful options and empower you to excel in your AEM career!


1. Use of Authoring User Interface

AMS 

Touch UI as well as Classic UI both are accessible and can be used by AEM Authors. Please note classic UI is deprecated by Adobe and they no longer recommend using it.

AEM as a Cloud Service

In AEM as a cloud Service only Touch UI is allowed to use. Adobe recommends using Touch UI for authoring as well as administrative works as it works seamlessly across devices with all screen size.


2. Adding a new AEM user (Author, Developer)

AMS 

Author Instance User Management page can be used to create a new AEM user in system. Following link can be followed to create a new AEM user. 
http://localhost:4502/useradmin

AEM as a Cloud Service

AEM user management can be done via Admin console. Users are organized into the groups called Identity Management System Groups and specific levels of access can be given based on the requirements. 

3. Access to CRXDE 

AMS 

CRXDE can be accessed for Author as well as Publish instance in Production environments. Also direct changes in the publish instance can be done (It is suggested to avoid doing direct changes in production publish instances, always use replication from author instance.)

AEM as a Cloud Service

CRXDE can not be accessed for Production environments, direct changes in publish instance cannot be done.

4. Run modes available

AMS 

Run modes in AEM helps us to use the AEM instance for specific purposes. custom Run Modes are available in AMS. Custom run mode can be specified during starting the AEM quikstart.

AEM as a Cloud Service

Custom Run Modes are not available in AEM as cloud service.


5. Use of a project repository 

AMS 

Any repository can be used to maintain and deploy the code.

AEM as a Cloud Service

Adobe Git repository is the only option for project repository.

6. Use of a Code Deployment Tool

AMS 

Any CI tool can be used for code deployment.

AEM as a Cloud Service

In AEM as a cloud service only Cloud Manager can be used for code deployment.


7. Use of replicating agents

AMS 

Publishing the content from author instance to publish instance will be taken care by replicating agents. Custom replicating agents can be created in AMS to achieve specific task.

AEM as a Cloud Service

In AEM as a cloud service Sling Content Distribution is used for publishing the content. Also we cannot use replication agent and we are not able to create custom replication agent.

8. Security Features Deployment

AMS 

Security features needs to be deployed manually after testing in lower environments.

AEM as a Cloud Service

Security features will be deployed automatically on daily basis.

9. Process for Upgrades

AMS 

Upgrades are done manually after throughout testing from lower environments to higher environments.

AEM as a Cloud Service

Upgrades are done automatically from lower environments to higher environments, where lower environment upgrade acts as a quality check and based on it upgrades are applied to higher environments. 


10. Dispatcher Configurations 

AMS 

We can organize dispatcher configurations in any folder structure as per the need.

AEM as a Cloud Service

Standard structure as per cloud manager needs to be followed for dispatcher configuration.


11. Use of Content Delivery Network (CDN)

AMS  

We can use any CDN service coupled with AMS, some of the examples are Akamai, Cloudfare, Fastly.

AEM as a Cloud Service

Adobe managed CDN is recommended to use, if AEM customer wants to use different CDN then customer CDN has to point to AEM managed CDN.


As you prepare for your AEM interviews, mastering the distinction between AEM as a Managed Service and AEM as a Cloud Service is essential. This knowledge showcases your technical acumen and ability to make strategic project decisions. By thoroughly understanding their intricacies, you'll be ready to impress interviewers and confidently navigate the evolving landscape of AEM deployment. So, go ahead and ace those interviews with your newfound AEM expertise!  

Feeling curious about a specific AEM topic or interview question? Don't hesitate to post your question in a comment below. Our team of AEM experts will be happy to assist you as soon as possible!

Comments

Popular posts from this blog

What is Adobe Experience Manager (AEM).

Important Questions & Answers on Articulation (Part 1)

Important Questions & Answers on Articulation (Part 2)

Important Questions & Answers on Articulation (Part 7)

Most asked questions for Generative AI