Reorganize Configuration section of the Security TOC (#2212) #2542
Conversation
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
* fix#2155-sec-toc-config-reorg Signed-off-by: cwillum <[email protected]> * fix#2155-sec-toc-config-reorg Signed-off-by: cwillum <[email protected]> * fix#2155-sec-toc-config-reorg Signed-off-by: cwillum <[email protected]> * fix#2155-sec-toc-config-reorg Signed-off-by: cwillum <[email protected]> * fix#2155-sec-toc-config-reorg Signed-off-by: cwillum <[email protected]> * fix#2155-sec-toc-config-reorg Signed-off-by: cwillum <[email protected]> * fix#2155-sec-toc-config-reorg Signed-off-by: cwillum <[email protected]> * fix#2155-sec-toc-config-reorg Signed-off-by: cwillum <[email protected]> * fix#2155-sec-toc-config-reorg Signed-off-by: cwillum <[email protected]> * fix#2155-sec-toc-config-reorg Signed-off-by: cwillum <[email protected]> * fix#2155-sec-toc-config-reorg Signed-off-by: cwillum <[email protected]> * Rename security section. Fix links. Add redirects Signed-off-by: Naarcha-AWS <[email protected]> --------- Signed-off-by: cwillum <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> Co-authored-by: Naarcha-AWS <[email protected]> (cherry picked from commit d04e88b)
cwillum
approved these changes
Jan 31, 2023
_im-plugin/security.md
Outdated
| @@ -9,11 +9,11 @@ has_children: false | |||
|
|
|||
| Using the security plugin with index management lets you limit non-admin users to certain actions. For example, you might want to set up your security such that a group of users can only read ISM policies, while others can create, delete, or change policies. | |||
|
|
|||
| All index management data are protected as system indices, and only a super admin or an admin with a Transport Layer Security (TLS) certificate can access system indices. For more information, see [System indices]({{site.url}}{{site.baseurl}}/security-plugin/configuration/system-indices). | |||
| All index management data are protected as system indices, and only a super admin or an admin with a Transport Layer Security (TLS) certificate can access system indices. For more information, see [System indices]({{site.url}}{{site.baseurl}}/security/configuration/system-indices). | |||
There was a problem hiding this comment.
I'm not sure if this change from System indices to System indexes goes back to 1.3. It goes back at least to 2.2, so I'm guessing it should go further. Although the doc sites for 2.1 and earlier aren't publishing Security content.
There was a problem hiding this comment.
I'll switch it here.
_monitoring-plugins/ad/security.md
Outdated
| @@ -10,7 +10,7 @@ has_children: false | |||
|
|
|||
| You can use the security plugin with anomaly detection in OpenSearch to limit non-admin users to specific actions. For example, you might want some users to only be able to create, update, or delete detectors, while others to only view detectors. | |||
|
|
|||
| All anomaly detection indices are protected as system indices. Only a super admin user or an admin user with a TLS certificate can access system indices. For more information, see [System indices]({{site.url}}{{site.baseurl}}/security-plugin/configuration/system-indices/). | |||
| All anomaly detection indices are protected as system indices. Only a super admin user or an admin user with a TLS certificate can access system indices. For more information, see [System indices]({{site.url}}{{site.baseurl}}/security/configuration/system-indices/). | |||
There was a problem hiding this comment.
I'm not sure if this change from System indices to System indexes goes back to 1.3. It goes back at least to 2.2, so I'm guessing it should go further. Although the doc sites for 2.1 and earlier aren't publishing Security content.
| @@ -160,7 +160,7 @@ Whereas query-level monitors run your specified query and then check whether the | |||
|
|
|||
| To define a monitor visually, choose **Visual editor**. Then choose a source index, a timeframe, an aggregation (for example, `count()` or `average()`), a data filter if you want to monitor a subset of your source index, and a group-by field if you want to include an aggregation field in your query. At least one group-by field is required if you're defining a bucket-level monitor. Visual definition works well for most monitors. | |||
|
|
|||
| If you use the security plugin, you can only choose indices that you have permission to access. For details, see [Alerting security]({{site.url}}{{site.baseurl}}/security-plugin/). | |||
| If you use the Security plugin, you can only choose indexes that you have permission to access. For details, see [Alerting security]({{site.url}}{{site.baseurl}}/security/). | |||
There was a problem hiding this comment.
I think this link should be
/monitoring-plugins/alerting/security/
_search-plugins/async/security.md
Outdated
| @@ -10,21 +10,21 @@ has_children: false | |||
|
|
|||
| You can use the security plugin with asynchronous searches to limit non-admin users to specific actions. For example, you might want some users to only be able to submit or delete asynchronous searches, while you might want others to only view the results. | |||
|
|
|||
| All asynchronous search indices are protected as system indices. Only a super admin user or an admin user with a Transport Layer Security (TLS) certificate can access system indices. For more information, see [System indices]({{site.url}}{{site.baseurl}}/security-plugin/configuration/system-indices/). | |||
| All asynchronous search indices are protected as system indices. Only a super admin user or an admin user with a Transport Layer Security (TLS) certificate can access system indices. For more information, see [System indices]({{site.url}}{{site.baseurl}}/security/configuration/system-indices/). | |||
There was a problem hiding this comment.
Same as above. System indexes now, I think.
Signed-off-by: Naarcha-AWS <[email protected]>
kolchfa-aws
approved these changes
Feb 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: cwillum [email protected]
Signed-off-by: cwillum [email protected]
Signed-off-by: cwillum [email protected]
Signed-off-by: cwillum [email protected]
Signed-off-by: cwillum [email protected]
Signed-off-by: cwillum [email protected]
Signed-off-by: cwillum [email protected]
Signed-off-by: cwillum [email protected]
Signed-off-by: cwillum [email protected]
Signed-off-by: cwillum [email protected]
Signed-off-by: cwillum [email protected]
Signed-off-by: Naarcha-AWS [email protected]
Signed-off-by: cwillum [email protected]
Signed-off-by: Naarcha-AWS [email protected]
Co-authored-by: Naarcha-AWS [email protected]
(cherry picked from commit d04e88b)
Description
Describe what this change achieves.
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.