Public Access Block

Control whether objects in a Stook Bucket can be accessed without credentials and prevent the bucket from being made public.

Public Access Block provides two controls for managing public access:

Public access allows objects in the Stook Bucket to be read without credentials.
Block public access prevents the Stook Bucket from being made public.

These settings cannot be enabled at the same time.

A Stook Bucket must have Public access enabled before it can be connected to a CDN Resource. When you create a CDN Resource using a Stook Bucket in the Medianova Control Panel, public access is enabled automatically for that bucket.

For complete request parameters, response schemas, and error responses, see Bucket Settings API.

How Public Access Works

When Public access is enabled, anyone who knows an object's URL can retrieve the object without an access key or signed request.

https://<ENDPOINT_URL>/<BUCKET_NAME>/<OBJECT_KEY>

Public access applies only to reading individual objects:

Objects can be downloaded without credentials.
Bucket contents cannot be listed without credentials.
Uploading, modifying, and deleting objects still require credentials with the appropriate permissions.

Use public access for content intended to be publicly retrievable, including website assets and media delivered through a CDN Resource.

How Block Public Access Works

Block public access prevents a Stook Bucket from being made public. Use this setting for buckets that must remain private, such as buckets containing backups or internal data.

While Block public access is enabled, the Stook Bucket cannot be made public through:

Medianova Control Panel
Stook API
S3-compatible clients

Public access and Block public access are mutually exclusive:

To enable Block public access, disable Public access first.
To enable Public access, disable Block public access first.

Configure Public Access Block

Open the Stook Bucket

In the Medianova Control Panel, select Stook Object Storage → Buckets, then select the Stook Bucket you want to configure.

Open Public Access Block

On the Bucket configuration page, select Public access block.

Configure public access

Enable or disable Public access and Block public access as required.

The two settings cannot be enabled at the same time.

Save the configuration

Select Save Changes.

Configuration Fields

Field

Description

Default

Public access

Allows objects in the Stook Bucket to be read without credentials.

Off

Block public access

Prevents the Stook Bucket from being made public.

Off

Public Access and CDN Resources

A Stook Bucket connected to a CDN Resource must remain public because the CDN Resource retrieves objects without credentials.

When a Stook Bucket is connected to a CDN Resource:

Public access cannot be disabled.
The Stook Bucket cannot be deleted.

To make the Stook Bucket private, first remove it from the CDN Resource, then disable Public access.

A Stook Bucket with Block public access enabled cannot be connected to a CDN Resource. Disable Block public access before connecting the bucket.

Configure Public Access with the API

Public access and Block public access use different API endpoints.

Configure Public Access

Use the bucket update endpoint to enable public access:

PUT /api/v2/stook/{organization_uuid}/bucket/{bucket_uuid}

Send:

{
  "anonymous_status": true
}

This request enables unauthenticated read access to individual objects in the Stook Bucket. The current state is returned as anonymous_status when you retrieve the bucket.

Configure Block Public Access

Use the bucket settings endpoint:

PATCH /api/v2/stook/{organization_uuid}/bucket/{bucket_uuid}/settings

Send:

{
  "block_public_access": true
}

This request prevents the Stook Bucket from being made public.

Troubleshooting