As per the tutorial at : https://www.digitalocean.com/community/tutorials/how-to-set-up-a-scalable-django-app-with-digitalocean-managed-databases-and-spaces
The guidance to setup CDN access via Spaces from the above is:
AWS_S3_ENDPOINT_URL = ‘spaces_endpoint_URL’ AWS_S3_CUSTOM_DOMAIN = ‘spaces_edge_endpoint_URL’
replace the spaces_edge_endpoint_URL with the Edge endpoint you just noted down, truncating the https:// prefix. For example, if the Edge endpoint URL is https://example.sfo2.cdn.digitaloceanspaces.com, AWS_S3_CUSTOM_DOMAIN should be set to example.sfo2.cdn.digitaloceanspaces.com.
With the above config, the edge path is not used - instead the path links only to the standard spaces endpoint and not the CDN endpoint.
Can you please advise if there is any further guidance on this issue? Thanks!
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!
Accepted Answer
Just a quick note to say that this was resolved. Reset the spaces and then seemed to work. thanks
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 SMBs
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.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.