Object Storage

Modify Object Storage Bucket Access

post
https://api.linode.com/v4beta/object-storage/buckets/{clusterId}/{bucket}/access
BETA

Allows changing basic Cross-origin Resource Sharing (CORS) and Access Control Level (ACL) settings. Only allows enabling/disabling CORS for all origins, and/or setting canned ACLs. For more fine-grained control of both systems, please use the S3 API directly.

This endpoint is available for convenience. It is recommended that instead you use the more more fully-featured S3 API directly.

Beta: This endpoint is in beta. Please make sure to prepend all requests with /v4beta instead of /v4, and be aware that this endpoint may receive breaking updates in the future. This notice will be removed when this endpoint is out of beta.

Authorizations

Personal Access Token
OAuth: ( object_storage:read_write)

Path Parameters

clusterId
Required
string

The ID of the cluster this bucket exists in.

bucket
Required
string

The bucket name.

Request Body Schema

acl
string
Enum: "private""public-read""authenticated-read"

The Access Control Level of the bucket, as a canned ACL string. For more fine-grained control of ACLs, use the S3 API directly.

cors_enabled
boolean

If true, the bucket will be created with CORS enabled for all origins. For more fine-grained controls of CORS, use the S3 API directly.

Request Samples

curl -H "Content-Type: application/json" \
 -H "Authorization: Bearer $TOKEN" \
  -X POST -d '{
      "cors_enabled": true,
      "acl": "private"
    }' \
  https://api.linode.com/v4beta/object-storage/buckets/us-east-1/example-bucket/access

Response Samples

{}

Responses

200: Access controls updated.

default: Error

errors
array of objects
reason
string

What happened to cause this error. In most cases, this can be fixed immediately by changing the data you sent in the request, but in some cases you will be instructed to open a Support Ticket or perform some other action before you can complete the request successfully.

field
string

The field in the request that caused this error. This may be a path, separated by periods in the case of nested fields. In some cases this may come back as "null" if the error is not specific to any single element of the request.