Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 841 discussion

AnswerB The problem is that we need to choose best solution which is most cost-effective and have minimal administrative effort. Glacier is the best choice for 1st look, but there is one problem with that solution. From what I know there is no easy way to copy from EBS to Glacier and additionally curent strategy is to make incremental snapshots. To copy file from EBS to (s3) Glacier we would need to run linux to which we will mount EBS and we will need copy everything to S3 and then move to glaceir deep archive. And what is more you will have only incremental snapshot. Hence every solution which will say copy/move to S3 is not minimal administrative effort. Not mentionig that you will not have full snapshot https://repost.aws/questions/QUsaCoBAfbR6WMOz6BH3vqHA/move-ebs-to-glacier

How much does EBS snapshots archive cost? Pricing and billing. Archived snapshots are billed at a rate of $0.0125 per GB-month. For example, if you archive a 100 GiB snapshot, you are billed $1.25 (100 GiB * $0.0125) per month. What is the cost of Glacier? Even though uploading data to Amazon S3 Glacier is free, there is a pricing method for upload requests, which is $0.03 per 1,000 requests. Transferring data out of S3 Glacier to the same region is free; however, there is a cost for transferring data to a different region. • $0.0036 per GB / Month

Cost Efficiency : Amazon EBS Snapshots Archive is designed to provide a cost-effective option for long-term storage of EBS snapshots. By moving monthly snapshots to the archive tier, you will significantly reduce the cost

Amazon EBS Snapshots Archive is a storage tier that you can use for low-cost, long-term storage of your rarely-accessed snapshots that do not need frequent or fast retrieval. Move to S3... more job, so A is not a good idea... Only 5% daily change.. would consider cheaper than S3 for long run... (MOST cost-effectively) I don't think in the exam need to calculate cost per $, how to remember? Just add new policy to move the snapshot to Amazon EBS Snapshots Archive (minimal administrative effort)

A or B but I will choose A because Is the MOST cost-effectively and companies will always choose to save money.

"EBS Snapshots are stored incrementally." "The snapshots are automatically saved to Amazon Simple Storage Service (Amazon S3) for long-term retention" "Save up to 75% in snapshot storage costs by using EBS Snapshots Archive for the long-term retention (over 90 days) of seldom-accessed snapshots." Moreover, copy files (option A) requires more administrative effort than automatic policy. https://aws.amazon.com/ebs/snapshots/#:~:text=available%20and%20durable-,Amazon%20EBS%20Snapshots%20are%20a%20convenient%20way%20to%20back%20up,availability%20of%20your%20EBS%20Snapshots.

A - S3 Glacier Deep Archive is designed for long-term data archiving with a retention period of up to 7 years or more at an extremely low cost (the most cost-effective S3 storage class). B - OK but EBS Snapshots Archive costs more. C - Keep the monthly snapshot in the standard tier for 1 month, OK. For 7 years??? You'll pay so much money for that. The standard EBS snapshot tier is designed for frequent access. D - Storing snapshots directly in Amazon S3 (even in the Infrequent Access tier) is not ideal for EBS snapshots because it doesn't leverage EBS snapshot mechanisms, which are designed for efficient storage and management of EBS backup data.

https://repost.aws/knowledge-center/ebs-copy-snapshot-data-s3-create-volume. =>I want to copy an Amazon Elastic Block Store (Amazon EBS) snapshot to my Amazon Simple Storage Service (Amazon S3) bucket. I also want to create Amazon EBS volumes from data that's stored in my S3 bucket. Looks like B Short description When you create an EBS snapshot, it's automatically stored in an Amazon S3 bucket that AWS manages. You can copy snapshots within the same AWS Region, or from one Region to another. However, you can't copy snapshots to S3 buckets that you manage.

If we consider both cost and administrative effort more closely: EBS Snapshots Archive may be easier to manage but could incur higher costs over 7 years compared to S3 Glacier. S3 Glacier, despite its complexity for initial transfers, could end up being more cost-effective in the long run, especially for large data volumes. Ultimately, if minimizing costs is a primary concern and the organization can handle the initial complexity of transferring snapshots, using S3 Glacier (Option A) could still be worth considering. So, while Option B is easier, if cost is a significant factor, Option A might be the better choice despite the additional administrative effort involved. It's a trade-off that depends on the organization's priorities regarding cost and operational simplicity.

Keyword here is cost. S3 Glacier deep archive is significantly cheaper than keeping snapshots in the EBS snapshot standard tier or even the EBS Snapshots Archive.

A is correct answer

Choose EBS Snapshot Archive when: Data is associated with EBS volumes. You need to maintain point-in-time copies of your EBS volumes.   You require faster restore times than S3 Glacier Archive. You need to comply with regulations requiring EBS snapshot retention.

Option (B) is incorrect due to the following: Archiving is recommended for monthly, quarterly, or yearly snapshots. Archiving daily incremental snapshots of a single volume can lead to higher costs when compared to keeping them in the standard tier. https://docs.aws.amazon.com/ebs/latest/userguide/snapshot-archive.html

I would like to vote "A". we have to focus on the cost as per question.

(A) is incorrect. Although S3 Glacier Deep Archive is cheaper, to copy the monthly EBS snapshot to S3 would leave a container filled with incremental snapshots that would need to be first assembled into a full snapshot before it could be available. Amazon EBS Snapshots Archive stores full snapshots ensuring 'that data is available with minimal administrative effort'.

looks like an archivesituation for me https://docs.aws.amazon.com/ebs/latest/userguide/snapshot-archive.html The option A is actually cheaper, but i do not like the word copy, and as far as i know there is no way, without writing custom code, to automate che move of snapshot to glacier and i think that the purposu of this question is to show that you know that there is the snapshot archive option

B , there is not admin effort for bringing it back