Personal Health Dashboard - Most Important

What is Personal health Dashboard?

AWS Personal Health Dashboard provides alerts and remediation guidance when AWS is experiencing events that may impact you. While the Service Health Dashboard displays the general status of AWS services, Personal Health Dashboard gives you a personalized view into the performance and availability of the AWS services underlying your AWS resources.

Types of Alerts

1. · Issues

2. · Notifications

3. · Scheduled Changes

Issues

Based on the service you choose there are different set of issues categorized by AWS

For one of our use cases lets pick EC2 and list the different issues:

· AWS_EC2_API_ISSUE

· AWS_EC2_DEDICATED_HOST_UNDER_RESERVATION_REPLACE

· AWS_EC2_DNS_RESOLUTION_ISSUE

· AWS_EC2_INSTANCE_AUTO_RECOVERY_FAILURE

· AWS_EC2_INSTANCE_AUTO_RECOVERY_SUCCESS

· AWS_EC2_INSTANCE_STORE_DRIVE_PERFORMANCE_DEGRADED

· AWS_EC2_NETWORK_CONNECTIVITY_ISSUE

· AWS_EC2_OPERATIONAL_ISSUE

· AWS_EC2_POWER_CONNECTIVITY_ISSUE

· AWS_EC2_RI_MARKETPLACE_BANK_ACCOUNT_UPDATE_REQUIRED

Notifications

Will gather categories under Notifications.

For one of our use cases lets pick EC2 and list the different notifications

· AWS_EC2_BILLING_NOTIFICATION

· AWS_EC2_CUSTOMER_ENGAGEMENT

· AWS_EC2_HOST_RECOVERY_COMPLETION

· AWS_EC2_HOST_RECOVERY_FAILURE

· AWS_EC2_OPERATIONAL_NOTIFICATION

· AWS_EC2_INSTANCE_AUTO_RECOVERY_NO_ACTION

· AWS_EC2_HOST_RECOVERY_INITIATION

· AWS_EC2_HOST_RECOVERY_SUCCESS

Scheduled Changes

Will gather categories under scheduled changes.

For one of our use cases lets pick EC2 and list the different scheduled events

· AWS_EC2_DEDICATED_HOST_ACCESSREVOKED_RETIREMENT_SCHEDULED

· AWS_EC2_DEDICATED_HOST_NETWORK_MAINTAINANCE_SCHEDULED

· AWS_EC2_DEDICATED_HOST_POWER_MAINTAINANCE_SCHEDULED

· AWS_EC2_DEDICATED_HOST_ RETIREMENT_SCHEDULED

· AWS_EC2_INSTANCE_REBOOT_FLEXIBLE_MAINTAINANCE_SCHEDULED

· AWS_EC2_INSTANCE_REBOOT_SCHEDULED

These are few things captured and PHD supports all services and captures the health.

How have we achieved this alerting

For Testing Scenario we have taken

Event : Events per service

Service : EC2

Specific Event type category : issue

Specific event type code : AWS_EC2_OPERATIONAL_ISSUE

Specific resource : <Instance IDs can be mentioned>

Services we have used to set up alerts:

· Cloud Watch

· Simple Notification service-SNS

· Lambda

· EC2(as we have set up alert for EC2 operational issues for testing)

Flow of the setup

· Personal Health Dashboard reports an event (issue, notification or Scheduled changes)

· Cloud watch will have a rule set to capture new events at health dashboard

· Cloudwatch target is set to lambda function to trigger a notification.

· Notification protocol is EMAIL and it is sent via SNS to subscribed email IDs

Why Personal health dashboard

Use case:

Event data

Event

AutoScaling operational issue

Status

Closed

Region/AZ

ap-southeast-2

Start time

November 26, 2019 at 7:18:46 AM UTC+5:30

End time

November 26, 2019 at 9:03:21 AM UTC+5:30

Event category

Issue

Event data

Event

RDS Security notification

Status

-

Region/AZ

us-east-1

Start time

November 26, 2019 at 2:29:00 PM UTC+5:30

End time

-

Event category

Notification

We previously sent a communication in early October to update your RDS SSL/TLS certificates by October 31, 2019. We have extended the dates and now request that you act before February 5, 2020 to avoid interruption of your applications that use Secure Sockets Layer (SSL) or Transport Layer Security (TLS) to connect to your RDS and Aurora database instances. Note that this new date is only 4 weeks before the actual Certificate Authority (CA) expiration on March 5, 2020. Because our own deployments, testing, and scanning to validate all RDS instances are ready for the expiry must take place during the final 4 weeks, the February 5th date cannot be further extended.

Cost Perspective

· Personal health dashboard is a free service available and does not require explicit settings to capture the events

· We are using Lambda functions and costing is very minimal.

Implementation details below

· Cloudwatch Rule

{ "source": [ "aws.health" ], "detail-type": [ "AWS Health Event" ], "detail": { "service": [ "EC2" ], "eventTypeCategory": [ "issue" ], "eventTypeCode": [ "AWS_EC2_OPERATIONAL_ISSUE" ] } }

Thank You. Hope this helps!!