Add/update AutoOps and Cloud Connect callouts across the docs

deploy-manage/_snippets/autoops-callout-with-ech.md

@@ -0,0 +1,5 @@
+:::{admonition} Simplify monitoring with AutoOps
+Use AutoOps in your {{ech}}, ECE, ECK, or self-managed deployments. 
+
+AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+::::

deploy-manage/cloud-connect.md

@@ -9,7 +9,7 @@ navigation_title: Cloud Connect
 
 # Cloud Connect
 
-Cloud Connect enables you to use {{ecloud}} services in your ECE, ECK, or self-managed cluster without having to install and maintain their infrastructure yourself. In this way, you can get faster access to new features while significantly reducing your operational overhead.
+Cloud Connect enables you to use {{ecloud}} services in your ECE, ECK, or self-managed cluster without having to install and maintain their infrastructure yourself. In this way, you can get faster access to new features without adding to your operational overhead.
 
 AutoOps is the first service available for use with Cloud Connect. More services are coming soon.
 

deploy-manage/cloud-organization/billing/billing-faq.md

@@ -98,8 +98,8 @@ $$$faq-deleteaccount$$$How can I delete my {{ecloud}} account?
 $$$faq-refund$$$Can I get a refund?
 :   Charges are non-refundable, but once you delete a deployment we’ll stop charging you for that deployment immediately. You only pay for what you use and you can stop using the service at any time. For any special considerations warranting a potential refund, use the {{ecloud}} Console [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) to open a support case and select *Billing issue* as the category. To ensure quick processing, be sure to provide detail about the reasons for the refund request as well as other matters pertaining to the issue. For other ways to open a Support case, check [Contact us](../../../troubleshoot/index.md).
 
-$$$billing-cc-additional-payment$$$ **Does Cloud Connect require additional payment?** 
-:   Each cloud connected service has its own licensing and payment requirements. For more information, refer to the [Elastic self-managed subscriptions](https://www.elastic.co/subscriptions) page.
+$$$billing-cc-additional-payment$$$Does Cloud Connect require additional payment?
+:   Each [cloud connected service](/deploy-manage/cloud-connect.md) has its own licensing and payment requirements. For more information, refer to the [Elastic self-managed subscriptions](https://www.elastic.co/subscriptions) page.
 
 $$$faq-included$$$What is included in my paid {{ech}} deployment?
 :   All subscription tiers for {{ech}} include the following free allowance:

deploy-manage/deploy.md

@@ -38,6 +38,10 @@ To learn how to deploy optional {{stack}} components, refer to the following sec
 :::{include} _snippets/deployment-options-overview.md
 :::
 
+::::{tip}
+Documentation will specify when certain features or configurations are not applicable to specific deployment types.
+::::
+
 ### Who manages the infrastructure?
 
 #### Managed by Elastic
@@ -58,8 +62,8 @@ If you need to run Elastic on your infrastructure, choose between a fully self-m
   - **{{eck}} (ECK)**: If you need Kubernetes-native orchestration
   - **{{ece}} (ECE)**: If you need a multi-tenant orchestration platform
 
-::::{tip}
-Documentation will specify when certain features or configurations are not applicable to specific deployment types.
+:::{admonition} Use cloud services in your self-hosted environment with Cloud Connect
+With [Cloud Connect](/deploy-manage/cloud-connect.md), you can use Elastic-managed cloud services in your self-managed, ECE, or ECK environment without having to install and manage their infrastructure yourself. In this way, you can get faster access to new features without adding to your operational overhead.
 ::::
 
 ### About orchestration
@@ -100,5 +104,5 @@ Learn more about [versioning and availability](/get-started/versioning-availabil
 - **Self-hosted options**: Infrastructure costs plus operational overhead mean a higher total cost of ownership (TCO)
 
 :::::{tip}
-For a detailed comparison of features and capabilities across deployment types, see the [Deployment comparison reference](./deploy/deployment-comparison.md).
+For a detailed comparison of features and capabilities across deployment types, see the [](./deploy/deployment-comparison.md).
 :::::

deploy-manage/deploy/cloud-enterprise.md

@@ -24,6 +24,10 @@ With {{ece}}, you can:
 
 Refer to [](./cloud-enterprise/ece-architecture.md) for details about the ECE platform architecture and the technologies used.
 
+:::{admonition} Use cloud services in your ECE environment with Cloud Connect
+With [Cloud Connect](/deploy-manage/cloud-connect.md), you can use Elastic-managed cloud services in your ECE environment without having to install and manage their infrastructure yourself. In this way, you can get faster access to new features without adding to your operational overhead.
+::::
+
 ## ECE features
 
 - **Automated scaling & orchestration**: Handles cluster provisioning, scaling, and upgrades automatically.

deploy-manage/deploy/cloud-on-k8s.md

@@ -16,6 +16,10 @@ products:
 
 Built on the Kubernetes Operator pattern, {{eck}} (ECK) extends the basic Kubernetes orchestration capabilities to support the setup and management of {{eck_resources_list}} on Kubernetes.
 
+:::{admonition} Use cloud services in your ECK environment with Cloud Connect
+With [Cloud Connect](/deploy-manage/cloud-connect.md), you can use Elastic-managed cloud services in your ECK environment without having to install and manage their infrastructure yourself. In this way, you can get faster access to new features without adding to your operational overhead.
+::::
+
 ## ECK overview
 
 With {{eck}}, you can streamline critical operations, such as:
@@ -35,7 +39,7 @@ This section provides everything you need to install, configure, and manage {{st
 
 Other sections of the documentation include the following important topics around ECK:
 
-- [Logging and Monitoring](../monitor.md): Configure stack monitoring and logs forwarding with the help of ECK.
+- [Logging and Monitoring](../monitor.md): Configure monitoring and logs forwarding with the help of ECK.
 - [Remote Clusters](../remote-clusters.md): Configure remote clusters on ECK.
 - [](../tools.md): Add snapshot repositories to your {{es}} clusters for automatic snapshots.
 - [Security](../security.md): Secure communications, manage HTTP certificates, or add secure settings to your applications.

deploy-manage/deploy/elastic-cloud/cloud-hosted.md

@@ -80,7 +80,10 @@ Refer to [](/deploy-manage/security.md) for more details.
 
 **Monitor your deployments and keep them healthy**
 
-{{ech}} provides several ways to monitor your deployments, anticipate and prevent issues, or fix them when they occur. Check [Monitoring your deployment](/deploy-manage/monitor.md) to get more details.
+{{ech}} provides several ways to monitor your deployments, anticipate and prevent issues, or fix them when they occur. Check [](/deploy-manage/monitor.md) to get more details.
+
+:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md
+:::
 
 ## More about {{ech}} [ec-about]
 

deploy-manage/deploy/self-managed.md

@@ -29,6 +29,12 @@ Self-hosted options:
 For a comparison of these deployment options, refer to [Choosing your deployment type](/deploy-manage/deploy.md#choosing-your-deployment-type) and [](/deploy-manage/deploy/deployment-comparison.md).
 :::
 
+:::{admonition} Use cloud services in your self-managed cluster with Cloud Connect
+If you need to run Elastic on your own infrastructure, use [Cloud Connect](/deploy-manage/cloud-connect.md). Cloud connect enables you to use Elastic-managed cloud services in your self-managed cluster without having to install and manage their infrastructure yourself.
+
+This way, you can get faster access to new cloud features while still meeting your infrastructure requirements.
+:::: 
+
 ## Section overview
 
 This section focuses on deploying {{es}} and {{kib}} without an orchestrator.

deploy-manage/index.md

@@ -44,6 +44,7 @@ Learn how to design and deploy a production-ready Elastic environment.
 * [](/deploy-manage/reference-architectures.md): Explore blueprints for deploying clusters tailored to different use cases.
 * [](/deploy-manage/tools.md): Learn about the tools available to safeguard data, ensure continuous availability, and maintain resilience in your {{es}} environment.
 * [](/deploy-manage/autoscaling.md): Learn how to configure your [orchestrated](/deploy-manage/deploy.md#about-orchestration) deployment to scale based on policies and cluster signals. Applies to {{ech}}, {{ece}}, and {{eck}} deployments.
+* [](/deploy-manage/cloud-connect.md): Learn how to use {{ecloud}} services in your self-hosted environment.
 
 :::{admonition} Serverless does it for you
 If you deploy an {{serverless-full}} project, then you don't need to learn about Elastic architecture, production design, resilience, or scaling concepts. Serverless automatically scales and backs up your cluster for you, and is ready for production out of the box.

deploy-manage/monitor.md

@@ -21,15 +21,17 @@ Depending on your deployment type, you can use a variety of solutions for monito
 
 ## Monitoring your cluster or deployment
 
-Depending on your deployment type and context, you have several options for monitoring your cluster or deployment.
+You have several options for monitoring your cluster or deployment.
 
-If you’re using {{ech}}, you can use [AutoOps](/deploy-manage/monitor/autoops.md) to monitor your cluster. 
+Use [AutoOps](/deploy-manage/monitor/autoops.md) in your {{ech}}, ECE, ECK, or self-managed deployments. AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. 
 
-AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection, and resolution paths. AutoOps is [rolling out](/deploy-manage/monitor/autoops/ec-autoops-regions.md) in phases across {{ech}} regions and cloud service providers. It will be automatically activated for your deployment with no installation required.
+Alternatively, you can use [Stack Monitoring](/deploy-manage/monitor/stack-monitoring.md) to monitor logs and metrics across the {{stack}}.
 
-For other deployment types, use [Stack Monitoring](/deploy-manage/monitor/stack-monitoring.md) to monitor logs and metrics across the {{stack}}.
+To help you decide between these two options, refer to [](/deploy-manage/monitor/autoops-vs-stack-monitoring.md).
 
-To help you make your decision, refer to [](/deploy-manage/monitor/autoops-vs-stack-monitoring.md).
+For ECE and {{ech}} deployments, there are also a number of out of the box monitoring tools available.
+
+The following sections provide more details.
 
 ### AutoOps (recommended)
 
@@ -43,7 +45,7 @@ deployment:
 
 AutoOps diagnoses issues in {{es}} by analyzing hundreds of metrics, providing root-cause analysis and accurate resolution paths. With AutoOps, customers can prevent and resolve issues, cut down administration time, and optimize resource utilization.
 
-AutoOps is available in all {{ech}} deployments and {{serverless-full}} projects, and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md). 
+In the [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md), and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md).
 
 ### Stack monitoring
 

deploy-manage/monitor/autoops.md

@@ -3,6 +3,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-autoops.html
 applies_to:
   deployment:
+  serverless:
     ess: all
     self:
     ece:
@@ -45,24 +46,28 @@ AutoOps diagnoses issues in {{es}} by analyzing hundreds of metrics, providing r
 * Possibility to customize event triggers and connect to different notification services such as PagerDuty, Slack, MS Teams, and webhooks.
 * Long-term reports for sustained evaluation. This feature is currently not available and will be rolled out shortly.
 
+## AutoOps availability
+
+In the [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md).
+
+AutoOps is currently not available for air-gapped environments since it is a cloud service and you need an internet connection to send metrics to {{ecloud}}. However, we plan to offer a locally deployable version in the future.
 
 ## AutoOps retention period [ec_autoops_retention_period]
 
-AutoOps currently has a 10 day retention period for all {{ech}} customers.
+AutoOps currently has a 10 day retention period.
 
 
 ## AutoOps scope [ec_autoops_scope]
 
-AutoOps currently monitors only {{es}}, not the entire {{stack}}. Any deployment information pertains solely to {{es}}. AutoOps supports {{es}} versions according to the [supported {{es}} versions](https://www.elastic.co/support/eol). There are plans to expand AutoOps monitoring to the entire stack.
-
+AutoOps currently monitors only {{es}}, not the entire {{stack}}. Any deployment information pertains solely to {{es}}. AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol)(7.17.x and above). We plan to expand AutoOps monitoring to the entire stack in the future.
 
 ## Section overview
 
 In this section, you'll find the following information:
 
 * How to [access AutoOps in your {{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md).
 * How to [connect your ECE, ECK, or self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) to AutoOps.
+* [Regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where AutoOps is available.
 * What [events](/deploy-manage/monitor/autoops/ec-autoops-events.md) are and how you can configure [event settings](/deploy-manage/monitor/autoops/ec-autoops-event-settings.md) and [notifications](/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md).
 * Which [views](/deploy-manage/monitor/autoops/views.md) AutoOps offers to gain insight into your deployment.
-* [Regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where AutoOps is available.
 * [Frequently asked questions](/deploy-manage/monitor/autoops/ec-autoops-faq.md) about AutoOps.

deploy-manage/monitor/autoops/ec-autoops-faq.md

@@ -23,7 +23,7 @@ $$$faq-what-is-autoops$$$What does AutoOps do?
 :   AutoOps for {{es}} significantly simplifies cluster management with performance recommendations, resource utilization and cost insights, real-time issue detection and resolution paths. By analyzing hundreds of {{es}} metrics, your configuration, and usage patterns, AutoOps recommends operational and monitoring insights that deliver savings in administration time and hardware costs.
 
 $$$faq-autoops-deployment-types$$$Is AutoOps available in all types of deployments?
-:   In the [regions](ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and {{serverless-full}} projects, and can be [set up](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) for ECE, ECK, and self-managed clusters.
+:   In the [regions](ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md).
 
 $$$faq-autoops-regions$$$Why can't I see AutoOps in some deployments?
 :   AutoOps is rolling out in phases across CSPs and [regions](ec-autoops-regions.md), so you may not see it if your deployment is in a region where AutoOps is not available yet. 

deploy-manage/monitor/stack-monitoring.md

@@ -17,10 +17,13 @@ products:
 :::{include} _snippets/stack-monitoring-def.md
 :::
 
-::::{admonition} Better monitoring with AutoOps
-:::{include} _snippets/autoops.md
+:::{admonition} Simplify monitoring with AutoOps
+Use [AutoOps](/deploy-manage/monitor/autoops.md) in your {{ech}}, ECE, ECK, or self-managed deployments. 
+
+AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. In the [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md).
+
+To help you make your decision, refer to [](/deploy-manage/monitor/autoops-vs-stack-monitoring.md).
 :::
-::::
 
 ## How it works
 

deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md

@@ -32,10 +32,7 @@ Monitoring consists of two components:
 
 With logging and monitoring enabled for a deployment, metrics are collected for {{es}}, {{kib}}, and APM with Fleet Server.
 
-:::{admonition} Simplify monitoring with AutoOps
-If you’re using {{ech}}, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths.
-
-For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md
 :::
 
 ## Before you begin [logging-and-monitoring-limitations]

deploy-manage/toc.yml

@@ -451,6 +451,7 @@ toc:
       - file: autoscaling/autoscaling-in-eck.md
       - file: autoscaling/autoscaling-deciders.md
       - file: autoscaling/trained-model-autoscaling.md
+  - file: cloud-connect.md
   - file: security.md
     children:
       - file: security/secure-hosting-environment.md
@@ -657,7 +658,6 @@ toc:
           - file: remote-clusters/remote-clusters-migrate.md
           - file: remote-clusters/remote-clusters-settings.md
       - file: remote-clusters/eck-remote-clusters.md
-  - file: cloud-connect.md
   - file: monitor.md
     children:
       - file: monitor/autoops.md

troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md

@@ -19,4 +19,7 @@ The **Deployments** page in the Cloud UI provides several ways to find deploymen
 
 * Use the visual indicators to review the health of your deployments at a glance.
 * Search by full or partial deployment names or IDs.
-* Use the **Health** and **Version** dropdown filters to narrow the list of deployments shown. These filters help you find deployments by version, configuration status, or other attributes, making it easier to identify those that require upgrades, are undergoing changes, or match specific operational criteria.
+* Use the **Health** and **Version** dropdown filters to narrow the list of deployments shown. These filters help you find deployments by version, configuration status, or other attributes, making it easier to identify those that require upgrades, are undergoing changes, or match specific operational criteria.
+
+:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md
+:::