from the cube studios in palo alto in boston bringing you data-driven insights from the cube and etr this is breaking analysis with dave vellante by our estimates aws will generate around nine billion dollars in storage revenue this year and is now the second largest supplier of enterprise storage behind dell we believe aws storage revenue will hit 11 billion in 2022 and continue to outpace on-prem storage growth by more than a thousand basis points for the next three to four years at its third annual storage day event aws signaled a continued drive to think differently about data storage and transform the way customers migrate manage and add value to their data over the next decade hello and welcome to this week's wikibon cube insights powered by etr in this breaking analysis we'll give you a brief overview of what we learned at aws's storage day share our assessment of the big announcement of the day a deal with netapp to run ontap natively in the cloud as a managed service and we'll share some new data on how we see the market evolving with aws executive perspectives on its strategy how it thinks about hybrid and where it fits into the emerging data mesh conversation let's start with a snapshot of the announcements made at storage day now as with most aws events this one had a number of announcements and introduced them at a pace that was predictably fast and oftentimes hard to follow here's a quick list of most of them with some comments on each the big big news is the announcement with netapp netapp and aws have engineered a solution which ports the rich netapp stack onto aws and will be delivered as a fully managed service this is a big deal because previously customers either had they had to make a trade-off they had a settle for cloud-based file service with less functionality than you could get with netapp on-prem or it had to lose the agility and elasticity of the cloud and the whole pay-by-the-drink model now customers can get access to a fully functional netapp stack with services like data reduction snaps clones the full multi-protocol support replication all the services ontap delivers in the cloud as a managed service through the aws console our estimate is that 80 of the data on-prem is stored in file format and that's not the revenue but that's the data and we all know about s3 object storage but the biggest market from a capacity standpoint is file storage you know this announcement reminds us quite a bit of the vmware cloud on aws deal but applied to storage netapp's aunt anthony lai told me dave this is bigger and we're going to come back to that in a moment aws announced s3 multi-region access points it's a service that optimizes storage performance it takes into account latency network congestion and the location of data copies to deliver data via the best route to ensure our best performance this is something we've talked about for quite some time using metadata to optimize that that access aws also announced improvements to s3 tiering where it will no longer charge for small objects of less than 128k so for example customers won't be charged for most metadata and other smaller objects remember aws years ago hired a bunch of emc engineers and those guys built a lot of tiering functionality into their boxes and we'll come back to that later in this episode aws also announced backup and monitoring tools to ensure backups are in compliance with regulations and corporate edicts this frankly is table stakes and was was overdue in my view aws also made a number of other announcements that have been well covered in the press around block storage and simplified data migration tools so we'll leave that to your perusal through other outlets i want to come back to the big picture on the market dynamics now as we've reported in previous breaking analysis segments aws storage revenue is on a path to 10 billion dollars we reported this last year this chart puts the market in context it shows our estimates for worldwide enterprise storage revenue in the calendar year 2021. this data is meant to include all storage revenue including primary secondary and archival storage and related maintenance services dell is the leader in the 60 billion market with aws now hot on its tail with 15 of the market in terms of the way we've cut it now in the pre-cloud days customers would tell us our storage strategy is the following we buy emc for block and netapp for file keeping it simple while remnants of this past habit continue the market is definitely changing as you can see here the companies highlighted in red represent the growing hyperscaler presence and you can see in the pi on the right they now account for around 25 percent of the market and they're growing much much faster than the on-prem vendors well over that thousand basis points when you combine them all a couple of other things to note in the data we're excluding kindrel from ibm's figures that's ibm spinout but including our estimates of storage software for example spectrums protect that is sold as part of the ibm cloud but not reported in ibm's income statement by the way pre-kindred spin ibm storage business we believe would approach the size of netapp's business now in the yellow we've highlighted the portion of hyper-converged that comprises storage this includes vmware nutanix cisco and others vmware and nutanix are the largest hci players but in total the storage piece of that market is less than two billion okay so the way to look at this market is changing traditional on-prem is vying for budgets with cloud storage services which are rapidly gaining presence in the market and we're seeing the on-prem piece evolve of course into as a service models with hpe's green lake dell's apex and other on-prem cloud-like models now let's come back to the netapp aws deal netapp as we know is the gold standard for file services they've been the market leader for a long long time and other than pure which is considerably smaller netapp is the one company that consistently was able to beat emc in the market emc developed its its nas business and developed on its own nasdaq and it bought isilon to compete with netapp with isilon's excellent global file system but generally netapp remains the best file storage company today now emerging disruptors like cumulo vast weka they would take issue with this statement and rightly so as they have really promising technology but netapp remains the king of the file hill you can't debate that now netapp however has had some serious headwinds as the largest independent storage player as seen in this etr chart the data shows a nine-year view of netapp's presence in the etr survey presence is referred to by etr as market share it's not traditional market share it measures the pervasiveness of responses in the etr survey over a thousand customers each quarter so the percentage of mentions essentially that netapp is getting and you can see well netapp remains a leader it has had a difficult time expanding its tam and it's become frankly less relevant in the eye in the grand scheme and the grand eyes of it buyers the company hit headwinds when it began migrating its base to ontap 8 and was late riding a number of new waves including flash but generally it is recovered from those headwinds and it's really now focused on the cloud opportunity opportunity as evidenced by this deal with aws now as i said earlier netapp evp anthony lai told me that this deal is bigger than vmware cloud on aws like me you may be wondering how can that be vmware is the leader in the data center it has half a million customers its deal with aws has been a tremendous success as seen in this etr chart the data here shows spending momentum or net score from when vmware cloud on aws was picked up in the etr surveys with a meaningful n which today is approaching 100 responses in the survey the yellow line is there for context it's vmware's overall business so repeat it buyers who responded vmware versus specifically vmware cloud on aws so you see vmware overall has a huge presence in the survey more than 600 n the red line is vmware cloud on aws and that red dotted line you see that that's that's my magic 40 mark anything above that line we consider elevated net score or spending velocity and while we saw some deceleration earlier this year in that line that top line for vmware cloud vmware cloud and aws has been consistently showing well in the survey well above that 40 percent line so could this netapp deal be bigger than vmware cloud on aws well probably not in our view but we like the strategy of netapp going cloud native on aws and aws's commitment to deliver this as a managed service now where could get interesting is across clouds in other words if netapp can take a page out of snowflake and build an abstraction layer that hides the underlying complexity of not only the aws cloud but also gcp and azure where you log into the netapp cloud netapp data cloud if you will just go ahead and steal steal it from snowflake and then netapp optimizes your on-prem your aws your azure and or your gcp file storage we see that as a winning strategy that could dramatically expand netapp's tam politically it may not sit well with aws but so what netapp has to go multi-cloud to expand that tam when the vmware deal was announced many people felt it was a one-way street where all the benefit would eventually accrue to aws in reality this has certainly been a near-term winner for aws and vmware and of course importantly vmware and aws join customers now longer term it's going to clearly be a win for aws because it gets access to vmware's customer base but we also think it will serve vmware well because it gives the company a clear and concise cloud strategy especially if it can go across clouds and eventually get to the edge so with this netapp aws deal will it be as big probably not in our view but it is big netapp in our view just leapfrogged the competition because of the deep engineering commitment aws has made this isn't a marketplace deal it's a native managed service and we think that's pretty huge okay we're going to close with a few thoughts on aws storage strategy and some other thoughts on hybrid talk about capturing mission critical workloads and where aws fits in the overall data mesh conversation which is one of our favorite topics first let's talk about aws's storage strategy overall as with other services aws approach is to give builders access to tools at a very granular level that means it does mean a lot of apis and access to primitives that are essentially building blocks while this may require greater developer skills it also allows aws to get to market quickly and add functionality faster than the competition enterprises however where they will pay up for solutions so this leaves some nice white space for partners and also competitors and especially the on-prem folks but let's hear from an aws executive i spoke to milan thompson bucheveck an aws vp on the cube and asked her to describe aws's storage strategy here's what she said play the clip we are 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 i've said this before uh 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 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 the the ability for us to route to intelligently router requests 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 as you hear and can see by milan's statements how these guys think outside the box mentality at the end of the day customers want rock solid storage that's dirt cheap and lightning fast they always have and they always will but what i'm hearing from aws is they think about delivering these capabilities in the broader context of an application or a business think deeper business integration not the traditional suppliers don't think about that as well but the services mentality the cloud services mentality is different than dropping off a box at a loading dock turning it over to a professional services organization and then moving on to the next deal now i also had a chance to speak with wayne dusso he's another aws vp in the storage group wayne do so is a long time tech athlete for years he was responsible for building storage arrays at emc aws as i said hired a bunch of emcs years ago and those guys did a lot of tiered storage so i asked wayne what's the difference in mentality when you're building boxes versus cloud services here's what he said 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 being constrained by only uh 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 from every industry accelerate uh 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 so each of the surfaces that we have in object block file movement services data services each of them provides very specific customer value in 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 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 concern so so the big difference is no constraints in the box but lots of opportunities to blend in with other services now all that said there are cases where the box is gonna win because of locality and and physics and latency issues you know particularly where latency is king that's where a box is gonna be advantageous and we'll come back to that in a bit okay but what about hybrid how does aws think about hybrid and on-prem here's my take and then let's hear from milan again the cloud is expanding it's moving out to the edge and aws looks at the data center as just another edge node and it's bringing its infrastructure as code mentality to that edge and of course to data centers so if aws is truly customer centric which we believe it is it will naturally have to accommodate on-prem use cases and it is doing just that here's how milan thompson-bucheveck explained how aws is thinking about hybrid roll the clip for us dave it always comes back to what the customer is 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 adudabi 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 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 fxs 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 evs for outposts for the same reason so look this is a case where the box or the appliance wins latency matters as we said and aws gets that this is where matt baker of dell is right it's not a zero-sum game this is especially accurate as it pertains to the cloud versus on-prem discussion but a budget dollar is a budget dollar and the dollar can't go to two places so the battle will come down to who has the best solution the best relationships and who can deliver the most rock solid storage at the lowest cost and highest performance let's take a look at mission critical workloads for a second we're seeing aws go after these it's doing a database it's doing it with block storage we're talking about oracle sap microsoft sql server db2 that kind of stuff high volume oltp transactions mission critical work now there's no doubt that aws is picking up a lot of low hanging fruit with business critical workloads but the really hard to move work isn't going without a fight frankly it's not going that fast aws and mace has made some improvements to block storage to remove some of the challenges related but generally we see this is a very long road ahead for aws and other cloud suppliers oracle is the king of mission critical work along with ibm mainframes and those infrastructures generally it's not easy to move to the cloud it's too risky it's too expensive and the business case oftentimes isn't there because very frequently you have to freeze applications to do so what generally what people are doing is they're building an abstraction layer over that putting that abstraction layer maybe in the cloud building new apps that can connect to the back end and the into the cloud but that back end is largely cemented and fossilized look it's all in the definition no doubt there's plenty of mission critical work that is going to move but just really depends on how you define it even aws struggles to move its most critical transaction systems off of oracle but we'll continue to keep an open mind there it's just that today we define the most mission-critical workloads as we define them we don't see a lot of movement to the hyperscale clouds and we're going to close with some thoughts on data mesh so one of our favorite topics we've written extensively about this and interviewed and are collaborating with jamaa dagani who has coined the term and we've announced a media collaboration with the data mesh community and believe it's a strong direction for the industry so we wanted to understand how aws thinks about data mesh and where it fits in the conversation here's what milan had to say about that play the clip 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 match 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 so it's very true that aws has customers that are implementing data mess data mesh data mess data mesh can be a data mess if you don't do it right jpmorgan chase is a firm that is doing that we've we've covered that they've got a great video out there check out the breaking analysis archive you'll see that hellofresh has also initiated a data mesh architecture in the cloud and several others are starting to pop up i think the point is the issues and challenges around data mesh are more organizational and process related and less focused on the technology platform look data by its very nature is decentralized so when mylan talks about customers building on centralized storage that's a logical view of the storage but not necessarily physically centralized it may be in a in a hybrid device it may be a copy that lives outside of that same physical location this is an important point as jpmorgan chase pointed out the data mesh must accommodate data products and services that are in the cloud and also on-prem it's got to be inclusive the data mesh looks at the data store as a node on the data mesh it shouldn't be confined by the technology whether it's a data warehouse a data hub a data mart or an s3 bucket so i would say this while people think of the cloud as a centralized walled garden and in many respects it is that very same cloud is expanding into a massively distributed architecture and that fits with the data mesh architectural model as i say the big challenges of data mesh are less technical and more cultural and we're super excited to see how data mesh plays out over time and we're really excited to be part of part of the the community and a media partner of the data mesh community okay that's it for now remember i publish each week on wikibon.com and siliconangle.com and these episodes they're all available as podcasts all you do is search for breaking analysis podcasts you can always connect on twitter i'm at d vellante or email me at david.velante at siliconangle.com i appreciate the comments you guys make on linkedin and don't forget to check out etr.plus for all the survey action this is dave vellante for the cube insights powered by etr be well and we'll see you next time [Music] you

(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.

(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]

>>from around the globe. It's the Cube presenting Cuban cloud brought to you by silicon angle. >>We continue >>with Cuban Cloud. We're here with Milan Thompson Bukovec, who's the vice president? Block and object storage at A W s, which comprise comprises elastic block storage, AWS s three and Amazon Glacier. Milan. Great to see you again. Thanks so much for coming on the program. >>Nice to be here. Thanks for having me, David. >>You're very welcome it So here we are. We're unpacking the future of cloud. And we'd love to get your perspectives on how customers should think about the future of infrastructure, things like applying machine intelligence to their data. But just to set the stage when we look back at the history of storage in the Cloud is obviously started with us three. And then a couple years later was introduced CBS for block storage. And those are the most well known services in the portfolio. But there's there's Mawr, this cold storage and new capabilities that you announced recently. It reinvent around, you know, super duper block storage and in tearing is another example. But it looks like AWS is really starting to accelerate and pick up the pace of customer >>options in >>storage. So my first question is, how should we think about this expanding portfolio? >>Well, I think you have to go all the way back to what customers air trying to do with their data. Dave, The path to innovation is paved by data. If you don't have data, you don't have machine learning. You don't have the next generation of analytics applications. That helps you chart a path forward into a world that seems to be changing every week. And so in orderto have that insight in orderto have that predictive forecasting that every company needs, regardless of what industry that you're in today. It all starts from data, and I think the key shift that I've seen is how customers are thinking about that data about being instantly usable, whereas in the past it might have been a backup. Now it's part of a data lake, and if you could bring that data into a data lake, you can have not just analytics or machine learning or auditing applications. It's really what does your application do for your business, and how can it take advantage of that vast amount of shared data set in your business. Awesome. >>So thank you. So I wanna I wanna make sure we're hitting on the big trends that you're seeing in the market. That kind of informing your strategy around the portfolio and what you're seeing with customers Instant usability. You you bring in machine learning into the equation. I think, um, people have really started to understand the benefits of of of cloud storage as a service on the pay paid by the drink and that whole whole model, obviously co vid has accelerated that cloud migration has accelerated. Anything else we're missing there. What are the other big trends that you see if any? >>Well, Dave, you did a good job of capturing a lot of the drivers. The one thing I would say that just sits underneath All of it is the massive growth of digital data year over year I. D. C. Says digital data is growing at a rate of 40% year over year, and that has been true for a while. And it's not going to stop. It's gonna keep on growing because the sources of that data acquisition keeps on expanding and whether it's coyote devices whether it is content created by users. That data is going to grow, and everything you're talking about depends on the ability to not just capture it and store it. But as you say, use it well, >>you know, and we talk about data growth a lot, and sometimes it becomes bromide. But I think the interesting thing that I've observed over the last a couple of decades really is that the growth is nonlinear on. It's really the curve is starting. Thio used to shape exponentially. You guys always talk about that flywheel. Effect it. It's really hard to believe, You know, people say trees don't grow to the moon. It seems like data does. >>It does. And what's interesting about working in the world of AWS storage Dave is that it's counterintuitive. But our goal without data growth is to make it cost effective. And so year over year, how could we make it cheaper and cheaper? Just have customers store more and more data so they can use it. But it's also to think about the definition of usage. And what kind of data is that? Eyes being tapped by businesses for their insights and make that easier than it's ever been before. Let me ask >>you a follow up question on that my life could I get asked this a lot? Or guy here comments a lot that yes, A W s continuously and rigorously reduces pricing. But it's just >>kind of >>following the natural curve of Moore's law or, you know, whatever. How >>do you >>respond to that? And there are other factors involved. Obviously, labor is another cost reducing factor. But what's the trend line say, >>Well, cost efficiencies in our DNA, Dave. We come to work every day and aws across all of our services, and we ask ourselves, How can we lower our costs and be able to pass that along to customers? As you say, there are many different aspects to cost. There's the cost of the storage itself is the cost of the data center. And that's really what we've seen impact a lot of customers that were slower or just getting started with removed. The cloud is they entered 2020 and then they found out exactly how expensive that data center was to maintain because they had to put in safety equipment and they had to do all the things that you have to do in a pandemic in a data center. And so sometimes that cost is a little bit hidden or won't show up until you really don't need to have it land. But the cost of managing that explosive growth of data is very riel. And when we're thinking about cost, we're thinking about cost in terms of how can I lower it on a per gigabyte per month basis? But we're also building into the product itself adaptive discounts like we have a storage class in S three that's called intelligent hearing. And in intelligence hearing, we have built in monitoring where, if particular objects aren't frequently accessed in a given month, ah, customer will automatically get a discounted price for that storage or a customer Can you know, as of late last year, say that they wanna automatically move storage in the storage class that has been stored, for example, longer than 100 and 80 days and saves 95% by moving it into archive storage, deep archives storage? And so it's not just, you know, relentlessly going after and lowering the cost of storage. It's also building into the products these new ways where we can adaptive Lee discount storage based on what a customer's storage is actually doing >>well. And I would, I would add to our audience, is the other thing that does has done is it's really forced transparency almost the same way that Amazon has done on retail. And now my mom, When we talked last I mentioned that s three was an object store. And of course, that's technically technically correct. But your comment to me was Dave. It's more than that. And you started to talk about sage Maker and AI and bringing in machine learning. And I wonder if you could talk a little bit about the future of how storage is gonna be leveraged in the cloud that's may be different than what we've been, you know, used to in the early days of s three and how your customers should be thinking about infrastructure not as bespoke services but as a suite of capabilities and maybe some of those adjacent adjacent services that you see as most leverage a ble for customers And why? >>Well, to tell this story, dude, we're gonna have to go a little bit back in time all the way back to the 19 nineties. Or before then, when all you had waas, a set of hardware appliance vendors that sold you appliances that you put in your data center and inherently created a data silo because those hardware appliances were hardwired to your application. And so an individual application that was dealing with auditing as an example wouldn't really be able to access the storage for another application. Because you know, the architecture er of that legacy world is tied to a data silo and s tree came out launched in 2000 and six and introduced very low cost storage. That is an object. And I'll tell you, Dave, you know, over the last 10 plus years, we have seen all kinds of data come into us three, whereas before it might have been backups or it might have been images and videos. Now a pretty substantial data set is our parquet files and orc files. Thes files are there for business analytics for more real time type of processing. And that has really been the trend of the future. Is taking these different files putting them in a shared file layer, So any application today or in the future can tap into that data. And so this idea of the shared file layer is a major trend that has been taking off for the last. I would say five or six years, and I expect that to not only keep on going, but to really open up the type of services that you can then do on that shared file layer and whether that sage maker or some of the machine learning introduced by our connect service, it's bringing together the data as a starting point. And then the applications can evolve very rapidly. On top of that, I want to >>ask your opinion about big data architectures. One of our guests, Jim Octagon E. She's amazing, uh, data architect, and she's put forth this notion of a distributed global mesh, and I picked him picking up on some of the comments. Andy Jassy made it at reinvent How essentially Hey, we're bringing a W s to the edge. We see the data center is just another edge. Notes. You're seeing this massive distributed system evolving. You guys have talked about that for a while, and data by its very nature is distributed. But we've had this tendency to put into it monolithic Data Lake or a data warehouse on bits sort of antithetical to that distributed nature. So how >>do >>you see that playing out? What do you see customers in the future doing in terms of their big data architectures? And what does that mean for storage? >>It comes down to the nature of the data and again, the usage and Dave. That's where I see the biggest difference in these modern data architectures from the legacy of 20 years ago is the idea that the data need drives the data storage. So let's taken example of the type of data that you always wanna have on the edge. We have customers today that need tohave storage in the field and whether the field of scientific research or oftentimes, it's content creation in the in the film industry or if it's for military operations. There's a lot of data that needs to be captured and analyzed in the field and for us, what that means is that you know we have a suite of products called Snowball and whether it's snowball or snow cone, take your pick. That whole portfolio of AWS services is targeted at customers that need to do work with storage at the edge. And so it you know, if you think about the need for multiple applications acting on the same data set, that's when you keep it in an AWS region. And what we've done in AWS storage is we've recognized that depending on the need of usage, where you put your data and how you interactive, it may vary. But we've built a whole set of services like data transfer to help make sure that we can connect data from, for example, that new snow cone into a region automatically. And so our goal Dave, is to make sure that when customers air operating at the edge or they're operating in the region, they have the same quality of storage service, and they have easy ways to go between them. You shouldn't have to pick. You should be able to do it all. >>So in the spirit of do it all, this is sort of age old dynamic in the tech business, where you've got the friction between the the best of breed and the integrated suite, and my question is around what you're optimizing for for customers. And can you have your cake and eat it too? In other words, why A W S storage does what makes a compelling? Is it because it's kind of a best of breed storage service? Or is it because it's integrated with a W S? Would you ever sub optimize one in in order to get an advantage to the other? Or can you actually, >>you >>know, have your cake and eat it, too? >>The way that we build storage is to focus on being both the breath of capabilities on the depth of capabilities. And so where we identify ah, particular need where we think that it takes a whole new service to deliver, we'll go build that service and example for that is FTP, our AWS sftp service, which you know there's a lot of sftp usage out there and there will be for a while because of the you know, the Legacy B two b type of architectures that still live in the business world today. And so we looked at that problem. We said, How are we gonna build that in the best depth way and the best focus? And we launched a separate service for them. And so our goal is to take the individual building blocks of CBS and Glacier and s three and make the best of class and the most comprehensive in the capabilities of what we can dio and where we identify very specific need. We'll go build a service for. But, Dave, you know, as an example for that idea of both depths and breath s three storage lands is a great example of that s three storage lands is a new capability that we launched last year. And what it does is it lets you look across all your regions and all your accounts and get a summary view of all your s three storage and whether that's buckets or, you know, the most active prefixes that you have and be able to drill down from that and that is built in to the S three service and available for any customer that wants to turn it on in the AWS Management Council. >>Right? And we we saw just recently made I called it super duper block storage. But you made some, you know, improvements and really addressing the highest performance. Um, I want to ask you So we've all learned about an experience the benefits of cloud over the last several years, and especially in the last 10 months during the pandemic. But one >>of >>the challenges, and it's particularly acute with bio is, of course, Leighton see and moving data around and accessing data remotely. It's It's a challenge for customers, you know, due to speed of light, etcetera. So my question is, how was a W s thinking about all that data that still resides on premises? I think we heard that reinvent. That's still 90% of the opportunities or or the workloads. They're still on Prem that live inside a customer's data center. So how do you tap into those and help customers innovate with on Prem data, particularly from a storage >>angle? Well, we always want to provide the best of class solution for those little Leighton see workloads, and that's why we launched Block Express just late last year. It reinvent and Black expresses a new capability and preview on top of our Iot to provisioned eye ops volume type, and what's really interesting about Block Express Dave, is that the way that we're able to deliver the performance of Block Express, which is sound performance with cloud elasticity, is that we went all the way down to the network layer and we customize the hardware software. And at the network Lehrer, we built a Block Express on something called SRD, which stands for a scalable, reliable diagrams. And basically, what is letting us to do is offload all of our EBS operations for Block Express on the Nitro card on hardware. And so that type of innovation where we're able Thio, you know, take advantage of modern cop commodity, multi tenant data center networks where we're sending in this new network protocol across a large number of network paths, and that that type of innovation all the way down to that protocol level helps us innovate in a way that's hard. In fact, I would say impossible for for other sound providers to kind of really catch up and keep up. And so we feel that the amount of innovation that we have for delivering those low latency workloads in our AWS cloud storage is is unlimited, really, Because of that ability to customize software, hardware and network protocols as we go along without requiring upgrades from a customer it just gets better and the customer benefits. Now if you want to stay in your data center, that's why we built outposts. And for outpost, we have EBS and we have s three for outposts. And our goal there is that some customers will have workloads where they want to keep them resident in the data center And for those customers, we want to give them that AWS storage opportunities as well. So >>thank you for coming back to block Express. So you call it in sand in the cloud eso Is that essentially you've you've comprises a custom built, essentially storage storage network. Is that is that right? What kind of what you just described? SRD? I think you call it. >>Yeah, it's SRT is used by other AWS services as well, but it is a custom network protocol that we designed to deliver the lowest latency experience on We're taking advantage of it with Block Express >>sticking with traditional data centers for a moment, I'm interested in your thoughts on the importance of the cloud you know, pricing approach I e. The consumption model to paid by the drink. Obviously, it's one of the most attractive features But But And I ask that because we're seeing what Andy Jassy first, who is the old Guard Institute? Flexible pricing models. Two of the biggest storage companies HP with Green Lake and Dell has this thing called Apex. They've announced such models for on Prem and and presumably, Cross Cloud. How >>do you think >>this is going to impact your customers Leverage of AWS cloud storage? Is it something that you have ah, opinion on? >>Yeah, I think it all comes down to again that usage of the storage And this is where I think there is an inherent advantage for our cloud storage. So there might be an attempt by the old guard toe lower prices or add flexibility. But the end of the day it comes down to what the customer actually needs to to. And if you think about gp three, which is the new E. B s volume, the idea with GP three is we're gonna pass along savings to the customer by making the storage 20% cheaper than GP two. And we're gonna make the product better by giving a great, reliable baseline performance. But we're also going to let customers who want to run work clothes like Cassandra on TBS tune their throughput separately, for example, from their capacity. So if you're running Cassandra, sometimes you don't need to change your capacity. Your storage capacity works just fine, but what happens with for example, Cassandra were quote is that you may need more throughput. And if you're buying hardware appliance, you just have to buy for your peak. You have to buy for the max of what you think, your throughput in the max of what your storage is and this inherent flexibility that we have for AWS storage and being able to tune throughput separate from IOP, separate from capacity like you do for GP three. That is really where the future is for customers having control over costs and control over customer experience without compromising or trading off either one. >>Awesome. Thank you for that. So another time we have remaining my line. I want to talk about the topic of diversity. Uh, social impact on Daz. Ah, woman leader, women executive on. I really wanna get your perspectives on this, and I've shared with the audience previously. One of my breaking analysis segments your your boxing video, which is awesome and eso so you've got a lot of unique, non traditional aspects to your to your life, and and I love it. But I >>want to >>ask you this. So it's obviously, you know, certainly politically and socially correct to talk about diversity, the importance of diversity. There's data that suggests that that that diversity is good both economically, not just socially. And of course, it's the right thing to do. But there are those. Peter Thiel is probably the most prominent, but there are others who say, You know what, >>But >>get that. Just hire people just like you will be able to go faster, ramp up more quickly, hit escape velocity. It's natural. And that's what you should dio. Why is that not the right approach? Why is diversity both course socially responsible, but also good for business? >>For Amazon, we think about diversity as something that is essential toe how we think about innovation. And so, Dave, you know, as you know, from listening to some of the announcements I reinvent, we launched a lot of new ideas, new concepts and new services in AWS and just bringing that lends down to storage U. S. Tree has been reinventing itself every year since we launched in 2000 and six. PBS introduced the first Son on the Cloud late last year and continues to reinvent how customers think about block storage. We would not be able Thio. Look at a product in a different way and think to ourselves Not just what is the legacy system dio in a data center today. But how do we want to build this new distributed system in a way that helps customers achieve not just what they're doing today, but what they want to do in five and 10 years? You can't get that innovative mindset without bringing different perspectives to the table. And so we strongly believe in hiring people who are from underrepresented groups and whether that's gender or it's related racial equality or if its geographic, uh, diversity and bringing them in tow have the conversation. Because those divers viewpoints inform how we can innovate at all levels in a W s >>right. And so I really appreciate the perspectives on that, and we've had a zoo. You probably know the Cube has been, you know, a very big advocate of diversity, you know, generally, but women in tech Specifically, we participated a lot. And you know, I often ask this question is, you know, as a smaller company, uh, I and some of my other colleagues in in small business Sometimes we struggle. Um and so my question is, how >>how do >>you go beyond What's your advice for going beyond, you know, the good old boys network? I think its large companies like AWS and the big players you've got a responsibility to that. You can put somebody in charge and make it you know, their full time job. How should smaller companies, um, that are largely white, male dominated? How should they become more diverse? What should they do? Thio increase that diversity? >>Well, I think the place to start his voice. A lot of what we try to dio is make sure that the underrepresented voice is heard. And so, Dave, any small business owner of any industry can encourage voice for your under represented or your unheard populations. And honestly, it is a simple as being in a meeting and looking around that table, we're on your screen as it were and asking yourself Who hasn't talked? Who hasn't weighed in particularly if the debate is contentious or even animated. And you will see, particularly if you note this. Over time you will see that there may be somebody and whether it's an underrepresented, a group or its ah woman whose early career or it's it's not. It's just a member of your team who happens to be a white male to who's not being hurt. And you can ask that person for their perspective. And that is a step that every one of us can and should do, which is asked toe, have everyone's voice at the table, toe listen and to weigh in on it. So I think that is something everyone should dio. I think if you are a member of an underrepresented groups, as for example, I'm Vietnamese American and I'm the female in Tech. I think it z something to think about how you can make sure that you're always taking that bold step forward. And it's one of the topics that we covered it at reinvent. We had a great discussion with a group of women CEOs, and a lot of it we talked about is being bolt, taking the challenge of being bold in tough situations, and that is an important thing, I think, for anybody to keep in mind, but especially for members of underrepresented groups, because sometimes Dave, that bold step that you kind of think of is like, Oh, I don't know if I should ask for that promotion or I don't know if I should volunteer for that project It's not. It's not a big ask, but it's big in your head. And so if you can internalize as a member of some, you know, a group that maybe hasn't heard or seen as much how you can take those bold challenges and step forward and learn, maybe fell also because that's how you learn. Then that is a way toe. Also have people learn and develop and become leaders in whatever industry it ISS. It's >>great advice, and I reminds me of, I mean, I think most of us can relate to that my land, because when we started in the industry, we may be timid. You didn't want to necessarily speak up, and I think it's incumbent upon those in a position of power. And by the way, power might just be running a meeting agenda to maybe calling those folks that are. Maybe it's not diversity of gender or, you know, our or race. And maybe it's just the underrepresented. Maybe that's a good way to start building muscle memory. So that's unique advice that I hadn't heard before. So thank you very much for that. Appreciate it. And, uh hey, listen, thanks so much for coming on the Cuban cloud. Uh, we're out of time and and really, always appreciate your perspectives. And you're doing a great job, and thank you. >>Great. Thank you, Dave. Thanks for having me and have a great day. >>All right? And keep it right, everybody. You're watching the cube on cloud right back.

>> We continue with cube on cloud. We here with Mai-Lan Tomsen Bukovec who's the vice president of block and object storage at AWS which comprises elastic block storage, AWS S3 and Amazon glacier. Mai-Lan Great to see you again. Thanks so much for coming on the program. >> Nice to be here. Thanks for having me, Dave. >> You're very welcome. So here we're unpacking the future of cloud and we'd love to get your perspectives on how customers should think about the future of infrastructure things like applying machine intelligence to their data but just to set the stage, when we look back at the history of storage and the cloud has obviously started with S3 and then a couple of years later AWS introduced EBS for block storage and those are the most well-known services in the portfolio but there's more of this cold storage and new capabilities that you announced recently at reinvent around, you know, super-duper block storage and in tiering is another example. But it looks like AWS is really starting to accelerate and pick up the pace of customer options in storage. So my first question is how should we think about this expanding portfolio? >> Well, I think you have to go all the way back to what customers are trying to do with their data Dave. The path to innovation is paved by data. If you don't have data, you don't have machine learning. You don't have the next generation of analytics applications that helps you chart a path forward into a world that seems to be changing every week. And so in order to have that insight in order to have that predictive forecasting that every company needs, regardless of what industry that you're in today, it all starts from data. And I think the key shift that I've seen is how customers are thinking about that data, about being instantly usable. Whereas in the past, it might've been a backup. Now it's part of a data lake. And if you can bring that data into a data lake you can have not just analytics or machine learning or auditing applications, it's really what does your application do for your business and how can it take advantage of that vast amount of shared data set in your business? >> Awesome, so thank you. So I want to make sure we're hitting on the big trends that you're seeing in the market that kind of are informing your strategy around the portfolio, and what you're seeing with customers. Instant usability, you know, you bring in machine learning into the equation. I think people have really started to understand the benefits of cloud storage as a service and the pay by the drink. and that whole model. Obviously COVID has accelerated that, you know, cloud migration is accelerated. Anything else we're missing there? What are the other big trends that you see? If any. >> Well, Dave, you did a good job of capturing a lot of the drivers. The one thing I would say that just sits underneath all of it is the massive growth of digital data year over year. IDC says digital data is growing at a rate of 40% year over year. And that has been true for a while and it's not going to stop. It's going to keep on growing because the sources of that data acquisition keeps on expanding and whether it's IOT devices whether it is a content created by users, that data is going to grow and everything you're talking about depends on the ability to not just capture it and store it. But as you say, use it. >> Well, you know, and we talk about data growth a lot and sometimes it can, it becomes bromide. But I think the interesting thing that I've observed over the last couple of decades really is that the growth is non-linear and it's really the curve is starting to shape exponentially. You guys always talk about that flywheel effect it's really hard to believe, you know people say trees don't grow to the moon. It seems like data does. >> It does and what's interesting about working in a world of AWS storage Dave is that it's counter-intuitive but our goal with a data growth is to make it cost effective. And so year over year how can we make it cheaper and cheaper? It is have customers store more and more data so they can use it. But it's also to think about the definition of usage and what kind of data is being tapped by businesses for their insights and make that easier than it's ever been before. >> Let me ask you a follow up question on that Mai-Lan. Cause I get asked this a lot, or I hear comments a lot that yes AWS continuously and rigorously reduces pricing but it's just kind of following the natural curve of Moore's law or whatever. How do you respond to that? Are there other factors involved? Obviously labor is another, you know, cost reducing factor, but what's the trend line say? >> Well, cost efficiency is in our DNA, Dave we come to work every day in AWS across all of our services and we ask ourselves, how can we lower our costs and be able to pass that along to customers. As you say, there are many different aspects to costs. There's a cost to the storage itself There's a cost to the data center. And that's really what we've seen impact a lot of customers that were slower or just getting started with a move to the cloud, is they entered 2020 and then they found out exactly how expensive that data center was to maintain because they had to put in safety equipment and they had to do all the things that you have to do in a pandemic, in a data center. And so sometimes that cost is a little bit hidden or it won't show up until you really don't need to have it land. But the costs of managing that explosive growth of data is very real. And when we're thinking about costs, we're thinking about costs in terms of how can I lower it on a per gigabyte per month basis, but we're also building into the product itself, adaptive discounts. Like we have a storage class in S3 that's called intelligent tiering. And in intelligent tiering we have built-in monitoring where if particular objects aren't frequently accessed in a given month, a customer will automatically get a discounted price for that storage or a customer can, you know, as of late last year say that they want to automatically move storage in the storage class that has been stored for example longer than 180 days and saves 95% by moving it into deep archive storage. And so it's not just, you know relentlessly going after and lowering the cost of storage. It's also building into the products these new ways where we can adaptively discount storage based on what a customer's storage is actually doing. >> Right, and I would add to already is the other thing Gatos has done is it's really forced transparency almost the same way that Amazon has done on retail. And now Mai-Lan when we talked last I mentioned that S3 was an object store. And of course that's technically correct but your comment to me was Dave, it's more than that. And you started to talk about SageMaker and AI and bringing in machine learning. And I wonder if you could talk a little bit about the future of how storage is going to be leveraged in the cloud. That's maybe different than what we've been used to in the early days of S3. And how your customers should be thinking about infrastructure, not as bespoke services, but as a suite of capabilities and maybe some of those adjacent services that you see as most leverageable for customers and why? >> Well, to tell this story, Dave, we're going to have to go a little bit back in time, all the way back to the 1990s or before then. When all you had was a set of hardware appliance vendors that sold you appliances that you put in your data center and inherently created a data silo because those hardware appliances were hardwired to your application. And so an individual application that was dealing with auditing as an example wouldn't really be able to access the storage for another application, because you know, the architecture of that legacy world is tied to a data silo and S3 came out launched in 2006 and introduced very low cost storage. That is an object. And I'll tell you, Dave, you know, over the last 10 plus years we have seen all kinds of data coming to S3. Whereas before it might've been backups or it might've been images and videos. Now a pretty substantial data set is our parquet files and work files. These files are there for business analytics for more real-time type of processing. And that has really been the trend of the future, is taking these different files putting them in a shared file layer, so any application today or in the future can tap into that data. And so this idea of the shared file layer is a major trend that has been taking off for the last I would say five or six years. And I expect that to not only keep on going but to really open up the type of services that you can then do on that shared file layer. And whether that's Sage maker or some of the machine learning introduced by our connect service, it's bringing together the data as a starting point and then the applications can evolve very rapidly on top of that. >> I want to ask your opinion about big data architectures. One of our guests Chamakh Tigani, she's amazing data architect. And she's put forth this notion of a distributed global mesh. And picking up on some of the comments, Andy Jassy made it at re-invent how essentially, "Hey we're bringing AWS to the edge. "We see the data center is just another edge node." So you're seeing this massive distributed system evolving. You guys have talked about that for a while and data by its very nature is distributed but we've had this tendency to put it into a monolithic data Lake or a data warehouse and it's sort of antithetical to that distributed nature. So how do you see that playing out? What do you see customers in the future doing in terms of their big data architectures and what does that mean for storage? >> It comes down to the nature of the data and again the usage and Dave that's where I see the biggest difference in these modern data architectures from the legacy of 20 years ago, is the idea that the data need drives the data storage. So let's take an example of the type of data that you always want to have on the edge. We have customers today that need to have storage in the field and whether the field of scientific research or oftentimes it's content creation in the film industry, or if it's for military operations there's a lot of data that needs to be captured and analyzed in the field. And for us, what that means is that, you know we have a suite of products called snow ball and whether it's snow ball or snow cone, take your pick. That whole portfolio of AWS services is targeted at customers that need to do work with storage at the edge. And so, you know, if you think about the need for multiple applications acting on the same data set that's when you keep it in an AWS region. And what we've done in AWS storage is we've recognized that depending on the need of usage where you put your data and how you interact with it may vary. But we've built a whole set of services like data transfer to help make sure that we can connect data from, for example that new snow cone into a region automatically. And so our goal Dave is to make sure that when customers are operating at the edge or they're operating in the region they have the same quality of storage service and they have easy ways to go between them. You shouldn't have to pick, you should be able to do it all. >> So in the spirit of do it all there's this sort of age old dynamic in the tech business where you've got the friction between the best of breed and the integrated suite. And my question is around what you're optimizing for customers. And can you have your cake and eat it too? In other words, why AWS storage? What makes it compelling? Is it because it's kind of a best of breed storage service or is it because it's integrated with AWS? Would you ever sub optimize one in order to get an advantage to the other? Or can you actually, you know have your cake and eat it too? >> The way that we build storage is to focus on being both the breadth of capabilities and the depth of capabilities. And so where we identify a particular need where we think that it takes a whole new service to deliver we'll go build that service. And an example for that as FTP our AWS SFTP service, which, you know, there's a lot of SFTP usage out there and there will be for a while because of the, you know, the legacy B2B type of architectures that still live in the business world today. And so we looked at that problem. We said, how are we going to build that in the best depth way, in the best focus? And we launched a separate service for that. And so our goal is to take the individual building blocks of EBS and glacier and S3 and make the best of class and the most comprehensive in the capabilities of what we can do and where we identify a very specific need. We'll go build a service for it. But Dave, you know as an example for that idea of both depth and breadth, S3 Storage Lens is a great example of that. S3 Storage Lens is a new capability that we launched late last year. And what it does is it lets you look across all your regions and all your accounts and get a summary view of all your S3 storage and whether that's buckets or the most active prefixes that you have and be able to drill down from that. And that is built in to the S3 service and available for any customer that wants to turn it on in the AWS management console. >> Right, and we saw just recently made, I called it super-duper block storage but you can make some improvements in really addressing the highest performance. I want to ask you, so we've all learned about an experience that benefits of cloud over the last several years and especially in the last 10 months during the pandemic but one of the challenges and it's particularly acute with IO is of course latency and moving data around and accessing data remotely. It's a challenge for customers, you know, due to speed of light, et cetera. So my question is how was AWS thinking about all that data that's still resides on premises? I think we heard at reinvent, that's still on 90% of the opportunity is, or the the workloads are still on prem that live inside a customer's data centers. So how do you tap into those and help customers innovate with on-prem data, particularly from a storage angle? >> Well, we always want to provide the best of class solution for those little latency workloads. And that's why we launched Block Express just late last year at reinvent. And Block Express has a new capability in preview on top of our IO to provisioned IOPS volume type. And what's really interesting about block express Dave is that the way that we're able to deliver the performance of Block Express, which is sound performance with cloud elasticity is that we went all the way down to the network layer and we customize the hardware software. And at the network layer we built Block Express on something called SRD which stands for a scalable reliable diagrams. And basically what it's letting us do is offload all of our EBS operations for Block Express on the nitrile card on hardware. And so that type of innovation where we're able to, you know, take advantage of modern cop commodity, multi-tenant data center networks, where we're sending in this new network protocol across a large number of network paths. And that type of innovation all the way down to that protocol level helps us innovate in a way that's hard. In fact, I would say impossible for other sound providers to kind of really catch up and keep up. And so we feel that the amount of innovation that we have for delivering those low latency workloads in our AWS cloud storage is unlimited really because of that ability to customize software hardware and network protocols as we go along without requiring upgrades from a customer it just gets better. And the customer benefits. Now, if you want to stay in your data center that's why we build outposts. And for outposts, we have UVS and we have S3 for outposts and our goal there is that some customers will have workloads where they want to keep them resident in the data center. And for those customers we want to give them that AWS storage opportunities as well. >> So thank you for coming back to Block Express. So you call it, you know, sand in the cloud. So is that essentially it comprises a custom built essentially storage network. Is that right? What you just described SRD? I think you called it. >> Yeah, it's a SRD is used by other AWS services as well but it is a custom network protocol that we designed to deliver the lowest latency experience and we're taking advantage of it with Block Express. >> So sticking with traditional data centers for a moment I'm interested in your thoughts on the importance of the cloud pricing approach, I.e the consumption model to pay by the drink. Obviously it's one of the most attractive features, and I asked that because we're seeing what Andy Jassy refers to as the old guard Institute, flexible pricing models two of the biggest storage companies, HP with GreenLake and Dell has this thing called apex. They've announced such models for on-prem and presumably cross cloud. How do you think this is going to impact your customers leverage of AWS cloud storage? Is it something that you have an opinion on? >> Yeah, I think it all comes down to, again that usage of the storage, and this is where I think there's an inherent advantage for our cloud storage. So there might be an attempt by the old guard to lower prices or add flexibility but at the end of the day it comes down to what the customer actually needs to tune. And if you think about gp3 which is the new EBS volume. The idea with gp3 is we're going to pass a long savings to the customer by making the storage 20% cheaper than gp2. And we're going to make the product better by giving a great, reliable baseline performance. But we're also going to let customers who want to run workloads like Cassandra on EBS tune their throughput separately, for example from their capacity. So if you're running Cassandra sometimes you don't need to change your capacity. Your storage capacity works just fine. But what happens with, for example Cassandra workload is that you may need more throughput. And if you're buying hardware appliance you just have to buy for your peak. You have to buy for the max of what you think your throughput and the max of what your storage is. And this inherent flexibility that we have for AWS storage and being able to tune throughput separate from up separate from capacity like you do for gp3 that is really where the future is for customers having control over costs and control over customer experience without compromising or trading off either one. >> Awesome, thank you for that. So in the time we have remaining Mai-Lan, I want to talk about the topic of diversity social impact, and as a woman leader, women executive, and I really want to get your perspectives on this. And I've shared with the audience previously, one of my breaking analysis segments, your boxing video which is awesome. And so, you've got a lot of unique non-traditional aspects to your life and I love it, but I want to ask you this. So it's obviously, you know, certainly politically and socially correct to talk about diversity, the importance of diversity, there's data that suggests that diversity is good both economically, not just socially, and of course it's the right thing to do. But there are those, you know, Peter teal is probably the most prominent but there are others that say, "You know what? "Forget that, just hire people, just like you'll be able "to go faster, ramp up more quickly, hit escape "velocity it's natural." And that's what you should do. Why is that not the right approach? Why is diversity both, of course, socially, you know responsible, but also, you know, good for business >> For Amazon we think about diversity as something that is essential to how we think about innovation. And so, Dave, as you know, from listening to some of the announcements at reinvent, we launch a lot of new ideas, like new concepts and new services in AWS. And just bringing that lens down to storage. Astri has been reinventing itself every year since we launched in 2006. EBS introduced the first sun on the cloud late last year, and continues to reinvent how customers think about block storage. We would not be able to look at a product in a different way and think to ourselves, not just what is the legacy system do in a data center today but how do we want to build this new distributed system in a way that helps customers achieve not just what they're doing today, but what they want to do in five and 10 years. You can't get that innovative mindset without bringing different perspectives to the table. And so we strongly believe in hiring people who are from under represented groups and whether that's gender or it's related to racial equality or if it's geographic diversity and bringing them in to have the conversation because those diverse viewpoints inform how we can innovate at all levels in AWS. >> Right, and so I really appreciate their perspectives on that. And we've had, as you probably know the cube has been, you know a very big advocate of diversity, you know, generally but women in tech specifically, we participated a lot. And I often ask this question is, you know, as a smaller company, I, and some of my other colleagues in small business, sometimes we struggle. And so my question is how do you go beyond what's your advice for going beyond, you know the good old boys network? I think it's large companies like AWS and, you know, the big players, you've got responsibility too that you can put somebody in charge and make it their full-time job. How should smaller companies that are largely white male dominated, how should they become more diverse? What should they do to increase that diversity? >> I think the place to start is voice. A lot of what we try to do is make sure that the under represented voice is heard. And so Dave, any small business owner of any industry can encourage voice for your under represented or your unheard populations. And honestly, it is as simple as being in a meeting and looking around that table or on your screen, as it were and asking yourself, who hasn't talked? Who hasn't weighed in? Particularly if the debate is contentious or even animated. And you will see, particularly if you note this over time you will see that there may be somebody and whether it's an under represented group or it's a woman who's early career, or it's not it's just a member of your team who happens to be a white male too, who's not being heard. And you can ask that person for their perspective. And that is a step that every one of us can and should do which is ask to have everyone's voice at the table to listen and to weigh in on it. So I think that is something everyone should do. I think if you are a member of an under represented group as for example, I'm Vietnamese American and I'm a female in tech, I think, it's something to think about how you can make sure that you're always taking that bold step forward. And it's one of the topics that we covered at re-invent. We had a great discussion with a group of women CEOs and a lot of it we talked about is being bold taking the challenge of being bold in tough situations. And that is an important thing, I think for anybody to keep in mind, but especially for members of under represented groups, because sometimes Dave that bold step that you kind of think of as like, "Oh I don't know if I should ask for that promotion." or "I don't know if I should volunteer for that project." It's not a big ask, but it's big in your head. And so if you can internalize as a member of some, you know, a group that maybe isn't heard as or seen as much how you can take those bold challenges and step forward and learn, maybe fail also cause that's how you learn. Then that is a way to also have people learn and develop and become leaders in whatever industry it is. >> That's great advice. It reminds me of, I think most of us can relate to that Mai-Lan, because when we started in the industry, we may be timid. You didn't want to necessarily speak up. And I think it's incumbent upon those in a position of power. And by the way power might just be running a meeting agenda to maybe call on those folks that are, maybe it's not diversity of gender or, you know, or race. Maybe it's just the under represented. Maybe that's a good way to start building muscle memory. So that's unique advice that I hadn't heard before. So thank you very much for that. I appreciate it. And Hey, listen. Thanks so much for coming on the Cube On Cloud. We're out of time and really always appreciate your perspectives and you're doing a great job. And thank you. >> Great, thank you Dave. Thanks for having me and have a great day. >> All right, and Keep it right there buddy. You're watching the Cube On Cloud. Right back. (gentle upbeat music)

>>from around the globe. It's the Cube with digital coverage of AWS reinvent 2020 sponsored by Intel and AWS. Yeah, hello, everyone, and welcome back to the Cubes Walter Wall coverage of AWS reinvent 2020. We've gone virtual along with reinvent and we heard in Andy Jassy is hours long. Keynote a number of new innovations in the area of storage. And with me to talk about that is Milan Thompson Bukovec. She's the vice president of Block and Object Storage and AWS. That's everything. Elastic block storage s three Glacier, the whole portfolio Milon. Thanks for coming on. >>Great to see you. >>Great to see you too. So you heard Andy. We all heard Andy talk a lot about reinventing different parts of the platform, reinventing industries and a really kind of exciting and visionary put talk that he put forth. Let's >>talk >>about storage, though. How is storage reinventing itself? >>Well, as you know, cloud storage was essentially invented by a W s a number of years ago. And whether that's in 2000 and six, when US three was launched, or 2000 and eight when CBS was launched and we first came up with this model of pay as you go for durable, attached storage. Too easy to instances. And so we haven't stopped and we haven't slowed down. If anything, we've picked up the rate of reinvention that we've done across the portfolio for storage. I think, as Andy called out, speed matters. And it matters for how customers air thinking about how do they pivot and move to the cloud as quickly as they can, particularly this year. And it matters a lot in storage as well, because the changing access patterns of what customers air doing with their new cloud applications, you know they're they're transforming their businesses and their applications, and they need a modern storage platform underneath it. And that's what you have with AWS Storage. And he talked about some of the key releases, particularly in block storage. It's actually kind of amazing. What's what's been done with CBS is here. We launched GP three GP two was the previous generation general purpose volume type. We launched that in 2000 and 14 again thief, first type of general purpose volume that had this great combination of simplicity and price, and just about everybody uses it for a boot or often a data volume. And with GP three, which was available yesterday with Andy's announcement, we added four times peak throughput on top of GP two, and it's a 20% lower storage price per gigabyte per month. And we took the feedback. The number one feedback we got on GP to which was how can I separate buying throughput and I ops from storage capacity? And that is really important. That goes back to the promise of the cloud. And it goes back to being able to pick what aspect do you want to scale your storage on? And so, with GP three, you could buy a certain amount of capacity. And if you're good with that capacity, but you need more throughput, more eye ops, you can buy those independently. And that is that fine grained customization for those changing data patterns that I just talked about. And it's available for GP three today. >>Yeah, that was I looked at that, like my life is a knob that you could turn Okay, juice my eye ops. And don't touch my capacity. I'm happy there. I don't wanna pay for more of it. >>And thio add to that it's a knob you could turn if you need it. We have more throughput, more eye ops as a baseline capacity for your storage capacity than we did for GP to. But then you can tune it based on whatever you need, not just now, but in the future. >>So so given the pandemic, I mean, how has that affected E? Everybody is talking about going to the cloud, because where else you gonna go? But But how has that affected what customers are doing this year, and does it change your roadmap at all? Does it change your thinking? >>Well, I have to say, there's two main things that we've seen. One is it's really accelerated customers thinking about getting off of on premises and into the club. It's done that because nobody really wants to manage the data center. And if there's ever a year you don't want to manage the data center, it's 2020 and it's because, particularly with storage appliances, it takes a long time to acquire. Let's just take storage area networks or sense super expensive. You get a fixed amount of capacity you have to acquire. It takes months to come in you gotta rack and stack. Then you gotta change all your networking and maintain it. Ah, lot of customers don't want to do that. And so what it's done for us is it's really, uh, you know, accelerated our thinking and you saw yesterday and Andy's keynote as well. Of how do we build the first san in the cloud? And we launched Io two. In August of this year, we introduced the first nines of durability, again reinventing how people think about durability and their block storage. But just this week we now have a Iot to block Express with 2 56 K ai ops, four K megabytes of throughput in 64 terabytes of capacity, that sand level performance. And it's available for preview because I 02 is going to be your son in the cloud. And that is a direct correlation to what we hear from customers, which is how can I get away from these expensive on premises purchases like Sands and combine the performance with the elasticity that I need? So that's the first thing. How can we accelerate getting off of these very rigid procurement cycles that we have and having to manage a data center. It's not just for EBS, its for S. Trias. Well, the second thing we're hearing from customers is how can I have the agility? So you talk to customers as well. He talked to CEOs and C. T. O s. It's been a crazy year in 2020. It was one thing that a company has to do its pivot. It's really figure out. How are you going to adjust and adjust quickly? And so we have customers like Ontario Telehealth Network up in Canada, where they went from 8000 to 30,000 users because they're doing virtual health for Ontario. And we have other customers who, you know, that's a pivot. That's an increase. And we have other customers, like APS Flyer, where their goal is to just save money without changing their application. And they also did a pivot. They used the intelligence hearing storage class, which is the most popular storage class, as three offers for data lakes, and they were able to make that change save 18% on their storage cost, no change of their application, just using the capabilities of AWS. And so his ability to pivot helped you know really make us think and accelerate what we're building as well. And so one of the things that we launched just recently for intelligent hearing is we added two new archival tears to intelligent hearing. And those are archival tears, you know, just like intelligence hearing automatically watches every object industry storage and your data lake and gives you dynamic pricing based on if it's frequently accessed in a month or inflict infrequently accessed, you can turn on archival tear. And if your object your pork a file, for example, isn't access or your backup isn't access for 90 days, intelligence hearing will automatically move it to glacier characteristics of archival or too deep archive and give you the same price. A dollar, a terabyte per month. If your data is an access to 180 days, it's done automatically, and it means you save up to 90% 95% and cost on that storage. And so, if you if you think about those two trends, how can I get away from getting locked into those on premises Hardware cycles? How can I get away from it faster for sands and other hardware appliances and then the other trend is how can I pivot and use the innovation and the reinvention in our storage services to just save money and be more agile in these changing conditions? >>So I gotta ask you follow up question on staying in the cloud, because when you think of sand, you think of switches. You think of complexity, but I get that you're connecting to the performance of a sand. But you guys are all about simplicity. So how did you What's behind there? Can you take us under the covers? Just you guys build your own little storage network because it's cloud. It's gotta be fast and simple. >>That's right. When we're thinking about performance and cost, we go down to the metal for this stuff. We think about Unicosta a very fine grained level, and when we're building new technology that we know is gonna be the foundation for everything we're doing for that high performance, we went down to the protocol level. We're using something called Us RD. It's all rolled up under the hood for Block Express, and it's the foundation of that super super high performance. As you know, there's a lot of engineering behind the scenes in the cloud and for for what we've done this year, as part of that reinvention we've reinvented all the way down to the protocol way. >>Let me ask you that the two things that come up in our survey when you talk to CEOs, they say two priorities. Security is actually second cloud migration actually popped up to the top. So where does storage fit in that whole notion about cloud migration, >>Storage eyes, usually where a lot of people start, you know, Luckily, with a W s, you don't have to choose between security or cloud of migration. Security is job one for every AWS service. And so when customers air thinking about how do I move an application, they gotta move the data first. And so they start from the from the data. What storage do I use? What is the best fit for the storage and how do I best secure that's storage? And so the innovation that we dio on storage always comes with that. That combination of, you know, migration, the set of tools that we provide for getting data from on premises into the cloud. We have tools like aws data sync which do a great job of this on. Then we also look at things like how do we continue to take the profile of security forward? And one example of that is something we launched just this week called Bucket keys s three bucket keys. And it drops the cost of using kms for service side encryption with us three by over 90%. And the way it does it is that we've integrated those two services super closely together so that you can minimize the amount of costs that you make for very, very frequent request. Because in data lakes you have millions and billions of objects and our goal is to make security so cost effective people don't even think about it. That also goes for other parts of the platform. We have guard duty for us three now, and what that does is security anomaly detection automatically to track your access patterns across as three and flag when something is not quite what it should be. And so this idea of like how do I not only get my data into the cloud? But then how do I take advantage of the breath of the storage portfolio, but also the breath of the AWS services to really maximize that security profile as well as the access patterns that I want from my application. >>Well, my way hit the major announcements and unfortunately, out of time. But I really would love to have you back and go deeper and have you share your vision of what the cloud storage piece looks like going forward. Thanks so much for coming in. The Cube is great to have you. >>Great to be here. Thanks, Dave. CIA. >>See you later and keep it right, everybody. You're watching the cubes. Coverage of aws reinvent 2020 right back.