Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
kabilar opened this issue Nov 10, 2024 · 1 comment
Open

Comments

@kabilar
Copy link
Member

kabilar commented Nov 10, 2024

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 that summarizes the buckets.

@mvandenburgh
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants