Easy, it's not cheaper, and I like control.
FTB can easily have 20,000,000 GET requests a day, that many requests on Amazon S3 would retail at $20, that's excluding the charge for the storage space.
Using their own "Simple Monthly Calculator", they would charge $3460.15 for what we provide at the moment for, I'll be honest, with the new system I've done it's going to cost us around $500...
With their calculator I selected only 5GB drive space, the actual monthly data transfer FTB are using at the moment, and an estimated amount of requests for a month, on the low side at that.
Our one provides 3TB storage, unlimited data transfer (Only limited by the concurrency of the boxes, currently sitting at around 14GBit/sec)... I think you can see now why we're doing this ourself, or I hope so.
ipconfig /flushdns
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
ping -n 10 america.creeperrepo.net
Pinging chicago1.creeperrepo.net [199.96.83.199] with 32 bytes of data:
Reply from 199.96.83.199: bytes=32 time=43ms TTL=51
Reply from 199.96.83.199: bytes=32 time=31ms TTL=51
Reply from 199.96.83.199: bytes=32 time=63ms TTL=51
Request timed out.
Reply from 199.96.83.199: bytes=32 time=33ms TTL=51
Reply from 199.96.83.199: bytes=32 time=49ms TTL=51
Reply from 199.96.83.199: bytes=32 time=34ms TTL=51
Reply from 199.96.83.199: bytes=32 time=33ms TTL=51
Reply from 199.96.83.199: bytes=32 time=33ms TTL=51
Reply from 199.96.83.199: bytes=32 time=31ms TTL=51
Ping statistics for 199.96.83.199:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 63ms, Average = 38ms
....rude much?I understand, I was more or less making sure you understood it already existed in another form.