DO Ideas 2

Allow custom domain alias for Spaces bucket

  • Jacob Hands
  • Sep 11 2018
  • Planned
  • Sep 11, 2018

    Admin Response

    Sorry for the delay in updating this. It is being worked on by the team and we expect a Q2 release for this.
  • Attach files
  • Findmate commented
    September 11, 2018 15:55

    This is badly needed. Saw they released SFO update for spaces, but got no reply asking about custom domains

  • Alex commented
    September 11, 2018 15:55

    This will be perfect! Waiting for it!

  • Ian O'Brien commented
    September 11, 2018 15:55

    Would love this implemented

  • Olaf Lederer commented
    September 11, 2018 15:55

    Here the same, I'm looking for this feature to use my own domain name. A 3rd party domain makes no sense.

  • Anonymous commented
    September 11, 2018 15:55

    Any updates? Just signed up and this is a required feature for me.

  • Alisson Patrick commented
    September 11, 2018 15:55

    need this asap!

  • Anonymous commented
    September 11, 2018 15:55

    Any updates?

  • Anonymous commented
    September 11, 2018 15:55

    We are waiting for this from almost 1 year..please made it available soon.. thanq

  • Luan commented
    September 11, 2018 15:55

    need that too

  • Paul Go commented
    September 11, 2018 15:55

    FWIW, this is a response I got from a DO support staff member:

    "Checking internally, I can confirm that Static-sites-as-a-Service products will support SSL and CDN with custom domains. However, I am sorry but I don't have ETA for the same."

  • Jin commented
    September 11, 2018 15:55

    Any updates?

  • Anonymous commented
    September 11, 2018 15:55

    Q2 is over ... my dear DO Team ... pls, give an exact date of release ...

  • Mohamad Tawakol commented
    September 11, 2018 15:55

    One more to the pile of we need this please.

  • Josh Hubi commented
    September 11, 2018 15:55

    Please, we need an update on this.

  • Sander commented
    September 11, 2018 15:55

    Waiting for proper ETA as well :)

  • Anonymous commented
    September 11, 2018 15:55

    second quarter already passed when's this feature going to be implemented?

  • Anonymous commented
    September 11, 2018 15:55

    Looking forward to seeing this be implemented!

  • David Matrick commented
    September 11, 2018 15:55

    would love a proper eta on this

  • Anonymous commented
    September 11, 2018 15:55

    any updates

  • Gin ! commented
    September 11, 2018 15:55

    has this been implemented yet?

  • Paul Go commented
    September 11, 2018 15:55

    FWIW: Just got this comment from support:

    "Checking internally, I can confirm that Static-sites-as-a-Service products will support SSL and CDN with custom domains. However, I am sorry but I don't have ETA for the same."

  • Anonymous commented
    September 11, 2018 15:55

    is there an update?

  • David D commented
    September 11, 2018 15:55

    Would REALLY love an update on this too.

  • Sarah Richardson commented
    September 11, 2018 15:55

    Is there any ETA for this? I would love to keep using Spaces for my assets and not have to think about using Amazon S3 with Cloudflare or the like. The Spaces platform is much more user friendly than S3 and I'm sure with time (and improvement) it will be a cheaper and more effective than S3 itself.

  • Anonymous commented
    September 11, 2018 15:55

    Already Q2 but still not release so sad to long waiting >.< Please more fasterrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr

  • Anonymous commented
    September 11, 2018 15:55

    really needed...

  • Aboozar Ghaffari commented
    September 11, 2018 15:55

    +1

  • Jason commented
    September 11, 2018 15:55

    Going to add one more "please do this soon" to the pile.

  • Gavin commented
    September 11, 2018 15:55

    @DO - Any timelines on this yet?

  • Nick Meyvis commented
    September 11, 2018 15:55

    how was this not implemented at launch...

  • Anonymous commented
    September 11, 2018 15:55

    please implement it soon. We need it

  • Anonymous commented
    September 11, 2018 15:55

    Any updates about CNAME. Spaces without CNAME is useless

  • Ben Neale commented
    September 11, 2018 15:55

    Will consider switching from S3 to DO Spaces for assets (as my websites are already on DO VM's), as soon as CNAMEs are allowed - custom domains are a deal breaker for me. Glad to hear it's in the works. Hope it's launched soon.

    Ben

  • Damar Pramudito Nurjati commented
    September 11, 2018 15:55

    please support custom domain with HTTPS :D
    waiting for SGP region :)

  • Christopher commented
    September 11, 2018 15:55

    How far into Q2 are you anticipating? It's almost halfway through Q2 now (03MAY2018). Just checking

  • Edgar commented
    September 11, 2018 15:55

    :D

  • Parker Charles commented
    September 11, 2018 15:55

    Looking forward to seeing this be implemented!

  • Hector Castillo commented
    September 11, 2018 15:55

    Definitivamente en cuanto tengan esta función mudo todo

  • Jared Henderson commented
    September 11, 2018 15:55

    Glad to hear it's being worked on. If this doesn't come relatively soon, I'd probably switch to S3, so it's definitely important to me.

  • James Jeffery commented
    September 11, 2018 15:55

    The thing people don't realise is Digital Ocean's spaces feature is built on top of s3. That's why they can not offer domain name support.

  • Anonymous commented
    September 11, 2018 15:55

    Pretty much pointless considering the unreliability issues of Spaces

  • Ben Pearson commented
    September 11, 2018 15:55

    I am ready right now to transfer complete control of my website to Digital Ocean, all I need is this feature to be allowed. I really want to do the switch to Digital Ocean, but only if they can set up spaces as a website. Otherwise, I'm probably not going to be able to do so. Please work on this ASAP!

  • Eric Fairon commented
    September 11, 2018 15:55

    CNAME is a must have for us to move from S3 to DO

  • Anonymous commented
    September 11, 2018 15:55

    I need it urgently!!

  • Tom Thorogood commented
    September 11, 2018 15:55

    Is it possible to get confirmation if this feature will be implemented or not? If so, an ETA would be great. Thanks.

  • Suhaib Roomy commented
    September 11, 2018 15:55

    is there any ETA on this?

  • mamank commented
    September 11, 2018 15:55

    can't wait

  • Anonymous commented
    September 11, 2018 15:55

    +1

  • tiancheng91 commented
    September 11, 2018 15:55

    +1

  • benrebia mohamed commented
    September 11, 2018 15:55

    update

  • Techtunes Inc. commented
    September 11, 2018 15:55

    Any update?

  • Danilo Polani commented
    September 11, 2018 15:55

    +1, any update?

  • Anonymous commented
    September 11, 2018 15:55

    DO completed forget all of us. Almost 6 months and no news about this.

  • Anonymous commented
    September 11, 2018 15:55

    This would be a great feature!

  • Allan Batista commented
    September 11, 2018 15:55

    this is a very important feature, we are wating for this. :)

  • Travis Bernard commented
    September 11, 2018 15:55

    I am scheduled to be buried alive by South American howler monkeys on March 31st, 2018 unless you guys add CNAME support to DigitalOcean Spaces. They are outside my window, staring at me. They are holding signs. The signs say "LEAVE AMAZON" and "CUSTOM DOMAINS, OR COVERED IN DIRT" and "WE WILL BURY YOU I GUESS." I don't know what to do.

  • Anonymous commented
    September 11, 2018 15:55

    THIS IS A MUST!!

  • Raymond Angel commented
    September 11, 2018 15:55

    This is an easy move once we have cname support from Amazon for me!

  • Anonymous commented
    September 11, 2018 15:55

    A lot of users are waiting for this feature and now it is getting annoying. Someone from DO support said in one of their blog posts (comments) that they will introduce this feature before the end of 2017. But looks like they don't care what customers need, instead, they are busy in launching new products leaving their old products incomplete and buggy!! This doesn't make sense.

  • Anonymous commented
    September 11, 2018 15:55

    +100

  • Tornado commented
    September 11, 2018 15:55

    +1

  • Ian McQueen commented
    September 11, 2018 15:55

    I need this to migrate from S3 to Spaces. 100%. Yes, please!

  • Douglas Miranda commented
    September 11, 2018 15:55

    I hope it comes with the possibility of using cloudflare too.

    https://www.digitalocean.com/community/questions/hiding-spaces-behind-cloudflare?comment=66151

  • Rehmat commented
    September 11, 2018 15:55

    Desperately need this feature.

  • Mark Steadman commented
    September 11, 2018 15:55

    I've got several tens of thousands of objects I'd like to move into Spaces for my customers, but one of the buckets absolutely has to have a CNAME attached, as the public URLs have to remain the same following a move from S3.

    At least an inkling of a timeline as to when this will be implemented would be great.

  • Liviu commented
    September 11, 2018 15:55

    great service in DO so CNAME for Spaces would be great!! Thanks!

  • Craig Wong commented
    September 11, 2018 15:55

    We need this service seriously!

  • Anonymous commented
    September 11, 2018 15:55

    We need this feature

  • Rohir Naik commented
    September 11, 2018 15:55

    Is this CNAME/Domain aliases feature given? Once they are available for Spaces we will immediately start using Spaces.

  • Anonymous commented
    September 11, 2018 15:55

    it's been 2 months, any news on this yet? I've been dying to switch from s3 to spaces, however I'm not willing to move and have a long auto-generated domain shown to thousand of users .

  • Corey C. commented
    September 11, 2018 15:55

    This feature is blocking us from moving to Spaces. We need to be able to put a CDN service in front of our DO Space. Once CNAME/domain aliases are available for Spaces we will immediately stop using S3 and start using Spaces.

  • Anonymous commented
    September 11, 2018 15:55

    make this happen in 2018 please.

  • Bogor Desain commented
    September 11, 2018 15:55

    I wait for this

  • Anonymous commented
    September 11, 2018 15:55

    Yes, CNAME is a very important feature.

  • Liviu commented
    September 11, 2018 15:55

    CNAMES would be excellent! :) Thanks

  • Rohir Naik commented
    September 11, 2018 15:55

    CNAME is must for spaces. do let me know if it works. Thank You

  • Trevor Pao commented
    September 11, 2018 15:55

    This is a must for me

  • Andrey commented
    September 11, 2018 15:55

    CNAME must be done for spaces bucket, instead of it's not useful service for static content usage.
    S3 seems the best with their custom domain name binding.

  • Anonymous commented
    September 11, 2018 15:55

    I have my static site here on DO spaces, but unless I can point my domain name here, I will have to move my site somewhere else.

  • MikeVL commented
    September 11, 2018 15:55

    +

  • James Jeffery commented
    September 11, 2018 15:55

    This is a must for me. I host numerous static landing pages that I need to point to a domain. I can do it with S3.

    I think the problem for DO is they built Spaces ontop of S3. It's literally an S3 service. Domain configuration would have to be set up by DO on their S3 account. I doubt they would do this.

  • Beerock Studios commented
    September 11, 2018 15:55

    CNAME / Cloudflare is a requirement for us. We want to move to Spaces from S3 but cannot until these are supported

  • Anonymous commented
    September 11, 2018 15:55

    This would be great!

  • Masum commented
    September 11, 2018 15:55

    Was considering to migrate from s3, but this is a blocker for me. I may not migrate if custom alias is not allowed.

  • John commented
    September 11, 2018 15:55

    This seemed so obvious I just automatically created cname after i made my space ... and it didn't work... lol

  • Jamie Druce commented
    September 11, 2018 15:55

    Would be good to get an update on this. This is a complete roadblock for us to move forward with Spaces.

  • Jin commented
    September 11, 2018 15:55

    We are also waiting on this. CNAME record would be great.

  • Anonymous commented
    September 11, 2018 15:55

    Are we there yet?

  • John Gannon commented
    September 11, 2018 15:55

    We will be supporting this very soon.

  • Anonymous commented
    September 11, 2018 15:55

    This would be really nice. I am missing this feature!

  • Younes Alian commented
    September 11, 2018 15:55

    I hope you add custom domain for the Space to be the link of the files I have uploaded ex: https://downiz.com/ { upload folder / file name . jpg }

  • Joe Pritchard commented
    September 11, 2018 15:55

    COMPLETELY agree. I would love to move my image hosting onto DO spaces, but changing the URLs to everything is just not an option... I have over a TB of images linked to from places that I have no control over.

  • Kevin Crider commented
    September 11, 2018 15:55

    Like everyone else has said, this feature is absolutely a requirement before a large number of us can consider using the service. Branded domains are extremely important for those of us providing services. We can do it with all other major CDN and object storage providers. If DO wants to be a real contender in this arena, they have absolutely got to offer this feature. No exceptions.

    I will continue to play with it during my free trial but I can't implement it in a production environment (and spend money on it, $5 or not) until this feature is available.

  • Mohammad Aliyan commented
    September 11, 2018 15:55

    even a CNAME Record would be fine

  • Anonymous commented
    September 11, 2018 15:55

    I will switch from S3 to spaces if i get that custom alias

  • Mustafa commented
    September 11, 2018 15:55

    +1

  • Damar Pramudito Nurjati commented
    September 11, 2018 15:55

    this is very important for branding website. Still waiting this feature...

  • Anonymous commented
    September 11, 2018 15:55

    I need this so badly... if this becomes possible I will make the switch from S3

  • Sam commented
    September 11, 2018 15:55

    Would probably have used Spaces, but too lazy to switch all the references to my media assets to an ugly auto-generated hostname. Will definitely use if this becomes an option.

  • Gautam Thapar commented
    September 11, 2018 15:55

    Very much needed!

  • Techtunes Inc. commented
    September 11, 2018 15:55

    Custom domain is must need to Space. Without custom domain it impossible for developer to offload their web assets in a vanity manner.

  • Anonymous commented
    September 11, 2018 15:55

    This is a must until DigitalOcean offers a CDN (if they ever do).

  • xxdesmus commented
    September 11, 2018 15:55

    This is critical for Spaces to be a reasonable competitor to other similar products that support custom hostnames.

  • Jan Werkhoven commented
    October 8, 2018 05:16

    +1

  • Techtunes Inc. commented
    October 14, 2018 13:34

    Please consider these 3 point to make Digital Ocean Spaces CDN a perfect for modern web application.

     

    1. Please Allow custom domain alias for Spaces bucket with SSL support must. Because all off the sites is now need SSL support and static files also. So custom domain without SSL support will be useless. For SSL supported sites, static files also need SSL support.

     

    2. Also please support multiple domain so that static file can be serve with different domain like css.domain.com js.domain.com video.domain.com etc. with SSL support of course.

     

    3. Wildcard domain support and option of uploading own SSL option is also needed.