Changed transform to rollup

_clients/go.md

@@ -1,145 +0,0 @@
----
-layout: default
-title: Go client
-nav_order: 80
----
-
-# Go client
-
-The OpenSearch Go client lets you connect your Go application with the data in your OpenSearch cluster.
-
-
-## Setup
-
-If you're creating a new project:
-
-```go
-go mod init
-```
-
-To add the client to your project, import it like any other module:
-
-```go
-go get github.com/opensearch-project/opensearch-go
-```
-
-## Sample code
-
-This sample code creates a client, adds an index with non-default settings, inserts a document, searches for the document, deletes the document, and finally deletes the index:
-
-```go
-package main
-import (
-    "os"
-    "context"
-    "crypto/tls"
-    "fmt"
-    opensearch "github.com/opensearch-project/opensearch-go"
-    opensearchapi "github.com/opensearch-project/opensearch-go/opensearchapi"
-    "net/http"
-    "strings"
-)
-const IndexName = "go-test-index1"
-func main() {
-    // Initialize the client with SSL/TLS enabled.
-    client, err := opensearch.NewClient(opensearch.Config{
-        Transport: &http.Transport{
-            TLSClientConfig: &tls.Config{InsecureSkipVerify: true},
-        },
-        Addresses: []string{"https://localhost:9200"},
-        Username:  "admin", // For testing only. Don't store credentials in code.
-        Password:  "admin",
-    })
-    if err != nil {
-        fmt.Println("cannot initialize", err)
-        os.Exit(1)
-    }
-
-    // Print OpenSearch version information on console.
-    fmt.Println(client.Info())
-
-    // Define index mapping.
-    mapping := strings.NewReader(`{
-     'settings': {
-       'index': {
-            'number_of_shards': 4
-            }
-          }
-     }`)
-
-    // Create an index with non-default settings.
-    res := opensearchapi.CreateRequest{
-        Index: IndexName,
-        Body:  mapping,
-    }
-    fmt.Println("creating index", res)
-
-    // Add a document to the index.
-    document := strings.NewReader(`{
-        "title": "Moneyball",
-        "director": "Bennett Miller",
-        "year": "2011"
-    }`)
-
-    docId := "1"
-    req := opensearchapi.IndexRequest{
-        Index:      IndexName,
-        DocumentID: docId,
-        Body:       document,
-    }
-    insertResponse, err := req.Do(context.Background(), client)
-    if err != nil {
-        fmt.Println("failed to insert document ", err)
-        os.Exit(1)
-    }
-    fmt.Println(insertResponse)
-
-    // Search for the document.
-    content := strings.NewReader(`{
-       "size": 5,
-       "query": {
-           "multi_match": {
-           "query": "miller",
-           "fields": ["title^2", "director"]
-           }
-      }
-    }`)
-
-    search := opensearchapi.SearchRequest{
-        Body: content,
-    }
-
-    searchResponse, err := search.Do(context.Background(), client)
-    if err != nil {
-        fmt.Println("failed to search document ", err)
-        os.Exit(1)
-    }
-    fmt.Println(searchResponse)
-
-    // Delete the document.
-    delete := opensearchapi.DeleteRequest{
-        Index:      IndexName,
-        DocumentID: docId,
-    }
-
-    deleteResponse, err := delete.Do(context.Background(), client)
-    if err != nil {
-        fmt.Println("failed to delete document ", err)
-        os.Exit(1)
-    }
-    fmt.Println("deleting document")
-    fmt.Println(deleteResponse)
-
-    // Delete previously created index.
-    deleteIndex := opensearchapi.IndicesDeleteRequest{
-        Index: []string{IndexName},
-    }
-
-    deleteIndexResponse, err := deleteIndex.Do(context.Background(), client)
-    if err != nil {
-        fmt.Println("failed to delete index ", err)
-        os.Exit(1)
-    }
-    fmt.Println("deleting index", deleteIndexResponse)
-}
-```

_clients/java-rest-high-level.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Java high-level REST client
-nav_order: 60
+nav_order: 97
 ---
 
 # Java high-level REST client

_im-plugin/ism/api.md

@@ -2,7 +2,7 @@
 layout: default
 title: ISM API
 parent: Index State Management
-nav_order: 5
+nav_order: 20
 ---
 
 # ISM API

_im-plugin/refresh-analyzer/index.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Refresh search analyzer
-nav_order: 40
+nav_order: 50
 has_children: false
 redirect_from: /im-plugin/refresh-analyzer/
 has_toc: false

_im-plugin/security.md

@@ -0,0 +1,41 @@
+---
+layout: default
+title: Index management security
+nav_order: 40
+has_children: false
+---
+
+# Index management security
+
+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).
+
+## Basic permissions
+
+The security plugin comes with one role that offers full access to index management: `index_management_full_access`. For a description of the role's permissions, see [Predefined roles]({{site.url}}{{site.baseurl}}/security-plugin/access-control/users-roles#predefined-roles).
+
+With security enabled, users not only need the correct index management permissions, but they also need permissions to execute actions to involved indices. For example, if a user wants to use the REST API to attach a policy that executes a rollup job to an index named `system-logs`, they would need the permissions to attach a policy and execute a rollup job, as well as access to `system-logs`.
+
+Finally, with the exceptions of Create Policy, Get Policy, and Delete Policy, users also need the `indices:admin/opensearch/ism/managedindex` permission to execute [ISM APIs]({{site.url}}{{site.baseurl}}/im-plugin/ism/api).
+
+## (Advanced) Limit access by backend role
+
+You can use backend roles to configure fine-grained access to index management policies and actions. For example, users of different departments in an organization might view different policies depending on what roles and permissions they are assigned.
+
+First, ensure your users have the appropriate [backend roles]({{site.url}}{{site.baseurl}}/security-plugin/access-control/index/). Backend roles usually come from an [LDAP server]({{site.url}}{{site.baseurl}}/security-plugin/configuration/ldap/) or [SAML provider]({{site.url}}{{site.baseurl}}/security-plugin/configuration/saml/). However, if you use the internal user database, you can use the REST API to [add them manually]({{site.url}}{{site.baseurl}}/security-plugin/access-control/api#create-user).
+
+Use the REST API to enable the following setting:
+
+```json
+PUT _cluster/settings
+{
+  "transient": {
+    "plugins.index_management.filter_by_backend_roles": "true"
+  }
+}
+```
+
+With security enabled, only users who share at least one backend role can see and execute the policies and actions relevant to their roles.
+
+For example, consider a scenario with three users: `John` and `Jill`, who have the backend role `helpdesk_staff`, and `Jane`, who has the backend role `phone_operator`. `John` wants to create a policy that performs a rollup job on an index named `airline_data`, so `John` would need a backend role that has permissions to access that index, create relevant policies, and execute relevant actions, and `Jill` would be able to access the same index, policy, and job. However, `Jane` cannot access or edit those resources or actions.

_security-plugin/access-control/users-roles.md

@@ -121,6 +121,7 @@ Role | Description
 `reports_full_access` | Grants full permissions to reports.
 `asynchronous_search_full_access` | Grants full permissions to all asynchronous search actions.
 `asynchronous_search_read_access` | Grants permissions to view asynchronous searches, but not to submit, modify, or delete async searches.
+`index_management_full_access` | Grants full permissions to all index management actions, including ISM, transforms, and rollups.
 
 
 For more detailed summaries of the permissions for each role, reference their action groups against the descriptions in [Default action groups]({{site.url}}{{site.baseurl}}/security-plugin/access-control/default-action-groups/).