4 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
This article explains how Datadog Storage Management helps organizations analyze their Amazon S3 storage costs. It provides tools to pinpoint cost drivers, identify cold data for archiving, and implement recommendations for savings.
If you do, here's more
Cloud object storage is essential for handling diverse workloads, but as data scales into petabytes, managing costs and ensuring reliability becomes challenging. Datadog Storage Management addresses this by offering visibility into storage costs at a granular level. It allows teams to analyze which specific services, workloads, or datasets contribute to spending, making it easier to identify areas for cost reduction. For example, if a data warehouse's prefixes are linked to database tables, teams can directly associate costs with particular workloads. This clarity helps in making informed decisions about archiving or transitioning data.
Many organizations default to storing data in the Amazon S3 Standard class, even when large portions are seldom accessed. Datadogβs tool enables users to differentiate between frequently accessed and cold data, allowing for efficient tier management. For instance, if a dataset used for training a language model hasn't been accessed in months, Storage Management can suggest moving it to Amazon S3 Glacier. The ability to view request metrics by prefix helps pinpoint these opportunities, minimizing unnecessary costs without compromising data availability.
Beyond identifying inefficiencies, Storage Management provides actionable recommendations for cost savings. Users receive a prioritized list of recommendations, such as transitioning infrequently accessed objects to cheaper storage tiers or consolidating small files to reduce overhead. This feature not only aids teams in acting quickly on savings but also integrates with tools like Jira for better management. A practical example highlights how a DevOps team identified a 40% increase in their storage costs and pinpointed a specific prefix within a shared bucket responsible for the spike. By implementing Storage Management's recommendations, they managed to significantly reduce projected costs while maintaining application performance.
Questions about this article
No questions yet.