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: reference/fleet/remote-elasticsearch-output.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ To configure a remote {{es}} cluster for your {{agent}} data:
43
43
2. In the **Outputs** section, copy the `Hosts` value of the default {{es}} output. If the value is not visible in full, edit the default {{es}} output to display the full value.
44
44
3. Back in your main cluster (Cluster A), paste the value you copied into the **Hosts** field of the remote output configuration.
45
45
46
-
Alternatively, for cloud deployments, you can navigate to your deployment's `deployments/<deployment_id>/security` page, scroll to the the **Remote cluster parameters** section, and copy the **Proxy Address** to use it in the `Hosts` field of the remote output configuration.
46
+
Alternatively, for cloud deployments, you can navigate to your deployment's `deployments/<deployment_id>/security` page and scroll to the **Remote cluster parameters** section. Copy the **Proxy Address**, and enter it in the **Hosts** field of the remote output configuration.
47
47
::::
48
48
49
49
5. In the **Service Token** field, add a service token to access the remote cluster (Cluster B).
@@ -120,7 +120,7 @@ This feature is only available with certain subscriptions. For more information,
120
120
2. In the **Outputs** section, copy the `Hosts` value of the default {{es}} output. If the value is not visible in full, edit the default {{es}} output to display the full value.
121
121
3. Back in your main cluster (Cluster A), paste the value you copied into the **Hosts** field of the remote output configuration.
122
122
123
-
Alternatively, for cloud deployments, you can navigate to your deployment's `deployments/<deployment_id>/security` page, scroll to the the **Remote cluster parameters** section, and copy the **Proxy Address** to use it in the `Hosts` field of the remote output configuration.
123
+
Alternatively, for cloud deployments, you can navigate to your deployment's `deployments/<deployment_id>/security` page and scroll to the **Remote cluster parameters** section. Copy the **Proxy Address**, and enter it in the **Hosts** field of the remote output configuration.
0 commit comments