Learn about metrics and monitoring. Discover what's possible.
- [Narrator] Okay, so you've decided to adopt Amazon Web Services, or AWS, as your infrastructure as a service partner. Whether you are migrating existing applications or building natively in AWS, you need monitoring tools to help you operate as efficiently and cost effectively as possible. Let me give you an analogy. Suppose you are on a road trip, driving along, you glance down and see that you are running low on gas. By the time you receive a low fuel alert, you could be out of luck if you are in a remote area.
While the fuel gauge is giving you a metric, it's of limited value on it's own. Now imagine that the gps system in your car is integrated with the car's trip computer combining fuel state and fuel consumption data from the trip computer with route information from the nav system, an alert can trigger earlier in the process. This alert will let you know that you are about to pass the last gas station along your route. Depending on your level of comfort, you may choose to automatically reroute to a fueling station when your destination is farther away than your projected distance to empty.
That is the power of a well designed monitoring solution. There are many different components to AWS. Let's start by exploring some of the things that are near and dear to the heart of a chief financial officer. Notice how these aren't all that technical but still very important to understand. From an organizational prospective, you will need to have a keen understanding of the overall amount that is being spent on AWS. This is especially true if you are using multiple AWS accounts.
As you drill into a given AWS account, you will be interested to know how much you spend on a region by region basis. From a service costing perspective, you want to be able to understand the total cost of operating each service that you have. Let's move from financial monitoring and talk about technical monitoring. With traditional applications and servers, common items to monitor include CPU utilization, memory utilization, disk activity and network activity. Of course, in AWS, there are many AWS specific items which you may never have encountered before.
Certainly, you will want to monitor the health of individual EC2 instances. If you are using any of the load balancing options within AWS, you'll want to ensure that those are performing as expected. If any of your services are designed for auto scaling, you may be interested in scale in and scale out events. You may be using other AWS services and will need to monitor them as well. Examples of these services include: relational database services, kinesis streams and simple q service q's.
Beyond standard monitoring and alerting, we will explore how to take action based on a monitoring event. In any system it is important to understand the metrics available to monitor the components of that system. Combining metrics with deep knowledge about system behavior lets you create an effective, actionable monitoring solution.
This course is also part of a series designed to help you prepare for the AWS Certified SysOps Administrator – Associate certification exam.
This course includes trademarks owned by Amazon Web Services. This course has not been prepared, approved, or endorsed by Amazon Web Services.
- Exploring monitoring tools
- Understanding CloudWatch
- Using CloudWatch alarms
- Monitoring EC2 memory
- Using AWS Config
- Understanding AWS logging and ElasticSearch
- Combining CloudWatch and Lambda