Cloud Manager supports the following Web browsers:
- Microsoft Internet Explorer 9.x
- Mozilla Firefox 7.x and later
- Google Chrome 13.x and later
- Apple Safari 5.x
Cloud Manager supports the following Web browsers:
The following Amazon EC2 regions are currently supported:
Five Amazon EC2 instance sizes are supported:
25 GB, 50 GB, 100 GB, 250 GB, 500 GB, and 1 TB EBS sizes are supported.
Refer to this Help page to learn more about Amazon EC2 concepts.
Small, medium, and extra large Rackspace instances are supported.
Small: 4 GB RAM/160 GB Disk
Medium: 8 GB RAM/320 GB Disk
Large: 16 GB RAM/620 GB Disk
Before creating CQ clouds, you must upload your .properties CQ license file. If you don't have a CQ license yet, contact Adobe at https://www.day.com/day/en/registration/contact.html.
Deactivated users are counted when the CQ license is metered.
The Cloud Manager user interface is available in four languages—English, German, French, and Japanese. Follow these steps to choose a language:
Before you add your first CQ cloud, you must select a cloud provider and configure your Adobe CQ Web Experience Management (WEM) license.
In the video tutorial below, Pierre Tager — Group Manager, Adobe CQ Cloud Manager — explains how you can retrieve your AWS account credentials for use within Cloud Manager.
Cloud Manager displays the new cloud in your dashboard with a blue status. The status turns green once the cloud has initialized. You can now install packages and services on the new cloud.
Rackspace CQ clouds launched using credentials created afresh in Cloud Manager versions later than August 2012 support keypair-based login and SSH host key validation. Additionally, you can reset the cloud password for these clouds using the Rackspace admin console.
|Yellow||Paused; you can restart the cloud|
|Blue||In transit from one state to another; typical state when a new cloud is initializing|
||Stopped; a user has stopped the cloud|
|Red cloud with hazard icon||Failed cloud; the cloud failed to initialize successfully
|Green cloud with hazard icon||Running cloud with a failed node. This status usually indicates failure while adding a new Publish instance to a running cloud.|
Manage a CQ cloud (Click here to view a larger version of the screenshot)
(Only for AWS) Pauses the currently-open cloud. When you pause a cloud, the cloud provider charges for CPU cycles at a reduced rate. However, you are still charged for the allocated storage (for example, Amazon EBS volumes).
(Only for AWS) Restarts the paused cloud. When the cloud is restarted, the cloud provider reattaches the allocated storage to new instances.
Stops the cloud. When you stop a cloud; no memory, storage, or instances remain allocated to it anymore. However, any online backups you created for the stopped cloud are still retained and can be restored. The cloud provider continues to charge for these saved online backups.
Stopped clouds are displayed in your Clouds dashboard with a red status.
You can remove clouds that have either stopped successfully or are in a failed/inconsistent state. Follow these steps:
You can easily add Publish instances in addition to the default three nodes (one Dispatcher, one Author instance, and one Publish instance).
The new node is added with a blue status and initialized. Node initialization may take several minutes.
To delete a node you added earlier, click Actions > Scale and then remove the node.
Online backups of the cloud are saved with your cloud provider. For Rackspace, backups are currently limited to 5 GB and are stored on Cloud Files. Backups are supported for Rackspace CQ clouds created using the July 2012 version of Cloud Manager or later.
Do not schedule backups until the cloud is in the Running state.
You can restore a stopped cloud from online backups.
Backed up CQ clouds having more than one Dispatcher or Publish instance are always restored in the 1-1-1 configuration (1 Dispatcher, 1 Author instance, and 1 Publish instance).
After a cloud is restored from backups, any future scheduled backups are unscheduled.
The Go To Publish/Go To Author buttons access the Publish/Author instances using DNS. Sometimes, right after restarting or restoring a cloud, you may not be immediately able to access these instances using DNS. As a workaround, access the instances using their IP addresses.
The activity log lists package/service installation or uninstallation events, as well as any issues that your CQ cloud may have encountered.
You can filter the activity log such that only activities by a specified user are displayed.
You can Love a package, bookmark it (*), or read its EULA. Packages that you bookmark are displayed in the Packages dashboard along with the packages you installed.
The Packages dashboard displays the packages that you've bookmarked.
Cloud Manager lets you easily download the ZIP archive for a package from Package Manager. Follow these steps:
More Adobe and third-party services will be available for installation soon.
Installed service/package statuses (Click here to view a larger version of the screenshot)
You can upload packages to a private folder in your company's Package Share hierarchy. Follow these steps:
If you want to share an uploaded package with another company or make the package publicly accessible, email the details of your request to firstname.lastname@example.org.
||Installing, starting, initializing, or restarting
||Paused or pausing
|Red||Stopped or stopping
SSH into the Dispatcher instance and run the following commands: