1 00:00:00,200 --> 00:00:02,830 ‫Okay, so now let's talk about Amazon FSx, 2 00:00:02,830 --> 00:00:05,340 ‫which is a managed service to get third-party 3 00:00:05,340 --> 00:00:07,380 ‫high-performance file systems on AWS. 4 00:00:07,380 --> 00:00:10,150 ‫So in case you don't wanna use EFS or S3, 5 00:00:10,150 --> 00:00:11,990 ‫and you want something else, then you can use FSX 6 00:00:11,990 --> 00:00:14,100 ‫to manage these file systems. 7 00:00:14,100 --> 00:00:15,300 ‫So you have three offerings today. 8 00:00:15,300 --> 00:00:18,840 ‫You have FSx for Lustre, FSx for Windows File Server, 9 00:00:18,840 --> 00:00:20,840 ‫and FSx for NetApp ONTAP. 10 00:00:20,840 --> 00:00:23,090 ‫And they can add file systems over time 11 00:00:23,090 --> 00:00:24,420 ‫to the FSx service, I'm pretty sure, 12 00:00:24,420 --> 00:00:26,080 ‫but they will not update this video 13 00:00:26,080 --> 00:00:28,440 ‫unless you need to know about the other ones. 14 00:00:28,440 --> 00:00:30,500 ‫So the two most important ones are going to be 15 00:00:30,500 --> 00:00:33,620 ‫FSx for Lustre, and FSx for Windows File Server, 16 00:00:33,620 --> 00:00:35,973 ‫and this is what is covered in this lesson. 17 00:00:36,990 --> 00:00:40,300 ‫The first one is Amazon FSx for Windows File Server, 18 00:00:40,300 --> 00:00:42,920 ‫which is a fully managed, highly reliable and scalable 19 00:00:42,920 --> 00:00:45,250 ‫Windows native shared file system 20 00:00:45,250 --> 00:00:46,910 ‫built on Windows File Server. 21 00:00:46,910 --> 00:00:49,970 ‫So this is meant for Windows instances. 22 00:00:49,970 --> 00:00:52,180 ‫So the way you do it is that deploy the FSx 23 00:00:52,180 --> 00:00:54,530 ‫usually across two availability zones, 24 00:00:54,530 --> 00:00:55,730 ‫and then there is support 25 00:00:55,730 --> 00:00:57,960 ‫for all the Windows native protocols, 26 00:00:57,960 --> 00:01:01,520 ‫such as the SMB protocol and Windows NTFS, 27 00:01:01,520 --> 00:01:03,430 ‫which allows you to mount this file system 28 00:01:03,430 --> 00:01:04,980 ‫onto your Windows machines. 29 00:01:04,980 --> 00:01:06,487 ‫And so if you look at your corporate data center 30 00:01:06,487 --> 00:01:08,570 ‫and you have a Windows Client, for example, 31 00:01:08,570 --> 00:01:12,830 ‫over SMB, it's able to access the Windows file server. 32 00:01:12,830 --> 00:01:15,440 ‫But also if you had EC2 instances that are Windows based, 33 00:01:15,440 --> 00:01:17,370 ‫and then they could also might as well 34 00:01:17,370 --> 00:01:18,830 ‫access this Windows file server. 35 00:01:18,830 --> 00:01:22,720 ‫So Amazon FSx is the way to deploy this Windows file server 36 00:01:22,720 --> 00:01:26,210 ‫that leverages the SMB protocol and Windows NTFS. 37 00:01:26,210 --> 00:01:29,560 ‫Because this is also a Microsoft type of offering, 38 00:01:29,560 --> 00:01:32,070 ‫there is integration with Microsoft Active Directory 39 00:01:32,070 --> 00:01:37,070 ‫for user security and Windows file server in Amazon FSx 40 00:01:37,120 --> 00:01:39,550 ‫can be accessed from AWS directly, 41 00:01:39,550 --> 00:01:41,810 ‫or as you can see on this diagram 42 00:01:41,810 --> 00:01:44,510 ‫from your on-premises infrastructure. 43 00:01:44,510 --> 00:01:47,970 ‫Now, the second flavor of Amazon FSx you have in AWS 44 00:01:47,970 --> 00:01:50,390 ‫is called Amazon FSx for Lustre. 45 00:01:50,390 --> 00:01:52,260 ‫And you need to remember that this says to have 46 00:01:52,260 --> 00:01:55,840 ‫a fully managed, high-performance and scalable file storage 47 00:01:55,840 --> 00:01:57,420 ‫for high performance computing. 48 00:01:57,420 --> 00:01:59,990 ‫So whenever you see storage for HPC, 49 00:01:59,990 --> 00:02:03,200 ‫so high-performance computing, thinks FSx for Lustre. 50 00:02:03,200 --> 00:02:05,550 ‫Why, well Lustre, there is derived from the name 51 00:02:05,550 --> 00:02:08,180 ‫Linux and cluster, so put together it's Lustre. 52 00:02:08,180 --> 00:02:10,270 ‫And so imagine cluster like processing 53 00:02:10,270 --> 00:02:12,360 ‫this kind of things, maybe it's a way for you to remember 54 00:02:12,360 --> 00:02:14,750 ‫what Amazon FSx for Lustre is. 55 00:02:14,750 --> 00:02:17,140 ‫This allows you to run a lot of use cases 56 00:02:17,140 --> 00:02:20,040 ‫for high performance computing, such as machine learning, 57 00:02:20,040 --> 00:02:23,310 ‫analytics, video processing, financial modeling, 58 00:02:23,310 --> 00:02:25,420 ‫and it scales to extremely high traffics 59 00:02:25,420 --> 00:02:27,550 ‫in terms of hundreds of gigabytes per second 60 00:02:27,550 --> 00:02:31,570 ‫of data exchanged, millions of IO operations per second, 61 00:02:31,570 --> 00:02:33,130 ‫sub milliseconds latency, 62 00:02:33,130 --> 00:02:35,700 ‫so it's really a high-performance file system. 63 00:02:35,700 --> 00:02:37,580 ‫So the way it works is that Amazon FSx for Lustre 64 00:02:37,580 --> 00:02:40,680 ‫can be connected either to your corporate data center 65 00:02:40,680 --> 00:02:44,200 ‫or to your compute instances directly within AWS. 66 00:02:44,200 --> 00:02:46,810 ‫And then in the backend, Amazon FSx for Lustre 67 00:02:46,810 --> 00:02:48,600 ‫is actually storing your data, 68 00:02:48,600 --> 00:02:52,000 ‫possibly onto an Amazon S3 bucket. 69 00:02:52,000 --> 00:02:54,020 ‫So that's it, that's all you need to know for Amazon FSx 70 00:02:54,020 --> 00:02:55,760 ‫there is no easy hands-on to do it. 71 00:02:55,760 --> 00:02:58,540 ‫So we'll skip that, but just remember the two flavors 72 00:02:58,540 --> 00:03:00,350 ‫of Amazon FSx going into the exam, 73 00:03:00,350 --> 00:03:01,930 ‫and you should be good to go. 74 00:03:01,930 --> 00:03:04,403 ‫So that's it, I will see you in the next lecture.