Cloud CORE is an open source tool that helps you calculate real-time, resource-specific costs in Amazon Web Services (AWS). This video explains how to best use the tool. Cloud CORE was developed by engineers at Blue Matador.

Every innovative team has two competing interests: rapid feature development and production stability. Blue Matador enables the best of both worlds, where time-strapped developers and DevOps teams only get notified of actionable events that threaten production. See how it works with this demo from our Founder and CEO Matthew Barlocker.

Monitoring freeable memory will help you know when it is time to scale your Amazon RDS cluster. Freeable memory is not reported by the database, but rather by the OS. Freeable memory is the combination of unused and temporarily used memory. It is the memory that the system can grant without adverse effects. When an Amazon RDS instance runs out of freeable memory the OS may do up to three things.

In another video we laid out seven critical metrics you should monitor with AWS CloudWatch to know when to scale your database cluster. This video will focus on the first of those metrics, database connections.

RDS is Amazon's managed relational database service. While RDS manages your databases maintenance, uptime and upgrade it is your responsibility to determine the cluster's scale and capacity. So the big question is when do you need to scale up? To answer this question you should understand and monitor seven metrics for each server in your cluster. They are: Database connections, Freeable memory, CPU credit balance, Free local storage, Replica lag, Commit latency, Select latency

A common problem with Amazon CloudFront and Amazon S3 hosting deals with negative TTLs. Matthew from Blue Matador outlines the steps needed to correct this problem. Understand eventual consistency in S3. New items may take time to propagate through redundant systems and be available in all locations., Understand CloudFront's default policy for handling errors, like 403 forbidden, is to cache that error for 5 minutes., The solution is to modify distribution settings in CloudFront.

Before Blue Matador Canopy was mostly using CloudWatch to monitor their AWS and Kubernetes infrastructure. Things they didn't know they should monitor would break. Now, they have moved from being proactive rather than reactive and are monitoring all of the unknowns. Find out more at www.bluematador.com

In this video Matthew Barlocker, the CEO of Blue Matador, will show you how to get custom error pages in AWS S3 and/or Cloudfront.

In this video Blue Matador will walk you through how to set up Amazon SNS to receive CloudWatch alarms by email or text message. Using AWS CloudWatch isn't hard, it's just tedious with an unusable UI. We are experts in AWS and Kubernetes monitoring and have built Blue Matador to make the lives of DevOps professionals easier. Learn more about our cloud monitoring solution and other CloudWatch resources at www.bluematador.com.