(upbeat music) >> Welcome back, everyone to CUBE Supercloud 22. I'm John Furrier, your host. Got a great influencer, Cloud Cloud RRT segment with Sarbjeet Johal, Cloud influencer, Cloud economist, Cloud consultant, Cloud advisor. Sarbjeet, welcome back, CUBE alumni. Good to see you. >> Thanks John and nice to be here. >> Now, what's your title? Cloud consultant? Analyst? >> Consultant, actually. Yeah, I'm launching my own business right now formally, soon. It's in stealth mode right now, we'll be (inaudible) >> Well, I'll just call you a Cloud guru, Cloud influencer. You've been great, friend of theCUBE. Really powerful on social. You share a lot of content. You're digging into all the trends. Supercloud is a thing, it's getting a lot of traction. We introduced that concept last reinvent. We were riffing before that. As we kind of were seeing the structural change that is now Supercloud, it really is kind of the destination or outcome of what we're seeing with hybrid cloud as a steady state into the what's now, they call multicloud, which is kind of awkward. It feels like it's default. Like multicloud, multi-vendor, but Supercloud has much more of a comprehensive abstraction around it. What's your thoughts? >> As you said, as Dave says that too, the Supercloud has that abstraction built into it. It's built on top of cloud, right? So it's being built on top of the CapEx which is being spent by likes of AWS and Azure and Google Cloud, and many others, right? So it's leveraging that infrastructure and building software stack on top of that, which is a platform. I see that as a platform being built on top of infrastructure as code. It's another platform which is not native to the cloud providers. So it's like a kind of cross-Cloud platform. That's what I said. >> Yeah, VMware calls it that cloud-cross cloud. I'm not a big fan of the name but I get what you're saying. We had a segment on earlier with Adrian Cockcroft, Laurie McVety and Chris Wolf, all part of the Cloud RRT like ourselves, and you've involved in Cloud from day one. Remember the OpenStack days Early Cloud, AWS, when they started we saw the trajectory and we saw the change. And I think the OpenStack in those early days were tell signs because you saw the movement of API first but Amazon just grew so fast. And then Azure now is catching up, their CapEx is so large that companies like Snowflake's like, "Why should I build my own? "I just sit on top of AWS, "move fast on one native cloud, then figure it out." Seems to be one of the playbooks of the Supercloud. >> Yeah, that is true. And there are reasons behind that. And I think number one reason is the skills gravity. What I call it, the developers and/or operators are trained on one set of APIs. And I've said that many times, to out compete your competition you have to out educate the market. And we know which cloud has done that. We know what traditional vendor has done that, in '90s it was Microsoft, they had VBS number one language and they were winning. So in the cloud era, it's AWS, their marketing efforts, their go-to market strategy, the micro nature of the releasing the micro sort of features, if you will, almost every week there's a new feature. So they have got it. And other two are trying to mimic that and they're having low trouble light. >> Yeah and I think GCP has been struggling compared to the three and native cloud on native as you're right, completely successful. As you're caught up and you see the Microsoft, I think is a a great selling point around multiple clouds. And the question that's on the table here is do you stay with the native cloud or you jump right to multicloud? Now multicloud by default is kind of what I see happening. We've been debating this, I'd love to get your thoughts because, Microsoft has a huge install base. They've converted to Office 365. They even throw SQL databases in there to kind of give it a little extra bump on the earnings but I've been super critical on their numbers. I think their shares are, there's clearly overstating their share, in my opinion, compared to AWS is a need of cloud, Azure though is catching up. So you have customers that are happy with Microsoft, that are going to run their apps on Azure. So if a customer has Azure and Microsoft that's technically multiple clouds. >> Yeah, true. >> And it's not a strategy, it's just an outcome. >> Yeah, I see Microsoft cloud as friendly to the internal developers. Internal developers of enterprises. but AWS is a lot more ISV friendly which is the software shops friendly. So that's what they do. They just build software and give it to somebody else. But if you're in-house developer and you have been a Microsoft shop for a long time, which enterprise haven't been that, right? So Microsoft is well entrenched into the enterprise. We know that, right? >> Yeah. >> For a long time. >> Yeah and the old joke was developers love code and just go with a lock in and then ops people don't want lock in because they want choice. So you have the DevOps movement that's been successful and they get DevSecOps. The real focus to me, I think, is the operating teams because the ops side is really with the pressure vis-a-vis. I want to get your reaction because we're seeing kind of the script flip. DevOps worked, infrastructure's code has worked. We don't yet see security as code yet. And you have things like cloud native services which is all developer, goodness. So I think the developers are doing fine. Give 'em a thumbs up and open source's booming. So they're shifting left, CI/CD pipeline. You have some issues around repo, monolithic repos, but devs are doing fine. It's the ops that are now have to level up because that seems to be a hotspot. What's your take? What's your reaction to that? Do you agree? And if you say you agree, why? >> Yeah, I think devs are doing fine because some of the devs are going into ops. Like the whole movement behind DevOps culture is that devs and ops is one team. The people who are building that application they're also operating that as well. But that's very foreign and few in enterprise space. We know that, right? Big companies like Google, Microsoft, Amazon, Twitter, those guys can do that. They're very tech savvy shops. But when it comes to, if you go down from there to the second tier of enterprises, they are having hard time with that. Once you create software, I've said that, I sound like a broken record here. So once you create piece of software, you want to operate it. You're not always creating it. Especially when it's inhouse software development. It's not your core sort of competency to. You're not giving that software to somebody else or they're not multiple tenants of that software. You are the only user of that software as a company, or maybe maximum to your employees and partners. But that's where it stops. So there are those differences and when it comes to ops, we have to still differentiate the ops of the big companies, which are tech companies, pure tech companies and ops of the traditional enterprise. And you are right, the ops of the traditional enterprise are having tough time to cope up with the changing nature of things. And because they have to run the old traditional stacks whatever they happen to have, SAP, Oracle, financial, whatnot, right? Thousands of applications, they have to run that. And they have to learn on top of that, new scripting languages to operate the new stack, if you will. >> So for ops teams do they have to spin up operating teams for every cloud specialized tooling, there's consequences to that. >> Yeah. There's economics involved, the process, if you are learning three cloud APIs and most probably you will end up spending a lot more time and money on that. Number one, number two, there are a lot more problems which can arise from that, because of the differences in how the APIs work. The rule says if you pick one primary cloud and then you're focused on that, and most of your workloads are there, and then you go to the secondary cloud number two or three on as need basis. I think that's the right approach. >> Well, I want to get your take on something that I'm observing. And again, maybe it's because I'm old school, been around the IT block for a while. I'm observing the multi-vendors kind of as Dave calls the calisthenics, they're out in the market, trying to push their wears and convincing everyone to run their workloads on their infrastructure. multicloud to me sounds like multi-vendor. And I think there might not be a problem yet today so I want to get your reaction to my thoughts. I see the vendors pushing hard on multicloud because they don't have a native cloud. I mean, IBM ultimately will probably end up being a SaaS application on top of one of the CapEx hyperscale, some say, but I think the playbook today for customers is to stay on one native cloud, run cloud native hybrid go in on OneCloud and go fast. Then get success and then go multiple clouds. versus having a multicloud set of services out of the gate. Because if you're VMware you'd love to have cross cloud abstraction layer but that's lock in too. So what's your lock in? Success in the marketplace or vendor access? >> It's tricky actually. I've said that many times, that you don't wake up in the morning and say like, we're going to do multicloud. Nobody does that by choice. So it falls into your lab because of mostly because of what MNA is. And sometimes because of the price to performance ratio is better somewhere else for certain kind of workloads. That's like foreign few, to be honest with you. That's part of my read is, that being a developer an operator of many sort of systems, if you will. And the third tier which we talked about during the VMworld, I think 2019 that you want vendor diversity, just in case one vendor goes down or it's broken up by feds or something, and you want another vendor, maybe for price negotiation tactics, or- >> That's an op mentality. >> Yeah, yeah. >> And that's true, they want choice. They want to get locked in. >> You want choice because, and also like things can go wrong with the provider. We know that, we focus on top three cloud providers and we sort of assume that they'll be there for next 10 years or so at least. >> And what's also true is not everyone can do everything. >> Yeah, exactly. So you have to pick the provider based on all these sort of three sets of high level criteria, if you will. And I think the multicloud should be your last choice. Like you should not be gearing up for that by default but it should be by design, as Chuck said. >> Okay, so I need to ask you what does Supercloud in my opinion, look like five, 10 years out? What's the outcome of a good Supercloud structure? What's it look like? Where did it come from? How did it get there? What's your take? >> I think Supercloud is getting born in the absence of having standards around cloud. That's what it is. Because we don't have standards, we long, or we want the services at different cloud providers, Which have same APIs and there's less learning curve or almost zero learning curve for our developers and operators to learn that stuff. Snowflake is one example and VMware Stack is available at different cloud providers. That's sort of infrastructure as a service example if you will. And snowflake is a sort of data warehouse example and they're going down the stack. Well, they're trying to expand. So there are many examples like that. What was the question again? >> Is Supercloud 10 years out? What does it look like? What's the components? >> Yeah, I think the Supercloud 10 years out will expand because we will expand the software stack faster than the hardware stack and hardware stack will be expanding of course, with the custom chips and all that. There was the huge event yesterday was happening from AWS. >> Yeah, the Silicon. >> Silicon Day. And that's an eyeopening sort of movement and the whole technology consumption, if you will. >> And yeah, the differentiation with the chips with supply chain kind of herding right now, we think it's going to be a forcing function for more cloud adoption. Because if you can't buy networking gear you going to go to the cloud. >> Yeah, so Supercloud to me in 10 years, it will be bigger, better in the likes of HashiCorp. Actually, I think we need likes of HashiCorp on the infrastructure as a service side. I think they will be part of the Supercloud. They are kind of sitting on the side right now kind of a good vendor lost in transition kind of thing. That sort of thing. >> It's like Kubernetes, we'll just close out here. We'll make a statement. Is Kubernetes a developer thing or an infrastructure thing? It's an ops thing. I mean, people are coming out and saying Kubernetes is not a developer issue. >> It's ops thing. >> It's an ops thing. It's in operation, it's under the hood. So you, again, this infrastructure's a service integrating this super pass layer as Dave Vellante and Wikibon call it. >> Yeah, it's ops thing, actually, which enables developers to get that the Azure service, like you can deploy your software in sort of different format containers, and then you don't care like what VMs are those? And, but Serverless is the sort of arising as well. It was hard for a while now it's like the lull state, but I think Serverless will be better in next three to five years on. >> Well, certainly the hyperscale is like AWS and Azure and others have had great CapEx and investments. They need to stay ahead, in your opinion, final question, how do they stay ahead? 'Cause, AWS is not going to stand still nor will Azure, they're pedaling as fast as they can. Google's trying to figure out where they fit in. Are they going to be a real cloud or a software stack? Same with Oracle. To me, it's really, the big race is now with AWS and Azure's nipping at their heels. Hyperscale, what do they need to do to differentiate going forward? >> I think they are in a limbo. They, on one side, they don't want to compete with their customers who are sitting on top of them, likes of Snowflake and others, right? And VMware as well. But at the same time, they have to keep expanding and keep innovating. And they're debating within their themselves. Like, should we compete with these guys? Should we launch similar sort of features and functionality? Or should we keep it open? And what I have heard as of now that internally at AWS, especially, they're thinking about keeping it open and letting people sort of (inaudible)- >> And you see them buying some the Cerner with Oracle that bought Cerner, Amazon bought a healthcare company. I think the likes of MongoDB, Snowflake, Databricks, are perfect examples of what we'll see I think on the AWS side. Azure, I'm not so sure, they like to have a little bit more control at the top of the stack with the SaaS, but I think Databricks has been so successful open source, Snowflake, a little bit more proprietary and closed than Databricks. They're doing well is on top of data, and MongoDB has got great success. All of these things compete with AWS higher level services. So, that advantage of those companies not having the CapEx investment and then going multiple clouds on other ecosystems that's a path of customers. Stay one, go fast, get traction, then go. >> That's huge. Actually the last sort comment I want to make is that, Also, that you guys include this in the definition of Supercloud, the likes of Capital One and Soner sort of vendors, right? So they are verticals, Capital One is in this financial vertical, and then Soner which Oracle bar they are in this healthcare vertical. And remember in the beginning of the cloud and when the cloud was just getting born. We used to say that we will have the community clouds which will be serving different verticals. >> Specialty clouds. >> Specialty clouds, community clouds. And actually that is happening now at very sort of small level. But I think it will start happening at a bigger level. The Goldman Sachs and others are trying to build these services on the financial front risk management and whatnot. I think that will be- >> Well, what's interesting, which you're bringing up a great discussion. We were having discussions around these vertical clouds like Goldman Sachs Capital One, Liberty Mutual. They're going all in on one native cloud then going into multiple clouds after, but then there's also the specialty clouds around functionality, app identity, data security. So you have multiple 3D dimensional clouds here. You can have a specialty cloud just on identity. I mean, identity on Amazon is different than Azure. Huge issue. >> Yeah, I think at some point we have to distinguish these things, which are being built on top of these infrastructure as a service, in past with a platform, a service, which is very close to infrastructure service, like the lines are blurred, we have to distinguish these two things from these Superclouds. Actually, what we are calling Supercloud maybe there'll be better term, better name, but we are all industry path actually, including myself and you or everybody else. Like we tend to mix these things up. I think we have to separate these things a little bit to make things (inaudible) >> Yeah, I think that's what the super path thing's about because you think about the next generation SaaS has to be solved by innovations of the infrastructure services, to your point about HashiCorp and others. So it's not as clear as infrastructure platform, SaaS. There's going to be a lot of interplay between this levels of services. >> Yeah, we are in this flasker situation a lot of developers are lost. A lot of operators are lost in this transition and it's just like our economies right now. Like I was reading at CNBC today, and here's sort of headline that people are having hard time understanding what state the economy is in. And so same is true with our technology economy. Like we don't know what state we are in. It's kind of it's in the transition phase right now. >> Well we're definitely in a bad economy relative to the consumer market. I've said on theCUBE publicly, Dave has as well, not as aggressive. I think the tech is still in a boom. I don't think there's tech bubble at all that's bursting, I think, the digital transformation from post COVID is going to continue. And this is the first recession downturn where the hyperscalers have been in market, delivering the economic value, almost like they're pumping on all cylinders and going to the next level. Go back to 2008, Amazon web services, where were they? They were just emerging out. So the cloud economic impact has not been factored into the global GDP relationship. I think all the firms that are looking at GDP growth and tech spend as a correlation, are completely missing the boat on the fact that cloud economics and digital transformation is a big part of the new economics. So refactoring business models this is continuing and it's just the early days. >> Yeah, I have said that many times that cloud works good in the bad economy and cloud works great in the good economy. Do you know why? Because there are different type of workloads in the good economy. A lot of experimentation, innovative solutions go into the cloud. You can do experimentation that you have extra money now, but in the bad economy you don't want to spend the CapEx because don't have money. Money is expensive at that point. And then you want to keep working and you don't need (inaudible) >> I think inflation's a big factor too right now. Well, Sarbjeet, great to see you. Thanks for coming into our studio for our stage performance for Supercloud 22, this is a pilot episode that we're going to get a consortium of experts Cloud RRT like yourselves, in the conversation to discuss what the architecture is. What is a taxonomy? What are the key building blocks and what things need to be in place for Supercloud capability? Because it's clear that if without standards, without defacto standards, we're at this tipping point where if it all comes together, not all one company can do everything. Customers want choice, but they also want to go fast too. So DevOps is working. It's going the next level. We see this as Supercloud. So thank you so much for your participation. >> Thanks for having me. And I'm looking forward to listen to the other sessions (inaudible) >> We're going to take it on A stickers. We'll take it on the internet. I'm John Furrier, stay tuned for more Supercloud 22 coverage, here at the Palo Alto studios in one minute. (bright music)

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