A company wants to reduce its Amazon S3 storage costs in its production environment without impacting durability or performance of the stored objects. What is the FIRST step the company should take to meet these objectives?
A.
Enable Amazon Macie on the business-critical S3 buckets to classify the sensitivity of the objects.
B.
Enable S3 analytics to identify S3 buckets that are candidates for transitioning to S3 Standard-Infrequent Access (S3 Standard-IA).
C.
Enable versioning on all business-critical S3 buckets.
D.
Migrate the objects in all S3 buckets to S3 Intelligent-Tiering.
We should notice the word 'FIRST' in block letters in the question. Obviously, we need S3 Standard IA but the first step should be S3 analytics, hence the answer should be B.
A - Macie is for DLP & PII : unrelated
B - Matches the purpose (reduce cost, keep performance & durability), and it has to be done FIRST
C - Could be a good option if we had more context, maybe to prevent data loss if changing storage class of critical data to a one zone IA class ? Hard to decide.
D - Cannot be intelligent tiering since it can move objects to archive & deep archive, thus impacting performance of the stored object
=> I go with B
D - Intelligent tiering only moves between frequent and infrequent access, not archive. https://aws.amazon.com/about-aws/whats-new/2018/11/s3-intelligent-tiering/ answer is therefore D
By using Amazon S3 analytics Storage Class Analysis you can analyze storage access patterns to help you decide when to transition the right data to the right storage class.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/analytics-storage-class.html
A - Macie is for DLP & PII : unrelated
B - Matches the purpose (reduce cost, keep performance & durability), and it has to be done FIRST
C - Could be a good option if we had more context, maybe to prevent data loss if changing storage class of critical data to a one zone IA class ? Hard to decide.
D - Cannot be intelligent tiering since it can move objects to archive & deep archive, thus impacting performance of the stored object
=> I go with B
not that D has opt in intelligent tierirng for archive so one might argue, but intelligent tirering might be a FINAL decision (set & forget), not a FIRST step (which implies some more). I understand why one could hesitate with D though
I thought D but I'm for B too: Storage analytics: This new Amazon S3 analytics feature observes data access patterns to help you determine when to transition less frequently accessed STANDARD storage to the STANDARD_IA
I may argue that, if your primary goal is to reduce costs, you first go for S3 IT and then perform your analysis to, possibly, further improve your solution.
S3 Analytics Storage Class Analysis cost $0.10 per million objects monitored per month.
S3 Intelligent - Tiering, Monitoring and Automation, All Storage / Month, cost $0.0025 per 1,000 objects = $2.5 per million objects monitored per month.
https://aws.amazon.com/s3/pricing/
So, the correct answer (reduce costs) is B.
To identify where you can cut down on your Amazon S3 charges, you must first understand your current billing and usage for Amazon S3. Then, you must understand the ways that you can incur cost.
You can also use the following Amazon S3 features to help you investigate billing concerns:
1.Use Amazon S3 Storage Lens to obtain a single view of usage and activity across your Amazon S3 storage.
2.Use Amazon S3 Storage Class Analysis to observe data access patterns.
https://aws.amazon.com/premiumsupport/knowledge-center/s3-reduce-costs/
Initially I thought D, however am going for B, as it is the FIRST thing to do. Also consider performance, so Glacier wouldn't provide results as quickly.
Intelligent Tiering S3-IT is used for data access pattern unpredictable which it only moves between frequent and infrequent access tier, not Glacier or Deep archive.
What if most obj in the bucket have not been accessed for a quite a long while which should be transit to Glacier instead of Standard-IA? Hence, without performing the S3 Analytics to get the true picture of the obj access pattern, to straight away proceed to transit to S3-IT is not sounded.
Paiseh, I revert my answer. It should be option D for the right answer. See below:
The S3 Intelligent-Tiering storage class automatically stores objects in three access tiers without performance impact or operational overhead and for a low monthly object monitoring and automation charge. One tier is optimized for frequent access, one lower-cost Infrequent Access tier is optimized for infrequent access (not been accessed for 30 consecutive days), and another very low-cost Archive Instant Access tier is optimized for rarely accessed data (not been accessed for 90 consecutive days). Can also further activate the optional archive capabilities, for obj without access after 180 consecutive days, the objects are moved to the Deep Archive Access tier.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/intelligent-tiering-overview.html
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
syu31svc
Highly Voted 3 years, 7 months agoSilNilanjan
3 years, 6 months agorobertomartinez
3 years, 7 months agoinduna
3 years, 5 months agoDahMac
3 years, 6 months agonoahsark
3 years, 6 months agorobertomartinez
Highly Voted 3 years, 7 months agoDahMac
3 years, 6 months agorobertomartinez
3 years, 7 months agoshantest1
3 years, 7 months agopatriktre
3 years, 7 months agoTwinkie
3 years, 6 months agoBECAUSE
Most Recent 1 year, 11 months agoF_Eldin
2 years, 5 months agoCurious76
2 years, 8 months agorodriiviru
2 years, 8 months agoAransi90
2 years, 8 months agocloud_collector
2 years, 9 months agoACloudptra
2 years, 9 months agoEzBL
2 years, 10 months agoRightsaidfred
2 years, 11 months agocutecolt
3 years agocutecolt
3 years agofuyin
3 years, 2 months agochani_god
3 years, 2 months agoosel
3 years, 3 months agoosel
3 years, 3 months agoFF11
3 years, 4 months ago