Monitoring Flashcards
Cloud Watch
used to monitor AWS services EC2, ELB, and S3’monitor your environment by configuring and viewing CloudWatch metrics.
CloudWatch Metrics
EC2 per-instance metrics: --CPUUtilization --CPUCreditUsage S3 Metrics: --NumberOfObjects --BucketSizeBytes ELB Metrics: --RequestCount --UnhealthyHostCount
Detailed vs. Basic level monitoring
Basic: data is available automatically in 5-minute periods at no charge
Detailed: data is available in 1-minute periods.
CloudWatch Alarms
can be created to trigger alerts( or other actions in your AWS accounts, such as an SNS topic), based on threshold you set on CloudWatch metrics.
Auto Scaling
heavily utilizes Cloudwatch – relying on threshold and alarms to trigger the addition(or removal) of instances from an auto scaling group.
CloudWatch EC2 Monitoring
System Status Checks;(things out of our control)
Instance Status Checks(things we do control)
System Status Checks
Loss of network connectivity; loss of system power; software issues on the physical host hardware issues on the physical host How to solveL generally stopping and restarting the instance will fix the issue. This causing the instance to launch on a different physical hardware device.
Instance status checks
Failed system status checks Misconfigured networking or startup configuration exhausted memory corrupted file system incompatible kernel
How to solve: a reboot, or solving the file system configuration issue.
By default, Cloudwatch will automatically monitor metrics that can be viewed at the host level(not the software level)
CPUUtiliztion
Network in/out
CPUCreditBalance
CPU Credit Usage
OS level metrics that required a third party script(perl) to be installed(provided by AWS)
Memory utilization, memory used, and memory available. DIsk Swap Utilization Disk Space utilization, disk space used, disk space avaiable.
Cloud Trail
API logging service that logs ALL API calls made to AWS
logs are placed into a designated S3 bucket – highly available by default.
logs help when addressing security concerns, by allowing you to view what actions users on your AWS account have performed.
can log ever single action taken in your account.
VPC Flow Log
allow you to collect information about the IP traffic going to and from network interfaces in your VPC.
data is stored in a log group in cloudwatch
can be created on a specific VPC, Subnet or Network interface
include all network interfaces in that VPC or subnet.
each network interface will have its own unique log stream.
you can set the log to capture in “real-time”. the capture window is about 10 minutes, the data is published.
consist of network traffic for a specific 5-tuple.
5-tuple
is a set of 5 different values that comprise a TCP/IP connection.
- source IP address
- source port number
- destination IP address
- destination port number
- Protocol
Benefits of VPC flow logs
troubleshoot why certain traffic is not reaching an EC2 instance
added security layer by allowing you to monitor that traffic that reaches your EC2 instances.
Limitations of VPC flow logs
Traffics not captured by VPC Flow logs:
- traffic between an EC2 instance and an Amazon DNS Server
- Traffic generated by request for instance metadata
- DHCP traffic.