03-15-2006, 09:56 AM
Current users of the service include University of California Berkeley "Stardust@Home" Team, Podcast transcription service provider CastingWords, storyboarding software maker FilmmakerLIVE.com, and others.
Cost to use the storage is $0.15 per GB of data stored and $0.20 per GB of bandwidth.
full press release: http://phx.corporate-ir.net/phoenix.zhtml?c=176060&p=irol-newsArticle&ID=830815&highlight=
The Amazon S3 info page: http://www.amazon.com/gp/browse.html/002...e=16427261
Cost to use the storage is $0.15 per GB of data stored and $0.20 per GB of bandwidth.
Quote:Amazon Web Services Launches "Amazon S3,'' a Simple Storage Service for Software Developers
S3 Provides Application Programming Interface for Highly Scalable, Reliable, Low-Latency Storage at Very Low Costs
Amazon Web Services today announced "Amazon S3™," a simple storage service that offers software developers a highly scalable, reliable, and low-latency data storage infrastructure at very low costs. Amazon S3 is available today at http://aws.amazon.com/s3.
Amazon S3 is storage for the Internet. It's designed to make web-scale computing easier for developers. Amazon S3 provides a simple web services interface that can be used to store and retrieve any amount of data, at any time, from anywhere on the web. It gives any developer access to the same highly scalable, reliable, fast, inexpensive data storage infrastructure that Amazon uses to run its own global network of web sites. The service aims to maximize benefits of scale and to pass those benefits on to developers.
Amazon S3 Functionality
Amazon S3 is intentionally built with a minimal feature set. The focus is on simplicity and robustness.
* Write, read, and delete objects containing from 1 byte to 5 gigabytes of data each. The number of objects that can be stored is unlimited.
* Each object is stored and retrieved via a unique developer-assigned key.
* Objects can be made private or public, and rights can be assigned to specific users.
* Uses standards-based REST and SOAP interfaces designed to work with any Internet-development toolkit.
Amazon S3 Design Requirements
Amazon built S3 to fulfill the following design requirements:
* Scalable: Amazon S3 can scale in terms of storage, request rate, and users to support an unlimited number of web-scale applications. It uses scale as an advantage: adding nodes to the system increases, not decreases, its availability, speed, throughput, capacity, and robustness.
* Reliable: Store data durably, with 99.99% availability. There can be no single points of failure. All failures must be tolerated or repaired by the system without any downtime.
* Fast: Amazon S3 must be fast enough to support high-performance applications. Server-side latency must be insignificant relative to Internet latency. Any performance bottlenecks can be fixed by simply adding nodes to the system.
* Inexpensive: Amazon S3 is built from inexpensive commodity hardware components. As a result, frequent node failure is the norm and must not affect the overall system. It must be hardware-agnostic, so that savings can be captured as Amazon continues to drive down infrastructure costs.
* Simple: Building highly scalable, reliable, fast, and inexpensive storage is difficult. Doing so in a way that makes it easy to use for any application anywhere is more difficult. Amazon S3 must do both.
A forcing function for the design was that a single Amazon S3 distributed system must support the needs of both internal Amazon applications and external developers of any application. This means that it must be fast and reliable enough to run Amazon.com's web sites, while flexible enough that any developer can use it for any data storage need.
Amazon S3 Design Principles
Amazon used the following principles of distributed system design to meet Amazon S3 requirements:
* Decentralization: Use fully decentralized techniques to remove scaling bottlenecks and single points of failure.
* Asynchrony: The system makes progress under all circumstances.
* Autonomy: The system is designed such that individual components can make decisions based on local information.
* Local responsibility: Each individual component is responsible for achieving its consistency; this is never the burden of its peers.
* Controlled concurrency: Operations are designed such that no or limited concurrency control is required.
* Failure tolerant: The system considers the failure of components to be a normal mode of operation and continues operation with no or minimal interruption.
* Controlled parallelism: Abstractions used in the system are of such granularity that parallelism can be used to improve performance and robustness of recovery or the introduction of new nodes.
* Decompose into small, well-understood building blocks: Do not try to provide a single service that does everything for everyone, but instead build small components that can be used as building blocks for other services.
* Symmetry: Nodes in the system are identical in terms of functionality, and require no or minimal node-specific configuration to function.
* Simplicity: The system should be made as simple as possible, but no simpler.
"Amazon S3 is based on the idea that quality Internet-based storage should be taken for granted," said Andy Jassy, vice president of Amazon Web Services. "It helps free developers from worrying about where they are going to store data, whether it will be safe and secure, if it will be available when they need it, the costs associated with server maintenance, or whether they have enough storage available. Amazon S3 enables developers to focus on innovating with data, rather than figuring out how to store it."
S3 lets developers pay only for what they consume and there is no minimum fee. Developers pay just $0.15 per gigabyte of storage per month and $0.20 per gigabyte of data transferred.
full press release: http://phx.corporate-ir.net/phoenix.zhtml?c=176060&p=irol-newsArticle&ID=830815&highlight=
The Amazon S3 info page: http://www.amazon.com/gp/browse.html/002...e=16427261