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/api-keys/elasticsearch-api-keys.md
+10-5Lines changed: 10 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Several types of {{es}} API keys exist:
15
15
***Cross-cluster** API key: allows other clusters to connect to this cluster.
16
16
***Managed** API key: created and managed by {{kib}} to run background tasks.
17
17
18
-
To manage API keys in {{kib}}, go to **Management > Stack Management > API Keys**from the navigation menu or use the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md).
18
+
To manage API keys in {{kib}}, go to the **API keys**management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
@@ -42,10 +42,13 @@ Two methods are available to create an API key:
42
42
43
43
Your personal API key is created with a default expiration of 90 days from the time of creation. You can manage the key from the **API Keys** page.
44
44
45
-
* To create a personal or cross-cluster API key with configurable options, go to **Management > Stack Management > API Keys** from the navigation menu or use the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md), and select **Create API key**.
45
+
* To create a personal or cross-cluster API key with configurable options:
46
+
1. Go to the **API keys** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
47
+
2. Select **Create API key**.
46
48
47
-
![Create API Key UI](/deploy-manage/images/kibana-create-user-api-key.png"")
49
+
![Create API Key UI](/deploy-manage/images/kibana-create-user-api-key.png"")
48
50
51
+
From the **Create API key** pane, you can configure your new key:
49
52
1. Choose to create either a user or a cross-cluster API key.
50
53
2. Optionally, set an expiry date. By default the API key will not expire, but it's a good security practice to give the key a limited lifespan.
51
54
3. Configure access:
@@ -55,7 +58,9 @@ Two methods are available to create an API key:
55
58
56
59
## Update an API key [update-api-key]
57
60
58
-
To update an API key, go to **Management > Stack Management > API Keys** from the navigation menu or use the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md), and then click on the name of the key. You cannot update the name or the type of an API key.
61
+
To update an API key, go to the **API keys** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From the **API keys** page, click on the name of the key you want to update.
62
+
63
+
You can't update the name or the type of an API key.
59
64
60
65
* For a user API key, you can update:
61
66
* The API key's access to {{es}} APIs and resources.
@@ -71,7 +76,7 @@ To update an API key, go to **Management > Stack Management > API Keys** from th
71
76
72
77
## View and delete API keys [view-api-keys]
73
78
74
-
The **API Keys**feature in {{kib}} lists your API keys, including the name, date created, and status. If an API key expires, its status changes from `Active` to `Expired`.
79
+
The **API Keys**management page in {{kib}} lists your API keys, including the name, date created, and status. If an API key expires, its status changes from `Active` to `Expired`.
75
80
76
81
If you have `manage_security` or `manage_api_key` permissions, you can view the API keys of all users, and see which API key was created by which user in which realm. If you have only the `manage_own_api_key` permission, you see only a list of your own keys.
Copy file name to clipboardExpand all lines: deploy-manage/cloud-organization/tools-and-apis.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,8 @@ You can use the [{{ecloud}} API](https://www.elastic.co/docs/api/doc/cloud/) to
13
13
* Refer to [](/deploy-manage/api-keys/elastic-cloud-api-keys.md) to learn how to generate an API key to access this API.
14
14
* Refer to [{{ecloud}} RESTful API](cloud://reference/cloud-hosted/ec-api-restful.md) for usage information and examples.
15
15
16
+
For additional billing and cost information for {{ecloud}}, you can use the [Cloud Billing API](https://www.elastic.co/docs/api/doc/cloud-billing/).
17
+
16
18
For {{ecloud}} [service status](/deploy-manage/cloud-organization/service-status.md) updates, you can use the [Service Status API](https://status.elastic.co/api/).
17
19
18
20
For information about all of the tools and APIs that you can use to manage your {{ech}} deployments and {{serverless-full}} projects, refer to [](/deploy-manage/deploy/elastic-cloud/tools-apis.md).
$$$ece-all-stacks$$$Additional {{stack}} versions are available as Docker images that you can use with ECE. For offline installations, you need to download both the {{stack}} pack and the Docker images for the same version.
@@ -36,27 +36,27 @@ To perform an offline installation without a private Docker registry, you have t
36
36
37
37
```sh subs=true
38
38
docker save -o ece.{{version.ece}}.tar docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:{{version.ece}}
39
-
docker save -o es.8.18.2.tar docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.8
40
-
docker save -o kibana.8.18.2.tar docker.elastic.co/cloud-release/kibana-cloud:8.18.8
41
-
docker save -o apm.8.18.2.tar docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.8
42
-
docker save -o enterprise-search.8.18.2.tar docker.elastic.co/cloud-release/enterprise-search-cloud:8.18.8
43
-
docker save -o es.9.0.1.tar docker.elastic.co/cloud-release/elasticsearch-cloud-ess:9.0.8
44
-
docker save -o kibana.9.0.1.tar docker.elastic.co/cloud-release/kibana-cloud:9.0.8
45
-
docker save -o apm.9.0.1.tar docker.elastic.co/cloud-release/elastic-agent-cloud:9.0.8
39
+
docker save -o es.8.18.2.tar docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-8}}
40
+
docker save -o kibana.8.18.2.tar docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-8}}
41
+
docker save -o apm.8.18.2.tar docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-8}}
42
+
docker save -o enterprise-search.8.18.2.tar docker.elastic.co/cloud-release/enterprise-search-cloud:{{ece-docker-images-8}}
43
+
docker save -o es.9.0.1.tar docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-9}}
44
+
docker save -o kibana.9.0.1.tar docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-9}}
45
+
docker save -o apm.9.0.1.tar docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-9}}
46
46
```
47
47
48
48
3. Copy the .tar files to a location on your network where they are available to each host where you plan to install {{ece}}. Alternatively, you can copy the .tar files to each host directly.
49
49
4. On each host, load the images into Docker, replacing `FILE_PATH` with the correct path to the .tar files:
@@ -42,26 +42,26 @@ Installing ECE on multiple hosts with your own registry server is simpler, becau
42
42
43
43
```sh subs=true
44
44
docker tag docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:{{version.ece}} REGISTRY/cloud-enterprise/elastic-cloud-enterprise:{{version.ece}}
45
-
docker tag docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.2 REGISTRY/cloud-release/elasticsearch-cloud-ess:8.18.8
46
-
docker tag docker.elastic.co/cloud-release/kibana-cloud:8.18.2 REGISTRY/cloud-release/kibana-cloud:8.18.8
47
-
docker tag docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.2 REGISTRY/cloud-release/elastic-agent-cloud:8.18.8
48
-
docker tag docker.elastic.co/cloud-release/enterprise-search-cloud:8.18.2 REGISTRY/cloud-release/enterprise-search-cloud:8.18.8
49
-
docker tag docker.elastic.co/cloud-release/elasticsearch-cloud-ess:9.0.1 REGISTRY/cloud-release/elasticsearch-cloud-ess:9.0.8
50
-
docker tag docker.elastic.co/cloud-release/kibana-cloud:9.0.1 REGISTRY/cloud-release/kibana-cloud:9.0.8
51
-
docker tag docker.elastic.co/cloud-release/elastic-agent-cloud:9.0.1 REGISTRY/cloud-release/elastic-agent-cloud:9.0.8
45
+
docker tag docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.2 REGISTRY/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-8}}
46
+
docker tag docker.elastic.co/cloud-release/kibana-cloud:8.18.2 REGISTRY/cloud-release/kibana-cloud:{{ece-docker-images-8}}
47
+
docker tag docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.2 REGISTRY/cloud-release/elastic-agent-cloud:{{ece-docker-images-8}}
48
+
docker tag docker.elastic.co/cloud-release/enterprise-search-cloud:8.18.2 REGISTRY/cloud-release/enterprise-search-cloud:{{ece-docker-images-8}}
49
+
docker tag docker.elastic.co/cloud-release/elasticsearch-cloud-ess:9.0.1 REGISTRY/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-9}}
50
+
docker tag docker.elastic.co/cloud-release/kibana-cloud:9.0.1 REGISTRY/cloud-release/kibana-cloud:{{ece-docker-images-9}}
51
+
docker tag docker.elastic.co/cloud-release/elastic-agent-cloud:9.0.1 REGISTRY/cloud-release/elastic-agent-cloud:{{ece-docker-images-9}}
52
52
```
53
53
54
54
4. Push the Docker images to your private Docker registry, using the same tags from the previous step. Replace `REGISTRY` with your actual registry URL, for example `my.private.repo:5000`:
Copy file name to clipboardExpand all lines: deploy-manage/deploy/elastic-cloud/serverless.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,6 +65,8 @@ To learn more about serverless status, see [Service status](../../cloud-organiza
65
65
66
66
The following FAQ addresses common questions about using {{serverless-full}} projects.
67
67
68
+
For information about upcoming features, refer to our [roadmap](https://www.elastic.co/cloud/serverless/roadmap).
69
+
68
70
### Pricing and availability
69
71
**Q: Where can I learn about pricing for {{serverless-short}}?**
70
72
A: See pricing information for [{{es-serverless}}](https://www.elastic.co/pricing/serverless-search), [{{observability}}](https://www.elastic.co/pricing/serverless-observability), and [{{sec-serverless}}](https://www.elastic.co/pricing/serverless-security).
@@ -73,6 +75,7 @@ A: See pricing information for [{{es-serverless}}](https://www.elastic.co/pricin
73
75
A: {{serverless-full}} is available in select AWS, GCP, and Azure regions, with plans to expand to more regions. For more information, refer to [](/deploy-manage/deploy/elastic-cloud/regions.md).
74
76
75
77
### Data management
78
+
76
79
**Q: How can I move data to or from {{serverless-short}} projects?**
77
80
A: We are working on data migration tools. In the interim, [use Logstash](logstash://reference/index.md) with {{es}} input and output plugins to move data to and from {{serverless-short}} projects.
78
81
@@ -83,6 +86,9 @@ A: Request for project backups or restores is currently unsupported, and we are
83
86
**Q: How can I create {{serverless-full}} service accounts?**
84
87
A: Create API keys for service accounts in your {{serverless-short}} projects. Options to automate the creation of API keys with tools such as Terraform will be available in the future.
85
88
89
+
**Q: What compliance and privacy standards does {{serverless-full}} adhere to?**
90
+
A: Alongside the entire Elastic platform, {{serverless-full}} is independently audited and certified to meet industry-leading compliance and privacy standards. Refer to the [Elastic Trust Center](https://www.elastic.co/trust) for more information. Further details about specific standards are available on our [roadmap](https://www.elastic.co/cloud/serverless/roadmap).
91
+
86
92
### Project lifecycle and support
87
93
**Q: How does {{serverless-full}} ensure compatibility between software versions?**
88
94
A: Connections and configurations are unaffected by upgrades. To ensure compatibility between software versions, quality testing and API versioning are used.
Copy file name to clipboardExpand all lines: deploy-manage/deploy/elastic-cloud/tools-apis.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,7 @@ The following REST APIs allow you to manage your {{ecloud}} organization, users,
33
33
| {{ecloud}} organization<br><br>{{ech}} deployments |[{{ecloud}} API](https://www.elastic.co/docs/api/doc/cloud/)| Manage your Cloud organization, members, costs, billing, and more.<br><br>Manage your hosted deployments and all of the resources associated with them, including scaling or autoscaling resources, and managing network security, deployment extensions, remote clusters, and {{stack}} versions.<br><br>Refer to [{{ecloud}} RESTful API](cloud://reference/cloud-hosted/ec-api-restful.md) for usage information and examples. |
| {{ecloud}} billing information |[Cloud Billing API](https://www.elastic.co/docs/api/doc/cloud-billing/)| Retrieve additional billing and cost information about your {{ecloud}} organization. |
36
37
37
38
38
39
### APIs to interact with data and solution features
Copy file name to clipboardExpand all lines: deploy-manage/kibana-reporting-configuration.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,7 +121,9 @@ When security is enabled, you grant users access to {{report-features}} with [{{
121
121
4. Click **Update user**.
122
122
123
123
124
-
Granting the privilege to generate reports also grants the user the privilege to view their reports in **Stack Management > Reporting**. Users can only access their own reports.
124
+
Granting the privilege to generate reports also grants the user the privilege to view their reports in **Reporting**. Users can only access their own reports.
125
+
126
+
To view reports, go to the **Reporting** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
0 commit comments