iSharkFly-Docs
/
opensearch-docs-cn
mirror of https://github.com/iSharkFly-Docs/opensearch-docs-cn
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

for acronym spell out 1st instance (#2232) 

Signed-off-by: alicejw <alicejw@amazon.com>

Signed-off-by: alicejw <alicejw@amazon.com>
This commit is contained in:
Alice Williams 2022-12-15 09:36:09 -08:00 committed by GitHub
parent 1e4dc30d5c
commit a41457242e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
_monitoring-plugins/alerting/security.md
View File

@ -85,7 +85,7 @@ Then, use this new role for all alerting users. -->
### Specify RBAC backend roles
You can specify RBAC backend roles when you create or update a monitor with the Alerting API.
You can specify role-based access control (RBAC) backend roles when you create or update a monitor with the Alerting API.
In a create monitor scenario, follow these guidelines to specify roles:
@ -110,7 +110,7 @@ Regular user | No | Don’t update the backend roles on the monitor.
To create an RBAC role, follow instructions in the Security Plugin API documentation to [Create role]({{site.url}}{{site.baseurl}}/security-plugin/access-control/api#create-role).
### Create a monitor with an RBAC role
When you create a monitor with the Alerting API, you can specify the role-based access control (RBAC) roles at the bottom of the request body. Use the `rbac_roles` parameter.
When you create a monitor with the Alerting API, you can specify the RBAC roles at the bottom of the request body. Use the `rbac_roles` parameter.
The following sample shows the RBAC roles specified by the RBAC parameter: