Well, you could certainly just download from archive.org for the first-time usage of any particular song and then cache them from there. Like being your own CDN.
> “Through further investigation, we learned that Pray.com had protected some files, setting them as private on the buckets to limit access,” they explained. “However, at the same time, Pray.com had integrated its S3 buckets with another AWS service, the AWS CloudFront content delivery network (CDN). Cloudfront allows app developers to cache content on proxy servers hosted by AWS around the world – and closer to an app’s users – rather than load those files from the app’s servers. As a result, any files on the S3 buckets could be indirectly viewed and accessed through the CDN, regardless of their individual security settings.”
I have minimal knowledge of this kind of configuration, but it seems like making content available via a CDN from the same vendor should by default carry forward access restrictions on the original backend data.
This was posted here a few months ago. The article indicated that a change/reduction in training starting in 2003, mainly for cost savings, was coming home to roost. I wonder if similar things are going on in the maintenance area.
Don't forget the tailings ponds that are constructed to park the waste and residue chemicals from extraction and processing. They are simply left there until time and eventual facilities decay allow them to leak into nearby waterways.