 Hi everybody, this is Dave Vellante, and welcome to Storage Day. We're here at Amazon and Boston, and you're watching theCUBE. Wayne Duso is here. He's the general manager of a lot of stuff. File, hybrid, edge, transfer, and data protection services at Amazon Web Services. Good to see you, Wayne, thanks. Good to see you. So let's talk about that. That's a pretty vast portfolio that you have. Explain that to our audience. Sure thing. So the portfolio that I'm responsible for covers a vast swath of our storage portfolio at AWS. So in that, we cover all of our file services. So that's EFS and FSX, our data transport services, which includes data sync, transfer for SFTP, and our snowball or snow services, and then also a hybrid edge, which includes our snowball compute and our storage gateway services, and then data protection, which includes AWS backup. Wow, okay. Great, congratulations on that portfolio. You know, I said earlier on, it started with S3 and it's just exploded now into all these services. This is part of what we sometimes call Tung and Cheek Cloud 2.0. There's more workloads, more capabilities, more granularity. But talk about some of the big picture macro trends that you guys see in the marketplace, specific to sort of your area. Yeah, so it actually is so many. As you said, things are expanding, things are accelerating in our space. One of the things I like to talk about with respect to our portfolio is we have storage services, data transport services to match the needs of your workloads and your applications. So all of these services are purpose built for the type of storage that you need, the programming model that you need for your applications and workloads. So whether it's object storage with S3 and Glacier, or block storage with EBS, or most recently, file service with EFS and FSX file services. So you have the tools at your disposal that you need based on your application workloads. Talk more about the programming model. How do you envision that? What's your mental model of the different programming? Sure, so forever. People have been programming based on whether it's performance or scale of some sort. Database is traditionally used block storage because they don't need a lot of logic between them and the storage medium itself. File storage has been used for 50 years and has a very specific program model that exists in every operating system in every programming language. Whether it's an open, a read, write, seek, close, it's a common paradigm that is used all over the place and that capability in the performance that you need to satisfy those applications and workloads is very specific. And so for AWS, we provide those file systems for Linux, if you would, with EFS, Windows, which is FSX for Windows, and for very high performance computing on Luster. We've had an amazing storage platform, which is S3. And S3 forms the basis for a lot of our customers, data lakes and basically storage data repositories for which there are many integrations with that through our other storage services. I often joke that if your expertise is unpacking boxes, plugging in, setting up storage arrays, managing luns, you might want to think about updating your skill sets, right? But so that's the other big mega trend that we certainly see is people just don't see a lot of value in planning and managing and migrating over six month periods storage arrays. It's something that really doesn't add a lot of value to the business. So you guys have announced all these services over the years and you've got some new announcements as well that kind of play into some of the trends that we've been talking about. Talk about the news. Yeah, so the news is pretty rich for this season. Let's start off with FSX. So FSX is our service for bringing fully managed third party or open source file systems to our customers. And so FSX Windows, as example, was launched last year at ReInvent and has been rolling out a whole series of features throughout the year. And we have a nice set of features coming out this year. So as example, today FSX Windows is a single AZ service. We are rolling out multi-AZ capability. Okay, and sometimes you guys make the point that the beauty is there's no change required in apps. We talked earlier about the program model, but talk a little bit more about that. Why is that important to customers? You know, and I'll index on FSX Windows for another minute. A lot of apps have been written to use the semantics of a particular file system. In case of Windows, we'll say NTFS. And they're written for that specific file system. We've provided customers with the capability of bringing those applications to AWS without any worry of compatibility. It's a pure lift and shift model. So it makes it really easy for them to bring their workloads. They should bring their workloads so they don't have to deal with some of the things you brought up earlier around provisioning, buying systems, having to worry about setting up planning for all of that. We take all of that work away from them and they get full compatibility based on what they need today. And with some of the additional capabilities we're bringing to bear with the integrations in the ecosystem, the AWS ecosystem, they'll be able to appreciate those as well. Let's talk a little bit more about that because you're basically, I'm inferring, you're saying, hey, there's compelling reasons why you should move into the cloud, for instance, file services into the cloud. What's the difference between my on-prem, is it just on-prem NAS stuffing in into the cloud or is it more than that? You touched on integration, so convince me. Why should I move? It's so much more than that. So if we look at the basic infrastructure, once you literally click three or four buttons to start a file system, create a file system, you no longer have to worry about it ever again. So the things that you would have done on-prem, you no longer have to worry about having a storage administrator or having to provision and buy storage and maintain it. We take care of all that. We take care of all the security elements. I'm so important to your data to make sure that it's in a secure environment. Security is job number one for us. So all of these capabilities and the ability to stand it up, to never have to manage it, never have to worry about the security, we take care of all the capabilities. Like, you should really be bringing those workloads onto a platform like this so that you can spend your time on added value services or applications for your business. Well, and the integration is also a key piece of it. I mean, for years, customers still sometimes want to roll their own. They like to have the knobs and turn them, but many customers that we talk to are saying, listen, it's too expensive. I don't want to be a systems integrator anymore. In the cloud, how can they take advantage of those, like sometimes they call it the flywheel effect, but the other innovations that you're bringing, whether it's machine learning or other services that you guys are bringing in, is that, how tight is that integration? So those integrations are ongoing and they're forever. It goes back to what I said a minute ago around. Over a three year period, all of these capabilities are going to be delivered to them if you would at the same cost as the basic service. So let's talk about what happened this year. A lot of our customers are using SageMaker for their ML and AI capabilities, and SageMaker is deeply integrated with both FSX Luster and EFS, so that customers, again, don't have to worry about stories, they don't have to worry about sharing, they don't have to worry about scaling. It's all there for them. You mentioned also, you're responsible for the snow products, you mentioned an edge. I always, to me, it was your first, you know, move to hybrid, I'll call it, but I always joke that, but it's true, the fastest way to get data from point A to point B is a Chevy truck, and so, but you're referring to it as sort of an edge play. Maybe talk a little bit more about that, help us understand it. Sure, so Snowball, as a service, was launched about five years ago. We initially launched a service as a bulk data migration service, and it's been that service for roughly four years. About a year ago, a little over a year ago, we started introducing the ability to have compute as part of that device, and the reason for that was customers were telling us, as we're moving the data, we would like to be able to do some pre-processing before it makes it onto AWS, before it goes into S3, as an example. So we started providing that capability. That ended up expanding into a full-blown, if you would, cloud platform on a device that can be run in disconnected environments or a stair environments. So with Snowball today, we have the ability to have EC2 instances, EBS storage, S3 storage, all in one device. And so that's a really powerful construct because you can build your applications on AWS using the same services, prove out, if you wouldn't dev-ups model, that they're what you need to be, and then literally lift them onto a Snowball device and have those executing in the field as if they were running directly in the cloud. Changing subject a little bit, when I look at the logo slide of all your customers, a lot of big names on there, they're global companies, and a lot of times people say, oh, I run a cloud and they got a data center, you know, East Boston or something, no offense if you have a data center in East Boston, but regions are critical, especially for global scale. I mean, cloud brings global scale, but it's also important to have data approximate to the users, so you're reducing latency, there's an availability and redundancy aspects. Talk about your philosophy around regions and how it fits into your portfolio. How do you take advantage of all that capability? So a lot of our customers have global presence and the ability for them to have their application, to have their business function in the regions that they're doing business and have those low latencies. And also the availability model of being in multiple places in case of disasters, super important. Our regions are built to have at minimum three availability zones, and an availability zone you can think about as a data center. So for example, with EFS, when you stand up a file system with EFS, your file system is automatically distributed, replicated across all three availability zones within that region, but as the user, you don't worry about any of that. We take care of it all for you. And in the unfortunate event that an availability zone is made unavailable, your data is still fine. You still have access to that data all the time. Yeah, and your customers are, I think, increasingly understanding this, they're beginning to architect around regions and availability zones. It's a different way of thinking, but it's in some respects sort of a modern way of thinking. Yeah, if you go back a few years and you think about all of the disaster recovery or business continuance software and capabilities that had been created, we're providing all of those capabilities today in our regional construct. Yeah, well, you know this. I mean, we've both been around for a while and we've seen the unnatural acts that you had to do to sort of create that level of redundancy and business continuance. And it was extremely expensive, complex, and really risky to test. So I'll leave you with the last word. Any other thoughts that you want to share with our audience? We're just, first off, thank you for giving me the time today. We're really excited about what we're doing with each of these services. We're very excited about the portfolio overall and the value that it's going to bring and is bringing to our customers today. We're excited about all the announcements. Yeah, we're seeing a lot of innovation, expansion of the Amazon portfolio, optionality, granularity, performance, Horses for Courses, the right tool for the right job way. Thanks so much for coming to theCUBE. My pleasure, thank you. All right, you're welcome. All right, keep it right there, everybody. You're watching theCUBE, storage day from Amazon and Boston. We'll be right back.