[kosabogi]

This PR introduces a Set up section for Elasticsearch search. It walks through choosing where Elasticsearch runs, getting an endpoint and API key, and connecting a language client.

Set up Elasticsearch for search: section overview

• Choose a deployment type: compare deployment types and start one
• Get your API key and endpoints: find the endpoint and create an API key
• Connect with an SDK: install a language client and check the connection

Related issues:

Fixes #8602
#8601

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• solutions/elasticsearch-solution-project/search-connection-details.md
• solutions/search/set-up.md
• solutions/search/set-up/api-key-and-endpoints.md
• solutions/search/set-up/connect-with-an-sdk.md
• solutions/search/set-up/get-elasticsearch-running-for-search.md
• solutions/vector-database/vector-full-text-search.md

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[leemthompo]

The flow is looking tighter now, but I still have some issues around the "start a deployment' step, and some language suggestions.

(Ideally we'd have onboarding tokens for free trials that weren't just vector too eventually)

[shainaraskas]

a couple of categories of comments:

• some positioning around deployment types (minor)
• some issues with the api key + endpoint retrieval instructions (unfortunately the ground keeps shifting under our feet here)
• some stepper/formatting/blahblah nits

[shainaraskas]

I think we're not doing any comparison on this page at all. instead, this page just says "pick one, here's the bare minimum info" -> "run a quickstart". positioning could use some work

would be a step forward to organize around decision criteria rather than the deployment type

[leemthompo]

instead, this page just says "pick one, here's the bare minimum info"

i think that's intended because otherwise this page shouldn't exist tbh, because if we expand the scope of this page to more comprehensive decision criteria

honestly not sure we need another page like that outside of deploy/manage and i have struggled with whether this new page should exist at all

[shainaraskas]

that's fine - it's just that the title and framing of the page don't match what's happening on the page, so readers might feel shortchanged.

[kosabogi]

I think Shaina has a good point, the title and intro position this page as something different from what it actually is. That happened because we went through a few iterations and the focus shifted a bit. I’d suggest rewriting the title to “Get {{es}} running for search” and updating the intro to:

{{es}} is at the core of every Elastic deployment type. The deployment type you choose determines who manages the infrastructure, scaling, and upgrades, and how usage is billed. This page briefly introduces the deployment types you can use to get {{es}} running quickly, and points you to resources that compare them in detail.

[shainaraskas]

thanks for addressing all of the feedback 🙏 I've commented a couple more things to consider - nothing blocking

[shainaraskas]

perhaps "Set environment variables" ?

[shainaraskas]

I think this would be nicer with an example response in each tab in the tabset above but will not block on that basis

[shainaraskas]

is the sdk step and the client install step separate really? usually sdks and clients are somewhat synonymous

does not mirror the steps in the linked tutorial (also the titles are now slightly out of sync)