The course is part of this learning path
This course covers the core learning objective to meet the requirements of the 'Designing storage solutions in AWS - Level 3' skill
Learning Objectives:
- Evaluate the different Amazon S2 encryption meachanisms available for both client and serfver cryptographic operations
- Create a file storage strategy for complex organizations
- Analyze the differenr AWS storage services available to implement a hybid storage solution based upon different data set sizes, business requirements, and cost optimization
Hello and welcome to this short lecture, which will provide a high-level overview of how you can import on-premise data into EFS. If you're looking to use EFS, then it's likely that you already have a dataset in mind that you think would be better served using this service. For example, your home directories for your employees that might be served on local file servers on-premises. So how would you go about moving this data into EFS to use the benefits that it offers?
The recommended course of action is to use another service called AWS DataSync. This service is specifically designed to help you securely move and migrate and synchronize data for your existing on-premises site into AWS Storage Services such as Amazon EFS or Amazon S3 with simplicity and ease. The data transfer can either be accomplished over a direct connect link or over the internet. To sync source files from your on-premises environment, you must download the DataSync agent as a VMware ESXi host to your site. The agent is configured with the source and destination target and associated with your AWS account, and logically sits in between your on-premise file system and your EFS file system.
DataSync is also very useful if you want to transfer files between EFS file systems either within the same AWS account or cross-account and owned by a third-party. To help with the management and implementation of this transfer, AWS has created an AWS DataSync in-cloud quick start and scheduler, which can be found here on GitHub.
Within the overview documentation of this tool, the following use cases are provided. You can migrate an NFS file system from Amazon EC2 to Amazon EFS within the same AWS region. Replace an NFS file system from Amazon EC2 in one AWS region to an Amazon EFS file system in a different AWS region for disaster recovery. You can migrate an Amazon EFS file system from EFS standard with no lifecycle management to an EFS file system with lifecycle management enabled.
File systems with lifecycle management enabled will automatically move to a lower-cost Infrequent Access storage class based on a predefined lifecycle policy. You can migrate an Amazon EFS file system from one performance mode to another performance mode within the same AWS region, and replicate an Amazon EFS file system from one AWS region to another Amazon EFS file system in a different AWS region for disaster recovery. The configuration and implementation of the AWS DataSync tool is out of scope of this course. However, you can find more information on this service here.
That brings me to the end of this lecture. Coming up next, I'll be providing a summary of the key points throughout the previous lectures of this course.
Stuart has been working within the IT industry for two decades covering a huge range of topic areas and technologies, from data center and network infrastructure design, to cloud architecture and implementation.
To date, Stuart has created 150+ courses relating to Cloud reaching over 180,000 students, mostly within the AWS category and with a heavy focus on security and compliance.
Stuart is a member of the AWS Community Builders Program for his contributions towards AWS.
He is AWS certified and accredited in addition to being a published author covering topics across the AWS landscape.
In January 2016 Stuart was awarded ‘Expert of the Year Award 2015’ from Experts Exchange for his knowledge share within cloud services to the community.
Stuart enjoys writing about cloud technologies and you will find many of his articles within our blog pages.