Ingestors#
An ingestor collects inventory, metrics and billing from one kind of source. A tier comes with its own ingestors and every one of the tiers below it. This page extends Connect AWS, Connect Azure and Connect GCP in the Community guide.
Which tier has which#
| Ingestor | Community | Pro | Enterprise |
|---|---|---|---|
| AWS | yes | yes | yes |
| Azure | yes | yes | yes |
| GCP | yes | yes | yes |
| Kubernetes | no | yes | yes |
| Databricks | no | no | yes |
| Snowflake | no | no | yes |
| AI platforms | no | no | yes |
What the 0.9.0 beta installs#
What the table says is the licence's reach. In 0.9.0:
- The chart installs the AWS ingestor by default, and the Azure and GCP ingestors when you switch them on
(
ingestors.azure.enabled,ingestors.gcp.enabled). - The Kubernetes, Databricks, Snowflake and AI ingestors are not installed by this chart in 0.9.0, and core has no integration to connect them to yet.
- There is no VMware ingestor yet.
- Core's detection run reaches AWS accounts only for now: an install shows no finding from the Azure and GCP rules yet.
Cloud accounts#
The Community Edition connects one cloud account at a time. The Enterprise Edition has no limit on the number of cloud accounts, or on the resources per scan.
Air-gapped installs#
Each ingestor has its own outbound calls and switch: see Air-gapped install.