Hi all,
What is the difference between AEM Cloud Service and Managed Service?
Understand that in Managed Service, Cloud, AEM installation, maintenance and upgrades are all Adobe's responsibility.
In AEM Cloud Service, everything is same as above, except that Cloud is provisioned and managed by someone other than Adobe?
Appreciate all your responses.
Thanks,
Rama.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @AEM_Forum!
Adobe Manages Services (AMS) and AEM as a Cloud Service (AEMaCS) are different offers by Adobe.
While AMS is more of a hosting offer for "classic" AEM 6.5 (similar to on-premise setups but run at/by Adobe), AEMaCS is a Software as a Service (SaaS) offer. Also AEMaCS has quite some differences compared to AEM 6.5 [1].
For additional details on AMS, please refer to this documentation [2] or ask your Adobe representative.
For additional details on AEMaCS, please refer to this documentation [3] (or ask your Adobe representative).
Hope that helps!
[2] https://helpx.adobe.com/legal/product-descriptions/adobe-experience-manager-managed-services.html
[3] https://helpx.adobe.com/legal/product-descriptions/aem-cloud-service.html
Update:
A couple of key differences:
Adobe Manages Services | AEM as a Cloud Service |
Hosting offer for AEM | Software as a Service (SaaS) |
Fixed size of environments (can be scaled on demand) | Autoscaling |
Licensed as packages varying by # of envs, size of envs, SLA, etc. (see [2] above) | Licensed based on content requests per month (see [3] above) |
"Classic" AEM 6.5, same as on-premise | Dedicated AEMaCS version that comes with some "guard rails" and cloud-specifics (see [1] above) |
Updates on demand through quarterly Service Packs | Continuous, automatic monthly updates |
Hi @AEM_Forum!
Adobe Manages Services (AMS) and AEM as a Cloud Service (AEMaCS) are different offers by Adobe.
While AMS is more of a hosting offer for "classic" AEM 6.5 (similar to on-premise setups but run at/by Adobe), AEMaCS is a Software as a Service (SaaS) offer. Also AEMaCS has quite some differences compared to AEM 6.5 [1].
For additional details on AMS, please refer to this documentation [2] or ask your Adobe representative.
For additional details on AEMaCS, please refer to this documentation [3] (or ask your Adobe representative).
Hope that helps!
[2] https://helpx.adobe.com/legal/product-descriptions/adobe-experience-manager-managed-services.html
[3] https://helpx.adobe.com/legal/product-descriptions/aem-cloud-service.html
Update:
A couple of key differences:
Adobe Manages Services | AEM as a Cloud Service |
Hosting offer for AEM | Software as a Service (SaaS) |
Fixed size of environments (can be scaled on demand) | Autoscaling |
Licensed as packages varying by # of envs, size of envs, SLA, etc. (see [2] above) | Licensed based on content requests per month (see [3] above) |
"Classic" AEM 6.5, same as on-premise | Dedicated AEMaCS version that comes with some "guard rails" and cloud-specifics (see [1] above) |
Updates on demand through quarterly Service Packs | Continuous, automatic monthly updates |
Views
Replies
Total Likes
Views
Replies
Total Likes
Hi @AEM_Forum!
I have updated my answer with a short table on key differences.
AEM as a Cloud Service (AEMaCS) is the SaaS offer.
Both offers have their pros and cons, there is no general recommendation. It all depends you a projects individual requirements.
Hope that helps!
Views
Replies
Total Likes
More Information:
Adobe Cloud Manager is integral to the continuous upgrade approach of AEM as a Cloud Service, as it controls all updates to your instances - this is mandatory.
Updates can be triggered by Adobe when a new version of the cloud service is available. Alternatively, you can trigger your application updates using the pipelines provided by Cloud Manager.
Cloud Manager is:
used to manage AEM programs and environments,
an essential component of AEM as a Cloud Service; each new tenant is first provisioned for Cloud Manager access,
the single entry point for your operations and development staff.
Specifically, the number of and the type of AEM programs that can be created from the Cloud Manager is derived either:
from the customer licensing agreement,
from internal-driven actors when AEM as a Cloud Service is used for enablement or training,
from external-driven processes such as trials started from Adobe.com.
Cloud Manager has evolved as a self-service portal where the main components of AEM as a Cloud Service can be created and configured:
Creating and managing new programs. Refer to Understanding Programs and Program Types for more details.
Creating and managing the AEM environments within these programs. Refer to Managing Environments for more details.
Creating and managing the pipelines for deploying the customer code and the related configuration to a specific environment. Refer to Configuring your CI-CD Pipeline for more details.
Being notified of important lifecycle events for these components (for example, product updates).
Cloud Manager creates environments in datacenters across many geographic regions, providing for global coverage. CDN Points of Presence (PoPs) ensure low-latency content delivery for customers located all over the world.
AEM as a Cloud Service(AEMaCS) is SaaS service.
AEM as a Cloud Service now uses Continuous Integration and Continuous Delivery (CI/CD) to ensure that your projects are on the most current AEM version
It provides autoscaling and scale based on the actual traffic and actual activity.
Cloud Manager is used to manage AEM programs and environments. We can access the console directly.
Licence Metric:Content Requests per month. refer here
Monthly updates.
The classic UI of AEM is no longer available with the cloud version.
fastly CDN is provided by deafult.
Adobe Manages Services provides Hosting offer for AEM.
Fixed size of environments are there and can be scaled on demand basis.
Updates are on demand or quarterly.
manage service Base package here
More Refer here
Views
Replies
Total Likes