You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 17, 2021. It is now read-only.
It would be a very handy feature to drop data output to S3 instead of to disk. This would enable easy searching/indexing of output in something like Amazon Athena, while also requiring a lot less infrastructure/disk/constraints to run domain-scan itself.
Since the abstraction difference between S3 and disk is pretty slim, it would also be likely worth it to add in enough adapter-ish code to easily support being extended to other non-disk destinations, such as Google Cloud Storage.
The text was updated successfully, but these errors were encountered:
It would be a very handy feature to drop data output to S3 instead of to disk. This would enable easy searching/indexing of output in something like Amazon Athena, while also requiring a lot less infrastructure/disk/constraints to run domain-scan itself.
Since the abstraction difference between S3 and disk is pretty slim, it would also be likely worth it to add in enough adapter-ish code to easily support being extended to other non-disk destinations, such as Google Cloud Storage.
The text was updated successfully, but these errors were encountered: