Put Bucket Policy

Last updated:2021-09-23 15:02:41


This PUT interface can add a BucketPolicy to a bucket.
If an interface already has a BucketPolicy, the newly added BucketPolicy will completely replace the old one.
If you want to use this interface, you need to be the owner of this Bucket.
If the interface call succeeds, 204 will be returned. If the call fails, the error code and specific error information will be returned.



PUT /?policy HTTP/1.1
Host: {BucketName}.{endpoint}
Date: {date}
Authorization: {SignatureValue}
Policy written in JSON


Request parameters

The interface does not use request parameters.

Request header

This interface only uses common request headers. For more information, please click Public request headers.

Request content

A JSON string describing the bucket policy.

Response header

This interface can use all common response headers. For more information, please click Public response headers.

Response content

The interface does not return the corresponding content.

Special errors

The interface does not return any special errors.


Request example

PUT /?policy HTTP/1.1
Host: ks3-example.ks3-cn-beijing.ksyuncs.com
Content-Length: 225
Authorization: authorization string
Content-Md5: 8evRehlmPHkf+VuSe8k6Rg==
Date: Tue, 19 Jul 2016 09:12:54 GMT


Response example

HTTP/1.1 204 No Content
Content-Length: 0
Connection: keep-alive
Date: Tue, 19 Jul 2016 09:14:23 GMT
Server: Tengine
X-Application-Context: application
X-Kss-Request-Id: 54a47bda18ac4e6e91de369add54218e

Did you find the above information helpful?

Mostly Unhelpful
A little helpful
Very helpful

What might be the problems?

Unclear or awkward
Redundant or clumsy
Lack of context for the complex system or functionality

More suggestions


Please give us your feedback.


Thank you for your feedback.