To learn about Cloud Manager for Adobe Experience Manager (AEM) 6.4 and above, please refer to Cloud Manager User Guide.
Adobe Experience Manager (AEM) Cloud Management is Software-as-a-Service (SaaS) that enables reduced time and costs for provisioning, managing, and metering Web Experience Management (WEM) solutions supporting digital marketing initiatives. AEM Cloud Management takes advantage of cloud computing technology, such as Amazon Web Services (AWS) and Rackspace® Cloud Hosting, to start up AEM clusters quickly and consistently.
Using AEM Cloud Management, Digital Marketing organizations can provision and deploy instances of their Web environment without having to procure hardware or pay large upfront costs. This ease of provisioning allows enterprises to rapidly engage customers, drive market shares, and focus on innovation.
Video: AEM Cloud Management overview and recent feature additions
An AEM cloud is a dedicated environment configured as a Web Experience Management (WEM) platform. You can deploy WEM applications and services on AEM clouds to support your organization's digital marketing initiatives. AEM clouds are provisioned and configured using the supported cloud provider of your choice.
You can create, access, manage, and monitor AEM clouds using AEM Cloud Management. AEM Cloud Management also lets you create automatic backups for any of your AEM clouds and restore those backups on demand.
The following infographic shows the AEM Cloud Management framework:
An AEM cloud is a dedicated environment configured as a Web Experience Management (WEM) platform. You can deploy Web Experience Management (WEM) applications and services on AEM clouds to support your organization's digital marketing initiatives.
While different AEM instances in different environments are all installations of the same AEM software, these instances differ mainly in the way they are configured. For example, how the AEM instance is configured determines whether the instance behaves as an Author instance or a Publish instance.
Publish instances provide an environment where visitors access your website and interact with it—on the Internet or within your organization's firewall. Publish instances perform tasks such as the following:
- holding content replicated from the authoring environment
- making that content available to the visitors of your website
- storing user data generated by visitors, such as comments or other form submissions
The publish environment generates your website's content pages dynamically in real time. If necessary, this content can be personalized for each individual user.
The Dispatcher is Adobe's caching and/or load balancing tool. The Dispatcher helps realize an environment that is both fast and dynamic. It works as part of a static HTML server, such as Apache, with the aim of storing (or "caching") as much of the site content as possible in the form of a static website; and accessing the layout engine as infrequently as possible.
For more information about AEM concepts, see this Help topic.
AEM packages extend the capabilities of your Web Experience Management (WEM) platform. You can install packages on all the instances across one or more AEM clouds in a single click.
AEM packages are available on PackageShare, the AEM application marketplace. You can install packages provided by Adobe or the AEM cloud community; or upload and share your own packages.
AEM Cloud Management lets you import credentials for cloud services, such as Adobe SiteCatalyst, that you have already subscribed to with different vendors. Once a cloud service has been added in AEM Cloud Management, you can choose to install the service on your AEM clouds. Later, you can also analyze the metering graphs to track service usage per AEM cloud or per instance/node.
Amazon products and services
This documentation contains references to the following Amazon Web Services (AWS) products, services, and terms:
- Amazon Elastic Compute Cloud (EC2)
- Amazon Simple Storage Service (Amazon S3)
- Amazon Elastic Block Store (Amazon EBS)
- Amazon Machine Instance (AMI)
- Ephemeral store: When an instance is created from an Amazon Machine Image (AMI), it often comes with a preconfigured block of pre-attached disk storage. This storage is referred to as an instance store or an ephemeral store. For more information, see this Amazon.com Help topic.
Rackspace products and services
This documentation contains references to the following Rackspace Cloud Hosting products, services, and terms:
- Managed and Unmanaged account
- Cloud Servers
- Cloud Files
For more information, refer to the Rackspace documentation.
New AEM clouds are created with a default three-tier architecture comprising an Author instance, a Publish instance, and a Dispatcher.
Default architecture of an AEM cloud (Click here to view a larger version of the infographic)
You can also add additional Publish instances and Dispatchers. The additional instances are set up in a farm topology.
An AEM cloud is provisioned on public clouds with one Dispatcher, one Publish instance, and one Author instance by default.
The following infographic illustrates how an AEM cloud is provisioned on the Amazon EC2 public cloud:
Dispatcher: Amazon EC2 instance launched from an Amazon Machine Image (AMI) with no additional storage attached. Since the Dispatcher is used for load balancing across Publish instances and for caching static content, it utilizes only the instance ephemeral store.
Publish instance: Amazon EC2 instance launched from an AMI with Elastic Block Store (EBS) storage attached. Adobe AEM is installed on the persistent EBS storage in the /mnt/crx folder. The instance ephemeral store is not used in the current implementation.
Author instances: Amazon EC2 instance launched from an AMI with EBS storage attached. Adobe AEM is installed on the persistent EBS storage in the /mnt/crx folder. The instance ephemeral store is not used in the current implementation.
Backups: Backups are triggered using the AEM backup feature and then copied automatically to the Amazon Simple Storage Service (Amazon S3) using your Amazon credentials.
Topologies: AEM Cloud Management supports two topologies for different hosting requirements:
Development/Testing: 1 Author instance, 1 Publish instance, and 1 Dispatcher with no load balancer
Staging/Production: 1 Author instance, 1 Publish instance, 1 Dispatcher, and a load balancer in front of the Dispatcher. You can scale to add a Dispatcher tier in addition to the default Dispatcher.
An AEM cloud is provisioned on Rackspace Cloud Hosting as follows:
Dispatcher: Rackspace cloud server launched from a Rackspace Server Image with persistent attached storage
Publish instance: Rackspace cloud server launched from a Rackspace Server Image with persistent attached storage. Adobe AEM is installed on the persistent storage in the /mnt/crx folder.
Author instances: Rackspace cloud server launched from a Rackspace Server Image with persistent attached storage. Adobe AEM is installed on the persistent storage in the /mnt/crx folder.
Backups: Backups are triggered using the AEM backup feature and then copied automatically to Cloud Files using your Rackspace credentials.