Migrating exiting data to AWS

Hi Ali, You can migrate the data to AWS, and the solution will depend on what you're trying to do. If you're looking to extend your on-premises storage in AWS for a hybrid storage model (e.g., backing up data in AWS, or extending storage in AWS as you're running out of storage on-premises), AWS Storage gateway is the solution for you and I'm listing a few resources for you to review... https://www.youtube.com/watch?v=ekbMD5yFRTk https://www.youtube.com/watch?v=zo0ImMbqLBY https://aws.amazon.com/blogs/storage/planning-to-replace-a-data-center-nas-with-amazon-fsx-file-gateway/ https://aws.amazon.com/cloud-data-migration/

However, if you're looking to migrate your data/files to AWS and use native AWS services moving forward, AWS Data Sync might be the better option and here are a couple of resources... https://aws.amazon.com/blogs/storage/migrating-storage-with-aws-datasync/ https://aws.amazon.com/blogs/storage/synchronizing-your-data-to-amazon-s3-using-aws-datasync/ https://www.youtube.com/watch?v=4xJOvSej1SE

The cost will depend on the solution you opt for but here's the pricing info for AWS Storage Gateway, and AWS DataSync... https://aws.amazon.com/storagegateway/pricing/ https://aws.amazon.com/datasync/pricing/

Hope this helps.

To add to this; Please keep in mind S3 is an HTTPs protocol, where your NAS probably will use SMB ('CIFS') and/or NFS. All of these come with their own way of authentication, so when you migrate your data to an S3 bucket, you will have to redefine access. As mentioned by @amanbajw, there are quite some migration tools. To name some another popular one: Cloudberry. My personal background was using the HCP Data Migrator which also was able to apply absolute/relative retention as well as custom metadata. The latter are examples of what added value of objects (S3) vs files (SMB/NFS).

BR, Henk