nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqjtm4dxvu3ccgk60wvvt0uw9j9vz7nuc80f7agrv0vgkkushxk5zqnzj90y (nprofile…j90y) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqln5q8np5aezhtt7ztv6tah86xk4t3smjuchdvxp0u6uta056204qf4h82d (nprofile…h82d) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqyz5hmul3qjuvzgsgh666xenzalxnn9ed55pcduspjfznzqvhwraq4jpvn3 (nprofile…pvn3)
As per your example
HLS typically uses chunks of ten seconds. Each of those are a separate request. So, a two hour show is the same amount of data vs a normal download, but 7,200 requests vs just one.
1,000,000 / 7200 = 138
1000 Plays / 138 = 7.24 x .75 = $5.43
So, in all reality, the request is where you get killed on AWS
This is where the clouflare solution is better until you move to much traffic and they force you into a contract.