The AWS Cost Explorer tool cannot separate the S3 bucket resource expenditures by name so we can tag them with their own bucket name.
TODO: If possible, convert to a cloud custodian policy.
wget https://gist.githubusercontent.com/nitrocode/b6da03f103f3a0b42220c6fd057102f6/raw/tag-buckets.sh
chmod +x tag-buckets.sh
./tag-buckets.sh