Multiple CNAME alias for 1 bucket

646 views
Skip to first unread message

rubenmch

unread,
Feb 4, 2011, 2:07:09 PM2/4/11
to Google Storage for Developers
Hi,

Is there a way to setup multiple CNAME aliases for a single bucket?

We currently use Amazon CloudFront and are migrating some buckets to
Google Storage. In Amazon CloudFront we can setup multiple CNAME
aliases for a single bucket, for example:
http://files.dummy1.com/Test1.txt
http://files.dummy2.com/Test1.txt
...would point to the same bucket and return the same file.

Is this possible with Google Storage? If not, are there any plans to
support this in the future?

Thanks

Navneet (Google)

unread,
Feb 6, 2011, 10:25:05 PM2/6/11
to gs-dis...@googlegroups.com
Ruben,

We don't currently support multiple CNAME aliases for a single bucket. Could you help me understand how you'd like this feature? It's not currently planned for the near term, but I will add it to our feature request list.

Thanks,
Navneet


--
You received this message because you are subscribed to the Google Groups "Google Storage for Developers" group.
To post to this group, send email to gs-dis...@googlegroups.com.
To unsubscribe from this group, send email to gs-discussio...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/gs-discussion?hl=en.


Mark

unread,
Feb 7, 2011, 12:15:53 AM2/7/11
to gs-dis...@googlegroups.com
I would just like to support whatever resources are chosen to add full DNS and domain functionality to this product, similar in fashion to other people working on creating cloud server infrastructure. Good Luck! - Mark

Ruben Montelongo

unread,
Feb 7, 2011, 12:06:51 PM2/7/11
to gs-dis...@googlegroups.com
Hi Navneet,

The way it's implemented in CloudFront works for us. When a new CloudFront distribution is created a unique subdomain is asigned to the distribution such as ab8990ef877acd98392.cloudfront.aws.com. After that we can add any number of CNAME aliases in the DNS records of our domain by pointing the CNAME records to the unique subdomain that was assigned to the distribution. 

For Google Storage a unique subdomain could be asigned to each bucket so that we could add the required CNAME aliases to the DNS records of our domain.

This would also allow us to easily change the CNAME aliases without having to create new buckets and move all the files.

And also by implementing it this way you could avoid having to require domain ownership verification because any CNAME aliases would have to be setup by the domain owner on the DNS records.

Thanks.
--
Saludos,

Ruben Montelongo

Bob Oliver Bigellow XLII

unread,
Oct 24, 2012, 12:41:03 AM10/24/12
to gs-dis...@googlegroups.com, gs-...@google.com
I'd like to chime in that I'd like something like this as well, but for a different reason.

When using Google Cloud Storage as a CDN for images (all images are public-read), we've found that we can get a small performance boost by randomly distributing the images on a calling page across more than one domain. This is possible with Akamai, for instance:


(the above are fake)

The performance boost comes from browsers deciding to only download so many images in parallel from a given domain. By using multiple domains, you can trick the browser into pulling down more images in parallel.

I figure, with Google Cloud Storage I could simulate this with the two different domain options provided.


...as well as via the CNAME method:


...then, I suppose if one really wanted to, the HTTPS versions of the commondatastorage methods could be used to add two more, but this seems unnecessary and a potential performance loss.

So, it would be really great if we could specify the equivalent of "Bucket Aliases" which allow new bucket names to really resolve to the content found in the bucket it really points to.

Another possibility is if there is some arbitrary (and completely ignored) portion of the domain:

...etc...

However, I could still see this conflicting with unique bucket names no matter what naming convention is given, unless you disallow naming buckets that start with "variation" just as you disallow those that start with "goog", but I think the "Bucket Alias" concept might give better control.

I realize this could also be done by generating each bucket name and syncing content between them, but this seems like a huge waste of storage and syncing activity to simply be able to simulate a bucket alias concept.

Has there been any further thought to supporting similar to this, or did I miss a memo?



Nelson Silva

unread,
Oct 24, 2012, 4:56:13 AM10/24/12
to gs-dis...@googlegroups.com
Hi,

I'd like to see this as well.. the max connections limit in browsers really makes this necessary for proper CDN serving, especially for image heavy sites.

Still, you can get to the bucket through:

http://<bucket>/
http://<bucket>.storage.googleapis.com/

So this should allow 3 * <browser max conn> files being served in parallel.
Reply all
Reply to author
Forward
Message has been deleted
0 new messages