Merge branch 'main' into 1496-fix-agent-restrictions-for-serverless

Author: benironside

solutions/observability/apm/tail-based-sampling.md

@@ -134,7 +134,7 @@ See [Tail-based sampling](/solutions/observability/apm/transaction-sampling.md#a
 
 The sample rate to apply to trace events matching this policy. Required in each policy.
 
-The sample rate must be greater than or equal to `0` and less than or equal to `1`. For example, a `sample_rate` of `0.01` means that 1% of trace events matching the policy will be sampled. A `sample_rate` of `1` means that 100% of trace events matching the policy will be sampled. (int)
+The sample rate must be greater than or equal to `0` and less than or equal to `1`. For example, a `sample_rate` of `0.01` means that 1% of trace events matching the policy will be sampled. A `sample_rate` of `1` means that 100% of trace events matching the policy will be sampled. (float)
 
 ### **`trace.name`** [sampling-tail-trace-name-ref]
 

solutions/security/cloud/get-started-with-cnvm.md

@@ -26,7 +26,7 @@ This page explains how to set up Cloud Native Vulnerability Management (CNVM).
 
 
 ::::{note}
-CNVM currently only supports AWS EC2 Linux workloads.
+CNVM currently only supports AWS EC2 Linux workloads (not supported on AWS GovCloud).
 ::::
 
 

solutions/security/get-started/content-connectors.md

@@ -0,0 +1,60 @@
+---
+applies_to:
+  stack: 
+  serverless:
+---
+
+# Content connectors
+
+Elastic's content connectors allow you to extract, transform, index, and sync data from third-party applications including Github, Jira, Teams, Google Drive, Slack, email, and more ([view all connectors](elasticsearch://reference/search-connectors/index.md)).
+
+## Managed vs self-managed connectors
+
+Content connectors are available in two deployment options: you can run them yourself or let Elastic run them within your managed deployment on {{ecloud}}.
+
+### Elastic managed connectors
+```yaml {applies_to}
+stack: preview 9.1
+deployment:
+    self: unavailable
+serverless:
+    security: preview
+```
+
+Elastic managed connectors are deployed within your managed Elastic environment. These connectors:
+- Require no infrastructure management
+- Offer simplified setup and maintenance
+- Do not support customization
+- Only send data to the serverless/hosted deployment they're deployed within
+
+### Self-managed connectors
+Self-managed connectors run on your own infrastructure, independent of where your {{es}} instance is running. These connectors:
+- Require you to deploy the connector service (Python) on your infrastructure
+- Can send data to any {{es}} instance (managed or self-managed)
+- Can be customized
+
+## Setup 
+
+To learn about setup for self-managed connectors, refer to [Self-managed connectors](elasticsearch://reference/search-connectors/self-managed-connectors.md). To set up an Elastic managed connector:
+
+1. Use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "Content conectors".
+1. Click **New Connector**.
+1. Under **Connector**, select your desired data source.
+1. Under **Setup**, select your deployment method. 
+1. Under **Configure index & API key**, click **Generate configuration**. After a few seconds, this will create a new connector and a new index for its data, and display their names and IDs. You can click their names to view details about each. 
+1. Click **Next** to continue to the **Configuration** page. This is where you can select details related to your specific data source. For more information about configuring your selected data source, follow the link on the left to the **Connector reference**.
+1. When configuration is complete, click **Next**. The **Finish up** page appears. Here you can set up recurring connector syncs, run a manual sync, or use queries and dev tools to interact with your data. Each sync updates the data in the connector's {{es}} index. You can also manage the connector.
+
+
+## Manage a connector 
+
+To manage an existing connector:
+
+1. Use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "Content connectors". 
+1. Click the connector you want to manage to open its settings page, which has six tabs:
+  - **Overview**: View general information such as the connector's name, ID, status, pipeline, and content sync history. Manage the connector's pipeline and attached index.
+  - **Documents**: View data from the connector.
+  - **Mappings**: Update index mappings for the connector's data.
+  - **Sync rules**: Manage basic and advanced [sync rules](elasticsearch://reference/search-connectors/es-sync-rules.md) to control which documents are synced from your third-party data source.
+  - **Scheduling**: Define when data from this connector gets synced, and set up document level security. A `Full content sync` deletes existing data in your index before fetching from your data source again. An `Incremental content sync` fetches updated data only, without deleting existing data. 
+  - **Configuration**: Edit the connector's data source-specific configuration.

solutions/toc.yml

@@ -477,6 +477,7 @@ toc:
               - file: security/get-started/enable-threat-intelligence-integrations.md
               - file: security/get-started/automatic-migration.md
               - file: security/get-started/automatic-import.md
+              - file: security/get-started/content-connectors.md
               - file: security/get-started/agentless-integrations.md
               - file: security/get-started/agentless-integrations-faq.md
           - file: security/get-started/spaces-elastic-security.md