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
Copy file name to clipboardExpand all lines: deploy-manage/deploy/cloud-on-k8s/configure-eck.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ mapped_pages:
12
12
This page explains the various methods for configuring and applying ECK settings.
13
13
14
14
::::{tip}
15
-
For a detailed list and description of all available settings in ECK, refer to [ECK configuration flags](asciidocalypse://docs/cloud-on-k8s/docs/reference/eck-configuration-flags.md).
15
+
For a detailed list and description of all available settings in ECK, refer to [ECK configuration flags](cloud-on-k8s://reference/eck-configuration-flags.md).
16
16
::::
17
17
18
18
By default, the ECK installation includes a [ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/) with an `eck.yaml` key where you can add, remove, or update configuration settings. This ConfigMap is mounted into the operator’s container as a file, and provided to the application through the `--config` flag.
@@ -56,7 +56,7 @@ If you installed ECK using the manifests and the commands listed in [Deploy ECK]
56
56
57
57
You can update the ConfigMap directly using the command `kubectl edit configmap elastic-operator -n elastic-operator` or modify the installation manifests and reapply them with `kubectl apply -f <your-manifest-file.yaml>`.
58
58
59
-
The following shows the default `elastic-operator` ConfigMap, for reference purposes. Refer to [ECK configuration flags](asciidocalypse://docs/cloud-on-k8s/docs/reference/eck-configuration-flags.md) for a complete list of available settings.
59
+
The following shows the default `elastic-operator` ConfigMap, for reference purposes. Refer to [ECK configuration flags](cloud-on-k8s://reference/eck-configuration-flags.md) for a complete list of available settings.
Copy file name to clipboardExpand all lines: deploy-manage/deploy/cloud-on-k8s/elasticsearch-deployment-quickstart.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ The cluster that you deployed in this quickstart guide only allocates a persiste
44
44
::::
45
45
46
46
47
-
For a full description of each `CustomResourceDefinition` (CRD), refer to the [*API Reference*](asciidocalypse://docs/cloud-on-k8s/docs/reference/k8s-api-reference.md) or view the CRD files in the [project repository](https://github.com/elastic/cloud-on-k8s/tree/2.16/config/crds). You can also retrieve information about a CRD from the cluster. For example, describe the {{es}} CRD specification with [`describe`](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_describe/):
47
+
For a full description of each `CustomResourceDefinition` (CRD), refer to the [*API Reference*](cloud-on-k8s://reference/api-docs.md) or view the CRD files in the [project repository](https://github.com/elastic/cloud-on-k8s/tree/2.16/config/crds). You can also retrieve information about a CRD from the cluster. For example, describe the {{es}} CRD specification with [`describe`](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_describe/):
Any Elasticsearch, Kibana, or APM Server resources deployed to a namespace with the above annotation will automatically join the mesh.
45
45
46
-
Alternatively, if you only want specific resources to join the mesh, add the `linkerd.io/inject: enabled` annotation to the `podTemplate` (check [API documentation](asciidocalypse://docs/cloud-on-k8s/docs/reference/k8s-api-reference.md)) of the resource as follows:
46
+
Alternatively, if you only want specific resources to join the mesh, add the `linkerd.io/inject: enabled` annotation to the `podTemplate` (check [API documentation](cloud-on-k8s://reference/api-docs.md)) of the resource as follows:
Copy file name to clipboardExpand all lines: deploy-manage/deploy/cloud-on-k8s/kibana-instance-quickstart.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ To deploy a simple [{{kib}}](/get-started/the-stack.md#stack-components-kibana)
66
66
```
67
67
68
68
69
-
For a full description of each `CustomResourceDefinition` (CRD), refer to the [*API Reference*](asciidocalypse://docs/cloud-on-k8s/docs/reference/k8s-api-reference.md) or view the CRD files in the [project repository](https://github.com/elastic/cloud-on-k8s/tree/2.16/config/crds). You can also retrieve information about a CRD from the instance. For example, describe the {{kib}} CRD specification with [`describe`](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_describe/):
69
+
For a full description of each `CustomResourceDefinition` (CRD), refer to the [*API Reference*](cloud-on-k8s://reference/api-docs.md) or view the CRD files in the [project repository](https://github.com/elastic/cloud-on-k8s/tree/2.16/config/crds). You can also retrieve information about a CRD from the instance. For example, describe the {{kib}} CRD specification with [`describe`](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_describe/):
Copy file name to clipboardExpand all lines: deploy-manage/deploy/elastic-cloud/regions.md
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ A region is the geographic area where the data center of the cloud provider that
12
12
Elastic Cloud Serverless handles all hosting details for you. You are unable to change the region after you create a project.
13
13
14
14
::::{note}
15
-
Currently, a limited number of Amazon Web Services (AWS) and Microsoft Azureregions are available. More regions for AWS and Azure, as well as Google Cloud Platform (GCP), will be added in the future.
15
+
Currently, a limited number of Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP) regions are available. More regions for AWS, Azure, and GCP, will be added in the future.
16
16
17
17
::::
18
18
@@ -39,4 +39,16 @@ The following Azure regions are currently available:
39
39
40
40
| Region | Name |
41
41
| :--- | :--- |
42
-
| eastus | East US |
42
+
| eastus | East US |
43
+
44
+
## Google Cloud Platform (GCP) regions [regions-gcp-regions]
45
+
46
+
```yaml {applies_to}
47
+
serverless: preview
48
+
```
49
+
50
+
The following GCP regions are currently available:
% {{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.
19
20
%
@@ -22,7 +23,7 @@ mapped_urls:
22
23
% encryption at rest (EAR) is enabled in {{ech}} by default. We support EAR for both the data stored in your clusters and the snapshots we take for backup, on all cloud platforms and across all regions.
23
24
% You can also bring your own key (BYOK) to encrypt your Elastic Cloud deployment data and snapshots. For more information, check [Encrypt your deployment with a customer-managed encryption key](../../../deploy-manage/security/encrypt-deployment-with-customer-managed-encryption-key.md).
24
25
25
-
Note that the encryption happens at the file system level.
26
+
% Note that the encryption happens at the file system level.
This section covers how to secure your Elastic environment. Learn how to implement TLS encryption, network security controls, and data protection measures.
79
+
80
+
## Security overview
81
+
82
+
An Elastic implementation comprises many moving parts: {es} nodes forming the cluster, {kib} instances, additional stack components such as Logstash and Beats, and various clients and integrations communicating with your deployment.
83
+
84
+
To keep your data secured, Elastic offers comprehensive security features that:
85
+
- Prevent unauthorized access to your deployment
86
+
- Encrypt communications between components
87
+
- Protect data at rest
88
+
- Secure sensitive settings and saved objects
89
+
90
+
Security requirements and capabilities vary by deployment. Features may be managed automatically by Elastic, require configuration, or must be fully self-managed. Refer to [Security by deployment type](#security-by-deployment-type) for details.
91
+
92
+
::::{tip}
93
+
See the [Deployment overview](/deploy-manage/deploy.md) to understand your options for deploying Elastic.
94
+
::::
95
+
96
+
### Security by deployment type
97
+
98
+
Security features have one of these statuses across deployment types:
99
+
100
+
| Status | Description |
101
+
|--------|-------------|
102
+
|**Managed**| Handled automatically by Elastic with no user configuration needed |
103
+
|**Configurable**| Built-in feature that needs your configuration (like IP filters or passwords) |
104
+
|**Self-managed**| Infrastructure-level security you implement and maintain |
105
+
|**N/A**| Not available for this deployment type |
Throughout this security documentation, you'll see deployment type indicators that show which content applies to specific deployment types. Each section clearly identifies which deployment types it applies to, and deployment-specific details are separated within each topic.
140
+
141
+
To get the most relevant information for your environment, focus on sections tagged with your deployment type and look for subsections specifically addressing your deployment model.
142
+
143
+
## Security topics
144
+
145
+
This security documentation is organized into four main areas:
146
+
147
+
% TODO: Add links to the sections below
148
+
149
+
### 1. Secure your hosting environment
150
+
151
+
The security of your hosting environment forms the foundation of your overall security posture. This section covers environment-specific security controls:
152
+
153
+
-**Elastic Cloud Hosted and Serverless**: Organization-level SSO, role-based access control, and cloud API keys
154
+
-**Elastic Cloud Enterprise**: TLS certificates, role-based access control, and cloud API keys
0 commit comments