Creates content connectors page in security docs

[benironside]

Fixes internal/34 by documenting the new Content connectors interface, and the setup process for Elastic managed content connectors.

Preview: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2113/solutions/security/get-started/content-connectors

@dhru42, in your issue you requested that we update our support table's Connectors row, but I'm thinking we should actually add a new row under the security section, since the connectors row currently only exists in the Search section. WDYT?

[github-actions]

🔍 Preview links for changed docs

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

[dhru42]

To see a complete list of the available connectors, follow the setup instructions below.

is there a place where we can link users for full list of connectors? @benironside

[florent-leborgne]

Suggested change

	{{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.

Suggestion to avoid confusion with stack deployment models

Reading this paragraph, I also wonder about what this page states: https://www.elastic.co/docs/reference/search-connectors/

"As of Elastic 9.0, managed connectors on Elastic Cloud Hosted are no longer available. All connectors must be self-managed."

If I reconcile this paragraph with the sentence from that other page, that gives:

• Serverless only supports Elastic managed connectors
• ECH only supports self-managed connectors
• What about other Stack deployment types?

I think we should try to clarify, as I either misunderstood, or we're giving conflicting/partial information in our various pages.

@leemthompo maybe you can help here?

[leemthompo]

Yes https://www.elastic.co/docs/reference/search-connectors/elastic-managed-connectors will have to be updated because now managed connectors have been revived by the Sec/Obs teams.

You'll need to update this page to mention the availability of managed connectors in certain serverless projects and 9.1+ ECH Obs/Sec navs.

That page is currently accurate for 9.0.

In 9.0:

• Serverless only supports self-managed connectors
• ECH only supports self-managed connectors
• What about other Stack deployment types? You can't run a managed connector on a self-managed deployment.

[leemthompo]

tldr is self-managed connectors can send data to Elasticsearch instances wherever they may be deployed

[leemthompo]

Managed connectors only send data to the serverless/hosted deployment they're deployed within

[leemthompo]

I don't think this paragraph belongs under Setup btw

[leemthompo]

Connectors have two deployment methods: Elastic managed and self-managed.

Self-managed deployments require you to deploy the connector service on your own infrastructure (i.e. run some Python code on a server you manage). When you use managed connectors Elastic runs that Python service for you within your deployment.

Self-managed connectors can be customized, whereas Elastic managed connectors cannot.

I think the serverless distinction is a bit nuanced:

• You can use self-managed connectors to send data to Elasticsearch on serverless
• AFAICT you can now use managed connectors for Obs/Sec projects