DigitalOcean home
  • Droplets
  • Spaces
  • Kubernetes
  • Tools & Integrations
  • One-click Apps
  • API Documentation
  • Community
  • Tutorials
  • Q&A
  • Projects
  • Meetups
  • Customers
  • Pricing
  • Docs
  • Support
  • DigitalOcean home
  • Products
    • Droplets

      Scalable compute services.

    • Spaces

      Simple object storage.

    • Kubernetes

      Run managed Kubernetes clusters.

    • Tools & Integrations

      Automate your infrastructure.

    • One-click Apps

      Deploy pre-built applications.

    • API Documentation
  • Customers
  • Community
    • Community Overview

      Connect, share and learn

    • Tutorials

      DevOps and development guides

    • Questions & Answers

      Development and systems Q&A

    • Projects

      Community-built integrations

    Get Involved
    Write for DOnations
    Join us at a Meetup
    Featured Post
    An Introduction to Kubernetes

    by Justin Ellingwood

  • Pricing
  • Docs
  • Support
    • Documentation

    • Contact Support

    • Network Status

  • Home /
  • DO-I-2914 /
  • New idea
56 Vote

Signed URL on Spaces CDN

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. 

  • Guest
  • Oct 19 2018
  • Future consideration
Object Storage (Spaces)
  • Comments (14)
  • Votes (56)
  • Attach files
  • Joel Hernandez commented
    10 Oct, 2020 05:47pm

    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

  • Anonymous commented
    17 Sep, 2020 09:15pm

    DigitalOcean Spaces is not a viable alternative of AWS S3.

    ×

    Attachments Open full size

  • Eric Demers commented
    4 Sep, 2020 03:10pm

    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

  • Eric Demers commented
    4 Sep, 2020 02:16pm

    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

  • Nick Willever commented
    16 Jul, 2020 07:41am

    This would be great to have.

    ×

    Attachments Open full size

  • Florian Ernst commented
    10 Jun, 2020 07:47pm

    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

  • Mehul Mohan commented
    3 May, 2020 09:41pm

    Any update on this?

    ×

    Attachments Open full size

  • Sebastian Kummer commented
    25 Apr, 2020 06:50pm

    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

  • Arvind Mittal commented
    15 Apr, 2020 07:57am

    yes, else no use and benefit of CDN

    ×

    Attachments Open full size

  • Samuel Horwitz commented
    2 Oct, 2019 12:21pm

    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

  • Jason Cooke commented
    12 Jul, 2019 04:23am

    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

  • Mike commented
    11 Jun, 2019 10:18am

    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

  • James Homer commented
    6 Jun, 2019 10:51am

    This is a dealbreaker for us!

    ×

    Attachments Open full size

  • Thomas F commented
    19 Dec, 2018 01:24pm

    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

Log in / Sign up

Identify yourself with your email address

Subscribe

You won't be notified about changes to this idea.

Related ideas

DigitalOcean home

© 2018 DigitalOcean, LLC. All rights reserved.
Proudly made in NY

  • Twitter
  • Facebook
  • Instagram
  • YouTube
  • LinkedIn
  • Glassdoor
Company
About
Leadership
Blog
Careers
Partner Network
Referral Program
Events
Press
Legal & Security
Products
Droplets
Spaces
Kubernetes
Tools & Integrations
One-click Apps
API
Pricing
Documentation
Release Notes
Community
Tutorials
Meetups
Q&A
Write for DOnations
Droplets for Demos
Hatch
Shop Swag
Research Program
Currents Research
Open Source
Support
Contact Support
FAQ
Network Status