By danh23072004
Recently I’ve just created a new Spaces Object Storage in sgp1 region, the problem is that I can’t find a way to configure CORS setting in this bucket. From the setting page to using awscil, s3cmd. It doesn’t seem to work.
- Here is an example command:
aws s3api put-bucket-cors --bucket edu-ai-document-storage --cors-configuration file://cors.json --endpoint-url=https://sgp1.digitaloceanspaces.com
and the errors:
aws: [ERROR]: An error occurred (NotImplemented) when calling the PutBucketCors operation: Functionality not implemented.
Additional error details: Resource: edu-ai-document-storage/
- Also, in the Setting page of my bucket, unlike this tutorial from DO: https://www.digitalocean.com/community/tutorials/configuring-digitalocean-spaces. My setting page doesn’t have a section for CORS and CDN. Maybe because I’ve choosen the Cold Storage option so that I can’t config CORS configuration?
Thank you for answering my question.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Heya, @danh23072004
Yeah, this is almost certainly because you picked Cold Storage. Cold Storage Spaces have a reduced feature set compared to regular Spaces, CORS and CDN aren’t available on them since they’re designed for infrequent access / archival, not serving content directly.
If you need CORS (which it sounds like you do if you’re building something that accesses files from a browser), you’ll need to create a regular Spaces bucket instead. The CORS settings section will show up in the UI and the S3-compatible API calls will work as expected.
Unfortunately, there’s no way to convert a Cold Storage bucket to a regular one, you’d have to create a new Space and move your objects over.
Regards
Hi there,
In addition to what’s already been mentioned, the key detail here is likely the Cold Storage option.
Cold Storage Spaces have a reduced feature set, and based on the behavior you’re seeing, it doesn’t look like CORS configuration is supported there (either via the UI or the S3 API). The NotImplemented error from put-bucket-cors usually indicates that the feature isn’t available for that bucket type rather than a misconfiguration.
The missing CORS/CDN section in the UI also points in the same direction.
If your use case involves accessing files directly from a browser (which requires CORS), you’ll likely need to use a standard (non-cold) Space. That’s where:
- the CORS settings will appear in the UI
- S3-compatible CORS commands should work as expected
I think that the usual approach is to create a new standard Space and migrate your data.
If you want to be completely sure for your specific setup, it might be worth reaching out to support as well:
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Start building today
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.
