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?
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.
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.
Same problem.
Origin: works CDN: does not work (403 (Forbidden))
Any solution?
Me too. Any solution?
I have the same problem.
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:
Has this issue been solved? Anyone know how, other than purging CDN after each upload?
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.