If a GET fails, just retry as usual (most higher-level libraries do this automatically, sometimes with a backoff mechanism).
Thanks! This is a very important detail which isn't documented anywhere: Retries are likely to succeed. A service where 1% of requests fail but failures are completely uncorrelated is far more usable than a service where 0.01% of requests fail but they keep on failing no matter how many times you retry them.
However, its SLA is a little more involved (for better or worse): http://aws.amazon.com/cloudfront/sla/
I'm not accessing S3 from EC2, though, so another benefit for me was it brought my S3 network costs way down.
I had to read these sentences a few times to understand what you were trying to say: "You now have the choice of three S3 storage classes (Standard, Standard – IA, and Glacier) that are designed to offer 99.999999999% (eleven nines) of durability. Standard – IA has an availability SLA of 99%."
No availability is mentioned for the others, but I assume it's 100%? Perhaps a simple table could help readers to scan and visually compare the values of two properties across three service classes?
Standard - IA: "Designed for 99.9% availability over a given year" [2]
Glacier: "Retrieval jobs typically complete within 3-5 hours." [3]
[1] https://aws.amazon.com/s3/storage-classes/#Amazon_S3_Standar...
[2] https://aws.amazon.com/s3/storage-classes/#Infrequent_Access
[3] http://aws.amazon.com/glacier/faqs/#How_can_I_retrieve_data
It does contradict the introductory blog post article here, but I'm assuming the actual documentation is more accurate.
When choosing between standard and this it would be helpful to understand the pros and cons. With the current description (below) it's as if the difference is only in pricing. But I assume there is a technical difference as well.
Also, the availability number could be explained better -- why is it different.
Standard - IA offers the high durability, throughput, and low latency
of Amazon S3 Standard, with a low per GB storage price and per GB retrieval fee.They might expect to be just as good as regular in the happy path, but are under-promising out of fear of some code-bug or other issue.
Either way, I'd definitely not migrate too soon for exactly the above reason.
> it’s vital that customers have immediate, instant access to any of [our photos] at a moment’s notice – even if they haven’t been viewed in years. [IA] offers the same high durability and performance ... so we can continue to deliver the same amazing experience for our customers.
The way this was phrased implies that this customer's use-case had a hard requirement that all of their data be in "online" storage at all times, and their satisfaction implies that IA does, in fact, hit this requirement.
I'm not sure what the 99% SLA means given that.
S3 Classic: Your file gets replicated on 3 live HDs (and/or HDs backed by RAID arrays—not sure about the internal S3 storage topology).
S3 Infrequent: Your file gets stored on 1 live HD (or single hardware redundancy component) and a copy in Glacier. If your live HD dies, your file will be automatically restored from Glacier to a new HD (but your data may be inaccessible during the automatic re-deploy).
Glacier: offline bluray combined with error correction accessed by robot arms, temporarily restored to live HDs on demand.
One thing concerns me however: Standard – IA has an availability SLA of 99%.
If this is just a reduced SLA but the actual availability is likely to be similar, that's fine. But if the actual availability is not expected to hit 99.9% -- say, if the backend implementation is "one copy in online storage, plus a backup in Glacier which gets retrieved if the online copy dies" that would be completely inadequate.
Hopefully we'll get more details over time.