kids-first / kf-api-bucketservice Goto Github PK

When a study is created, a Cavatica volume should be created that corresponds to that study's bucket. We will also need to track this volume somewhere in the dataservice.

Buckets should be created with encryption turned on.

Need documentation outlining functionality and endpoints for the bucket service.

See: https://docs.sevenbridges.com/docs/enabling-cross-origin-resource-sharing-cors

This will allow easy display of various types of reports generated by the bix team in place of the Cavatica platform versus downloading, improving the user experience. The Marazita specifically asked for this capabilities.

This requires trust on the Cavatica side, which is already done due to the IAM read policies in place. This policy is already in place for the *seq* buckets. I will triple check this before we move forward on automating across all buckets.

Buckets should be created with a standard set of tags.
Tags:

• Name (study id)
• Description
• Environment
• Owner

Do not need qa and dev buckets for most studies, should not be created by default

Study buckets should have a no-delete policy so that users do not accidentally remove data.

The bucket service should be able to validate tokens to verify that they were correctly granted by Auth0 for the bucket service.