This lesson's interactive features are locked, please to keep using them

Monitoring Targets

We can't get started with monitoring until we have something to monitor!

Let's set up our EC2 instance as a target that we can monitor with CloudWatch, AWS' built-in service for collecting metrics, logs, and events from various resources and applications.

Assignment

Use your existing patientping-web-v2 EC2 instance as the monitoring target and make sure it's ready for this chapter.

Cost check: A t3.micro instance costs about $0.0104 per hour (~$7.60 per month). A public IPv4 address costs $0.005 per hour (~$3.60 per month).

Navigate to "EC2" → "Instances" in the AWS Console.
Confirm you have a running patientping-web-v2 instance. If patientping-web-v2 is missing, recreate it from your launch template from chapter 3.
Verify with the AWS CLI:

# VPC
aws ec2 describe-vpcs --filters Name=tag:Name,Values=patientping

# Public subnet
aws ec2 describe-subnets --filters Name=tag:Name,Values=patientping-public-a

# EC2 instance
aws ec2 describe-instances --filters Name=tag:Name,Values=patientping-web-v2

# Public IP on instance
aws ec2 describe-instances --filters Name=tag:Name,Values=patientping-web-v2 --query 'Reservations[*].Instances[*].PublicIpAddress'

Run and submit the CLI tests.