Book Image

AWS Certified SysOps Administrator ??? Associate Guide

By : Marko Sluga
Book Image

AWS Certified SysOps Administrator ??? Associate Guide

By: Marko Sluga

Overview of this book

AWS certifications are becoming one of the must have certifications for any IT professional working on an AWS Cloud platform. This book will act as your one stop preparation guide to validate your technical expertise in deployment, management, and operations on the AWS platform. Along with exam specific content this book will also deep dive into real world scenarios and hands-on instructions. This book will revolve around concepts like teaching you to deploy, manage, and operate scalable, highly available, and fault tolerant systems on AWS. You will also learn to migrate an existing on-premises application to AWS. You get hands-on experience in selecting the appropriate AWS service based on compute, data, or security requirements. This book will also get you well versed with estimating AWS usage costs and identifying operational cost control mechanisms. By the end of this book, you will be all prepared to implement and manage resources efficiently on the AWS cloud along with confidently passing the AWS Certified SysOps Administrator – Associate exam.
Table of Contents (26 chapters)

Monitoring EC2

When working with our virtual machine instances in EC2, we are provided with standard metrics that can help us determine the performance and state of our instance. For each instance, we are able to enable detailed metrics if required and install a CloudWatch agent that can provide us with custom metrics and the ability to export system and application logs into the CloudWatch Logs component.

By default, the CloudWatch metrics being collected for EC2 instances are any metrics related to CPU, disk, and network utilization as well as the status check that determines the instance health. Most new users to EC2 are astonished to find that no information about memory usage is provided within the CloudWatch metrics. There is a simple reason for that: AWS has no access to the operating system and thus has no way of correctly determining the amount of memory the instance...