diff --git a/docs/assistant/images/assistant-settings-menu.png b/docs/assistant/images/assistant-settings-menu.png
index 2b0b60475a..8e2b271c58 100644
Binary files a/docs/assistant/images/assistant-settings-menu.png and b/docs/assistant/images/assistant-settings-menu.png differ
diff --git a/docs/assistant/security-assistant.asciidoc b/docs/assistant/security-assistant.asciidoc
index 6a073cc0d5..04e80daa82 100644
--- a/docs/assistant/security-assistant.asciidoc
+++ b/docs/assistant/security-assistant.asciidoc
@@ -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 communicate with third-party AI providers.
 
 [role="screenshot"]
 image::images/assistant.gif[Animation of AI Assistant chat window,90%]
@@ -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]