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

This will be perfect! Waiting for it!

Would love this implemented

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

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

need this asap!

Any updates?

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

need that too

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."

Any updates?

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

One more to the pile of we need this please.

Please, we need an update on this.

Waiting for proper ETA as well :)

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

Looking forward to seeing this be implemented!

would love a proper eta on this

any updates

has this been implemented yet?

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."

is there an update?

Would REALLY love an update on this too.

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.

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

really needed...

+1

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

@DO - Any timelines on this yet?

how was this not implemented at launch...

please implement it soon. We need it

Any updates about CNAME. Spaces without CNAME is useless

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

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

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

:D

Looking forward to seeing this be implemented!

Definitivamente en cuanto tengan esta función mudo todo

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.

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.

Pretty much pointless considering the unreliability issues of Spaces

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!

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

I need it urgently!!

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

is there any ETA on this?

can't wait

+1

+1

update

Any update?

+1, any update?

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

This would be a great feature!

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

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.

THIS IS A MUST!!

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

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.

+100

+1

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

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

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

Desperately need this feature.

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.

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

We need this service seriously!

We need this feature

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

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 .

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.

make this happen in 2018 please.

I wait for this

Yes, CNAME is a very important feature.

CNAMES would be excellent! :) Thanks

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

This is a must for me

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.

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.

+

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.

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

This would be great!

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

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

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

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

Are we there yet?

We will be supporting this very soon.

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

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 }

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.

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.

even a CNAME Record would be fine

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

+1

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

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

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.

Very much needed!

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

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

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