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.

We asked developers across the globe, each with their own take on what makes for a great developer experience. And while every developer’s journey is unique, the need for smooth, efficient workflows is universal. That’s why we’re excited to kick start DevExDays – a celebration of the tools, practices, and innovations that make development easier and more intuitive. To make it even better, we’re offering up to 80% off your first GitKraken Pro seat with the code DEVEXDAYS24 for a limited time!