diff --git a/deploy-manage/deploy/cloud-enterprise/add-custom-bundles-plugins.md b/deploy-manage/deploy/cloud-enterprise/add-custom-bundles-plugins.md index 1e49d39a62..29bf97da2f 100644 --- a/deploy-manage/deploy/cloud-enterprise/add-custom-bundles-plugins.md +++ b/deploy-manage/deploy/cloud-enterprise/add-custom-bundles-plugins.md @@ -71,7 +71,7 @@ Custom plugins can include the official {{es}} plugins not provided with {{ece}} "elasticsearch_version" : "" <2> }, { - "url": "http://www.MYURL.com/my-custom-plugin.zip", + "url": "/my-custom-plugin.zip", "name": "my-custom-plugin", "elasticsearch_version": "7.17.1" } @@ -105,7 +105,7 @@ This example adds a custom LDAP bundle for deployment level role-based access co "user_bundles": [ { "name": "ldap-cert", - "url": "http://www.MYURL.com/ldapcert.zip", <1> + "url": "/ldapcert.zip", <1> "elasticsearch_version": "*" } ] @@ -151,7 +151,7 @@ In this example, we assume the Identity Provider does not publish its SAML metad "user_bundles": [ { "name": "saml-metadata", - "url": "http://www.MYURL.com/saml-metadata.zip", <1> + "url": "/saml-metadata.zip", <1> "elasticsearch_version": "*" } ] @@ -254,7 +254,7 @@ To import a JVM trust store: "user_bundles": [ { "name": "custom-ca-certs", - "url": "http://www.MYURL.com/cacerts.zip", <1> + "url": "/cacerts.zip", <1> "elasticsearch_version": "*" <2> } ] @@ -309,7 +309,7 @@ To import a JVM trust store: "user_bundles": [ { "name": "custom-geoip-db", - "url": "http://www.MYURL.com/my-geoip-file.zip", + "url": "/my-geoip-file.zip", "elasticsearch_version": "*" } ] @@ -359,7 +359,7 @@ To import a JVM trust store: "user_bundles": [ { "name": "custom-synonyms", - "url": "http://www.MYURL.com/synonyms.zip", + "url": "/synonyms.zip", "elasticsearch_version": "*" } ] diff --git a/deploy-manage/deploy/cloud-enterprise/ce-add-support-for-node-roles-autoscaling.md b/deploy-manage/deploy/cloud-enterprise/ce-add-support-for-node-roles-autoscaling.md index 2566230b98..2d368052e5 100644 --- a/deploy-manage/deploy/cloud-enterprise/ce-add-support-for-node-roles-autoscaling.md +++ b/deploy-manage/deploy/cloud-enterprise/ce-add-support-for-node-roles-autoscaling.md @@ -1418,7 +1418,7 @@ Having added support for `node_roles` and autoscaling to your custom template, i 1. Obtain the existing deployment templates by sending the following `GET` request, and take note of the `id` of the template you wish to update. ```sh - curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/deployments/templates?region=ece-region + curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/templates?region=ece-region ``` 2. Send a `PUT` request with the updated template on the payload, in order to effectively replace the outdated template with the new one. Note that the following request is just an example, you have to replace `{{template_id}}` with the `id` you collected on step 1. and set the payload to the updated template JSON. Check [set deployment template API](https://www.elastic.co/docs/api/doc/cloud-enterprise/operation/operation-set-deployment-template-v2) for more details. diff --git a/deploy-manage/deploy/cloud-enterprise/change-endpoint-urls.md b/deploy-manage/deploy/cloud-enterprise/change-endpoint-urls.md index 836de86e24..c6009339aa 100644 --- a/deploy-manage/deploy/cloud-enterprise/change-endpoint-urls.md +++ b/deploy-manage/deploy/cloud-enterprise/change-endpoint-urls.md @@ -15,8 +15,8 @@ products: By default, the deployments `CNAME` is set to `LOCAL_HOST_IP.ip.es.io`, where `LOCAL_HOST_IP` is the IP address of the first installed ECE host. This results in the following default endpoint URLs: ```sh -http://CLUSTER_ID.LOCAL_HOST_IP.ip.es.io:9200 -https://CLUSTER_ID.LOCAL_HOST_IP.ip.es.io:9243 +http://.ip.es.io:9200 +https://.ip.es.io:9243 ``` ::::{important} diff --git a/deploy-manage/deploy/cloud-enterprise/configure-allocator-affinity.md b/deploy-manage/deploy/cloud-enterprise/configure-allocator-affinity.md index 8ba9067b8a..fbacbc2bd6 100644 --- a/deploy-manage/deploy/cloud-enterprise/configure-allocator-affinity.md +++ b/deploy-manage/deploy/cloud-enterprise/configure-allocator-affinity.md @@ -42,7 +42,7 @@ $$$fill-anti-affinity$$$`fill-anti-affinity` (default) To check how allocator affinity is currently configured: ```sh -curl -X GET -u admin:PASSWORD -k https://COORDINATOR_HOST:12443/api/v1/platform/configuration/store/constructor +curl -X GET -u admin:PASSWORD -k https://$COORDINATOR_HOST:12443/api/v1/platform/configuration/store/constructor { "errors": [{ "code": "platform.config.store.not_found", @@ -56,7 +56,7 @@ If a configuration option cannot be found, the default `fill-anti-affinity` stra To set allocator affinity to the `distribute-anti-affinity` strategy: ```sh -curl -X POST -u admin:PASSWORD -k https://COORDINATOR_HOST:12443/api/v1/platform/configuration/store/constructor -H 'Content-Type: application/json' -d '{ "value": "{ \"allocator_prioritization\": \"distribute-anti-affinity\" }" }' +curl -X POST -u admin:PASSWORD -k https://$COORDINATOR_HOST:12443/api/v1/platform/configuration/store/constructor -H 'Content-Type: application/json' -d '{ "value": "{ \"allocator_prioritization\": \"distribute-anti-affinity\" }" }' { "changed": false, "name": "constructor", @@ -67,7 +67,7 @@ curl -X POST -u admin:PASSWORD -k https://COORDINATOR_HOST:12443/api/v1/platform To update allocator affinity to the `distribute` strategy: ```sh -curl -X PUT -u admin:PASSWORD -k https://COORDINATOR_HOST:12443/api/v1/platform/configuration/store/constructor -H 'Content-Type: application/json' -d '{ "value": "{ \"allocator_prioritization\": \"distribute\" }" }' +curl -X PUT -u admin:PASSWORD -k https://$COORDINATOR_HOST:12443/api/v1/platform/configuration/store/constructor -H 'Content-Type: application/json' -d '{ "value": "{ \"allocator_prioritization\": \"distribute\" }" }' { "changed": true, "name": "constructor", @@ -78,7 +78,7 @@ curl -X PUT -u admin:PASSWORD -k https://COORDINATOR_HOST:12443/api/v1/platform/ To change allocator affinity back to the default behavior: ```sh -curl -X DELETE -u admin:PASSWORD -k https://COORDINATOR_HOST:12443/api/v1/platform/configuration/store/constructor +curl -X DELETE -u admin:PASSWORD -k https://$COORDINATOR_HOST:12443/api/v1/platform/configuration/store/constructor { } diff --git a/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md b/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md index ac762920f1..fc9d83daf3 100644 --- a/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md +++ b/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md @@ -144,7 +144,7 @@ Make sure to use a supported combination of Linux distribution and container eng ```text [engine] - env = ["HTTP_PROXY=http://{proxy-ip}:{proxy-port}", "HTTPS_PROXY=http://{proxy-ip}:{proxy-port}"] + env = ["HTTP_PROXY=http://:", "HTTPS_PROXY=http://:"] ``` 7. Reload systemd configuration diff --git a/deploy-manage/deploy/cloud-enterprise/connect-elasticsearch.md b/deploy-manage/deploy/cloud-enterprise/connect-elasticsearch.md index b135f388e6..20e072bf5b 100644 --- a/deploy-manage/deploy/cloud-enterprise/connect-elasticsearch.md +++ b/deploy-manage/deploy/cloud-enterprise/connect-elasticsearch.md @@ -32,7 +32,7 @@ Once you have the endpoint, use it in your client application. To test connectiv * Modify the following `curl` example to fit your environment by replacing the URL and proxy CA certificate with your own values. ```sh - curl --cacert /path/to/elastic-ece-ca-cert.pem -u elastic https://f76e96da2a7f4d3f8f3ee25d686b879c.HOST-IP-ADDRESS.ip.es.io:9243 + curl --cacert /path/to/elastic-ece-ca-cert.pem -u elastic https://.ip.es.io:9243 { "name" : "instance-0000000000", "cluster_name" : "f76e96da2a7f4d3f8f3ee25d686b879c", diff --git a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-configure-system-templates.md b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-configure-system-templates.md index 56416aa1ae..791028af26 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-configure-system-templates.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-configure-system-templates.md @@ -28,7 +28,7 @@ The API user must have the `Platform admin` role in order to configure system te 1. Obtain the existing system deployment template you wish to modify. Note the `id` of the system deployment template as you will include this value in the API call to edit the template. ```sh - curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/deployments/templates?region=ece-region + curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/templates?region=ece-region ``` 2. Edit the JSON of the system deployment template you wish to modify. diff --git a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md index f605af60c9..869bbae0e4 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md @@ -89,7 +89,7 @@ Before you start creating your own deployment templates, you should have: [tagge 1. Obtain the existing deployment templates to get some examples of what the required JSON looks like. You can take the JSON for one of the existing templates and modify it to create a new template, similar to what gets shown in the next step. ```sh - curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/deployments/templates?region=ece-region + curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/templates?region=ece-region ``` 2. Post the JSON for your new deployment template. diff --git a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-instance-configurations-create.md b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-instance-configurations-create.md index 1b8e26f00f..0d4eb7b4fb 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-instance-configurations-create.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-instance-configurations-create.md @@ -60,7 +60,7 @@ Before you start creating your own instance configurations, you should have [tag 1. Obtain the existing instance configurations to get some examples of what the required JSON looks like. You can take the JSON for one of the existing configurations and modify it to create a new instance configuration, similar to what gets shown in the next step. ```sh - curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/platform/configuration/instances + curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/platform/configuration/instances ``` 2. Post the JSON for your new instance configuration. @@ -68,7 +68,7 @@ Before you start creating your own instance configurations, you should have [tag The following examples creates an instance configuration for machine learning with size increments that start at the recommended minimum of 16 GB of memory. To make sure that machine learning nodes get deployed only on the right allocators, this instance configuration also filters for [allocator tags from our earlier example](ece-configuring-ece-tag-allocators.md) to match only allocators with high CPU resources and SSD storage. ```sh - curl -k -X POST -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/platform/configuration/instances -H 'content-type: application/json' -d '{ + curl -k -X POST -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/platform/configuration/instances -H 'content-type: application/json' -d '{ "name": "Machine Learning Only", "description": "Custom machine learning instance configuration", "storage_multiplier": 32.0, diff --git a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-tag-allocators.md b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-tag-allocators.md index f39088521b..5b04ced6e8 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-tag-allocators.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-tag-allocators.md @@ -77,7 +77,7 @@ If you have an allocator that meets several criteria, such as an allocator with 1. Get a list of the allocators in your ECE installation: ```sh - curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/platform/infrastructure/allocators + curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/platform/infrastructure/allocators ``` ::::{note} @@ -87,7 +87,7 @@ If you have an allocator that meets several criteria, such as an allocator with 2. $$$check-allocator-tags$$$Check what tags have already been assigned to your allocators. In a new or newly upgraded ECE installation, this command returns `[]`, which means that you have not assigned any tags, yet. ```sh - curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/platform/infrastructure/allocators/ALLOCATOR_ID/metadata + curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/platform/infrastructure/allocators/ALLOCATOR_ID/metadata ``` `ALLOCATOR_ID` @@ -102,7 +102,7 @@ If you have an allocator that meets several criteria, such as an allocator with * Example: To assign a single `highCPU: true` tag to an allocator: ```sh - curl -k -X PUT -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/platform/infrastructure/allocators/ALLOCATOR_ID/metadata/highCPU -H 'content-type: application/json' -d '{ "value": "true" }' + curl -k -X PUT -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/platform/infrastructure/allocators/ALLOCATOR_ID/metadata/highCPU -H 'content-type: application/json' -d '{ "value": "true" }' [{ "key": "highCPU", "value": "true" @@ -114,7 +114,7 @@ If you have an allocator that meets several criteria, such as an allocator with * Example: To assign multiple tags to an allocator with a single command: ```sh - curl -k -X PUT -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/platform/infrastructure/allocators/ALLOCATOR_ID/metadata -H 'content-type: application/json' -d ' + curl -k -X PUT -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/platform/infrastructure/allocators/ALLOCATOR_ID/metadata -H 'content-type: application/json' -d ' { "items": [ { diff --git a/deploy-manage/deploy/cloud-enterprise/ece-load-balancers.md b/deploy-manage/deploy/cloud-enterprise/ece-load-balancers.md index f55a02fe00..333f3c3b0a 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-load-balancers.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-load-balancers.md @@ -54,13 +54,13 @@ This returns a healthy response as: For {{ece}} 2.1 and later, the health check endpoint has changed. You can use `/_health` on proxy hosts with a result of either a 200 OK to indicate healthy or a 502 Bad Gateway response for unhealthy. A healthy response also means that internal routing tables in the proxy are valid and initialized, but not necessarily up-to-date. ``` -http://PROXY_ADDRESS:9200/_health +http://:9200/_health ``` or ``` -https://PROXY_ADDRESS:9243/_health +https://:9243/_health ``` This returns a healthy response as: diff --git a/deploy-manage/deploy/cloud-enterprise/generate-roles-tokens.md b/deploy-manage/deploy/cloud-enterprise/generate-roles-tokens.md index 190d79d0d5..23805bb7ef 100644 --- a/deploy-manage/deploy/cloud-enterprise/generate-roles-tokens.md +++ b/deploy-manage/deploy/cloud-enterprise/generate-roles-tokens.md @@ -51,7 +51,7 @@ The permitted roles are the same as those you can [assign in the Cloud UI](./ass To generate an ephemeral token for additional allocators: ```sh -curl -H 'Content-Type: application/json' -u USER:PASSWORD https://COORDINATOR_HOST_IP:12443/api/v1/platform/configuration/security/enrollment-tokens -d '{ "persistent": false, "roles": [ "allocator"] }' +curl -H 'Content-Type: application/json' -u USER:PASSWORD https://$COORDINATOR_HOST:12443/api/v1/platform/configuration/security/enrollment-tokens -d '{ "persistent": false, "roles": [ "allocator"] }' { "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiI0Njk3N2I3ZC1hM2U2LTQ2MDUtYjcwZC0xNzIzMTI5YWY4ZTQiLCJyb2xlcyI6WyJwcm94eSIsImFsbG9jYXRvciJdLCJpc3MiOiJib290c3RyYXAtaW5pdGlhbCIsImV4cCI6MTQ5MzY0NjIxM30.xsaRb72CsNMuXKy6Y-PJgqLc0qmjCljlB4Smcx_MRxg" } @@ -60,7 +60,7 @@ curl -H 'Content-Type: application/json' -u USER:PASSWORD https://COORDINATOR_HO To generate a persistent token for additional allocators: ```sh -curl -H 'Content-Type: application/json' -u USER:PASSWORD https://COORDINATOR_HOST_IP:12443/api/v1/platform/configuration/security/enrollment-tokens -d '{ "persistent": true, "roles": [ "allocator"] }' +curl -H 'Content-Type: application/json' -u USER:PASSWORD https://$COORDINATOR_HOST:12443/api/v1/platform/configuration/security/enrollment-tokens -d '{ "persistent": true, "roles": [ "allocator"] }' { "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiI0Yzg5OTBkZi0xZmI3LTQ4MjAtYjg2OC02YmM5ZTg4NjA4MTQiLCJyb2xlcyI6WyJwcm94eSIsImFsbG9jYXRvciJdLCJpc3MiOiJib290c3RyYXAtaW5pdGlhbCJ9.mfTkO4j8uZJ-qwB2jmBuMScyYfLmcJpvKgSTLx2WV24", "token_id": "4c8990df-1fb7-4820-b868-6bc9e8860814" diff --git a/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md b/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md index 72147a0467..68fad46f8e 100644 --- a/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md +++ b/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md @@ -15,8 +15,8 @@ To access the Cloud UI in a web browser: 1. Connect to one of the URLs provided at the end of the installation process on your first host, replacing `FIRST_HOST` with the correct IP address or DNS hostname. ```sh - http://FIRST_HOST:12400 - https://FIRST_HOST:12443 + http://:12400 + https://:12443 ``` Secure access through the HTTPS protocol is available with certificates generated during the installation of {{ece}}, but will prompt you with a warning in your browser. To avoid this warning, you can add [your own TLS/SSL security certificates](../../security/secure-your-elastic-cloud-enterprise-installation/manage-security-certificates.md). If you are on AWS and can’t access the Cloud UI, [check if the URL points to a private IP address](../../../troubleshoot/deployments/cloud-enterprise/common-issues.md#ece-aws-private-ip). diff --git a/deploy-manage/deploy/cloud-enterprise/manage-elastic-stack-versions.md b/deploy-manage/deploy/cloud-enterprise/manage-elastic-stack-versions.md index 94c12dd800..08f93eabfe 100644 --- a/deploy-manage/deploy/cloud-enterprise/manage-elastic-stack-versions.md +++ b/deploy-manage/deploy/cloud-enterprise/manage-elastic-stack-versions.md @@ -294,13 +294,13 @@ To obtain information about available {{stack}} versions through the Cloud UI: To obtain information about available {{stack}} versions through the command line: ```sh -curl -X GET -u USER:PASSWORD https://COORDINATOR_HOST:12443/api/v1/stack/versions +curl -X GET -u USER:PASSWORD https://$COORDINATOR_HOST:12443/api/v1/stack/versions ``` For example (output abridged for brevity): ``` -curl -X GET -u admin:4Z52y8Gq7PrxMDy47ipJPSh4ozBMynOGa9HWxcy2D3j https://10.56.12.153:12443/api/v1/stack/versions +curl -X GET -u admin: https://:12443/api/v1/stack/versions { "stacks": [ { @@ -362,7 +362,7 @@ curl -X GET -u admin:4Z52y8Gq7PrxMDy47ipJPSh4ozBMynOGa9HWxcy2D3j https://10.56.1 ] } ``` -You can also query for a specific version with a URI such as `https://COORDINATOR_HOST:12443/api/v1/stack/versions/5.3.2`, for example. +You can also query for a specific version with a URI such as `https://$COORDINATOR_HOST:12443/api/v1/stack/versions/5.3.2`, for example. ## Add {{stack}} packs [ece-manage-elastic-stack-add] @@ -409,7 +409,7 @@ To add a new {{stack}} pack through the RESTful API from the command line: 2. Add the {{stack}} pack with the following API call: ```sh - curl -X POST -u USER:PASSWORD https://COORDINATOR_HOST:12443/api/v1/stack/versions \ + curl -X POST -u USER:PASSWORD https://$COORDINATOR_HOST:12443/api/v1/stack/versions \ -H 'content-type: application/zip' \ --data-binary "@PATH/STACK_PACK_FILE" <1> ``` @@ -420,7 +420,7 @@ To add a new {{stack}} pack through the RESTful API from the command line: For example: ```sh - curl -X POST -u admin:pGX5DwKzVAAIeCIpTwwAkCuJDu0ASdFP33UmYpfogfF https://10.56.12.153:12443/api/v1/stack/versions \ + curl -X POST -u admin:pGX5DwKzVAAIeCIpTwwAkCuJDu0ASdFP33UmYpfogfF :12443/api/v1/stack/versions \ -H 'content-type: application/zip' \ --data-binary "@/Users/iuriitceretian/Documents/stacks/5.4.0.zip" ``` @@ -451,7 +451,7 @@ To update {{stack}} packs through the RESTful API from the command line: 2. Update the {{stack}} pack with the following API call: ```sh - curl -X PUT -u USER:PASSWORD https://COORDINATOR_HOST:12443/api/v1/stack/versions/VERSION \ <1> + curl -X PUT -u USER:PASSWORD https://$COORDINATOR_HOST:12443/api/v1/stack/versions/VERSION \ <1> -H 'content-type: application/zip' \ --data-binary "@PATH/STACK_PACK_FILE" <2> ``` @@ -463,7 +463,7 @@ To update {{stack}} packs through the RESTful API from the command line: For example: ```sh - curl -X PUT -u admin:pGX5DwKzVAAIeCIpTwAAkCuJDu0ASdFP33UmYpfogfF https://10.58.12.153:12443/api/v1/stack/versions/6.4.0 \ + curl -X PUT -u admin:pGX5DwKzVAAIeCIpTwAAkCuJDu0ASdFP33UmYpfogfF https://$COORDINATOR_HOST:12443/api/v1/stack/versions/6.4.0 \ -H 'content-type: application/zip' \ --data-binary "@/Users/johnsmith/Documents/stacks/6.4.0.zip" ``` diff --git a/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md b/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md index d4d8dff78c..a69b4b4132 100644 --- a/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md +++ b/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md @@ -174,7 +174,7 @@ Using Docker or Podman as container runtime is a configuration local to the host ```text [engine] - env = ["HTTP_PROXY=http://{proxy-ip}:{proxy-port}", "HTTPS_PROXY=http://{proxy-ip}:{proxy-port}"] + env = ["HTTP_PROXY=http://:", "HTTPS_PROXY=http://:"] ``` 7. Reload systemd configuration diff --git a/deploy-manage/deploy/cloud-on-k8s/configuration-fleet.md b/deploy-manage/deploy/cloud-on-k8s/configuration-fleet.md index 8f1a3ca9cc..cb4ecbacae 100644 --- a/deploy-manage/deploy/cloud-on-k8s/configuration-fleet.md +++ b/deploy-manage/deploy/cloud-on-k8s/configuration-fleet.md @@ -53,8 +53,8 @@ metadata: name: kibana-sample spec: config: - xpack.fleet.agents.elasticsearch.hosts: ["https://elasticsearch-sample-es-http.default.svc:9200"] - xpack.fleet.agents.fleet_server.hosts: ["https://fleet-server-sample-agent-http.default.svc:8220"] + xpack.fleet.agents.elasticsearch.hosts: ["-es-http.default.svc:9200"] + xpack.fleet.agents.fleet_server.hosts: ["-sample-agent-http.default.svc:8220"] xpack.fleet.packages: - name: system version: latest @@ -92,8 +92,8 @@ spec: name: system ``` -* `xpack.fleet.agents.elasticsearch.hosts` must point to the {{es}} cluster where {{agents}} should send data. For ECK-managed {{es}} clusters ECK creates a Service accessible through `https://ES_RESOURCE_NAME-es-http.ES_RESOURCE_NAMESPACE.svc:9200` URL, where `ES_RESOURCE_NAME` is the name of {{es}} resource and `ES_RESOURCE_NAMESPACE` is the namespace it was deployed within. See [Storing local state in host path volume](configuration-examples-standalone.md#k8s_storing_local_state_in_host_path_volume) for details on adjusting this field when running agent as non-root as it becomes required. -* `xpack.fleet.agents.fleet_server.hosts` must point to {{fleet-server}} that {{agents}} should connect to. For ECK-managed {{fleet-server}} instances, ECK creates a Service accessible through `https://FS_RESOURCE_NAME-agent-http.FS_RESOURCE_NAMESPACE.svc:8220` URL, where `FS_RESOURCE_NAME` is the name of {{agent}} resource with {{fleet-server}} enabled and `FS_RESOURCE_NAMESPACE` is the namespace it was deployed in. +* `xpack.fleet.agents.elasticsearch.hosts` must point to the {{es}} cluster where {{agents}} should send data. For ECK-managed {{es}} clusters ECK creates a Service accessible through `-es-http..svc:9200` URL, where `ES_RESOURCE_NAME` is the name of {{es}} resource and `ES_RESOURCE_NAMESPACE` is the namespace it was deployed within. See [Storing local state in host path volume](configuration-examples-standalone.md#k8s_storing_local_state_in_host_path_volume) for details on adjusting this field when running agent as non-root as it becomes required. +* `xpack.fleet.agents.fleet_server.hosts` must point to {{fleet-server}} that {{agents}} should connect to. For ECK-managed {{fleet-server}} instances, ECK creates a Service accessible through `-agent-http.FS_RESOURCE_NAMESPACE.svc:8220` URL, where `FS_RESOURCE_NAME` is the name of {{agent}} resource with {{fleet-server}} enabled and `FS_RESOURCE_NAMESPACE` is the namespace it was deployed in. * `xpack.fleet.packages` are required packages to enable {{fleet-server}} and {{agents}} to enroll. * `xpack.fleet.agentPolicies` policies are needed for {{fleet-server}} and {{agents}} to enroll to, check https://www.elastic.co/guide/en/fleet/current/agent-policy.html for more information. @@ -380,20 +380,20 @@ metadata: spec: config: # xpack.fleet.agents.elasticsearch.hosts: <1> - xpack.fleet.agents.fleet_server.hosts: ["https://fleet-server-sample-agent-http.default.svc:8220"] + xpack.fleet.agents.fleet_server.hosts: ["-agent-http.default.svc:8220"] xpack.fleet.outputs: - id: eck-fleet-agent-output-elasticsearch is_default: true name: eck-elasticsearch type: elasticsearch hosts: - - "https://elasticsearch-sample-es-http.default.svc:9200" <2> + - "-es-http.default.svc:9200" <2> ssl: certificate_authorities: ["/mnt/elastic-internal/elasticsearch-association/default/elasticsearch-sample/certs/ca.crt"] <3> ``` 1. This entry must not exist when running agent in fleet mode as a non-root user. -2. Note that the correct URL for {{es}} is `https://ELASTICSEARCH_NAME-es-http.YOUR-NAMESPACE.svc:9200` +2. Note that the correct URL for {{es}} is `-es-http..svc:9200` 3. Note that the correct path for {{es}} `certificate_authorities` is `/mnt/elastic-internal/elasticsearch-association/YOUR-NAMESPACE/ELASTICSEARCH-NAME/certs/ca.crt` diff --git a/deploy-manage/deploy/cloud-on-k8s/configuration-logstash.md b/deploy-manage/deploy/cloud-on-k8s/configuration-logstash.md index 22bd28d040..665fa3b5ee 100644 --- a/deploy-manage/deploy/cloud-on-k8s/configuration-logstash.md +++ b/deploy-manage/deploy/cloud-on-k8s/configuration-logstash.md @@ -487,7 +487,7 @@ kind: Secret metadata: name: external-es-ref stringData: - url: https://abcd-42.xyz.elastic-cloud.com:443 <1> + url: https://.elastic-cloud.com:443 <1> username: logstash_user <2> password: REDACTED <3> ca.crt: REDACTED <4> diff --git a/deploy-manage/deploy/cloud-on-k8s/configuration-standalone.md b/deploy-manage/deploy/cloud-on-k8s/configuration-standalone.md index 1a097ce779..e03d961434 100644 --- a/deploy-manage/deploy/cloud-on-k8s/configuration-standalone.md +++ b/deploy-manage/deploy/cloud-on-k8s/configuration-standalone.md @@ -398,20 +398,20 @@ metadata: spec: config: # xpack.fleet.agents.elasticsearch.hosts: <1> - xpack.fleet.agents.fleet_server.hosts: ["https://fleet-server-sample-agent-http.default.svc:8220"] + xpack.fleet.agents.fleet_server.hosts: ["-sample-agent-http.default.svc:8220"] xpack.fleet.outputs: - id: eck-fleet-agent-output-elasticsearch is_default: true name: eck-elasticsearch type: elasticsearch hosts: - - "https://elasticsearch-sample-es-http.default.svc:9200" <2> + - "-es-http.default.svc:9200" <2> ssl: certificate_authorities: ["/mnt/elastic-internal/elasticsearch-association/default/elasticsearch-sample/certs/ca.crt"] <3> ``` 1. This entry must not exist when running agent in fleet mode as a non-root user. -2. Note that the correct URL for {{es}} is `https://ELASTICSEARCH_NAME-es-http.YOUR-NAMESPACE.svc:9200` +2. Note that the correct URL for {{es}} is `-es-http..svc:9200` 3. Note that the correct path for {{es}} `certificate_authorities` is `/mnt/elastic-internal/elasticsearch-association/YOUR-NAMESPACE/ELASTICSEARCH-NAME/certs/ca.crt` diff --git a/deploy-manage/deploy/cloud-on-k8s/connect-to-external-elastic-resources.md b/deploy-manage/deploy/cloud-on-k8s/connect-to-external-elastic-resources.md index aa76c2bcd8..313a93ae4c 100644 --- a/deploy-manage/deploy/cloud-on-k8s/connect-to-external-elastic-resources.md +++ b/deploy-manage/deploy/cloud-on-k8s/connect-to-external-elastic-resources.md @@ -18,7 +18,7 @@ kind: Secret metadata: name: external-es-ref stringData: - url: https://sample.gcp.elastic-cloud.com + url: username: "elastic" password: REDACTED --- @@ -41,7 +41,7 @@ kind: Secret metadata: name: external-es-ref stringData: - url: https://abcd-42.xyz.elastic-cloud.com:443 + url: :443 username: "" password: "" api-key: REDACTED diff --git a/deploy-manage/deploy/cloud-on-k8s/elasticsearch-deployment-quickstart.md b/deploy-manage/deploy/cloud-on-k8s/elasticsearch-deployment-quickstart.md index 780f6dc747..77ef0cd5e1 100644 --- a/deploy-manage/deploy/cloud-on-k8s/elasticsearch-deployment-quickstart.md +++ b/deploy-manage/deploy/cloud-on-k8s/elasticsearch-deployment-quickstart.md @@ -125,7 +125,7 @@ In order to make requests to the [{{es}} API](elasticsearch://reference/elastics * From inside the Kubernetes cluster: ```sh - curl -u "elastic:$PASSWORD" -k "https://quickstart-es-http:9200" + curl -u "elastic:$PASSWORD" -k ":9200" ``` * From your local workstation: diff --git a/deploy-manage/deploy/cloud-on-k8s/k8s-kibana-es.md b/deploy-manage/deploy/cloud-on-k8s/k8s-kibana-es.md index 9d28b4b7f4..f2b4d62f0c 100644 --- a/deploy-manage/deploy/cloud-on-k8s/k8s-kibana-es.md +++ b/deploy-manage/deploy/cloud-on-k8s/k8s-kibana-es.md @@ -65,7 +65,7 @@ spec: count: 1 config: elasticsearch.hosts: - - https://elasticsearch.example.com:9200 + - :9200 elasticsearch.username: elastic secureSettings: - secretName: kibana-elasticsearch-credentials @@ -83,7 +83,7 @@ spec: count: 1 config: elasticsearch.hosts: - - https://elasticsearch-sample-es-http:9200 + - -es-http:9200 elasticsearch.username: elastic elasticsearch.ssl.certificateAuthorities: /etc/certs/ca.crt secureSettings: diff --git a/deploy-manage/deploy/cloud-on-k8s/quickstart-fleet.md b/deploy-manage/deploy/cloud-on-k8s/quickstart-fleet.md index ab56b17903..080ffb9d5f 100644 --- a/deploy-manage/deploy/cloud-on-k8s/quickstart-fleet.md +++ b/deploy-manage/deploy/cloud-on-k8s/quickstart-fleet.md @@ -72,8 +72,8 @@ products: elasticsearchRef: name: elasticsearch-quickstart config: - xpack.fleet.agents.elasticsearch.hosts: ["https://elasticsearch-quickstart-es-http.default.svc:9200"] - xpack.fleet.agents.fleet_server.hosts: ["https://fleet-server-quickstart-agent-http.default.svc:8220"] + xpack.fleet.agents.elasticsearch.hosts: [".default.svc:9200"] + xpack.fleet.agents.fleet_server.hosts: [".default.svc:8220"] xpack.fleet.packages: - name: system version: latest diff --git a/deploy-manage/deploy/elastic-cloud/heroku-getting-started-installing.md b/deploy-manage/deploy/elastic-cloud/heroku-getting-started-installing.md index 26e24d7d13..e5cdc617fc 100644 --- a/deploy-manage/deploy/elastic-cloud/heroku-getting-started-installing.md +++ b/deploy-manage/deploy/elastic-cloud/heroku-getting-started-installing.md @@ -33,7 +33,7 @@ After the {{heroku}} gets added, you can find the canonical URL you use to acces ```bash heroku config --app MY_APP | grep FOUNDELASTICSEARCH_URL -FOUNDELASTICSEARCH_URL: https://74f176887fdef36bb51e6e37nnnnnnnn.us-east-1.aws.found.io +FOUNDELASTICSEARCH_URL: .aws.found.io ``` ## Install a specific version and plugins [ech-getting-started-installing-version] diff --git a/deploy-manage/deploy/elastic-cloud/heroku-working-with-elasticsearch.md b/deploy-manage/deploy/elastic-cloud/heroku-working-with-elasticsearch.md index ddb00d9612..26a2074666 100644 --- a/deploy-manage/deploy/elastic-cloud/heroku-working-with-elasticsearch.md +++ b/deploy-manage/deploy/elastic-cloud/heroku-working-with-elasticsearch.md @@ -22,7 +22,7 @@ To find out what the ELASTICSEARCH_URL is for your {{es}} cluster, grep on the o ```bash heroku config --app MY_APP | grep ELASTICSEARCH_URL -ELASTICSEARCH_URL: https://74f176887fdef36bb51e6e37nnnnnnnn.us-east-1.aws.found.io +ELASTICSEARCH_URL: .aws.found.io ``` When you know your {{es}} URL, you can interact with the {{es}} endpoint using tools like curl. @@ -32,7 +32,7 @@ When you know your {{es}} URL, you can interact with the {{es}} endpoint using t To index a document into {{es}}, `POST` your document: ```bash -curl -u USER:PASSWORD https://ELASTICSEARCH_URL/my_index/_doc -XPOST -H 'Content-Type: application/json' -d '{ +curl -u USER:PASSWORD https:///my_index/_doc -XPOST -H 'Content-Type: application/json' -d '{ "title": "One", "tags": ["ruby"] }' ``` diff --git a/deploy-manage/deploy/elastic-cloud/manage-plugins-extensions-through-api.md b/deploy-manage/deploy/elastic-cloud/manage-plugins-extensions-through-api.md index d5a46d28d3..fd1392a567 100644 --- a/deploy-manage/deploy/elastic-cloud/manage-plugins-extensions-through-api.md +++ b/deploy-manage/deploy/elastic-cloud/manage-plugins-extensions-through-api.md @@ -51,7 +51,7 @@ curl -X POST \ -H "Authorization: ApiKey $CLOUD_API_KEY" \ -H 'Content-Type: application/json' \ -d '{ - "download_url" : "https://my_site/custom-plugin-8.4.3.zip", + "download_url" : "/custom-plugin-8.4.3.zip", "extension_type" : "plugin", "name" : "custom-plugin", "version" : "8.4.3" @@ -325,7 +325,7 @@ curl -X POST \ -H "Authorization: ApiKey $CLOUD_API_KEY" \ -H 'Content-Type: application/json' \ -d '{ - "download_url" : "https://my_site/custom-plugin-8.4.3-10212022.zip", + "download_url" : "/custom-plugin-8.4.3-10212022.zip", "extension_type" : "plugin", "name": "custom-plugin-10212022", "version" : "8.4.3" diff --git a/deploy-manage/deploy/self-managed/install-kibana-with-docker.md b/deploy-manage/deploy/self-managed/install-kibana-with-docker.md index 4f18f2d291..73114407a0 100644 --- a/deploy-manage/deploy/self-managed/install-kibana-with-docker.md +++ b/deploy-manage/deploy/self-managed/install-kibana-with-docker.md @@ -202,7 +202,7 @@ services: image: docker.elastic.co/kibana/kibana:{{stack-version}} environment: SERVER_NAME: kibana.example.org - ELASTICSEARCH_HOSTS: '["http://es01:9200","http://es02:9200","http://es03:9200"]' + ELASTICSEARCH_HOSTS: '[":9200",":9200",":9200"]' ``` Since environment variables are translated to CLI arguments, they take precedence over settings configured in `kibana.yml`. diff --git a/deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md b/deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md index 8aa6f575c8..4baf0c51bb 100644 --- a/deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md +++ b/deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md @@ -45,7 +45,7 @@ If you’re using {{agent}}, do not deploy {{filebeat}} for log collection. Inst ```yaml output.elasticsearch: # Array of hosts to connect to. - hosts: ["http://es-mon-1:9200", "http://es-mon-2:9200"] <1> + hosts: [":9200", ":9200"] <1> # Optional protocol and basic auth credentials. #protocol: "https" diff --git a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md index f15adb0f65..fa7525ca21 100644 --- a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md +++ b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md @@ -93,7 +93,7 @@ Want to use {{agent}} instead? Refer to [Collecting monitoring data with {{agent ```yaml output.elasticsearch: # Array of hosts to connect to. - hosts: ["http://es-mon-1:9200", "http://es-mon-2:9200"] <1> + hosts: [":9200", ":9200"] <1> # Optional protocol and basic auth credentials. #protocol: "https" diff --git a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md index e32354f1c5..93fb6e2f07 100644 --- a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md @@ -161,7 +161,7 @@ kind: Secret metadata: name: monitoring-metrics-es-ref stringData: - url: https://mon1.es.abcd-42.xyz.elastic-cloud.com:9243 + url: :9243 username: monitoring-user password: ``` diff --git a/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md b/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md index 4071d5bb96..cabeac2fb7 100644 --- a/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md +++ b/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md @@ -94,7 +94,7 @@ To learn about monitoring in general, see [Monitor a cluster](../../monitor.md). xpack.monitoring.exporters: id1: type: http - host: ["http://es-mon-1:9200", "http://es-mon-2:9200"] + host: [":9200", ":9200"] ``` 2. If the Elastic {{security-features}} are enabled on the monitoring cluster, you must provide appropriate credentials when data is shipped to the monitoring cluster: @@ -108,7 +108,7 @@ To learn about monitoring in general, see [Monitor a cluster](../../monitor.md). xpack.monitoring.exporters: id1: type: http - host: ["http://es-mon-1:9200", "http://es-mon-2:9200"] + host: [":9200", ":9200"] auth.username: remote_monitoring_user # "xpack.monitoring.exporters.id1.auth.secure_password" must be set in the keystore ``` @@ -121,7 +121,7 @@ To learn about monitoring in general, see [Monitor a cluster](../../monitor.md). xpack.monitoring.exporters: id1: type: http - host: ["https://es-mon1:9200", "https://es-mon-2:9200"] + host: [":9200", ":9200"] auth: username: remote_monitoring_user # "xpack.monitoring.exporters.id1.auth.secure_password" must be set in the keystore @@ -135,7 +135,7 @@ To learn about monitoring in general, see [Monitor a cluster](../../monitor.md). xpack.monitoring.exporters: id1: type: http - host: ["https://es-mon1:9200", "https://es-mon-2:9200"] + host: [":9200", ":9200"] auth: username: remote_monitoring_user # "xpack.monitoring.exporters.id1.auth.secure_password" must be set in the keystore diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md index 615a67e43d..46ab6aba9c 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md @@ -127,7 +127,7 @@ To learn about monitoring in general, refer to [](/deploy-manage/monitor/stack-m ```yaml output.elasticsearch: # Array of hosts to connect to. - hosts: ["http://es-mon-1:9200", "http://es-mon2:9200"] <1> + hosts: [":9200", "http://es-mon2:9200"] <1> # Optional protocol and basic auth credentials. #protocol: "https" diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md index bb2dd2212a..62df273216 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md @@ -121,7 +121,7 @@ You can update a deployment using the appropriate trust settings for the {{es}} The current trust settings can be found in the path `.resources.elasticsearch[0].info.settings.trust` when calling: ```sh -curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID?show_settings=true +curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID?show_settings=true ``` For example: diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md index 617df55ed3..bc50512d11 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md @@ -213,7 +213,7 @@ This section only applies if you’re using TLS certificates as cross-cluster se ```sh -curl -k -H 'Content-Type: application/json' -X PUT -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters -d ' +curl -k -H 'Content-Type: application/json' -X PUT -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters -d ' { "resources" : [ { @@ -241,7 +241,7 @@ Note the following when using the {{ece}} RESTful API: The following API request retrieves the remote clusters configuration: ```sh -curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters +curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters ``` ::::{note} diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md index c305b75591..6b6d3cda8f 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md @@ -158,7 +158,7 @@ You can update a deployment using the appropriate trust settings for the {{es}} Establishing the trust between the two {{ece}} environments can be done using the [trust relationships API](https://www.elastic.co/docs/api/doc/cloud-enterprise/group/endpoint-platformconfigurationtrustrelationships). For example, the list of trusted environments can be obtained calling the [list trust relationships endpoint](https://www.elastic.co/docs/api/doc/cloud-enterprise/group/endpoint-platformconfigurationtrustrelationships): ```sh -curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443//api/v1/regions/ece-region/platform/configuration/trust-relationships?include_certificate=false +curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443//api/v1/regions/ece-region/platform/configuration/trust-relationships?include_certificate=false ``` For each remote ECE environment, it will return something like this: @@ -286,7 +286,7 @@ This section only applies if you’re using TLS certificates as cross-cluster se ```sh -curl -k -H 'Content-Type: application/json' -X PUT -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters -d ' +curl -k -H 'Content-Type: application/json' -X PUT -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters -d ' { "resources" : [ { @@ -314,7 +314,7 @@ Note the following when using the {{ece}} RESTful API: The following API request retrieves the remote clusters configuration: ```sh -curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters +curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters ``` ::::{note} diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md index ce88e22ce4..1802f79ea5 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md @@ -122,7 +122,7 @@ You can update a deployment using the appropriate trust settings for the {{es}} The current trust settings can be found in the path `.resources.elasticsearch[0].info.settings.trust` when calling: ```sh -curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID?show_settings=true +curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID?show_settings=true ``` For example: @@ -242,7 +242,7 @@ This section only applies if you’re using TLS certificates as cross-cluster se ```sh -curl -k -H 'Content-Type: application/json' -X PUT -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters -d ' +curl -k -H 'Content-Type: application/json' -X PUT -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters -d ' { "resources" : [ { @@ -270,7 +270,7 @@ Note the following when using the {{ece}} RESTful API: The following API request retrieves the remote clusters configuration: ```sh -curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters +curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters ``` ::::{note} diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md index 43b64eb6bd..6f35067feb 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md @@ -293,7 +293,7 @@ This section only applies if you’re using TLS certificates as cross-cluster se ```sh -curl -k -H 'Content-Type: application/json' -X PUT -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters -d ' +curl -k -H 'Content-Type: application/json' -X PUT -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters -d ' { "resources" : [ { @@ -321,7 +321,7 @@ Note the following when using the {{ece}} RESTful API: The following API request retrieves the remote clusters configuration: ```sh -curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters +curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID/elasticsearch/$REF_ID/remote-clusters ``` ::::{note} diff --git a/deploy-manage/security/aws-privatelink-traffic-filters.md b/deploy-manage/security/aws-privatelink-traffic-filters.md index 2dbd160800..6859338b57 100644 --- a/deploy-manage/security/aws-privatelink-traffic-filters.md +++ b/deploy-manage/security/aws-privatelink-traffic-filters.md @@ -168,7 +168,7 @@ The mapping will be different for your region. Our production VPC Service for `u * Alternatively, use the following URL structure: ``` - https://{{alias}}.{product}.{{private_hosted_zone_domain_name}} + https://.. ``` For example: diff --git a/deploy-manage/security/azure-private-link-traffic-filters.md b/deploy-manage/security/azure-private-link-traffic-filters.md index 69dbd51a6d..f477d9b9ad 100644 --- a/deploy-manage/security/azure-private-link-traffic-filters.md +++ b/deploy-manage/security/azure-private-link-traffic-filters.md @@ -162,7 +162,7 @@ Let’s test the connection: * If you have a [custom endpoint alias](/deploy-manage/deploy/elastic-cloud/custom-endpoint-aliases.md) configured, you can use the custom endpoint URL to connect. ``` - https://{{alias}}.{product}.{{private_hosted_zone_domain_name}} + https://.. ``` For example: @@ -174,7 +174,7 @@ Let’s test the connection: * Alternatively, use the following URL structure: ``` - https://{{elasticsearch_cluster_ID}}.{private_hosted_zone_domain_name}:9243 + https://.:9243 ``` For example: diff --git a/deploy-manage/security/gcp-private-service-connect-traffic-filters.md b/deploy-manage/security/gcp-private-service-connect-traffic-filters.md index 0245642e82..393ec710ad 100644 --- a/deploy-manage/security/gcp-private-service-connect-traffic-filters.md +++ b/deploy-manage/security/gcp-private-service-connect-traffic-filters.md @@ -108,7 +108,7 @@ The process of setting up the Private link connection to your clusters is split * If you have a [custom endpoint alias](/deploy-manage/deploy/elastic-cloud/custom-endpoint-aliases.md) configured, you can use the custom endpoint URL to connect. ``` - https://{{alias}}.{product}.{{private_hosted_zone_domain_name}} + https://.. ``` For example: @@ -120,7 +120,7 @@ The process of setting up the Private link connection to your clusters is split * Alternatively, use the following URL structure: ``` - https://{{elasticsearch_cluster_ID}}.{private_hosted_zone_domain_name}:9243 + https://.:9243 ``` For example: diff --git a/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md b/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md index f25b184198..7e103fccbc 100644 --- a/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md +++ b/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md @@ -71,7 +71,7 @@ To delete a snapshot repository configuration from your {{ece}} installation: 4. Run the following command against the repository name: ```sh - curl -s -XDELETE -u USER:PASSWORD https://COORDINATOR_HOST:12443/api/v1/platform/configuration/snapshots/repositories/REPOSITORY_NAME + curl -s -XDELETE -u USER:PASSWORD https://$COORDINATOR_HOST:12443/api/v1/platform/configuration/snapshots/repositories/REPOSITORY_NAME ``` ::::{note} diff --git a/deploy-manage/tools/snapshot-and-restore/cloud-on-k8s.md b/deploy-manage/tools/snapshot-and-restore/cloud-on-k8s.md index 20a9cc0c6a..41a6caaa57 100644 --- a/deploy-manage/tools/snapshot-and-restore/cloud-on-k8s.md +++ b/deploy-manage/tools/snapshot-and-restore/cloud-on-k8s.md @@ -484,7 +484,7 @@ spec: "settings": { "bucket": "es-repo", "path_style_access": true, <1> - "endpoint": "https://mys3service.default.svc.cluster.local/" <2> + "endpoint": ".default.svc.cluster.local/" <2> } } ``` diff --git a/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md b/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md index b6bbeda119..5e798a12de 100644 --- a/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md +++ b/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md @@ -106,7 +106,7 @@ If your ECE installation is still using the default, auto-generated certificates - Apply a valid license. It is required to have an `Enterprise resource unit`-compatible license applied before upgrading to ECE 2.7 or later. The most reliable way to check if your license is compatible is to use the {{ece}} API and check the value of the license version field: ```sh - curl -X GET -u admin:PASSWORD -k https://COORDINATOR_HOST:12443/api/v1/platform/license + curl -X GET -u admin:PASSWORD -k https://$COORDINATOR_HOST:12443/api/v1/platform/license { "license": { "version": 4, diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md b/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md index efe8489d0e..4ab004acea 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md @@ -95,7 +95,7 @@ Client authentication is enabled by default for the JWT realms. Disabling client order: 3 token_type: id_token client_authentication.type: shared_secret - allowed_issuer: "https://issuer.example.com/jwt/" + allowed_issuer: "/jwt/" allowed_audiences: [ "8fb85eba-979c-496c-8ae2-a57fde3f12d0" ] allowed_signature_algorithms: [RS256,HS256] pkc_jwkset_path: jwt/jwkset.json @@ -136,7 +136,7 @@ Client authentication is enabled by default for the JWT realms. Disabling client order: 4 token_type: access_token client_authentication.type: shared_secret - allowed_issuer: "https://issuer.example.com/jwt/" + allowed_issuer: "/jwt/" allowed_subjects: [ "123456-compute@admin.example.com" ] allowed_subject_patterns: [ "wild*@developer?.example.com", "/[a-z]+<1-10>\\@dev\\.example\\.com/"] allowed_audiences: [ "elasticsearch" ] @@ -144,7 +144,7 @@ Client authentication is enabled by default for the JWT realms. Disabling client token_use: access version: ["1.0", "2.0"] allowed_signature_algorithms: [RS256,HS256] - pkc_jwkset_path: "https://idp-42.example.com/.well-known/configuration" + pkc_jwkset_path: "/.well-known/configuration" fallback_claims.sub: client_id fallback_claims.aud: scope claims.principal: sub diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md b/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md index e70b9f56e8..c0c5a8da9f 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md @@ -56,7 +56,7 @@ xpack.security.authc.providers: order: 1 realm: saml1 description: "Log in with SSO" - icon: "https://my-company.xyz/saml-logo.svg" + icon: "/saml-logo.svg" saml.saml2: order: 2 realm: saml2 diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md b/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md index df9c3644a8..3bfda78cac 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md @@ -304,12 +304,12 @@ For more information about OpenID connect in Okta, refer to [Okta OAuth 2.0 docu rp.response_type: "code" rp.requested_scopes: ["openid", "email"] rp.redirect_uri: "KIBANA_ENDPOINT_URL/api/security/oidc/callback" - op.issuer: "https://YOUR_OKTA_DOMAIN" - op.authorization_endpoint: "https://YOUR_OKTA_DOMAIN/oauth2/v1/authorize" - op.token_endpoint: "https://YOUR_OKTA_DOMAIN/oauth2/v1/token" - op.userinfo_endpoint: "https://YOUR_OKTA_DOMAIN/oauth2/v1/userinfo" - op.endsession_endpoint: "https://YOUR_OKTA_DOMAIN/oauth2/v1/logout" - op.jwkset_path: "https://YOUR_OKTA_DOMAIN/oauth2/v1/keys" + op.issuer: "https://" + op.authorization_endpoint: "https:///oauth2/v1/authorize" + op.token_endpoint: "https:///oauth2/v1/token" + op.userinfo_endpoint: "https:///oauth2/v1/userinfo" + op.endsession_endpoint: "https:///oauth2/v1/logout" + op.jwkset_path: "https:///oauth2/v1/keys" claims.principal: email claim_patterns.principal: "^([^@]+)@YOUR_DOMAIN\\.TLD$" ``` @@ -318,7 +318,7 @@ For more information about OpenID connect in Okta, refer to [Okta OAuth 2.0 docu * `YOUR_CLIENT_ID` is the Client ID that you set up in the previous steps. * `KIBANA_ENDPOINT_URL` is your {{kib}} endpoint, available from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). - * `YOUR_OKTA_DOMAIN` is the URL of your Okta domain shown on your Okta dashboard. + * `` is the URL of your Okta domain shown on your Okta dashboard. * `YOUR_DOMAIN` and `TLD` in the `claim_patterns.principal` regular expression are your organization email domain and top level domain. diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/openid-connect.md b/deploy-manage/users-roles/cluster-or-deployment-auth/openid-connect.md index 09a21101c3..daaad3a266 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/openid-connect.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/openid-connect.md @@ -95,16 +95,16 @@ This realm has a few mandatory settings, and a number of optional settings. The order: 2 rp.client_id: "the_client_id" rp.response_type: code - rp.redirect_uri: "https://kibana.example.org:5601/api/security/oidc/callback" - op.issuer: "https://op.example.org" - op.authorization_endpoint: "https://op.example.org/oauth2/v1/authorize" - op.token_endpoint: "https://op.example.org/oauth2/v1/token" + rp.redirect_uri: ":5601/api/security/oidc/callback" + op.issuer: "" + op.authorization_endpoint: "/oauth2/v1/authorize" + op.token_endpoint: "/oauth2/v1/token" op.jwkset_path: oidc/jwkset.json - op.userinfo_endpoint: "https://op.example.org/oauth2/v1/userinfo" - op.endsession_endpoint: "https://op.example.org/oauth2/v1/logout" - rp.post_logout_redirect_uri: "https://kibana.example.org:5601/security/logged_out" + op.userinfo_endpoint: "/oauth2/v1/userinfo" + op.endsession_endpoint: "/oauth2/v1/logout" + rp.post_logout_redirect_uri: ":5601/security/logged_out" claims.principal: sub - claims.groups: "http://example.info/claims/groups" + claims.groups: "/claims/groups" ``` ::::{dropdown} Common settings @@ -173,7 +173,7 @@ In {{ech}} and {{ece}}, after you configure Client Secret, any attempt to restar ::: ::::{note} -According to the OpenID Connect specification, the OP should also make their configuration available at a well known URL, which is the concatenation of their `Issuer` value with the `.well-known/openid-configuration` string. For example: `https://op.org.com/.well-known/openid-configuration`. +According to the OpenID Connect specification, the OP should also make their configuration available at a well known URL, which is the concatenation of their `Issuer` value with the `.well-known/openid-configuration` string. For example: `/.well-known/openid-configuration`. That document should contain all the necessary information to configure the OpenID Connect realm in {{es}}. :::: @@ -228,7 +228,7 @@ To configure claims mapping: * `claims.principal: sub`: Instructs {{es}} to look for the OpenID Connect claim named `sub` in the ID Token that the OP issued for the user (or in the UserInfo response) and assign the value of this claim to the `principal` user property. `sub` is a commonly used claim for the principal property as it is an identifier of the user in the OP and it is also a required claim of the ID Token. This means that `sub` is available in most OPs. However, the OP may provide another claim that is a better fit for your needs. - * `claims.groups: "http://example.info/claims/groups"`: Instructs {{es}} to look for the claim with the name `http://example.info/claims/groups`, either in the ID Token or in the UserInfo response, and map the value(s) of it to the user property `groups` in {{es}}. + * `claims.groups: "/claims/groups"`: Instructs {{es}} to look for the claim with the name `/claims/groups`, either in the ID Token or in the UserInfo response, and map the value(s) of it to the user property `groups` in {{es}}. There is no standard claim in the specification that is used for expressing roles or group memberships of the authenticated user in the OP, so the name of the claim that should be mapped here will vary between providers. Consult your OP documentation for more details. @@ -274,12 +274,12 @@ xpack.security.authc.realms.oidc.oidc1: order: 2 rp.client_id: "the_client_id" rp.response_type: code - rp.redirect_uri: "https://kibana.example.org:5601/api/security/oidc/callback" - op.authorization_endpoint: "https://op.example.org/oauth2/v1/authorize" - op.token_endpoint: "https://op.example.org/oauth2/v1/token" - op.userinfo_endpoint: "https://op.example.org/oauth2/v1/userinfo" - op.endsession_endpoint: "https://op.example.org/oauth2/v1/logout" - op.issuer: "https://op.example.org" + rp.redirect_uri: ":5601/api/security/oidc/callback" + op.authorization_endpoint: "/oauth2/v1/authorize" + op.token_endpoint: "/oauth2/v1/token" + op.userinfo_endpoint: "/oauth2/v1/userinfo" + op.endsession_endpoint: "/oauth2/v1/logout" + op.issuer: "" op.jwkset_path: oidc/jwkset.json claims.principal: email_verified claim_patterns.principal: "^([^@]+)@staff\\.example\\.com$" diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/saml.md b/deploy-manage/users-roles/cluster-or-deployment-auth/saml.md index 4ed142bc01..51e3c9c80c 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/saml.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/saml.md @@ -135,10 +135,10 @@ If you're using {{ece}} or {{ech}}, and you're using machine learning or a deplo xpack.security.authc.realms.saml.saml1: order: 2 idp.metadata.path: saml/idp-metadata.xml - idp.entity_id: "https://sso.example.com/" - sp.entity_id: "https://kibana.example.com/" - sp.acs: "https://kibana.example.com/api/security/saml/callback" - sp.logout: "https://kibana.example.com/logout" + idp.entity_id: "" + sp.entity_id: "" + sp.acs: "/api/security/saml/callback" + sp.logout: "/logout" attributes.principal: "urn:oid:0.9.2342.19200300.100.1.1" attributes.groups: "urn:oid:1.3.6.1.4.1.5923.1.5.1." ``` @@ -701,34 +701,34 @@ Each SAML realm must have its own unique Entity ID (`sp.entity_id`), and its own These realms may use the same Identity Provider, but are not required to. -The following is example of having 3 difference {{kib}} instances, 2 of which use the same internal IdP, and another which uses a different IdP. +The following is example of having 3 different {{kib}} instances, 2 of which use the same internal IdP, and another which uses a different IdP. ```yaml xpack.security.authc.realms.saml.saml_finance: order: 2 idp.metadata.path: saml/idp-metadata.xml - idp.entity_id: "https://sso.example.com/" - sp.entity_id: "https://kibana.finance.example.com/" - sp.acs: "https://kibana.finance.example.com/api/security/saml/callback" - sp.logout: "https://kibana.finance.example.com/logout" + idp.entity_id: "" + sp.entity_id: "" + sp.acs: "/api/security/saml/callback" + sp.logout: "/logout" attributes.principal: "urn:oid:0.9.2342.19200300.100.1.1" attributes.groups: "urn:oid:1.3.6.1.4.1.5923.1.5.1." xpack.security.authc.realms.saml.saml_sales: order: 3 idp.metadata.path: saml/idp-metadata.xml - idp.entity_id: "https://sso.example.com/" - sp.entity_id: "https://kibana.sales.example.com/" - sp.acs: "https://kibana.sales.example.com/api/security/saml/callback" - sp.logout: "https://kibana.sales.example.com/logout" + idp.entity_id: "" + sp.entity_id: "" + sp.acs: "/api/security/saml/callback" + sp.logout: "/logout" attributes.principal: "urn:oid:0.9.2342.19200300.100.1.1" attributes.groups: "urn:oid:1.3.6.1.4.1.5923.1.5.1." xpack.security.authc.realms.saml.saml_eng: order: 4 idp.metadata.path: saml/idp-external.xml - idp.entity_id: "https://engineering.sso.example.net/" - sp.entity_id: "https://kibana.engineering.example.com/" - sp.acs: "https://kibana.engineering.example.com/api/security/saml/callback" - sp.logout: "https://kibana.engineering.example.com/logout" + idp.entity_id: "" + sp.entity_id: "" + sp.acs: "/api/security/saml/callback" + sp.logout: "/logout" attributes.principal: "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn" ``` diff --git a/manage-data/data-store/manage-data-from-the-command-line.md b/manage-data/data-store/manage-data-from-the-command-line.md index 5038ba8dc1..213ce7cf9d 100644 --- a/manage-data/data-store/manage-data-from-the-command-line.md +++ b/manage-data/data-store/manage-data-from-the-command-line.md @@ -32,7 +32,7 @@ To use these examples, you also need to have the [curl](http://curl.haxx.se/) co To index a document into {{es}}, `POST` your document: ```bash -curl -u USER:PASSWORD https://ELASTICSEARCH_URL/my_index/_doc -XPOST -H 'Content-Type: application/json' -d '{ +curl -u USER:PASSWORD https:///my_index/_doc -XPOST -H 'Content-Type: application/json' -d '{ "title": "One", "tags": ["ruby"] }' ``` @@ -49,7 +49,7 @@ To achieve the best possible performance, use the bulk API. To index some additional documents with the bulk API: ```bash -curl -u USER:PASSWORD https://ELASTICSEARCH_URL/my_index/_doc/_bulk -XPOST -H 'Content-Type: application/json' -d ' +curl -u USER:PASSWORD https:///my_index/_doc/_bulk -XPOST -H 'Content-Type: application/json' -d ' {"index": {}} {"title": "Two", "tags": ["ruby", "python"] } {"index": {}} @@ -73,7 +73,7 @@ To update an existing document in {{es}}, `POST` the updated document to `http:/ For example, to update the last document indexed from the previous example with `"_id":"06NqhW4BnhCSymaqFHQn"`: ```bash -curl -u USER:PASSWORD https://ELASTICSEARCH_URL/my_index/_doc/06NqhW4BnhCSymaqFHQn -XPOST -H 'Content-Type: application/json' -d '{ +curl -u USER:PASSWORD https:///my_index/_doc/06NqhW4BnhCSymaqFHQn -XPOST -H 'Content-Type: application/json' -d '{ "title": "Four updated", "tags": ["ruby", "php", "python"] }' ``` @@ -86,7 +86,7 @@ The JSON response shows that the version counter for the document got incremente To take a look at a specific document you indexed, here the last document we updated with the ID `0KNPhW4BnhCSymaq_3SI`: ```bash -curl -u USER:PASSWORD https://ELASTICSEARCH_URL/my_index/_doc/06NqhW4BnhCSymaqFHQn +curl -u USER:PASSWORD https:///my_index/_doc/06NqhW4BnhCSymaqFHQn ``` This request didn’t include `GET`, as the method is implied if you don’t specify anything else. If the document you are looking for exists, {{es}} returns `found":true` along with the document as part of the JSON response. Otherwise, the JSON response contains `"found":false`. @@ -97,14 +97,14 @@ This request didn’t include `GET`, as the method is implied if you don’t spe You issue search requests for documents with one of these {{es}} endpoints: ```bash -https://ELASTICSEARCH_URL/_search -https://ELASTICSEARCH_URL/INDEX_NAME/_search +https:///_search +https:///INDEX_NAME/_search ``` Either a `GET` or a `POST` request with some URI search parameters works, or omit the method to default to `GET` request: ```bash -curl -u USER:PASSWORD https://ELASTICSEARCH_URL/my_index/_doc/_search?q=title:T* +curl -u USER:PASSWORD https:///my_index/_doc/_search?q=title:T* ``` For an explanation of the allowed parameters, check [URI Search](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search). @@ -112,7 +112,7 @@ For an explanation of the allowed parameters, check [URI Search](https://www.ela To make {{es}} return a more human readable JSON response, add `?pretty=true` to the request: ```bash -curl -u USER:PASSWORD https://ELASTICSEARCH_URL/my_index/_doc/_search?pretty=true -H 'Content-Type: application/json' -d '{ +curl -u USER:PASSWORD https:///my_index/_doc/_search?pretty=true -H 'Content-Type: application/json' -d '{ "query": { "query_string": {"query": "*"} } @@ -131,13 +131,13 @@ You delete documents from {{es}} by sending `DELETE` requests. To delete a single document by ID from an earlier example: ```bash -curl -u USER:PASSWORD https://ELASTICSEARCH_URL/my_index/_doc/06NqhW4BnhCSymaqFHQn -XDELETE +curl -u USER:PASSWORD https:///my_index/_doc/06NqhW4BnhCSymaqFHQn -XDELETE ``` To delete a whole index, here `my_index`: ```bash -curl -u USER:PASSWORD https://ELASTICSEARCH_URL/my_index -XDELETE +curl -u USER:PASSWORD https:///my_index -XDELETE ``` The JSON response returns `{"acknowledged":true}` to indicate that the index deletion was a success. diff --git a/manage-data/data-store/templates/index-template-management.md b/manage-data/data-store/templates/index-template-management.md index b6d769fafc..4683e992c2 100644 --- a/manage-data/data-store/templates/index-template-management.md +++ b/manage-data/data-store/templates/index-template-management.md @@ -108,7 +108,7 @@ You’re now ready to create new indices using your index template. "lon": -121.7864906 } }, - "url": "https://media-for-the-masses.theacademyofperformingartsandscience.org/uploads/charles-fullerton.jpg" + "url": "" } POST /my-index-000002/_doc @@ -124,7 +124,7 @@ You’re now ready to create new indices using your index template. } }, "memory": 241720, - "url": "https://theacademyofperformingartsandscience.org/people/type:astronauts/name:laurel-b-clark/profile" + "url": "" } ``` diff --git a/manage-data/migrate.md b/manage-data/migrate.md index ed428842c0..3f9ed07be9 100644 --- a/manage-data/migrate.md +++ b/manage-data/migrate.md @@ -95,7 +95,7 @@ Follow these steps to reindex data remotely: { "source": { "remote": { - "host": "https://REMOTE_ELASTICSEARCH_ENDPOINT:PORT", + "host": "https://:", "username": "USER", "password": "PASSWORD" }, diff --git a/manage-data/migrate/migrate-from-a-self-managed-cluster-with-a-self-signed-certificate-using-remote-reindex.md b/manage-data/migrate/migrate-from-a-self-managed-cluster-with-a-self-signed-certificate-using-remote-reindex.md index 0ae113f0f7..cffa7c4b0d 100644 --- a/manage-data/migrate/migrate-from-a-self-managed-cluster-with-a-self-signed-certificate-using-remote-reindex.md +++ b/manage-data/migrate/migrate-from-a-self-managed-cluster-with-a-self-signed-certificate-using-remote-reindex.md @@ -28,7 +28,7 @@ Let’s assume that the self-managed cluster that uses a self-signed certificate 2. Test `cecert.pem` you have just created with `curl`, this should return a successful response: ```text - curl -XGET https://$SOURCE_SERVER:$PORT -u : --cacert cacert.pem + curl -XGET https://: -u : --cacert cacert.pem ``` 3. Create the folder `my_source_ca` to store the file `cacert.pem`, and compress the folder to `my_source_ca.zip`. @@ -80,7 +80,7 @@ POST _reindex { "source": { "remote": { - "host": "https://$SOURCE_SERVER:$PORT", + "host": "https://:", "username": "username", "password": "xxx" }, diff --git a/solutions/observability/apm/monitor-fleet-managed-apm-server.md b/solutions/observability/apm/monitor-fleet-managed-apm-server.md index b5676bf7f0..ccc8ae078e 100644 --- a/solutions/observability/apm/monitor-fleet-managed-apm-server.md +++ b/solutions/observability/apm/monitor-fleet-managed-apm-server.md @@ -134,7 +134,7 @@ See the [{{agent}} command reference](/reference/fleet/agent-command-reference.m ```yaml output.elasticsearch: # Array of hosts to connect to. - hosts: ["http://es-mon-1:9200", "http://es-mon2:9200"] <1> + hosts: [":9200", "http://es-mon2:9200"] <1> # Optional protocol and basic auth credentials. #protocol: "https" diff --git a/solutions/observability/apm/use-metricbeat-to-send-monitoring-data.md b/solutions/observability/apm/use-metricbeat-to-send-monitoring-data.md index 3355eee1d4..a5b85399b6 100644 --- a/solutions/observability/apm/use-metricbeat-to-send-monitoring-data.md +++ b/solutions/observability/apm/use-metricbeat-to-send-monitoring-data.md @@ -127,7 +127,7 @@ To collect and ship monitoring data: ```yaml output.elasticsearch: # Array of hosts to connect to. - hosts: ["http://es-mon-1:9200", "http://es-mon2:9200"] <1> + hosts: [":9200", "http://es-mon2:9200"] <1> # Optional protocol and basic auth credentials. #protocol: "https" diff --git a/troubleshoot/elasticsearch/security/trb-security-setup.md b/troubleshoot/elasticsearch/security/trb-security-setup.md index 52b108849b..49294261c6 100644 --- a/troubleshoot/elasticsearch/security/trb-security-setup.md +++ b/troubleshoot/elasticsearch/security/trb-security-setup.md @@ -58,7 +58,7 @@ The [elasticsearch-setup-passwords command](elasticsearch://reference/elasticsea xpack.security.http.ssl. ... ERROR: Failed to establish SSL connection to elasticsearch at - https://elasticsearch.example.com:9200/_security/_authenticate?pretty. + :9200/_security/_authenticate?pretty. ``` diff --git a/troubleshoot/elasticsearch/unable-to-retrieve-node-fs-stats.md b/troubleshoot/elasticsearch/unable-to-retrieve-node-fs-stats.md index 9bc80c5638..4aea3a9de4 100644 --- a/troubleshoot/elasticsearch/unable-to-retrieve-node-fs-stats.md +++ b/troubleshoot/elasticsearch/unable-to-retrieve-node-fs-stats.md @@ -62,7 +62,7 @@ elasticsearch.ssl.certificateAuthorities: ["path/to/ca.crt"] Use `curl` to test the connection to each host in `elasticsearch.hosts`: ```bash -curl http://es01:9200/ +curl :9200/ ``` If you're using TLS, try one of the following: