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

AWS DataSync is a fully managed data transfer service that simplifies and automates the process of moving data between on-premises storage and Amazon S3. It provides secure and efficient data transfer with built-in encryption, ensuring that the data is encrypted in transit. By using AWS DataSync, the company can easily migrate the 100 GB of historical data from their on-premises location to an S3 bucket. DataSync will handle the encryption of data in transit and ensure secure transfer.

Using DataSync, the company can easily migrate the 100 GB of historical data to an S3 bucket. DataSync will handle the encryption of data in transit, so the company does not need to set up a VPN or worry about managing encryption keys. Option A, using the s3 sync command in the AWS CLI to move the data directly to an S3 bucket, would require more operational overhead as the company would need to manage the encryption of data in transit themselves. Option D, setting up an IPsec VPN from the on-premises location to AWS, would also require more operational overhead and would be overkill for this scenario. Option C, using AWS Snowball, could work but would require more time and resources to order and set up the physical device.

s3 sync Disadvantages: Manual process = You handle errors, retries, progress monitoring Basic tool = No optimization for large transfers Network issues = Manual restart if connection drops No built-in throttling = Could saturate bandwidth Higher operational overhead = More hands-on management needed

encrypted = DataSync

I will not use cli (A) to send 100GB to s3 from web. This means I will have to stay by computer? or use a different ec2 to login into it and initiate cli from there? hell no!! B Datasync is the elegant way.

My counter to all those, picking choice A, you will have to manually re-run the command if on-premise internet goes down however with datasync the service auto resume. (less operational overhead and less monitoring)

You can also copy or synchronize data from on-premises to AWS manually with the AWS CLI, but doing so requires a fair bit of system tuning see https://aws.amazon.com/blogs/storage/migrating-and-managing-large-datasets-on-amazon-s3/

For A, it is more straightforward approach, with 100Mbps = 12.5MBs, 100 GB = 100 * 1024 MB = 102,400 MB, 102400 / 12.5 = 8192s = 2.3 hours, so if the network is stable, it should be less operational overhead than B which requires the installation of agent and network configuration, so compared to S3 sync, DataSync requires more upfront configuration but provides more robust, automated transfer capabilities.In an AWS certification exam, they typically expect you to choose the solution that provides the most straightforward, efficient approach with the least operational overhead while meeting all specified requirements. For this scenario, they would likely expect you to choose A.

Option A meets all the requirements with the LEAST operational overhead (while option B will introduce unnecessary complexity for a one-time transfer). The data will be encrypted in transit (via HTTPS), and a 100 Mbps connection is sufficient to transfer data of 100 GB. If the task involves periodic transfers or error recovery, DataSync (option B) could be considered as an alternative.

Why would u u se the CLI

Assertions: - needs to encrypt the data in transit to the S3 bucket. - The company will store new data directly in Amazon S3. Requirements: - with the LEAST operational overhead Even Though options A and B could do the job, option A requires VM maintenance because it is not a once-off migration (The company will store new data directly in Amazon S3) NB: According to me, we must stuck to the question and avoid to interpret

A - one single command, uses encryption automatically B - Must install, configure and eventually decommission DataSync C - Overkill D - No need for VPN

By default, all data transmitted from the client computer running the AWS CLI and AWS service endpoints is encrypted by sending everything through a HTTPS/TLS connection. You don't need to do anything to enable the use of HTTPS/TLS. It is always enabled unless you explicitly disable it for an individual command by using the --no-verify-ssl command line option. This is simpler compared to datasync, which will cost operational overhead to configure.

storage data (including metadata) is encrypted in transit, but how it's encrypted throughout the transfer depends on your source and destination locations.

B is correct to migrate A is incorrect because is it only used to upload minor files (about a few GB) to AWS. 100 GB is not appropriate.

Use AWS DataSync to migrate the data from the on-premises location to an S3 bucket

B is a good option but as the volume is not large and the speed is not bad, A requires less operational overhead