Docs

Torch Object Storage

Access control

Troubleshooting access denied errors

Troubleshooting access denied errors

Symptoms

You get an "access denied" message when you try to access TOS using the console, an API, an SDK, or a tool.

What it means

Your account lacks sufficient permissions. Obtain the necessary permissions and try again. The following section contains the information you need to fix this issue.

How to fix it

Possible cause	Solution
IAM policies not yet effective	The reason for this was caching. After an IAM policy is configured, it takes one to two minutes for it to take effect. If you have confirmed that the policy is correct, wait two minutes before retrying.
Incorrect access credentials	Please verify that the access key ID (AK) and secret access key (SK), or Security Token Service (STS) token you are using are correct. For instructions on how to obtain AK/SK, see Obtaining the Access Key ID and Secret Access Key.
Incorrect permissions	Configure the correct permission policy for your scenarios. Permission errors are often caused by missing or incorrect Action or Resource elements. Action incorrectly configured or missing. Common examples: You need PutObject permission to upload objects, GetObject permission to download them, and DeleteObject permission to delete them. To manage TOS resources via TOS Browser, you need a set of permissions, including ListBuckets. For more information, see Allowing access to TOS resources via TOS Browser. Viewing Console overview data requires Cloud Monitor permissions. Resource incorrectly configured or missing. Common examples: Permissions were granted only for the bucket and not for the objects within it. Permissions were granted for some, but not all, objects in the bucket.
Others	If none of the above solutions work, submit a ticket to contact our technical team.

Last updated: 2026.01.04 17:36:52