Akave O3
CORS Configuration
Setting CORS Policies

Setting CORS Policies

Cross-Origin Resource Sharing (CORS) policies in Akave O3 allow your bucket to be accessed by web apps from other origins. This is essential for use cases involving frontend apps, embedded content, or external data consumers.

Akave O3 supports full S3-compatible CORS configuration via both aws s3api and aws s3.

Put a CORS Policy

Using aws s3api:

aws s3api put-bucket-cors \
  --bucket my-akave-bucket \
  --cors-configuration file://cors.json \
  --endpoint-url https://o3-rc1.akave.xyz

Using aws s3:

Not supported for CORS. Use s3api for CORS operations.

View Current CORS Policy

Using aws s3api:

aws s3api get-bucket-cors \
  --bucket my-akave-bucket \
  --endpoint-url https://o3-rc1.akave.xyz

Delete Existing CORS Policy

Using aws s3api:

aws s3api delete-bucket-cors \
  --bucket my-akave-bucket \
  --endpoint-url https://o3-rc1.akave.xyz
ℹ️
  • CORS applies at the bucket level.
  • The configuration must be passed as a JSON file.
  • Improper CORS configuration may block access to your objects from browsers.

To create a valid configuration file, see the next section on CORS examples.

Last updated on
CORS Examples