Achieve Low-Latency Data Backup and Storage on AWS

Efficiently Store and Access Data with Low Latency on AWS

Prev Question Next Question

Question

A company currently hosts a lot of data on its On-premises location.

It wants to start storing backups of this data with low latency access to data on AWS.

How could this be achieved most efficiently?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

For storing backups of data from an on-premises location with low-latency access on AWS, the most efficient solution would be to make use of AWS Storage Gateway Stored Volumes, which is option C.

AWS Storage Gateway is a hybrid storage service that enables companies to securely and seamlessly integrate their on-premises applications with cloud storage. It supports three types of storage volumes:

  1. Cached Volumes
  2. Stored Volumes
  3. Tape Volumes

Cached volumes store data on-premises and cache frequently accessed data in AWS, while stored volumes store all data locally and asynchronously backup to AWS. Tape volumes provide a virtual tape library that can be backed up to AWS.

In this scenario, stored volumes would be the most appropriate option. Stored volumes store all data locally and asynchronously backup to AWS. The data is stored on-premises in a Storage Gateway appliance that connects to AWS over the internet, allowing for low-latency access to data on AWS. Stored volumes are ideal for frequently accessed data, providing low-latency access to the data stored on AWS.

Option A, creating EBS volumes and storing the data, would not be the best solution as EBS volumes are block-level storage devices used to store data on EC2 instances, which are not ideal for backing up data.

Option B, creating EBS snapshots and storing the data, is also not the best solution. EBS snapshots are point-in-time backups of EBS volumes and are primarily used to create backups of EC2 instances or EBS volumes. While it's possible to use EBS snapshots for backups of on-premises data, the process is not efficient, and the data would not be easily accessible.

Option D, making use of Amazon Glacier, is not the most efficient solution for this scenario. Amazon Glacier is a low-cost storage service for data archiving and long-term backups. The data stored in Amazon Glacier is not readily accessible, and it can take several hours to retrieve the data, which is not ideal for backups requiring low-latency access.

Therefore, the best solution for this scenario would be to use AWS Storage Gateway Stored Volumes, as it provides low-latency access to data stored in AWS, making it ideal for frequently accessed backups.