Docs

Torch Object Storage

Authorizing IAM users of the current account

Allowing an IAM user to upload and download objects in a bucket

This topic explains how to allow an IAM user of the current account to upload and download objects to and from a bucket.

Scenario

Principal: IAM user iamuser of account 210015****.

Resource: Bucket bucketname.

Actions: GetObject and PutObject.

Notes

If a configured permission does not take effect, we recommend that you retry later, as there is a delay.

Steps

In the left navigation pane, click Buckets.

In the top menu bar, select the project of the bucket you want to manage.

On the Buckets page, click the name of the bucket.

In the left navigation pane, select Permissions > Bucket policies.

Edit the policy using your preferred view.

Visual view

JSON view

Click Create policy.

On the Create Bucket Authorization Policy page, select Custom Policy and click Next.

Configure the following parameters.

Category	Parameter	Description
Basic configuration	Policy configuration method	Use the default option, i.e., Visual view.
Basic configuration		Policy name	Enter a name for the policy. The policy name must be unique within a bucket.
Effect	Effect	Select the effect of the policy. In this example, use the default value. Allow (Default): Allows the matched requests. Deny: Denies the matched requests.
Authorized user	Authorized user	Use the default option, i.e., Specified account.
Authorized user		Other accounts	Select Current main account. Then, click Add Field and select the IAM user you want to authorize from the drop-down menu under Sub account name. In this example, we use iamuser.
Resource	Resource scope	Select Objects in bucket. The policy will then take effect on the objects in the bucket. You can configure object actions in the Action section. All objects: The policy takes effect on all objects in the bucket. Specified object(s): The policy takes effect on the specified object(s) in the bucket. After selecting this option, enter the Resource Path to specify the object you want to share. Click Add Field to specify multiple objects. Follow these guidelines when specifying a resource: Resource paths can contain Chinese characters, letters, numbers, and common symbols. Resource paths can point to the entire bucket, an object, or a directory. When granting permissions to a directory, use a wildcard () at the end, for example, test/. Resource paths cannot start with a forward slash (/) or backslash (\). Consecutive forward slashes (/) are not allowed. .. cannot be used as a directory name.
Action	General Action	It is optional. You can also select one or more actions you want to authorize based on your needs. For more information, see Supported actions.
			Bucket Action
		Object Action	Select GetObject and PutObject. You can also select other actions as needed. For more information, see Object actions.
		Operational strategy	Use the default option, i.e., Include the above actions. This option allows users to perform the specified actions.
Condition (Optional)	-	Click the Add Field icon and set the condition and value. For more information, see Conditions.

Save your settings by clicking Next.

After verifying the details, click Create.

Then, you will see the bucket policy that you just created in the policy list.

Next steps

Once the bucket policy has been created, the IAM user can upload and download objects to and from the bucket via an API or SDK.

To upload and download via the console, the IAM user must be granted permission via an IAM policy to perform the following actions: ListBuckets, ListBucket and HeadBucket.

To upload and download via TOS Browser, the IAM user must be granted ListBucket permission via a bucket policy.

For more information about actions allowed by IAM policies, see Supported actions.

tip

Despite having the aforementioned permissions, the IAM user may still encounter errors such as Request failed with status code 403 or Insufficient permissions when attempting to download or upload via the console. This occurs due to missing permissions for other APIs. These errors do not affect existing permissions and can be disregarded.

Last updated: 2026.08.14 16:23:30