Separate Buckets for Samples, Supporting Data and Goodware

[c3rb3ru5d3d53c]

Feature Category

• Correctness
• User Interface / User Experience
• Performance
• Other (please explain)

Describe the problem

Right now mwdb uploads everything to the same s3 bucket or local storage folder even if it's strings extracted from a binary.

When you are building a large default set this can be detrimental to your default data-set.

Likely a ton of work but I thought I'd suggest it.

Describe the solution you'd like

• Default supporting data bucket
• Configuration Supporting List of s3 Buckets or folders you want to use
• Buckets can be selected in GUI upload
• Buckets can be selected using the API when uploading
• Samples are tagged according to the bucket
• Search via API and Interface supports searching by the tagged bucket or data-set
• Kartons should be able to choose bucket they upload to as part of the framework
• Goodware should by default not go through the karton analysis

Describe alternatives you've considered

The alternative is to just upload other samples to a s3 bucket using other CLI and s3 API tools separate from mwdb.