From 269dee0f41d4e7d007aae877d0770d345a6d2a0c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dan=20Gr=C3=B8ndahl?= Date: Fri, 25 Sep 2026 17:46:12 +0200 Subject: [PATCH] docs: replace 'customer' with 'tenant' --- administration/cloud_capture/overview.md | 6 +++--- administration/cloud_capture/security.md | 2 +- terraform-reference/resources/action.mdx | 1 + 3 files changed, 5 insertions(+), 4 deletions(-) diff --git a/administration/cloud_capture/overview.md b/administration/cloud_capture/overview.md index b7b2a1ce..06b4c211 100644 --- a/administration/cloud_capture/overview.md +++ b/administration/cloud_capture/overview.md @@ -20,7 +20,7 @@ To set it up for your organization, see [Getting started with Cloud Capture](/ad Cloud Capture connects to your cloud accounts using permissions that you manage. You configure Cloud Capture by activating it for different services, and Cloud Capture uses the permissions to regularly reach into your estate and record snapshots, sending the data into your Kosli organization. Cloud Capture uses details about your infrastructure, such as the name of an ECS cluster, to build environments within Kosli. -Diagram showing Cloud Capture, inside Kosli, sending queries to and receiving snapshots from three customer cloud accounts, then passing the data to the Kosli API and database +Diagram showing Cloud Capture, inside Kosli, sending queries to and receiving snapshots from three tenant cloud accounts, then passing the data to the Kosli API and database ## Security @@ -28,8 +28,8 @@ Cloud Capture connects to your cloud accounts using permissions that you manage. The security of your cloud infrastructure is the primary driver behind the internal architecture of Cloud Capture. You grant a read-only IAM role in your account, protected by an external ID that acts as a shared secret between Kosli and you. On Kosli's side, each Cloud Capture job runs under a role -scoped to your organization alone, so a worker running for another customer cannot reach your cloud -account. Cloud Capture holds no customer data; snapshots go straight to Kosli through the same ingest +scoped to your organization alone, so a worker running for another tenant cannot reach your cloud +account. Cloud Capture holds no tenant data; snapshots go straight to Kosli through the same ingest path as your existing pipelines. See [Cloud Capture Security](/administration/cloud_capture/security) for the isolation model and the full list of permissions. diff --git a/administration/cloud_capture/security.md b/administration/cloud_capture/security.md index e4cc5ef1..32616e68 100644 --- a/administration/cloud_capture/security.md +++ b/administration/cloud_capture/security.md @@ -322,7 +322,7 @@ gcloud infra-manager deployments apply \ -## How Kosli isolates customers +## How Kosli isolates tenants Cloud Capture runs as a shared, autoscaled service, but each job runs under a role that is scoped to one customer: diff --git a/terraform-reference/resources/action.mdx b/terraform-reference/resources/action.mdx index 5eae4c19..8afa8e81 100644 --- a/terraform-reference/resources/action.mdx +++ b/terraform-reference/resources/action.mdx @@ -2,6 +2,7 @@ title: "kosli_action resource" description: "Manages a Kosli action. Actions define webhook notifications triggered by environment compliance events." icon: "cube" +mode: "wide" --- Manages a Kosli action. Actions define webhook notifications triggered by environment compliance events.