Module 10

Cloud Watch

  • Main service that will gather and deal with metrics from resources. We can also have custom data sources. Only over resources we own

  • Collects and tracks metrics for AWS services across Regions in a metric repository

  • Collects logs by using Amazon CloudWatch Logs

  • Supports built-in AWS service metrics or custom metrics

  • Calculates statistics from metrics and anddisplays graphs of the metric statistics

  • Provides alarms for responsive event-driven architectures

  • Provides notifications to make changes to monitored resources

CloudWatch Alarms

A notification via email or SMS can be sent with Amazon SNS

EventBridge

  • We can set up set up EventBride in a way to listen to events in AWS services and third party instances and act off it. This can be based on a schedule OR listening to events

Example: GitHub commit triggers a Lambda function to do XYZ.

Example: Someone uploads a file to a S3 Bucket, we do sum idk

We don't have to have full control over what it's listening to

  • Processes events with an event bus or a pipe

  • Pipes are point-to-point integrations between one source and one target

  • Event buses are routers that receive events and optionally delivers them to one or multiple targets.

  • Makes routing decisions with configurable rules

  • Rules run based on matching an event pattern or on a schedule with Amazon EventBridge Scheduler.

  • Targets can be in another AWS account, in another Region, or in both

Amazon EC3 Auto Scaling

  • Manages a logical collection of Amazon Elastic Compute Cloud (Amazon EC2) instances called an Amazon EC2 Auto Scaling group across Availability Zones

  • Launches or retires EC2 instances configured by launch templates•Resizes based on events from scaling policies, load balancer health check notifications, or schedule actions

  • Integrates with Elastic Load Balancing (ELB) to send new instance registrations and receive health notifications

  • Balances the number of instances across Availability Zones

EC2 Auto Scaling group components

This can be scaled up or down

Styles of scaling

Scheduled Actions
Dynamic Policies
Predictive Policy (AI)

Scale based on a date and time

Scale based on tracked metrics

Scales based on previous traffic patterns with machine learning

Are for predictable workloads

Are for moderately spiky workloads

Is for workload traffic that can be predicted with a pattern

Other options

Scaling AWS Databases

Elastic Load Balancer (ELB)

  • Distributes traffic across multiple targets in one or more Availability Zone

  • Can receive public or private traffic

  • Monitors the health of registered targets with health checks•Routes traffic to only healthy targets

  • Scales based on incoming traffic

Load Balancer Types

Load Balancer Components

Route53

  • Your own DNS server and can be configured in any way with records and routing

  • Is a DNS web service that manages domain name registrations and provides hosted zones.

  • Provides authoritative name servers for DNS resolution

  • Performs DNS routing to route traffic to healthy endpoints•Performs health checks against IP addresses or domains to manage Availability Zone or Regional failovers

  • Can monitor CloudWatch alarms

  • Supports multiple routing options

Traditional DNS

Route 53 DNS

Last updated

Was this helpful?