Thanks for flagging this issue for us. It looks like the input validation in our control panel is a bit too strict here. As a work-around until this experience is improved, you can create CORs configurations for Spaces using the API for origins without a TLD. For example, using
s3cmd you can run:
- s3cmd setcors cors.xml s3://example-space
Where the contents of the
cors.xml file contains your CORs configurations in XML format. For example:
s3cmd is a popular cross-platform command-line tool for managing S3 and S3-compatible object stores. This guide provides a quick reference to commands that are useful for managing DigitalOcean Spaces.