Skip to content

Commit 2a6364e

Browse files
committed
Fix
1 parent 6e184d6 commit 2a6364e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

reference/fleet/remote-elasticsearch-output.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ To configure a remote {{es}} cluster for your {{agent}} data:
4343
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.
4444
3. Back in your main cluster (Cluster A), paste the value you copied into the **Hosts** field of the remote output configuration.
4545

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.
4747
::::
4848

4949
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,
120120
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.
121121
3. Back in your main cluster (Cluster A), paste the value you copied into the **Hosts** field of the remote output configuration.
122122

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.
124124
::::
125125

126126
4. Enable **Synchronize integrations**.

0 commit comments

Comments
 (0)