Osquery uses basic SQL commands to leverage a relational data-model to describe a device.

osquery

I'm a little confused by the fleet s3 bucket configuration: there appears to be two variables:
• `s3_bucket` (<https://fleetdm.com/docs/configuration/fleet-server-configuration#s-3>)
• `packaging_s3_bucket` (<https://fleetdm.com/docs/configuration/fleet-server-configuration#packaging-s-3-bucket>)
Are they purposefully distinct?

If I want to self-host fleetd installers, how do I do so? I haven't noticed e.g. a `fleetctl upload` command.

Hey <@U06FS72M2EB>!

`s3_bucket` is where file carves and software installers (.pkg, .msi, .deb file that you want to deploy to your devices) get stored. As of 4.51.1, we've added the `carves_` and `software_installers_` prefix to the `s3_bucket` config variables so you can keep them in separate buckets if you wish.

`packaging_s3_bucket` is for the packaging server which is not available yet. This option is only documented for being used in Fleet sandbox at the moment

Thanks Dale, sad to see the packaging server isn't available yet

but I also just caught up by the S3 buckets for carving/software installers!
I note that the docs only have `FLEET_S3_BUCKET` documented, but I had to use `FLEET_S3_CARVES_BUCKET` and `FLEET_S3_SOFTWARE_INSTALLERS_BUCKET` to get things working.
That whole struct looks like a bit of a mess TBH

heh, I see there was a bug fixed today around that! <https://github.com/fleetdm/fleet/releases/tag/fleet-v4.53.0>

Hey <@U06FS72M2EB>, yes these are brand new options and we've got a <https://github.com/fleetdm/fleet/pull/20032/|PR> to update docs to properly document these options.