Folks. I'm Craig Lowell from DoiT back again to walk you through another everyday cloud management task that's tedious to do manually, but takes seconds to automate with Cloudflow. Let's talk about tagging and labeling compute resources. If you've ever tried to keep your Amazon EC two instances or Google Cloud VMs consistently tagged for cost allocation, chargeback, or showback, you know how quickly things can get messy. One missed tag here and unlabeled VM there, and suddenly your billing data is too fragmented to break down by team or project. Fixing this problem involves finding every resource missing the right tag or label and applying it. The problem is that doing this across multiple accounts, projects, or clouds means hours of console clicking, describe or list API calls, and manual cross checks. It's tedious work that steals time from actual engineering, and that's exactly the kind of workflow Cloudflow was built to handle. With Cloudflow, you can scan all of your instances across any AWS or Google Cloud service, identify the ones missing a required tag, apply it automatically, and generate a full audit report all from a single prompt. Auto tagging is one of the most popular use cases in the Cloudflow blueprint library with templates available for both AWS and Google Cloud services. Using the same native AWS and Google Cloud APIs you'd use yourself, Cloudflow can search across all Amazon EC two and Google Compute Engine instances, filter for resources missing the required tag or label, apply the missing metadata, and generate a report of what was updated and when. By creating cloud flows like this that run on a regular basis, you can ensure cloud governance at scale without having to write new scripts, conduct manual audits, or chase down tag drift. You just get consistent, accurate tagging in seconds across every account. Thanks for watching. For more information about Cloudflow and how you can apply it to other repetitive FinOps tasks, raise a support ticket or reach out to your DoIT account manager.