Merge remote-tracking branch 'upstream/main' into serverless-chrome/a…

…dd-panel-to-side-nav

.buildkite/pipelines/es_serverless/verify_es_serverless_image.yml

@@ -63,7 +63,7 @@ steps:
           queue: n2-4-spot
         depends_on: build
         timeout_in_minutes: 60
-        parallelism: 2
+        parallelism: 4
         retry:
           automatic:
             - exit_status: '*'

.buildkite/pipelines/on_merge.yml

@@ -85,7 +85,7 @@ steps:
       queue: n2-4-spot
     depends_on: build
     timeout_in_minutes: 60
-    parallelism: 2
+    parallelism: 4
     retry:
       automatic:
         - exit_status: '*'

.buildkite/pipelines/quality-gates/pipeline.tests-qa.yaml

@@ -13,12 +13,13 @@ steps:
         EC_REGION: aws-eu-west-1
       message: "${BUILDKITE_MESSAGE} (triggered by pipeline.tests-qa.yaml)"
 
-  - group: ":female-detective: Security Solution Tests"
-    key: "security"
-    steps:
-      - label: ":pipeline::female-detective::seedling: Trigger Security Solution quality gate script"
-        command: .buildkite/scripts/pipelines/security_solution_quality_gate/pipeline.sh
-        soft_fail: true # Remove this when tests are fixed
+  - label: ":pipeline::female-detective::seedling: Trigger Security Solution quality gate script"
+    trigger: security-serverless-quality-gate # https://buildkite.com/elastic/security-serverless-quality-gate
+    soft_fail: true # Remove this when tests are fixed
+    build:
+      env:
+        ENVIRONMENT: ${ENVIRONMENT}
+      message: "${BUILDKITE_MESSAGE} (triggered by pipeline.tests-qa.yaml)"
 
   - label: ":pipeline::ship::seedling: Trigger Fleet serverless smoke tests for ${ENVIRONMENT}"
     trigger: fleet-smoke-tests # https://buildkite.com/elastic/fleet-smoke-tests

.ci/Dockerfile

@@ -1,7 +1,7 @@
 # NOTE: This Dockerfile is ONLY used to run certain tasks in CI. It is not used to run Kibana or as a distributable.
 # If you're looking for the Kibana Docker image distributable, please see: src/dev/build/tasks/os_packages/docker_generator/templates/dockerfile.template.ts
 
-ARG NODE_VERSION=18.17.1
+ARG NODE_VERSION=18.18.2
 
 FROM node:${NODE_VERSION} AS base
 

.node-version

@@ -1 +1 @@
-18.17.1
+18.18.2

.nvmrc

@@ -1 +1 @@
-18.17.1
+18.18.2

WORKSPACE.bazel

@@ -22,13 +22,13 @@ load("@build_bazel_rules_nodejs//:index.bzl", "node_repositories", "yarn_install
 # Setup the Node.js toolchain for the architectures we want to support
 node_repositories(
   node_repositories = {
-    "18.17.1-darwin_amd64": ("node-v18.17.1-darwin-x64.tar.gz", "node-v18.17.1-darwin-x64", "b3e083d2715f07ec3f00438401fb58faa1e0bdf3c7bde9f38b75ed17809d92fa"),
-    "18.17.1-darwin_arm64": ("node-v18.17.1-darwin-arm64.tar.gz", "node-v18.17.1-darwin-arm64", "18ca716ea57522b90473777cb9f878467f77fdf826d37beb15a0889fdd74533e"),
-    "18.17.1-linux_arm64": ("node-v18.17.1-linux-arm64.tar.xz", "node-v18.17.1-linux-arm64", "2743722f164df953b11663a6c25f9cf35769bf500e712e21a6c20e896177da30"),
-    "18.17.1-linux_amd64": ("node-v18.17.1-linux-x64.tar.xz", "node-v18.17.1-linux-x64", "4612954fef461bb05ba952112636bd11e51c0a59db94e6c4b26328fee4d4d9ab"),
-    "18.17.1-windows_amd64": ("node-v18.17.1-win-x64.zip", "node-v18.17.1-win-x64", "afc83f5cf6e8b45a4d3fb842904f604dcd271fefada31ad6654f8302f8da28c9"),
+    "18.18.2-darwin_amd64": ("node-v18.18.2-darwin-x64.tar.gz", "node-v18.18.2-darwin-x64", "5bb8da908ed590e256a69bf2862238c8a67bc4600119f2f7721ca18a7c810c0f"),
+    "18.18.2-darwin_arm64": ("node-v18.18.2-darwin-arm64.tar.gz", "node-v18.18.2-darwin-arm64", "9f982cc91b28778dd8638e4f94563b0c2a1da7aba62beb72bd427721035ab553"),
+    "18.18.2-linux_arm64": ("node-v18.18.2-linux-arm64.tar.xz", "node-v18.18.2-linux-arm64", "8a5a03f6a742159c9aa0ae3a99b368cd938cf62f3a5522a2e5acbe6313710efe"),
+    "18.18.2-linux_amd64": ("node-v18.18.2-linux-x64.tar.xz", "node-v18.18.2-linux-x64", "f7cf590bc7153f3beaa9e1138d00e50d74df223f0bec61f63e7df65f7315b76a"),
+    "18.18.2-windows_amd64": ("node-v18.18.2-win-x64.zip", "node-v18.18.2-win-x64", "3bb0e51e579a41a22b3bf6cb2f3e79c03801aa17acbe0ca00fc555d1282e7acd"),
   },
-  node_version = "18.17.1",
+  node_version = "18.18.2",
   node_urls = [
     "https://us-central1-elastic-kibana-184716.cloudfunctions.net/kibana-ci-proxy-cache/dist/v{version}/{filename}",
   ],

docs/action-type-template.asciidoc

@@ -28,42 +28,9 @@ List of user-facing connector configurations. This should align with the fields
 Property1:: A short description of this property.
 Property2:: A short description of this property with format hints. This can be specified in `this specific format`.
 
-[float]
-[[preconfigured-<ACTION-TYPE>-configuration]]
-=== Create preconfigured connectors
-
-If you are running {kib} on-prem, you can define connectors by
-adding `xpack.actions.preconfigured` settings to your `kibana.yml` file.
-For example:
-
-////
-Example preconfigured format for this connector type
-////
-
-[source,text]
---
-xpack.actions.preconfigured:
-  my-<ACTION-TYPE>:
-    name: preconfigured-<ACTION-TYPE>-connector-type
-    actionTypeId: .<ACTION-TYPE>
-    config:
-      property1: value1
-      property2: value2
-    secrets:
-      property3: value3
---
-
 ////
-List of properties from the ConfigSchema and SecretsSchema for this action type.
+Add preconfigured settings for this connector type in alert-action-settings.asciidoc and an example in pre-configured-connectors.asciidoc.
 ////
-Config defines information for the connector type.
-
-`property1`:: A short description of this property.
-`property2`:: A short descriptionn of this property.
-
-Secrets defines sensitive information for the connector type.
-
-`property3`:: A short descriptionn of this property.
 
 [float]
 [[<ACTION-TYPE>-action-configuration]]

docs/developer/advanced/upgrading-nodejs.asciidoc

@@ -17,7 +17,7 @@ These files must be updated when upgrading Node.js:
   - {kib-repo}blob/{branch}/WORKSPACE.bazel[`WORKSPACE.bazel`] - The version is specified in the `node_version` property.
     Besides this property, the list of files under `node_repositories` must be updated along with their respective SHA256 hashes.
     These can be found on the https://nodejs.org[nodejs.org] website.
-    Example for Node.js v18.17.1: https://nodejs.org/dist/v18.17.1/SHASUMS256.txt.asc
+    Example for Node.js v18.18.2: https://nodejs.org/dist/v18.18.2/SHASUMS256.txt.asc
 
 See PR {kib-repo}pull/128123[#128123] for an example of how the Node.js version has been upgraded previously.
 

docs/management/action-types.asciidoc

@@ -7,9 +7,9 @@ Connectors provide a central place to store connection information for services
 [cols="2"]
 |===
 
-a| <<bedrock-action-type,AWS Bedrock>>
+a| <<bedrock-action-type,{bedrock}>>
 
-| Send a request to AWS Bedrock.
+| Send a request to {bedrock}.
 
 a| <<d3security-action-type,D3 Security>>
 

docs/management/cases/add-connectors.asciidoc

@@ -1,7 +1,10 @@
 [[add-case-connectors]]
 == Add connectors
 
-preview::[]
+:frontmatter-description: Configure connectors to push case details to external incident management systems.
+:frontmatter-tags-products: [kibana]
+:frontmatter-tags-content-type: [how-to] 
+:frontmatter-tags-user-goals: [configure]
 
 You can add connectors to cases to push information to these external incident
 management systems:
@@ -24,7 +27,7 @@ You can create connectors in *{stack-manage-app} > {connectors-ui}*,
 as described in <<action-types>>. Alternatively, you can create them in
 *{stack-manage-app} > Cases*:
 
-. Click *Edit external connection*.
+. Click *Settings*.
 +
 --
 [role="screenshot"]
@@ -50,7 +53,7 @@ configuration details.
 You can create additional connectors, update existing connectors, change
 the default connector, and change case closure options.
 
-. Go to *{stack-manage-app} > Cases*, click *Edit external connection*.
+. Go to *{stack-manage-app} > Cases* and click *Settings*.
 
 . To change whether cases are automatically closed after they are sent to an
 external system, update the case closure options.

docs/management/cases/cases.asciidoc

@@ -1,7 +1,9 @@
 [[cases]]
 == Cases
-
-preview::[]
+:frontmatter-description: Open and track issues in {kib} cases. 
+:frontmatter-tags-products: [kibana]
+:frontmatter-tags-content-type: [overview] 
+:frontmatter-tags-user-goals: [analyze]
 
 Cases are used to open and track issues directly in {kib}. You can add
 assignees and tags to your cases, set their severity and status, and add alerts,

docs/management/cases/manage-cases.asciidoc

@@ -6,8 +6,6 @@
 :frontmatter-tags-content-type: [how-to] 
 :frontmatter-tags-user-goals: [analyze]
 
-preview::[]
-
 [[open-case]]
 === Open a new case
 

docs/management/cases/setup-cases.asciidoc

@@ -1,7 +1,10 @@
 [[setup-cases]]
 == Configure access to cases
 
-preview::[]
+:frontmatter-description: Learn about the {kib} feature privileges required to access cases. 
+:frontmatter-tags-products: [kibana]
+:frontmatter-tags-content-type: [how-to] 
+:frontmatter-tags-user-goals: [configure]
 
 To access cases in *{stack-manage-app}*, you must have the appropriate {kib}
 privileges:

docs/management/connectors/action-types/bedrock.asciidoc

@@ -1,15 +1,15 @@
 [[bedrock-action-type]]
-== AWS Bedrock connector and action
+== {bedrock} connector and action
 ++++
-<titleabbrev>AWS Bedrock</titleabbrev>
+<titleabbrev>{bedrock}</titleabbrev>
 ++++
-:frontmatter-description: Add a connector that can send requests to AWS Bedrock.
+:frontmatter-description: Add a connector that can send requests to {bedrock}.
 :frontmatter-tags-products: [kibana] 
 :frontmatter-tags-content-type: [how-to] 
 :frontmatter-tags-user-goals: [configure]
 
 
-The AWS Bedrock connector uses https://github.com/axios/axios[axios] to send a POST request to AWS Bedrock. The connector uses the <<execute-connector-api,run connector API>> to send the request.
+The {bedrock} connector uses https://github.com/axios/axios[axios] to send a POST request to {bedrock}. The connector uses the <<execute-connector-api,run connector API>> to send the request.
 
 [float]
 [[define-bedrock-ui]]
@@ -19,18 +19,18 @@ You can create connectors in *{stack-manage-app} > {connectors-ui}*.  For exampl
 
 [role="screenshot"]
 // TODO: need logo before screenshot
-image::management/connectors/images/bedrock-connector.png[AWS Bedrock connector]
+image::management/connectors/images/bedrock-connector.png[{bedrock} connector]
 
 [float]
 [[bedrock-connector-configuration]]
 ==== Connector configuration
 
-AWS Bedrock connectors have the following configuration properties:
+{bedrock} connectors have the following configuration properties:
 
 Name::      The name of the connector.
-API URL::   The AWS Bedrock request URL.
-Default model:: The GAI model for AWS Bedrock to use. Current support is for the Anthropic Claude models, defaulting to Claude 2. The model can be set on a per request basis by including a "model" parameter alongside the request body.
-Region::   The AWS Bedrock request URL.
+API URL::   The {bedrock} request URL.
+Default model:: The GAI model for {bedrock} to use. Current support is for the Anthropic Claude models, defaulting to Claude 2. The model can be set on a per request basis by including a "model" parameter alongside the request body.
+Region::   The {bedrock} request URL.
 Access Key::   The AWS access key for authentication.
 Secret::   The secret for authentication.
 
@@ -43,11 +43,11 @@ as you're creating or editing the connector in {kib}. For example:
 
 [role="screenshot"]
 // TODO: need logo before screenshot
-image::management/connectors/images/bedrock-params.png[AWS Bedrock params test]
+image::management/connectors/images/bedrock-params.png[{bedrock} params test]
 
-The AWS Bedrock actions have the following configuration properties.
+The {bedrock} actions have the following configuration properties.
 
-Body::      A stringified JSON payload sent to the AWS Bedrock Invoke Model API URL. For example:
+Body::      A stringified JSON payload sent to the {bedrock} Invoke Model API URL. For example:
 +
 [source,text]
 --

docs/management/connectors/pre-configured-connectors.asciidoc

@@ -1,5 +1,9 @@
 [[pre-configured-connectors]]
 == Preconfigured connectors
+:frontmatter-description: Define connectors in the {kib} configuration file.
+:frontmatter-tags-products: [kibana] 
+:frontmatter-tags-content-type: [how-to] 
+:frontmatter-tags-user-goals: [configure]
 
 If you are running {kib} on-prem, you can preconfigure a connector to have all
 the information it needs prior to startup by adding it to the `kibana.yml` file.
@@ -20,6 +24,7 @@ predefined, including the connector name and ID.
 
 Add `xpack.actions.preconfigured` settings to your `kibana.yml` file. The
 settings vary depending on which type of connector you're adding.
+Refer to <<preconfigured-connector-settings>>.
 
 This example shows a valid configuration for a Slack connector and a Webhook
 connector:
@@ -107,6 +112,7 @@ Index names must start with `kibana-alert-history-` to take advantage of the pre
 [[preconfigured-connector-examples]]
 === Examples
 
+* <<preconfigured-bedrock-configuration>>
 * <<preconfigured-d3security-configuration>>
 * <<preconfigured-email-configuration>>
 * <<preconfigured-gen-ai-configuration>>
@@ -128,6 +134,30 @@ Index names must start with `kibana-alert-history-` to take advantage of the pre
 * <<preconfigured-cases-webhook-configuration>>
 * <<preconfigured-xmatters-configuration>>
 
+[float]
+[[preconfigured-bedrock-configuration]]
+==== {bedrock} connectors
+
+The following example creates an <<bedrock-action-type,{bedrock} connector>>:
+
+[source,text]
+--
+xpack.actions.preconfigured:
+  my-bedrock:
+    name: preconfigured-bedrock-connector-type
+    actionTypeId: .bedrock
+    config:
+      apiUrl: https://bedrock.us-east-1.amazonaws.com <1>
+      defaultModel: anthropic.claude-v2 <2>
+    secrets:
+      accessKey: key-value <3>
+      secret: secret-value <4>
+--
+<1> The {bedrock} request URL.
+<2> The default model to use for requests. Current support is for the Anthropic Claude models, defaulting to Claude 2.
+<3> The AWS access key for authentication.
+<4> The AWS secret for authentication.
+
 [float]
 [[preconfigured-d3security-configuration]]
 ==== D3 Security connectors
@@ -302,7 +332,7 @@ xpack.actions.preconfigured:
     secrets:
       apiKey: superlongapikey <4>
 --
-<1> The OpenAI request URL
+<1> The OpenAI request URL.
 <2> The OpenAI API provider, either `OpenAI` or `Azure OpenAI`.
 <3> The default model to use for requests. This setting is optional and applicable only when `apiProvider` is `OpenAI`.
 <4> The OpenAI or Azure OpenAI API key for authentication.

docs/settings/alert-action-settings.asciidoc

@@ -267,6 +267,7 @@ For a <<openai-action-type,OpenAI connector>>, specifies the OpenAI API provider
 A configuration URL that varies by connector:
 +
 --
+* For an <<bedrock-action-type,{bedrock} connector>>, specifies the {bedrock} request URL.
 * For a <<openai-action-type,OpenAI connector>>, specifies the OpenAI request URL.
 * For a <<resilient-action-type,{ibm-r} connector>>, specifies the {ibm-r} instance URL.
 * For a <<jira-action-type,Jira connector>>, specifies the Jira instance URL.
@@ -327,7 +328,12 @@ NOTE: If you are using the `xpack.actions.allowedHosts` setting, make sure the h
 For a <<cases-webhook-action-type,{webhook-cm} connector>>, specifies a string from the response body of the create case method that corresponds to the external service identifier.
 
 `xpack.actions.preconfigured.<connector-id>.config.defaultModel`::
-For a <<openai-action-type,OpenAI connector>>, specifies the default model to use for requests. It is optional and applicable only when `xpack.actions.preconfigured.<connector-id>.config.apiProvider` is `OpenAI`.
+The default model to use for requests, which varies by connector:
++
+--
+* For an <<bedrock-action-type,{bedrock} connector>>, current support is for the Anthropic Claude models. Defaults to `anthropic.claude-v2`.
+* For a <<openai-action-type,OpenAI connector>>, it is optional and applicable only when `xpack.actions.preconfigured.<connector-id>.config.apiProvider` is `OpenAI`.
+--
 
 `xpack.actions.preconfigured.<connector-id>.config.executionTimeField`::
 For an <<index-action-type,index connector>>, a field that indicates when the document was indexed.
@@ -463,6 +469,9 @@ Sensitive configuration details, such as username, password, and keys, which are
 +
 TIP: Sensitive properties, such as passwords, should be stored in the <<creating-keystore,{kib} keystore>>.
 
+`xpack.actions.preconfigured.<connector-id>.secrets.accessKey`::
+For an <<bedrock-action-type,{bedrock} connector>>, specifies the AWS access key for authentication.
+
 `xpack.actions.preconfigured.<connector-id>.secrets.apikey`::
 An API key secret that varies by connector:
 +
@@ -517,6 +526,9 @@ For a <<servicenow-action-type,{sn-itsm}>>, <<servicenow-sir-action-type,{sn-sir
 `xpack.actions.preconfigured.<connector-id>.secrets.routingKey`::
 For a <<pagerduty-action-type,PagerDuty connector>>, specifies the 32 character PagerDuty Integration Key for an integration on a service, also referred to as the routing key.
 
+`xpack.actions.preconfigured.<connector-id>.secrets.secret`::
+For an <<bedrock-action-type,{bedrock} connector>>, specifies the AWS secret for authentication.
+
 `xpack.actions.preconfigured.<connector-id>.secrets.secretsUrl`::
 For an <<xmatters-action-type,xMatters connector>> with URL authentication, specifies the request URL for the Elastic Alerts trigger in xMatters with the API key included in the URL.
 It is used only when `xpack.actions.preconfigured.<connector-id>.config.usesBasic` is `false`.