Indexes Cannot Be Backed Up

Check Whether the Account or IAM User Has the Index Backup Permissions

1. In the cluster list, click the name of the target cluster. The cluster information page is displayed.
2. Click the Cluster Snapshots tab.
3. Click the IAM agency name under IAM Agency to go to the agency details page.
4. On the Basic Information tab, check that Cloud Service is Cloud Search Service (CSS).
5. On the Permissions tab, click a permission name. On the displayed page, check that Policy Content contains the following actions:

   "obs:bucket:GetBucketLocation",
   "obs:object:GetObjectVersion",
   "obs:object:GetObject",
   "obs:object:DeleteObject",
   "obs:bucket:HeadBucket",
   "obs:bucket:GetBucketStoragePolicy",
   "obs:object:DeleteObjectVersion",
   "obs:bucket:ListBucketVersions",
   "obs:bucket:ListBucket",
   "obs:object:PutObject"

6. If the selected OBS bucket is encrypted, check that the agency's policy also contains the following KMS-related actions:

   "kms:cmk:create",
   "kms:dek:create",
   "kms:cmk:get",
   "kms:dek:decrypt",
   "kms:cmk:list"

7. If the agency has insufficient permissions, modify its permissions.
   • If a custom agency is used, you can modify the agency to add the missing actions.
   • If the default CSS agency is used, click Modify Settings on the Cluster Snapshots page, and click Automatically Create IAM Agency or One-click Authorization in the IAM Agency area to modify the agency.
8. If indexes still cannot be backed up after the agency permissions are modified, contact technical support.