You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{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.
2
+
3
+
In {{ech}}, you can augment these security features in the following ways:
4
+
* Configure [traffic filtering](/deploy-manage/security/traffic-filtering.md) to prevent unauthorized access to your deployments.
5
+
* Encrypt your deployment with a [customer-managed encryption key](/deploy-manage/security/encrypt-deployment-with-customer-managed-encryption-key.md).
6
+
*[Secure your settings](/deploy-manage/security/secure-settings.md) using {{es}} and {{kib}} keystores.
7
+
* Use the list of [{{ecloud}} static IPs](/deploy-manage/security/elastic-cloud-static-ips.md) to allow or restrict communications in your infrastructure.
8
+
9
+
{{ech}} doesn't support custom SSL certificates, which means that a custom CNAME for an {{ech}} endpoint such as *mycluster.mycompanyname.com* also is not supported.
10
+
11
+
Refer to [{{ecloud}} security](https://www.elastic.co/cloud/security) for more details about Elastic security and privacy programs.
% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
30
-
31
-
$$$faq-aws-difference$$$
32
-
33
-
$$$faq-aws$$$
34
-
35
-
$$$faq-config$$$
36
-
37
-
$$$faq-elastic$$$
38
-
39
-
$$$faq-full-stack$$$
40
-
41
-
$$$faq-limit$$$
42
-
43
-
$$$faq-subscriptions$$$
44
-
45
-
$$$faq-trial$$$
46
-
47
-
$$$faq-vs-aws$$$
48
-
49
-
$$$faq-what$$$
50
-
51
-
$$$faq-where$$$
52
-
53
-
$$$faq-x-pack$$$
54
-
55
14
**{{ech}} is the {{stack}}, managed through {{ecloud}} deployments.**
56
15
57
16
It is also formerly known as {{es}} Service.
@@ -64,7 +23,6 @@ A **hosted deployment** helps you manage an {{es}} cluster and instances of othe
64
23
{{ech}} is one of the two deployment options available on {{ecloud}}. [Depending on your needs](../elastic-cloud.md), you can also run [{{serverless-full}} projects](/deploy-manage/deploy/elastic-cloud/serverless.md).
65
24
::::
66
25
67
-
68
26
**Hardware profiles to optimize deployments for your usage.**
69
27
70
28
You can optimize the configuration and performance of a deployment by selecting a **hardware profile** that matches your usage.
@@ -91,7 +49,7 @@ These solutions help you accomplish your use cases: Ingest data into the deploym
91
49
Of course, you can choose to follow your own path and use Elastic components available in your deployment to ingest, visualize, and analyze your data independently from solutions.
92
50
93
51
94
-
## How to operate {{ech}}?[ec_how_to_operate_elasticsearch_service]
52
+
## How to operate {{ech}} [ec_how_to_operate_elasticsearch_service]
95
53
96
54
**Where to start?**
97
55
@@ -110,7 +68,13 @@ There are a few things that can help you make sure that your production deployme
110
68
111
69
**Secure your environment**
112
70
113
-
Control which users and services can access your deployments by [securing your environment](/deploy-manage/security/secure-your-cluster-deployment.md). [Add authentication mechanisms](/deploy-manage/users-roles.md), configure [traffic filtering](/deploy-manage/security/traffic-filtering.md) for private link, encrypt your deployment data and snapshots at rest [with your own key](/deploy-manage/security/encrypt-deployment-with-customer-managed-encryption-key.md), [manage trust](/deploy-manage/remote-clusters.md) with {{es}} clusters from other environments, and more.
Copy file name to clipboardExpand all lines: deploy-manage/security.md
+2-11Lines changed: 2 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,22 +32,13 @@ deployment:
32
32
serverless: all
33
33
```
34
34
35
-
{{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.
36
-
37
-
In {{ech}}, you can augment these Security features in the following ways:
38
-
* Configure [traffic filtering](/deploy-manage/security/traffic-filtering.md) to prevent unauthorized access to your deployments.
39
-
* Encrypt your deployment with a [customer-managed encryption key](/deploy-manage/security/encrypt-deployment-with-customer-managed-encryption-key.md).
40
-
* [Secure your settings](/deploy-manage/security/secure-settings.md) using {{es}} and {{kib}} keystores.
41
-
* Use the list of [{{ecloud}} static IPs](/deploy-manage/security/elastic-cloud-static-ips.md) to allow or restrict communications in your infrastructure.
42
-
43
-
{{ech}} doesn't support custom SSL certificates, which means that a custom CNAME for an {{ech}} endpoint such as *mycluster.mycompanyname.com* also is not supported.
0 commit comments