## Prerequisites
Before launching CMS Enterprise, make sure you have:
* An existing AWS Account.
* An existing EC2 Key Pair.
* A preexisting VPC in the region you intend to launch in. If you don't have one, launch this stack to create one first.
You'll also need to subscribe to Solodev on the AWS Marketplace. Click the button below to get started, then return to this article and follow the instructions below:
!!! Note:
Already subscribed? Skip ahead to [Launch this software](#launch-this-software).
!!!
## AWS Setup
At the top of the AWS Marketplace listing page for the CMS Enterprise, click the **“Continue to Subscribe”** button.
### Subscribe to this Software
By subscribing, you gain access to a comprehensive suite of tools and features designed to enhance your productivity and streamline your workflow.
1. Review and accept the **"Terms and Conditions"**.
2. Click **"Continue to Configuration"**.
### Configure this Software
Specify the basic configuration such as the software version and the region you wish to launch the stack. Click on the **"Continue to Launch"** button to proceed.
1. Select a fulfillment option. Fulfillment options relate to how software products are delivered and deployed. This software is packaged as a virtual appliance and deployed on Amazon EC2 instances.
2. Select a software version. The latest version of Solodev CMS Micro is always recommended.
3. When selecting an available AWS Region for hosting, you may want to consider a region that is closer to your users to help reduce your network latency.
4. Click **"Continue to Launch."**
### Launch this software
Review the launch configuration details and follow the instructions to launch this software.
1. **Choose an Action**
2. Click **"Launch"**.
#### Choose an Action
There are two options for configuring your Solodev CMS Enterprise: Launch CloudFormation or Copy to Service Catalog. Select one from the menu.
## Fill Out the CloudFormation Stack Wizard
Continue with the preselected CloudFormation Template. The Amazon S3 template URL (used for the CloudFormation configuration) should be pre-selected. Click **"Next"** to continue.
The following parameters must be configured to launch your Solodev CMS CloudFormation stack:
**Step 1:** Stack Name
**Parameter Name** | **Description**
:--- | ---
Stack name | The name of your stack. Please note the name must be all lowercase, start with a letter and only contain alphanumeric characters.
**Step 2:** Network Settings
**Parameter Name** | **Description**
:--- | ---
VPCID | Choose which VPC the application should be deployed to
PublicSubnet1ID | The ID of the public subnet in Availability Zone 1 in your existing VPC (e.g., subnet-a0246dcd)
PublicSubnet2ID | The ID of the public subnet in Availability Zone 2 in your existing VPC (e.g., subnet-b1236eea)
InstanceType | The EC2 instance type you wish to launch
InstanceCount | Number of instances behind the load balancer. Minimum 2 required for high availability.
KeyName | Name of an existing EC2 KeyPair to enable SSH access to the instances
AmiAlias | A user-defined name identifying the Amazon Machine Image (AMI) to launch. Leave the default unless Solodev support has given you a specific alias to use.
**Step 3:** CMS Settings
**Parameter Name** | **Description**
:--- | ---
AdminUser | The solodev admin username
AdminPassword | The solodev admin password
AdminCidrIpAccess | The CIDR range allowed to reach the admin layer. Change this from the default `127.0.0.1/32` to your own IP or CIDR range before launching.
DatabaseUsername | The database admin account username
DatabasePassword | The database root password
**Step 4:** Optional: Website Settings
**Parameter Name** | **Description**
:--- | ---
WebsiteURL | Name of initial Solodev website
CertificateArn | CertificateArn for SSL cert that matches the FQDN above. Please visit the AWS Certificate Manager
**Step 5:** Optional: Network Settings
**Parameter Name** | **Description**
:--- | ---
AdminEnabled | Enable admin layer
RedisEnabled | Enable Redis ElastiCache cluster
CookbookURL | https://s3.amazonaws.com/solodev-cms/chef/1.2/cookbooks.tar.gz. Download and host on your own S3 bucket or use this URL
CidrIpAccess | Please set CIDR to x.x.x.x/32 to allow one specific IP address access, 0.0.0.0/0 to allow all IP addresses access, or another CIDR range
DeletionPolicy | Experimental: Deletion Policy (Retain, Delete, Snapshot)
StorageEncrypted | Enable encryption for both Database (RDS) and Filesystem (EFS)
**Step 6:** Optional: SSO Settings
If your organization uses single sign-on, configure it here. Leave these blank to sign in with a standard Solodev admin account instead.
**Parameter Name** | **Description**
:--- | ---
SsoProviderUrl | The issuer URL of your OpenID Connect provider.
SsoClientId | The client ID registered with your SSO provider for this CMS instance.
SsoClientSecret | The client secret paired with the SSO Client ID above.
**Step 7:** Confirm your stack details
Click the **"Next"** button on the bottom of the screen to continue.
**Step 8:** Specify Options
Generally speaking, no additional options need to be configured. If you are experiencing continued problems installing the software, disable **"Rollback on failure"** under the **"Advanced"** options. This will allow for further troubleshooting if necessary. Click on the **"Next"** button to continue.
**Step 9:** Review
Review all CloudFront details and options. Ensure that the "I acknowledge that AWS CloudFormation might create IAM resources with custom names" checkbox is selected as well as the "I acknowledge that AWS CloudFormation might require the following capability: CAPABILITY_AUTO_EXPAND" checkbox. Click on the **"Create"** button to launch your stack.
## Monitor the CloudFormation Stack Creation Process
Upon launching your CloudFormation stack, you can monitor the installation logs under the **"Events"** tab. The CloudFormation template will launch several stacks related to your Solodev instance, including EFS, EDS, and EC2. If you encounter any failures during this time, please visit the Common Issues page to begin troubleshooting.
!!! Note:
Creating a stack may take up to 30 min depending on the InstanceType you have chosen. During this time, your AWS session may expire, however the stack will continue to build. In such case simply re-login to your AWS account.
!!!
## View CloudFormation Stack Outputs
If your stack builds successfully, you will see the green "CREATE_COMPLETE" message. Click on the primary stack and view the **"Outputs"** tab. You will find the load balancer URL for the Solodev backend. Point your primary domain (mydomain.com) and a dedicated backend domain/subdomain (solodev.mydomain.com) to this URL.
## Next Steps
### Login to Solodev
Visit the IP address or the backend domain you previously configured. Log in to Solodev using the username and the password you configured on your stack.
### Add your First Website
Please [follow this link](/websites/add-website/) to learn more about Solodev and to learn how to build your first website.
Moving your Solodev CMS to a different server, or need help with a backup and restore? Contact Solodev support.
