Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
<b> I want to check daily bandwidth usage of my Object Spaces</b> Question Question
Setting up a CDN using Digitalocean Spaces Question Question

Question

403 when loading from Spaces Edge (works with Origin)

Posted June 13, 2019 3.5k views
Ubuntu 16.04CDN

I’ve used Spaces in my application for a while, using a Spaces access key to talk to the Origin endpoint.

Today I’ve enabled the built in Spaces CDN, but when I try to use the new Edge endpoint I get a 403 back from my GET request.

I use the AmazonS3 Java API and get no error message except 403 Forbidden. Using the Origin endpoint still works fine.

Am I missing something?

Add a comment
johnoloven
By:
johnoloven

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
<b> I want to check daily bandwidth usage of my Object Spaces</b> Question Question
Setting up a CDN using Digitalocean Spaces Question Question

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.

×
Submit an Answer
7 answers
nunowar June 24, 2019

I have the same problem.

Reply Report
studiomoob September 26, 2019

Me too. Any solution?

Reply Report
davidtgill June 9, 2020

Hi all, we really shouldn’t have to run a “fix” for this it should “just” work.
The frustrating thing for me is that sometimes it works and sometimes it doesn’t.
I will contact DO today about this. I will let you know what I hear.

Reply Report
raymond6a810e9b October 21, 2019

I had this issue too!

What ended up solving the issue completely was running a full purge at the space level.

Ensure CDN is enabled, just in case.

Reply Report
davidtgill June 7, 2020

Same problem.

Origin: works
CDN: does not work (403 (Forbidden))

Any solution?

Reply Report
aviAngler July 3, 2020

Has this issue been solved? Anyone know how, other than purging CDN after each upload?

Reply Report
johnoloven July 3, 2020

It seems like private resources (requiring an API token) cannot be fetched from an edge endpoint. This is the response I’ve received from support:

The CDN is independent of Spaces, it’s good for speeding up requests for users who are geographically far away from the origin. However it only houses cached files/objects and serves them to the end-user. This doesn’t work for speeding up normal API operations/requests(via api key/token) for Spaces.

Because they are seperate systems, all Space operations would need to be done at the ‘source’ or origin endpoint. Then once changes are done at origin, your public (and signed URLs) objects will cache to the CDN and be available for end-users/applications to use.

https://developers.digitalocean.com/documentation/spaces/#aws-s3-compatibility

If you made all your objects private in your Space, then when you check the Origin or CDN you would get a 403. In order to access the file via origin it would need to be signed. However there are 2 formats that can be used, 1 will cache to CDN and be available, the other will not and only work through Origin.

An example of signed URLs that WILL NOT cache to the CDN are the QuickShare links in the DigitalOcean UI. They use the following format:
<REGION>.digitaloceanspaces.com/<SPACE>

However if you do want your signed URLs to be cached, use the following format and it WILL be available via CDN:
<SPACE>.<REGION>.digitaloceanspaces.com

Reply Report

Related

Looking for something else?

Ask a new question Search for more help