-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
70 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -21,3 +21,4 @@ from Heartbeat 7.0. | |
|
||
include::overview.asciidoc[] | ||
include::monitor.asciidoc[] | ||
include::security.asciidoc[] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,69 @@ | ||
[role="xpack"] | ||
[[uptime-security]] | ||
|
||
== Use with Elasticsearch Security | ||
|
||
If you have Elasticsearch security enabled you'll need to enable certain privileges for users | ||
that would like to access the Uptime app. In this document we'll show an example of creating | ||
a user and support role to implement those privileges. | ||
|
||
=== Creating the Role | ||
|
||
You'll need a role that lets you access the Heartbeat indices, which by default are `heartbeat-*`. | ||
You can create this with the following request: | ||
|
||
["source","sh",subs="attributes,callouts"] | ||
--------------------------------------------------------------- | ||
PUT /_security/role/uptime | ||
{ "indices" : [ | ||
{ | ||
"names" : [ | ||
"heartbeat-*" | ||
], | ||
"privileges" : [ | ||
"read", | ||
"view_index_metadata" | ||
], | ||
"field_security" : { | ||
"grant" : [ | ||
"*" | ||
] | ||
}, | ||
"allow_restricted_indices" : false | ||
} | ||
], | ||
"applications" : [ | ||
{ | ||
"application" : "kibana-.kibana", | ||
"privileges" : [ | ||
"all" | ||
], | ||
"resources" : [ | ||
"*" | ||
] | ||
} | ||
], | ||
"transient_metadata" : { | ||
"enabled" : true | ||
} | ||
} | ||
--------------------------------------------------------------- | ||
|
||
=== Creating the User | ||
|
||
You will then need to create a user with both the `kibana_user`, and `uptime` roles. | ||
You can do this with the following request. | ||
|
||
["source","sh",subs="attributes,callouts"] | ||
--------------------------------------------------------------- | ||
PUT /_security/user/jacknich | ||
{ | ||
"password" : "j@rV1s", | ||
"roles" : [ "uptime", "kibana_user" ], | ||
"full_name" : "Jack Nicholson", | ||
"email" : "[email protected]", | ||
"metadata" : { | ||
"intelligence" : 7 | ||
} | ||
} | ||
--------------------------------------------------------------- |