The Operations team has created multiple snapshots for the Amazon EBS volumes using Data Lifecycle Manager.
These snapshots are stored in an Amazon S3 bucket.
They want to seek your guidance to read the contents of the snapshot so that only a particular snapshot can be used to create volume. Which of the following can be used to read the contents of Amazon EBS snapshots effectively?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: C.
Amazon EBS direct APIs can be used to create EBS snapshots, write data directly to snapshots, read data from snapshots, and identify the difference between two snapshots.
Option A is incorrect as Data Lifecycle Manager cannot be used to read contents within snapshots.
Option B is incorrect as EBS snapshots stored in Amazon S3 are not directly accessible from the S3 console.
Option D is incorrect as creating volumes from the snapshot requires additional administrative work.
For more information on EBS direct APIs, refer to the following URLs,
https://aws.amazon.com/fr/blogs/aws/new-programmatic-access-to-ebs-snapshot-content/ https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-accessing-snapshot.htmlThe most effective option to read the contents of an Amazon EBS snapshot would be to create a new volume from the snapshot and attach it to an Amazon EC2 instance. This would allow you to read the contents of the snapshot and verify that it contains the data you need before creating a volume from it.
Option A is not correct as Data Lifecycle Manager is used to automate the creation, retention, and deletion of EBS snapshots based on lifecycle policies. It does not provide a way to read the contents of the snapshot.
Option B is partially correct but not the most effective solution. You can read the contents of the snapshot by accessing the S3 bucket where it is stored and using the GET API to download the snapshot. However, this would require more steps and may not be as efficient as the other options.
Option C is not correct as the Amazon EBS Direct API is used for low-level access to EBS volumes and does not provide a way to read the contents of a snapshot.
Therefore, the most effective option would be to create a new volume from the snapshot and attach it to an EC2 instance to read the contents of the snapshot.