Matteo Piano c89cd370d5 Add AWS S3 as file carving backend (#126) ... This adds the option to set up an S3 bucket as the storage backend for file carving (partially solving #111). It works by using the multipart upload capabilities of S3 to maintain compatibility with the "upload in blocks" protocol that osquery uses. It does this basically replacing the carve_blocks table while still maintaining the metadata in the original place (it would probably be possible to rely completely on S3 by using object tagging at the cost of listing performance). To make this pluggable, I created a new field in the service struct dedicated to the CarveStore which, if no configuration for S3 is set up will be just a reference to the standard datastore, otherwise it will point to the S3 one (effectively this separation will allow in the future to add more backends).		2020-12-16 09:16:55 -08:00
..
fleet	Add AWS S3 as file carving backend (#126)	2020-12-16 09:16:55 -08:00
fleetctl	Migrate remaining URLs to fleetdm.com (#116)	2020-12-10 11:26:00 -08:00