Skip to content

Commit 22f3bb4

Browse files
committed
[DOCS] Fixes security links (#49563)
1 parent 3cfaeac commit 22f3bb4

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

docs/plugins/discovery-ec2.asciidoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -338,7 +338,7 @@ connections are unreliable or slow, it is not optimised for this case and its
338338
performance may suffer. If you wish to geographically distribute your data, you
339339
should provision multiple clusters and use features such as
340340
{ref}/modules-cross-cluster-search.html[cross-cluster search] and
341-
{stack-ov}/xpack-ccr.html[cross-cluster replication].
341+
{ref}/xpack-ccr.html[cross-cluster replication].
342342

343343
===== Other recommendations
344344

docs/reference/ingest/apis/enrich/put-enrich-policy.asciidoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ DELETE /_enrich/policy/my-policy
5757
If you use {es} {security-features}, you must have:
5858

5959
* `read` index privileges for any indices used
60-
* The `enrich_user` {stack-ov}/built-in-roles.html[built-in role]
60+
* The `enrich_user` <<built-in-roles,built-in role>>
6161
// end::enrich-policy-api-prereqs[]
6262

6363

docs/reference/monitoring/esms.asciidoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ output.elasticsearch:
7878
<1> Replace `MONITORING_ELASTICSEARCH_URL` with the appropriate URL for
7979
{esms-init}, which was provided by the Elastic support team.
8080
<2> The Elastic support team creates this user in {esms-init} and grants it the
81-
{stack-ov}/built-in-roles.html[`remote_monitoring_agent` built-in role].
81+
<<built-in-roles,`remote_monitoring_agent` built-in role>>.
8282
<3> Replace `MONITORING_AGENT_PASSWORD` with the value provided to you by the
8383
Elastic support team.
8484
// end::metricbeat-config[]
@@ -180,9 +180,9 @@ If the Elastic {security-features} are enabled, you must also provide a user
180180
ID and password so that {metricbeat} can collect metrics successfully:
181181

182182
.. Create a user on the production cluster that has the
183-
`remote_monitoring_collector` {stack-ov}/built-in-roles.html[built-in role].
183+
`remote_monitoring_collector` <<built-in-roles,built-in role>>.
184184
Alternatively, use the `remote_monitoring_user`
185-
{stack-ov}/built-in-users.html[built-in user].
185+
<<built-in-users,built-in user>>.
186186

187187
.. Add the `username` and `password` settings to the {kib} module configuration
188188
file.

0 commit comments

Comments
 (0)