Moving 1PB of data from OnPrem to AWS S3 can be a complex process, but there are several tools and services available that can help you to achieve this.
AWS DataSync is a fast and simple way to move large amounts of data from on-premises to Amazon S3 or Amazon EFS (Elastic File System). AWS DataSync is designed to optimize network utilization and minimize the time it takes to transfer data. It also provides features like data validation, task scheduling, and task monitoring to ensure that data is transferred correctly.
AWS Snowball Edge is a physical device that can be used to move large amounts of data into and out of Amazon S3. It has built-in compute and storage capabilities, and can be used to move large volumes of data faster than over the network. Snowball Edge can also be used to support use cases that require data processing and analysis at the edge, before being transferred to Amazon S3.
AWS also provides several other migration services, including AWS Database Migration Service (DMS) and AWS Server Migration Service (SMS), that can help you to migrate databases and servers to AWS.
Regarding the SFTP limit, it's true that there is a 5TB limit for a single SFTP transfer to Amazon S3. However, you can use multipart uploads to transfer larger files. Multipart uploads can break a large file into smaller parts and upload them in parallel, which can help to optimize network utilization and transfer speed.
Overall, there are several tools and services available that can help you to move 1PB of data to AWS S3, including AWS DataSync, AWS Snowball Edge, and AWS migration services. It's important to evaluate your specific use case and requirements to determine which approach is the best fit for your needs. AWS documentation and best practices can provide further guidance and references on this topic.
Here are some links to AWS documentation that can help you learn more about the tools and services I mentioned:
AWS Snowball Edge: https://aws.amazon.com/snowball-edge/
AWS Database Migration Service (DMS): https://aws.amazon.com/dms/
AWS Server Migration Service (SMS): https://aws.amazon.com/server-migration-service/
Amazon S3 Multipart Upload: https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html
Additionally, here are some general references on data migration and best practices:
AWS Data Migration Whitepaper: https://d1.awsstatic.com/whitepapers/Migration/aws-migration-whitepaper.pdf
AWS Data Transfer Costs: https://aws.amazon.com/s3/pricing/data-transfer/
AWS Data Transfer Best Practices: https://aws.amazon.com/training/course-descriptions/data-transfer-best-practices/
I hope these resources are helpful! If you have any more specific questions or concerns, please let me know.
Using the "Storage Class Options" Menu Item
Right-click on the S3 bucket you want to archive to S3 Glacier Deep Archive or an other storage class, then select Storage Class Options item in the context menu.
In the Object Properties box, switch to the Storage Class tab.
In the Use storage class drop-down menu, select the storage class you want your objects to be moved.
When you are finished, click Apply.
Using the “Move to Glacier” Option
Right-click on the S3 bucket that you want to archive to S3 Glacier storage class.
Select Move to Glacier.
In the Bucket Lifecycle dialog box, click Add.. to create a lifecycle rule for your bucket.
In the Bucket Lifecycle Rule dialog box, specify the path and data transition rules.
Select the Enable this rule check box to apply this lifecycle rule to your bucket.
When you are finished, click OK. Note that you can also manage Object Expiration using this dialog box. Click this link to learn more about Object Expiration. Note that the Object Expiration policy may delete files permanently, with no possibility of restoring them.
Note that your backup data may appear to be located in S3 Standard storage class, but in fact it is located in the Glacier storage class. Make sure your backup data is in the Glacier storage class and check the status in the Storage Class column (it should read GLACIER). According to Amazon's Lifecycle policy, it may take up to 24 hours to apply storage class changes.
Using Upload Rules
In the Tools menu, select Upload Rules.
In the Upload Rules dialog box, select the storage account you want to configure, then click Add.
In the Select actions to perform when upload file to cloud storage drop-down menu, select Set HTTP headers.
Specify settings as shown on the screenshot below:Add HTTP header step
Specify file types or buckets you want this upload rule to be applied to, then click OK
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 7 months ago
- EXPERTpublished 3 months ago