Nathan (gemsling) wrote,

Using S3 for storage: the bucket/domain conundrum.

I like the idea behind permalinks: keep stuff online and accessible over time via a URL that doesn't change.

To avoid fragmentation, this requires some future planning. For example, where should I put images or files that I refer to in posts or blog comments?

I'm thinking of using Amazon S3 to store some stuff, especially if it's big - video and audio can quickly take up valuable space on our shared web hosting.

The question is, what domain name(s) do I use? I already have stuff all over the place, so it would be nice to consolidate. I could put things under the generic S3 domain, but then I'm locked in. I could put things under my own domain, but which one? Or do I need to set up separate buckets for different purposes, essentially creating deliberate fragmentation?


EDIT: I decided on setting up - that should do for most stuff.
Tags: tech

  • Stymied by a generous download quota

    All I want to do is run a simple Perl script. But... It requires Net::DNS. Fortunately, Net::DNS can be easily installed by using the CPAN…

  • Computing cost and elapsed time

    Okay, I admit that opening a file 14334 times to see if it has a line matching the current item may not be the most efficient thing to do. In…

  • Local countdown

    nathanj@pecan.local> 11:59pm [~/]: date Sat 31 Dec 2011 23:59:55 EST nathanj@pecan.local> 11:59pm [~/]: date Sat 31 Dec 2011 23:59:56 EST…

  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded