Step 1: Launch the stack

This automated AWS CloudFormation template deploys amazon-cloudwatch-monitoring-framework.template for Apache, NGINX, and Puma workloads in the AWS Cloud.

Note

You are responsible for the cost of the AWS services used while running this solution. For more details, refer to the Cost section in this guide, and refer to the pricing webpage for each AWS service used in this solution.

1. Sign in to the AWS Management Console and select the button to launch the framework AWS CloudFormation template.

   

2. The template launches in the US East (N. Virginia) Region by default. To launch the solution in a different AWS Region, use the Region selector in the console navigation bar.

3. On the Create stack page, verify that the correct template URL is in the Amazon S3 URL text box and choose Next.

4. On the Specify stack details page, assign a name to your solution stack. For information about naming character limitations, refer to IAM and STS Limits in the AWS Identity and Access Management User Guide.

5. Under Parameters, review the parameters for Apache workload. Modify them as necessary. This solution uses the following default values.

   Parameter	Default	Description
   Apache Tagging Schema	{"Key":"CW-Dashboard","Value":"Apache"}	Tagging schema to identity apache workload instances. Note Tags are key sensitive.
   Apache Demo Instance	Yes	Demo EC2 instance with needed configurations and Apache workload running.
   NGINX Tagging Schema	{"Key":"CW-Dashboard","Value":"Nginx"}	Tagging schema to identity NGINX workload instances. Note Tags are key sensitive. Leave empty if you don’t want to monitor NGINX workload.
   NGINX Demo Instance	Yes	Demo EC2 instance with required configurations and NGINX workload running.
   Puma Tagging Schema	{"Key":"CW-Dashboard","Value":"Puma"}	Tagging schema to identity Puma workload instances. Note Tags are key sensitive. Leave empty if you don’t want to monitor Puma workload.
   Puma Demo Instance	Yes	Demo EC2 instance with required configurations and Puma workload running.

6. Choose Next.

7. On the Configure stack options page, choose Next.

8. On the Review page, review and confirm the settings. Check the box acknowledging that the template will create AWS Identity and Access Management (IAM) resources.

9. Choose Create stack to deploy the stack.

   You can view the status of the stack in the AWS CloudFormation Console in the Status column. You should receive a CREATE_COMPLETE status in approximately five minutes.

Note

In addition to the primary AWS Lambda functions TagHandler & DashboardHandler this solution includes the solution-helper Lambda function, which runs only during initial configuration or when resources are updated or deleted.

When you run this solution, you will notice these Lambda functions in the AWS console. Only the primary lambda functions are regularly active. However, you must not delete the solution-helper function, as it is necessary to manage associated resources.