AEM OpenCloud on AWS
Open-source infrastructure platform for running AEM
This Partner Solution deploys an Adobe Experience Manager (AEM) OpenCloud architecture on the Amazon Web Services (AWS) Cloud with high-availability features, which includes Amazon Elastic Compute Cloud (Amazon EC2) Auto Scaling, Elastic Load Balancing, and Amazon CloudFront.
This deployment of AEM OpenCloud uses two instances each for Author-Dispatcher, Publish-Dispatcher, and Publish across multiple Availability Zones. Amazon CloudWatch alarms are configured to monitor the average CPU utilization of the Publish-Dispatcher Auto Scaling group. The Orchestrator application manages AEM replication and flush agents as instances are created and terminated.
Other services used by this Quick Start include AWS Certificate Manager (ACM), AWS Lambda, Amazon Route 53, AWS Secrets Manager, Amazon Simple Notification Service (Amazon SNS), Amazon Simple Queue Service (Amazon SQS), Amazon Simple Storage Service (Amazon S3), and AWS Systems Manager.
Shine’s AWS and AEM expertise has been key for running non-cloud-native AEM successfully on AWS. Shine’s approach to partnering combined with technical skills in delivery and training to uplift our workforce has been key to our success in building a solution that we now support ourselves.
—Brendan Colson, National Australia Bank
This Partner Solution was created by Shine Solutions Group in collaboration with AWS. Shine Solutions Group is an AWS Partner.
What you'll build
How to deploy
Costs and licenses
What you'll build
This Partner Solution sets up the following:
- A highly available architecture that spans two Availability Zones.*
- A virtual private cloud (VPC) configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.*
- In the public subnets:
- Managed network address translation (NAT) gateways to allow outbound internet access for resources in the private subnets.*
- A Linux bastion host in an Auto Scaling group to allow inbound Secure Shell (SSH) access to EC2 instances in public and private subnets.*
- An internet-facing Classic Load Balancer (CLB) for routing traffic to the content delivery web server.
- In the private subnets:
- Content management EC2 instances are designed for active/passive standby and are not part of an Auto Scaling Group.
- Content delivery EC2 instances are deployed into an Auto Scaling group.
- Content delivery web server EC2 instances are deployed into an Auto Scaling group.
- Content management web server EC2 instances are deployed into an Auto Scaling group.
- Utility EC2 instances are deployed into their own Auto Scaling group.
- An internal CLB for routing traffic to the active content management server.
- An internal CLB for routing traffic to the content management web server.
- Amazon CloudFront for content delivery.
- EC2 Amazon Machine Image (AMI) for each AEM OpenCloud role.
- ACM for storing SSL certificates.
- Amazon CloudWatch for monitoring deployed services.
- AWS Lambda to support provisioning of AEM OpenCloud on AWS.
- An Amazon Route 53 private hosted zone for internal Domain Name System (DNS) lookups.
- AWS Secrets Manager to store the AEM keystore password and AEM SSL private key.
- Amazon SNS for receiving Auto scaling group alarm notifications.
- Amazon Simple Queue Service (SQS) for forwarding Auto scaling group alarm notifications to utility EC2 instances.
- An Amazon S3 bucket for storing AEM OpenCloud stack assets.
- AWS Systems Manager to store AEM OpenCloud configuration parameters.
* The template that deploys the Partner Solution into an existing VPC skips the tasks marked by asterisks and prompts you for your existing VPC configuration.
How to deploy
To deploy AEM OpenCloud, follow the instructions in the deployment guide. The deployment process, which takes about 1–1.5 hours, includes these steps:
- If you don't already have an AWS account, sign up at https://aws.amazon.com, and sign in to your account.
- Launch the Partner Solution. You can choose from the following two options:
- Test the deployment.
Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.
Costs and licenses
This Partner Solution requires a license for Adobe Experience Manager. Contact your Adobe sales representative or Adobe partner for a full Adobe AEM on-premise license. When you launch the Partner Solution, place the license key in the Amazon S3 installation bucket, and specify its location.
Warning: If you don’t have a full Adobe AEM on-premise license, the deployment will fail.
You are responsible for the cost of the AWS services and any third-party licenses used while running this solution. There is no additional cost for using the solution.
This solution includes configuration parameters that you can customize. Some of these settings, such as instance type, affect the cost of deployment. For cost estimates, refer to the pricing pages for each AWS service you use. Prices are subject to change.
Tip: After you deploy a solution, create AWS Cost and Usage Reports to track associated costs. These reports deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. They provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information, refer to What are AWS Cost and Usage Reports?