Review and potentially delete AWS S3 buckets that are no longer needed

[kabilar]

There are several S3 buckets under the McGovern DANDI AWS account that seem to be test data (and some buckets are empty). As a group, we should decide which ones can be deleted so that we are not paying for this storage.

As a first step, @waxlamp has generated a report Google sheet that summarizes the buckets.

TODO:

• meet to discuss buckets and finalize disposition column
• check which buckets are defined via Terraform

[mvandenburgh]

To add to some of the unknown buckets in that list - dandi-api-storage and dandi-api-staging-storage are S3 buckets automatically created by the terraform-heroku-girder4 module. Because DANDI has its own requirements around S3 buckets, like separate accounts and the whole "sponsored" bucket thing, we don't make use of those buckets and instead define our own outside of the module.

[yarikoptic]

how we should proceed on that handy table @waxlamp has generated? is it impossible to edit in that gist ? otherwise -- maybe let's generate a PR here with that markdown and as with design docs provide feedback/distill the solution?

I thought to suggest going with google docs, but I think PR would be better

[waxlamp]

I thought to suggest going with google docs, but I think PR would be better

I think a PR dealing with markdown-formatted tables will be very difficult to deal with. I went ahead and created a Google sheet with the current state of my little table. Anyone can view this link, but I need to invite people to be editors, so let me know if you need that access.

Instead of a discussion through GitHub, I think we should just set a meeting and go through this synchronously (@kabilar, if you want to set that up, please go ahead).