Client: CloudSprawl · DevOps, SRE & Cloud · US digital media group (130 staff)

Reducing Cloud Spend for a Media Platform

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team helped CloudSprawl right-size its AWS and GCP infrastructure. Over six months, the client’s billing records show cloud spend falling from $210,000 to $139,000 per month. Idle resources fell from 340 to 41.

Client and engagement facts

Client
CloudSprawl
Industry
DevOps, SRE & Cloud
Business context
US digital media group (130 staff)
Delivery model
Cloud infrastructure right-sizing
Application
Multi-cloud media platform
Supplied geography
US
Company size in source
130 staff

Application stack and tools

Application stack

  • AWS + GCP
  • Kubernetes

Tools used

  • AWS billing
  • GCP billing
  • Datadog
  • Terraform

Why Support Was Needed

Spending had risen despite flat usage when the work started. Unused volumes, 12 oversized RDS instances and a long log-retention setting were the main targets for review.

Technical Work

  • Audited cloud volumes, RDS sizing and backup retention.
  • Removed idle volumes and right-sized oversized RDS instances.
  • Added cost alerts to the client’s monitoring.

Representative Incident

A vendor price change added $8,000 in month four. The engineers adjusted resource sizing within two weeks to partially offset the increase.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
Cloud spend$210k/mo$139k/mo6 monthsClient AWS/GCP
Idle resources340416 monthsClient billing
Cost-alert noise60/wk6/wk/wk6 monthsClient Datadog

Evidence and Limitations

The six-month comparison uses the client’s AWS and GCP billing records. It includes a supplier price change. Datadog tracked cost alert volume.

Cloud Cost Baseline

The client’s cost review identified 340 idle volumes and a seven-year log retention policy on a system with no prior deletions.

Scope a Similar Engagement

Share the cost categories that changed, the workload they serve and who approves retention changes. Request a support plan or explore DevOps support.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.