Amazon, Andrew Crutch, Senior Product Manager discussed on AWS Podcast

AWS Podcast
|

Automatic TRANSCRIPT

This is episode two hundred and eighty nine of the AWS podcast released on January thirteenth twenty nineteen. Lorena? Welcome back the adipose podcast Sunday. She here with you. Great to have you back, and I'm joined by very special guests to talk about a very special topic. I'm joined by Andrew crutch, who's is senior product manager for if X at Amazon workum, Andrew, thank you. Now, you I you talk to us today about a new service that I know a lot of customers who'd be waiting for which is Amazon if x four windows file server, and I'm sure all trip over that name at some point today. But one of the things that we're talking at briefly before we started recording the show is that ninety five percent of error map. He's actually created by what customers are asking us to do for them, which is a great way to go. So maybe let's start with that. Why did customers ask us to create the service for them? Absolutely. So a lot of customers that we spoke to when we were initially developing the product, you know, a lot of feedback that they shared was many of these customers have existing windows. Which workloads onto the currently running either on AWS or unpracticed and these are workloads like CRM software. European software done that applications of variety of media processing transporting workloads as well as simple home directories. So things like departmental shares or user shares where you're just storing your files and you want to share it with your teammates. And a core threat across all of these types of workloads is that many of these workloads rely on shared storage that can be broadly accessed from windows instances. And so a lot of these customers are really excited to move these workloads to Italy us, and they're looking for restored solution that can help support these workloads as we were looking at possible solutions, and you know, different alternatives for supporting the storage need. We asked a lot of questions to customers about what what are they need from the storage? You know, what what types of compatibility do they need? What types of features? Do they need? What are they looking for when they're evaluating storage options? And ultimately what a lot of customer. Is shared with us is they're really just looking for a native windows file system. A file system that you know, is compatible with currently doing the file system that has all the features that the currently taking advantage of customers don't want to necessarily need to compare the current solution to something else that exists in in do extensive testing to try to understand which features may or may not work. Exactly the same way. They're really just looking for a solution. That works the way their current solution. Does. You up in replacement anti let just give me what got easier for me. Yep. Exactly. So actually, we looked at a number of different options, including adding SMD support to our existing Amazon elastic file system product SMB as the underlying protocol that a lot of windows. Applications are used when talking to shared file storage. His him. Big. Yeah. I mean, it's sort of another another word that's used for it. And it makes people tweets when you say seeps humane assembly slightly. Yeah. We did. We did. Explore. Adding, you know, a bunch of different protocols to f s an ultimately what we realized was customers are just looking for a solution that works like what they have today. And so as a result that that was sort of the starting point for this product as we envisioned it, and as a result of this feedback that we heard pretty strongly from a large number of customers the product that we actually ended up building Amazon FSX for windows file server is actually built on top of windows server. It's it's powered by windows server software. And as a result, you know, it provides a lot of compatibility for features that customers have come to expect from window storage features like NTFS, like active directory integration features like distributed file system or DFS for replication across sites things like that. That's a really interesting starting point too. Because really what was saying here is the core of the service is built on the windows platform. So there's no kind of emulation or she means all kind of work arounds at my work. Nabet. Quick. Like, these these the the the NBA platform on the windows platform. Exactly. Yup. We really want to allow customers who have existing setup that are running on top of windows based storage to be able to have the same kinds of features the same kinds of compatibility in the cloud as they would today. So let's talk about that. Let's talk about the protocol support. Because it's probably the the starting point for most listeners who are running any kind of windows false is at the moment. It's and be protocol support. What are the versions that customers can use on this earth? So we support our version two point oh newer of the SME protocol. So we support, you know, up to the latest version at this time, which is a believe three point one point one. So we're accessible as a result from a variety of different operating systems, including the newest windows server, twenty sixteen twenty nineteen as well as windows ten but also some of the older versions such as windows server, two thousand thirteen or two thousand eight and windows seven is well, cool, and you could use lyrics to if if Lennox you've got leaked systems currently accessing those fall systems, whatever you can continue says to KAI. Yeah. Absolutely. Yeah. We we do support access to episode for windows file server file systems from Lennox clients. That are running the open source song to plant. Testing. And so let's talk about performance because performance typically is the the main will the first pine if you lock of false serve as which is do I make it run fast enough. And this service is built on is this day storage, which probably can't hurt the throughput in performance aspects Kennett. Yeah. No, absolutely not. Yeah. We we purposely wanted to make sure the product offer customers the performance that they would expect and they would need a lot of their applications. And so as a result, we

Coming up next