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

LAUNCH CMS MICRO

1. Create a stack.

2. Click Next.

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

1. Specify the parameters in the setup section.

2. Optional: SSO.

3. Click Next.

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.

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

3. Select the stack failure options.

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

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

2. Click Next.

1. Review your settings.

2. Acknowledge the AWS CloudFormation terms.

3. Click Submit.

1. Watch your CMS being created! Once the status changes from CREATE_IN_PROGRESS to CREATE_COMPLETE, you can access your CMS.

2. Click on the Outputs tab and copy the AdminUrl value.

3. 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.

1. Select Launch through EC2.

2. Click Launch.

Create virtual machines, or instances, that run on the AWS Cloud. Quickly get started by following the simple steps below.

1. Name and tags. Give your instance a name. You can also add additional tags (Optional).

2. Application and OS Images (Amazon Machine Image). An AMI contains the software configuration (operating system (OS), application server, and applications) required to launch your instance.

For more information about Amazon Machine Image, click here .

3. Instance Type. Select an instance type that meets your computing, memory, networking, or storage needs.

To learn more about which instance to select based on your traffic needs, click here .

4. Key Pair. You can use a key pair to securely connect to your instance. Ensure that you have access to the selected key pair before you launch the instance.

5. Network Settings. Here you can create or select an existing security group, create an instance that can connect using SSH, and more.

6. Configure storage. Specify the storage options for the instance.

For more information about storage, click here .

7. Click Launch Instance.

8. You will get a success message. Click on the ID to access your EC2 Instance.

1. Check the Instance State and Status Check of your instance. Once your instance state changed from Pending to Running, click on the instance you created to access it.

2. Click on your Public IPv4 address to access the login page.

3. To log in, use solodev as the username and your instance ID as the password.

1. Select Launch from Website

2. EC2 Instance Type. CMS Micro runs on a single Amazon Elastic Compute (EC2) instance and is defaulted to run on a recommended t2.large 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 .

3. VPC Settings. 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 .

4. Subnet Settings. 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 .

5. Security Group Settings. A security group acts as a firewall that controls the traffic allowed to reach one or more instances. You can create a new security group or choose one of your existing groups. Select an existing security group from the menu or configure a new security group using the form provided. Name your security group and give it a description.

To learn more about security groups, click here .

6. Key Pair Settings. 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 .

7. Click Launch.

8. You will receive a success message to view your instance. Click on EC2 Console.

1. Check the Instance State and Status Check of your instance. Once your instance state changed from Pending to Running, click on the instance you created to access it.

2. Click on your Public IPv4 address to access the login page.

3. To log in, use solodev as the username and your instance ID as the password.