You need to enable JavaScript to run this app.
Torch Object Storage

Torch Object Storage

Copy page
Download PDF
Authorizing IAM users of the current account
Granting an IAM user access to RenameObject
Copy page
Download PDF
Granting an IAM user access to RenameObject
This topic explains how to allow an IAM user of the current account to perform the RenameObject operation.​
Scenario​
  • Principal: IAM user iamuser of account 210015****.​
  • Resource: Bucket bucketname.​
  • Actions: PutBucketRename, GetBucketRename, DeleteBucketRename, PutObject, and RenameObject.​
tip​
The RenameObject operation involves writing the renamed object to TOS. Therefore, one must have both RenameObject and PutObject permissions to perform this operation.​
Recommended authorization method​
We recommend using a bucket policy in this scenario. For more information about bucket policies, see Overview.​
Notes​
If a configured permission does not take effect, we recommend that you retry later, as there is a delay.​
Steps​
  1. Log in to the TOS console.​
  1. In the left navigation pane, click Buckets. In the Buckets list, click the bucket you want to manage.​
  1. In the left navigation pane, select Permissions > Bucket policies.​
  1. On the Bucket policies page, click the JSON view tab.​
  1. Click Edit. Then, copy the following content into the text box, and click Save.​
  • ​
    {​
    "Statement": [​
    {​
    "Sid": "Bucket Read-Only-d0e6",​
    "Effect": "Allow",​
    "Principal": [​
    "210015****/iamuser"​
    ],​
    "Action": [​
    "tos:PutBucketRename",​
    "tos:GetBucketRename",​
    "tos:DeleteBucketRename",​
    "tos:PutObject",​
    "tos:RenameObject"​
    ],​
    "Resource": [​
    "trn:tos:::bucketname",​
    "trn:tos:::bucketname/*"​
    ]​
    }​
    ]​
    }​
    ​
Next steps​
Once the bucket policy has been created, the IAM user can use the PutBucketRename API to enable RenameObject, and rename objects in the bucket via the RenameObject API. For more information, see PutBucketRename and RenameObject.​
Last updated: 2026.01.04 17:36:52