(upbeat music) >> Hi everybody, we're here in downtown Seattle covering AWS storage day. My name is Dave Vellante with the Cube, and we're really excited. We're going to talk about rethinking data protection in the 2020s. I'm here with Nancy Wong, who is the general manager of AWS backup, and Satish Lakshmanan, the director of storage business development at AWS. Folks, welcome. Good to see you again. So let's talk about the evolution of data protection. You've got three major disruptors going on. There's obviously the data explosion. We talk about that all the time, but there's cloud has changed the way people are thinking about data protection and now you've got cyber. What's AWS's point of view on all this. >> Great question, Dave. You know, in my role as the global head of storage business development and solution architecture for storage, I have the privilege of working with customers all around the globe, in every geography and every segment. And we recently talked to thousands of customers and we did a survey for about 5,000 customers. And many of them told us that they expect to see a ransomware attack once every 11 seconds. So it's top of mind for almost every customer so much so that if you remember earlier this year, the white house issued an executive order, you know, making the nation aware of across public and private sector about cybersecurity and the need for, for, for us to be prepared. Customers as a result, largely think of not only ransomware protection, but also recovery. And they have largely allocated budgets across every geography to make sure that they're well protected. And in the, in the event of an attack, they can recover from it. That's where Nancy's, you know, data protection services and backup services come into play. And maybe she'll add a few comments about how she approaches it from a technology perspective. >> Yeah, sure. Thanks, Satish yeah, as a general manager of AWS backup and our data protection services, it's really my team and my charter to help our customers centralize, automate, and also protect themselves from attacks like ransomware. Right? And so for example, you know, across our many services today we offer AWS backup as a secondary data collection and management across our many AWS regions and also across the aid of many AWS accounts that a single customer must manage, right. And if you recall having multiple copies of your data exist in backups is a core part of any customers ransomware protection strategy. And lastly, I just want to say something that we just launched recently called AWS backup audit manager also helps you operationalize and monitor your backups against any ransomware attack. >> So, the adversary, obviously, as we know, was well-equipped and they're quite sophisticated. And anybody who has inside access can become a ransomware attacker because of things like ransomware as a service. So, what are you specifically doing to address ransomware? >> Yeah. So, in talking to several thousand of our customers, what we have learned is customers are typically vulnerable in one or more of three scenarios, right? The first scenario is when they're not technically ready. What that means is either their software patches are not up to date, or they have too many manual processes that really prevent them from being prepared for defending against an attack. The second is typically around a lack of awareness. These are situations where IT administrators leveraging cloud-based services are recognizing that, or not recognizing per se, that they're easy to instances, Lambda instances have public access and same applies to S3 buckets. And the third is lack of governance and governance based practices. The way we are educating our customers training in enabling them and empowering them, because it's a shared security model, is really through our well-architected framework. That's the way we shared best practices that we have learned across all our customers, across our industries. And we enable it and empower them to not only identify areas of vulnerability, but also be able to recover in the event of an attack. Nancy. >> Yeah, and to add to that right, our team, and now my team and I, for example, watch every ransomware incident and because it really informs the way that we plan our product roadmap and deliver features that help our customers protect, detect, and also recover from ransomware. So there's an ebook out there, suggest you go check it out, of securing your cloud environment against ransomware attacks. And aside from the technical maintenance suggestions that Satish provided, as well as the security awareness suggestions, there's really two things that I usually tell customers who come to me with ransomware questions. Which is one, right, don't rely on the good will of your ransomware attacker to restore your data. Because I mean, just studies show over 90% of ransom payers actually don't successfully recover all of their data because, hey, what if they don't give you the full decryption utility? Or what if your backups are not restorable? Right? So, rather than relying on that good will, make sure that you have a plan in place where you can recover from backups in case you get ransomed. Right? And two, is make sure that in addition to just taking backups, which obviously, you know, as a GM of AWS backup, I would highly recommend you do, right. Is make sure that those backups are actually restorable, right? Do game day testing, make sure that it's configured properly because you'd be surprised at the, just the number and the sheer percentage of customers who when, let's say the attack happens, actually find that they don't have a good set of data to recover their businesses from. >> I believe it. Backup is, one thing as they say, recovery is everything. So you've got the AWS well-architected framework. How does that fit in, along with the AWS data protection services into this whole ransomware discussion? >> Yeah, absolutely. You know, the AWS wall architected framework actually has four design approaches that I usually share with customers that are very relevant to the ransomware conversation. And one is, you know, anticipate where that ransomware attack may come from. Right? And two, make sure that you write down your approaches whereby you can solve for that ransomware attack, right? Three, just like I advocate my teams and customers to do, right. Then look back on what you've written down as your approach and reflect back on what are the best practices or lessons learned that you can gain from that exercise. And make sure as part four, is you consistently plan game days where you can go through these various scenario tests or ransomware game day attacks. And lastly, just as a best practice is ransomware recovery and protection isn't just the role of IT Professionals like us, right. It's really important to also include HR, professional, legal professionals. Frankly, anyone in a business who might come and be compromised by ransomware attack, and make sure that they're involved in your response. And so Satish, I'd love to hear as well, how you communicate to customers and what best practices you offer them. >> Yeah, thanks Nancy. I think in addition to the fantastic points you made, Nancy, Dave, the well architected framework has been built on eight to 10 years worth of customer engagements across all segments and verticals. And essentially it's a set of shared best practices, tools, training, and methodology that we, you know, exchange with customers in order to help them be more prepared to fight ransomware attacks and be able to recover from them. Recently, there've been some enhancements made where we have put industry or use case specific lenses to the well architected framework. For example, for customers looking to build IOT applications, customers who are trying to use server less and Lambda functions, customers who may be within the financial services or healthcare life sciences, where to go, looking to understand best practices from other people who've implemented, you know, some of the technologies that Nancy talked about. In addition, as I talked about earlier, training and enablement is extremely critical to make sure that if companies don't have the skillset, we are basically giving them the skillset to be able to defend. So we do a lot of hands-on labs. Lastly, the well architected framework tool has been integrated into the console, and it gives customers who are essentially managing the workloads, the ability to look at access permissions, ability to look at what risks they have through malware and ransomware detection techniques. Machine learning capability is built into all the services that are native to AWS that allow them to then react to them. If companies don't have the skills, we have a vast network of partners who can help them basically implement the right technologies. And they can always reach out to our technical account manager for additional information as well. >> I love the best practice discussion. For customers, it's a journey. I mean, CSOs tell us their one problem is lack of talent and so they need help. So, last question is what can people expect from AWS? You're the experts. In particular, how you can help them recover from ransomware? >> Yeah, and that conversation is ever evolving, right? As hackers get more sophisticated then clearly we have to get more sophisticated as well. And so one of our mental models that we often share with customers is defense in depth, right? So if you consider all of the layers, including all of the constructs that exist natively on AWS, right? The first layer is through identity access management constructs. So building a trust radius around your workloads, around your applications, whereby you can deny permissions or access permissions to individuals who are not authorized to access your mission critical applications, right. Then beyond that first layer of defense, the second layer should be automated monitoring or observability. For example, if individuals were to penetrate within your security perimeter, and often times I, you know, that could be done through a delayed response where it gives your CSO or your security operations team, the ability to react to such a unauthorized access, for example. And so the third line of defense is if someone were to penetrate both first layer, as well as the second layer, is actually through backups. And this is where it goes back to what I was mentioning earlier is make sure that your backups are ready and able to be restored and have the RTO and SLA guarantees that help your business remain functional even after an attack. >> Excellent. Guys, we got to go. I love that, zero trust layer defenses, got to have the observability in the analytics and then the last resort RTO, and of course, RPO. Guys, thanks so much, really appreciate your insights. >> Good to see you. >> Thank you for watching. Keep it right there for more great content from AWS storage day. (upbeat music)

>>We'll go back to the queue. It's continuous coverage of AWS storage day. We're here in Seattle home with the Mariners home, with the Seahawks home of the Seattle storm. If you're a w NBA fan your cloud migration, according to our surveys and the ETR data that we use last year was number two initiative for it. Practitioners behind security. Welcome to this power panel on migration and transfer services. And I'm joined now by Matt Matthews. Who's the general manager of AWS transfer a family of services sitting. Roy is the GM of the snow family. And Randy boudin is the general manager of AWS data sync, gents. Welcome to good to see you. Thank you. So, Matt, you heard my narrative upfront, obviously it's top of mind for it. Pros, what are you seeing in the marketplace? >>Yeah, uh, certainly, um, many customers are currently executing on data migration strategies, uh, to the cloud. And AWS has been a primary choice for cloud storage for 15 years. Right. Um, but we still see many customers are evaluating, um, how to do their cloud migration strategies. And they're looking for, you know, um, uh, understanding what services can help them with those migrations. >>So said, well, why now? I mean, a lot of people might be feeling, you know, you got, you've got a hesitancy of taking a vaccine. What about hesitancy making a move? Maybe the best move is no movable. W why now? Why does it make sense? >>So AWS offers compelling, uh, cost savings to customers. I think with our global footprint that our 11 nines of durability are fully managed services. You're really getting the centralization benefits for the cloud, like all the resiliency and durability. And then besides that you are unlocking the on-prem data center and data store costs as well. So it's like a dual prong cost saving on both ends >>Follow up on that. If I may, I mean, again, the data was very clear cloud migration, top priority F for a lot of reasons, but at the same time migration, as you know, it's almost like a dirty word sometimes in it. So, so where do people even start? I mean, they've got so much data to migrate. How can they even handle >>That? Yeah. I'd recommend, uh, customers look at their cool and cold data. Like if they look at their backups and archives and they have not been used for long, I mean, it doesn't make sense to kind of keep them on prem, look at how you can move those and migrate those first and then slowly work your way up into like warm data and then hot data. >>Okay, great. Uh, so Randy, we know about the snow family of products. Of course, everybody's familiar with that, but what about online data migration? What can you tell us there? What's the, what are customers thinking >>About? Sure. So as you know, for many their journey to the cloud starts with data migration, right? That's right. So if you're, if you're starting that journey with, uh, an offline movement, you look to the snow family of products. If you, if you're looking for online, that's when you turn to data, sync data thinks that online data, movement, service data is it makes it fast and easy to move your data into AWS. The customers >>Figure out which services to use. Do you, how do you advise them on that? Or is it sort of word of mouth, peer to peer? How do they figure it out that that's squint through that? Yeah, >>So it comes down to a combination of things. So first is the amount of available bandwidth that you have, the amount of data that you're looking to move and the timeframe you have in which to do that. Right. So if you have a, high-speed say gigabit, uh, uh, network, uh, you can move data very quickly using data sync. If, if you have a slower network or perhaps you don't want to utilize your existing network for this purpose, then the snow family of products makes a lot of sense. Call said, that's it? Call center. That's >>My answer. Yeah, there you go. Oh, you'll >>Joke. Right. See Tam that's Chevy truck access method. You put it right on there and break it over. How about, you know, Matt, I wonder if we could talk maybe about some, some customer examples, any, any favorites that you see are ones that stand out in various industries? >>Yeah. So one of the things we're seeing is certainly getting your data to the cloud is, is important, but also customers want to migrate their applications to the cloud. And when they, when they do that, they, uh, the many applications still need ongoing data transfers from third parties, from ex partners and customers and, and whatnot. So, great example of this is, uh, FINRA and their partnership with AWS. So a FINRA is the single largest, um, uh, regulatory body for securities in the U S and they take in 335 billion market events per day, over 600,000 of their member brokers, registered brokers. So, uh, they use, um, AWS transfer family, uh, secure file transfers, uh, to get that data in an aggregated in, in S3, so they can, um, analyze it and, and, uh, really kind of, uh, understand that data so they can protect investors. So that's, that's a great example. >>So it's not just seeding the cloud, right? It's the ongoing population of it. How about, I mean, how do you guys see this shaping up the future? We all talk about storage silos. I see this as, you know, the cloud is in some ways a silo Buster. Okay. We've got all this data in the cloud now, but you know, you can not apply machine learning. There are other tooling, so what's the north star here. >>Yeah. It's really the north star of getting, you know, we want to unlock, uh, not only get the data in the cloud, but actually use it to unlock the benefits of the cloud has to offer. Right. That's really what you're getting at, aggregating all that data, uh, and using the power of the cloud to really, um, you know, harness that power to analyze the data. It's >>A big, big challenge that customers have. I mean, you guys are obsessed listening to customers, you know, w what kinds of things do you see in the future? Sid and Randy, maybe, maybe see if you can start, >>Uh, I'll start with the I'll kind of dovetail, on example, a Matthews, uh, I'll talk about a customer join, who moved 3.4 petabytes of data to the cloud joined was a streaming service provider out of Germany. They had prohibitive on-prem costs. They saved 500 K per year by moving to the cloud. And by moving to the cloud, they get much more of the data by being able to fine tune their content to local audiences and be more reactive and quicker, a reaction to business changes. So centralizing in the cloud had its benefits of access, flexibility, agility, and faster innovation, and faster time to market. Anything you'd add, right. >>Yeah, sure. So we have a customer Takara bio they're a biotech company. Uh, they're working with genome sequencing, right? So data rich information coming out of those sequencers, they're collecting and analyzing this data daily and sending it up into AWS for analysis, um, and, uh, by using data sync in order to do that, they've improved their data transfer rate by three times. And they've reduced their, uh, overhead six by 66% in terms of their process. >>Guys get, must be blown away by this. I mean, we've all sort of lived in this, so I'm prem world and you sort of lay it out infrastructure, and then you go onto the next one, but the use cases are so diverse. The industry, examples. Matt will give you the last >>Word here. Yeah, no, w w what are we looking to do? You know, we, we always want to listen to our customers, uh, but you know, collectively our, our services and working across other services, AWS, we really, uh, want to help customers not only move their data in the crowd, but also unlock the power of that data. And really, um, you know, uh, we think there's a big opportunity across their migration and transfer services to help customers choose, choose the right service, uh, based on their, where they are in their cloud migration, uh, and, and all the different things they're dealing with. >>I've said a number of times the next 10 years is not going to be like the last 10 years. It's like the cloud is growing up. You know, it's out of the infancy stage. Maybe it's an adolescent. So I don't really know exactly, but guys, thanks so much for coming to the cube and sharing your insights and information. Appreciate it. And thank you for watching everybody keep it right there. More great content from AWS storage day in Seattle.

(bright music) >> Welcome to this next session of AWS Storage Day. I'm your host, Dave Vellante of theCUBE. And right now we're going to explore how to simplify and evolve your data lake backup disaster recovery and analytics in the cloud. And we're joined by Kevin Miller who's the general manager of Amazon S3. Kevin, welcome. >> Thanks Dave. Great to see you again. >> Good to see you too. So listen, S3 started as like a small ripple in the pond and over the last 15 years, I mean, it's fundamentally changed the storage market. We used to think about storage as, you know, a box of disc drives that either store data in blocks or file formats and then object storage at the time it was, kind of used in archival storage, it needed specialized application interfaces, S3 changed all that. Why do you think that happened? >> Well, I think first and foremost, it's really just, the customers appreciated the value of S3 and being fully managed where, you know, we manage capacity. Capacity is always available for our customers to bring new data into S3 and really therefore to remove a lot of the constraints around building their applications and deploying new workloads and testing new workloads where they know that if something works great, it can scale up by a 100x or a 1000x. And if it doesn't work, they can remove the data and move on to the next application or next experiment they want to try. And so, you know, really, it's exciting to me. Really exciting when I see businesses across essentially every industry, every geography, you know, innovate and really use data in new and really interesting ways within their business to really drive actual business results. So it's not just about building data, having data to build a report and have a human look at a report, but actually really drive the day-to-day operations of their business. So that can include things like personalization or doing deeper analytics in industrial and manufacturing. A customer like Georgia-Pacific for example, I think is one of the great examples where they use a big data lake and collect a lot of sensor data, IoT sensor data off of their paper manufacturing machines. So they can run them at just the right speed to avoid tearing the paper as it's going through, which really just keeps their machines running more and therefore, you know, just reduce their downtime and costs associated with it. So you know, it's just that transformation again, across many industries, almost every industry that I can think of. That's really what's been exciting to see and continue to see. I think we're still in the really early days of what we're going to see as far as that innovation goes. >> Yeah, I got to agree. I mean, it's been pretty remarkable. Maybe you could talk about the pace of innovation for S3. I mean, if anything, it seems to be accelerating. How Kevin, does AWS, how has it thought about innovation over the past decade plus and where do you see it headed? >> Yeah, that's a great question Dave, really innovation is at our core as part of our core DNA. S3 launched more than 15 years ago, almost 16 years old. We're going to get a learner's permit for it next year. But, you know, as it's grown to exabytes of storage and trillions of objects, we've seen almost every use case you can imagine. I'm sure there's a new one coming that we haven't seen yet, but we've learned a lot from those use cases. And every year we just think about what can we do next to further simplify. And so you've seen that as we've launched over the last few years, things like S3 Intelligent Tiering, which was really the clouds first storage class to automatically optimize and reduce customer's costs for storage, for data that they were storing for a long time. And based on, you know, variable access patterns. We launched S3 Access Points to provide a simpler way to have different applications operating on shared data sets. And we launched earlier this year S3 Object Lambda, which really is, I think, cool technology. We're just starting to see how it can be applied to simplify serverless application development. Really the next wave, I think, of application development that doesn't need, not only is the storage fully managed, but the compute is fully managed as well. Really just simplify that whole end to end application development. >> Okay, so we heard this morning in the keynote, some exciting news. What can you tell us, Kevin? >> Yeah, so this morning we launched S3 Multi-Region Access Points and these are access points that give you a single global endpoint to access data sets that can span multiple S3 buckets in different AWS regions around the world. And so this allows you to build these multi-region applications and multi-region architectures with, you know, with the same approach that you use in a single region and then run these applications anywhere around the world. >> Okay. So if I interpret this correctly, it's a good fit for organizations with clients or operations around the globe. So for instance, gaming, news outlets, think of content delivery types of customers. Should we think about this as multi-region storage and why is that so important in your view? >> Absolutely. Yeah, that is multi-region storage. And what we're hearing is seeing as customers grow and we have multinational customers who have operations all around the world. And so as they've grown and their data needs grow around the world, they need to be using multiple AWS regions to store and access that data. Sometimes it's for low latency so that it can be closer to their end users or their customers, other times it's for regions where they just have a particular need to have data in a particular geography. But this is really a simple way of having one endpoint in front of data, across multiple buckets. So for applications it's quite easy, they just have that one end point and then the data, the requests are automatically routed to the nearest region. >> Now earlier this year, S3 turned 15. What makes S3 different, Kevin in your view? >> Yeah, it turned 15. It'll be 16 soon, you know, S3 really, I think part of the difference is it just operates at really an unprecedented scale with, you know, more than a hundred trillion objects and regularly peaking to tens of millions of requests per second. But it's really about the resiliency and availability and durability that are our responsibility and we focus every single day on protecting those characteristics for customers so that they don't have to. So that they can focus on building the businesses and applications that they need to really run their business and not worry about the details of running highly available storage. And so I think that's really one of the key differences with S3. >> You know, I first heard the term data lake, it was early last decade. I think it was around 2011, 2012 and obviously the phrase has stuck. How are S3 and data lakes simpatico, and how have data lakes on S3 changed or evolved over the years? >> Yeah. You know, the idea of data lakes, obviously, as you say, came around nine or 10 years ago, but I actually still think it's really early days for data lakes. And just from the standpoint of, you know, originally nine or 10 years ago, when we talked about data lakes, we were looking at maybe tens of terabytes, hundreds of terabytes, or a low number of petabytes and for a lot of data lakes, we're still seeing that that's the kind of scale that currently they're operating at, but I'm also seeing a class of data lakes where you're talking about tens or hundreds of petabytes or even more, and really just being used to drive critical aspects of customer's businesses. And so I really think S3, it's been a great place to run data lakes and continues to be. We've added a lot of capability over the last several years, you know, specifically for that data lake use case. And we're going to continue to do that and grow the feature set for data lakes, you know, over the next many years as well. But really, it goes back to the fundamentals of S3 providing that 11 9s of durability, the resiliency of having three independent data centers within regions. So the customers can use that storage knowing their data is protected. And again, just focus on the applications on top of that data lake and also run multiple applications, right? The idea of a data lake is you're not limited to one access pattern or one set of applications. If you want to try out a new machine learning application or something, do some advanced analytics, that's all possible while running the in-flight operational tools that you also have against that data. So it allows for that experimentation and for transforming businesses through new ideas. >> Yeah. I mean, to your point, if you go back to the early days of cloud, we were talking about storing, you know, gigabytes, maybe tens of terabytes that was big. Today, we're talking about hundreds and hundreds of terabytes, petabytes. And so you've got huge amount of information customers that are of that size and that scale, they have to optimize costs. Really that's top of mind, how are you helping customers save on storage costs? >> Absolutely. Dave, I mean, cost optimization is one of the key things we look at every single year to help customers reduce their costs for storage. And so that led to things like the introduction of S3 Intelligent Tiering, 10 years ago. And that's really the only cloud storage class that just delivers the automatic storage cost savings, as data access patterns change. And, you know, we deliver this without performance impact or any kind of operational overhead. It's really intended to be, you know, intelligent where customers put the data in. And then we optimize the storage cost. Or for example, last year we launched S3 Storage Lens, which is really the first and only service in the cloud that provides organization-wide visibility into where customers are storing their data, what the request rates are and so forth against their storage. So when you talk about these data lakes of hundreds of petabytes or even smaller, these tools are just really invaluable to help customers reduce their storage costs year after year. And actually, Dave I'm pleased, you know, today we're also announcing the launch of some improvements to S3 Intelligent Tiering, to actually further automate the cost savings. And what we're doing is we're actually removing the minimum storage duration. Previously, Intelligent Tiering had a 30 day minimum storage duration, and we're also eliminating our monitoring and automation charge for small objects. So previously there was that monitoring and automation charge applied to all objects independent of size. And now any object less than 120 kilobytes is not charged at that charge. So, and I think some pretty critical innovations on Intelligent Tiering that will help customers use that for an even wider set of data lake and other applications. >> That's three, it's ubiquitous. The innovation continues. You can learn more by attending the Storage Day S3 deep dive right after this interview. Thank you, Kevin Miller. Great to have you on the program. >> Yeah, Dave, thanks for having me. Great to see you. >> You're welcome, this is Dave Vellante and you're watching theCUBE's coverage of AWS Storage Day. Keep it right there. (bright music)

(upbeat music) >> Welcome back to theCUBE's continuous coverage of AWS storage day. My name is Dave Vellante and we're here from Seattle. And we're going to look at the really hard workloads, those business and mission critical workloads, the most sensitive data. They're harder to move to the cloud. They're hardened. They have a lot of technical debt. And the blocker in some cases has been storage. Ashish Palekar is here. He's the general manager of EBS snapshots, and he's joined by Cami Tavares who's a senior manager of product management for Amazon EBS. Folks, good to see you. >> Ashish: Good to see you again Dave. >> Dave: Okay, nice to see you again Ashish So first of all, let's start with EBS. People might not be familiar. Everybody knows about S3 is famous, but how are customers using EBS? What do we need to know? >> Yeah, it's super important to get the basics, right? Right, yeah. We have a pretty broad storage portfolio. You talked about S3 and S3 glacier, which are an object and object and archival storage. We have EFS and FSX that cover the file site, and then you have a whole host of data transfer services. Now, when we think about block, we think of a really four things. We think about EBS, which is the system storage for EC2 volumes. When we think about snapshots, which is backups for EBS volumes. Then we think about instant storage, which is really a storage that's directly attached to an instance and manages and then its life cycle is similar to that of an instance. Last but not the least, data services. So things like our elastic volumes capability of fast snapshot restore. So the answer to your question really is EBS is persistent storage for EC2 volumes. So if you've used EC2 instances, you'll likely use EBS volumes. They service boot volumes and they service data volumes, and really cover a wide gamut of workloads from relational databases, no SQL databases, file streaming, media and coding. It really covers the gamut of workloads. >> Dave: So when I heard SAN in the cloud, I laughed out loud. I said, oh, because I could think about a box, a bunch of switches and this complicated network, and then you're turning it into an API. I was like, okay. So you've made some announcements that support SAN in the cloud. What, what can you tell us about? >> Ashish: Yeah, So SANs and for customers and storage, those are storage area networks, really our external arrays that customers buy and connect their performance critical and mission critical workloads. With block storage and with EBS, we got a bunch of customers that came to us and said, I'm thinking about moving those kinds of workloads to the cloud. What do you have? And really what they're looking for and what they were looking for is performance availability and durability characteristics that they would get from their traditional SANs on premises. And so that's what the team embarked on and what we launched at reinvent and then at GEd in July is IO2 block express. And what IO2 block express does is it's a complete ground app, really the invention of our storage product offering and gives customers the same availability, durability, and performance characteristics that can, we'll go into little later about that they're used to in their on premises. The other thing that we realized is that it's not just enough to have a volume. You need an instance that can drive that kind of throughput and IOPS. And so coupled with our trends in EC2 we launched our R5b that now triples the amount of IOPS and throughput that you can get from a single instance to EBS storage. So when you couple the sub millisecond latency, the capacity and the performance that you get from IO2 block express with R5b, what we hear from customers is that gives them enough of the performance availability characteristics and durability characteristics to move their workloads from on premises, into the cloud, for the mission critical and business critical apps. >> Dave: Thank you for that. So Cami when I, if I think about how the prevailing way in which storage works, I drop off a box at the loading dock and then I really don't know what happens. There may be a service organization that's maybe more intimate with the customer, but I don't really see the innovations and the use cases that are applied clouds, different. You know, you live it every day. So you guys always talk about customer inspired innovation. So what are you seeing in terms of how people are using this capability and what innovations they're driving? >> Cami: Yeah, so I think when we look at the EBS portfolio and this, the evolution over the years, you can really see that it was driven by customer need and we have different volume types and they have very specific performance characteristics, and they're built to meet these unique needs of customer workloads. So I'll tell you a little bit about some of our specific volume types to kind of illustrate this evolution over the years. So starting with our general purpose volumes, we have many customers that are using these volumes today. They really are looking for high performance at a low cost, and you have all kinds of transactional workloads and low-latency interactive applications and boot volumes, as Ashish mentioned. And they tell us, the customer is using these general purpose volumes, they tell us that they really like this balanced cost and performance. And customers also told us, listen, I have these more demanding applications that need higher performance. I need more IOPS, more throughput. And so looking at that customer need, we were really talking about these IO intensive applications like SAP HANA and Oracle and databases that require just higher durability. And so we looked at that customer feedback and we launched our provisioned IOPS IO2 volume. And with that volume, you get five nines of durability and four times the IOPS that you would get with general purpose volumes. So it's a really compelling offering. Again, customers came to us and said, this is great. I need more performance, I need more IOPS, more throughput, more storage than I can get with a single IO2 volume. And so these were talking about, you mentioned mission critical applications, SAP HANA, Oracle, and what we saw customers doing often is they were striping together multiple IO2 volumes to get the maximum performance, but very quickly with the most demanding applications, it got to a point where we have more IO2 volumes that you want to manage. And so we took that feedback to heart and we completely reinvented the underlying EBS hardware and the software and networking stacks. And we'll launched block express. With block express, you can get four times the IOPS throughput and storage that you would get with a single io2 volume. So it's a really compelling offering for customers. >> Dave: If I had to go back and ask you, what was the catalyst, what was the sort of business climate that really drove the decision here. Was that people were just sort of fed up with you know, I'll use the phrase, the undifferentiated, heavy lifting around SAN, what was it, was it COVID driven? What was the climate? >> You know, it's important to recognize when we are talking about business climate today, every business is a data business and block storage is really a foundational part of that. And so with SAN in the cloud specifically, we have seen enterprises for several years, buying these traditional hardware arrays for on premises SANs. And it's a very expensive investment. Just this year alone, they're spending over $22 billion on SANs. And with this old model on premises SANs, you would probably spend a lot of time doing this upfront capacity planning, trying to figure out how much storage you might need. And in the end, you'd probably end up overbuying for peak demand because you really don't want to get stuck, not having what you need to scale your business. And so now with block express, you don't have to do that anymore. You pay for what you need today, and then you can increase your storage as your business needs change. So that's cost and cost is a very important factor. But really when we're talking to customers and enterprises that are looking for SAN in the cloud, the number one reason that they want to move to the cloud with their SANs and these mission, critical workloads is agility and speed. And it's really transformational for businesses to be able to change the customer experience for their customers and innovate at a much faster pace. And so with the block express product, you get to do that much faster. You can go from an idea to an implementation orders of magnitude faster. Whereas before if you had these workloads on premises, it would take you several weeks just to get the hardware. And then you have to build all this surrounding infrastructure to get it up and running. Now, you don't have to do that anymore. You get your storage in minutes, and if you change your mind, if your business needs change, if your workloads change, you can modify your EBS volume types without interrupting your workload. >> Dave: Thank you for that. So Cami kind of addressed some of this, but I know store admins say, don't touch my SAN, I'm not moving it. This is a big decision for a lot of people. So kind of a two-part question, you know, why now, what do people need to know? And give us the north star close it out with, with where you see the future. >> Ashish: Yeah, so let's, I'll kick things off and then Cami, do jump in. So first of the volume is one part of the story, right? And with IO2 block express, I think we've given customers an extremely compelling offering to go build their mission critical and business critical applications on. We talked about the instance type R5b in terms of giving that instance level performance, but all this is on the foundation of AWS in terms of availability zones and regions. So you think about the constructs and we talk them in terms of building blocks, but our building blocks are really availability zones and regions. And that gives you that core availability infrastructure that you need to build your mission critical and business critical applications. You then take layer on top of that our regional footprint, right. And now you can spin up those workloads globally, if you need to. And then last but not the least, once you're in AWS, you have access to other services. Be it AI, be it ML, be it our relational database services that you can start to think about undifferentiated, heavy lifting. So really you get the smorgasbord really from the availability footprint to global footprint and all the way up to sort of our service stack that you get access to. >> Dave: So that's really thinking out of the box. We're out of time. Cami we'll give you the last word. >> Cami: I just want to say, if you want to learn more about EBS, there's a deep dive session with our principal engineer, Marc Olson later today. So definitely join that. >> Dave: Folks, thanks so much for coming to theCUBE. (in chorus )Thank you. >> Thank you for watching. Keep it right there for more great content from AWS storage day from Seattle.

>>Welcome back to the cubes, continuous coverage of AWS storage day. We're in beautiful downtown Seattle in the great Northwest. My name is Dave Vellante and we're going to talk about file systems. File systems are really tricky and making those file systems elastic is even harder. They've got a long history of serving a variety of use cases as with me as Duncan Lennox. Who's the general manager of Amazon elastic file system. Dunkin. Good to see you again, Dave. Good to see you. So tell me more around the specifically, uh, Amazon's elastic file system EFS you, you know, broad file portfolio, but, but let's narrow in on that. What do we need to know? >>Yeah, well, Amazon elastic file system or EFS as we call it is our simple serverless set and forget elastic file system service. So what we mean by that is we deliver something that's extremely simple for customers to use. There's not a lot of knobs and levers. They need to turn or pull to make it work or manage it on an ongoing basis. The serverless part of it is there's absolutely no infrastructure for customers to manage. We handled that entirely for them. The elastic part then is the file system automatically grows and shrinks as they add and delete data. So they never have to provision storage or risk running out of storage and they pay only for the storage they're actually using. >>What are the sort of use cases and workloads that you see EFS supporting? >>Yeah. Yeah. It has to support a broad set of customer workloads. So it's everything from, you know, serial, highly latency, sensitive applications that customers might be running on-prem today and want to move to the AWS cloud up to massively parallel scale-out workloads that they have as well. >>So. Okay. Are there any industry patterns that you see around that? Are there other industries that sort of lean in more or is it more across the board? We >>See it across the board, although I'd have to say that we see a lot of adoption within compliance and regulated industries. And a lot of that is because of not only our simplicity, but the high levels of availability and durability that we bring to the file system as well. The data is designed for 11 nines of durability. So essentially you don't need to be worrying about your anything happening into your data. And it's a regional service meaning that your file system is available from all availability zones in a particular region for high availability. >>So as part of storage data, we, we saw some, some new tiering announcements. W w w what can you tell us about those >>Super excited to be announcing EFS intelligent tiering? And this is a capability that we're bringing to EFS that allows customers to automatically get the best of both worlds and get cost optimization for their workloads and how it works is the customer can select, uh, using our lifecycle management capability, a policy for how long they want their data to remain active in one of our active storage classes, seven days, for example, or 30 days. And what we do is we automatically monitor every access to every file they have. And if we see no access to a file for their policy period, like seven days or 30 days, we automatically and transparently move that file to one of our cost optimized, optimized storage classes. So they can save up to 92% on their storage costs. Um, one of the really cool things about intelligent tiering then is if that data ever becomes active again and their workload or their application, or their users need to access it, it's automatically moved back to a performance optimized storage class, and this is all completely transparent to their applications and users. >>So, so how, how does that work? Are you using some kind of machine intelligence to sort of monitor things and just learn over time? And like, what if I policy, what if I don't get it quite right? Or maybe I have some quarter end or maybe twice a year, you know, I need access to that. Can you, can the system help me figure >>That out? Yeah. The beauty of it is you don't need to know how your application or workload is accessing the file system or worry about those access patterns changing. So we'll take care of monitoring every access to every file and move the file either to the cost optimized storage class or back to the performance optimized class as needed by your application. >>And then optimized storage classes is again, selected by the system. I don't have to >>It that's right. It's completely transparent. So we will take care of that for you. So you'll set the policy by which you want active data to be moved to the infrequent access cost optimized storage class, like 30 or seven days. And then you can set a policy that says if that data is ever touched again, to move it back to the performance optimized storage class. So that's then all happened automatically by the service on our side. You don't need to do anything >>It's, it's it's serverless, which means what I don't have to provision any, any compute infrastructure. >>That's right. What you get is an end point, the ability to Mount your file system using NFS, or you can also manage your file system from any of our compute services in AWS. So not only directly on an instance, but also from our serverless compute models like AWS Lambda and far gays, and from our container services like ECS and EKS, and all of the infrastructure is completely managed by us. You don't see it, you don't need to worry about it. We scale it automatically for you. >>What was the catalyst for all this? I mean, you know, you got to tell me it's customers, but maybe you could give me some, some insight and add some, some color. Like, what would you decoded sort of what the customers were saying? Did you get inputs from a lot of different places, you know, and you had to put that together and shape it. Uh, tell us, uh, take us inside that sort of how you came to where you are >>Today. Well, you know, I guess at the end of the day, when you think about storage and particularly file system storage, customers always want more performance and they want lower costs. So we're constantly optimizing on both of those dimensions. How can we find a way to deliver more value and lower cost to customers, but also meet the performance needs that their workloads have. And what we found in talking to customers, particularly the customers that EFS targets, they are application administrators, their dev ops practitioners, their data scientists, they have a job they want to do. They're not typically storage specialists. They don't want to have know or learn a lot about the bowels of storage architecture, and how to optimize for what their applications need. They want to focus on solving the business problems. They're focused on whatever those are >>You meaning, for instance. So you took tiering is obvious. You're tiering to lower cost storage, serverless. I'm not provisioning, you know, servers, myself, the system I'm just paying for what I use. The elasticity is a factor. So I'm not having to over provision. And I think I'm hearing, I don't have to spend my time turning knobs. You've talked about that before, because I don't know how much time is spent, you know, tuning systems, but it's gotta be at least 15 to 20% of the storage admins time. You're eliminating that as well. Is that what you mean by sort of cost optimum? Absolutely. >>So we're, we're providing the scale of capacity of performance that customer applications need as they needed without the customer needing to know exactly how to configure the service, to get what they need. We're dealing with changing workloads and changing access patterns. And we're optimizing their storage costs. As at the same time, >>When you guys step back, you get to the whiteboard out, say, okay, what's the north star that you're working because you know, you set the north star. You don't want to keep revisiting that, right? This is we're moving in this direction. How do we get there might change, but what's your north star? Where do you see the future? >>Yeah, it's really all about delivering simple file system storage that just works. And that sounds really easy, but there's a lot of nuance and complexity behind it, but customers don't want to have to worry about how it works. They just need it to work. And we, our goal is to deliver that for a super broad cross section of applications so that customers don't need to worry about how they performance tune or how they cost optimize. We deliver that value for them. >>Yeah. So I'm going to actually follow up on that because I feel like, you know, when you listen to Werner Vogels talk, he gives takes you inside. It's a plumbing sometimes. So what is the, what is that because you're right. That it, it sounds simple, but it's not. And as I said up front file systems, getting that right is really, really challenging. So technically what's the challenges, is it doing this at scale? And, and, and, and, and, and having some, a consistent experience for customers, there's >>Always a challenge to doing what we do at scale. I mean, the elasticity is something that we provide to our customers, but ultimately we have to take their data as bits and put them into Adams at some point. So we're managing infrastructure on the backend to support that. And we also have to do that in a way that delivers something that's cost-effective for customers. So there's a balance and a natural tension there between things like elasticity and simplicity, performance, cost, availability, and durability, and getting that balance right. And being able to cover the maximum cross section of all those things. So for the widest set of workloads, we see that as our job and we're delivering value, and we're doing that >>For our customers. Then of course, it was a big part of that. And of course, when we talk about, you know, the taking away the, the need for tuning, but, but you got to get it right. I mean, you, you, you can't, you can't optimize for every single use case. Right. But you can give great granularity to allow those use cases to be supported. And that seems to be sort of the balancing act that you guys so >>Well, absolutely. It's focused on being a general purpose file system. That's going to work for a broad cross section of, of applications and workloads. >>Right. Right. And that's, that's what customers want. You know, generally speaking, you go after that, that metal Dunkin, I'll give you the last word. >>I just encourage people to come and try out EFS it's as simple as a single click in our console to create a file system and get started. So come give it a, try the >>Button Duncan. Thanks so much for coming back to the cube. It's great to see you again. Thanks, Dave. All right. And keep it right there for more great content from AWS storage day from Seattle.

(Upbeat intro music) >> Thanks guys. Hi everybody. Welcome back to The Spheres. My name is Dave Vellante and you're watching theCubes continuous coverage of AWS storage day. I'm really excited to bring on Wayne Duso. Wayne is the vice-president of AWS Storage Edge and Data Governance Services. Wayne, two Boston boys got to come to Seattle to see each other. You know. Good to see you, man. >> Good to see you too. >> I mean, I'm not really from Boston. The guys from East Boston give me crap for saying that. [Wayne laughs] That my city, right? You're a city too. >> It's my city as well I'm from Charlestown so right across the ocean. >> Charlestown is actually legit Boston, you know I grew up in a town outside, but that's my city. So all the sports fan. So, hey great keynote today. We're going to unpack the keynote and, and really try to dig into it a little bit. You know, last 18 months has been a pretty bizarre, you know, who could have predicted this. We were just talking to my line about, you know, some of the permanent changes and, and even now it's like day to day, you're trying to figure out, okay, you know, what's next, you know, our business, your business. But, but clearly this has been an interesting time to say the least and the tailwind for the Cloud, but let's face it. How are customers responding? How are they changing their strategies as a result? >> Yeah. Well, first off, let me say it's good to see you. It's been years since we've been in chairs across from one another. >> Yeah. A couple of years ago in Boston, >> A couple of years ago in Boston. I'm glad to see you're doing well. >> Yeah. Thanks. You too. >> You look great. (Wayne Laughs) >> We get the Sox going. >> We'll be all set. >> Mm Dave you know, the last 18 months have been challenging. There's been a lot of change, but it's also been inspiring. What we've seen is our customers engaging the agility of the Cloud and appreciating the cost benefits of the Cloud. You know, during this time we've had to be there for our partners, our clients, our customers, and our people, whether it's work from home, whether it's expanding your capability, because it's surging say a company like zoom, where they're surging and they need more capability. Our cloud capabilities have allowed them to function, grow and thrive. In these challenging times. It's really a privilege that we have the services and we have the capability to enable people to behave and, execute and operate as normally as you possibly can in something that's never happened before in our lifetimes. It's unprecedented. It's a privilege. >> Yeah. I mean, I agree. You think about it. There's a lot of negative narrative, in the press about, about big tech and, and, and, you know, the reality is, is big tech has, has stood and small tech has stepped up big time and we were really think about it, Wayne, where would we be without, without tech? And I know it sounds bizarre, but we're kind of lucky. This pandemic actually occurred when it did, because had it occurred, you know, 10 years ago it would have been a lot tougher. I mean, who knows the state of vaccines, but certainly from a tech standpoint, the Cloud has been a savior. You've mentioned Zoom. I mean, you know, we, productivity continues. So that's been, been pretty key. I want to ask you, in you keynote, you talked about two paths to, to move to the Cloud, you know, Vector one was go and kind of lift and shift if I got it right. And then vector two was modernized first and then go, first of all, did I get that right? And >> Super close and >> So help me course correct. And what are those, what are those two paths mean for customers? How should we think about that? >> Yeah. So we want to make sure that customers can appreciate the value of the Cloud as quickly as they need to. And so there's, there's two paths and with not launches and, we'll talk about them in a minute, like our FSX for NetApp ONTAP, it allows customers to quickly move from like to like, so they can move from on-prem and what they're using in terms of the storage services, the processes they use to administer the data and manage the data straight onto AWS, without any conversion, without any change to their application. So I don't change to anything. So storage administrators can be really confident that they can move. Application Administrators know it will work as well, if not better with the Cloud. So moving onto AWS quickly to value that's one path. Now, once they move on to AWS, some customers will choose to modernize. So they will, they will modernize by containerizing their applications, or they will modernize by moving to server-less using Lambda, right? So that gives them the opportunity at the pace they want as quickly or as cautiously as they need to modernize their application, because they're already executing, they're already operating already getting value. Now within that context, then they can continue that modernization process by integrating with even more capabilities, whether it's ML capabilities or IOT capabilities, depending on their needs. So it's really about speed agility, the ability to innovate, and then the ability to get that flywheel going with cost optimization, feed those savings back into betterment for their customers. >> So how did the launches that you guys have made today and even, even previously, do they map into those two paths? >> Yeah, they do very well. >> How so? Help us understand that. >> So if we look, let's just run down through some of the launches today, >> Great. >> And we can, we can map those two, those two paths. So like we talked about FSX for NetApp ONTAP, or we just like to say FSX for ONTAP because it's so much easier to say. [Dave laughs] >> So FSX for ONTAP is a clear case of move. >> Right >> EBS io2 Block Express for Sand, a clear case of move. It allows customers to quickly move their sand workloads to AWS, with the launch of EBS direct API, supporting 64 terabyte volumes. Now you can snapshot your 64 terabyte volumes on-prem to already be in AWS, and you can restore them to an EBS io2 Block Express volume, allowing you to quickly move an ERP application or an Oracle application. Some enterprise application that requires the speed, the durability and the capability of VBS super quickly. So that's, those are good examples of, of that. In terms of the modernization path, our launch of AWS transfer managed workflows is a good example of that. Manage workflows have been around forever. >> Dave: Yeah. >> And, and customers rely on those workflows to run their business, but they really want to be able to take advantage of cloud capabilities. They want to be able to, for instance, apply ML to those workflows because it really kind of makes sense that their workloads are people related. You can apply artificial intelligence to them, >> Right >> This is an example of a service that allows them to modify those workflows, to modernize them and to build additional value into them. >> Well. I like that example. I got a couple of followup questions, if I may. Sticking on the machine learning and machine intelligence for a minute. That to me is a big one because when I was talking to my line about this is this, it's not just you sticking storage in a bucket anymore, right? You're invoking other services: machine intelligence, machine learning, might be database services, whatever it is, you know, streaming services. And it's a service, you know, there it is. It's not a real complicated integration. So that to me is big. I want to ask you about the block side of things >> Wayne: Sure >> You built in your day, a lot of boxes. >> Wayne: I've built a lot of boxes. >> And you know, the Sand space really well. >> Yeah. >> And you know, a lot of people probably more than I do storage admins that say you're not touching my Sand, right? And they just build a brick wall around it. Okay. And now eventually it ages out. And I think, you know, that whole cumbersome model it's understood, but nonetheless, their workloads and our apps are running on that. How do you see that movement from those and they're the toughest ones to move. The Oracle, the SAP they're really, you know, mission critical Microsoft apps, the database apps, hardcore stuff. How do you see that moving into the Cloud? Give us a sense as to what customers are telling you. >> Storage administrators have a hard job >> Dave: Yeah >> And trying to navigate how they move from on-prem to in Cloud is challenging. So we listened to the storage administrators, even when they tell us, No. we want to understand why no. And when you look at EBS io2 Block Express, this is in part our initial response to moving their saying into the Cloud super easily. Right? Because what do they need? They need performance. They need their ability. They need availability. They need the services to be able to snap and to be able to replicate their Capa- their storage. They need to know that they can move their applications without having to redo all they know to re-plan all they work on each and every day. They want to be able to move quickly and confidently. EBS io2 Block Express is the beginning of that. They can move confidently to sand in the Cloud using EBS. >> Well, so why do they say 'no'? Is it just like the inherent fear? Like a lawyer would say, don't do that, you know, don't or is it just, is it, is it a technical issue? Is it a cultural issue? And what are you seeing there? >> It's a cultural issue. It's a mindset issue, but it's a responsibility. I mean, these folks are responsible for the, one of the most important assets that you have. Most important asset for any company is people. Second most important asset is data. These folks are responsible for a very important asset. And if they don't get it right, if they don't get security, right. They don't get performance right. They don't get durability right. They don't get availability right. It's on them. So it's on us to make sure they're okay. >> Do you see it similar to the security discussion? Because early on, I was just talking to Sandy Carter about this and we were saying, you remember the CIA deal? Right? So I remember talking to the financial services people said, we'll never put any data in the Cloud. Okay they got to be one of your biggest industries, if not your biggest, you know customer base today. But there was fear and, and the CIA deal changed that. They're like, wow CIA is going to the Cloud They're really security conscious. And that was an example of maybe public sector informing commercial. Do you see it as similar? I mean there's obviously differences, but is it a sort of similar dynamic? >> I do. I do. You know, all of these ilities right. Whether it's, you know, durability, availability, security, we'll put ility at the end of that somehow. All of these are not jargon words. They mean something to each persona, to each customer. So we have to make sure that we address each of them. So like security. And we've been addressing the security concern since the beginning of AWS, because security is job number one. And operational excellence job number two. So, a lot of things we're talking about here is operational excellence, durability, availability, likeness are all operational concerns. And we have to make sure we deliver against those for our customers. >> I get it. I mean, the storage admins job is thankless, but the same time, you know, if your main expertise is managing LUNs, your growth path is limited. So they, they want to transform. They want to modernize their own careers. >> I love that. >> It's true. Right? I mean it's- >> Yeah. Yeah. So, you know, if you're a storage administrator today, understanding the storage portfolio that AWS delivers will allow you, and it will enable you empower you to be a cloud storage administrator. So you have no worry because you're, let's take FSX for ONTAP. You will take the skills that you've developed and honed over years and directly apply them to the workloads that you will bring to the Cloud. Using the same CLIs, The same APIs, the same consoles, the same capabilities. >> Plus you mentioned you guys announced, you talked about AWS backup services today, announced some stuff there. I see security governance, backup, identity access management, and governance. These are all adjacency. So if you're a, if you're a cloud storage administrator, you now are going to expand your scope of operations. You, you know, you're not going to be a security, Wiz overnight by any means, but you're now part of that, that rubric. And you're going to participate in that opportunity and learn some things and advance your career. I want to ask you, before we run out of time, you talked about agility and cost optimization, and it's kind of the yin and the yang of Cloud, if you will. But how are these seemingly conflicting forces in sync in your view. >> Like many things in life, right? [Wayne Laughs] >> We're going to get a little spiritually. >> We might get a little philosophical here. [Dave Laughs] >> You know, cloud announced, we've talked about two paths and in part of the two paths is enabling you to move quickly and be agile in how you move to the Cloud. Once you are on the Cloud, we have the ability through all of the service integrations that we have. In your ability to see exactly what's happening at every moment, to then cost optimize, to modernize, to cost optimize, to improve on the applications and workloads and data sets that you've brought. So this becomes a flywheel cost optimization allows you to reinvest, reinvest, be more agile, more innovative, which again, returns a value to your business and value to your customers. It's a flywheel effect. >> Yeah. It's kind of that gain sharing. Right? >> It is. >> And, you know, it's harder to do that in a, in an on-prem world, which everything is kind of, okay, it's working. Now boom, make it static. Oh, I want to bring in this capability or this, you know, AI. And then there's an integration challenge >> That's true. >> Going on. Not, not that there's, you know, there's differences in, APIs. But that's, to me is the opportunity to build on top of it. I just, again, talking to my line, I remember Andy Jassy saying, Hey, we purposefully have created our services at a really atomic level so that we can get down to the primitives and change as the market changes. To me, that's an opportunity for builders to create abstraction layers on top of that, you know, you've kind of, Amazon has kind of resisted that over the years, but, but almost on purpose. There's some of that now going on specialization and maybe certain industry solutions, but in general, your philosophy is to maintain that agility at the really granular level. >> It is, you know, we go back a long way. And as you said, I've built a lot of boxes and I'm proud of a lot of the boxes I've built, but a box is still a box, right? You have constraints. And when you innovate and build on the Cloud, when you move to the Cloud, you do not have those constraints, right? You have the agility, you can stand up a file system in three seconds, you can grow it and shrink it whenever you want. And you can delete it, get rid of it whenever you want back it up and then delete it. You don't have to worry about your infrastructure. You don't have to worry about is it going to be there in three months? It will be there in three seconds. So the agility of each of these services, the unique elements of all of these services allow you to capitalize on their value, use what you need and stop using it when you don't, and you don't have the same capabilities when you use more traditional products. >> So when you're designing a box, how is your mindset different than when you're designing a service? >> Well. You have physical constraints. You have to worry about the physical resources on that device for the life of that device, which is years. Think about what changes in three or five years. Think about the last two years alone and what's changed. Can you imagine having been constrained by only having boxes available to you during this last two years versus having the Cloud and being able to expand or contract based on your business needs, that would be really tough, right? And it has been tough. And that's why we've seen customers for every industry accelerate their use of the Cloud during these last two years. >> So I get that. So what's your mindset when you're building storage services and data services. >> So. Each of the surfaces that we have in object block file, movement services, data services, each of them provides very specific customer value and each are deeply integrated with the rest of AWS, so that when you need object services, you start using them. The integrations come along with you. When, if you're using traditional block, we talked about EBS io2 Block Express. When you're using file, just the example alone today with ONTAP, you know, you get to use what you need when you need it, and the way that you're used to using it without any concerns. >> (Dave mumbles) So your mindset is how do I exploit all these other services? You're like the chef and these are ingredients that you can tap and give a path to your customers to explore it over time. >> Yeah. Traditionally, for instance, if you were to have a filer, you would run multiple applications on that filer you're worried about. Cause you should, as a storage administrator, will each of those applications have the right amount of resources to run at peak. When you're on the Cloud, each of those applications will just spin up in seconds, their own file system. And those file systems can grow and shrink at whatever, however they need to do so. And you don't have to worry about one application interfering with the other application. It's not your concern anymore. And it's not really that fun to do. Anyway. It's kind of the hard work that nobody really you know, really wants to reward you for. So you can take your time and apply it to more business generate, you know, value for your business. >> That's great. Thank you for that. Okay. I'll I'll give you the last word. Give us the bumper sticker on AWS Storage day. Exciting day. The third AWS storage day. You guys keep getting bigger, raising the bar. >> And we're happy to keep doing it with you. >> Awesome. >> So thank you for flying out from Boston to see me. >> Pleasure, >> As they say. >> So, you know, this is a great opportunity for us to talk to customers, to thank them. It's a privilege to build what we build for customers. You know, our customers are leaders in their organizations and their businesses for their customers. And what we want to do is help them continue to be leaders and help them to continue to build and deliver we're here for them. >> Wayne. It's great to see you again. Thanks so much. >> Thanks. >> Maybe see you back at home. >> All right. Go Sox. All right. Yeah, go Sox. [Wayne Laughs] All right. Thank you for watching everybody. Back to Jenna Canal and Darko in the studio. Its Dave Volante. You're watching theCube. [Outro Music]

(pensive music) >> Thank you, Jenna, it's great to see you guys and thank you for watching theCUBE's continuous coverage of AWS Storage Day. We're here at The Spheres, it's amazing venue. My name is Dave Vellante. I'm here with Mai-Lan Tomsen Bukovec who's Vice President of Block and Object Storage. Mai-Lan, always a pleasure to see you. Thanks for coming on. >> Nice to see you, Dave. >> It's pretty crazy, you know, this is kind of a hybrid event. We were in Barcelona a while ago, big hybrid event. And now it's, you know, it's hard to tell. It's almost like day-to-day what's happening with COVID and some things are permanent. I think a lot of things are becoming permanent. What are you seeing out there in terms of when you talk to customers, how are they thinking about their business, building resiliency and agility into their business in the context of COVID and beyond? >> Well, Dave, I think what we've learned today is that this is a new normal. These fluctuations that companies are having and supply and demand, in all industries all over the world. That's the new normal. And that has what, is what has driven so much more adoption of cloud in the last 12 to 18 months. And we're going to continue to see that rapid migration to the cloud because companies now know that in the course of days and months, you're, the whole world of your expectations of where your business is going and where, what your customers are going to do, that can change. And that can change not just for a year, but maybe longer than that. That's the new normal. And I think companies are realizing it and our AWS customers are seeing how important it is to accelerate moving everything to the cloud, to continue to adapt to this new normal. >> So storage historically has been, I'm going to drop a box off at the loading dock and, you know, have a nice day. And then maybe the services team is involved in, in a more intimate way, but you're involved every day. So I'm curious as to what that permanence, that new normal, some people call it the new abnormal, but it's the new normal now, what does that mean for storage? >> Dave, in the course of us sitting here over the next few minutes, we're going to have dozens of deployments go out all across our AWS storage services. That means our customers that are using our file services, our transfer services, block and object services, they're all getting improvements as we sit here and talk. That is such a fundamentally different model than the one that you talked about, which is the appliance gets dropped off at the loading dock. It takes a couple months for it to get scheduled for setup and then you have to do data migration to get the data on the new appliance. Meanwhile, we're sitting here and customers storage is just improving, under the hood and in major announcements, like what we're doing today. >> So take us through the sort of, let's go back, 'cause I remember vividly when, when S3 was announced that launched this cloud era and people would, you know, they would do a lot of experimentation of, we were storing, you know, maybe gigabytes, maybe even some terabytes back then. And, and that's evolved. What are you seeing in terms of how people are using data? What are the patterns that you're seeing today? How is that different than maybe 10 years ago? >> I think what's really unique about AWS is that we are the only provider that has been operating at scale for 15 years. And what that means is that we have customers of all sizes, terabytes, petabytes, exabytes, that are running their storage on AWS and running their applications using that storage. And so we have this really unique position of being able to observe and work with customers to develop what they need for storage. And it really breaks down to three main patterns. The first one is what I call the crown jewels, the crown jewels in the cloud. And that pattern is adopted by customers who are looking at the core mission of their business and they're saying to themselves, I actually can't scale this core mission on on-premises. And they're choosing to go to the cloud on the most important thing that their business does because they must, they have to. And so, a great example of that is FINRA, the regulatory body of the US stock exchanges, where, you know, a number of years ago, they took a look at all the data silos that were popping up across their data centers. They were looking at the rate of stock transactions going up and they're saying, we just can't keep up. Not if we want to follow the mission of being the watchdog for consumers, for transactions, for stock transactions. And so they moved that crown jewel of their application to AWS. And what's really interesting Dave, is, as you know, 'cause you've talked to many different companies, it's not technology that stops people from moving to the cloud as quick as they want to, it's culture, it's people, it's processes, it's how businesses work. And when you move the crown jewels into the cloud, you are accelerating that cultural change and that's certainly what FINRA saw. Second thing we see, is where a company will pick a few cloud pilots. We'll take a couple of applications, maybe one or a several across the organization and they'll move that as sort of a reference implementation to the cloud. And then the goal is to try to get the people who did that to generalize all the learning across the company. That is actually a really slow way to change culture. Because, as many of us know, in large organizations, you know, you have, you have some resistance to other organizations changing culture. And so that cloud pilot, while it seems like it would work, it seems logical, it's actually counter-productive to a lot of companies that want to move quickly to the cloud. And the third example is what I think of as new applications or cloud first, net new. And that pattern is where a company or a startup says all new technology initiatives are on the cloud. And we see that for companies like McDonald's, which has transformed their drive up experience by dynamically looking at location orders and providing recommendations. And we see it for the Digital Athlete, which is what the NFL has put together to dynamically take data sources and build these models that help them programmatically simulate risks to player health and put in place some ways to predict and prevent that. But those are the three patterns that we see so many customers falling into depending on what their business wants. >> I like that term, Digital Athlete, my business partner, John Furrier, coined the term tech athlete, you know, years ago on theCUBE. That third pattern seems to me, because you're right, you almost have to shock the system. If you just put your toe in the water, it's going to take too long. But it seems like that third pattern really actually de-risks it in a lot of cases, it's so it's said, people, who's going to argue, oh, the new stuff should be in the cloud. And so, that seems to me to be a very sensible way to approach that, that blocker, if you will, what are your thoughts on that? >> I think you're right, Dave. I think what it does is it allows a company to be able to see the ideas and the technology and the cultural change of cloud in different parts of the organization. And so rather than having a, one group that's supposed to generalize it across an organization, you get it decentralized and adopted by different groups and the culture change just goes faster. >> So you, you bring up decentralization and there's a, there's an emerging trend referred to as a data mesh. It was, it was coined, the term coined by Zhamak Dehghani, a very thought-provoking individual. And the concept is basically the, you know, data is decentralized, and yet we have this tendency to sort of shove it all into, you know, one box or one container, or you could say one cloud, well, the cloud is expanding, it's the cloud is, is decentralizing in many ways. So how do you see data mesh fitting in to those patterns? >> We have customers today that are taking the data mesh architectures and implementing them with AWS services. And Dave, I want to go back to the start of Amazon, when Amazon first began, we grew because the Amazon technologies were built in microservices. Fundamentally, a data mesh is about separation or abstraction of what individual components do. And so if I look at data mesh, really, you're talking about two things, you're talking about separating the data storage and the characteristics of data from the data services that interact and operate on that storage. And with data mesh, it's all about making sure that the businesses, the decentralized business model can work with that data. Now our AWS customers are putting their storage in a centralized place because it's easier to track, it's easier to view compliance and it's easier to predict growth and control costs. But, we started with building blocks and we deliberately built our storage services separate from our data services. So we have data services like Lake Formation and Glue. We have a number of these data services that our customers are using to build that customized data mesh on top of that centralized storage. So really, it's about at the end of the day, speed, it's about innovation. It's about making sure that you can decentralize and separate your data services from your storage so businesses can go faster. >> But that centralized storage is logically centralized. It might not be physically centralized, I mean, we put storage all over the world, >> Mai-Lan: That's correct. >> right? But, but we, to the developer, it looks like it's in one place. >> Mai-Lan: That's right. >> Right? And so, so that's not antithetical to the concept of a data mesh. In fact, it fits in perfectly to the point you were making. I wonder if we could talk a little bit about AWS's storage strategy and it started of course, with, with S3, and that was the focus for years and now of course EBS as well. But now we're seeing, we heard from Wayne this morning, the portfolio is expanding. The innovation is, is accelerating that flywheel that we always talk about. How would you characterize and how do you think about AWS's storage strategy per se? >> We are a dynamically and constantly evolving our AWS storage services based on what the application and the customer want. That is fundamentally what we do every day. We talked a little bit about those deployments that are happening right now, Dave. That is something, that idea of constant dynamic evolution just can't be replicated by on-premises where you buy a box and it sits in your data center for three or more years. And what's unique about us among the cloud services, is again that perspective of the 15 years where we are building applications in ways that are unique because we have more customers and we have more customers doing more things. So, you know, I've said this before. It's all about speed of innovation Dave, time and change wait for no one. And if you're a business and you're trying to transform your business and base it on a set of technologies that change rapidly, you have to use AWS services. Let's, I mean, if you look at some of the launches that we talk about today, and you think about S3's multi-region access points, that's a fundamental change for customers that want to store copies of their data in any number of different regions and get a 60% performance improvement by leveraging the technology that we've built up over, over time, leveraging the, the ability for us to route, to intelligently route a request across our network. That, and FSx for NetApp ONTAP, nobody else has these capabilities today. And it's because we are at the forefront of talking to different customers and that dynamic evolution of storage, that's the core of our strategy. >> So Andy Jassy used to say, oftentimes, AWS is misunderstood and you, you comfortable with that. So help me square this circle 'cause you talked about things you couldn't do on on-prem, and yet you mentioned the relationship with NetApp. You think, look at things like Outposts and Local Zones. So you're actually moving the cloud out to the edge, including on-prem data centers. So, so how do you think about hybrid in that context? >> For us, Dave, it always comes back to what the customer's asking for. And we were talking to customers and they were talking about their edge and what they wanted to do with it. We said, how are we going to help? And so if I just take S3 for Outposts, as an example, or EBS and Outposts, you know, we have customers like Morningstar and Morningstar wants Outposts because they are using it as a step in their journey to being on the cloud. If you take a customer like First Abu Dhabi Bank, they're using Outposts because they need data residency for their compliance requirements. And then we have other customers that are using Outposts to help, like Dish, Dish Networks, as an example, to place the storage as close as account to the applications for low latency. All of those are customer driven requirements for their architecture. For us, Dave, we think in the fullness of time, every customer and all applications are going to be on the cloud, because it makes sense and those businesses need that speed of innovation. But when we build things like our announcement today of FSx for NetApp ONTAP, we build them because customers asked us to help them with their journey to the cloud, just like we built S3 and EBS for Outposts for the same reason. >> Well, when you say over time, you're, you believe that all workloads will be on the cloud, but the cloud is, it's like the universe. I mean, it's expanding. So what's not cloud in the future? When you say on the cloud, you mean wherever you meet customers with that cloud, that includes Outposts, just the programming, it's the programmability of that model, is that correct? That's it, >> That's right. that's what you're talking about? >> In fact, our S3 and EBS Outposts customers, the way that they look at how they use Outposts, it's either as part of developing applications where they'll eventually go the cloud or taking applications that are in the cloud today in AWS regions and running them locally. And so, as you say, this definition of the cloud, you know, it, it's going to evolve over time. But the one thing that we know for sure, is that AWS storage and AWS in general is going to be there one or two steps ahead of where customers are, and deliver on what they need. >> I want to talk about block storage for a moment, if I can, you know, you guys are making some moves in that space. We heard some announcements earlier today. Some of the hardest stuff to move, whether it's cultural or maybe it's just hardened tops, maybe it's, you know, governance edicts, or those really hardcore mission critical apps and workloads, whether it's SAP stuff, Oracle, Microsoft, et cetera. You're clearly seeing that as an opportunity for your customers and in storage in some respects was a blocker previously because of whatever, latency, et cetera, then there's still some, some considerations there. How do you see those workloads eventually moving to the cloud? >> Well, they can move now. With io2 Block Express, we have the performance that those high-end applications need and it's available today. We have customers using them and they're very excited about that technology. And, you know, again, it goes back to what I just said, Dave, we had customers saying, I would like to move my highest performing applications to the cloud and this is what I need from the, from the, the storage underneath them. And that's why we built io2 Block Express and that's how we'll continue to evolve io2 Block Express. It is the first SAN technology in the cloud, but it's built on those core principles that we talked about a few minutes ago, which is dynamically evolving and capabilities that we can add on the fly and customers just get the benefit of it without the cost of migration. >> I want to ask you about, about just the storage, how you think about storage in general, because typically it's been a bucket, you know, it's a container, but it seems, I always say the next 10 years aren't going to be like the last, it seems like, you're really in the data business and you're bringing in machine intelligence, you're bringing in other database technology, this rich set of other services to apply to the data. That's now, there's a lot of data in the cloud and so we can now, whether it's build data products, build data services. So how do you think about the business in that sense? It's no longer just a place to store stuff. It's actually a place to accelerate innovation and build and monetize for your customers. How do you think about that? >> Our customers use the word foundational. Every time they talk about storage, they say for us, it's foundational, and Dave, that's because every business is a data business. Every business is making decisions now on this changing landscape in a world where the new normal means you cannot predict what's going to happen in six months, in a year. And the way that they're making those smart decisions is through data. And so they're taking the data that they have in our storage services and they're using SageMaker to build models. They're, they're using all kinds of different applications like Lake Formation and Glue to build some of the services that you're talking about around authorization and data discovery, to sit on top of the data. And they're able to leverage the data in a way that they have never been able to do before, because they have to. That's what the business world demands today, and that's what we need in the new normal. We need the flexibility and the dynamic foundational storage that we provide in AWS. >> And you think about the great data companies, those were the, you know, trillions in the market cap, their data companies, they put data at their core, but that doesn't mean they shove all the data into a centralized location. It means they have the identity access capabilities, the governance capabilities to, to enable data to be used wherever it needs to be used and, and build that future. That, exciting times we're entering here, Mai-Lan. >> We're just set the start, Dave, we're just at the start. >> Really, what ending do you think we have? So, how do you think about Amazon? It was, it's not a baby anymore. It's not even an adolescent, right? You guys are obviously major player, early adulthood, day one, day zero? (chuckles) >> Dave, we don't age ourself. I think if I look at where we're going for AWS, we are just at the start. So many companies are moving to the cloud, but we're really just at the start. And what's really exciting for us who work on AWS storage, is that when we build these storage services and these data services, we are seeing customers do things that they never thought they could do before. And it's just the beginning. >> I think the potential is unlimited. You mentioned Dish before, I mean, I see what they're doing in the cloud for Telco. I mean, Telco Transformation, that's an industry, every industry, there's a transformation scenario, a disruption scenario. Healthcare has been so reluctant for years and that's happening so quickly, I mean, COVID's certainly accelerating that. Obviously financial services have been super tech savvy, but they're looking at the Fintech saying, okay, how do we play? I mean, there isn't manufacturing with EV. >> Mai-Lan: Government. >> Government, totally. >> It's everywhere, oil and gas. >> There isn't a single industry that's not a digital industry. >> That's right. >> And there's implications for everyone. And it's not just bits and atoms anymore, the old Negroponte, although Nicholas, I think was prescient because he's, he saw this coming, it really is fundamental. Data is fundamental to every business. >> And I think you want, for all of those in different industries, you want to pick the provider where innovation and invention is in our DNA. And that is true, not just for storage, but AWS, and that is driving a lot of the changes you have today, but really what's coming in the future. >> You're right. It's the common editorial factors. It's not just the, the storage of the data. It's the ability to apply other technologies that map into your business process, that map into your organizational skill sets that drive innovation in whatever industry you're in. It's great Mai-Lan, awesome to see you. Thanks so much for coming on theCUBE. >> Great seeing you Dave, take care. >> All right, you too. And keep it right there for more action. We're going to now toss it back to Jenna, Canal and Darko in the studio. Guys, over to you. (pensive music)

(upbeat music) >> Welcome back to AWS storage day. This is the Cubes continuous coverage. My name is Dave Vellante, and we're going to talk about file storage. 80% of the world's data is in unstructured storage. And most of that is in file format. Devs want infrastructure as code. They want to be able to provision and manage storage through an API, and they want that cloud agility. They want to be able to scale up, scale down, pay by the drink. And the big news of storage day was really the partnership, deep partnership between AWS and NetApp. And with me to talk about that as Ed Naim, who's the general manager of Amazon FSX and Anthony Lye, executive vice president and GM of public cloud at NetApp. Two Cube alums. Great to see you guys again. Thanks for coming on. >> Thanks for having us. >> So Ed, let me start with you. You launched FSX 2018 at re-invent. How has it being used today? >> Well, we've talked about MSX on the Cube before Dave, but let me start by recapping that FSX makes it easy to, to launch and run fully managed feature rich high performance file storage in the cloud. And we built MSX from the ground up really to have the reliability, the scalability you were talking about. The simplicity to support, a really wide range of workloads and applications. And with FSX customers choose the file system that powers their file storage with full access to the file systems feature sets, the performance profiles and the data management capabilities. And so since reinvent 2018, when we launched this service, we've offered two file system choices for customers. So the first was a Windows file server, and that's really storage built on top of Windows server designed as a really simple solution for Windows applications that require shared storage. And then Lustre, which is an open source file system that's the world's most popular high-performance file system. And the Amazon FSX model has really resonated strongly with customers for a few reasons. So first, for customers who currently managed network attached storage or NAS on premises, it's such an easy path to move their applications and their application data to the cloud. FSX works and feels like the NAZA appliances that they're used to, but added to all of that are the benefits of a fully managed cloud service. And second, for builders developing modern new apps, it helps them deliver fast, consistent experiences for Windows and Linux in a simple and an agile way. And then third, for research scientists, its storage performance and its capabilities for dealing with data at scale really make it a no-brainer storage solution. And so as a result, the service is being used for a pretty wide spectrum of applications and workloads across industries. So I'll give you a couple of examples. So there's this class of what we call common enterprise IT use cases. So think of things like end user file shares the corporate IT applications, content management systems, highly available database deployments. And then there's a variety of common line of business and vertical workloads that are running on FSX as well. So financial services, there's a lot of modeling and analytics, workloads, life sciences, a lot of genomics analysis, media and entertainment rendering and transcoding and visual effects, automotive. We have a lot of electronic control units, simulations, and object detection, semiconductor, a lot of EDA, electronic design automation. And then oil and gas, seismic data processing, pretty common workload in FSX. And then there's a class of, of really ultra high performance workloads that are running on FSX as well. Think of things like big data analytics. So SAS grid is a, is a common application. A lot of machine learning model training, and then a lot of what people would consider traditional or classic high performance computing or HPC. >> Great. Thank you for that. Just quick follow-up if I may, and I want to bring Anthony into the conversation. So why NetApp? This is not a Barney deal, this was not elbow grease going into a Barney deal. You know, I love you. You love me. We do a press release. But, but why NetApp? Why ONTAP? Why now? (momentary silence) Ed, that was to you. >> Was that a question for Anthony? >> No, for you Ed. And then I want to bring Anthony in. >> Oh, Sure. Sorry. Okay. Sure. Yeah, I mean it, uh, Dave, it really stemmed from both companies realizing a combined offering would be highly valuable to and impactful for customers. In reality, we started collaborating in Amazon and NetApp on the service probably about two years ago. And we really had a joint vision that we wanted to provide AWS customers with the full power of ONTAP. The complete ONTAP with every capability and with ONTAP's full performance, but fully managed an offer as a full-blown AWS native service. So what that would mean is that customers get all of ONTAP's benefits along with the simplicity and the agility, the scalability, the security, and the reliability of an AWS service. >> Great. Thank you. So Anthony, I have watched NetApp reinvent itself started in workstations, saw you go into the enterprise, I saw you lean into virtualization, you told me at least two years, it might've been three years ago, Dave, we are going all in on the cloud. We're going to lead this next, next chapter. And so, I want you to bring in your perspective. You're re-inventing NetApp yet again, you know, what are your thoughts? >> Well, you know, NetApp and AWS have had a very long relationship. I think it probably dates now about nine years. And what we really wanted to do in NetApp was give the most important constituent of all an experience that helped them progress their business. So ONTAP, you know, the industry's leading shared storage platform, we wanted to make sure that in AWS, it was as good as it was on premise. We love the idea of giving customers this wonderful concept of symmetry. You know, ONTAP runs the biggest applications in the largest enterprises on the planet. And we wanted to give not just those customers an opportunity to embrace the Amazon cloud, but we wanted to also extend the capabilities of ONTAP through FSX to a new customer audience. Maybe those smaller companies that didn't really purchase on premise infrastructure, people that were born in the cloud. And of course, this gives us a great opportunity to present a fully managed ONTAP within the FSX platform, to a lot of non NetApp customers, to our competitors customers, Dave, that frankly, haven't done the same as we've done. And I think we are the benefactors of it, and we're in turn passing that innovation, that, that transformation onto the, to the customers and the partners. >> You know, one is the, the key aspect here is that it's a managed service. I don't think that could be, you know, overstated. And the other is that the cloud nativeness of this Anthony, you mentioned here, our marketplace is great, but this is some serious engineering going on here. So Ed maybe, maybe start with the perspective of a managed service. I mean, what does that mean? The whole ball of wax? >> Yeah. I mean, what it means to a customer is they go into the AWS console or they go to the AWS SDK or the, the AWS CLI and they are easily able to provision a resource provision, a file system, and it automatically will get built for them. And if there's nothing that they need to do at that point, they get an endpoint that they have access to the file system from and that's it. We handle patching, we handle all of the provisioning, we handle any hardware replacements that might need to happen along the way. Everything is fully managed. So the customer really can focus not on managing their file system, but on doing all of the other things that they, that they want to do and that they need to do. >> So. So Anthony, in a way you're disrupting yourself, which is kind of what you told me a couple of years ago. You're not afraid to do that because if we don't do it, somebody else is going to do it because you're, you're used to the old days, you're selling a box and you say, we'll see you next time, you know, three or four years. So from, from your customer's standpoint, what's their reaction to this notion of a managed service and what does it mean to NetApp? >> Well, so I think the most important thing it does is it gives them investment protection. The wonderful thing about what we've built with Amazon in the FSX profile is it's a complete ONTAP. And so one ONTAP cluster on premise can immediately see and connect to an ONTAP environment under FSX. We can then establish various different connectivities. We can use snap mirror technologies for disaster recovery. We can use efficient data transfer for things like dev test and backup. Of course, the wonderful thing that we've done, that we've gone beyond, above and beyond, what anybody else has done is we want to make sure that the actual primary application itself, one that was sort of built using NAS built in an on-premise environment an SAP and Oracle, et cetera, as Ed said, that we can move those over and have the confidence to run the application with no changes on an Amazon environment. So, so what we've really done, I think for customers, the NetApp customers, the non NetApp customers, is we've given them an enterprise grade shared storage platform that's as good in an Amazon cloud as it was in an on-premise data center. And that's something that's very unique to us. >> Can we talk a little bit more about those, those use cases? You know, both, both of you. What are you seeing as some of the more interesting ones that you can share? Ed, maybe you can start. >> Yeah, happy to. The customer discussions that we've, we've been in have really highlighted four cases, four use cases the customers are telling us they'll use a service for. So maybe I'll cover two and maybe Anthony can cover the other two. So, the first is application migrations. And customers are increasingly looking to move their applications to AWS. And a lot of those are applications work with file storage today. And so we're talking about applications like SAP. We're talking about relational databases like SQL server and Oracle. We're talking about vertical applications like Epic and the healthcare space. As another example, lots of media entertainment, rendering, and transcoding, and visual effects workload. workflows require Windows, Linux, and Mac iOS access to the same set of data. And what application administrators really want is they want the easy button. They want fully featured file storage that has the same capabilities, the same performance that their applications are used to. Has extremely high availability and durability, and it can easily enable them to meet compliance and security needs with a robust set of data protection and security capabilities. And I'll give you an example, Accenture, for example, has told us that a key obstacle their clients face when migrating to the cloud is potentially re-architecting their applications to adopt new technologies. And they expect that Amazon FSX for NetApp ONTAP will significantly accelerate their customers migrations to the cloud. Then a second one is storage migrations. So storage admins are increasingly looking to extend their on-premise storage to the cloud. And why they want to do that is they want to be more agile and they want to be responsive to growing data sets and growing workload needs. They want to last to capacity. They want the ability to spin up and spin down. They want easy disaster recovery across geographically isolated regions. They want the ability to change performance levels at any time. So all of this goodness that they get from the cloud is what they want. And more and more of them also are looking to make their company's data accessible to cloud services for analytics and processing. So services like ECS and EKS and workspaces and App Stream and VMware cloud and SageMaker and orchestration services like parallel cluster and AWS batch. But at the same time, they want all these cloud benefits, but at the same time, they have established data management workflows, and they build processes and they've built automation, leveraging APIs and capabilities of on-prem NAS appliances. It's really tough for them to just start from scratch with that stuff. So this offering provides them the best of both worlds. They get the benefits of the cloud with the NAS data management capabilities that they're used to. >> Right. >> Ed: So Anthony, maybe, do you want to talk about the other two? >> Well, so, you know, first and foremost, you heard from Ed earlier on the, the, the FSX sort of construct and how successful it's been. And one of the real reasons it's been so successful is, it takes advantage of all of the latest storage technologies, compute technologies, networking technologies. What's great is all of that's hidden from the user. What FSX does is it delivers a service. And what that means for an ONTAP customer is you're going to have ONTAP with an SLA and an SLM. You're going to have hundreds of thousands of IOPS available to you and sub-millisecond latencies. What's also really important is the design for FSX and app ONTAP was really to provide consistency on the NetApp API and to provide full access to ONTAP from the Amazon console, the Amazon SDK, or the Amazon CLI. So in this case, you've got this wonderful benefit of all of the, sort of the 29 years of innovation of NetApp combined with all the innovation AWS, all presented consistently to a customer. What Ed said, which I'm particularly excited about, is customers will see this just as they see any other AWS service. So if they want to use ONTAP in combination with some incremental compute resources, maybe with their own encryption keys, maybe with directory services, they may want to use it with other services like SageMaker. All of those things are immediately exposed to Amazon FSX for the app ONTAP. We do some really intelligent things just in the storage layer. So, for example, we do intelligent tiering. So the customer is constantly getting the, sort of the best TCO. So what that means is we're using Amazon's S3 storage as a tiered service, so that we can back off code data off of the primary file system to give the customer the optimal capacity, the optimal throughput, while maintaining the integrity of the file system. It's the same with backup. It's the same with disaster recovery, whether we're operating in a hybrid AWS cloud, or we're operating in an AWS region or across regions. >> Well, thank you. I think this, this announcement is a big deal for a number of reasons. First of all, it's the largest market. Like you said, you're the gold standard. I'll give you that, Anthony, because you guys earned it. And so it's a large market, but you always had to make previously, you have to make trade-offs. Either I could do file in the cloud, but I didn't get the rich functionality that, you know, NetApp's mature stack brings, or, you know, you could have wrapped your stack in Kubernete's container and thrown it into the cloud and hosted it there. But now that it's a managed service and presumably you're underneath, you're taking advantage. As I say, my inference is there's some serious engineering going on here. You're taking advantage of some of the cloud native capabilities. Yeah, maybe it's the different, you know, ECE two types, but also being able to bring in, we're, we're entering a new data era with machine intelligence and other capabilities that we really didn't have access to last decade. So I want to, I want to close with, you know, give you guys the last word. Maybe each of you could give me your thoughts on how you see this partnership of, for the, in the future. Particularly from a customer standpoint. Ed, maybe you could start. And then Anthony, you can bring us home. >> Yeah, well, Anthony and I and our teams have gotten to know each other really well in, in ideating around what this experience will be and then building the product. And, and we have this, this common vision that it is something that's going to really move the needle for customers. Providing the full ONTAP experience with the power of a, of a native AWS service. So we're really excited. We're, we're in this for the long haul together. We have, we've partnered on everything from engineering, to product management, to support. Like the, the full thing. This is a co-owned effort, a joint effort backed by both companies. And we have, I think a pretty remarkable product on day one, one that I think is going to delight customers. And we have a really rich roadmap that we're going to be building together over, over the years. So I'm excited about getting this in customer's hands. >> Great, thank you. Anthony, bring us home. >> Well, you know, it's one of those sorts of rare chances where you get to do something with Amazon that no one's ever done. You know, we're sort of sitting on the inside, we are a peer of theirs, and we're able to develop at very high speeds in combination with them to release continuously to the customer base. So what you're going to see here is rapid innovation. You're going to see a whole host of new services. Services that NetApp develops, services that Amazon develops. And then the whole ecosystem is going to have access to this, whether they're historically built on the NetApp APIs or increasingly built on the AWS APIs. I think you're going to see orchestrations. I think you're going to see the capabilities expand the overall opportunity for AWS to bring enterprise applications over. For me personally, Dave, you know, I've demonstrated yet again to the NetApp customer base, how much we care about them and their future. Selfishly, you know, I'm looking forward to telling the story to my competitors, customer base, because they haven't done it. So, you know, I think we've been bold. I think we've been committed as you said, three and a half years ago, I promised you that we were going to do everything we possibly could. You know, people always say, you know, what's, what's the real benefit of this. And at the end of the day, customers and partners will be the real winners. This, this innovation, this sort of, as a service I think is going to expand our market, allow our customers to do more with Amazon than they could before. It's one of those rare cases, Dave, where I think one plus one equals about seven, really. >> I love the vision and excited to see the execution Ed and Anthony, thanks so much for coming back in the Cube. Congratulations on getting to this point and good luck. >> Anthony and Ed: Thank you. >> All right. And thank you for watching everybody. This is Dave Vellante for the Cube's continuous coverage of AWS storage day. Keep it right there. (upbeat music)

(upbeat music) >> According to storage guru, Fred Moore, 60 to 80% of all stored data is archival data leading to the need for what he calls the infinite archive, In this world digital customers require inexpensive access to archive data that's protected it's got to be available, durable, it's got to be able to scale and also has to support the governance and compliance edicts of the organizations. Welcome to this next session of the AWS storage day with The Cube. I'm your host, Dave Vellante. We're going to dig into the topic of archiving and digitally preserving data and we're joined by Joe Fitzgerald, who is the general manager of Amazon S3 Glacier, Joe. Welcome to the program. >> Hey Dave, it's great to be here. Thanks for having me. >> Yeah, I remember early last decade, AWS announced Glacier, it got a lot of buzz, and since then you've evolved your archival storage services, strategy and offerings. First question. Why should customers archive their data in AWS? >> That's a great question. I think Amazon S3 Glacier is a great place for customers to archive data and I think the preface that you gave, I think covers a lot of the reasons why customers are looking to archive data on the cloud. We're finding a lot of customers have a lot of data. And if you think about it, most of the world's data is cold by nature. It's not data that you're accessing all the time. So if you don't have an archival story as part of your data strategy, I think you're missing out on a cost savings opportunity. So one of the reasons we're finding customers looking to move data S3 glacier is because of cost with Glacier Deep archive we have an industry leading price point of a dollar per terabyte per month. I think another reason that we're finding customers wanting to move data to the cloud into glacier is because of the security, durability, and availability that we offer. Instead of having to worry about some of the most valuable data that your company has and worrying about that being in a tape library that doesn't get accessed very often on premises or offsite in a, in a data locker that you don't really have access to. And we offer the best story in terms of the durability and security and availability of that data. And I think the other reason that we're finding customers wanting to move data to S3 Glacier is just the flexibility and agility that having your data in the cloud offers. A lot of the data, you can put it in deep archive and have it sit there and not access it, but then if you have, you know, some sort of event that you want to access that data, you can get that back very quickly, as well as put to power the rest of the AWS offerings, whether that's our compute offerings, or our machine learning and analytics offerings. So you just have like unmatched, you know, flexibility, cost, and durability of your data. So we're finding a lot of customers looking to optimize their business by moving their archive data to the cloud. >> Let's stick on the business case for a minute. I mean, you kind of nailed the cost side of the equation. Clearly you mentioned several of the benefits, but, but for those customers that may not be leaning in to, to, to archive data, how do they think about the cost benefit analysis when you talk to customers, what are you hearing from them? The ones that have used your services to archive data, what are the benefits that they're getting? >> It's a great question. I think we find customers fall into a few different, you know, camps in use cases. And one thing that we recommend as a starting point is if you have a lot of data and you're not really familiar with your access patterns, like which what, what part of the data is warm, what part is cold, we offer a storage class called S3 intelligent tiering. And what that storage class does is it optimizes the placement of that data and the cost of that data based on the access patterns. So if, if it's data that is accessed very regularly, it'll sit in one of the warmer storage tiers. If it's, accessed infrequently, it'll move down into the infrequent access tier or into the archive or deep archive access tiers. So it's a great way for customers who are struggling to think about archive, because it's not something that every customer thinks about every day to get on automatic cost savings. And then for customers who have, you know, either larger amounts of data or, or better understand the access patterns, like, you know, some of the industries that we're seeing like in, you know, autonomous vehicles, you know, they, they might have, they might generate like tons of training data from, from, you know, from running the autonomous vehicles. And they kind of know, okay, this data it's, it's, we're not actively using it, but it's also very valuable. They don't want to throw it away, they'll choose to move that data into an archive tier. So a lot of it kind of comes down to the degree to which you're able to easily understand the access pattern of the data to figure out which storage class and which archive storage class match best to your use case. >> I get it, so if you add that deep archive tier, you auto-magically get the benefit thanks to the intelligent tiering. What about industry patterns? I mean, obviously highly regulated industries have compliance issues. You know,, data intensive industries are going to potentially have this because they want to lower lower costs, but do you see any patterns emerging? I mean, every industry kind of needs this, but, but are there any industries that are getting more bang from the buck that, that you see? >> I would say every industry definitely has archived data. So we have, we have customers in every vertical segment. I think some of the ones that we're definitely seeing more activity from would be, you know, media and entertainment customers are a great fit for archive. If you think about, you know, even like digital native studios who are, you know, generate, you know, very high definition footage and, you know, they take all that footage, they produce the movie, but they have a lot of original data that they, you know, they, they might reuse. You know, remaster director's cut or, you know, to use later. They're finding archive is a great fit for that. So they're able to use S3 standard for their active production, but when they're done finishing a movie or production, they can save all that valuable original footage and move it into deep archive and just know that it's going to be there whenever they might need to use it. Another use case for staying in media entertainment, you know, kind of similar to that. And this is a good use case for S3 Glacier is if, if you have like sports footage from like the '60s, and then, you know, there's like some sort of breaking news event about some athlete that you want to be able to cut a shot for the six o'clock news, with S3 Glacier and expedited retrievals, you're able to kind of get like that, you know, that data back in a couple of minutes and that way you have the benefit of like very low cost archive storage, but being able to get the immediacy of having some of that data back when you need it. So, that's just some of the examples that we're seeing in terms of how customers are using archives. >> I love that example because, you know, the, the prevailing wisdom is the older, you know, data is the less valuable it is, but if you can pull a clip up of, you know, Babe Ruth at the right time, even though it's a little grainy, wow. That's huge value for the-- >> Yeah, I mean, we're, we're finding like lots of customers that, you know, they've retained this data, they haven't known why they're going to need it. They just sort of intrinsically know this data is really valuable and, you know, we might need it. And then as they, you know, they look for new opportunities and they're like, hey, you know, we're, we're going to remaster this and they they've gone through a lot of digital transformation. So we're seeing companies have, you know, decades of original material moving to the cloud where we're also seeing, you know, fairly new startups who are also just generating lots of archive data. So it's just, you know, one of the many use cases we see from our customers who love Glacier. >> Data hoarder's heaven, I love it. Okay, Joe, let's wrap up, give us your closing thoughts, how you see the future of this business, where you want to take, take your, your business for your customers. >> I think mostly we, we just really want to help customers optimize their storage and realize the potential of their data. So for a lot of customers that really just comes down to knowing that S3 Glacier is a great and trusted place for their data, and that they're able to kind of meet their compliance and regulatory needs, but for, you know, a lot of other customers, they're, they're looking to kind of transform their business and reinvent themselves as they move to the cloud, and I think we're just excited by a lot of emerging use cases, and, you know, being able to find that flexibility of having like very low cost storage, as well as being able to get access to that data and, hook it up into the other AWS services and really realize the potential of their data. >> 100%, I mean, we've seen it over the decades, cost drops and use cases explode. Thank you, Joe. Thanks so much for coming on The Cube. >> Thanks a lot, Dave, it's been great being here. >> All right keep it right there for more storage and data insights. You're watching AWS Storage Day on The Cube. (upbeat music)

>>Welcome back to the cubes coverage of AWS storage. They were here in downtown Seattle, crisp downtown Seattle. Winter is coming we're to talk about the snow unintended and also the ever expanding cloud, the cloud it's in a way it's like the universe, it's moving out to the edge and to the data center, which is literally another edge node. If you think about it, Mark Curry is here as the general manager of AWS gateway and Sid Roy is the GM of AWS snow family. Folks. Welcome. Good to see you. Thank you. So mark, talk about how you think about on-prem and hybrid. >>That's an excellent question, Dave. So I represent a group of services called storage gateway, and that's exactly what storage gateway does. Is it bridges your on-prem applications with the cloud? And the way we do that is we deliver it with really four services that we all call it. We call it gateway is the first one being volume gateway. And what volume gateway does is give you a way to connect your block storage on prem with the cloud for file shares for backup is what popular application there. And, uh, for applications that can tolerate some latency and that's a traditional service, then we, uh, came out with something called virtual tape gateway, which I'm personally really excited about because we all know about, you know, the big clunky tapes that have been around for 50 years, that you have to have trucks pick up and go store in a mountain and all that, um, with the virtual tape gateway, what we can do is we all have our gateways install either as a software package on-prem or as an appliance hardware appliance, but we put the tape gateway on prem and the customer is able to back up their tapes to us. >>And we look like a tape drive, virtual tape dry. So what we're doing is we're allowing the customer to basically digitize in the cloud, all of their legacy tapes. And this I think is a huge industry and we've got some great customers there. One would be formula one. Um, they've used virtual tape library. Our gateway to, um, basically could reduce the recovery time from five days down to one. So big impact there. Uh, the next gateway is our file gateway. And what I felt gateway does, again, sits on-prem either the software package or as a hardware appliance and fell gateway exposed as both an SMB share for Microsoft traffic and then an NFS share for your NFS traffic. And basically what we do as we front end S3 with this gateway. And so the gateway caches, so your active workflow gets really great performance, but you can move your inactive data to the cloud in S3, uh, where you've got durable storage. >>It's, you know, it's over multiple regions. You can run all of our analytics on that, on that data as well. Um, a good example, there would be modernize. A company worked on the COVID vaccine. They used storage gateway the file version to move their instrumentation and scientific data into the cloud, where once it's up in S3 week, you know, we've got a really robust set of tools, allow them to do analytics on it. And then finally, but not least our last announcement was something called FSX gateway and FSX is a chemical product. So we offer FSX as a windows file system or file share in the cloud. Um, the, the gateway basically acts as a cache to that. So a customer can put our FSX gateway on prem in lieu of like a server of some sort, and we'll cash all the traffic for that active workflow again, and then push their inactive data back to the FSX file system in the cloud. >>Cool. Lots of ways to get data to the cloud compatibility >>Issues. So, excellent. Thank you for that. Mark said, >>We know about snowball snowcones snowmobile all the snows, where does that fit >>In? Yeah. So let me, let me talk about the AWS edge. First, the broader edge spectrum of AWS spans many things from snow to outpost, to IOT, where there's a lot of data being created at the edge within this edge spectrum. There's the rugged mobile edge, which is where snow plays, right? So snow's purpose is really to capture transform and optionally move the data from rugged edge to AWS, right? And in our portfolio we have different devices. Uh, so let me start with the stone device. We announced last year in 2020, uh, snow cone is a small, uh, tissue box sized device. You know, it, it, it is portable. It's highly mobile, portable, rugged. It can, it can capture data from rugged sensory and end points and industrial equipment. And once we capture the data, you can process the data locally right there. And then if you have to send the data back to AWS, you can ship the device back or use data sync to transfer the data back at VWs. >>Now, if you have higher compute needs, where you have what we call the core edge, where it's not portable, but you need to kind of process there. We have the snowball edge device now that can be single known or multi-node snowball edge devices in groups of clusters for storage at storage edge compute. There, you can process like large scale data capture and transform it right there with, you know, machine learning or other data management and analytics right there for real time and AI based edge local decisions. So I'll give you a couple of examples in each category. So for snowcones, for example, we are partnering with Facebook to deliver, uh, private, LTE based, uh, networks for, uh, remote and rural areas where the connectivity is not here there. Right? So, so, uh, we are serving those communities in partnership with Facebook to deliver private LTE networks. The second example I'll give you is with the snowball edge device, that multiple nodes, we, us air force recently demonstrated, uh, that ABM a system, which is the advanced battle management system, where they can do like a lot of data capture and local simulation with AI and ML on containers, right on the snow cone, uh, on the snowball edge devices. So those are two examples of how we're doing, uh, edge local processing and capture. >>Well, I think, I think you guys got it right. You got a lot of ways to get data on the on-ramps into the cloud, but I I'm particularly struck by your edge. You know, we didn't get into the it strategy, but the idea of processing locally, bringing machine learning, uh, you know, cause the future we think anyway is AI and for instance, where the data lives, right. And yet, like you said, if you want to bring it back and bring it back and we have ways to get it back. Right, exactly. I'll give you guys the last word. >>Well, I, I would just say, you know, our FSX gateways of relatively new announcement, it's got some really cool applications for, um, high-performance Microsoft applications, but also for remote offices that want to share files. >>Great. Well guys, mark said, thanks so much for coming on the cube. Thank you for sharing the insights and the data and really appreciate it. Okay. Thank you for watching. This is the cubes coverage of AWS storage day. Keep it right there.