From 51ab2e19cb958a67ee5e4eb8e39e67a65f4ad929 Mon Sep 17 00:00:00 2001 From: Benjamin Ironside Goldstein Date: Fri, 11 Jul 2025 11:40:32 -0400 Subject: [PATCH 1/4] Creates content connectors page in security docs --- .../get-started/content-connectors.md | 36 +++++++++++++++++++ solutions/toc.yml | 1 + 2 files changed, 37 insertions(+) create mode 100644 solutions/security/get-started/content-connectors.md diff --git a/solutions/security/get-started/content-connectors.md b/solutions/security/get-started/content-connectors.md new file mode 100644 index 0000000000..e5f252f01a --- /dev/null +++ b/solutions/security/get-started/content-connectors.md @@ -0,0 +1,36 @@ +--- +applies_to: + stack: preview 9.1 + serverless: preview +--- + +# Content connectors + +Elastic's content connectors allow you to extract, transform, index, and sync data from third-party applications including Github, PagerDuty, Jira, OpsGenie, Teams, Google Drive, Slack, email, and more. To see a complete list of the available connectors, follow the setup instructions below. + +## Setup +{{stack}} supports two deployment methods: Elastic managed, and self-managed. {{serverless}} only supports Elastic managed deployments. Self-managed deployments require you to manage the {{elastic-agent}} that forwards data to Elastic and allow you to customize the connector's code, whereas Elastic managed deployments use agentless technology and do not allow customization. + +To learn about set up for self-managed connectors, refer to [Self managed connectors](elasticsearch://reference/search-connectors/self-managed-connectors.md). To set up an Elastic managed connector: + +- Use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "Content conectors". +- Click **New Connector**. +- Under **Connector**, select your desired data source. +- Under **Setup**, select your deployment method. +- 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. +- 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**. +- 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: + +- Use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "Content connectors". +- 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**: Use EQL to select which documents from the connector you wish to save. By default, all documents are saved. + - **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. \ No newline at end of file diff --git a/solutions/toc.yml b/solutions/toc.yml index 918381a427..d4131be054 100644 --- a/solutions/toc.yml +++ b/solutions/toc.yml @@ -474,6 +474,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 From 647937fb1ac922bb714155147e18a143a78badd1 Mon Sep 17 00:00:00 2001 From: Benjamin Ironside Goldstein Date: Fri, 11 Jul 2025 11:45:56 -0400 Subject: [PATCH 2/4] fixes broken attribute --- solutions/security/get-started/content-connectors.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/security/get-started/content-connectors.md b/solutions/security/get-started/content-connectors.md index e5f252f01a..9e284f8bf8 100644 --- a/solutions/security/get-started/content-connectors.md +++ b/solutions/security/get-started/content-connectors.md @@ -9,7 +9,7 @@ applies_to: Elastic's content connectors allow you to extract, transform, index, and sync data from third-party applications including Github, PagerDuty, Jira, OpsGenie, Teams, Google Drive, Slack, email, and more. To see a complete list of the available connectors, follow the setup instructions below. ## Setup -{{stack}} supports two deployment methods: Elastic managed, and self-managed. {{serverless}} only supports Elastic managed deployments. Self-managed deployments require you to manage the {{elastic-agent}} that forwards data to Elastic and allow you to customize the connector's code, whereas Elastic managed deployments use agentless technology and do not allow customization. +{{stack}} supports two deployment methods: Elastic managed, and self-managed. {{sec-serverless}} only supports Elastic managed deployments. Self-managed deployments require you to manage the {{elastic-agent}} that forwards data to Elastic and allow you to customize the connector's code, whereas Elastic managed deployments use agentless technology and do not allow customization. To learn about set up for self-managed connectors, refer to [Self managed connectors](elasticsearch://reference/search-connectors/self-managed-connectors.md). To set up an Elastic managed connector: From 626ab8ead6c9f400325274de5c3496bc3da89d1a Mon Sep 17 00:00:00 2001 From: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com> Date: Wed, 16 Jul 2025 22:50:55 -0700 Subject: [PATCH 3/4] Apply suggestions from code review Co-authored-by: florent-leborgne Co-authored-by: Liam Thompson --- solutions/security/get-started/content-connectors.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/solutions/security/get-started/content-connectors.md b/solutions/security/get-started/content-connectors.md index 9e284f8bf8..93497ebdbc 100644 --- a/solutions/security/get-started/content-connectors.md +++ b/solutions/security/get-started/content-connectors.md @@ -6,10 +6,10 @@ applies_to: # Content connectors -Elastic's content connectors allow you to extract, transform, index, and sync data from third-party applications including Github, PagerDuty, Jira, OpsGenie, Teams, Google Drive, Slack, email, and more. To see a complete list of the available connectors, follow the setup instructions below. +Elastic's content connectors allow you to extract, transform, index, and sync data from third-party applications including Github, PagerDuty, Jira, Teams, Google Drive, Slack, email, and more. [View all available connectors](elasticsearch://reference/search-connectors/index.md) ## Setup -{{stack}} supports two deployment methods: Elastic managed, and self-managed. {{sec-serverless}} only supports Elastic managed deployments. Self-managed deployments require you to manage the {{elastic-agent}} that forwards data to Elastic and allow you to customize the connector's code, whereas Elastic managed deployments use agentless technology and do not allow customization. +{{stack}} supports two deployment methods for your connectors: Elastic managed, and self-managed. {{sec-serverless}} only supports Elastic managed connectors. Self-managed connectors require you to manage the {{elastic-agent}} that forwards data to Elastic and allow you to customize the connector's code, whereas Elastic managed connectors use agentless technology and do not allow customization. To learn about set up for self-managed connectors, refer to [Self managed connectors](elasticsearch://reference/search-connectors/self-managed-connectors.md). To set up an Elastic managed connector: @@ -31,6 +31,6 @@ To manage an existing connector: - **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**: Use EQL to select which documents from the connector you wish to save. By default, all documents are saved. + - **Sync rules**: Manage basic and advanced [sync rules](elasticsearch://reference/elasticsearch/search-connectors/es-sync-rule.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. \ No newline at end of file From f3edea0cac20d0fef0aec739e9ccc4fdb8b5d3a0 Mon Sep 17 00:00:00 2001 From: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com> Date: Thu, 17 Jul 2025 11:26:10 -0700 Subject: [PATCH 4/4] Update solutions/security/get-started/content-connectors.md Co-authored-by: florent-leborgne --- solutions/security/get-started/content-connectors.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/security/get-started/content-connectors.md b/solutions/security/get-started/content-connectors.md index 93497ebdbc..f6ac873188 100644 --- a/solutions/security/get-started/content-connectors.md +++ b/solutions/security/get-started/content-connectors.md @@ -31,6 +31,6 @@ To manage an existing connector: - **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/elasticsearch/search-connectors/es-sync-rule.md) to control which documents are synced from your third-party data source. + - **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. \ No newline at end of file