Setting up monitoring on AWS is hard. There are countless monitoring possibilities on AWS. Overlooking the important settings is easy. Monitoring Jump Starts connect you with all relevant AWS sources for comprehensive monitoring coverage.
Jump Starts are CloudFormation templates or Terraform modules that you can deploy to your AWS account to setup CloudWatch Alarms, CloudWatch Event Rules, and much more. Events are sent to Slack or Microsoft Teams.
At the moment, you can monitor:
Monitoring goal | CloudFormation Action | CloudFormation Template URL |
---|---|---|
AWS basics | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot.yml |
Application Load Balancer (ALB) | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-alb.yml |
Auto Scaling Group | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-auto-scaling-group.yml |
EC2 instance | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-ec2-instance.yml |
EC2 instances | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-ec2-instances.yml |
EFS file system | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-efs.yml |
Elastic Beanstalk | Launch Stack and don't forget to put the marbot-elastic-beanstalk.config file into your .ebextensions folder! | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-elastic-beanstalk.yml |
ElastiCache memcached cluster | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-elasticache-memcached.yml |
Elasticsearch domain | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-elasticsearch.yml |
VPC interface endpoint | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-interface-endpoint.yml |
CloudFormation Drift Detection | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-cloudformation-drift.yml |
CloudFront | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-cloudfront.yml |
Lambda function | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-lambda-function.yml |
NAT Gateway | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-nat-gateway.yml |
RDS database instance | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-rds.yml |
RDS cluster (Aurora) | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-rds-cluster.yml |
Redshift cluster | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-redshift.yml |
Repeated task | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-repeated-task.yml |
Reserved Instance | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-reserved-instance.yml |
SQS queue | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-sqs-queue.yml |
Synthetics Website | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-synthetics-website.yml |
WorkSpaces | Launch Stack | https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-workspaces.yml |
To update a Jump Start:
- Visit the AWS Management Console.
- Double-check the selected AWS region.
- Search for marbot.
- Select a stack and grab the matching CloudFormation Template URL from the table above (the Description has to match the Monitoring goal here!).
- Click on Update.
- Select Replace current template and paste the CloudFormation Template URL into the Amazon S3 URL field.
- Click on Next.
- Scroll to the bottom of the page and click on Next.
- Once again, scroll to the bottom of the page and click on Next.
- Scroll to the bottom of the page and select I acknowledge that AWS CloudFormation might create IAM resources.
- Click on Update stack.
- Repeat this procedure for every CloudFormation stack that is based on the updated Jump Starts.
- If you use more than one AWS region, repeat the procedure for each region.
All templates are published under Apache License Version 2.0.