Skip to content

Commit

Permalink
updates image and text to include additional connector type
Browse files Browse the repository at this point in the history
  • Loading branch information
benironside committed Oct 18, 2023
1 parent 11a80b5 commit b237270
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
Binary file modified docs/assistant/images/assistant-settings-menu.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 2 additions & 2 deletions docs/assistant/security-assistant.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@

The Elastic AI Assistant utilizes generative AI to bolster your cybersecurity operations team. It allows users to interact with {elastic-sec} for tasks such as alert investigation, incident response, and query generation or conversion using natural language and much more.

A connector for OpenAI or Azure OpenAI Service powers AI Assistant.
AI Assistant relies on Generative AI connectors to third-party AI providers.

[role="screenshot"]
image::images/assistant.gif[Animation of AI Assistant chat window,90%]
Expand All @@ -34,7 +34,7 @@ For example, refer to OpenAI's documentation on https://platform.openai.com/docs

* To set up AI Assistant, you need the **Actions and Connectors : All** {kibana-ref}/kibana-privileges.html[privilege].

* You need an account with a third-party generative AI provider, which AI Assistant uses to generate responses. Supported providers are OpenAI and Azure OpenAI Service.
* You need an account with a third-party generative AI provider, which AI Assistant uses to generate responses. Supported providers are OpenAI, Azure OpenAI Service, and Amazon Bedrock.
--

[discrete]
Expand Down

0 comments on commit b237270

Please sign in to comment.