Phil Gervasi introduces a method for identifying idle resources in AWS using the Kentik platform. By selecting dimensions such as Logging Status, Observing VPC ID, and Observing Region, users can filter the data to determine if a resource is actually doing anything from a network perspective. “No Data” messages indicate resources with no network activity, and a more specific filter can be created based on this message to isolate idle resources. By adjusting the time frame and observing bits per second, users can determine how long resources have been idle. The information can then be shared with the cloud team.

Learn more about Kentik solutions for multi-cloud observability here:
https://www.kentik.com/product/multi-cloud-observability/

CHAPTERS:

0:00 Introduction

0:15 Data Explorer and Filtering Selections

0:37 Identifying Idle Resources

0:59 Adjusting Time Frame

1:20 Sharing Information