While using CDN with Spaces, allow the possibility of creating signed URL for CDN endpoints. Currently, if we set the CDN on a private bucket, the content can be accessed from the CDN endpoint by knowing the filename.Â
Not only would it be great to have, it's a must. The lack of signed URLs on the CDN will most likely cause me to leave Spaces at some point for a different service. My users will be accessing private data from all over the world, so CDN is very important.
Spaces looks like they are abandonned by the DO team. No private signed URLs on CDN, no notification feature... Spaces isn't that great at its current state.
This is becoming a dealbreaker, as connections are very slow (less than 100KB/s). As I need presigned URLs the CDN is out of the picture. Please implement that.
Yes this would be very useful. I currently am not at the scale where this is a dealbreaker, but it is a theoretical limitation I'll face if I'm lucky enough to get a large enough user base.
I would like to see this feature as well. The docs say "use a CDN" if you run into the rate limit (200 requests per second). But signed URLs are not compatible with the DO CDN. So basically that does mean you are unable to scale private URLs on DO spaces.
I know we would love to have this. We work on an older game and we use the CDN to deliver content patches and install images of the game. However, we would like to be able to lock these down to authenticated users.Â
Â
Currently this causes us to have to split our spaces up into a non-CDN space for the internal stuff that requires a signed URL, and a CDN space for the public stuff where having one would be convenient but not possible currently. It would be nice to be able to combine them into one space, and have our internal stuff on the CDN as well. Though even if we don't combine them, for separation reasons, it'd still be nice to be able to put them on the CDN with signed URLs.
This is a huge show-stopper.
We were considering migrating from AWS to DigitalOcean given the latest App Service but without this available, not a chance.
Its tenths of thousands of dollars in business lost.
Attachments Open full size
DigitalOcean Spaces is not a viable alternative of AWS S3.
Attachments Open full size
I just figured out that you can change the URL after pre-signing to point to the CDN, and it will work.
Attachments Open full size
Not only would it be great to have, it's a must. The lack of signed URLs on the CDN will most likely cause me to leave Spaces at some point for a different service. My users will be accessing private data from all over the world, so CDN is very important.
Attachments Open full size
This would be great to have.
Attachments Open full size
Spaces looks like they are abandonned by the DO team. No private signed URLs on CDN, no notification feature... Spaces isn't that great at its current state.
Attachments Open full size
Any update on this?
Attachments Open full size
This is becoming a dealbreaker, as connections are very slow (less than 100KB/s). As I need presigned URLs the CDN is out of the picture. Please implement that.
Attachments Open full size
yes, else no use and benefit of CDN
Attachments Open full size
Yes this would be very useful. I currently am not at the scale where this is a dealbreaker, but it is a theoretical limitation I'll face if I'm lucky enough to get a large enough user base.
Attachments Open full size
Due to the rate limits imposed by DO Spaces, I opted for the CDN, with a custom subdomain (loving this feature btw).
However, I use presigned urls for my private bucket, thus rendering the CDN useless...
Attachments Open full size
I would like to see this feature as well. The docs say "use a CDN" if you run into the rate limit (200 requests per second). But signed URLs are not compatible with the DO CDN. So basically that does mean you are unable to scale private URLs on DO spaces.
Attachments Open full size
This is a dealbreaker for us!
Attachments Open full size
I know we would love to have this. We work on an older game and we use the CDN to deliver content patches and install images of the game. However, we would like to be able to lock these down to authenticated users.Â
Â
Currently this causes us to have to split our spaces up into a non-CDN space for the internal stuff that requires a signed URL, and a CDN space for the public stuff where having one would be convenient but not possible currently. It would be nice to be able to combine them into one space, and have our internal stuff on the CDN as well. Though even if we don't combine them, for separation reasons, it'd still be nice to be able to put them on the CDN with signed URLs.
Attachments Open full size