Skip to content

Commit 34f9e49

Browse files
authored
Add/update AutoOps and Cloud Connect callouts across the docs (#3385)
This PR includes the following: - adds/updates AutoOps callouts to bring attention to Cloud Connect and AutoOps for self-managed clusters - adds connective tissue between related deployment pages and Cloud Connect - makes small fixes for typos/links when I came across them Closes elastic/docs-content-internal#13 and elastic/opex-product#617
1 parent db19958 commit 34f9e49

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

54 files changed

+166
-131
lines changed
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
:::{admonition} Simplify monitoring with AutoOps
2+
Use AutoOps in your {{ech}}, ECE, ECK, or self-managed deployments.
3+
4+
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).
5+
::::

deploy-manage/cloud-connect.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ navigation_title: Cloud Connect
99

1010
# Cloud Connect
1111

12-
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.
12+
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.
1313

1414
AutoOps is the first service available for use with Cloud Connect. More services are coming soon.
1515

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -98,8 +98,8 @@ $$$faq-deleteaccount$$$How can I delete my {{ecloud}} account?
9898
$$$faq-refund$$$Can I get a refund?
9999
: 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).
100100

101-
$$$billing-cc-additional-payment$$$ **Does Cloud Connect require additional payment?**
102-
: 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.
101+
$$$billing-cc-additional-payment$$$Does Cloud Connect require additional payment?
102+
: 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.
103103

104104
$$$faq-included$$$What is included in my paid {{ech}} deployment?
105105
: All subscription tiers for {{ech}} include the following free allowance:

deploy-manage/deploy.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,10 @@ To learn how to deploy optional {{stack}} components, refer to the following sec
3838
:::{include} _snippets/deployment-options-overview.md
3939
:::
4040

41+
::::{tip}
42+
Documentation will specify when certain features or configurations are not applicable to specific deployment types.
43+
::::
44+
4145
### Who manages the infrastructure?
4246

4347
#### Managed by Elastic
@@ -58,8 +62,8 @@ If you need to run Elastic on your infrastructure, choose between a fully self-m
5862
- **{{eck}} (ECK)**: If you need Kubernetes-native orchestration
5963
- **{{ece}} (ECE)**: If you need a multi-tenant orchestration platform
6064

61-
::::{tip}
62-
Documentation will specify when certain features or configurations are not applicable to specific deployment types.
65+
:::{admonition} Use cloud services in your self-hosted environment with Cloud Connect
66+
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.
6367
::::
6468

6569
### About orchestration
@@ -100,5 +104,5 @@ Learn more about [versioning and availability](/get-started/versioning-availabil
100104
- **Self-hosted options**: Infrastructure costs plus operational overhead mean a higher total cost of ownership (TCO)
101105

102106
:::::{tip}
103-
For a detailed comparison of features and capabilities across deployment types, see the [Deployment comparison reference](./deploy/deployment-comparison.md).
107+
For a detailed comparison of features and capabilities across deployment types, see the [](./deploy/deployment-comparison.md).
104108
:::::

deploy-manage/deploy/cloud-enterprise.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,10 @@ With {{ece}}, you can:
2424

2525
Refer to [](./cloud-enterprise/ece-architecture.md) for details about the ECE platform architecture and the technologies used.
2626

27+
:::{admonition} Use cloud services in your ECE environment with Cloud Connect
28+
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.
29+
::::
30+
2731
## ECE features
2832

2933
- **Automated scaling & orchestration**: Handles cluster provisioning, scaling, and upgrades automatically.

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,10 @@ products:
1616

1717
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.
1818

19+
:::{admonition} Use cloud services in your ECK environment with Cloud Connect
20+
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.
21+
::::
22+
1923
## ECK overview
2024

2125
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
3539

3640
Other sections of the documentation include the following important topics around ECK:
3741

38-
- [Logging and Monitoring](../monitor.md): Configure stack monitoring and logs forwarding with the help of ECK.
42+
- [Logging and Monitoring](../monitor.md): Configure monitoring and logs forwarding with the help of ECK.
3943
- [Remote Clusters](../remote-clusters.md): Configure remote clusters on ECK.
4044
- [](../tools.md): Add snapshot repositories to your {{es}} clusters for automatic snapshots.
4145
- [Security](../security.md): Secure communications, manage HTTP certificates, or add secure settings to your applications.

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,10 @@ Refer to [](/deploy-manage/security.md) for more details.
8080

8181
**Monitor your deployments and keep them healthy**
8282

83-
{{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.
83+
{{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.
84+
85+
:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md
86+
:::
8487

8588
## More about {{ech}} [ec-about]
8689

deploy-manage/deploy/self-managed.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,12 @@ Self-hosted options:
2929
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).
3030
:::
3131

32+
:::{admonition} Use cloud services in your self-managed cluster with Cloud Connect
33+
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.
34+
35+
This way, you can get faster access to new cloud features while still meeting your infrastructure requirements.
36+
::::
37+
3238
## Section overview
3339

3440
This section focuses on deploying {{es}} and {{kib}} without an orchestrator.

deploy-manage/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,7 @@ Learn how to design and deploy a production-ready Elastic environment.
4444
* [](/deploy-manage/reference-architectures.md): Explore blueprints for deploying clusters tailored to different use cases.
4545
* [](/deploy-manage/tools.md): Learn about the tools available to safeguard data, ensure continuous availability, and maintain resilience in your {{es}} environment.
4646
* [](/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.
47+
* [](/deploy-manage/cloud-connect.md): Learn how to use {{ecloud}} services in your self-hosted environment.
4748

4849
:::{admonition} Serverless does it for you
4950
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

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -21,15 +21,17 @@ Depending on your deployment type, you can use a variety of solutions for monito
2121

2222
## Monitoring your cluster or deployment
2323

24-
Depending on your deployment type and context, you have several options for monitoring your cluster or deployment.
24+
You have several options for monitoring your cluster or deployment.
2525

26-
If you’re using {{ech}}, you can use [AutoOps](/deploy-manage/monitor/autoops.md) to monitor your cluster.
26+
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.
2727

28-
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.
28+
Alternatively, you can use [Stack Monitoring](/deploy-manage/monitor/stack-monitoring.md) to monitor logs and metrics across the {{stack}}.
2929

30-
For other deployment types, use [Stack Monitoring](/deploy-manage/monitor/stack-monitoring.md) to monitor logs and metrics across the {{stack}}.
30+
To help you decide between these two options, refer to [](/deploy-manage/monitor/autoops-vs-stack-monitoring.md).
3131

32-
To help you make your decision, refer to [](/deploy-manage/monitor/autoops-vs-stack-monitoring.md).
32+
For ECE and {{ech}} deployments, there are also a number of out of the box monitoring tools available.
33+
34+
The following sections provide more details.
3335

3436
### AutoOps (recommended)
3537

@@ -43,7 +45,7 @@ deployment:
4345

4446
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.
4547

46-
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).
48+
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).
4749

4850
### Stack monitoring
4951

0 commit comments

Comments
 (0)