Amazon calls it CloudFront, and it costs $0.17 - $0.22 per GB at the lowest usage tiers. It seems that you simply put your files in an S3 container, make an API call to share them, then let your users enjoy the lower-latency, higher performance service.
Their domestic locations include sites in Virginia, Texas, California, Florida, [...]

Posted November 25, 2008 by Casey
Categories: Dispatches, Technology. Tags: amazon, amazon web services, AWS, CDN, content delivery network. Be the first one.

Via an email from the Amazon Web Services group today:
…we are excited to share some early details with you about a new offering we have under development here at AWS — a content delivery service.
This new service will provide you a high performance method of distributing content to end users, giving your customers low latency [...]

Posted September 18, 2008 by Casey Bisson
Categories: Technology. Tags: amazon, amazon web services, AWS, CDN, content delivery networks, optimization, performance, website optimization, website performance. Be the first one.

ProgrammableWeb pointed out an InformationWeek story that claimed 28% of Amazon’s sales in early 2005 were attributable to Amazon affiliates. And C|net claims Amazon now has 180,000 AWS developers (up from the 140,000 Amazon was claiming about a year ago).
(Note: not every Amazon affiliate/associate is an Amazon Web Services (AWS) developer, but Amazon hasn’t [...]

Posted March 29, 2007 by Casey Bisson
Categories: Libraries & Networked Information, Technology. Tags: amazon api, amazon web services, Amazon.com, api, AWS, developers, earnings, mashups. One Comment.

Ryan Eby got me excited about S3 a while ago when he pointed out this post on the Amazon web services blog and started talking up the notion of building library-style digital repositories.
I’m interested in the notion that storage is being offered as a commodity service, where it used to be closely connected to servers [...]

Posted May 9, 2006 by Casey Bisson
Categories: Libraries & Networked Information. Tags: amazon, amazon web services, AWS, commodity service, internet applications, ryan eby, s3, simple storage service. One Comment.

I prefaced my point about how the standards we choose in libraries isolate us from the larger stream of progress driving development outside libraries with the note that I was sure to get hanged for it.
It’s true.
I commented that there were over 140,00 registered Amazon API developers and 365 public OpenSearch targets (hey look, there’s [...]

Posted February 23, 2006 by Casey Bisson
Categories: Libraries & Networked Information, Politics & Controversy. Tags: a9, amazon api, amazon web services, argument, AWS, cage match, code4lib, code4lib 2006, future libraries, information retrieval, lib20, libraries, library, library 2.0, library standards, opensearch, search, search and retrieval, search retrieval, sru/srw, srw/sru, web services. 5 Comments.

No, I’m not talking about the interface our users see in the web browser — there’s enough argument about that — I’m talking about web services, the technologies that form much of the infrastructure for Web 2.0.
Once upon a time, the technology that displayed a set of data, let’s say catalog records, was inextricably [...]

Posted November 30, 2005 by Casey Bisson
Categories: Libraries & Networked Information, Technology. Tags: amazon, amazon api, amazon web services, api, dublin core, ead, libraries, library, library catalog, marc, marc-xml, opac data, opensearch, web 2.0, web service, web services, web20, webservice, webservices, xml, xml server. 7 Comments.