<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws-Mediaconvert on Kuldeep Pisda</title><link>https://kdpisda.in/tag/aws-mediaconvert/</link><description>Recent content in Aws-Mediaconvert on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 18 Apr 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/aws-mediaconvert/index.xml" rel="self" type="application/rss+xml"/><item><title>Zeroing the Egress Bill: Wasabi, Cloudflare, and the Transcoder It Cost Us</title><link>https://kdpisda.in/s3-to-wasabi-losing-mediaconvert/</link><pubDate>Sat, 18 Apr 2026 10:00:00 +0530</pubDate><guid>https://kdpisda.in/s3-to-wasabi-losing-mediaconvert/</guid><description>&lt;p&gt;Putting a cost-to-serve number next to daily active users told me exactly what the Happy Thoughts platform was spending on bandwidth. It did not make the spending stop. Once the 1,500 dollar day had my full attention, I did the obvious thing — went hunting for a cheaper way to put video in front of people — and the answer that eventually won was not a cheaper CDN. It was to stop paying for egress at all.&lt;/p&gt;</description></item><item><title>150 Videos a Day Buried Our CPU Transcoders, So I Stopped Encoding In-House</title><link>https://kdpisda.in/cpu-transcoding-too-slow-aws-mediaconvert/</link><pubDate>Sat, 04 Apr 2026 10:00:00 +0530</pubDate><guid>https://kdpisda.in/cpu-transcoding-too-slow-aws-mediaconvert/</guid><description>&lt;p&gt;In the last chapter we owned the whole video pipeline: content uploaded to an S3 ingest bucket, a Celery worker on ECS ran ffmpeg to build the adaptive-bitrate ladder, and CloudFront served the HLS chunks. It worked beautifully the day I demoed it with three test videos. Then the content team found the bulk uploader.&lt;/p&gt;
&lt;p&gt;I opened Grafana on a Tuesday and the &lt;code&gt;transcode_video&lt;/code&gt; queue depth was a straight diagonal line, climbing since nine that morning. Not a spike that drains — a line that only went up. The team had discovered they could select a course&amp;rsquo;s entire back-catalogue and push it in one sitting, and they were doing exactly what a good content team should do: 150-plus videos before lunch. My CPU workers were going to be chewing on that pile until Friday.&lt;/p&gt;</description></item></channel></rss>