The idea is awesome; you store objects in the Intelligent Tiering storage class. As they go longer without being accessed, they get moved into first infrequent access, and then (as of today, if you enable it), into Glacier / Glacier Deep Archive. You pay less over time!
The caveats that you'll smack into here.
1. Only objects larger than 128kb are transitioned. A bunch of small objects will stay at Standard Tier pricing.
2. There's a per-object monitoring charge. For a lot of sufficiently small objects, you're going to pay the monitoring charge on things that will never be transitioned.
3. Every object that you store in S3 Intelligent Tiering is charged for 30 days of storage, regardless of how long it lives. So if you're using S3 as a message queue, this is going to get... spendy.
4. While Glacier / Glacier Deep Archive storage is awesome for cost, retrieval latencies are measured in minutes or hours. That's a long time to watch your "loading" spinner circle your screen.
So, is S3 Intelligent Tiering awesome? Hell yes--we recommend it to our customers constantly.
But we run a bunch of analytics *FIRST* to make sure nobody is about to get a Surprise Bill.
I maintain that @awscloud S3 is the eighth wonder of the world, and this doesn't change that perception any.
/fin
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The @LastWeekinAWS annual charity t-shirt fundraiser wrapped up yesterday. You wonderful, amazing people helped us raise $15,225 for @826National with exactly 500 shirts sold. The check is on the way, 826 folks.
I was out on parental leave for most of this. Some amazing people stepped up to help make this possible. Their work happened behind the scenes, though you clearly saw the results of it.
First, our delightful copywriter Lianna (@punchlinecopy). She's the only writer I've ever worked with where I have to say "that's HILARIOUS, but it's a bit TOO edgy." She's incredible.
Middle of the night alert from my @Synology. "Security risk found!"
The risk in question: I haven't bound SSH to a non-standard port.
Security myth: binding SSH to a non-standard port is somehow safer.
In practice, use keypair auth only; then the only benefit of a non-standard port is that your logs don't fill up with brute force attempts.
Security myth: rotate your @awscloud IAM credentials frequently so your console doesn't yell at you.
In practice, compromised keys are exploited in less time than it takes to microwave a burrito. Use role assumption if you can, but rotating keys is busywork.
Anomaly Detection for @awscloud bills is stupidly hard to get right. I’m optimistic about what they’ve built—now let’s see how it works in the wild! aws.amazon.com/blogs/aws-cost…
Me: “How hard could it possibly be?!” @mike_julian, monitoring wizard: “Oh my sweet summer child.”
...there might be some @awscloud UX teething issues.