3 ms·

This is online storage. If a GET fails, just retry as usual (most higher-level libraries do this automatically, sometimes with a backoff mechanism).

cperciva 11y ago
If a GET fails, just retry as usual 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.
- zeckalpha 11y ago
  Additionally, assuming your block data is being hash-addressed, i.e. not changing the S3 objects once they are in S3, adding CloudFront in front of your buckets may go a long way to increasing that percentage. However, its SLA is a little more involved (for better or worse): http://aws.amazon.com/cloudfront/sla/ 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.
seiji 11y ago
(constructive review) 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?
- dbarlett 11y ago
  S3 Standard: "Designed for 99.99% availability over a given year" [1] 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_Standard https://aws.amazon.com/s3/storage-classes/#Amazon_S3_Standar... [2] https://aws.amazon.com/s3/storage-classes/#Infrequent_Access https://aws.amazon.com/s3/storage-classes/#Infrequent_Access [3] http://aws.amazon.com/glacier/faqs/#How_can_I_retrieve_data http://aws.amazon.com/glacier/faqs/#How_can_I_retrieve_data
  - seiji 11y ago
    Thanks for rounding those up. There's a nice table just below this URL too with all relevant comparisons too: https://aws.amazon.com/s3/storage-classes/#Archive https://aws.amazon.com/s3/storage-classes/#Archive It does contradict the introductory blog post article here, but I'm assuming the actual documentation is more accurate.
sandstrom 11y ago
Jeff, could you elaborate on the trade-offs? 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.

cperciva 11y ago

If a GET fails, just retry as usual 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.

zeckalpha 11y ago
Additionally, assuming your block data is being hash-addressed, i.e. not changing the S3 objects once they are in S3, adding CloudFront in front of your buckets may go a long way to increasing that percentage. However, its SLA is a little more involved (for better or worse): http://aws.amazon.com/cloudfront/sla/ 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.

seiji 11y ago

(constructive review) 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?

dbarlett 11y ago
S3 Standard: "Designed for 99.99% availability over a given year" [1] 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_Standard https://aws.amazon.com/s3/storage-classes/#Amazon_S3_Standar... [2] https://aws.amazon.com/s3/storage-classes/#Infrequent_Access https://aws.amazon.com/s3/storage-classes/#Infrequent_Access [3] http://aws.amazon.com/glacier/faqs/#How_can_I_retrieve_data http://aws.amazon.com/glacier/faqs/#How_can_I_retrieve_data
- seiji 11y ago
  Thanks for rounding those up. There's a nice table just below this URL too with all relevant comparisons too: https://aws.amazon.com/s3/storage-classes/#Archive https://aws.amazon.com/s3/storage-classes/#Archive It does contradict the introductory blog post article here, but I'm assuming the actual documentation is more accurate.

sandstrom 11y ago

Jeff, could you elaborate on the trade-offs? 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.