Cleanup & Normalize S3 Bucket Structure

[mark-dce]

ISSUE The S3 bucket naming convention is not immediately obvious when reviewing the S3 console

ACCEPTANCE

• [ ] Remove references to "Samples" for persistent data displayed by an environment - i.e. live PTIFFs are no longer samples and we shouldn't carry this nomenclature forward
• [ ] Ensure there is one top-level bucket for each environment
• [ ] Ensure cached data is clearly segregated from authoritative content
• [ ] Draw a diagram of environments, buckets, and folders

NOTE We can't rename buckets and will need to plan how to create buckets with desired new names and copy data without negatively impacting running clusters.

CURRENT STATE

[K8Sewell]

Updated S3 Bucket Naming Structure

Please edit the wiki with any future updates. Link to Internal Wiki Documentation

Next Steps

• [ ] determine if new buckets should have encryption turned on - see ticket #846 ZenHub Link
• [ ] create the following new buckets
  • yul-dc-dev-images
  • yul-dc-uat-images
  • yul-dc-test-manifests
  • yul-dc-uat-manifests
  • yul-dc-demo-manifests
  • yul-dc-staging-manifests
  • yul-dc-prod-manifests
• [ ] once files have completed copying into the new buckets the following PR should be merged into camerata repo to update which bucket is used for local development
• [ ] if the buckets are set in any Jenkins deploy scripts those will need updated to use the new bucket names
• [ ] once bucket names have been updated for all environments the yul-dc-testing-manifests bucket and all buckets with 'samples' in the name can be deleted