SlideShare a Scribd company logo

SRV401 Deep Dive on Amazon Elastic File System (Amazon EFS)

•
•
Amazon Web Services
Amazon Web Services

In this session we will review Amazon EFS and how it delivers fully managed, petabyte-scale file storage for Amazon EC2 instances. Large scale and consistent performance make Amazon EFS ideal for web and content serving, enterprise applications, media processing, container storage, and Big Data analytics use cases. Session attendees will learn how to identify appropriate applications for use with Amazon EFS, understand performance details and security models, and hear how established customers are using it in production. The target audience is file system administrators, application developers, and application owners that operate or build file-based applications that require consistent latencies at cloud scale.

1 of 79
Download to read offline
© 2015, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Yong Kim AWS – Storage Business Development April 18, 2017 Deep Dive on Amazon Elastic File System SRV401 David Green AWS – Enterprise Solutions Architect
What customers are using EFS for today Web serving Content management Analytics Media and Entertainment workflows Workflow management Home directories Container storage Database backups
Shared File Solutions in the Cloud… before EFS 3rd Party Software Do It Yourself 3rd Party Hardware in AWS Direct Connect locations
Do It Yourself – NFS Architecture NFS Clients NFS Server Volume Volume NFS Clients NFS Server Volume Volume NFS Clients NFS Server Volume Volume
Do It Yourself – NFS Architecture  Launch, patch, monitor, & pay for EC2 instances  Create, attach, monitor, & pay for provisioned EBS volumes  Create, maintain, and monitor auto scaling group  Install, patch, monitor, & pay for* file system software  Configure, maintain, monitor, & pay for file system data intra/inter-AZ replication • IOPS for replication are still IOPS  Configure DNS for client HA access to inter-AZ NFS fleet
Do It Yourself
Do It Yourself NFS Architecture NFS Clients NFS Server Volume Volume NFS Clients NFS Server Volume Volume NFS Clients NFS Server Volume Volume
Amazon EFS Architecture NFS Clients NFS Clients NFS Clients Mount Target Single Namespace Mount Target Mount Target
Do It Yourself – Cost NFS Clients NFS Server Volume Volume NFS Clients NFS Server Volume Volume NFS Clients NFS Server Volume Volume
Amazon EFS Architecture NFS Clients NFS Clients NFS Clients Mount Target Single Namespace Mount Target Mount Target
Amazon Elastic File System (EFS) Provides simple, scalable, highly available & durable file storage in the cloud Petabyte scale file system distributed across an unconstrained number of storage servers in multiple Availability Zones (AZs) Elastic capacity, automatically growing & shrinking as you add & remove files
Amazon Elastic File System (EFS) Standard file system interface & semantics Shared storage Highly available & highly durable Consistent low latency Strong read-after-write consistency Elastic capacity Fully managed
Cloud Data Migration Direct Connect Snow* data transport family 3rd Party Connectors Transfer Acceleration Storage Gateway Kinesis Firehose The AWS Storage Portfolio Object Amazon GlacierAmazon S3 Block Amazon EBS (persistent) Amazon EC2 Instance Store (ephemeral) File Amazon EFS
Do you need an EFS file system? If you have an application running on EC2 or use case that requires a file system… AND • Requires multi-attach OR • GBs/s throughput OR • Multi-AZ availability/durability OR • Requires automatic scaling (grow/shrink) of storage
Where is EFS available today? • US West (Oregon) • US East (N. Virginia) • US East (Ohio) • EU (Ireland) • Asia Pacific (Sydney) More coming soon!
Hands-on: Create an EFS File System (Console)
Resources for Amazon EFS File System • Tags • Key-value pairs • Mount Targets • Subnet ID • Security Groups
Resources for Amazon EFS File System • Regional construct • Ten per account per region (soft) • Default throughput limit 3 GB/s (soft) • Metered size updates approx. every hour • Accessible from EC2 • VPC, EC2-Classic via ClassicLink • Accessible from on-premises • AWS Direct Connect
Resources for Amazon EFS File System cont… • Scenarios for on-prem via Direct Connect Bursting Migration Tiering Backup / DR
Resources for Amazon EFS Tags • Typical key-value pair • Create & associate tag with file system • Up to 50 tags per file system
Resources for Amazon EFS Mount Targets • One or more per file system • Create in a VPC Subnet • One per Availability Zone • Must be in the same VPC
Resources for Amazon EFS Security Groups • Standard VPC Security Group • Same VPC as subnet • Up to five per mount target • Allow inbound TCP port 2049 from NFS clients
All EFS AWS CLI Commands aws efs create-file-system aws efs create-mount-target aws efs create-tags aws efs delete-file-system aws efs delete-mount-target aws efs delete-tags aws efs describe-file-systems aws efs describe-mount-target-security-groups aws efs describe-mount-targets aws efs describe-tags aws efs modify-mount-target-security-groups
Mount EFS NFSv4.0 NFSv4.1 Linux Kernel 4+
Recommended Mount Options -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,async Mount using NFSv4.1 (default options) Specify 1MB read/write buffers Hard mount Timeout of 60 seconds (600 tenths of a second) 2 minor timeouts & retransmissions before major timeout Ensure operations are asynchronous
Mount an EFS File System Launch EC2 instance from EC2 Console Connect to the instance Make a directory Mount EFS file system Query disk file system & file system table • df; df -hT; df -h -t nfsv4; mount -t nfsv4
Amazon EFS Architecture NFS Clients Mount Target Availability Zone VPC subnet Amazon EFS EFS File System fs-123456ab Default Default
Amazon EFS Architecture NFS Clients Mount Target Availability Zone VPC subnet Amazon EFS VPC subnet EFS File System fs-123456ab Default Default
Amazon EFS Architecture NFS Clients Mount Target VPC subnet Amazon EFS Mount Target EFS File System fs-123456ab DefaultDefault Default Default
Security Control network traffic using VPC security groups and network ACLs Control file and directory access by using POSIX permissions Control administrative access (API access) to file systems by using AWS Identity and Access Management (IAM) action-level and resource-level permissions
High throughput and parallel I/O Low latency and serial I/O Genomics Big data analytics Scale-out jobs Home directories Content management Web serving Metadata-intensive jobs Amazon EFS is designed for wide spectrum of performance needs
Performance modes for different workloads Mode What’s it for Advantages Tradeoffs When to use General purpose (default) Latency- sensitive applications and general-purpose workloads Lowest latencies for file operations Limit of 7K ops/sec Best choice for most workloads Max I/O Large-scale and data-heavy applications Virtually unlimited ability to scale out throughput / IOPS Slightly higher latencies Consider for large scale-out workloads
EFS CloudWatch Metric - PercentIOLimit Determine whether you’re being constrained by General Purpose mode (PercentIOLimit at or near 100%)
EC2 EC2 … EC2 EC2 … EC2 EC2 … • File systems distributed across unconstrained number of servers • Avoids bottlenecks/constraints of traditional file servers • Enables high levels of aggregate IOPS/throughput • Data also distributed across Availability Zones (durability, availability) Amazon EFS - distributed data storage design
How to think about EFS perf relative to EBS Amazon EFS Amazon EBS PIOPS Performance Per-operation latency Low, consistent Lowest, consistent Throughput scale Multiple GBs per second Single GB per second Characteristics Data availability / durability Stored redundantly across multiple AZs Stored redundantly in a single AZ Access 1 to 1000s of EC2 instances, from multiple AZs, concurrently Single EC2 instance in a single AZ Use cases Big Data and analytics, media processing workflows, content management, web serving, home directories Boot volumes, transactional and NoSQL databases, data warehousing & ETL
I/O size impacts throughput of serialized operations 4 KB 32 KB 256 KB 2 MB 16 MB I/O size Throughput I/O Size Implication
Take advantage of EFS’s distributed architecture Parallelize via multiple threads and/or multiple instances 0 5000 10000 15000 20000 25000 30000 0 20 40 60 80 100 120 140 160 IOPS # of Total Threads Aggregate IOPS of parallel writes using 10 m4.xlarge instances Parallelize
Previous Scalability Test Small files – 300 instancesLarge files – 50 instances
Scale-out Demo Parallelize
Walk-through: Transferring Data
Goal: Move Data Quickly!!
Two Scenarios:
Transferring media assets to EFS • Size ranges from a few GB to 100+GB per file • Data sources: • Amazon S3 • Amazon EBS
Transferring many small files to EFS • Size ranges from 64K to 256K • Data sources: • Amazon S3 • Amazon EBS
Serial vs Parallel
Serial file transfer
Parallel file transfer
How do we do this?
GNU parallel • Tool for executing jobs in parallel • Similar to xargs • Replace loops in shell scripts • GNU parallel makes sure output from the commands is the same output as you would get had you run the commands sequentially. https://www.gnu.org/software/parallel/ For people who live life in the parallel lane
Use parallel threads – GNU parallel # Create destination directory tree from source find . -type d -print0 | parallel -j $N_THREADS -0 "mkdir -p ${DST_DIR}/{}" > /dev/null 2>&1 # Copy files find . ! ( -type d ) -print0 | parallel -j $N_THREADS -0 "cp - f {} ${DST_DIR}/{}"
Optimizing Transfers
Monitoring performance • Data-Driven results • Repeatable Outcomes • Optimize for Costs
Benchmark different instance types • Determine the optimal instance size • What is best? T2, C3, C4, M3, M4, R3, X? • Transfer test set of 1000 small files • Increase thread count from 1-1024 concurrent threads
Tools • Command Orchestration • Instance Configuration • Log Collection • Visualization • Instance performance
Test Results – Large Files
Large Files: Four Instances
Large Files: Four Instances
Adding Additional Instances
Large File: 50 Instances
Test Results – Small Files
Small File Performance - Instance Family Test ~200 threads
c3.large – 5,342 files per minute @ 200 threads
Increase Instance Count • Using Optimal Instance Size • c3.large • Using optimal thread counts • ~200 per instance • Increase instance count • 300 instances • Optimize for costs • EC2 Spot Market
EC2 Spot
c3.large – 300 instances
Summary / tl;dr
Results Small Files – 300 instancesLarge Files – 50 instances
Summary / tl;dr • Parallelize Everything • Instances • Threads • Test, Test, Test • Capture & Analyze Test Data • Less than $5/hr for 300 Instances
EFS Burst Model
Burst Model Based on size of file system Starts w/ 2.1 TiB burst credits Min. burst throughput 100 MiB/s Baseline throughput 50 MiB/s per TiB Burst throughput 100 MiB/s Per TiB
Burst Model Examples File System Size (GiB) Baseline Aggregate Throughput (MiB/s) Burst Aggregate Throughput (MiB/s) Maximum Burst Duration (Min/Day) 10 0.5 100 7.2 512 25 100 360 1024 50 100 720 4096 200 400 720 16384 800 1600 720
Burst Model Current throughput is above baseline… consuming burst credits Throughput(MiB/s) Time Baseline Current
Burst Model Current throughput is below baseline… adding burst credits Throughput(MiB/s) Time Baseline Current
EFS CloudWatch Metrics • DataReadIOBytes • DataWriteIOBytes • MetaDataIOBytes • TotalIOBytes • BurstCreditBalance • PermittedThroughput • ClientConnections • PercentIOLimit Amazon CloudWatch
EFS Economics No minimum commitments or up-front fees No need to provision storage in advance No other fees, charges, or billing dimensions Price: $0.30/GB-Month (US Regions) $0.33/GB-Month (EU Ireland) $0.36/GB-Month (AP Sydney)
EFS TCO example Let’s say you need to store ~500 GB and require high availability and durability Using a shared file layer on top of EBS, you might provision 600 GB (with ~85% utilization) and fully replicate the data to a second Availability Zone for availability/durability Example comparative cost: Storage (2x 600 GB EBS gp2 volumes): $120 per month Compute (2x m4.xlarge instances): $350 per month Inter-AZ data transfer costs (est.): $129 per month Total $599 per month EFS cost is (500GB * $0.30/GB-month) = $150 per month, with no additional charges
Key recommendations • Test your application! • Use General Purpose mode for lowest latency, Max-I/O for scale-out • Use Linux kernel version 4.0 or newer, mount via NFSv4.1 • To optimize, look for opportunities to: • Aggregate I/O • Perform async operations • Parallelize (demo later) • Cache (demo later) • Don’t forget to check your burst credit earn/spend rate when testing – ensure sufficient amount of storage
Reference AWS Loft EFS Hands-on Walk-through - https://bit.ly/awsloft2017 AWS 10-minute Tutorials - https://aws.amazon.com/getting-started/tutorials/ Amazon EFS Web page - https://aws.amazon.com/efs/ YouTube AWS Channel - https://www.youtube.com/user/AmazonWebServices Reference Architecture - https://aws.amazon.com/architecture/ QuickStarts - https://aws.amazon.com/architecture/ qwikLABS - https://aws.qwiklabs.com/
Thank you!

More Related Content

SRV401 Deep Dive on Amazon Elastic File System (Amazon EFS)

  • 1. © 2015, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Yong Kim AWS – Storage Business Development April 18, 2017 Deep Dive on Amazon Elastic File System SRV401 David Green AWS – Enterprise Solutions Architect
  • 2. What customers are using EFS for today Web serving Content management Analytics Media and Entertainment workflows Workflow management Home directories Container storage Database backups
  • 3. Shared File Solutions in the Cloud… before EFS 3rd Party Software Do It Yourself 3rd Party Hardware in AWS Direct Connect locations
  • 4. Do It Yourself – NFS Architecture NFS Clients NFS Server Volume Volume NFS Clients NFS Server Volume Volume NFS Clients NFS Server Volume Volume
  • 5. Do It Yourself – NFS Architecture  Launch, patch, monitor, & pay for EC2 instances  Create, attach, monitor, & pay for provisioned EBS volumes  Create, maintain, and monitor auto scaling group  Install, patch, monitor, & pay for* file system software  Configure, maintain, monitor, & pay for file system data intra/inter-AZ replication • IOPS for replication are still IOPS  Configure DNS for client HA access to inter-AZ NFS fleet
  • 7. Do It Yourself NFS Architecture NFS Clients NFS Server Volume Volume NFS Clients NFS Server Volume Volume NFS Clients NFS Server Volume Volume
  • 9. Do It Yourself – Cost NFS Clients NFS Server Volume Volume NFS Clients NFS Server Volume Volume NFS Clients NFS Server Volume Volume
  • 11. Amazon Elastic File System (EFS) Provides simple, scalable, highly available & durable file storage in the cloud Petabyte scale file system distributed across an unconstrained number of storage servers in multiple Availability Zones (AZs) Elastic capacity, automatically growing & shrinking as you add & remove files
  • 12. Amazon Elastic File System (EFS) Standard file system interface & semantics Shared storage Highly available & highly durable Consistent low latency Strong read-after-write consistency Elastic capacity Fully managed
  • 13. Cloud Data Migration Direct Connect Snow* data transport family 3rd Party Connectors Transfer Acceleration Storage Gateway Kinesis Firehose The AWS Storage Portfolio Object Amazon GlacierAmazon S3 Block Amazon EBS (persistent) Amazon EC2 Instance Store (ephemeral) File Amazon EFS
  • 14. Do you need an EFS file system? If you have an application running on EC2 or use case that requires a file system… AND • Requires multi-attach OR • GBs/s throughput OR • Multi-AZ availability/durability OR • Requires automatic scaling (grow/shrink) of storage
  • 15. Where is EFS available today? • US West (Oregon) • US East (N. Virginia) • US East (Ohio) • EU (Ireland) • Asia Pacific (Sydney) More coming soon!
  • 16. Hands-on: Create an EFS File System (Console)
  • 17. Resources for Amazon EFS File System • Tags • Key-value pairs • Mount Targets • Subnet ID • Security Groups
  • 18. Resources for Amazon EFS File System • Regional construct • Ten per account per region (soft) • Default throughput limit 3 GB/s (soft) • Metered size updates approx. every hour • Accessible from EC2 • VPC, EC2-Classic via ClassicLink • Accessible from on-premises • AWS Direct Connect
  • 19. Resources for Amazon EFS File System cont… • Scenarios for on-prem via Direct Connect Bursting Migration Tiering Backup / DR
  • 20. Resources for Amazon EFS Tags • Typical key-value pair • Create & associate tag with file system • Up to 50 tags per file system
  • 21. Resources for Amazon EFS Mount Targets • One or more per file system • Create in a VPC Subnet • One per Availability Zone • Must be in the same VPC
  • 22. Resources for Amazon EFS Security Groups • Standard VPC Security Group • Same VPC as subnet • Up to five per mount target • Allow inbound TCP port 2049 from NFS clients
  • 23. All EFS AWS CLI Commands aws efs create-file-system aws efs create-mount-target aws efs create-tags aws efs delete-file-system aws efs delete-mount-target aws efs delete-tags aws efs describe-file-systems aws efs describe-mount-target-security-groups aws efs describe-mount-targets aws efs describe-tags aws efs modify-mount-target-security-groups
  • 25. Recommended Mount Options -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,async Mount using NFSv4.1 (default options) Specify 1MB read/write buffers Hard mount Timeout of 60 seconds (600 tenths of a second) 2 minor timeouts & retransmissions before major timeout Ensure operations are asynchronous
  • 26. Mount an EFS File System Launch EC2 instance from EC2 Console Connect to the instance Make a directory Mount EFS file system Query disk file system & file system table • df; df -hT; df -h -t nfsv4; mount -t nfsv4
  • 27. Amazon EFS Architecture NFS Clients Mount Target Availability Zone VPC subnet Amazon EFS EFS File System fs-123456ab Default Default
  • 28. Amazon EFS Architecture NFS Clients Mount Target Availability Zone VPC subnet Amazon EFS VPC subnet EFS File System fs-123456ab Default Default
  • 29. Amazon EFS Architecture NFS Clients Mount Target VPC subnet Amazon EFS Mount Target EFS File System fs-123456ab DefaultDefault Default Default
  • 30. Security Control network traffic using VPC security groups and network ACLs Control file and directory access by using POSIX permissions Control administrative access (API access) to file systems by using AWS Identity and Access Management (IAM) action-level and resource-level permissions
  • 31. High throughput and parallel I/O Low latency and serial I/O Genomics Big data analytics Scale-out jobs Home directories Content management Web serving Metadata-intensive jobs Amazon EFS is designed for wide spectrum of performance needs
  • 32. Performance modes for different workloads Mode What’s it for Advantages Tradeoffs When to use General purpose (default) Latency- sensitive applications and general-purpose workloads Lowest latencies for file operations Limit of 7K ops/sec Best choice for most workloads Max I/O Large-scale and data-heavy applications Virtually unlimited ability to scale out throughput / IOPS Slightly higher latencies Consider for large scale-out workloads
  • 33. EFS CloudWatch Metric - PercentIOLimit Determine whether you’re being constrained by General Purpose mode (PercentIOLimit at or near 100%)
  • 34. EC2 EC2 … EC2 EC2 … EC2 EC2 … • File systems distributed across unconstrained number of servers • Avoids bottlenecks/constraints of traditional file servers • Enables high levels of aggregate IOPS/throughput • Data also distributed across Availability Zones (durability, availability) Amazon EFS - distributed data storage design
  • 35. How to think about EFS perf relative to EBS Amazon EFS Amazon EBS PIOPS Performance Per-operation latency Low, consistent Lowest, consistent Throughput scale Multiple GBs per second Single GB per second Characteristics Data availability / durability Stored redundantly across multiple AZs Stored redundantly in a single AZ Access 1 to 1000s of EC2 instances, from multiple AZs, concurrently Single EC2 instance in a single AZ Use cases Big Data and analytics, media processing workflows, content management, web serving, home directories Boot volumes, transactional and NoSQL databases, data warehousing & ETL
  • 36. I/O size impacts throughput of serialized operations 4 KB 32 KB 256 KB 2 MB 16 MB I/O size Throughput I/O Size Implication
  • 37. Take advantage of EFS’s distributed architecture Parallelize via multiple threads and/or multiple instances 0 5000 10000 15000 20000 25000 30000 0 20 40 60 80 100 120 140 160 IOPS # of Total Threads Aggregate IOPS of parallel writes using 10 m4.xlarge instances Parallelize
  • 38. Previous Scalability Test Small files – 300 instancesLarge files – 50 instances
  • 41. Goal: Move Data Quickly!!
  • 43. Transferring media assets to EFS • Size ranges from a few GB to 100+GB per file • Data sources: • Amazon S3 • Amazon EBS
  • 44. Transferring many small files to EFS • Size ranges from 64K to 256K • Data sources: • Amazon S3 • Amazon EBS
  • 48. How do we do this?
  • 49. GNU parallel • Tool for executing jobs in parallel • Similar to xargs • Replace loops in shell scripts • GNU parallel makes sure output from the commands is the same output as you would get had you run the commands sequentially. https://www.gnu.org/software/parallel/ For people who live life in the parallel lane
  • 50. Use parallel threads – GNU parallel # Create destination directory tree from source find . -type d -print0 | parallel -j $N_THREADS -0 "mkdir -p ${DST_DIR}/{}" > /dev/null 2>&1 # Copy files find . ! ( -type d ) -print0 | parallel -j $N_THREADS -0 "cp - f {} ${DST_DIR}/{}"
  • 52. Monitoring performance • Data-Driven results • Repeatable Outcomes • Optimize for Costs
  • 53. Benchmark different instance types • Determine the optimal instance size • What is best? T2, C3, C4, M3, M4, R3, X? • Transfer test set of 1000 small files • Increase thread count from 1-1024 concurrent threads
  • 54. Tools • Command Orchestration • Instance Configuration • Log Collection • Visualization • Instance performance
  • 55. Test Results – Large Files
  • 56. Large Files: Four Instances
  • 57. Large Files: Four Instances
  • 59. Large File: 50 Instances
  • 60. Test Results – Small Files
  • 61. Small File Performance - Instance Family Test ~200 threads
  • 62. c3.large – 5,342 files per minute @ 200 threads
  • 63. Increase Instance Count • Using Optimal Instance Size • c3.large • Using optimal thread counts • ~200 per instance • Increase instance count • 300 instances • Optimize for costs • EC2 Spot Market
  • 65. c3.large – 300 instances
  • 67. Results Small Files – 300 instancesLarge Files – 50 instances
  • 68. Summary / tl;dr • Parallelize Everything • Instances • Threads • Test, Test, Test • Capture & Analyze Test Data • Less than $5/hr for 300 Instances
  • 70. Burst Model Based on size of file system Starts w/ 2.1 TiB burst credits Min. burst throughput 100 MiB/s Baseline throughput 50 MiB/s per TiB Burst throughput 100 MiB/s Per TiB
  • 71. Burst Model Examples File System Size (GiB) Baseline Aggregate Throughput (MiB/s) Burst Aggregate Throughput (MiB/s) Maximum Burst Duration (Min/Day) 10 0.5 100 7.2 512 25 100 360 1024 50 100 720 4096 200 400 720 16384 800 1600 720
  • 72. Burst Model Current throughput is above baseline… consuming burst credits Throughput(MiB/s) Time Baseline Current
  • 73. Burst Model Current throughput is below baseline… adding burst credits Throughput(MiB/s) Time Baseline Current
  • 74. EFS CloudWatch Metrics • DataReadIOBytes • DataWriteIOBytes • MetaDataIOBytes • TotalIOBytes • BurstCreditBalance • PermittedThroughput • ClientConnections • PercentIOLimit Amazon CloudWatch
  • 75. EFS Economics No minimum commitments or up-front fees No need to provision storage in advance No other fees, charges, or billing dimensions Price: $0.30/GB-Month (US Regions) $0.33/GB-Month (EU Ireland) $0.36/GB-Month (AP Sydney)
  • 76. EFS TCO example Let’s say you need to store ~500 GB and require high availability and durability Using a shared file layer on top of EBS, you might provision 600 GB (with ~85% utilization) and fully replicate the data to a second Availability Zone for availability/durability Example comparative cost: Storage (2x 600 GB EBS gp2 volumes): $120 per month Compute (2x m4.xlarge instances): $350 per month Inter-AZ data transfer costs (est.): $129 per month Total $599 per month EFS cost is (500GB * $0.30/GB-month) = $150 per month, with no additional charges
  • 77. Key recommendations • Test your application! • Use General Purpose mode for lowest latency, Max-I/O for scale-out • Use Linux kernel version 4.0 or newer, mount via NFSv4.1 • To optimize, look for opportunities to: • Aggregate I/O • Perform async operations • Parallelize (demo later) • Cache (demo later) • Don’t forget to check your burst credit earn/spend rate when testing – ensure sufficient amount of storage
  • 78. Reference AWS Loft EFS Hands-on Walk-through - https://bit.ly/awsloft2017 AWS 10-minute Tutorials - https://aws.amazon.com/getting-started/tutorials/ Amazon EFS Web page - https://aws.amazon.com/efs/ YouTube AWS Channel - https://www.youtube.com/user/AmazonWebServices Reference Architecture - https://aws.amazon.com/architecture/ QuickStarts - https://aws.amazon.com/architecture/ qwikLABS - https://aws.qwiklabs.com/