Merge branch 'main' into best-practices-ingest-pipelines

Author: colleenmcginnis

.github/CODEOWNERS

@@ -47,8 +47,6 @@
 /solutions/observability/get-started/       @elastic/ski-docs
 /solutions/search/                          @elastic/developer-docs
 /solutions/security/                        @elastic/experience-docs
-/solutions/security/get-started/            @elastic/ingest-docs @elastic/experience-docs
-/solutions/security/cloud/                  @elastic/ingest-docs
 
 /troubleshoot/                              @elastic/docs
 /troubleshoot/deployments/                  @elastic/admin-docs

.github/ISSUE_TEMPLATE/b-internal-request.yaml

@@ -65,6 +65,7 @@ body:
         - '8.19'
         - '9.0'
         - '9.1'
+        - '9.2'
       default: 0
     validations:
       required: true

.github/workflows/comment-on-removed-files.yml

@@ -6,7 +6,7 @@ applies_to:
 
 # Use dark mode in Kibana
 
-The dark mode changes Kibana's default light appearance to a darker and higher-contrast color theme. From the application header, you can turn on dark mode or synchronize the color mode with your operating system settings.
+The dark mode changes Kibana's default light appearance to a darker color theme. From the application header, you can turn on dark mode or synchronize the color mode with your operating system settings.
 
 :::{tip}
 If you're using {{ecloud}}, this setting only applies to the Kibana UI of your serverless projects and hosted deployments. If you'd like to change the {{ecloud}} Console color theme too, you must do so separately from its respective interface.
@@ -16,10 +16,15 @@ If you're using {{ecloud}}, this setting only applies to the Kibana UI of your s
 
 1. Open the user menu from the header.
 2. Select **Appearance**.
+   
+   :::{note}
+   On self-managed deployments of {{kib}}, this option is located on your profile page. To access it, select **Edit profile** from the header's user menu.
+   :::
+
 3. Choose a color mode:
 
     - **Light**: The default color mode of Kibana
-    - **Dark**: The dark and high-contrast color mode of Kibana
+    - **Dark**: The dark color mode of Kibana
     - **System**: Synchronizes Kibana's color mode with your system settings
     - **Space default**: Sets the color mode to the value defined in the [Space settings](kibana://reference/advanced-settings.md#kibana-general-settings)
 

cloud-account/dark-mode.md

@@ -0,0 +1,28 @@
+---
+description: Use high-contrast mode in Kibana.
+applies_to:
+  stack: ga 9.1
+  serverless: ga
+products:
+  - id: kibana
+---
+
+# Use high-contrast mode in Kibana
+
+You can change the interface contrast mode of Kibana to improve visibility and readability in low-light conditions.
+
+1. Open the user menu from the header.
+2. Select **Appearance**.
+   
+   :::{note}
+   On self-managed deployments of {{kib}}, this option is located on your profile page. To access it, select **Edit profile** from the header's user menu.
+   :::
+
+3. Choose an interface contrast mode:
+
+    - **System**: Synchronizes Kibana's contrast mode with your system settings.
+    - **Normal**: Normal contrast mode.
+    - **High**: The high-contrast color mode of Kibana.
+
+4. Select **Save changes**.
+5. Refresh the page to apply the selected contrast mode.

cloud-account/high-contrast.md

@@ -6,4 +6,5 @@ toc:
   - file: change-your-password.md
   - file: add-a-login-method.md
   - file: multifactor-authentication.md
-  - file: dark-mode.md
+  - file: dark-mode.md
+  - file: high-contrast.md

cloud-account/toc.yml

@@ -0,0 +1,6 @@
+:::{dropdown} Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?
+
+This path is not supported. Currently, we only support using Cloud Connect to connect ECE, ECK, and self-managed clusters to AutoOps.
+
+For {{ech}} clusters, AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), and can be [accessed](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) from the deployment overview page. 
+:::

deploy-manage/_snippets/autoops-cc-ech-faq.md

@@ -0,0 +1 @@
+Using [AutoOps for ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) through Cloud Connect is included with your [self-managed Enterprise license](https://www.elastic.co/subscriptions).

deploy-manage/_snippets/autoops-cc-payment-faq.md

@@ -1,7 +1,9 @@
 {{ecloud}} has built-in security. For example, HTTPS communications between {{ecloud}} and the internet, as well as inter-node communications, are secured automatically, and cluster data is encrypted at rest.
 
+In both {{ech}} and {{serverless-full}}, you can also configure [IP filters](/deploy-manage/security/ip-filtering-cloud.md) to prevent unauthorized access to your deployments and projects.
+
 In {{ech}}, you can augment these security features in the following ways:
-* Configure [traffic filtering](/deploy-manage/security/traffic-filtering.md) to prevent unauthorized access to your deployments.
+* [Configure private connectivity and apply VPC filtering](/deploy-manage/security/private-connectivity.md) to establish a secure connection for your {{ecloud}} deployments to communicate with other cloud services, and restrict traffic to deployments based on those private connections.
 * Encrypt your deployment with a [customer-managed encryption key](/deploy-manage/security/encrypt-deployment-with-customer-managed-encryption-key.md).
 * [Secure your settings](/deploy-manage/security/secure-settings.md) using {{es}} and {{kib}} keystores.
 * Use the list of [{{ecloud}} static IPs](/deploy-manage/security/elastic-cloud-static-ips.md) to allow or restrict communications in your infrastructure.

deploy-manage/_snippets/ecloud-security.md

@@ -0,0 +1,5 @@
+::::{note}
+With [{{serverless-full}}](/deploy-manage/deploy/elastic-cloud/serverless.md), upgrades of the Elastic-managed infrastructure and project components are fully handled by Elastic. Users automatically receive the latest features and improvements, with no need to plan or perform project-level upgrades.
+
+Keep in mind that the [ingest components](/deploy-manage/upgrade/ingest-components.md) or clients you manage externally, such as {{agent}}, {{beats}}, {{ls}}, or custom applications, still need to be updated manually.
+::::