CMS Enterprise Logo

CMS Enterprise

An enterprise-grade content management system built from the ground up for
Amazon Web Services (AWS).

Diagram

SUBSCRIBE

Solodev CMS Enterprise is designed for high-availability websites and apps that require a secure, scalable, and redundant infrastructure powered by the AWS Cloud. Solodev CMS Enterprise deploys a cluster of three servers, complete with load balancing and auto-scaling services. This architecture allows your websites and apps to meet the most demanding traffic while maintaining the highest levels of uptime.

#Prerequisites

#CMS Subscription

The following steps cover the setup of the CMS Enterprise on the AWS Marketplace. Click the “Continue to Subscribe” button at the top of the AWS Marketplace listing page to continue the process. By subscribing, you gain access to a comprehensive suite of tools and features designed to enhance your productivity and streamline your workflow.

  1. Subscribe to Solodev on the AWS Marketplace. SUBSCRIBE
  2. Review and accept the "Terms and Conditions".
  3. Click "Continue to Configuration".

CMS Enterprise Configuration

#Configure Software

  1. Choose a fulfillment option and software version to launch this software.

CMS Enterprise Configure

NameDescription
Fulfillment optionSelect a fulfillment option.
Software versionSelect the software version. The latest version of Solodev CMS Enterprise is always recommended.
RegionSelect the AWS Region.
  1. Click "Continue to Launch."

CMS Enterprise Continue to Launch

#Launch Software

Review the launch configuration details and follow the instructions to launch this software.

To continue the installation, click the Launch button below and follow the outlined steps.

LAUNCH CMS ENTERPRISE

#Create Stack

  1. Create a stack.

CMS Enterprise Create Stack

  1. Click Next.

#Stack Details

#Provide a stack name
  1. Provide a stack name. Stack name must be 1 to 128 characters, start with a letter, and only contain alphanumeric characters.

CMS Enterprise stack name

#Parameters
  1. Specify the parameters in the network settings section.

CMS Enterprise network settings

NameDescription
VPCIDChoose which VPC the Application should be deployed to.

An Amazon Virtual Private Cloud (VPC) is a dedicated environment that lets you launch the AWS resources that power your CMS Micro in an isolated virtual network. If you do not have a VPC, you will need to create one in your VPC Console. For instructions on how to create a VPC, click here for instructions .
PublicSubnet1IDThe ID of the public subnet in Availability Zone 1 in your existing VPC (e.g., subnet-a0246dcd).

A subnet is a range of IP addresses contained in your VPC. You can create AWS resources, such as EC2 instances, in specific subnets, enabling you to group network resources more efficiently. If you do not have any existing subnets, you will need to create one in your Subnet Console. For instructions, click here .
PublicSubnet2IDThe ID of the public subnet in Availability Zone 2 in your existing VPC (e.g., subnet-b1236eea).

A subnet is a range of IP addresses contained in your VPC. You can create AWS resources, such as EC2 instances, in specific subnets, enabling you to group network resources more efficiently. If you do not have any existing subnets, you will need to create one in your Subnet Console. For instructions, click here .
InstanceTypeCMS Micro runs on a single Amazon Elastic Compute (EC2) instance and is defaulted to run on a recommended t2.medium server. Depending on your traffic needs, you can select an instance size from the available options in the menu.

To learn more about which instance to choose based on your traffic needs, click here .
InstanceCountNumber of instances behind load balancer. Minimum 2 required for high availability.
KeyNameName of an existing EC2 KeyPair to enable SSH access to the instances.

An Amazon EC2 key pair is a set of security credentials consisting of a public and private key that verify a user’s identity when connecting or communicating with an EC2 instance. Select an existing security group from the menu or configure a new security group using the form provided. If you do not have a Key Pair, you will need to create one in your Key Pair Console. For instructions click here .
AmiAliasAn AMI Alias refers to a user-defined name or identifier for an Amazon Machine Image (AMI) that simplifies the process of referring to an AMI. Click here to learn more about AMIs.
  1. Specify the CMS Settings.

CMS Enterprise CMS Settings

NameDescription
AdminUserThe solodev admin username to login onto your CMS.
AdminPasswordThe solodev admin password to login onto your CMS.
AdminCidrIpAccessPlease change CIDR from 127.0.0.1/32 to a specific IP or another CIDR range. For more information, click here.
DatabaseUsernameThe database admin account username.
DatabasePasswordThe database root password.
  1. Optional: Website Settings.

CMS Enterprise CMS Network Settings Optional

NameDescription
WebsiteUrlName of initial Solodev website.
CertificateArnCertificateArn for SSL cert that matches the FQDN above. Please visit the AWS Certificate Manager .
  1. Optional: Network Settings.

CMS Enterprise CMS Settings Optional

NameDescription
RedisEnabledEnable Redis ElastiCache cluster.
CookbookURLDownload and host on your own S3 bucket or copy this URL.
CidrIpAccessPublic CIDR range for web servers behind load balancer.
DeletionPolicyA Deletion Policy is a configuration that you can set for resources in AWS CloudFormation templates to specify what should happen to the resource when its stack is deleted.
StorageEncryptedEnable encryption for both Database (RDS) and Filesystem (EFS).
  1. Optional: SSO.

CMS Enterprise CMS SSO Optional

NameDescription
SsoProviderUrlIssuer URL of your OpenID Connect provider.
SsoClientIdUnique identifier assigned to a client application that is registered with an AWS Single Sign-On (SSO) service, used to authenticate and authorize the application to access SSO resources.
SsoClientSecretConfidential key assigned to a client application registered with an AWS Single Sign-On (SSO) service, used in conjunction with the SSO Client ID to authenticate the application and secure access to SSO resources.
  1. Click Next.

#Configure Stack Options

  1. Add a new tag. This step is optional.

Tags (key-value pairs) are used to apply metadata to AWS resources, which can help in organizing, identifying, and categorizing those resources. You can add up to 50 unique tags for each stack. If you need more information about tags, click here.

CMS Enterprise tags

  1. Specify an existing AWS Identity and Access Management (IAM) service role that CloudFormation can assume. This step is optional.

CMS Enterprise permissions

  1. Select the stack failure options.

CMS Enterprise failure

NameDescription
Behavior on provisioning failureSpecify the roll back behavior for a stack failure..
Delete newly created resources during a rollbackSpecify whether resources that were created during a failed operation should be deleted regardless of their deletion policy.

To learn more about the stack failure options, click here .

#Advanced options

  1. You can set additional options for your stack, like notification options and a stack policy. For more information, click here .

CMS Enterprise advanced options

  1. Click Next.

#Review and create

  1. Review your settings.

  2. Acknowledge the AWS CloudFormation terms.

CMS Enterprise capabilities

  1. Click Submit.

#Stacks

  1. Watch your CMS being created! Once the status changes from CREATE_IN_PROGRESS to CREATE_COMPLETE, you can access your CMS.
  1. Click on the Outputs tab and copy the AdminUrl value.

CMS Enterprise Stack Outputs

  1. Open your preferred browser and paste the AdminUrl value to access the CMS login page. Use the Admin Username and Admin Password provided in the stacks output to log in.

Solodev CMS Login Screen

#Next Steps

#Add your first website

Please follow this link to learn more about Solodev and to learn how to build your first website.