(light music) >> Hi everybody. Welcome to this Cube Conversation. I'm really pleased to announce a collaboration with Rob Strechay. He's a guest cube analyst, and we'll be working together to extract the signal from the noise. Rob is a long-time product pro, working at a number of firms including AWS, HP, HPE, NetApp, Snowplow. I did a stint as an analyst at Enterprise Strategy Group. Rob, good to see you. Thanks for coming into our Marlboro Studios. >> Well, thank you for having me. It's always great to be here. >> I'm really excited about working with you. We've known each other for a long time. You've been in the Cube a bunch. You know, you're in between gigs, and I think we can have a lot of fun together. Covering events, covering trends. So. let's get into it. What's happening out there? We're sort of exited the isolation economy. Things were booming. Now, everybody's tapping the brakes. From your standpoint, what are you seeing out there? >> Yeah. I'm seeing that people are really looking how to get more out of their data. How they're bringing things together, how they're looking at the costs of Cloud, and understanding how are they building out their SaaS applications. And understanding that when they go in and actually start to use Cloud, it's not only just using the base services anymore. They're looking at, how do I use these platforms as a service? Some are easier than others, and they're trying to understand, how do I get more value out of that relationship with the Cloud? They're also consolidating the number of Clouds that they have, I would say to try to better optimize their spend, and getting better pricing for that matter. >> Are you seeing people unhook Clouds, or just reduce maybe certain Cloud activities and going maybe instead of 60/40 going 90/10? >> Correct. It's more like the 90/10 type of rule where they're starting to say, Hey I'm not going to get rid of Azure or AWS or Google. I'm going to move a portion of this over that I was using on this one service. Maybe I got a great two-year contract to start with on this platform as a service or a database as a service. I'm going to unhook from that and maybe go with an independent. Maybe with something like a Snowflake or a Databricks on top of another Cloud, so that I can consolidate down. But it also gives them more flexibility as well. >> In our last breaking analysis, Rob, we identified six factors that were reducing Cloud consumption. There were factors and customer tactics. And I want to get your take on this. So, some of the factors really, you got fewer mortgage originations. FinTech, obviously big Cloud user. Crypto, not as much activity there. Lower ad spending means less Cloud. And then one of 'em, which you kind of disagreed with was less, less analytics, you know, fewer... Less frequency of calculations. I'll come back to that. But then optimizing compute using Graviton or AMD instances moving to cheaper storage tiers. That of course makes sense. And then optimize pricing plans. Maybe going from On Demand, you know, to, you know, instead of pay by the drink, buy in volume. Okay. So, first of all, do those make sense to you with the exception? We'll come back and talk about the analytics piece. Is that what you're seeing from customers? >> Yeah, I think so. I think that was pretty much dead on with what I'm seeing from customers and the ones that I go out and talk to. A lot of times they're trying to really monetize their, you know, understand how their business utilizes these Clouds. And, where their spend is going in those Clouds. Can they use, you know, lower tiers of storage? Do they really need the best processors? Do they need to be using Intel or can they get away with AMD or Graviton 2 or 3? Or do they need to move in? And, I think when you look at all of these Clouds, they always have pricing curves that are arcs from the newest to the oldest stuff. And you can play games with that. And understanding how you can actually lower your costs by looking at maybe some of the older generation. Maybe your application was written 10 years ago. You don't necessarily have to be on the best, newest processor for that application per se. >> So last, I want to come back to this whole analytics piece. Last June, I think it was June, Dev Ittycheria, who's the-- I call him Dev. Spelled Dev, pronounced Dave. (chuckles softly) Same pronunciation, different spelling. Dev Ittycheria, CEO of Mongo, on the earnings call. He was getting, you know, hit. Things were starting to get a little less visible in terms of, you know, the outlook. And people were pushing him like... Because you're in the Cloud, is it easier to dial down? And he said, because we're the document database, we support transaction applications. We're less discretionary than say, analytics. Well on the Snowflake earnings call, that same month or the month after, they were all over Slootman and Scarpelli. Oh, the Mongo CEO said that they're less discretionary than analytics. And Snowflake was an interesting comment. They basically said, look, we're the Cloud. You can dial it up, you can dial it down, but the area under the curve over a period of time is going to be the same, because they get their customers to commit. What do you say? You disagreed with the notion that people are running their calculations less frequently. Is that because they're trying to do a better job of targeting customers in near real time? What are you seeing out there? >> Yeah, I think they're moving away from using people and more expensive marketing. Or, they're trying to figure out what's my Google ad spend, what's my Meta ad spend? And what they're trying to do is optimize that spend. So, what is the return on advertising, or the ROAS as they would say. And what they're looking to do is understand, okay, I have to collect these analytics that better understand where are these people coming from? How do they get to my site, to my store, to my whatever? And when they're using it, how do they they better move through that? What you're also seeing is that analytics is not only just for kind of the retail or financial services or things like that, but then they're also, you know, using that to make offers in those categories. When you move back to more, you know, take other companies that are building products and SaaS delivered products. They may actually go and use this analytics for making the product better. And one of the big reasons for that is maybe they're dialing back how many product managers they have. And they're looking to be more data driven about how they actually go and build the product out or enhance the product. So maybe they're, you know, an online video service and they want to understand why people are either using or not using the whiteboard inside the product. And they're collecting a lot of that product analytics in a big way so that they can go through that. And they're doing it in a constant manner. This first party type tracking within applications is growing rapidly by customers. >> So, let's talk about who wins in that. So, obviously the Cloud guys, AWS, Google and Azure. I want to come back and unpack that a little bit. Databricks and Snowflake, we reported on our last breaking analysis, it kind of on a collision course. You know, a couple years ago we were thinking, okay, AWS, Snowflake and Databricks, like perfect sandwich. And then of course they started to become more competitive. My sense is they still, you know, compliment each other in the field, right? But, you know, publicly, they've got bigger aspirations, they get big TAMs that they're going after. But it's interesting, the data shows that-- So, Snowflake was off the charts in terms of spending momentum and our EPR surveys. Our partner down in New York, they kind of came into line. They're both growing in terms of market presence. Databricks couldn't get to IPO. So, we don't have as much, you know, visibility on their financials. You know, Snowflake obviously highly transparent cause they're a public company. And then you got AWS, Google and Azure. And it seems like AWS appears to be more partner friendly. Microsoft, you know, depends on what market you're in. And Google wants to sell BigQuery. >> Yeah. >> So, what are you seeing in the public Cloud from a data platform perspective? >> Yeah. I think that was pretty astute in what you were talking about there, because I think of the three, Google is definitely I think a little bit behind in how they go to market with their partners. Azure's done a fantastic job of partnering with these companies to understand and even though they may have Synapse as their go-to and where they want people to go to do AI and ML. What they're looking at is, Hey, we're going to also be friendly with Snowflake. We're also going to be friendly with a Databricks. And I think that, Amazon has always been there because that's where the market has been for these developers. So, many, like Databricks' and the Snowflake's have gone there first because, you know, Databricks' case, they built out on top of S3 first. And going and using somebody's object layer other than AWS, was not as simple as you would think it would be. Moving between those. >> So, one of the financial meetups I said meetup, but the... It was either the CEO or the CFO. It was either Slootman or Scarpelli talking at, I don't know, Merrill Lynch or one of the other financial conferences said, I think it was probably their Q3 call. Snowflake said 80% of our business goes through Amazon. And he said to this audience, the next day we got a call from Microsoft. Hey, we got to do more. And, we know just from reading the financial statements that Snowflake is getting concessions from Amazon, they're buying in volume, they're renegotiating their contracts. Amazon gets it. You know, lower the price, people buy more. Long term, we're all going to make more money. Microsoft obviously wants to get into that game with Snowflake. They understand the momentum. They said Google, not so much. And I've had customers tell me that they wanted to use Google's AI with Snowflake, but they can't, they got to go to to BigQuery. So, honestly, I haven't like vetted that so. But, I think it's true. But nonetheless, it seems like Google's a little less friendly with the data platform providers. What do you think? >> Yeah, I would say so. I think this is a place that Google looks and wants to own. Is that now, are they doing the right things long term? I mean again, you know, you look at Google Analytics being you know, basically outlawed in five countries in the EU because of GDPR concerns, and compliance and governance of data. And I think people are looking at Google and BigQuery in general and saying, is it the best place for me to go? Is it going to be in the right places where I need it? Still, it's still one of the largest used databases out there just because it underpins a number of the Google services. So you almost get, like you were saying, forced into BigQuery sometimes, if you want to use the tech on top. >> You do strategy. >> Yeah. >> Right? You do strategy, you do messaging. Is it the right call by Google? I mean, it's not a-- I criticize Google sometimes. But, I'm not sure it's the wrong call to say, Hey, this is our ace in the hole. >> Yeah. >> We got to get people into BigQuery. Cause, first of all, BigQuery is a solid product. I mean it's Cloud native and it's, you know, by all, it gets high marks. So, why give the competition an advantage? Let's try to force people essentially into what is we think a great product and it is a great product. The flip side of that is, they're giving up some potential partner TAM and not treating the ecosystem as well as one of their major competitors. What do you do if you're in that position? >> Yeah, I think that that's a fantastic question. And the question I pose back to the companies I've worked with and worked for is, are you really looking to have vendor lock-in as your key differentiator to your service? And I think when you start to look at these companies that are moving away from BigQuery, moving to even, Databricks on top of GCS in Google, they're looking to say, okay, I can go there if I have to evacuate from GCP and go to another Cloud, I can stay on Databricks as a platform, for instance. So I think it's, people are looking at what platform as a service, database as a service they go and use. Because from a strategic perspective, they don't want that vendor locking. >> That's where Supercloud becomes interesting, right? Because, if I can run on Snowflake or Databricks, you know, across Clouds. Even Oracle, you know, they're getting into business with Microsoft. Let's talk about some of the Cloud players. So, the big three have reported. >> Right. >> We saw AWSs Cloud growth decelerated down to 20%, which is I think the lowest growth rate since they started to disclose public numbers. And they said they exited, sorry, they said January they grew at 15%. >> Yeah. >> Year on year. Now, they had some pretty tough compares. But nonetheless, 15%, wow. Azure, kind of mid thirties, and then Google, we had kind of low thirties. But, well behind in terms of size. And Google's losing probably almost $3 billion annually. But, that's not necessarily a bad thing by advocating and investing. What's happening with the Cloud? Is AWS just running into the law, large numbers? Do you think we can actually see a re-acceleration like we have in the past with AWS Cloud? Azure, we predicted is going to be 75% of AWS IAS revenues. You know, we try to estimate IAS. >> Yeah. >> Even though they don't share that with us. That's a huge milestone. You'd think-- There's some people who have, I think, Bob Evans predicted a while ago that Microsoft would surpass AWS in terms of size. You know, what do you think? >> Yeah, I think that Azure's going to keep to-- Keep growing at a pretty good clip. I think that for Azure, they still have really great account control, even though people like to hate Microsoft. The Microsoft sellers that are out there making those companies successful day after day have really done a good job of being in those accounts and helping people. I was recently over in the UK. And the UK market between AWS and Azure is pretty amazing, how much Azure there is. And it's growing within Europe in general. In the states, it's, you know, I think it's growing well. I think it's still growing, probably not as fast as it is outside the U.S. But, you go down to someplace like Australia, it's also Azure. You hear about Azure all the time. >> Why? Is that just because of the Microsoft's software state? It's just so convenient. >> I think it has to do with, you know, and you can go with the reasoning they don't break out, you know, Office 365 and all of that out of their numbers is because they have-- They're in all of these accounts because the office suite is so pervasive in there. So, they always have reasons to go back in and, oh by the way, you're on these old SQL licenses. Let us move you up here and we'll be able to-- We'll support you on the old version, you know, with security and all of these things. And be able to move you forward. So, they have a lot of, I guess you could say, levers to stay in those accounts and be interesting. At least as part of the Cloud estate. I think Amazon, you know, is hitting, you know, the large number. Laws of large numbers. But I think that they're also going through, and I think this was seen in the layoffs that they were making, that they're looking to understand and have profitability in more of those services that they have. You know, over 350 odd services that they have. And you know, as somebody who went there and helped to start yet a new one, while I was there. And finally, it went to beta back in September, you start to look at the fact that, that number of services, people, their own sellers don't even know all of their services. It's impossible to comprehend and sell that many things. So, I think what they're going through is really looking to rationalize a lot of what they're doing from a services perspective going forward. They're looking to focus on more profitable services and bringing those in. Because right now it's built like a layer cake where you have, you know, S3 EBS and EC2 on the bottom of the layer cake. And then maybe you have, you're using IAM, the authorization and authentication in there and you have all these different services. And then they call it EMR on top. And so, EMR has to pay for that entire layer cake just to go and compete against somebody like Mongo or something like that. So, you start to unwind the costs of that. Whereas Azure, went and they build basically ground up services for the most part. And Google kind of falls somewhere in between in how they build their-- They're a sort of layer cake type effect, but not as many layers I guess you could say. >> I feel like, you know, Amazon's trying to be a platform for the ecosystem. Yes, they have their own products and they're going to sell. And that's going to drive their profitability cause they don't have to split the pie. But, they're taking a piece of-- They're spinning the meter, as Ziyas Caravalo likes to say on every time Snowflake or Databricks or Mongo or Atlas is, you know, running on their system. They take a piece of the action. Now, Microsoft does that as well. But, you look at Microsoft and security, head-to-head competitors, for example, with a CrowdStrike or an Okta in identity. Whereas, it seems like at least for now, AWS is a more friendly place for the ecosystem. At the same time, you do a lot of business in Microsoft. >> Yeah. And I think that a lot of companies have always feared that Amazon would just throw, you know, bodies at it. And I think that people have come to the realization that a two pizza team, as Amazon would call it, is eight people. I think that's, you know, two slices per person. I'm a little bit fat, so I don't know if that's enough. But, you start to look at it and go, okay, if they're going to start out with eight engineers, if I'm a startup and they're part of my ecosystem, do I really fear them or should I really embrace them and try to partner closer with them? And I think the smart people and the smart companies are partnering with them because they're realizing, Amazon, unless they can see it to, you know, a hundred million, $500 million market, they're not going to throw eight to 16 people at a problem. I think when, you know, you could say, you could look at the elastic with OpenSearch and what they did there. And the licensing terms and the battle they went through. But they knew that Elastic had a huge market. Also, you had a number of ecosystem companies building on top of now OpenSearch, that are now domain on top of Amazon as well. So, I think Amazon's being pretty strategic in how they're doing it. I think some of the-- It'll be interesting. I think this year is a payout year for the cuts that they're making to some of the services internally to kind of, you know, how do we take the fat off some of those services that-- You know, you look at Alexa. I don't know how much revenue Alexa really generates for them. But it's a means to an end for a number of different other services and partners. >> What do you make of this ChatGPT? I mean, Microsoft obviously is playing that card. You want to, you want ChatGPT in the Cloud, come to Azure. Seems like AWS has to respond. And we know Google is, you know, sharpening its knives to come up with its response. >> Yeah, I mean Google just went and talked about Bard for the first time this week and they're in private preview or I guess they call it beta, but. Right at the moment to select, select AI users, which I have no idea what that means. But that's a very interesting way that they're marketing it out there. But, I think that Amazon will have to respond. I think they'll be more measured than say, what Google's doing with Bard and just throwing it out there to, hey, we're going into beta now. I think they'll look at it and see where do we go and how do we actually integrate this in? Because they do have a lot of components of AI and ML underneath the hood that other services use. And I think that, you know, they've learned from that. And I think that they've already done a good job. Especially for media and entertainment when you start to look at some of the ways that they use it for helping do graphics and helping to do drones. I think part of their buy of iRobot was the fact that iRobot was a big user of RoboMaker, which is using different models to train those robots to go around objects and things like that, so. >> Quick touch on Kubernetes, the whole DevOps World we just covered. The Cloud Native Foundation Security, CNCF. The security conference up in Seattle last week. First time they spun that out kind of like reinforced, you know, AWS spins out, reinforced from reinvent. Amsterdam's coming up soon, the CubeCon. What should we expect? What's hot in Cubeland? >> Yeah, I think, you know, Kubes, you're going to be looking at how OpenShift keeps growing and I think to that respect you get to see the momentum with people like Red Hat. You see others coming up and realizing how OpenShift has gone to market as being, like you were saying, partnering with those Clouds and really making it simple. I think the simplicity and the manageability of Kubernetes is going to be at the forefront. I think a lot of the investment is still going into, how do I bring observability and DevOps and AIOps and MLOps all together. And I think that's going to be a big place where people are going to be looking to see what comes out of CubeCon in Amsterdam. I think it's that manageability ease of use. >> Well Rob, I look forward to working with you on behalf of the whole Cube team. We're going to do more of these and go out to some shows extract the signal from the noise. Really appreciate you coming into our studio. >> Well, thank you for having me on. Really appreciate it. >> You're really welcome. All right, keep it right there, or thanks for watching. This is Dave Vellante for the Cube. And we'll see you next time. (light music)

(techno intro music) >> Hey everyone, good afternoon from sin city. This is Lisa Martin with Dave Vellante. We are in full swing of theCUBE's four days of coverage of AWS re:invent 2022. North of 50,000 people are here. We're nearing hundreds of thousands online. Dave, this has been, this is a great event. We've had great conversations. We're going to be having more conversations. One of the things we love talking about on theCUBE is AWS and its ecosystem of partners, and we are going to do just that right now. Brian Henderson joins us, Director of Marketing at Dell Technologies. Marc Trimuschat, Director of Worldwide Storage Specialists at AWS is also here. Guys, it's great to have you. >> Great to be here. >> Great to be here, yeah. Feeling the energy of the show. >> Isn't it great? >> Mark: I know, amazing. >> It's amazing. It started out high and it has not dropped since Monday night. Brian, talk a little bit about Dell, what you're doing with customers on their Cloud journeys. Every customer, every industry is on one at different points in their journey, but what's Dell helping out with there? >> What we're here to talk about is the progression that we've seen, right, Cloud has changed a lot over the years and Dell has really put out a strategy to help people with their Cloud journey, kind of wherever they are. So a lot of people have moved full shift. A lot of people see that as another location, and what we're showing at the booth is the idea of taking these enterprise capabilities that people know and trust from Dell, courting them to the Cloud. In some cases not courting, but just delivering that software in the Cloud, as well as taking some of the Kubernetes integrations, EKS Anywhere, bringing that on-prem. So we've got some storage, data protection, and our Kubernetes integration to talk about at the show. >> Awesome, Mark, talk about the role from Amazon's point of view that third party vendors like Dell Technologies plays in AWS's expanding vision of Cloud. >> Great, well, we're really excited to be partnering with Dell. What we see that historically is, you know, AWS is focused on builders, people, and really the developer community who are building those components themselves, putting together really resilient infrastructure and applications. What we're seeing today is a shift also to the type of customers that we're seeing, more traditional enterprise customers, who are demanding really performance, the scalability, also the resiliency of what they had on-premises, and they want that on the Cloud as well. So with Dell, and we've got some great solutions that we're partnering on, including Dell PowerFlex that provides that linear scalability and some of the high performance capabilities that customers are demanding. And also, another big trend that we're seeing is customers being affected by things like unfortunately malware events, right, and data protection. So Dell provides some great solutions in both those areas that allow enterprise customers to really experience that mission critical capability and resiliency that they have on-premises in the Cloud. >> You know, Brian, we've been at this a long time. >> Brian: Oh yeah, great to see you again. >> And I've been hearing my whole career that storage is going to get commoditized. And I guess if you're talking about spinning discs or flash drives, it's probably true, but as Mark was just saying if you want resilient storage and things that are recoverable, that don't go down all the time, they're not commodities. >> Brian: Yeah. >> It's real engineering. And you built the stack up, so talk about how that connection, what value you bring to the Cloud and your customers. >> Yeah, so what we see is people are always looking out for enterprise grade capabilities. So there's going to be a set of offerings, and AWS has a fantastic foundation for building on top of with the marketplace. So what we're able to do is really bring, in some cases, decades worth of investment in software engineering and put these advanced capabilities, whether it be PowerFlex with its linear scale. We'll have a file offering very soon. These products have been built from the ground up to do a very unique purpose. Giving that to people in the Cloud is just another location for us, AWS being the market leader. We're the market leader in storage. So us working together for the benefit of customers is really where it's at. >> Can you double click on that, Brian, what Dell and AWS? Give us all those juicy details. >> Sure, sure, sure, so what we've done right before this show is we put a product called PowerFlex, if you go back to 2018 scale IO, and you're taking this really linear scaling software defined architecture, and you're putting that in the Cloud. What that allows you to do is get that really advanced linear scale performance. You can even span clusters across AWS regions, as well as zones. So it's a really unique capability that allows us to be able to check in and do that. And in the data protection space, it's a whole separate category. We've been at this actually quite a while. We've got about 14 exo bytes of data that's already being protected on the AWS Cloud. So we've been at that for quite a while. And the two levels are really, do you want to back that up? Do you want to take a traditional back up application, maybe it's a lift and shift, and I want to back it up the way I used to, and you can do that in the Cloud now. Or we're seeing cyber resiliency come up a lot more, and we were just talking right before, it's a question of when, not if, and so we have to give our customers the option to not only detect that failure event early, but also to separate that copy with a logical air gap. >> The cyber resiliency is a topic we are talking more and more about. It's absolutely critical. We've seen the threat landscape change dramatically in the last couple of years. To your point, Brian, it's no longer, when we think of ransomware, it's no longer are we going to get hit? It's when, it's how often. What's the damage going to be? I think I saw a stat recently that there's one ransomware attack every 11 seconds. The average cost of reaches is in the millions, so what you're doing together on cyber resiliency for businesses in any industry is table stakes. >> Yeah, we just saw a survey that, it was done earlier this year survey, 66% unfortunately of corporations have experienced a malware attack. And that's an 80% increase from last year. >> Lisa: Wow. >> So again, I think that's an opportunity. It's a threat, but an opportunity, and so the partnership with Dell really helps bridge that and helps our customers, our mutual customers, recover from those incidents. >> A lot of people might say, this is interesting. A storage guy from Amazon, a storage guy from Dell, two leaders. And one might think, why didn't they just throw in a dash three, right, but you guys are both customer driven, customer obsessed. In the field, what are customers saying to you in terms of how they want you to work together? >> Well I think there's a place for everything. When you say throw in to S3, so S3 today, one of the big trends when you're looking here is just the amount of data, you know, we hear that rhetoric, you know, we've been in storage for many years, and the data has all increased up and to the right. But, you know, AWSI, S3 today, we have over 280 trillion objects in our, driving a hundred million transactions per second right now, so that's scale. So there's always a place for those really, we have hundreds of thousands of customers running their data links, so that's always going to be that really, you know, highly reliable, highly durable, high available solution for data links. But customers, there's a lot of different applications out there. So where customers are asking are those enterpise. So we have EBS, for example, which is our great, you know, scalable block search, elastic block store. We introduced some new volume types, like GP2, GP2, and IO2VX, which will have that performance. But there's still single availability zone. So what customers have done historically is they maybe the application layer, they put an application layer replication or resiliency across, but customers on-prem, they've relied on storage layers to do that work for them. So, with PowerFlex, that'll stand either using instant storage or EBS, building on that really strong foundation, but provide that additional layer to make it easy for customers to get that resiliency and that scalability that Brian talked about. >> Yep, yep. >> Anything you can add to that? >> Yeah, I mean to your question, how do we work together is really, it's all customer driven. So we see customers that are shifting workloads in the Cloud for the first time. And it might make sense to take an object, like PowerFlex or another storage technology, maybe you want to compress it a little bit before you send it to the Cloud. Maybe you don't want to lift and shift everything. So we have a team of people that works very closely with AWS to be able to determine how are you going to shift that workload out there? Does this make the right sense for you? So it's a very collaborative relationship. And it's all very customer driven because our customers are saying, I've got assets in the public Cloud, and I want them to be managed in a similar fashion to how I'm doing that on-prem. >> So customer obsession is clearly on both sides there. We know that. >> It's where it starts. >> Exactly, exactly. Going back to PowerFlex for a second, Brian, and I'd love to get an example of a joint customer that really is showing the value of what Dell and AWS are doing together. The question for you on PowerFlex, talk about the value that it offers to the public Cloud. And why should customers start there if they are early in this journey? >> All right, yeah, so the two angles are basically, are you coming from PowerFlex or you're coming from Cloud. If you're Cloud native, the advantage would be things like a really, really advanced block file system that has been built from the ground up to be software defined and pretty much Cloud native. What you're getting is that really linear scale up to about 1,000 nodes. You can span that across regions, across availability zones, so it's highly resilient. So if there's a node failure in one site, you're going to rebuild really fast, depending on the size of that cluster. So it's a very advanced architecture that's been built to run, you know, we didn't have to change a single line of code to run this product in the Cloud because it was Cloud native by default, so. >> Well that's the thing. We also see, and you've seen that with some of the other solutions, but customers really want that. Enterprise customers are, they want us to make sure those mission critical applications are working and stay up. So they also want to use the same environment. So we were talking before, we also see use cases where maybe they're using PowerFlex on-premises today and they want to be able to replicate that to PowerFlex that's in the Cloud. So we're seeing those, and the familiarity with that infrastructure really is that easy path, if you will, for those more conservative mission critical customers. >> We've learned a lot over the years from AWS's entry into the marketplace. Two recent teams working backwards. We talk about customer obsession. And also the Cloud experience. It brings me to APEX. >> Oh yeah. >> Dave: How does APEX fit in here? >> Yeah, so APEX is the categorization for all the things that we're doing around a modern Cloud experience for Dell customers. So we're taking them also on a journey, kind of as a service model. There's a do-it-yourself model. And anything that we do that touches Cloud is now being kind of put under that APEX moniker. So everything that we're doing around Project Alpine, enterprise software capabilities in the Cloud. Do you want someone else to manage it for you? Do you want it in a polo? That might be the right fit for you. It's all under that APEX umbrella and journey. So we're kind of still just getting started there, but we're seeing a lot of great traction. People want to pay as they go, you know, it's a very popular model that AWS has pretty much set the foundation for. So pay as you go, utility based pricing, this is all things our customers have been asking for. >> Yeah, so APEX, you basically set a baseline. You can dial it up, dial it down, very much pay by the drink. >> Absolutely. >> And, you know, like you said, it's early days. >> Brian: Yeah. >> But that's, again, AWS has influenced the business in a lot of different ways. >> Again, with the Dell, you know, the trust customers that Dell has built over the years and having those customers come in. We obviously are getting, again, it's an accelerated option for financial services to healthcare and all these customers that have relied on Dell for years, moving to the Cloud, having that trusted name and also that infrastructure that's similar and familiar to them. And then the resilience of the foundation that we have at AWS, I think it works really well together for those customers. >> I think it underscores to the majority of both AWS and in a lot of ways Dell, right. In the early days of Cloud, it was like uh oh, and now it's like oh, actually big market. Customers are demanding this. There's new value that we can create working together. Let's do it. >> Yeah, I mean, it didn't take us that long to get to it, but I'd say we had little fits and starts over the years, and now we've recognized like, this is where the future is. It's going to be Cloud, it's going to be on-prem, it's going to be Edge, it's going to be everything. It's going to be an and world. And so just doing the right thing for customers I think is exactly where we landed. It's a great partnership. >> Do you have a favorite customer story that you think really shines the light on the value of the Dell AWS partnership in terms of the business impact they're making? >> We have several large customers that I can't always like drop the names, but one of them is a very large video game production company. And we do a lot of work together where they're rendering maybe in house, they're sending to a shared location. They're copying data over to S3. They're able to let all their editors access that. They bring it back when it's compressed down a little bit and deliver that. We're also doing a lot of work with, I think I can say this, Amazon Thursday night football games. So what they've done there, it's a partner of ours working with AWS. All the details inside of that roaming truck that they drive around, there's a lot of Dell gear within there, and then everything connects back to AWS for that exact same kind of model. We need to get to the editors on a nightly basis. They're also streaming directly form that truck while they're enabling the editors to access a shared copy of it, so it's really powerful stuff. >> Thursday night prime is pretty cool. You know, some people are complaining cause I can't just switch channels during the commercials. It's like, first of all, you can. Second of all, the stats are unbelievable, right. You can just do your own replay when you want to. There's some cool innovations there. >> Oh yeah, absolutely. >> Very cool innovations. I've got one more question for each of you before we wrap. Marc, a question for you, we're making a fun Instagram reel. So think about a sizzle reel of if you were to summarize the show so far, what is AWS's message to its massive audience this year? >> Well, that's a big question. Because we have such a wide, as we mentioned, such a wide ranging audience. I really see a couple key trends that we're trying to address. One is, again don't forget, I'm a storage guy, so it's going to come from an angle from data, right. So, I think it's just this volume of data and that customers are bringing into the Cloud, either moving in from enterprises today or organically, just growing. You know, a couple years ago, megabytes were a lot, and now, you know, we're talking about petabytes every day. Soon it's going to be exo bytes are going to become the norm. So the big, I'd say, point one is the trend that I see is just the volume of data. And so what we're doing to address that is obviously we talked a little bit about S3 and being able to manage volumes of data, but also things like DataZone that we introduced because customers are looking to make sure that the right governance and controls to be able to access that data. So I think that's one big thing that I see the theme for the show today. The second thing is around, as I said, really these enterprise customers really wanted to move in these mission critical applications into the Cloud, and having that infrastructure to be able to support that easily from what they're doing today and move in quickly. The third area is around data protection, making sure the data protection and malware recovery, that's the theme that we see is really unfortunately that's today. But being able to recover quickly, both having native services and native offerings just built in resiliency into the core platforms, like S3 with object application, et cetera. And also partnering with Dell with cyber recovery and some of the solutions with Dell. >> Excellent, and Brian, last question for you. A bumper sticker that succinctly and powerfully describes why Dell and AWS are such awesome partners for customer issues. >> Best of both worlds, right? >> Lisa: Mic drop. >> Mic drop, done. >> That's awesome. You said that a lot more succinctly. (people laughing) >> Enterprise in Cloud, Cloud comin' to enterprise. >> Yeah, leader meets leader, right? >> Yeah, right. >> Love it, leader meets leader. Guys, it's been a pleasure having you on theCUBE. We appreciate hearing the latest from AWS and Dell from a storage perspective and from a Cloud perspective and how you're helping customers manage the explosion of data that's not going to slow down. We really appreciate you coming by the set. >> Thank you. >> Great, thanks so much, appreciate it. >> My pleasure. For our guests and Dave Vellante, I'm Lisa Martin, you're watching theCUBE, the leader in live enterprise and emerging tech coverage. (techno music)

>>Good afternoon and welcome back to the Classiest Show in Technology. This is the Cube we are at AWS Reinvent 2022 in Fabulous Sin City. That's why I've got my sequence on. We love a little Vegas, don't we? I'm joined by John Farer, another, another Vegas >>Fan. I don't have my sequence, I left it in my room. We're >>Gonna have to figure out how to get us 20 as soon as possible. What's been your biggest shock for you at the show so far? >>Well, I think the data story and security is so awesome. I love how that's front and center. If you look at the minutes of the keynote of Adamski, the CEO on day one, it's all bulked into data and security. All worked hand in hand. That's on top of already the innovation of their infrastructure. So I think you're gonna see a lot of interplay going on in this next segment. It's gonna tell a lot of that innovation story that's coming next. It's pretty awesome. >>It is pretty awesome, and I'm super excited. It's not only what we do here on the Cube, it's also in my show notes. We are gonna be geeking out for the next segment. Please welcome Paul and Puja. Wonderful to have you both here. Paul from Amazon, s3, glacier, and Pujan, CEO of kuo. I wanna turn to you Pujan, to start us off, just in case the audience isn't familiar, give us the Kuo pitch. >>Yeah, so basically Kuo is a, a backup as a service offering, right? Built in AWS four aws, right? And effectively going after, you know, any service that a customer uses on top of aws, right? And so a lot of the data sitting on s3, right? So that's been like our, our big use case going and basically building backup and air gap protection for, for s3. But we basically go to every other service, e c two, ebs, dynamo, you know, you name it, right? So basically do the whole thing >>And the relationship with aws. Can you guys share, I mean, you got you here together. You guys are a great partnership. Born in the cloud, operation in the cloud. Absolutely. I think talk about the partnership with aws. >>Absolutely. I think the last five years of building on AWS has been phenomenal, right? And I love the platform. It's, it's a very pure platform for us. You know, the APIs and, and the access you get and access you get to the service teams like Paul sitting here and the other teams you have gotten access to, I think has been phenomenal. But we also have, I would say, pushed the envelope in terms of how innovative we have been and how aggressive we have been in utilizing all the innovation that AWS has built in over the last few years. But it would not have happened without the fantastic partnership with the service teams. >>Paul, talk about the, AM the S3 part of this. What's the story there? >>Well, it's been great working with the CUO team over the course of the last few years. We were just upstairs diving deep into the, to the features that they're taking advantage of. They really push us hard on behalf of customers, and it's been a, it's just been a great relationship over the last years. >>That's awesome. And the ecosystem at such a, we're gonna hear tomorrow, the keynote on the, from Aruba who's gonna tend over the ecosystem. You guys are working together. There's a lot of strategic partnerships, so much collaboration between you guys that makes it very, this is the next gen cloud of cloud environment we're seeing. And you heard the, the economies around the corner. It's still gonna be challenging, but still there's more growth in the cloud. This is not stopping. This is impacts the customers. What are the customers saying to you guys when you work backwards from their needs? They want it faster, easier, cheaper. They want it more integrated. What are some of the things, all those you guys hearing from customers? >>So for us, you know, if you think about it, like, you know, as people are moving to the cloud, especially like take a use case like s3, right? So much of critical data sitting on top of S3 today. And so what folks have realized that as they're, you know, putting all of those, you know, what, over two 50 trillion objects, you know, sitting on s3, a lot of them need backup and data protection because there could be accidental deletions, there could be software bugs, there could be a ransomware type event due to which you need a second copy of the data that is outside of your security domain, right? But again, that needs to get be done at the, at the right price point, right? And that's where like a technology like Columbia comes in because since we've been built on the cloud, we've optimized it correctly. So especially for folks who are very cost conscious, given the macroeconomic conditions, we are heading into a technology that's built correctly so that, you know, you get the right architecture and the right solution at the right price point and the scale, right? Talking about trillions of objects, billions of objects within a single customer, within a single bucket sometimes. And that's where Columbia comes in. Cause we basically do that at scale without, again, impacting the, the customer's wallet more than it needs to. >>The porridge has to be the right temperature and the right size bowl. With the right spoon. You've got a lot of complexity when it comes to solving those customer challenges. You have a couple customer story examples you're allowed to share with us. Correct? Paul, do you want to kick one off? Go ahead. Oh, puja. All right. >>No, absolutely. I think there's a ton of them. I, I'll talk about, you know, want to begin with like Cox Automotive, right? A phenomenal customer that we, all of us have worked together with them. And again, looking for a solution to backup S3 to essentially go air gap protection outside of their account, right? They looked at doing it themselves, right? They thought they'll go and basically do it themselves. And then they fortunately bumped into Columbia, they looked at our architecture, looked at what it would really go and take to build it. And guess what, sitting in 2022, getting 23 right now, nobody wants to go and build this themselves. They actually want a turnkey solution that just does it, right? And so, again, we are a phenomenal joint customer of ours doing this at a pretty massive scale, right? And there are many more like that. There's Warner Brothers that are essentially going into the cloud from on premises, right? And they're going really fast accelerating the usage on aws again, looking at, you know, backup and data protection and using clum because of our extreme simplicity that we provide. >>Yeah, I think it's, you've got a, a lot of different people solving different problems that you're working with all the time. Millions of customers. Well, how do you prioritize? >>Well, for us, it really all comes down to fundamentals, right? So Amazon, s3 s unique distributed architecture delivers industry leading durability, availability, performance and security at virtually unlimited scale, right? And it's really been delivering on the fundamentals that has earned the trust of so many customers of all sizes and industries over the course of over 16 years. Now, in terms of how we prioritize on behalf of those customers, we always say that 90% of our roadmap comes directly from what customers are telling us is important. And a large number of our customers now are using S3 through lumino, which is why the relationship is so important. We're here talking about customer use cases here at the show, and we do that regularly throughout the year as well. And that's, that's how we land on a road. >>And what are the, what are the top stories from customers? What, what are they telling you? What's the number one top three things you're hearing? >>I tell you, like, again, it just comes down to the fundamentals, right? Of security, availability, durability and performance at virtually unlimited scale. Like that is the first customer first discussions that we have with customers talking about durable storage, for >>Sure. What I find interesting in, you mentioned scale, right? That comes up a lot scale with data. Yeah. That we heard data. The big theme here, security, what's in my S3 bucket? Can you find out what's in there? Is it backed up properly? How do I get it back? Where's the ransomware? Why not just target the ransomware? So how do you navigate the, the security challenges, the, the need to store all that scale data? What's the secret sauce? >>Yeah, so I think the, the big thing is we'll start with the, you know, how we have architected the product, right? If you think about it, this, you're dealing with a lot of scale, right? You get to a hundred million, a billion and billions very fast on S3 few, especially on a cloud native application. So it starts with the visibility, right? It's basically about, like we have things where you do, where you create a subset of your buckets called protection groups that you can essentially, you know, do it based on prefixes. So now you can essentially figure out what prefix you want to back up and what you don't want to back up. Maybe there's log data that you don't care about, so you don't back that up, right? And it all starts with that visibility that you give. And the prefix level data protection then comes the scale, which is where I was telling you, right? We have basically built an orchestration engine, right? It's like we call the ES for Lambdas, right? So we have a internal orchestration engine and essentially what what we have done is we have our own language internally that spawns off these lambdas, right? And they go after these S3 partitions do the right things and then you basically reel them back. So things like that that we do that are not possible if you're not built on the >>Clock. Well also, I mean, just mind blowing and go back 10 years. Yeah. I mean you got Lambda. What you're talking about here is the gift of the cloud innovation. Yeah. So the benefit of S3 is now accelerated. This is the story this year. Yeah. I mean they're highlighting it at scale, not just in the data, but like what we knew when Lambda came out and what S3 could do. But now mainstream solutions are coming in. Does that change your backup plans? Because we're gonna see a lot more end to end, lot more solutions. We heard that on the keynote. Some are saying it's more complexity. Of course it might, but you can abstract another way with the cloud that's the best part of the cloud. So these abstraction leads. So what's your view on that? But I wanna get your thoughts because you guys are perfectly positioned for this scale, but there's more coming. Yes. Yes. Exactly. What, how are you looking at that? >>So again, I think the, you know, obviously the, the S3 teams and every team in AWS is basically pushing the envelope in terms of innovation. But the key for a partner like us is to go and take that innovation. A lot of complex architectures behind the scene. But what you deliver to the customer is simple. I'll give you one more example. One of the things we launched that, you know, Paul and others are very excited about, is this ability to do instant access on the backup, right? So you could have billions of objects that you backed up. Maybe you need just 10,000 of them for a DR test. And we can basically create like an instant virtual bucket on top of that backup that you can instantly restore >>Spinning up a sandbox of temporary data to go check it >>Out. Exactly. Offer an inte application. >>Think we're geeking out right now. >>Yeah, I know. Brought that part of the segment, John. Don't worry, we're safely there. But, >>But that's the thing, right? That all that is possible because of all the, the scale and innovation and all the APIs and everything that, you know, Paul and the team gives us that we go and build on top of >>Paul, geek out on with us on this. We >>Are super excited for instant restore >>For store. I mean, automation programmability. >>It is, I mean it's the logical next step for backup in the cloud. Exactly. Yeah. But it's a super hard engineering problem to go solve for customers. I mean, the RTO benefits alone are super compelling, but then there's a cost element as well of not having to bring back all that stuff for a test restore, for example. And so it's, it's been really great to, to work with the team on that. We have some ideas on how we may help solve it from our side, and we're looking forward to collaborating on it. >>This is a great illustration of what I was writing about this week around the classic cloud, which is great. And as Adam said, and used like to use the word and, and you got this new functionality we're seeing emerge from the growth. Yes. From the companies that are built on Amazon web services that are growing. You're a partner, they have a lot of other partners and people are taking over restaurant here off action. I mean, there's real growth and new functionality on top of aws. You guys are no different. What's, are you prepared for that? Are you ready to go? >>Yeah, no, absolutely. And I think if you think about, if you think about it, right, I think it's also about doing this without impacting the primary application. Like if the customer is running a primary application at scale on s3, a backup application like ours can't come in and really mess with that. So I think being able to do things where, and this is where you solve really hard computer science problems, right? Where you're bottling yourself. If you are essentially seeing any kind of, you know, interfering with the primary, you're going to cut yourself down. You're gonna go after a different partition. So there are a lot of things you need to do behind the scenes, which is again, all the complexity, all of that, but deliver the, to the customer a very, very simple thing. >>You know, Paul, I wanna get your thoughts and I want you to chime in. Yeah. In 2014, I interviewed Steven Schmidt, my first interview with the, he was the CISO then, and now he's a CSO and, and former ciso, he's back at that time, the word was the cloud's not secure. Now we're talking about security. Just in the complexity of how you're partitioning and managing your sub portions, how you explained it, it's harder for the attackers. The cloud in its in its architecture has become a more secure environment. Yeah. Well, and getting more secure as you have laying out this, this is a new dynamic. This is good. Can you explain the, >>I mean, I, I can just tell you that at AWS security is job zero and that it will always be our number one priority, right? We have a, an infrastructure with under AWS that is vetted and approved to run even top secret workloads, which benefits all customers in all regions. >>And your, your security posture is embedded on top of that. And you got your own stuff. >>Yeah. And if you think of it as a shared responsibility model, so security of the cloud is the responsibility of the cloud provider, but then security of the data on top of it. Like you, you go and delete stuff, your software goes and does something that resiliency, the integrity of the data is your responsibility as a customer. And that's where, you know, we come in. Who >>Shared responsibility has been such a hot topic all week. Yeah. >>I gotta ask him one more question. Cause this is fascinating. And we are talking about on the cube all day today after we saw the announcement and Adam's comment on the cube, Adams LE's comment on the keynote. I mean, he said, if you're gonna tighten your belt, meaning economic cost recovery, re right sizing. If you want to tighten your belt, come to the cloud. So I have to ask you guys, Puja, if you can comment, that'd be great. There's a lot of other competitors out there that aren't born on aws. What is the customer gonna do when they tighten the build? What does that mean? They're gonna go to, to the individual contracts. They're gonna work in the marketplace. I mean this, there's a new dynamic in town. It's called AWS 2022. They weren't really around much in the recession of 2008. They were just starting to grow. Now they're an economic force. People like yourselves have embedded in there. There's a lot of competition. What's gonna happen? >>I think people are gonna just go to a place like, you know, AWS marketplace. You're going to essentially look for solutions and essentially like, and, and the right solutions built in are going to be self-service like aws. It's a very self-service thing. A hundred percent. So you go and do self-service, you figure out what's working, what's not working. Also, the model has to be consumption oriented. No longer can you expect the customer to go and pay a bunch of money for shelfware, right? It's like, like how we charge how AWS charges, which is you pay for what you consume. That and all has to be front and center, >>Right? I think that's a really, I think that's a really important >>Point. It's time >>And I think it's time. So we have a new challenge on the cube. We give you 30 seconds roughly to give us your extraordinarily hot take your shining thought leadership moment and, and highlight what you think is the most important takeaway from the show. The biggest soundbite, the juiciest announcement. Paul, I'll >>Start with an Instagram. Real basically. Yeah. Okay. >>Yeah. Hi. Go. I would just say from an S3 perspective, over the course of the last several years, we've really seen workloads shift from just backup and recovery and static images on websites to data lake analytics applications. And you continue to see that here. And I can tell you that some of these scaled applications are running at enormous mind blowing scale, right? And so, so every year we come here, we talk to customers, and it's just every year it sort of blows me away. And I've been in the storage industry for a long time and it's just is, it blows me away. Just the scale at customers are running in >>And >>Blowing scale. And when it comes to backup, let me just say that it's easy to back up and recover a single object, but doing an easy thing, a billion or 10 billion times over, that's actually quite hard. >>And just to, just to bold that a little bit, just pull out my highlighter. S3 now has over 280 trillion objects. That's a lot. >>That's a lot of objects. >>Yeah. You are not, you are not kidding. When you talk about scale, I mean, this is the most scalable. >>That's not solution's not there. Yeah. That, that's right. And we wake up every, we have a culture of durability and we wake up every single day to raise the bar on the fundamentals and make sure that every single one of those objects is protected and safe. >>Okay. You, I, >>I can't imagine worrying about two, two 80 trillion different things. >>Let's go. You're Instagram real >>For me again, you know, between S3 and us, we are two players out there that are really, you know, processing the data at the end of the day, right? And so I'm very excited about, you know, what we are going to do more and more with the instant restore capability where we can integrate third party services on top of it that can do more things with the data that is not, not passively sitting, but now becomes active data that you can analyze and do things with. So that's something where we take this to the next level is something that I'm super excited about. >>There's a lot to be excited about and, and we're excited to have you. We're excited to hear what happens next. Excited to see more collaboration like this. Paul Pon, thank you so much for joining us here on the show. Thank all of you from for tuning into our continuous wall to wall super thrilling live coverage of AWS reinvent here in fabulous Las Vegas, Nevada, with John Furrier. I'm Savannah Peterson. We're the cube, the leading source for high tech coverage.

(upbeat music) >> Welcome back to Vegas. Lisa Martin and Dave Vellante here with theCUBE live on the Venetian Expo Hall Floor, talking all things AWS re:Invent 2022. This is the first full day of coverage. It is jam-packed here. People are back. They are ready to hear all the new innovations from AWS. Dave, how does it feel to be back yet again in Vegas? >> Yeah, Vegas. I think it's my 10th time in Vegas this year. So, whatever. >> This year alone. You must have a favorite steak restaurant then. >> There are several. The restaurants in Vegas are actually really good. >> You know? >> They are good. >> They used to be terrible. But I'll tell you. My favorite? The place that closed. >> Oh! >> Yeah, closed. In between where we are in the Wynn and the Venetian. Anyway. >> Was it CUT? >> No, I forget what the name was. >> Something else, okay. >> It was like a Greek sort of steak place. Anyway. >> Now, I'm hungry. >> We were at Pure Accelerate a couple years ago. >> Yes, we were. >> When they announced Cloud Block Store. >> That's right. >> Pure was the first- >> In Austin. >> To do that. >> Yup. >> And then they made the acquisition of Portworx which was pretty prescient given that containers have been going through the roof. >> Yeah. >> So I'm sort of excited to have these guys on and talk about that. >> We're going to unpack all of this. We've got one of our alumni back with us, Venkat Ramakrishna, VP of Product, Portworx by Pure Storage. And Dan Kogan joins us for the first time, VP of Product Management and Product Marketing, FlashArray at Pure Storage. Guys, welcome to the program. >> Thank you. >> Hey, guys. >> Dan: Thanks for having us. >> Do you have a favorite steak restaurant in Vegas? Dave said there's a lot of good choices. >> There's a lot of good steak restaurants here. >> I like SDK. >> Yeah, that's a good one. >> That's the good one. >> That's a good one. >> Which one? >> SDK. >> SDK. >> Where's that? >> It's, I think, in Cosmopolitan. >> Ooh. >> Yeah. >> Oh, yeah, yeah, yeah. >> It's pretty good, yeah. >> There's one of the Western too that's pretty. >> I'm an Herbs and Rye guy. Have you ever been there? >> No. >> No. >> Herbs and Rye is off strip, but it's fantastic. It's kind of like a locals joint. >> I have to dig through all of this great stuff today and then check that out. Talk to me. This is our first day, obviously. First main day. I want to get both of your perspectives. Dan, we'll start with you since you're closest to me. How are you finding this year's event so far? Obviously, tons of people. >> Busy. >> Busy, yeah. >> Yeah, it is. It is old times. Bigger, right? Last re:Invent I was at was 2019 right before everything shut down and it's probably half the size of this which is a different trend than I feel like most other tech conferences have gone where they've come back, but a little bit smaller. re:Invent seems to be the IT show. >> It really does. Venkat, are you finding the same? In terms of what you're experiencing so far on day one of the events? >> Yeah, I mean... There's tremendous excitement. Overall, I think it's good to be back. Very good crowd, great turnout, lot of excitement around some of the new offerings we've announced. The booth traffic has been pretty good. And just the quality of the conversations, the customer meetings, have been really good. There's very interesting use cases shaping up and customers really looking to solve real large scale problems. Yeah, it's been a phenomenal first day. >> Venkat, talk a little bit about, and then we'll get to you Dan as well, the relationship that Portworx by Pure Storage has with AWS. Maybe some joint customers. >> Yeah, so we... Definitely, we have been a partner of AWS for quite some time, right? Earlier this year, we signed what is called a strategic investment letter with AWS where we kind of put some joint effort together like to better integrate our products. Plus, kind of get in front of our customers more together and educate them on how going to how they can deploy and build vision critical apps on EKS and EKS anywhere and Outpost. So that partnership has grown a lot over the last year. We have a lot of significant mutual customer wins together both on the public cloud on EKS as well as on EKS anywhere, right? And there are some exciting use cases around Edge and Edge deployments and different levels of Edge as well with EKS anywhere. And there are pretty good wins on the Outpost as well. So that partnership I think is kind of like growing across not just... We started off with the one product line. Now our Portworx backup as a service is also available on EKS and along with the Portworx Data Services. So, it is also expanded across the product lanes as well. >> And then Dan, you want to elaborate a bit on AWS Plus Pure? >> Yeah, it's for kind of what we'll call the core Pure business or the traditional Pure business. As Dave mentioned, Cloud Block Store is kind of where things started and we're seeing that move and evolve from predominantly being a DR site and kind of story into now more and more production applications being lifted and shifted and running now natively in AWS honor storage software. And then we have a new product called Pure Fusion which is our storage as code automation product essentially. It takes you from moving and managing of individual arrays, now obfuscates a fleet level allows you to build a very cloud-like backend and consume storage as code. Very, very similar to how you do with AWS, with an EBS. That product is built in AWS. So it's a SaaS product built in AWS, really allowing you to turn your traditional Pure storage into an AWS-like experience. >> Lisa: Got it. >> What changed with Cloud Block Store? 'Cause if I recall, am I right that you basically did it on S3 originally? >> S3 is a big... It's a number of components. >> And you had a high performance EC2 instances. >> Dan: Yup, that's right. >> On top of lower cost object store. Is that still the case? >> That's still the architecture. Yeah, at least for AWS. It's a different architecture in Azure where we leverage their disc storage more. But in AWS were just based on essentially that backend. >> And then what's the experience when you go from, say, on-prem to AWS to sort of a cross cloud? >> Yeah, very, very simple. It's our replication technology built in. So our sync rep, our async rep, our active cluster technology is essentially allowing you to move the data really, really seamlessly there and then again back to Fusion, now being that kind of master control plan. You can have availability zones, running Cloud Block Store instances in AWS. You can be running your own availability zones in your data centers wherever those may happen to be, and that's kind of a unification layer across it all. >> It looks the same to the customer. >> To the customer, at the end of the day, it's... What the customer sees is the purity operating system. We have FlashArray proprietary hardware on premises. We have AWS's hardware that we run it on here. But to the customer, it's just the FlashArray. >> That's a data super cloud actually. Yeah, it's a data super cloud. >> I'd agree. >> It spans multiple clouds- >> Multiple clouds on premises. >> It extracts all the complexity of the underlying muck and the primitives and presents a common experience. >> Yeah, and it's the same APIs, same management console. >> Dave: Yeah, awesome. >> Everything's the same. >> See? It's real. It's a thing, On containers, I have a question. So we're in this environment, everybody wants to be more efficient, what's happening with containers? Is there... The intersection of containers and serverless, right? You think about all the things you have to do to run containers in VMs, configure everything, configure the memory, et cetera, and then serverless simplifies all that. I guess Knative in between or I guess Fargate. What are you seeing with customers between stateless apps, stateful apps, and how it all relates to containers? >> That's a great question, right? I think that one of the things that what we are seeing is that as people run more and more workloads in the cloud, right? There's this huge movement towards being the ability to bring these applications to run anywhere, right? Not just in one public cloud, but in the data centers and sometimes the Edge clouds. So there's a lot of portability requirements for the applications, right? I mean, yesterday morning I was having breakfast with a customer who is a big AWS customer but has to go into an on-prem air gap deployment for one of their large customers and is kind of re-platforming some other apps into containers in Kubernetes because it makes it so much easier for them to deploy. So there is no longer the debate of, is it stateless versus it stateful, it's pretty much all applications are moving to containers, right? And in that, you see people are building on Kubernetes and containers is because they wanted multicloud portability for their applications. Now the other big aspect is cost, right? You can significantly run... You know, like lower cost by running with Kubernetes and Portworx and by on the public cloud or on a private cloud, right? Because it lets you get more out of your infrastructure. You're not all provisioning your infrastructure. You are like just deploying the just-enough infrastructure for your application to run with Kubernetes and scale it dynamically as your application load scales. So, customers are better able to manage costs. >> Does serverless play in here though? Right? Because if I'm running serverless, I'm not paying for the compute the whole time. >> Yeah. >> Right? But then stateless and stateful come into play. >> Serverless has a place, but it is more for like quick event-driven decision. >> Dave: The stateless apps. >> You know, stuff that needs to happen. The serverless has a place, but majority of the applications have need compute and more compute to run because there's like a ton of processing you have to do, you're serving a whole bunch of users, you're serving up media, right? Those are not typically good serverless apps, right? The several less apps do definitely have a place. There's a whole bunch of minor code snippets or events you need to process every now and then to make some decisions. In that, yeah, you see serverless. But majority of the apps are still requiring a lot of compute and scaling the compute and scaling storage requirements at a time. >> So what Venkat was talking about is cost. That is probably our biggest tailwind from a cloud adoption standpoint. I think initially for on-premises vendors like Pure Storage or historically on-premises vendors, the move to the cloud was a concern, right? In that we're getting out the data center business, we're going all in on the cloud, what are you going to do? That's kind of why we got ahead of that with Cloud Block Store. But as customers have matured in their adoption of cloud and actually moved more applications, they're becoming much more aware of the costs. And so anywhere you can help them save money seems to drive adoption. So they see that on the Kubernetes side, on our side, just by adding in things that we do really well: Data reduction, thin provisioning, low cost snaps. Those kind of things, massive cost savings. And so it's actually brought a lot of customers who thought they weren't going to be using our storage moving forward back into the fold. >> Dave: Got it. >> So cost saving is great, huge business outcomes potentially for customers. But what are some of the barriers that you're helping customers to overcome on the storage side and also in terms of moving applications to Kubernetes? What are some of those barriers that you could help us? >> Yeah, I mean, I can answer it simply from a core FlashArray side, it's enabling migration of applications without having to refactor them entirely, right? That's Kubernetes side is when they think about changing their applications and building them, we'll call quote unquote more cloud native, but there are a lot of customers that can't or won't or just aren't doing that, but they want to run those applications in the cloud. So the movement is easier back to your data super cloud kind of comment, and then also eliminating this high cost associated with it. >> I'm kind of not a huge fan of the whole repatriation narrative. You know, you look at the numbers and it's like, "Yeah, there's something going on." But the one use case that looks like it's actually valid is, "I'm going to test in the cloud and I'm going to deploy on-prem." Now, I dunno if that's even called repatriation, but I'm looking to help the repatriation narrative because- >> Venkat: I think it's- >> But that's a real thing, right? >> Yeah, it's more than repatriation, right? It's more about the ability to run your app, right? It's not just even test, right? I mean, you're going to have different kinds of governance and compliance and regulatory requirements have to run your apps in different kinds of cloud environments, right? There are certain... Certain regions may not have all of the compliance and regulatory requirements implemented in that cloud provider, right? So when you run with Kubernetes and containers, I mean, you kind of do the transformation. So now you can take that app and run an infrastructure that allows you to deliver under those requirements as well, right? So that portability is the major driver than repatriation. >> And you would do that for latency reasons? >> For latency, yeah. >> Or data sovereign? >> Data sovereignty. >> Data sovereignty. >> Control. >> I mean, yeah. Availability of your application and data just in that region, right? >> Okay, so if the capability is not there in the cloud region, you come in and say, "Hey, we can do that on-prem or in a colo and get you what you need to comply to your EDX." >> Yeah, or potentially moves to a different cloud provider. It's just a lot more control that you're providing on customer at the end of the day. >> What's that move like? I mean, now you're moving data and everybody's going to complain about egress fees. >> Well, you shouldn't be... I think it's more of a one-time move. You're probably not going to be moving data between cloud providers regularly. But if for whatever reasons you decide that I'm going to stop running in X Cloud and I'm going to move to this cloud, what's the most seamless way to do? >> So a customer might say, "Okay, that's certification's not going to be available in this region or gov cloud or whatever for a year, I need this now." >> Yeah, or various commercial. Whatever it might be. >> "And I'm going to make the call now, one-way door, and I'm going to keep it on-prem." And then worry about it down the road. Okay, makes sense. >> Dan, I got to talk to you about the sustainability element there because it's increasingly becoming a priority for organizations in every industry where they need to work with companies that really have established sustainability programs. What are some of the factors that you talk with customers about as they have choice in all FlashArray between Pure and competitors where sustainability- >> Yeah, I mean we've leaned very heavily into that from a marketing standpoint recently because it has become so top of mind for so many customers. But at the end of the day, sustainability was built into the core of the Purity operating system in FlashArray back before it was FlashArray, right? In our early generation of products. The things that drive that sustainability of high density, high data reduction, small footprint, we needed to build that for Pure to exist as a company. And we are maybe kind of the last all-flash vendor standing that came ground up all-flash, not just the disc vendor that's refactored, right? And so that's sort of engineering from the ground up that's deeply, deeply into our software as a huge sustainability payout now. And we see that and that message is really, really resonating with customers. >> I haven't thought about that in a while. You actually are. I don't think there's any other... Nobody else made it through the knothole. And you guys hit escape velocity and then some. >> So we hit escape velocity and it hasn't slowed down, right? Earnings will be tomorrow, but the last many quarters have been pretty good. >> Yeah, we follow you pretty closely. I mean, there was one little thing in the pandemic and then boom! It's just kept cranking since, so. >> So at the end of the day though, right? We needed that level to be economically viable as a flash bender going against disc. And now that's really paying off in a sustainability equation as well because we consume so much less footprint, power cooling, all those factors. >> And there's been some headwinds with none pricing up until recently too that you've kind of blown right through. You know, you dealt with the supply issues and- >> Yeah, 'cause the overall... One, we've been, again, one of the few vendors that's been able to navigate supply really well. We've had no major delays in disruptions, but the TCO argument's real. Like at the end of the day, when you look at the cost of running on Pure, it's very, very compelling. >> Adam Selipsky made the statement, "If you're looking to tighten your belt, the cloud is the place to do it." Yeah, okay. It might be that, but... Maybe. >> Maybe, but you can... So again, we are seeing cloud customers that are traditional Pure data center customers that a few years ago said, "We're moving these applications into the cloud. You know, it's been great working with you. We love Pure. We'll have some on-prem footprint, but most of everything we're going to do is in the cloud." Those customers are coming back to us to keep running in the cloud. Because again, when you start to factor in things like thin provisioning, data reduction, those don't exist in the cloud. >> So, it's not repatriation. >> It's not repatriation. >> It's we want Pure in the cloud. >> Correct. We want your software. So that's why we built CBS, and we're seeing that come all the way through. >> There's another cost savings is on the... You know, with what we are doing with Kubernetes and containers and Portworx Data Services, right? So when we run Portworx Data Services, typically customers spend a lot of money in running the cloud managed services, right? Where there is obviously a sprawl of those, right? And then they end up spending a lot of item costs. So when we move that, like when they run their data, like when they move their databases to Portworx Data Services on Kubernetes, because of all of the other cost savings we deliver plus the licensing costs are a lot lower, we deliver 5X to 10X savings to our customers. >> Lisa: Significant. >> You know, significant savings on cloud as well. >> The operational things he's talking about, too. My Fusion engineering team is one of his largest customers from Portworx Data Services. Because we don't have DBAs on that team, it's just developers. But they need databases. They need to run those databases. We turn to PDS. >> This is why he pays my bills. >> And that's why you guys have to come back 'cause we're out of time, but I do have one final question for each of you. Same question. We'll start with you Dan, the Venkat we'll go to you. Billboard. Billboard or a bumper sticker. We'll say they're going to put a billboard on Castor Street in Mountain View near the headquarters about Pure, what does it say? >> The best container for containers. (Dave and Lisa laugh) >> Venkat, Portworx, what's your bumper sticker? >> Well, I would just have one big billboard that goes and says, "Got PX?" With the question mark, right? And let people start thinking about, "What is PX?" >> I love that. >> Dave: Got Portworx, beautiful. >> You've got a side career in marketing, I can tell. >> I think they moved him out of the engineering. >> Ah, I see. We really appreciate you joining us on the program this afternoon talking about Pure, Portworx, AWS. Really compelling stories about how you're helping customers just really make big decisions and save considerable costs. We appreciate your insights. >> Awesome. Great. Thanks for having us. >> Thanks, guys. >> Thank you. >> For our guests and for Dave Vellante, I'm Lisa Martin. You're watching theCUBE, the leader in live enterprise and emerging tech coverage. (upbeat music)

(upbeat music) >> Hey everyone. Welcome back to San Francisco, VMware Explorer 2022, Lisa Martin and Dave Nicholson here. We've been having some great conversations today. Lots of news coming out about VMware and its partner ecosystem. We're going to have another conversation about that next. Please welcome two guests to the program, Chance Bingen, technical marketing engineer at NetApp and Jason Massae, staff technical marketing architect, storage and vVols at VMware. Guys, welcome to the program. >> Thanks. >> Glad to be here. >> It's nice to be back in person. >> It is. It's very nice. Oh my gosh. >> And we're hearing there about 7,000 to 10,000 people here, when I was in the Keynote, this morning it was definitely standing room only. >> Yeah, yeah. You've definitely seen the numbers ticked up at the last minute. It was good to see that. It's good, I think a lot of people have really wanted to get back, get that one on one that face to face. There's nothing like being able to, you know, talk to, the experts, talk to the vendors, you know, see your comrades. I mean, that's the thing. I mean, we've seen people that I haven't seen for years, even on my own team, so really good to be back into it. >> It is and it was lots of news coming out this morning during the Keynote. My goodness. But Jason, talk to me, the NetApp and VMware folks had been in tight partnership for a long time. Talk to me about, get both of your perspective from a technical perspective about the depth of the partnership. >> Yeah, so actually NetApp was one of the original design partners for vVols. And with that, now with some of the stuff we're doing with more current stuff with virtual volumes is, NetApp is back and we've got some pretty neat stuff that we've been working on with vVols. And NetApp's got some pretty neat stuff that they've been working on to enable the customers with more features, more functionality with the virtual volume functionality. >> Yeah, absolutely. >> Give us a quick primer on what is a vVol? What is a virtual volume? How does it fit into the, into this stack of stuff that we do in IT? >> Yeah. So the easiest way to kind of think of what a vVol is or a virtual volume is you can think of it kind of like an RDM, those row device map, which is kind of a four letter word. We don't really like those, but the idea is that object, that virtual volume is native on the array and presented directly to the VM. But now what we do is we're presenting all of the storage array features up to vSphere and we're managing those storage features via policy based management. But instead of applying storage capabilities at a data store level, we're now applying them at a VM or an application level. So you can have one data store and multiple VMs, and every VM can have a different storage capability managed by a policy that the VI admin gets to manage now. So he doesn't have to go to the storage admin to say, I need a new line, or I need a new volume. He can just go in and create a policy or change a policy. And now that storage capability is applied to the VM or the application. >> Yeah. One thing I'd like to add to that is you can mentioned the word capabilities. >> So we look at the actual data protocols, whether they're file based or block based, you know, I-scuzzy, fiber channel, whatever the case might be. Those protocols have defined sets of capabilities and attributes and things they can expose. What vVols along with the VASA protocol brings to the table is the ability to expose things that are just impossible to expose via the data protocols themselves. So that the, actual nature of the array, what kind of array is it? What's it capable of doing? What is the nature of, you know, encryption? You know, is this going to be a secure, encrypted data store? Is it going to be something else? It just allows you to do so much more with the advanced capabilities that modern storage arrays have than you could ever do if you were just using the data protocols by themselves. >> Right? Yeah. Kind of under that same context. If you think about before with traditional storage, the vSphere or the array really doesn't understand what's going on underlying storage, but with vVols the array and vSphere completely understand at a disc level even, how that VM should be treated. So that helps the storage admin. Storage admin can now go in and see a specific disc of a VM and see the performance on the array. They can go in the array and see, oh, this disc on this VM has got performance issues or needs to be encrypted, or here's the size of that disc. And you couldn't easily see that with your traditional storage. So there's really a lot of benefits and it frees up a lot of time for the storage administrator and enables the VI admin to be able to do a lot of the storage management. >> So there have been, there been a lot of movements over the last decade in the realm of software defined storage. Where essentially all of the things that you are talking about are completely abstracted from the underlying hardware. In this case, you're leveraging the horsepower, if you will and the intelligence of a storage array that has a lot of horsepower and intelligence, and you're accessing those features. You mentioned encryption, whether if you're doing a snapshot or something like that, what's interesting here is it kind of maps to what we're looking at now, which is the trend in the direction of things like DPUs. >> If you go back in history long enough, we had the, you know, the TOE, NIC, TCP offload, you know, the idea of, hey, you know what, what if we had a smart device with its own brain power and we leveraged it. Well, you guys have been doing that from a vVols all perspective with NetApp filers, for lack of better term. For how long now, when did, when were they originally? >> 6.0 it was so it's been what? 11, 12 years. Something like that. >> It's been a while. So yeah, but it's been a decade or so. >> Mm-hmm >> So what's on the frontier. What's the latest there in terms of, in terms of cool stuff that's coming out. >> So actually today, in one of the things that we worked with NetApp that was part of the design partnership was, you know, the NVMe over Fabric protocol has become very popular to extend that functionality of all flash to the, an external array. And now we announce today, in including with that NVMe over Fabrics, you can now do vVols with NVMe over Fabrics. And again, that was something that we worked with NetApp to be a design partner for them. >> That's right. We're very excited about it. We've always been, you know, NVMe been something we've been very proud of for a while. Delivering the first end to end NVMe stack from inside the host, through the fabric, to the array, with the arrays front ports, all the way to the disc on the backend. So we're very excited about that. >> So target market joint NetApp, VMware customers, I presume. >> Really it's, the key here that I like to make sure customers understand is to see that vVols are on the leading edge of VMware's storage design. Some tend to think that maybe vVols wasn't the primary focus, but actually now it is the primary focus. Now I always like to give the caveat that VMFS and NFS are not going away. Those are still very much stuff that we work on. It's just that most of the engineering focus is on virtual volumes or vVols. >> Yeah. Similarly, when you talk about and you're sort of alluding to vSAN when we start talking about VMFS and things like that. >> Yeah. >> Architecturally, we've been talking to folks about the recent announcements with capabilities within AWS. You know, NetApp in AWS for VMware environments. Breaking out of the stranglehold that the, oh, you want more storage, you must buy more CPU and memory, building block process entails. The reality is no matter what you do with vSAN, you're going to have certain constraints that go away when now you have the option to leverage storage from the NetApp filers. >> Yeah, absolutely. >> So how does, how do vVols play in the cloud strategy moving forward? >> Well, so one of the things that we do with, vVols currently is mostly On-prem. But when you have the storage architecture, that vVols gives you as far as individual objects, it makes it much easier to migrate up into the cloud because you're not trying to migrate individual VMs that are on another type of system, whatever it might be, those objects are already their own entity. Right, so cloud, Tanzu, those type of things, those vVol objects are already their own entity. So it makes it very easy to migrate them on and off prem. >> So Chance talk to us a little bit about this from NetApp's perspective. You're in customer conversations, who are you talking to? Is this primarily an engineering conversation? Has this gone up the stack in terms of customers are finding themselves in this default multi-cloud environment? >> Yeah, so interestingly, when I talk to customers these days they are almost all either on a journey to a hybrid multi-cloud or they're in some kind of phase of transforming themselves into their own hyperscaler, right? They're be adopting a cloud service provider model and vVols is a perfect fit for that kind of model, because you have the ability to offer different tiers of service, different qualities of service with VM granular controls or VMDK granular controls, even. And even if you look at First Class Disc, right? Which is something that came out largely to support Tanzu, I think which fantastic use case for vVols as well there, but that gives you the ability to offer something like Amazon EBS, right? You can offer Amazon EBS in a native VMware stack using First Class Discs and vVols. And you're able to apply things like quality of service with that granular control that allows you to guarantee that customer the disc that they bought and paid for. They're going to get the IOPS that they're paying for because you're applying those QoS policies directly to that object on the array. And instead of having to worry about is the array going to be able to handle it? Are you going to have one VM that consumes all your IO, you know? You don't have to worry about that with vVols because you've got that integration with the array's native quality controls. >> And Chance what's in this for me as a customer? I'm hearing productivity, I'm hearing cost savings, control efficiency. Talk to me about the benefits in it for the folks that you're talking to. >> Yeah, absolutely. A lot of times it comes down to, you know I mentioned like the cloud service provider model, right? When you're looking to build a robust service catalog and you're able, you want to be able to meet all these like, we mentioned Tanzu, right? Containers as a service, you're able to provide the persistent volumes for your Kubernetes containers that are again, these native objects on the array and you have these fine grain controls, but it's handled at massive scale because it's all handled by storage policies, Kubernetes storage classes, which are natively mapped to VM storage policies through Tanzu. So it just, it gives you the ability to offer all of these services in a, again a rich and robust contents catalog. >> So what are you doing? So you mentioned a couple of things in terms of using array based quality of service. So give me an example of how you're avoiding issues of contention and over subscription in an environment where I'm an administrator and I've got this virtual volume that's servicing this VM or this app on this VM. What kind of visibility do I have down into the actual resources because look at the end of that chain there's a physical resource. And that physical resource represents, what? IOPS and bandwidth and latency and throughput and all of this bundle of things. So how do you avoid colliding with others who are trying to carve vVols out of this world? >> You mean like a noisy neighbor type of thing? >> Yeah. Yeah. >> So that's actually one of the big benefits that you get with vVols is that because those vial objects are native on the array, they're not sharing a loan or a volume. They're not sharing a resource. The only resource they're actually sharing is the array itself. So you don't get that typical noisy neighbor where this one's using all the resources of that volume because really you're looking out at the all encompassing array. And so a storage administrator and the VI admin have a lot more insight. The VI admin can now go to the storage admin if there's say a debugging issue, they want to find a problem. The storage admin now can see those individual objects and say, oh, well this VM, it's not really this, it's not all the discs. It's just disc number two or disc number three or they can actually see at a single disc level on the array, the performance, the latency, you know, the QS, all that stuff. >> Oh, absolutely. >> And that really is what, it frees up at the storage admin's time because the debugging is so much more simple. And it also allows the storage admin a lot more insight. Right? They know those, what's the problem. If you were typically looking at a loaner volume, they don't really know what's going on inside that and neither does the array. But with vVols, the array knows what each disc and how it's supposed to be treated based on the policies that the customer defines. So if one VM is supposed to have a certain QS and another VM isn't. The array knows that that VM, if it goes above it, it's going to be like, nope, you can't have those resources. You weren't granted those resources, but this one was. So you have much more control. And again, it's at an application or a VM level. >> And it's still, it's fairly dynamically configurable. I spoke to a customer just the other day. They are a cloud service provider. And what they do is their customers are able to go in and change their quality of service. So they go into that service portal and they say, okay, I'm paying for gold and I want platinum and they'll go in. They know that they've got a certain time where they need more IO capacity. So they'll go in, they'll pay the fee, increase that capability. And then when they don't need it anymore, they'll downgrade again. >> Okay, so that assumes some ability at the array level to do some sort of resource sharing and balancing to be able to go out and get, say more IO. Because again, fundamentally, if you have a virtual volume, that's drawing its resources from five storage devices, whether those are SSD based or NVMe or spinning disc that represents a finite it amount of resource. The assumption is if you're saying that the array is the pool that you need to worry about, that assumes the array has the ability to go beyond here, based on a policy. >> So that's how it works. It does... >> Well, essentially. I mean, you can't outrun physics. So if the array can't go faster, but the idea is that you understand the performance profile of your array and then you create your service tiers appropriately. >> Okay. >> Yeah. And one of the big benefits is like Chance was saying, if you want to change a profile that used to be a Storage vMotion to a different data store. Now it's just a policy change. The storage admin doesn't have to do anything. The VI admin just changes the policy. And then the array understands, oh, I now need to treat that different. And that's exactly what Chance was talking about in that cloud provider situation, where today I'm using a 100,000 IOPS. I need to use 200,000 tomorrow for special, whatever it is, but I only need to use it for tomorrow. So they don't have to move anything. They just change the policy for that time. And then they change it back. They don't have to do anything on the array itself. They don't have to change anything physically on the VM. It's just a policy change. And that's really where you get that dynamic control of the storage capability. >> So as business dynamics are changing and I'm thinking of like black Friday or Prime day, being able to dial things up and dial it down, they have the ability to do that with a policy. >> Yes. >> Exactly. >> So huge time savings there. >> Oh, it's huge. Yeah. >> Yeah. >> And it simplifies because now, I don't have to have multiple data stores. You can have one data store, all your VMs in there. You can limit test and dev and you can maximize business critical applications. Again, all via policy. So you've simplified your infrastructure. You've gone to more of a programmatic approach of managing your storage capabilities. But you're now managing at the VM level. >> So we mentioned that the cloud chaos (indistinct) that was mentioned this morning during the Keynote and we're saying a lot of customers are still in this cloud chaos phase. They want to get to Cloud Smart. How is this going to be one of those tools that helps customers pull the levers, dial the knobs, to be able to get to eventually, Cloud Smart. >> I could go on for this for hours. (Lisa Laughs) (Chance chuckles) This is really what simplifies storage. Because typically when you use traditional storage, you're going to have to figure out that this data store has this capability or another example, as you mentioned was Tanzu. If you're managing persistent volumes and you're not using something like vVols, if you want to get a certain storage capability, you have to either tag it or you have to create that data store with that capability. All of that goes away when you use vVols. So now that chaos of multiple data stores, multiple lines or multiple volumes, all that stuff goes away. So now you're simplifying your infrastructure, you have a programmatic approach to managing your storage and you can use it for all of your different types of workloads. So cloud, Kubernetes, persistent volumes, all that type of stuff. And again, all being managed via a simple and again, programmatic approach. So you could automate this. You know today, like you said, black Friday. Okay, Black, Friday's coming up. I want to change the policy. You could automate that. So you don't even have to go in and physically make the change of the policy now. You just say on Fridays, change it to this policy on Sunday night, change it back. >> Yep. >> Again, that's not something you can do with traditional storage. >> Okay. >> And I think from a simplification standpoint as well, you know, I was telling you about that other customer a couple days ago, they were running into the inability to grow beyond the bounds of VMFS file systems for very, very large VMs. And so what I talked to them about was look, if you go to vVols, you're not bound by file systems anymore. You have the capacity of the array and you can have VM discs up to 62 terabytes, you know, as many as you want. And it doesn't matter what they fit in because we can fit them all. So it's, to be able to, and that's some of our largest customers, the reason they go with vVols is to be able to grow beyond the bounds of traditional storage, anything like path limits, you know. That's something you have to contend with. >> Path limits, line limits, all that stuff. Typically just disappears with vVols. >> All those limits go away. Guys- >> They go away. >> Amazing. Congratulations on the work that you guys have done. Thank you so much for joining us on theCUBE talking about the value in it for customers and obviously the technical depths of the NetApp, VMware relationship. Guys, we appreciate your time. >> Yeah, thanks for having us on. >> Our pleasure. For my guests and Dave Nicholson. I'm Lisa Martin. You're watching theCUBE live from VMware Explorer 2022, Dave and I will be right back with our next guest. So stick around. (upbeat music)

>>Hey everyone. It's the cube live at VMware Explorer, 2022. We're at Mascone center and lovely, beautiful San Francisco. Dave Volante is with me, Lisa Martin. Beautiful weather here today. >>It is beautiful. I couldn't have missed this one because you know, the orange and the pure and VA right. Are history together. I had a, I had a switch sets. You >>Did. You were gonna have FOMO without a guest. Who's back. One of our longtime alumni V Stewart, VP of global technology alliances partners at pure storage one. It's great to have you back on the program, seeing you in 3d >>It's. It's so great to be here and we get a guest interviewer. So this >>Is >>Fantastic. Fly by. Fantastic. >>So talk to us, what's going on at pure. It's been a while since we had a chance to talk, >>Right. Well, well, besides the fact that it's great to see in person and to be back at a conference and see all of our customers, partners and prospects, you know, pure storage has just been on a tear just for your audience. Many, those who don't follow pure, right? We finished our last year with our Q4 being 41% year over year growth. And in the year, just under 2.2 billion, and then we come outta the gates this year, close our Q1 at 50% year over year, quarter quarterly growth. Have you ever seen a storage company or an infrastructure partner at 2 billion grow at that rate? >>Well, the thing was, was striking was that the acceleration of growth, because, you know, I mean, COVID, there were supply chain issues and you know, you saw that. And then, and we've seen this before at cloud companies, we see actually AWS as accelerated growth. So this is my premise here is you guys are actually becoming a cloud-like company building on top of, of infrastructure going from on-prem to cloud. But we're gonna talk about that. >>This is very much that super cloud premise. Well, >>It is. And, and, but I think it's it's one of the characteristics is you can actually, it, you know, we used to see companies, they go, they'd come out of escape velocity, and then they'd they'd growth would slow. I used to be at IDC. We'd see it. We'd see it. Okay. Down then it'd be single digits. You guys are seeing the opposite. >>It's it's not just our bookings. And by the way, I would be remiss if I didn't remind your audience that our second quarter earnings call is tomorrow. So we'll see how this philosophy and momentum keeps going. See, right. But besides the growth, right? All the external metrics around our business are increasing as well. So our net promoter score increased right at 85.2. We are the gold standard, not just in storage in infrastructure period. Like there's no one close to us, >>85. I mean, that's like, that's a, like apple, >>It's higher than apple than apple. It's apple higher than Tesla. It's higher than AWS shopping. And if you look in like our review of our products, flash rate is the leader in the gardener magic quadrant for, for storage array. It's been there for eight years. Port works is the leader in the GIGO OME radar for native Kubernetes storage three years in a row. Like just, it's great to be at a company that's hitting on all cylinders. You know, particularly at a time that's just got so much change going on in our >>Industry. Yeah. Tremendous amount of change. Talk about the, the VMware partnership from a momentum of velocity perspective what's going on there. And some of the things that you're accelerating. >>Absolutely. So VMware is, is the, the oldest or the longest tenured technology partner that we've had. I'm about to start my 10th year at pure storage. It feels like it was yesterday. When I joined, they were a, an Alliance partner before I joined. And so not to make that about me, but that's just like we built some of the key aspects around our first product, the flash array with VMware workloads in mind. And so we are a, a co-development partner. We've worked with them on a number of projects over years of, of late things that are top of mind is like the evolution of vials, the NV support for NVMe over fabric storage, more recently SRM support for automating Dr. With Viv a deployments, you know, and, and, and then our work around VMware ex extends to not just with VMware, they're really the catalyst for a lot of three way partnerships. So partnerships into our investments in data protection partners. Well, you gotta support V ADP for backing up the VMware space, our partnership within Nvidia, well, you gotta support NVA. I, so they can accelerate bringing those technologies into the enterprise. And so it's it, it's not just a, a, a, you know, unilateral partnership. It's a bidirectional piece because for a lot of customers, VMware's kind of like a touchpoint for managing the infrastructure. >>So how is that changing? Because you you've mentioned, you know, all the, the, the previous days, it was like, okay, let's get, make storage work. Let's do the integration. Let's do the hard work. It was kind of a race for the engineering teams to get there. All the storage companies would compete. And it was actually really good for the industry. Yeah, yeah. Right. Because it, it went from, you know, really complex, to much, much simpler. And now with the port works acquisition, it brings you closer to the whole DevOps scene. And you're seeing now VMware it's with its multi-cloud initiatives, really focusing on, you know, the applications and that, and that layer. So how does that dynamic evolve in terms of the partnership and, and where the focus is? >>So there's always in the last decade or so, right. There's always been some amount of overlap or competing with your partnerships, right. Something in their portfolios they're expanding maybe, or you expand you encroach on them. I think, I think two parts to how I would want to answer your question. The retrospective look V VMware is our number one ISV from a, a partner that we, we turn transactions with. The booking's growth that I shared with you, you could almost say is a direct reflection of how we're growing within that, that VMware marketplace. We are bringing a platform that I think customers feel services their workloads well today and gives them the flexibility of what might come in their cloud tomorrow. So you look at programs like our evergreen one subscription model, where you can deploy a consumption based subscription model. So very cloud-like only pay for what you use on-prem and turn that dial as you need to dial it into a, a cloud or, or multiple clouds. >>That's just one example. Looking forward, look, port works is probably the platform that VMware should have bought because when you look at today's story, right, when kit Culbert shared a, a cross cloud services, right, it was, it was the modern version of what VMware used to say, which was, here's a software defined data center. We're gonna standardize all your dissimilar hardware, another saying software defined management to standardize all your dissimilar clouds. We do that for Kubernetes. We talk about accelerating customers' adoption of Kubernetes by, by allowing developers, just to turn on an enable features, be its security, backup high availability, but we don't do it mono in a, you know, in a, in a homogeneous environment, we allow customers to do it heterogeneously so I can deploy VMware Tansu and connect it to Amazon EKS. I can switch one of those over to red head OpenShift, non disruptively, if I need to. >>Right? So as customers are going on this journey, particularly the enterprise customers, and they're not sure where they're going, we're giving them a platform that standardizes where they want to go. On-prem in the cloud and anywhere in between. And what's really interesting is our latest feature within the port works portfolio is called port works data services, and allows customers to deploy databases on demand. Like, install it, download the binaries. You have a cus there, you got a database, you got a database. You want Cassandra, you want Mongo, right? Yeah. You know, and, and for a lot of enterprise customers, who've kind of not, not know where to don't know where to start with port works. We found that to be a great place where they're like, I have this need side of my infrastructure. You can help me reduce cost time. Right. And deliver databases to teams. And that's how they kick off their Tansu journey. For example. >>It's interesting. So port works was the enabler you mentioned maybe VMware should above. Of course they had to get the value out of, out of pivotal. >>Understood. >>So, okay. Okay. So that, so how subsequent to the port works acquisition, how has it changed the way that you guys think about storage and how your customers are actually deploying and managing storage? >>Sure. So you touched base earlier on what was really great about the cloud and VMware was this evolution of simplifying storage technologies, usually operational functions, right? Making things simpler, more API driven, right. So they could be automated. I think what we're seeing customers do to today is first off, there's a tremendous rise in everyone wanting to do every customer, not every customer, a large portion of the customer bases, wanting to acquire technology on as OPEX. And it, I think it's really driven by like eliminate technical debt. I sign a short term agreement, our short, our shortest commitment's nine months. If we don't deliver around what we say, you walk away from us in nine months. Like you, you couldn't do that historically. Furthermore, I think customers are looking for the flexibility for our subscriptions, you know, more from between on-prem and cloud, as I shared earlier, is, is been a, a, a big driver in that space. >>And, and lastly, I would, would probably touch on our environmental and sustainability efforts. You saw this morning, Ragu in the keynote touch on what was it? Zero carbon consumption initiative, or ZCI my apologies to the veer folks. If I missed VO, you know, we've had, we've had sustainability into our products since day one. I don't know if you saw our inaugural ESG report that came out about 60 days ago, but the bottom line is, is, is our portfolio reduces the, the power directly consumed by storage race by up to 80%. And another aspect to look at is that 97% of all of the products that we sold in the last six years are still in the market today. They're not being put into, you know, into, to recycle bins and whatnot, pure storage's goal by the end of this decade is to further drive the efficiency of our platforms by another 66%. And so, you know, it's an ambitious goal, but we believe it's >>Important. Yeah. I was at HQ earlier this month, so I actually did see it. So, >>Yeah. And where is sustainability from a differentiation perspective, but also from a customer requirements perspective, I'm talking to a lot of customers that are putting that requirement when they're doing RFPs and whatnot on the vendors. >>I think we would like to all, and this is a free form VO comment here. So my apologies, but I think we'd all like to, to believe that we can reduce the energy consumption in the planet through these efforts. And in some ways maybe we can, what I fear in the technology space that I think we've all and, and many of your viewers have seen is there's always more tomorrow, right? There's more apps, more vendors, more offerings, more, more, more data to store. And so I think it's really just an imperative is you've gotta continue to be able to provide more services or store more data in this in yesterday's footprint tomorrow. A and part of the way they get to is through a sustainability effort, whether it's in chip design, you know, storage technologies, et cetera. And, and unfortunately it's, it's, it's something that organizations need to adopt today. And, and we've had a number of wins where customers have said, I thought I had to evacuate this data center. Your technology comes in and now it buys me more years of time in this in infrastructure. And so it can be very strategic to a lot of vendors who think their only option is like data center evacuation. >>So I don't want to, I, I don't wanna set you up, but I do want to have the super cloud conversation. And so let's go, and you, can you, you been around a long time, your, your technical, or you're more technical than I am, so we can at least sort of try to figure it out together when I first saw you guys. I think Lisa, so you and I were at, was it, when did you announce a block storage for AWS? The, was that 2019 >>Cloud block store? I believe block four years >>Ago. Okay. So 20 18, 20 18, 20 18. Okay. So we were there at, at accelerate at accelerate and I said, oh, that's interesting. So basically if I, if I go back there, it was, it was a hybrid model. You, you connecting your on-prem, you were, you were using, I think, priority E C two, you know, infrastructure to get high performance and connecting the two. And it was a singular experience yeah. Between on-prem and AWS in a pure customer saw pure. Right. Okay. So that was the first time I started to think about Supercloud. I mean, I think thought about it in different forms years ago, but that was the first actual instantiation. So my, my I'm interested in how that's evolved, how it's evolving, how it's going across clouds. Can you talk just conceptually about how that architecture is, is morphing? >>Sure. I just to set the expectations appropriately, right? We've got, we've got a lot of engineering work that that's going on right now. There's a bunch of stuff that I would love to share with you that I feel is right around the corner. And so hopefully we'll get across the line where we're at today, where we're at today. So the connective DNA of, of flash array, OnPrem cloud block store in the cloud, we can set up for, for, you know, what we call active. Dr. So, so again, customers are looking at these arrays is a, is a, is a pair that allows workloads to be put into the, put into the cloud or, or transferred between the cloud. That's kind of like your basic building, you know, blocking tackling 1 0 1. Like what do I do for Dr. Example, right? Or, or gimme an easy button to, to evacuate a data center where we've seen a, a lot of growth is around cloud block store and cloud block store really was released as like a software version of our hardware, Ray on-prem and it's been, and, and it hasn't been making the news, but it's been continually evolving. >>And so today the way you would look at cloud block store is, is really bringing enterprise data services to like EBS for, for AWS customers or to like, you know, is Azure premium disc for Azure users. And what do I mean by enterprise data services? It's, it's the, the, the way that large scale applications are managed, on-prem not just their performance and their avail availability considerations. How do I stage the, the development team, the sandbox team before they patch? You know, what's my cyber protection, not just data protection, how, how am I protected from a cyber hack? We bring all those capabilities to those storage platforms. And the, the best result is because of our data reduction technologies, which was critical in reducing the cost of flash 10 years ago, reduces the cost of the cloud by 50% or more and pays for the, for pays more than pays for our software of cloud block store to enable these enterprise data services, to give all these rapid capabilities like instant database, clones, instant, you know, recovery from cyber tech, things of that nature. >>Do customers. We heard today that cloud chaos are, are customers saying so, okay, you can run an Azure, you can run an AWS fine. Are customers saying, Hey, we want to connect those islands. Are you hearing that from customers or is it still sort of still too early? >>I think it's still too early. It doesn't mean we don't have customers who are very much in let's buy, let me buy some software that will monitor the price of my cloud. And I might move stuff around, but there's also a cost to moving, right? The, the egress charges can add up, particularly if you're at scale. So I don't know how much I seen. And even through the cloud days, how much I saw the, the notion of workloads moving, like kind of in the early days, like VMO, we thought there might be like a, is there gonna be a fall of the moon computing, you know, surge here, like, you know, have your workload run where power costs are lower. We didn't really see that coming to fruition. So I think there is a, is a desire for customers to have standardization because they gain the benefits of that from an operational perspective. Right. Whether they put that in motion to move workloads back and forth. I think >>So let's say, let's say to be determined, let let's say they let's say they don't move them because your point you knows too expensive, but, but, but, but you just, I think touched on it is they do want some kind of standard in terms of the workflow. Yep. You you're saying you're, you're starting to see demand >>Standard operating practices. Okay. >>Yeah. SOPs. And if they're, if they're big into pure, why wouldn't they want that? If assuming they have, you know, multiple clouds, which a lot of customers do. >>I, I, I I'll assure with you one thing that the going back to like basic primitives and I touched it touched on it a minute ago with data reduction. You have customers look at their, their storage bills in the cloud and say, we're gonna reduce that by half or more. You have a conversation >>Because they can bring your stack yeah. Into the cloud. And it's got more maturity than what you'd find from a cloud company, cloud >>Vendor. Yeah. Just data. Reduction's not part of block storage today in the cloud. So we've got an advantage there that we, we bring to bear. Yeah. >>So here we are at, at VMware Explorer, the first one of this name, and I love the theme, the center of the multi-cloud universe. Doesn't that sound like a Marvel movie. I feel like there should be superheroes walking around here. At some point >>We got Mr. Fantastic. Right here. We do >>Gone for, I dunno it >>Is. But a lot of, a lot of news this morning in the keynote, you were in the keynote, what are some of the things that you're hearing from VMware and what excites you about this continued evolution of the partnership with pure >>Yeah. Great point. So I, I think I touched on the, the two things that really caught my attention. Obviously, you know, we've got a lot of investment in V realize it was now kind of rebranded as ay, that, you know, I think we're really eager to see if we can help drive that consumption a bit higher, cuz we believe that plays into our favor as a vendor. We've we've we have over a hundred templates for the area platform right now to, you know, automation templates, whether it's, you know, levels set your platform, you know, automatically move workloads, deploy on demand. Like just so, so again, I think the focus there is very exciting for us, obviously when they've got a new release, like vSphere eight, that's gonna drive a lot of channel behaviors. So we've gotta get our, you know, we're a hundred percent channel company. And so we've gotta go get our channel ready because with about half of the updates of vSphere is, is hardware refresh. And so, you know, we've gotta be, be prepared for that. So, you know, some of the excitements about just being how to find more points in the market to do more business together. >>All right. Exciting cover the grounds. Right. I mean, so, okay. You guys announce earnings tomorrow, so we can't obviously quiet period, but of course you're not gonna divulge that anyway. So we'll be looking for that. What other catalysts are out there that we should be paying attention to? You know, we got, we got reinvent coming up in yep. In November, you guys are obviously gonna be there in, in a big way. Accelerate was back this year. How was accelerate >>Accelerate in was in Los Angeles this year? Mm. We had great weather. It was a phenomenal venue, great event, great partner event to kick it off. We happened to, to share the facility with the president and a bunch of international delegates. So that did make for a little bit of some logistic securities. >>It was like the summit of the Americas. I, I believe I'm recalling that correctly, but it was fantastic. Right. You, you get, you get to bring the customers out. You get to put a bunch of the engineers on display for the products that we're building. You know, one of the high, you know, two of the highlights there were, we, we announced our new flash blade S so, you know, higher, more performant, more scalable version of our, our scale and object and file platform with that. We also announced the, the next generation of our a I R I, which is our AI ready, AI ready infrastructure within video. So think of it like converged infrastructure for AI workloads. We're seeing tremendous growth in that unstructured space. And so, you know, we obviously pure was funded around block storage, a lot around virtual machines. The data growth is in unstructured, right? >>We're just seeing, we're seeing, you know, just tons of machine learning, you know, opportunities, a lot of opportunities, whether we're looking at health, life sciences, genome sequencing, medical imaging, we're seeing a lot of, of velocity in the federal space. You know, things, I can't talk about a lot of velocity in the automotive space. And so just, you know, from a completeness of platform, you know, flat flash blade is, is really addressing a need really kind of changing the market from NAS as like tier two storage or object is tier three to like both as a tier one performance candidate. And now you see applications that are supporting running on top of object, right? All your analytics platforms are on an object today, Absolut. So it's a, it's a whole new world. >>Awesome. And Pierce also what I see on the website, a tech Fest going on, you guys are gonna be in Seoul, Mexico city in Singapore in the next week alone. So customers get the chance to be able to in person talk with those execs once again. >>Yeah. We've been doing the accelerate tech tech fests, sorry about that around the globe. And if one of those align with your schedule, or you can free your schedule to join us, I would encourage you. The whole list of events dates are on pure storage.com. >>I'm looking at it right now. Vaon thank you so much for joining Dave and me. I got to sit between two dapper dudes, great conversation about what's going on at pure pure with VMware better together and the, and the CATA, the cat catalysis that's going on on both sides. I think that's an actual word I should. Now I have a degree biology for Vaughn Stewart and Dave Valante I'm Lisa Martin. You're watching the cube live from VMware Explorer, 22. We'll be right back with our next guest. So keep it here.

(upbeat music) >> Okay, we're back covering AWS Storage Day 2022 with Ashish Palekar. Who's the general manager of AWS EBS Snapshot and Edge and Cami Tavares. Who's the head of product at Amazon EBS. Thanks for coming back in theCube guys. Great to see you again. >> Great to see you as well, Dave. >> Great to see you, Dave. Ashish, we've been hearing a lot today about companies all kinds of applications to the cloud and AWS and using their data in new ways. Resiliency is always top of mind for companies when they think about just generally their workloads and specifically the clouds. How should they think about customers think about data resiliency? >> Yeah, when we think about data resiliency it's all about making sure that your application data, the data that your application needs is available when it needs it. It's really the ability for your workload to mitigate disruptions or recover from them. And to build that resilient architecture you really need to understand what kinds of disruptions your applications can experience. How broad the impact of those disruptions is, and then how quickly you need to recover. And a lot of this is a function of what the application does, how critical it is. And the thing that we constantly tell customers is, this works differently in the cloud than it does in a traditional on-premises environment. >> What's different about the cloud versus on-prem? Can you explain how it's different? >> Yeah, let me start with a video on-premises one. And in the on-premises one, building resilient architectures is really the customer's responsibility, and it's very challenging. You'll start thinking about what your single points of failure are. To avoid those, you have to build in redundancy, you might build in replication as an example for storage and doing this now means you have to have provision more hardware. And depending on what your availability requirements are, you may even have to start looking for multiple data centers, some in the same regions, some in different geographical locations. And you have to ensure that you're fully automated, so that your recovery processes can take place. And as you can see that's a lot of owners being placed on the customer. One other thing that we hear about is really elasticity and how elasticity plays into the resiliency for applications. As an example, if you experience a sudden spike in workloads, in a on-premises environment, that can lead to resource saturation. And so really you have two choices. One is to sort of throttle the workload and experience resiliency, or your second option becomes buying additional hardware and securing more capacity and keeping it fair low in case of experiencing such a spike. And so your two propositions that are either experiencing resiliency, challenges or paying really to have infrastructure that's lying around. And both of those are different really when you start thinking about the cloud. >> Yeah, there's a third option too, which is lose data, which is not an option. Go ahead- >> Which is not, yeah, I pretty much as a storage person, that is not an option. The reason about that that we think is reasonable for customers to take. The big contrast in the cloud really comes with how we think about capacity. And fundamentally the the cloud gives you that access to capacity so you are not managing that capacity. The infrastructure complexity and the cost associated with that are also just a function of how infrastructure is built really in the cloud. But all of that really starts with the bedrock of how we design for avoiding single points of failure. The best way to explain this is really to start thinking about our availability zones. Typically these availability zones consist of multiple data centers, located in the same regional area to enable high throughput and low latency for applications. But the availability zones themselves are physically independent. They have independent connections to utility power, standalone backup power resources, independent mechanical services and independent network connectivity. We take availability zone independence extremely seriously, so that when customers are building the availability of their workload, they can architect using these multiple zones. And that is something that when I'm talking to customers or Tami is talking to customers, we highly encourage customers to keep in mind as they're building resiliency for their applications. >> Right, so you can have within an availability zone, you can have, you know, instantaneous, you know when you're doing it right. You've got, you've captured that data and you can asynchronously move to outside of that in case there's, the very low probability, but it does happen, you get some disasters. You're minimizing that RPO. And I don't have to worry about that as a customer and figuring out how to do three site data centers. >> That's right. Like that even further, now imagine if you're expanding globally. All those things that we described about like creating new footprint and creating a new region and finding new data centers. As a customer in an on-premises environment, you take that on yourself. Whereas with AWS, because of our global presence, you can expand to a region and bring those same operational characteristics to those environments. And so again, bringing resiliency as you're thinking about expanding your workload, that's another benefit that you get from using the availability zone region architecture that AWS has. >> And as Charles Phillips, former CEO of Infor said, "Friends, don't let friends build data center," so I don't have to worry about building the data center. Let's bring Cami into the discussion here. Cami, think about elastic block storage, it gives, you know customers, you get persistent block storage for EC2 instances. So it's foundational for any mission critical or business critical application that you're building on AWS. How do you think about data resiliency in EBS specifically? I always ask the question, what happens if something goes wrong? So how should we think about data resiliency in EBS specifically? >> Yeah, you're right Dave, block storage is a really foundational piece. When we talk to customers about building in the cloud or moving an application to the cloud, and data resiliency is something that comes up all the time. And with EBS, you know EBS is a very large distributed system with many components. And we put a lot of thought and effort to build resiliency into EBS. So we design those components to operate and fail independently. So when customers create an EBS volume for example, we'll automatically choose the best storage nodes to address the failure domain and the data protection strategy for each of our different volume types. And part of our resiliency strategy also includes separating what we call a volume life cycle control plane. Which are things like creating a volume, or attaching a volume to an EC2 instance. So we separate that control plane, from the storage data plane, which includes all the components that are responsible for serving IO to your instance, and then persisting it to durable media. So what that means is once a volume is created and attached to the instance, the operations on that volume they're independent from the control point function. So even in the case of an infrastructure event, like a power issue, for example, you can recreate an EBS volume from a snapshot. And speaking of snapshots, that's the other core pillar of resiliency in EBS. Snapshots are point in time copies of EBS volumes that would store in S3. And snapshots are actually a regional service. And that means internally we use multiple of the availability zones that Ashish was talking about to replicate your data so that the snapshots can withstand the failure of an availability zone. And so thanks to that availability zone independence, and then this builtin component independence, customers can use that snapshot and recreate an EBS following another AZO or even in another region if they need to. >> Great so, okay, so you touched on some of the things EBS does to build resiliency into the service. Now thinking about over your right shoulders, you know, Joan Deviva, so what can organizations do to build more resilience into their applications on EBS so they can enjoy life without anxiety? >> (laughs) That is a great question. Also something that we love to talk to customers about. And the core thing to think about here is that we don't believe in a one size fits all approach. And so what we are doing in EBS is we give customers different tools so that they can design a resiliency strategy that is custom tailored for their data. And so to do this, this resiliency assessment, you have to think about the context of this specific workload and ask questions like what other critical services depend on this data and what will break if this data's not available and how long can can those systems withstand that, for example. And so the most important step I'll mention it again, snapshots, that is a very important step in a recovery plan. Make sure you have a backup of your data. And so we actually recommend that customers take the snapshots at least daily. And we have features that make that easier for you. For example, Data Lifecycle Manager which is a feature that is entirely free. It allows you to create backup policies, and then you can automate the process of creating the snapshot, so it's very low effort. And then when you want to use that backup to recreate a volume, we have a feature called Fast Snapshot Restore, that can expedite the creation of the volume. So if you have a more, you know a shorter recovery time objective you can use that feature to expedite the recovery process. So that's backup. And then the other pillar we talked to customers about is data replication. Just another very important step when you're thinking about your resiliency and your recovery plans. So with EBS, you can use replication tools that work at the level of the operating system. So that's something like DRBD for example. Or you can use AWS Elastic Disaster Recovery, and that will replicate your data across availability zones or nearby regions too. So we talked about backup and replication, and then the last topic that we recommend customers think about is having a workload monitoring solution in place. And you can do that in EBS, using cloud watch metrics. So you can monitor the health of your EBS volume using those metrics. We have a lot of tips in our documentation on how to measure that performance. And then you can use those performance metrics as triggers for automated recovery workflows that you can build using tools like auto scaling groups for example. >> Great, thank you for that advice. Just quick follow up. So you mentioned your recommendation, at least daily, what kind of granularity, if I want to compress my RPO can I go at a more granular level? >> Yes, you can go more granular and you can use again the daily lifecycle manager to define those policies. >> Great, thank you. Before we go, I want to just quickly cover what's new with EBS. Ashish, maybe you could talk about, I understand you've got something new today. You've got an announcement, take us through that. >> Yeah, thanks for checking in and I'm so glad you asked. We talked about how snapshots help resilience and are a critical part of building resilient architectures. So customers like the simplicity of backing up their EC2 instances, using multi volume snapshots. And what they're looking for is the ability to back up only to exclude specific volumes from the backup, especially those that don't need backup. So think of applications that have cash data, or applications that have temporary data that really doesn't need backup. So today we are adding a new parameter to the create snapshots API, which creates a crash consistent set of snapshots for volumes attached to an EC2 instance. Where customers can now exclude specific volumes from an instance backup. So customers using data life cycle manager that can be touched on, can automate their backups. And again they also get to exclude these specific volumes. So really the feature is not just about convenience, but it's also to help customers save on cost. As many of these customers are managing tens of thousands of snapshots. And so we want to make sure they can take it at the granularity that they need it. So super happy to bring that into the hands of customers as well. >> Yeah, that's a nice option. Okay, Ashish, Cami thank you so much for coming back in theCube, helping us learn about what's new and what's cool and EBS, appreciate your time. >> Thank you for having us Dave. >> Thank you for having us Dave. >> You're very welcome now, if you want to learn more about EBS resilience, stay right here because coming up, we've got a session which is a deep dive on protecting mission critical workloads with Amazon EBS. Stay right there, you're watching theCube's coverage of AWS Storage Day 2022. (calm music)

(upbeat music) >> Hello, and welcome to "theCUBE" conversation here in Palo Alto, California. I'm John Furrier, host of "theCUBE," got a great security conversation, Ed Casper who's the founder and CEO of Cloud Storage Security, the great Cloud background, Cloud security, Cloud storage. Welcome to the "theCUBE Conversation," Ed. Thanks for coming on. >> Thank you very much for having me. >> I got Lafomo on that background. You got the nice look there. Let's get into the storage blind spot conversation around Cloud Security. Obviously, reinforced has came up a ton, you heard a lot about encryption, automated reasoning but still ransomware was still hot. All these things are continuing to be issues on security but they're all brought on data and storage, right? So this is a big part of it. Tell us a little bit about how you guys came about the origination story. What is the company all about? >> Sure, so, we're a pandemic story. We started in February right before the pandemic really hit and we've survived and thrived because it is such a critical thing. If you look at the growth that's happening in storage right now, we saw this at reinforced. We saw even a recent AWS Storage Day. Their S3, in particular, houses over 200 trillion objects. If you look just 10 years ago, in 2012, Amazon touted how they were housing one trillion objects, so in a 10 year period, it's grown to 200 trillion and really most of that has happened in the last three or four years, so the pandemic and the shift in the ability and the technologies to process data better has really driven the need and driven the Cloud growth. >> I want to get into some of the issues around storage. Obviously, the trend on S3, look at what they've done. I mean, I saw my land at storage today. We've interviewed her. She's amazing. Just the EC2 and S3 the core pistons of AWS, obviously, the silicons getting better, the IaaS layers just getting so much more innovation. You got more performance abstraction layers at the past is emerging Cloud operations on premise now with hybrid is becoming a steady state and if you look at all the action, it's all this hyper-converged kind of conversations but it's not hyper-converged in a box, it's Cloud Storage, so there's a lot of activity around storage in the Cloud. Why is that? >> Well, because it's that companies are defined by their data and, if a company's data is growing, the company itself is growing. If it's not growing, they are stagnant and in trouble, and so, what's been happening now and you see it with the move to Cloud especially over the on-prem storage sources is people are starting to put more data to work and they're figuring out how to get the value out of it. Recent analysts made a statement that if the Fortune 1000 could just share and expose 10% more of their data, they'd have net revenue increases of 65 million. So it's just the ability to put that data to work and it's so much more capable in the Cloud than it has been on-prem to this point. >> It's interesting data portability is being discussed, data access, who gets access, do you move compute to the data? Do you move data around? And all these conversations are kind of around access and security. It's one of the big vulnerabilities around data whether it's an S3 bucket that's an manual configuration error, or if it's a tool that needs credentials. I mean, how do you manage all this stuff? This is really where a rethink kind of comes around so, can you share how you guys are surviving and thriving in that kind of crazy world that we're in? >> Yeah, absolutely. So, data has been the critical piece and moving to the Cloud has really been this notion of how do I protect my access into the Cloud? How do I protect who's got it? How do I think about the networking aspects? My east west traffic after I've blocked them from coming in but no one's thinking about the data itself and ultimately, you want to make that data very safe for the consumers of the data. They have an expectation and almost a demand that the data that they consume is safe and so, companies are starting to have to think about that. They haven't thought about it. It has been a blind spot, you mentioned that before. In regards to, I am protecting my management plane, we use posture management tools. We use automated services. If you're not automating, then you're struggling in the Cloud. But when it comes to the data, everyone thinks, "Oh, I've blocked access. I've used firewalls. I've used policies on the data," but they don't think about the data itself. It is that packet that you talked about that moves around to all the different consumers and the workflows and if you're not ensuring that that data is safe, then, you're in big trouble and we've seen it over and over again. >> I mean, it's definitely a hot category and it's changing a lot, so I love this conversation because it's a primary one, primary and secondary cover data cotton storage. It's kind of good joke there, but all kidding aside, it's a hard, you got data lineage tracing is a big issue right now. We're seeing companies come out there and kind of superability tangent there. The focus on this is huge. I'm curious, what was the origination story? What got you into the business? Was it like, were you having a problem with this? Did you see an opportunity? What was the focus when the company was founded? >> It's definitely to solve the problems that customers are facing. What's been very interesting is that they're out there needing this. They're needing to ensure their data is safe. As the whole story goes, they're putting it to work more, we're seeing this. I thought it was a really interesting series, one of your last series about data as code and you saw all the different technologies that are processing and managing that data and companies are leveraging today but still, once that data is ready and it's consumed by someone, it's causing real havoc if it's not either protected from being exposed or safe to use and consume and so that's been the biggest thing. So we saw a niche. We started with this notion of Cloud Storage being object storage, and there was nothing there protecting that. Amazon has the notion of access and that is how they protect the data today but not the packets themselves, not the underlying data and so, we created the solution to say, "Okay, we're going to ensure that that data is clean. We're also going to ensure that you have awareness of what that data is, the types of files you have out in the Cloud, wherever they may be, especially as they drift outside of the normal platforms that you're used to seeing that data in. >> It's interesting that people were storing data lakes. Oh yeah, just store a womp we might need and then became a data swamp. That's kind of like go back 67 years ago. That was the conversation. Now, the conversation is I need data. It's got to be clean. It's got to feed the machine learning. This is going to be a critical aspect of the business model for the developers who are building the apps, hence, the data has code reference which we've focused on but then you say, "Okay, great. Does this increase our surface area for potential hackers?" So there's all kinds of things that kind of open up, we start doing cool, innovative, things like that so, what are some of the areas that you see that your tech solves around some of the blind spots or with object store, the things that people are overlooking? What are some of the core things that you guys are seeing that you're solving? >> So, it's a couple of things, right now, the still the biggest thing you see in the news is configuration issues where people are losing their data or accidentally opening up to rights. That's the worst case scenario. Reads are a bad thing too but if you open up rights and we saw this with a major API vendor in the last couple of years they accidentally opened rights to their buckets. Hackers found it immediately and put malicious code into their APIs that were then downloaded and consumed by many, many of their customers so, it is happening out there. So the notion of ensuring configuration is good and proper, ensuring that data has not been augmented inappropriately and that it is safe for consumption is where we started and, we created a lightweight, highly scalable solution. At this point, we've scanned billions of files for customers and petabytes of data and we're seeing that it's such a critical piece to that to make sure that that data's safe. The big thing and you brought this up as well is the big thing is they're getting data from so many different sources now. It's not just data that they generate. You see one centralized company taking in from numerous sources, consolidating it, creating new value on top of it, and then releasing that and the question is, do you trust those sources or not? And even if you do, they may not be safe. >> We had an event around super Clouds is a topic we brought up to get bring the attention to the complexity of hybrid which is on premise, which is essentially Cloud operations. And the successful people that are doing things in the software side are essentially abstracting up the benefits of the infrastructures of service from HN AWS, right, which is great. Then they innovate on top so they have to abstract that storage is a key component of where we see the innovations going. How do you see your tech that kind of connecting with that trend that's coming which is everyone wants infrastructures code. I mean, that's not new. I mean, that's the goal and it's getting better every day but DevOps, the developers are driving the operations and security teams to like stay pace, so policy seeing a lot of policy seeing some cool things going on that's abstracting up from say storage and compute but then those are being put to use as well, so you've got this new wave coming around the corner. What's your reaction to that? What's your vision on that? How do you see that evolving? >> I think it's great, actually. I think that the biggest problem that you have to do as someone who is helping them with that process is make sure you don't slow it down. So, just like Cloud at scale, you must automate, you must provide different mechanisms to fit into workflows that allow them to do it just how they want to do it and don't slow them down. Don't hold them back and so, we've come up with different measures to provide and pretty much a fit for any workflow that any customer has come so far with. We do data this way. I want you to plug in right here. Can you do that? And so it's really about being able to plug in where you need to be, and don't slow 'em down. That's what we found so far. >> Oh yeah, I mean that exactly, you don't want to solve complexity with more complexity. That's the killer problem right now so take me through the use case. Can you just walk me through how you guys engage with customers? How they consume your service? How they deploy it? You got some deployment scenarios. Can you talk about how you guys fit in and what's different about what you guys do? >> Sure, so, we're what we're seeing is and I'll go back to this data coming from numerous sources. We see different agencies, different enterprises taking data in and maybe their solution is intelligence on top of data, so they're taking these data sets in whether it's topographical information or whether it's in investing type information. Then they process that and they scan it and they distribute it out to others. So, we see that happening as a big common piece through data ingestion pipelines, that's where these folks are getting most of their data. The other is where is the data itself, the document or the document set, the actual critical piece that gets moved around and we see that in pharmaceutical studies, we see it in mortgage industry and FinTech and healthcare and so, anywhere that, let's just take a very simple example, I have to apply for insurance. I'm going to upload my Social Security information. I'm going to upload a driver's license, whatever it happens to be. I want to one know which of my information is personally identifiable, so I want to be able to classify that data but because you're trusting or because you're taking data from untrusted sources, then you have to consider whether or not it's safe for you to use as your own folks and then also for the downstream users as well. >> It's interesting, in the security world, we hear zero trust and then we hear supply chain, software supply chains. We get to trust everybody, so you got kind of two things going on. You got the hardware kind of like all the infrastructure guys saying, "Don't trust anything 'cause we have a zero trust model," but as you start getting into the software side, it's like trust is critical like containers and Cloud native services, trust is critical. You guys are kind of on that balance where you're saying, "Hey, I want data to come in. We're going to look at it. We're going to make sure it's clean." That's the value here. Is that what I'm hearing you, you're taking it and you're saying, "Okay, we'll ingest it and during the ingestion process, we'll classify it. We'll do some things to it with our tech and put it in a position to be used properly." Is that right? >> That's exactly right. That's a great summary, but ultimately, if you're taking data in, you want to ensure it's safe for everyone else to use and there are a few ways to do it. Safety doesn't just mean whether it's clean or not. Is there malicious content or not? It means that you have complete coverage and control and awareness over all of your data and so, I know where it came from. I know whether it's clean and I know what kind of data is inside of it and we don't see, we see that the interesting aspects are we see that the cleanliness factor is so critical in the workflow, but we see the classification expand outside of that because if your data drifts outside of what your standard workflow was, that's when you have concerns, why is PII information over here? And that's what you have to stay on top of, just like AWS is control plane. You have to manage it all. You have to make sure you know what services have all of a sudden been exposed publicly or not, or maybe something's been taken over or not and you control that. You have to do that with your data as well. >> So how do you guys fit into the security posture? Say it a large company that might want to implement this right away. Sounds like it's right in line with what developers want and what people want. It's easy to implement from what I see. It's about 10, 15, 20 minutes to get up and running. It's not hard. It's not a heavy lift to get in. How do you guys fit in once you get operationalized when you're successful? >> It's a lightweight, highly scalable serverless solution, it's built on Fargate containers and it goes in very easily and then, we offer either native integrations through S3 directly, or we offer APIs and the APIs are what a lot of our customers who want inline realtime scanning leverage and we also are looking at offering the actual proxy aspects. So those folks who use the S3 APIs that our native AWS, puts and gets. We can actually leverage our put and get as an endpoint and when they retrieve the file or place the file in, we'll scan it on access as well, so, it's not just a one time data arrest. It can be a data in motion as you're retrieving the information as well >> We were talking with our friends the other day and we're talking about companies like Datadog. This is the model people want, they want to come in and developers are driving a lot of the usage and operational practice so I have to ask you, this fits kind of right in there but also, you also have the corporate governance policy police that want to make sure that things are covered so, how do you balance that? Because that's an important part of this as well. >> Yeah, we're really flexible for the different ways they want to consume and and interact with it. But then also, that is such a critical piece. So many of our customers, we probably have a 50/50 breakdown of those inside the US versus those outside the US and so, you have those in California with their information protection act. You have GDPR in Europe and you have Asia having their own policies as well and the way we solve for that is we scan close to the data and we scan in the customer's account, so we don't require them to lose chain of custody and send data outside of the accoun. That is so critical to that aspect. And then we don't ask them to transfer it outside of the region, so, that's another critical piece is data residency has to be involved as part of that compliance conversation. >> How much does Cloud enable you to do this that you couldn't really do before? I mean, this really shows the advantage of natively being in the Cloud to kind of take advantage of the IaaS to SAS components to solve these problems. Share your thoughts on how this is possible. What if there was no problem, what would you do? >> It really makes it a piece of cake. As silly as that sounds, when we deploy our solution, we provide a management console for them that runs inside their own accounts. So again, no metadata or anything has to come out of it and it's all push button click and because the Cloud makes it scalable because Cloud offers infrastructure as code, we can take advantage of that and then, when they say go protect data in the Ireland region, they push a button, we stand up a stack right there in the Ireland region and scan and protect their data right there. If they say we need to be in GovCloud and operate in GovCloud East, there you go, push the button and you can behave in GovCloud East as well. >> And with server lists and the region support and all the goodness really makes a really good opportunity to really manage these Cloud native services with the data interaction so, really good prospects. Final question for you. I mean, we love the story. I think it is going to be a really changing market in this area in a big way. I think the data storage relationship relative to higher level services will be huge as Cloud native continues to drive everything. What's the future? I mean, you guys see yourself as a all encompassing, all singing and dancing storage platform or a set of services that you're going to enable developers and drive that value. Where do you see this going? >> I think that it's a mix of both. Ultimately, you saw even on Storage Day the announcement of file cash and file cash creates a new common name space across different storage platforms and so, the notion of being able to use one area to access your data and have it come from different spots is fantastic. That's been in the on-prem world for a couple of years and it's finally making it to the Cloud. I see us following that trend in helping support. We're super laser-focused on Cloud Storage itself so, EBS volumes, we keep having customers come to us and say, "I don't want to run agents in my EC2 instances. I want you to snap and scan and I don't want to, I've got all this EFS and FSX out there that we want to scan," and so, we see that all of the Cloud Storage platforms, Amazon work docs, EFS, FSX, EBS, S3, we'll all come together and we'll provide a solution that's super simple, highly scalable that can meet all the storage needs so, that's our goal right now and where we're working towards. >> Well, Cloud Storage Security, you couldn't get a more a descriptive name of what you guys are working on and again, I've had many contacts with Andy Jassy when he was running AWS and he always loves to quote "The Innovator's Dilemma," one of his teachers at Harvard Business School and we were riffing on that the other day and I want to get your thoughts. It's not so much "The Innovator's Dilemma" anymore relative to Cloud 'cause that's kind of a done deal. It's "The Integrator's Dilemma," and so, it's the integrations are so huge now. If you don't integrate the right way, that's the new dilemma. What's your reaction to that? >> A 100% agreed. It's been super interesting. Our customers have come to us for a security solution and they don't expect us to be 'cause we don't want to be either. Our own engine vendor, we're not the ones creating the engines. We are integrating other engines in and so we can provide a multi engine scan that gives you higher efficacy. So this notion of offering simple integrations without slowing down the process, that's the key factor here is what we've been after so, we are about simplifying the Cloud experience to protecting your storage and it's been so funny because I thought customers might complain that we're not a name brand engine vendor, but they love the fact that we have multiple engines in place and we're bringing that to them this higher efficacy, multi engine scan. >> I mean the developer trends can change on a dime. You make it faster, smarter, higher velocity and more protected, that's a winning formula in the Cloud so Ed, congratulations and thanks for spending the time to riff on and talk about Cloud Storage Security and congratulations on the company's success. Thanks for coming on "theCUBE." >> My pleasure, thanks a lot, John. >> Okay. This conversation here in Palo Alto, California I'm John Furrier, host of "theCUBE." Thanks for watching.

>> Announcer: "theCUBE" presents HPE Discover 2022. Brought to you by HPE. >> Welcome back to HPE Discover 2022. You're watching "theCUBE's" coverage. This is Day 2, Dave Vellante with John Furrier. Sheila Rohra is here. She's the Senior Vice President and GM of the Data Infrastructure Business at Hewlett Packard Enterprise, and of course, the storage division. And Omer Asad. Welcome back to "theCUBE", Omer. Senior Vice President and General Manager for Cloud Data Services, Hewlett Packard Enterprise storage. Guys, thanks for coming on. Good to see you. >> Thank you. Always a pleasure, man. >> Thank you. >> So Sheila, I'll start with you. Explain the difference. The Data Infrastructure Business and then Omer's Cloud Data Services. You first. >> Okay. So Data Infrastructure Business. So I'm responsible for the primary secondary storage. Basically, what you physically store, the data in a box, I actually own that. So I'm going to have Omer explain his business because he can explain it better than me. (laughing) Go ahead. >> So 100% right. So first, data infrastructure platforms, primary secondary storage. And then what I do from a cloud perspective is wrap up those things into offerings, block storage offerings, data protection offerings, and then put them on top of the GreenLake platform, which is the platform that Antonio and Fidelma talked about on main Keynote stage yesterday. That includes multi-tenancy, customer subscription management, sign on management, and then on top of that we build services. Services are cloud-like services, storage services or block service, data protection service, disaster recovery services. Those services are then launched on top of the platform. Some services like data protection services are software only. Some services are software plus hardware. And the hardware on the platform comes along from the primary storage business and we run the control plane for that block service on the GreenLake platform and that's the cloud service. >> So, I just want to clarify. So what we maybe used to know as 3PAR and Nimble and StoreOnce. Those are the products that you're responsible for? >> That is the primary storage part, right? And just to kind of show that, he and I, we do indeed work together. Right. So if you think about the 3PAR, the primary... Sorry, the Primera, the Alletras, the Nimble, right? All that, right? That's the technology that, you know, my team builds. And what Omer does with his magic is that he turns it into HPE GreenLake for storage, right? And to deliver as a service, right? And basically to create a self-service agility for the customer and also to get a very Cloud operational experience for them. >> So if I'm a customer, just so I get this right, if I'm a customer and I want Hybrid, that's what you're delivering as a Cloud service? >> Yes. >> And I don't care where the data is on-premises, in storage, or on Cloud. >> 100%. >> Is that right? >> So the way that would work is, as a customer, you would come along with the partner, because we're 100% partner-led. You'll come to the GreenLake Console. On the GreenLake Console, you will pick one of our services. Could be a data protection service, could be the block storage service. All services are hybrid in nature. Public Cloud is 100% participant in the ecosystem. You'll choose a service. Once you choose a service, you like the rate card for that service. That rate card is just like a hyperscaler rate card. IOPS, Commitment, MINCOMMIT's, whatever. Once you procure that at the price that you like with a partner, you buy the subscription. Then you go to console.greenLake.com, activate your subscription. Once the subscription is activated, if it's a service like block storage, which we talked about yesterday, service will be activated, and our supply chain will send you our platform gear, and that will get activated in your site. Two things, network cable, power cable, dial into the cloud, service gets activated, and you have a cloud control plane. The key difference to remember is that it is cloud-consumption model and cloud-operation model built in together. It is not your traditional as a service, which is just like hardware leasing. >> Yeah, yeah, yeah. >> That's a thing of the past. >> But this answers a question that I had, is how do you transfer or transform from a company that is, you know, selling boxes, of course, most of you are engineers are software engineers, I get that, to one that is selling services. And it sounds like the answer is you've organized, I know it's inside baseball here, but you organize so that you still have, you can build best of breed products and then you can package them into services. >> Omer: 100%. 100%. >> It's separate but complementary organization. >> So the simplest way to look at it would be, we have a platform side at the house that builds the persistence layers, the innovation, the file systems, the speeds and feeds, and then building on top of that, really, really resilient storage services. Then how the customer consumes those storage services, we've got tremendous feedback from our customers, is that the cloud-operational model has won. It's just a very, very simple way to operate it, right? So from a customer's perspective, we have completely abstracted away out hardware, which is in the back. It could be at their own data center, it could be at an MSP, or they could be using a public cloud region. But from an operational perspective, the customer gets a single pane of glass through our service console, whether they're operating stuff on-prem, or they're operating stuff in the public cloud. >> So they get storage no matter what? They want it in the cloud, they got it that way, and if they want it as a service, it just gets shipped. >> 100%. >> They plug it in and it auto configures. >> Omer: It's ready to go. >> That's right. And the key thing is simplicity. We want to take the headache away from our customers, we want our customers to focus on their business outcomes, and their projects, and we're simplifying it through analytics and through this unified cloud platform, right? On like how their data is managed, how they're stored, how they're secured, that's all taken care of in this operational model. >> Okay, so I have a question. So just now the edge, like take me through this. Say I'm a customer, okay I got the data saved on-premise action, cloud, love that. Great, sir. That's a value proposition. Come to HPE because we provide this easily. Yeah. But now at the edge, I want to deploy it out to some edge node. Could be a tower with Telecom, 5G or whatever, I want to box this out there, I want storage. What happens there? Just ship it out there and connects up? Does it work the same way? >> 100%. So from our infrastructure team, you'll consume one or two platforms. You'll consume either the Hyperconverged form factor, SimpliVity, or you might convert, the Converged form factor, which is proliant servers powered by Alletras. Alletra 6Ks. Either of those... But it's very different the way you would procure it. What you would procure from us is an edge service. That edge service will come configured with certain amount of compute, certain amount of storage, and a certain amount of data protection. Once you buy that on a dollars per gig per month basis, whichever rate card you prefer, storage rate card or a VMware rate card, that's all you buy. From that point on, the platform team automatically configures the back-end hardware from that attribute-based ordering and that is shipped out to your edge. Dial in the network cable, dial in the power cable, GreenLake cloud discovers it, and then you start running the- >> Self-service, configure it, it just shows up, plug it in, done. >> Omer: Self-service but partner-led. >> Yeah. >> Because we have preferred pricing for our partners. Our partners would come in, they will configure the subscriptions, and then we activate those customers, and then send out the hardware. So it's like a hyperscaler on-prem at-scale kind of a model. >> Yeah, I like it a lot. >> So you guys are in the data business. You run the data portion of Hewlett Packard Enterprise. I used to call it storage, even if we still call it storage but really, it's evolving into data. So what's your vision for the data business and your customer's data vision, if you will? How are you supporting that? >> Well, I want to kick it off, and then I'm going to have my friend, Omer, chime in. But the key thing is that what the first step is is that we have to create a unified platform, and in this case we're creating a unified cloud platform, right? Where there's a single pane of glass to manage all that data, right? And also leveraging lots of analytics and telemetry data that actually comes from our infosite, right? We use all that, we make it easy for the customer, and all they have to say, and they're basically given the answers to the test. "Hey, you know, you may want to increase your capacity. You may want to tweak your performance here." And all the customers are like, "Yes. No. Yes, no." Basically it, right? Accept and not accept, right? That's actually the easiest way. And again, as I said earlier, this frees up the bandwidth for the IT teams so then they actually focus more on the business side of the house, rather than figuring out how to actually manage every single step of the way of the data. >> Got it. >> So it's exactly what Sheila described, right? The way this strategy manifests itself across an operational roadmap for us is the ability to change from a storage vendor to a data services vendor, right? >> Sheila: Right. >> And then once we start monetizing these data services to our customers through the GreenLake platform, which gives us cloud consumption model and a cloud operational model, and then certain data services come with the platform layer, certain data services are software only. But all the services, all the data services that we provide are hybrid in nature, where we say, when you provision storage, you could provision it on-prem, or you can provision it in a hyperscaler environment. The challenge that most of our customers have come back and told us, is like, data center control planes are getting fragmented. On-premises, I mean there's no secrecy about it, right? VMware is the predominant hypervisor, and as a result of that, vCenter is the predominant configuration layer. Then there is the public cloud side, which is through either Ajour, or GCP, or AWS, being one of the largest ones out there. But when the customer is dealing with data assets, the persistence layer could be anywhere, it could be in AWS region, it could be your own data center, or it could be your MSP. But what this does is it creates an immense amount of fragmentation in the context in which the customers understand the data. Essentially, John, the customers are just trying to answer three questions: What is it that I store? How much of it do I store? Should I even be storing it in the first place? And surprisingly, those three questions just haven't been answered. And we've gotten more and more fragmented. So what we are trying to produce for our customers, is a context to ware data view, which allows the customer to understand structured and unstructured data, and the lineage of how it is stored in the organization. And essentially, the vision is around simplification and context to ware data management. One of the key things that makes that possible, is again, the age old infosite capability that we have continued to hone and develop over time, which is now up to the stage of like 12 trillion data points that are coming into the system that are not corroborated to give that back. >> And of course cost-optimizing it as well. We're up against the clock, but take us through the announcements, what's new from when we sort of last talked? I guess it was in September. >> Omer: Right. >> Right. What's new that's being announced here and, or, you know, GA? >> Right. So three major announcements that came out, because to keep on establishing the context when we were with you last time. So last time we announced GreenLake backup and recovery service. >> John: Right. >> That was VMware backup and recovery as a complete cloud, sort of SaaS control plane. No backup target management, no BDS server management, no catalog management, it's completely a SaaS service. Provide your vCenter address, boom, off you go. We do the backups, agentless, 100% dedup enabled. We have extended that into the public cloud domain. So now, we can back up AWS, EC2, and EBS instances within the same constructs. So a single catalog, single backup policy, single protection framework that protects you both in the cloud and on-prem, no fragmentation, no multiple solutions to deploy. And the second one is we've extended our Hyperconverged service to now be what we call the Hybrid Cloud On-Demand. So basically, you go to GreenLake Console control plane, and from there, you basically just start configuring virtual machines. It supports VMware and AWS at the same time. So you can provision a virtual machine on-prem, or you can provision a virtual machine in the public cloud. >> Got it. >> And, it's the same framework, the same catalog, the same inventory management system across the board. And then, lastly, we extended our block storage service to also become hybrid in nature. >> Got it. >> So you can manage on-prem and AWS, EBS assets as well. >> And Sheila, do you still make product announcements, or does Antonio not allow that? (Omer laughing) >> Well, we make product announcements, and you're going to see our product announcements actually done through the HPE GreenLake for block storage. >> Dave: Oh, okay. >> So our announcements will be coming through that, because we do want to make it as a service. Again, we want to take all of that headache of "What configuration should I buy? How do I actually deploy it? How do I...?" We really want to take that headache away. So you're going to see more feature announcements that's going to come through this. >> So feature acceleration through GreenLake will be exposed? >> Absolutely. >> This is some cool stuff going on behind the scenes. >> Oh, there's a lot good stuff. >> Hardware still matters, you know. >> Hardware still matters. >> Does it still matter? Does hardware matter? >> Hardware still matters, but what matters more is the experience, and that's actually what we want to bring to the customer. (laughing) >> John: That's good. >> Good answer. >> Omer: 100%. (laughing) >> Guys, thanks so much- >> John: Hardware matters. >> For coming on "theCUBE". Good to see you again. >> John: We got it. >> Thanks. >> And hope the experience was good for you Sheila. >> I know, I know. Thank you. >> Omer: Pleasure as always. >> All right, keep it right there. Dave Vellante and John Furrier will be back from HPE Discover 2022. You're watching "theCUBE". (soft music)

>>Hello and welcome to the AWS partners showcase season one, episode two. I'm your host of the cube John ferry. We're here with two great guests who John Kumar, CEO of and Sabina Joseph, the general manager of AWS. Welcome to the show. Welcome to welcome to the cube, >>John. Good to see you >>Again. Great to see both of you both cube. Alumna's great to see how the businesses is going, going very well. Cloud scale, continuing to dominate Columbia is doing extremely well. Tell us more about what's going on in Columbia. What's your mission? What kinds of use cases are you seeing? Napa John, that's helping you guys keep your growth trajectory and solve your customer problems. >>Yeah. Firstly, thank you, John. Thank you, Sabina. Great to be here is a backup as a service platform. That's built natively on AWS for AWS, and we do support other use cases beyond AWS. But our primary mission is to basically deliver, you know, a ransomware data protection solution, you know, on AWS for AWS customers. Right? So if we think about it, you know, one of the things that's, you know, typically holding back any company to put mission critical workloads on a fantastic platform, a public cloud platform like AWS is to make sure that the data is protected in the event of any attack. And it's also done with extreme amount of simplicity, right? So that nobody is doing the heavy lift of doing backup themselves, right? So that's what really drew me or provides. It's a service. It's a turnkey service that provides, you know, data protection on AWS, whatever. >>Well, you're a frequent cube alumni. We're always talking about the importance of that, but I want to ask you this year more than ever, you're seeing it at the center of the conversation built in from day one, you're seeing a lot more threats, certainly mentioned ransomware and more there's more and more online attacks that's impacting this particular area more than ever before. Can you comment on what your focus has been this year around that? >>Yeah, I see it. If you think about tumor's evolution, our primary mission has been to go and protect every data source, but guess what? Right with more and more move to the public cloud and you look just AWS is journey and that pioneer in public cloud going from, you know, whatever 3 billion in revenues, 10 years ago to north of 70 billion run rate today, there's so much of data that is in the public cloud and the, and the most important thing that customers need is they want to free themselves from going and protecting this data themselves. Right? And, and there's a lot of scale in these environments, right? If you look at customers running hundreds of thousands of AWS accounts across every region on AWS, and if you give them that kind of flexibility and that kind of scale, what they want is give me a turnkey solution that just allows me to go and protect all of these workloads running across all of these regions in a service that takes the data out of my accounts separately in an air gap fashion, right. And that's really what we basically provide. And that's what we focused on over the last 12 months. Right? So if you look at what we have done is we've gone after every important service on AWS TC to EBS RDS, S3, dynamo, sequel databases, and other databases running on top of BC too. So now that becomes the comprehensive set of things that somebody needs to use to really deliver an application on top of the public cloud. And that's where we want for, >>And the growth has been there and the results on Amazon because of the refactoring has been huge. Can you share any examples of some successes that you've had with, with the AWS refactoring and all that good stuff going on? >>Yeah. I mean, I think that what we have seen is, you know, customers that basically told us that before you guys existed, we had to go and build these things ourselves, right. Again, you know, they had all the, the, the blocks to go and do it themselves, but it was so much of a heavy lift to go and do it themselves. And again, they didn't want to be in a, you know, in that business. So, so what we have done essentially for, and we have, you know, we have some joint customers at a pretty massive scale that basically have said that, okay, let me just use your solution to protect my critical assets. Like, you know, things, you know, sitting in S3 and really, you know, we'll use gloomy as a, as a >>Yeah, I think that's a great example of the refactoring Sabina. Gotta, I gotta ask you, you obviously you're at the center of this. You have your hand on the wheel of the partnerships and all the innovators out there. The growth of AWS just has been spectacular because there's value being created. Again, companies are refactoring their business on the cloud and you're at the center of it. So talk about the partnership with Clooney. Can you tell us how it all started and where it's going? >>Yeah, thanks for having me here, John, and good to see you again, Fujian, if I'm not mistaken for John, we met each other at the San Francisco summit, the AWS San Francisco summit, actually I believe it was in 2016 or 2017. You can correct me if I'm wrong here, but yes, I think so. It was, it was in the 8% a month of April. I still remember it. And that's when, you know, you kind of mentioned to me about and this modern backup as a service solution that you were creating, you're still in stealth mode. So you couldn't talk a lot about it. And B started to engage deeply on the partnership, right from 2017. And initially we were kind of focused around helping Colombia build a solution using our well-architected review. And then as soon as we all came out of stealth mode, we started to engage more deeply around deeper integrations and also on go to market activities. >>As you know, AWS has a very prescriptive approach to our partnerships. So we started to work with around the five pillars of security, reliability, cost optimization, performance, and operational excellence to really help them tune the solution on AWS. And we also started to engage with our service teams and I have to thank Paul John and his team here. They really embraced those deeper and broader integrations, many services that Pooja mentioned, but also specifically want to mention S3 EBS. And our Columbia was also a launch partner for AWS outpost when AWS in fact, launched outpost. So I want to kind of commend CLU, CLU MEO, and the entire team kind of embracing this technology and innovation and this modern backup as a service approach. And also also embracing how we want to focus on the five key pillars that I mentioned. >>And that's a great example of success when you ride the wave, which I talk about the ACLU, Colombia trends in the data protection, because one of the things that you pointed out earlier is the ransomware. Okay. That's a big one, right? That's a big, hot area. How, how is the cloud, first of all, how is that going? And then how has the cloud equation changed the ransomware defense and protection piece of it? >>Yeah. Now I just, I wonder I had a little bit on what Sabina mentioned before I answered the question, John, if you don't mind. Sure. I think that collaboration is where is the reason why we are here today, right? Like if you think about it, like we were the first design partners to go and build, you know, the EBS direct API, right. And we work closely with the EBS teams, not just for the API, but the cost structure of it. How would somebody like us use it? So we are at the bleeding edge of some of these services that we are using and that has enabled us, you know, to be where we are today. So again, thank you very much to be enough for this fantastic partnership. And again, there's so much to go and do to really go and nail this in a, in a, in a, in a great way on, on the public cloud. >>So now coming back to your question, John, you know, fundamentally, if you see right, you know, what happened is when, when, when customers move to the public cloud, you know, right there, you know, the ease of use with which, you know, AWS provides these services, right? And the consumption of these services actually drives some amazing behavior, right? Where people actually want to go and build, build, build, and build. But then it comes a time where somebody comes in and says, okay, you know, are you compliant? Right. You know, do you have the right compliance in place? You have all these accounts that you have, but what is running in each of these accounts, you have visibility in those accounts. And are these accounts that the data in these accounts is this gap, right? This is getting air gap in the same region, or does it need to be across regions? >>Right. You know, I'm in the east, do I need to, you know, have an air gap in the west and so on and so forth. Right? So all of these, you know, confluence of all these things come in and by the, all these problems existed in on-premise world, they get translated in, in the public cloud, where do I need to replicate my data, doing it to back it up? Do I need air gapped in a, like an on-prem world? You had a data domain of plans, which was separate from your primary storage for a reason, same similar something similar now needs to happen here for compliance reasons and for ransomware reason. So a lot of parallels here is just that here we are, it almost feels like, you know, as they say, right, the more things changed. The more they remain the same. That's what it is in the public cloud again. >>Well, that's a good point. I mean, let's take that example of on premises versus the cloud. Also, the clouds got more scale too, by the way. So now you've got regions, this is a common problem that customers are having, you can build your own and, or use solutions, but if you don't get ahead of it, the compliance question can bite you in the, you know what, because you then got to go back and retrofit everything. So, so that's kind of what I hear a lot on my end is like, okay, I want to be compliant from day one. I want to have an answer when asked, I don't want to have to go to old techniques that don't fit the cloud. That comes up a lot. What's your answer to that? >>Yeah, no, no. We were pretty much right. I think it's like, you know, when it, when it comes to compliance and all of these things, you know, people at the end of the day are looking for that same foundation of, of things. The same questions are asked for an encryption. You know, you know, I is my data where it needs to be when it needs to be right. What is my recovery point? Objective? What is my recovery time objective? All of these things basically come together. And now, as you said, it's just the scale that you're dealing is, is extremely different in the cloud and the, and the services, right? The easier it is that, you know, it is to use these services. And especially what AWS does, it makes it so easy. So compelling that same ease of use needs to get translated with a SAS service, like what we are doing with data protection, right? That that ease of use is very important. You have to preserve that sanctity >>Sabina. Let's get back to you. You mentioned earlier about the design partner, that benefits for Colombia. Now let's take it to the next level. As customers really realize they have a problem, they need solutions and you're on the AWS side. So you gotta have the answers for the customers. You've got to put people together, make things work. There's a variety of things that you guys offer. What are some of the different facets of the ISV or the partner programs that you offer to partners like Clooney, you know, that they can benefit from? >>Absolutely John, we believe in a win-win approach to the partnerships because that's what makes partnerships durable over time. We're always striving to do better here. And we continue to broaden our investments. As you know, John, the AWS management team, right from Adam Phillipsky, our CEO down firmly believe that partners are critical to our success, our longterm success, and as partners like CLU MEO work to lean in with us with more investment resources, our technology innovation. We also ensure that we are doing our part by providing value back to Cleo about a few years ago, as you might recall, right. We really did a lot of investment in our sales team on the AWS side. Well, one of the tanks me and also our partners observed is while we were making investments in the AWS sales team, I don't think we were doing a great job at helping our partners with reaching out to those customers. >>What we call as co-sale and partners gave us feedback on this. We are very partner and customer feedback driven, and we introduced in fact, a new role called the ISP success manager, ISS, who are basically embedded in our field. And they work with partners to help them close opportunities. And also net new opportunities are we've also in 2020. I believe that re-invent, we launched the ISB accelerate program whereby we offer incentives to the AWS field team to work with our partners to close existing opportunities and also bring in net new opportunities. So all of this has led to closer collaboration in the field between both our field teams, Muir's field team and our field team, but also accelerated mutual customer wins. I'm not saying that we are doing everything great. We still have a long ways to go. And we are constantly getting feedback from cluneal and also some of our other key partners, and we'll continue to get better at it. But I think the role of the ISV success manager and also the ISP accelerate program has been key to bringing in cold cell success. >>Well, John, what's your take on, is this a good partnership for you? I mean, see, the wave of Vegas has got the growth numbers. You mentioned that, but from a partnership standpoint, you're closing business, they got scale. Is it working? How do you organize your company to take advantage of these benefits? Can you share your thoughts? >>Absolutely not. We have embraced the ecosystem wholeheartedly 100%, but if you think about it, what we have done is look at our offering on AWS marketplace. There's an example, right? We are the only company I would say in our domain, obviously that routes our entire business through AWS marketplace. Whether obviously we get a lot of organic benefit from AWS marketplace, people go and search for a solution and from your shows up, and obviously they go and onboard self onboard themselves, and guess what? We let them self onboard themselves. And we rely on AWS's billing automatically. So you don't need to talk to us. You can just get billed automatically in your AWS bill and you get your data protection solution. Or if you directly reached out to us, guess what we do. We actually route you through AWS marketplace. All the onboarding is just to one place and it's a fantastic experience. >>So we have gone like all in, on that experience and completely like, you know, internalized that that's the right way to do things. And of course, thanks to, you know, Sabina's team and the marketplace team to create that platform so that we could actually plug it into it. But that's the kind of benefits that we have that we have, you know, taken advantage of a DWI. That's one example, another example that Sabina mentioned, right, which is the whole ACE program. We put a ton of registrations on AIS and with all the wins that we get on AWS, they could broadcast it to the sellers. So that creates its own vicious cycle in terms of more coming into the pipeline and more closing in. So, so these are just two small examples, but there's other examples that we look at our recent press release, where AWS, you know, when we, when we launched yesterday data protection and backup, the GM of AWSs three supported us in the press release. So there's things like that, that it's a, it's a fantastic collaboration. That's working really well for our joint customers. Sorry. >>And tell us something about the partnership between 80 of us, including, you know, that people might not be aware of some of the things that Poojan said that they're different out there that, that are, co-selling go marketing, that you guys offer people you guys work together on. >>Yeah. The, the ISV accelerate program that was created, it was really created with partners like Klunier in mind, our SAS partners. I think that that is something very, very unique between our partnership and, you know, I, I want to double click on what Poojan said, which is riding their opportunities through marketplace, right? All of their opportunities. That is something pretty unique. They understand the richness of the platform and also how customers are procuring software today in this world. And they've embraced that. And we really appreciate that. And I want to say, you know, another thing about Qumulo is they're all in on AWS, which is another unique thing. There are not a lot of, I would say all in partnerships in my world and I manage infrastructure, business apps, applications, and industry partnerships from the Americas globally. And all of those things are very, very unique in our partnership, which has led to success. Right. We started very, very early stage when Columbia was in stealth mode in 2017 and look where we've come today. And it's really kudos to Paul, John and his entire team for believing in the partnership for leaning in with us and for placing that trust with us. >>Awesome. Pooja, any final words you'd like to share for folks out there about the conversation and what's going on in Columbia? >>Yeah, no, absolutely. You know, as I said, I think we have been fortunate to be very early adopters of all these technologies and go and really build what a true cloud native solution has to be. Right. And, and again, right, you know, this is what customers are really looking for. And people are looking for, you know, at least on the data protection side, you know, ransomware air gap solution, people are looking for a solution natively built on the cloud because that's the only way a solution can deliver something at the scale and the cost structure that is needed to have, you know, a data protection solution in the public cloud. So, so this has been just a fantastic thing end to end, you know, for us overall. And we really look forward to, you know, going, you know, doing much more with AWS as we essentially go and scale, >>I have to ask, but before we, before we go, cause you're the CEO of the company and founder having all that backend infrastructure from Amazon, just on the resources, great. It creates a market for your product, but also the sales piece, you know, they got the marketplace, you mentioned, that's a big expense that you don't have to carry, you know, and you get revenue and top line. I mean, that's an impact for startups out there and growing companies. That's a pretty big deal. What's your, what's your advice to folks out there who are trying to think about the buy versus use the leverage of the, of the marketplace, which is, which is at large scale, because as a CEO, you're, you've got to make these decisions. What's your opinion on that? >>It's not, it's not as, as easy as I make it sound to do your own part. You know, AWS is, is, is, is huge, right? It's huge. And so we have to do our part to educate everybody within the, you know, even the AWS seller base to make sure that they internalize the fact that this is the right solution for the customers, for our joint customers, right? So we have to do that all day long. So there's no running away the no shortcut to everything, but obviously AWS does its part to make it very, as easy as possible, but there's a lot of heavy lifting we still have to do. And I think that'll only become easier and easier over the next few years >>And Sabina your takeout at AVS. You've got a great job. You were with all the hot growth companies. This is the big wave we're on right now with the cloud next generation clouds here, a lot of opportunities. >>Absolutely. And it's, and it's thanks to Pooja and, and partners like Lumeo that really understand what it takes to build a cloud native solution because it's part of it is building. And part of it is the co-selling go-to-market engine and embracing both of that is critical to success. >>Well, thank you both for coming on this journey here on the cube, as part of the showcase, push on. Great to see you to being a great to see you as well. And thanks for sharing that insight. Appreciate it. >>Thank you very much. >>Okay. AWS partners showcase speeding innovation with AWS. I'm John Ford, your host of the cube. Thanks for watching.

>>Hello, everyone. Welcome to the cubes presentation of the AWS partner showcase. This is season one, episode two. I'm your host, John furry with the cube. I'm joined by two cube alumni as Andy Langston, SVP and GM at Veem and Sabina Joseph, the general manager of technology partners at AWS. We're here talking about speeding the innovation with AWS. Welcome to the show. >>Ready to meet you >>And good to see you, Andy again. >>Great to have you guys back on. I hope you guys are doing well. Great to see both of you Veem. Obviously we've been covering you guys for a long time. You got your VIMANA event coming up in person, which is great. Congrats on the continued success of the company and the product you guys have always been all in on AWS. We've been covering for many, many years. Andy, what's the innovation going on now at Veem? Lots of lots happening, lots going on. What's the new innovation. >>Well, I think, you know, clearly people are in, you know, when we talk to people they're interested in, in ransomware, so ransomware protection, we they're interested in a hybrid cloud hybrid. Um, you know, AWS in particular, we get a lot of interest there. Um, clearly modern data protection, uh, what we're doing in office 365, people are looking at all those things >>And what's the, the platform, uh, approach that you guys have with AWS. You guys have a broad range. It's not just the classic. I call it the green classic solution. That's also a good product. What's some of the new platform advantages you guys got going on with the cloud native with AWS. >>Well, you know, look we are, our strategy is to protect as many AWS services as possible, you know, and, and, you know, from the ECE to EBS, S3, RDS, uh, VMC, and many of the services that they're coming out with. And in many times they come to us and say, Hey, you know, these are important to us. We'd like you to, to support these. So clearly we're, um, we're focused on those, uh, Kubernetes workloads is, is a newer set of workloads on AWS. That we're a very interested, we made an acquisition and have a product called, uh, Kasten that we've been investing in and working with AWS with their, uh, uh, EKS anywhere. So very excited. >>Great. So being on the partnership, you guys, it's growing a lot's going on. Can you tell us more about how Veeam and abs AWS are jointly helping customers? >>Yeah. As, um, as both of, you know, right. Data is exploding. And, uh, that means, you know, we have to keep backing up this data and finding new ways to back up this data because people are stepping away from the traditional backup methods, tape libraries, secondary storage sites and things like that. And they're backing up data into the cloud. And we AWS offers a number of different storage services, data transfer methods and networking solutions, which provide unmatched your ability, reliability, security. And of course, uh, AWS and Veem have been partnering together enough for quite a number of years and the cost effective. And so you mentioned that Veem has on AWS really enables customers to have offsite storage solutions, providing that physical separation between their on premises, primary data, and also utilizing the pay as you go cloud economics. So we have a great collaboration and, you know, beam has a great solution on AWS and they're constantly innovating and providing capabilities for our customers. Just like Andy said, providing as many capabilities for our services to back up, >>Andy, the volume of data I'll say is always the story. Every year, the volume is tsunami of data. It's getting worse it's every day. Um, and as you got more cloud scale, you guys have been doing a lot integration. You guys always have, you have demanding customers, you have a lot of customers actually. So as you leverage Amazon for data protection, the security conversation is front and center these days. Can you give us an update on how you guys are doing, uh, the data protection security in the cloud with AWS? That's, that's, um, that's hot with your customers, >>You know, it's a great, it's a great comment. You know, you've talked about a lot of customers. Veem has over 400,000 customers now it's, it's truly extraordinary when you think about the size and scope and scale. And if you think, uh, my belief is a majority, almost all of them will tear up two and move their data up into the cloud at some point in our, in the next few years. And so we've just, I think we've described the surface and we're moving hack, you know, hundreds of petabytes or more per year up to the cloud at the same time when I make customer executive calls. It's kind of interesting. A lot of times you think they're going to want to talk about backup and disaster recovery. They want to talk about security. And when this first started happening, I thought, Hey, why don't you talk to your security vendor now? >>And what I realized was that data protection is front and center because of the, we just, we just published a study where a number jumped out at me, 71% of the thousands of people that responded said that they had already been a victim of, or had had a ransomware attack. It's a staggering number. And, um, so, you know, when we look at our relationship with Amazon and we look at the integration we've done around what we call cloud during that's moving, are moving data up to object storage. AWS has a capability called immutable data sets. And so that allows you affords you some great protection against ransomware as an example. And that's one of the areas that we're investing in very heavily. And by the way, our mutual customers are backing up and restoring with Veem and we're doing it on AWS and, and, uh, the data volumes are exploding, I think, because of that. Yeah. >>You know, it's interesting. And you made me have a throwback for, you know, 10 years ago, we used to talk about backup and recovery. And you know, the big thing back then was, was the conversation was don't think of backup as a, as a last minute thing, think of it at the front end, it was always kind of an afterthought and a, of the it decision makers. And you mentioned that security comment about call your security vendor. It's almost the scripts has flipped backup and recovery is the security solution. And so it's not, it's not an afterthought. This is 10 years ago. It was the primary message. It's the primary thought. So when you talk about automated tiering, that's kind of a networking thing. It's like, policy-based hearing. I mean, I mean, if you go back 10 years and we're talking, policy-based hearing, you were like, what? So this is a really different dynamic. And I want you guys to comment because this is the, this is the market right now. This is with the flip, the script has flipped. >>Yeah. Sabina. What do you, what, what do you from y'all's perspective kind of in, in your technology, partnerships, storage vendors, Veem security, what, what do you w what do you see? >>Well, I think that there is an interplay here because I think customers are looking at various ways, right? When I look at those five cybersecurity framework, right? First is identifying what you need to protect, protecting it. And then that's a very important step of, out of those five steps is recovery, right? How do you get your business back to normal? But you cannot do that if you are not protecting and backing up your data. And that's where our partnership comes in. Right? So I believe that all of those five stages in the NIST cybersecurity framework kind of go together and be in place nicely into the very critical phase of recovery. Would you agree, Andy? >>I would. You know, and, and I look at, um, you know, when you're doing a recovery and your gut, your secure backups and AWS, it's, it's like your last line of defense, you know, beam and AWS deliver a mutable backups and has three tiers through S3 object lock integration. And I think that's, that's pretty much, you know, even if a ransomware attack is successful, we can, we can ensure that the backup data hadn't been changed and encrypted or deleted. And, uh, that's pretty exciting, you know, for customers and prospects, they're really worried about this. And I think the teamwork and the, the, the partnership between the two companies to build a solution like this is pretty awesome. >>Yeah. Let me, let me just double, double click on that for a second. You mentioned it got a lot of customers. Ransomware does not discriminate with the size of the company. It could be, it could be a hospital school. It could be a big company. Ransomware is bad, and we see that, and it's a great conversation. And how do you take that solution out to the customers? You got hundreds of thousands of customers. So Sabine, I guess the question is, how is this 80 of us in Veem work together? There's this channel first concept you guys are talking about, tell us about how you guys work together, because there's millions of customers who want this, and you guys actually have hundreds of thousands of customers that Veem, how do you get the customers to leverage that, the relationship and what can you bring to them? >>Yeah, I'll give you like four numbers, right? So AWS has millions of customers and we have, um, hundred thousand partners across 150 countries. Now Veem has, as Andy mentioned, right, has over 400,000 customers and 35,000 partners worldwide. So somewhere in these four numbers, we all intersect both of us intersect both on those customers and also on those partners. And one of the initiatives that my team is heavily focused on is triangulating between the partners that Veeam has. We have, and also our technology partnership. And how can we provide value to our customers by bringing together these partners together with AWS Veeam and Veeam is a V it's a hundred percent channel driven business, and they know how to do this. That is why we are heavily partnered with them to see what we can do for our customers through our mutual partner. >>And he wants you to weigh in here, you know, the channel business, it's gotta be easy, it's got to add value. And I got to wrap services around it. That's what partners love. Well, how does this work? How does that work? >>Well, I, I think to extend beyond what, what did take, what Sabina had said is, you know, we have kind of been subsetted. Our partners are the ones that, that do business with AWS and, and which is a exploding number of partners. And so they have a relationship database. We have a relationship at S and we have this solution set that have, are of interest to our customers through these partners. And AWS has customers through these partners. And so a lot of times we'll share, um, information and customers, uh, information on, around, um, how we can kind of go to these customers who are both AWS customers and Veem customers and market, this joint solution protect them from ransomware. >>And how's it been going so far? What's your, what's your assessment? >>It's been fantastic. I think the, I think one of the, the, the real proof points is that we've moved, uh, over a half a petabyte of data, you know, uh, recently up into their cloud. And, uh, you know, that says that people not only are using the solution, but they're, uh, they're actually delivering on it. >>Well, why got you here, Andy, I want to ask you for the, all the people watching the customers, what's the biggest change that's happening in this market right now. Again, I love this shift that we're seeing backup and recovery. Isn't a point solution anymore. It's the solution it's baked in, and everyone's talking about this, it's integrated in, it's not, it's, it's totally front and center. What's the big change that customers should be thinking about now as they move forward. And, uh, obviously ransomware is still front and center. That's not going away anytime soon. What's the big thing to focus on for customers? >>Well, I think, you know, I always say, you know, listen to the customer and focus on what their specific needs are, right? You can assume, obviously in the business war and everybody, everybody has a backup solution. And, uh, so you're not trying to create a market there, but like I said, you know, people are very focused on security. They're focused on cost, they're focus on skillset or lack of skill sets, right? I mean, we have a shortage of skills in the industry. So we try to make our products easy to use. We try to work with our partners, putting AWS to deliver the best solution we can for our customers. And, uh, you know, I think we have the broadest invest, you know, ransomware protection, uh, and recovery in the storage space. And so we're very focused on that, leveraging all of our technologies across the platforms, physical, virtual Kubernetes, uh, type environments. >>And you have this and you get the beam on event coming up and that's going to be good in person. Right. That's a confirmed, >>It's a, it's a, it's a hybrid yet. In-person and virtual. >>Awesome. Great to see you guys in person. So being a, for the folks, watching the Amazon partnerships, as you guys scale up these, these partnerships and take it the next level, what's your, what's your closing comment. Yes. >>Yeah. I also want to say, write something that I should mention, right. We miss also invested in AWS marketplace. So it's not just the direct consulting partners and the partners that I mentioned, the a hundred thousand and 35,000, right. They, customers can also purchase beam on AWS marketplace through consulting partner, private offers. And that's why Viva's embraced many of these aspects to try to help our customers and continue to grow that 400,000 customer base, which is a pretty phenomenal number. >>Yeah. I've always been impressed with beam's customer base and they've got a very loyal base as well. I point that out and give props to the VM team. Andy closing comments for you, the V natives relationship, how would you summarize that? >>I'd say it's fantastic. You know, years ago it started as just a normal technology partnership. You know, now we're an advanced technology partner with storage competency, numerous programs like APN, uh, customer engagement. We're a marketplace seller. And I would say that it's not only that, but, but customers can take advantages of their, um, EDP with AWS to purchase on the marketplace and get credits against that. And our partners can as well. That's a, that's a very important thing because we're seeing more and more interest in that today. Uh, we're a public sector partner with them. We're an ISV accelerate SAS revenue recognition program. We're, we're, uh, I think we're checking a lot of boxes, but really taking advantage of it. The last thing I would say is, uh, I've known Sabina for quite a few years now. And I think it's the people relationships in the two companies that make this work. >>We have a lot of people, a lot smarter than me on the, on the speeds and feeds here. But at the end of the day, um, Sabina has a team of people that work with us on a, on a, almost a daily basis to solve customer problems. Right. We get people calling in all the time. How do I make Veem work on AWS? How do I get AWS solutions to work with theme? And our job is to make it as easy as possible because we both believe, uh, that customers, they say customer first. I always say, customer always are always right, but, but, but, but you know, at the end of the day, that's what makes this >>Yeah. Customer is always right. Customer obsession, working backwards from the customer fucking customer first Sabina. This is really interesting. This is a good point. I just come quick, go back to you real quick. This integration of relationships and also cloud technology integration is a big theme this year, post re-invent. Your thoughts >>Absolutely means, um, uh, to be candid. Uh, one of the goals that me and my team take is how do we bring technology partners together to add more value to our customers in end to end solutions, along with technology partners and consulting partners. So that is a huge focus for us because we need to do that in order to scale, not just for each other, but also for our customers and bring that, bring together meaningful, comprehensive end to end solutions. >>That's awesome. Andy, great to see you. We'll see at Veem on as well, coming up for the Veem show and your conference. You've been conference hybrid conference in person and virtual and digital to be in a great to see you again. Thanks for sharing all the great updates. And this is the season two. It's all about the data and the innovations with AWS. I'm John for your host of the cube season one episode, two of the AWS partner showcase. Thanks for watching.

>> From theCUBE studios in Palo Alto, in Boston, bringing you data driven insights from theCUBE and ETR. This is Breaking Analysis with Dave Vollante. >> The rise of Kubernetes came about through a combination of forces that were, in hindsight, quite a long shot. Amazon's dominance created momentum for Cloud native application development, and the need for newer and simpler experiences, beyond just easily spinning up computer as a service. This wave crashed into innovations from a startup named Docker, and a reluctant competitor in Google, that needed a way to change the game on Amazon and the Cloud. Now, add in the effort of Red Hat, which needed a new path beyond Enterprise Linux, and oh, by the way, it was just about to commit to a path of a Kubernetes alternative for OpenShift and figure out a governance structure to hurt all the cats and the ecosystem and you get the remarkable ascendancy of Kubernetes. Hello and welcome to this week's Wikibon CUBE Insights powered by ETR. In this breaking analysis, we tapped the back stories of a new documentary that explains the improbable events that led to the creation of Kubernetes. We'll share some new survey data from ETR and commentary from the many early the innovators who came on theCUBE during the exciting period since the founding of Docker in 2013, which marked a new era in computing, because we're talking about Kubernetes and developers today, the hoodie is on. And there's a new two part documentary that I just referenced, it's out and it was produced by Honeypot on Kubernetes, part one and part two, tells a story of how Kubernetes came to prominence and many of the players that made it happen. Now, a lot of these players, including Tim Hawkin Kelsey Hightower, Craig McLuckie, Joe Beda, Brian Grant Solomon Hykes, Jerry Chen and others came on theCUBE during formative years of containers going mainstream and the rise of Kubernetes. John Furrier and Stu Miniman were at the many shows we covered back then and they unpacked what was happening at the time. We'll share the commentary from the guests that they interviewed and try to add some context. Now let's start with the concept of developer defined structure, DDI. Jerry Chen was at VMware and he could see the trends that were evolving. He left VMware to become a venture capitalist at Greylock. Docker was his first investment. And he saw the future this way. >> What happens is when you define infrastructure software you can program it. You make it portable. And that the beauty of this cloud wave what I call DDI's. Now, to your point is every piece of infrastructure from storage, networking, to compute has an API, right? And, and AWS there was an early trend where S3, EBS, EC2 had API. >> As building blocks too. >> As building blocks, exactly. >> Not monolithic. >> Monolithic building blocks every little building bone block has it own API and just like Docker really is the API for this unit of the cloud enables developers to define how they want to build their applications, how to network them know as Wills talked about, and how you want to secure them and how you want to store them. And so the beauty of this generation is now developers are determining how apps are built, not just at the, you know, end user, you know, iPhone app layer the data layer, the storage layer, the networking layer. So every single level is being disrupted by this concept of a DDI and where, how you build use and actually purchase IT has changed. And you're seeing the incumbent vendors like Oracle, VMware Microsoft try to react but you're seeing a whole new generation startup. >> Now what Jerry was explaining is that this new abstraction layer that was being built here's some ETR data that quantifies that and shows where we are today. The chart shows net score or spending momentum on the vertical axis and market share which represents the pervasiveness in the survey set. So as Jerry and the innovators who created Docker saw the cloud was becoming prominent and you can see it still has spending velocity that's elevated above that 40% red line which is kind of a magic mark of momentum. And of course, it's very prominent on the X axis as well. And you see the low level infrastructure virtualization and that even floats above servers and storage and networking right. Back in 2013 the conversation with VMware. And by the way, I remember having this conversation deeply at the time with Chad Sakac was we're going to make this low level infrastructure invisible, and we intend to make virtualization invisible, IE simplified. And so, you see above the two arrows there related to containers, container orchestration and container platforms, which are abstraction layers and services above the underlying VMs and hardware. And you can see the momentum that they have right there with the cloud and AI and RPA. So you had these forces that Jerry described that were taking shape, and this picture kind of summarizes how they came together to form Kubernetes. And the upper left, Of course you see AWS and we inserted a picture from a post we did, right after the first reinvent in 2012, it was obvious to us at the time that the cloud gorilla was AWS and had all this momentum. Now, Solomon Hykes, the founder of Docker, you see there in the upper right. He saw the need to simplify the packaging of applications for cloud developers. Here's how he described it. Back in 2014 in theCUBE with John Furrier >> Container is a unit of deployment, right? It's the format in which you package your application all the files, all the executables libraries all the dependencies in one thing that you can move to any server and deploy in a repeatable way. So it's similar to how you would run an iOS app on an iPhone, for example. >> A Docker at the time was a 30% company and it just changed its name from .cloud. And back to the diagram you have Google with a red question mark. So why would you need more than what Docker had created. Craig McLuckie, who was a product manager at Google back then explains the need for yet another abstraction. >> We created the strong separation between infrastructure operations and application operations. And so, Docker has created a portable framework to take it, basically a binary and run it anywhere which is an amazing capability, but that's not enough. You also need to be able to manage that with a framework that can run anywhere. And so, the union of Docker and Kubernetes provides this framework where you're completely abstracted from the underlying infrastructure. You could use VMware, you could use Red Hat open stack deployment. You could run on another major cloud provider like rec. >> Now Google had this huge cloud infrastructure but no commercial cloud business compete with AWS. At least not one that was taken seriously at the time. So it needed a way to change the game. And it had this thing called Google Borg, which is a container management system and scheduler and Google looked at what was happening with virtualization and said, you know, we obviously could do better Joe Beda, who was with Google at the time explains their mindset going back to the beginning. >> Craig and I started up Google compute engine VM as a service. And the odd thing to recognize is that, nobody who had been in Google for a long time thought that there was anything to this VM stuff, right? Cause Google had been on containers for so long. That was their mindset board was the way that stuff was actually deployed. So, you know, my boss at the time, who's now at Cloudera booted up a VM for the first time, and anybody in the outside world be like, Hey, that's really cool. And his response was like, well now what? Right. You're sitting at a prompt. Like that's not super interesting. How do I run my app? Right. Which is, that's what everybody's been struggling with, with cloud is not how do I get a VM up? How do I actually run my code? >> Okay. So Google never really did virtualization. They were looking at the market and said, okay what can we do to make Google relevant in cloud. Here's Eric Brewer from Google. Talking on theCUBE about Google's thought process at the time. >> One interest things about Google is it essentially makes no use of virtual machines internally. And that's because Google started in 1998 which is the same year that VMware started was kind of brought the modern virtual machine to bear. And so Google infrastructure tends to be built really on kind of classic Unix processes and communication. And so scaling that up, you get a system that works a lot with just processes and containers. So kind of when I saw containers come along with Docker, we said, well, that's a good model for us. And we can take what we know internally which was called Borg a big scheduler. And we can turn that into Kubernetes and we'll open source it. And suddenly we have kind of a cloud version of Google that works the way we would like it to work. >> Now, Eric Brewer gave us the bumper sticker version of the story there. What he reveals in the documentary that I referenced earlier is that initially Google was like, why would we open source our secret sauce to help competitors? So folks like Tim Hockin and Brian Grant who were on the original Kubernetes team, went to management and pressed hard to convince them to bless open sourcing Kubernetes. Here's Hockin's explanation. >> When Docker landed, we saw the community building and building and building. I mean, that was a snowball of its own, right? And as it caught on we realized we know what this is going to we know once you embrace the Docker mindset that you very quickly need something to manage all of your Docker nodes, once you get beyond two or three of them, and we know how to build that, right? We got a ton of experience here. Like we went to our leadership and said, you know, please this is going to happen with us or without us. And I think it, the world would be better if we helped. >> So the open source strategy became more compelling as they studied the problem because it gave Google a way to neutralize AWS's advantage because with containers you could develop on AWS for example, and then run the application anywhere like Google's cloud. So it not only gave developers a path off of AWS. If Google could develop a strong service on GCP they could monetize that play. Now, focus your attention back to the diagram which shows this smiling, Alex Polvi from Core OS which was acquired by Red Hat in 2018. And he saw the need to bring Linux into the cloud. I mean, after all Linux was powering the internet it was the OS for enterprise apps. And he saw the need to extend its path into the cloud. Now here's how he described it at an OpenStack event in 2015. >> Similar to what happened with Linux. Like yes, there is still need for Linux and Windows and other OSs out there. But by and large on production, web infrastructure it's all Linux now. And you were able to get onto one stack. And how were you able to do that? It was, it was by having a truly open consistent API and a commitment into not breaking APIs and, so on. That allowed Linux to really become ubiquitous in the data center. Yes, there are other OSs, but Linux buy in large for production infrastructure, what is being used. And I think you'll see a similar phenomenon happen for this next level up cause we're treating the whole data center as a computer instead of trading one in visual instance is just the computer. And that's the stuff that Kubernetes to me and someone is doing. And I think there will be one that shakes out over time and we believe that'll be Kubernetes. >> So Alex saw the need for a dominant container orchestration platform. And you heard him, they made the right bet. It would be Kubernetes. Now Red Hat, Red Hat is been around since 1993. So it has a lot of on-prem. So it needed a future path to the cloud. So they rang up Google and said, hey. What do you guys have going on in this space? So Google, was kind of non-committal, but it did expose that they were thinking about doing something that was you know, pre Kubernetes. It was before it was called Kubernetes. But hey, we have this thing and we're thinking about open sourcing it, but Google's internal debates, and you know, some of the arm twisting from the engine engineers, it was taking too long. So Red Hat said, well, screw it. We got to move forward with OpenShift. So we'll do what Apple and Airbnb and Heroku are doing and we'll build on an alternative. And so they were ready to go with Mesos which was very much more sophisticated than Kubernetes at the time and much more mature, but then Google the last minute said, hey, let's do this. So Clayton Coleman with Red Hat, he was an architect. And he leaned in right away. He was one of the first outside committers outside of Google. But you still led these competing forces in the market. And internally there were debates. Do we go with simplicity or do we go with system scale? And Hen Goldberg from Google explains why they focus first on simplicity in getting that right. >> We had to defend of why we are only supporting 100 nodes in the first release of Kubernetes. And they explained that they know how to build for scale. They've done that. They know how to do it, but realistically most of users don't need large clusters. So why create this complexity? >> So Goldberg explains that rather than competing right away with say Mesos or Docker swarm, which were far more baked they made the bet to keep it simple and go for adoption and ubiquity, which obviously turned out to be the right choice. But the last piece of the puzzle was governance. Now Google promised to open source Kubernetes but when it started to open up to contributors outside of Google, the code was still controlled by Google and developers had to sign Google paper that said Google could still do whatever it wanted. It could sub license, et cetera. So Google had to pass the Baton to an independent entity and that's how CNCF was started. Kubernetes was its first project. And let's listen to Chris Aniszczyk of the CNCF explain >> CNCF is all about providing a neutral home for cloud native technology. And, you know, it's been about almost two years since our first board meeting. And the idea was, you know there's a certain set of technology out there, you know that are essentially microservice based that like live in containers that are essentially orchestrated by some process, right? That's essentially what we mean when we say cloud native right. And CNCF was seated with Kubernetes as its first project. And you know, as, as we've seen over the last couple years Kubernetes has grown, you know, quite well they have a large community a diverse con you know, contributor base and have done, you know, kind of extremely well. They're one of actually the fastest, you know highest velocity, open source projects out there, maybe. >> Okay. So this is how we got to where we are today. This ETR data shows container orchestration offerings. It's the same X Y graph that we showed earlier. And you can see where Kubernetes lands not we're standing that Kubernetes not a company but respondents, you know, they doing Kubernetes. They maybe don't know, you know, whose platform and it's hard with the ETR taxon economy as a fuzzy and survey data because Kubernetes is increasingly becoming embedded into cloud platforms. And IT pros, they may not even know which one specifically. And so the reason we've linked these two platforms Kubernetes and Red Hat OpenShift is because OpenShift right now is a dominant revenue player in the space and is increasingly popular PaaS layer. Yeah. You could download Kubernetes and do what you want with it. But if you're really building enterprise apps you're going to need support. And that's where OpenShift comes in. And there's not much data on this but we did find this chart from AMDA which show was the container software market, whatever that really is. And Red Hat has got 50% of it. This is revenue. And, you know, we know the muscle of IBM is behind OpenShift. So there's really not hard to believe. Now we've got some other data points that show how Kubernetes is becoming less visible and more embedded under of the hood. If you will, as this chart shows this is data from CNCF's annual survey they had 1800 respondents here, and the data showed that 79% of respondents use certified Kubernetes hosted platforms. Amazon elastic container service for Kubernetes was the most prominent 39% followed by Azure Kubernetes service at 23% in Azure AKS engine at 17%. With Google's GKE, Google Kubernetes engine behind those three. Now. You have to ask, okay, Google. Google's management Initially they had concerns. You know, why are we open sourcing such a key technology? And the premise was, it would level the playing field. And for sure it has, but you have to ask has it driven the monetization Google was after? And I would've to say no, it probably didn't. But think about where Google would've been. If it hadn't open source Kubernetes how relevant would it be in the cloud discussion. Despite its distant third position behind AWS and Microsoft or even fourth, if you include Alibaba without Kubernetes Google probably would be much less prominent or possibly even irrelevant in cloud, enterprise cloud. Okay. Let's wrap up with some comments on the state of Kubernetes and maybe a thought or two about, you know, where we're headed. So look, no shocker Kubernetes for all its improbable beginning has gone mainstream in the past year or so. We're seeing much more maturity and support for state full workloads and big ecosystem support with respect to better security and continued simplification. But you know, it's still pretty complex. It's getting better, but it's not VMware level of maturity. For example, of course. Now adoption has always been strong for Kubernetes, for cloud native companies who start with containers on day one, but we're seeing many more. IT organizations adopting Kubernetes as it matures. It's interesting, you know, Docker set out to be the system of the cloud and Kubernetes has really kind of become that. Docker desktop is where Docker's action really is. That's where Docker is thriving. It sold off Docker swarm to Mirantis has made some tweaks. Docker has made some tweaks to its licensing model to be able to continue to evolve its its business. To hear more about that at DockerCon. And as we said, years ago we expected Kubernetes to become less visible Stu Miniman and I talked about this in one of our predictions post and really become more embedded into other platforms. And that's exactly what's happening here but it's still complicated. Remember, remember the... Go back to the early and mid cycle of VMware understanding things like application performance you needed folks in lab coats to really remediate problems and dig in and peel the onion and scale the system you know, and in some ways you're seeing that dynamic repeated with Kubernetes, security performance scale recovery, when something goes wrong all are made more difficult by the rapid pace at which the ecosystem is evolving Kubernetes. But it's definitely headed in the right direction. So what's next for Kubernetes we would expect further simplification and you're going to see more abstractions. We live in this world of almost perpetual abstractions. Now, as Kubernetes improves support from multi cluster it will be begin to treat those clusters as a unified group. So kind of abstracting multiple clusters and treating them as, as one to be managed together. And this is going to create a lot of ecosystem focus on scaling globally. Okay, once you do that, you're going to have to worry about latency and then you're going to have to keep pace with security as you expand the, the threat area. And then of course recovery what happens when something goes wrong, more complexity, the harder it is to recover and that's going to require new services to share resources across clusters. So look for that. You also should expect more automation. It's going to be driven by the host cloud providers as Kubernetes supports more state full applications and begins to extend its cluster management. Cloud providers will inject as much automation as possible into the system. Now and finally, as these capabilities mature we would expect to see better support for data intensive workloads like, AI and Machine learning and inference. Schedule with these workloads becomes harder because they're so resource intensive and performance management becomes more complex. So that's going to have to evolve. I mean, frankly, many of the things that Kubernetes team way back when, you know they back burn it early on, for example, you saw in Docker swarm or Mesos they're going to start to enter the scene now with Kubernetes as they start to sort of prioritize some of those more complex functions. Now, the last thing I'll ask you to think about is what's next beyond Kubernetes, you know this isn't it right with serverless and IOT in the edge and new data, heavy workloads there's something that's going to disrupt Kubernetes. So in that, by the way, in that CNCF survey nearly 40% of respondents were using serverless and that's going to keep growing. So how is that going to change the development model? You know, Andy Jassy once famously said that if they had to start over with Amazon retail, they'd start with serverless. So let's keep an eye on the horizon to see what's coming next. All right, that's it for now. I want to thank my colleagues, Stephanie Chan who helped research this week's topics and Alex Myerson on the production team, who also manages the breaking analysis podcast, Kristin Martin and Cheryl Knight help get the word out on socials, so thanks to all of you. Remember these episodes, they're all available as podcasts wherever you listen, just search breaking analysis podcast. Don't forget to check out ETR website @etr.ai. We'll also publish. We publish a full report every week on wikibon.com and Silicon angle.com. You can get in touch with me, email me directly david.villane@Siliconangle.com or DM me at D Vollante. You can comment on our LinkedIn post. This is Dave Vollante for theCUBE insights powered by ETR. Have a great week, everybody. Thanks for watching. Stay safe, be well. And we'll see you next time. (upbeat music)

(bright upbeat music) >> Welcome back to theCube's coverage of AWS re:Invent 2021. This is "theCube". We go out to the events. We extract the signal from the noise. We're here at a live event, hybrid event, two sets. We had two remote studios prior to the event, over 100 interviews. Really excited to have George Elissaios here. He's the director of product management for EC2 Edge, really interesting topic at AWS. George, great to see you. Thanks for coming on. >> Yeah, great to be here. Thanks for having me. >> So, everybody's talking about Edge, IoT, EC2. What's the scope of your portfolio, your responsibility? >> Yeah, well, our vision here at AWS is to really bring the power of the AWS platform wherever customers need it. AWS wherever our customers want it is our long-term vision. And we have a bunch of products in this space that help us do that and help us enable our customers whatever their use case is. So we have things like Wavelength. I know we talked about Wavelength before here in "theCube", where we bring full AWS service at the edge of the 5G network, so with 5G edge computing in partnership with telcos worldwide, our partnership with Verizon in the US has been flourishing. We're up to, I think, 15 or more Wavelength zones right now in many of the major cities in the US, but also in Japan and Korea, and in Europe with Vodafone. So that's one of the portfolio kind of offerings. And that helps you as a customer of AWS if you want to have the best latency to mobile devices, whether they are sensors, or mobile phones, or what have you. But we're also feeling out that Edge portfolio with local zones. Earlier today in Werner's keynote, we announced that we're going to launch another 30 local zones in 20 new countries, everywhere from South America, Africa, Asia, Australia, and Europe, obviously. So a lot of expansion there. Very excited about that. And that is kind of a similar offering, but it basically brings you closer to customers in metropolitan areas over the internet. >> So, Wavelength's a big feature. George, I want to get just to touch on it because I think latency comes up a lot in Edge conversations, low latency issues, whether it's cars, factories. You guys gave a demo yesterday to the press corps in the press room, I was there, where you had someone in San Francisco from the Opera and someone in person here in Vegas, and you had 13 milliseconds going back and forth demoing, real time- >> Collaboration. >> The benefit of low latency in remote. It wasn't next door. It was San Francisco. This is kind of the purpose of what Edge is about. Can you explain what that means, that demo, why it was important, and what you were trying to show, and how does it mean for the Edge? >> So there is multiple use cases. One of them is human collaboration, right? Like, we spent the last two years of our lives over conferences and kind of like the teleconferences, and trying to talk over each other and unmute ourselves desperately. But existing solutions kind of work, generally, for most of the things that we do, but when it comes to music collaboration where milliseconds matter, it's a lot harder with existing solutions to get artists to collaborate when they're hundreds of miles away. Last night, we saw a really inspiring demo, I think, of how two top tier musicians, one located in San Francisco and one located in Vegas, can collaborate in opera, which is one of the most precise art forms in the music world. There are no beats in opera to kind of synchronize, so you really need to play off each other, right? So we provided a latency between them of less than 30 milliseconds, which translates, if you're thinking about audio or if you're thinking about the speed of sound, that's like being in the same stage. And that was very inspiring. But there's also a lot of use cases that are machine to machine communications, where even lower latencies matter, and we can think of latencies down to one millisecond, like single digit milliseconds when it comes to, for example, vehicles or robots, and things like that. So we're, with our products, we're enabling customers to drive down that latency, but also the jitter, which is the variation of latency. Especially in human communications, that is almost more important than latency itself. Your mind can adapt to latency, and you can start predicting what's going to happen, but if I'm keep changing that for you, that becomes even harder. >> Well, this is what I want to get to because you got outcomes and applications like this opera example. That's an application, I guess. So working backwards from the application, that's one thing, but now people are really starting to trying to figure out, "What is the Edge?" So I have to ask you, what is AWS's Edge? Is it Outpost, Wavelength? What do people buy to make the Edge work? >> Well, for us, is providing a breadth of services that our customers can either use holistically or combine multiple of those. So a really good example, for example, is DISH Wireless. I'm sure you know we're building with DISH the first in the world mobile network, 5G mobile network fully on cloud, right? So these combines Outposts and combines local zones in order to distribute the 5G network across nationwide. And different parts of their applications live in different edges, right? The local zone, the Outputs, and the region itself. So we have our customers... You know, I talked about how local zones is going to be, you know, in total, 45 cities in the world, right? We're already in 15 in the U.S. We're going to do another 30. But customers might still come, and say, "Oh, why are you not," you know, "in "in Costa Rica?" Well, we'll have Outposts in Costa Rica. So you could build your own offering there, or you could build on top of Outputs while you distribute the rest of your workload in existing AWS offering. So to answer your question, John, there is no single answer. I think that it is per use case and per workload that customers are going to combine or choose which one of- >> Okay, so let's go through local zones. Explain what a local zone is real quick. I know we covered it a bit last year with the virtual event, but local zones are now part of the nomenclature of the AWS language. >> Yes. >> And we know what a region is, right? So regions are regions. What's a local zone? >> When your region's saying new availability zones, and then we're just (chuckles)- >> You got availability zones. Now you got local zones. Take us through the topology, if you will, of how to think about this. >> Right, so a local zone is a fully-managed AWS infrastructure deployment. So it's owned and managed and operated by AWS. And because of that, it offers you the same elasticity, and security, and all of the goodies of the cloud, but it's positioned closer to your end customers or to your own deployment. So it's positioned in the local urban, metropolitan or industrial center closer to you. So if you think about the U.S., for example, we have a few regions, like, in the East Coast and in the West Coast, but now, we're basically extending these regions, and we're bringing more and more services to 15 cities. So if you are in Miami, there is a local zone there. If you are in LA, there is two locals zones actually in LA. That enables customers to run two different types of workloads. One is these distributed clouds or distributed Edge kind of workload that we've been hearing more and more about. Think of gaming, for example, right? Like, we have customers that are, like Supercell, that need to be closer to the gamers, wherever they are. So they're going to be using a bunch of local zones to deploy. And also, we have these hyper-local use cases, where we're talking, for example, about Netflix that are enabling in LA their creative artists to connect locally and get like as low as single millisecond latencies. So local zone is like an availability zone, but it's closer to you. It offers the same scalability, the same elasticity, the same security and the same services as the AWS cloud. And it connects back to the regions to offer you the full breadth of the platform. >> So just to clarify, so the Edge strategy essentially is to bring the cloud, AWS, the primitives, the APIs, to where the customers are in instances where they either can't move or won't move their resources into the cloud, or there's no connectivity? >> Right, we have a bunch of use cases where customers either need to be there because of regulation or because of some data gravity, so data is being generated in a specific place and you need to locally process it, or we'll have customers in this distributed use case. But I think that you're pointing out a very important thing, which is a common factor across all of these offerings. It's it is the cloud. It's not like a copycat of the cloud. It's the same API. It's the same services that you already know and use, et cetera. So extending the cloud rather than copying it around is our vision, and getting those customers who, well, connectivity obviously needs to be there. We were offering AWS Private 5G. We talked about it yesterday. >> Now, a premise that we've had is that a lot of Edge use cases will be driven by AI inferencing. And so... First of all, is that a reasonable premise, that's growing, we think, very quickly, and it has huge potential. What does the compute, if that's the correct premise, what does the compute look like for that type of workload? >> That is a great premise, and that's why we think that the model that we're offering is so powerful, because you have the Edge and the cloud fully cooperating and being connected together. You know, the Edge is a resource that's more limited than the full cloud in the AWS region. So when you're doing inferencing, what you really want to do is you want to train your models back up in the region where you get more scalability and the best prices. You know, you have the full scale of AWS. But for the latency-sensitive parts of your applications, you want to push those to the Edge. So when you're doing the actual inferencing, not the training of the models- >> Real time. Yeah. >> Real time, you push that to the Edge, whether that's if your connectivity is 5G, you can push that into a Wavelength zone. If your connectivity is wired, you can push it into a local zone. If you really need it to be in your data center, you can push it in your Outposts. So you see how our kind of like building out for all of those use cases. >> But in those instances, I'm interested in what the compute looks like, 'cause I presume it's got to be low power, low cost, super high performance. I mean, all of those things that are good for data-driven workloads. >> Right, the power, if we think here, is the same compute that you know and love in the cloud. So the same EC2 instance types, the EBS volumes, the S3 for storage, or RDS for your databases and EMR clusters. You can use the same service. And the compute is the same powerful all the way down from the hardware up to the service. >> And is the promise to customers that eventually those... It's not all of those services, right? I mean, you go to Outposts today, it continues to grow. >> Continuing to grow, yeah. Right, so but conceptually, as many services you could possibly push to the Edge, you intend to do so? >> We are pushing services according to customer requests, but also there is a nuance here. The nuance is that you push down the services that are truly latency-sensitive. You don't need to push everything down to the Edge when you're talking about latency- >> Like, what's an example of what you wouldn't push down? >> So management tools, right? So when you're doing monitoring and management, yeah, you don't need these to be at the Edge. You can do that, and you can scale that. Or, you know, batch processing, it doesn't have to be at the Edge because it's, by definition, not online, not like a latency service. So we're keeping those, like AWS Batch, for example, that's in the region because, you know, that's where customers really use it. But things like EC2, EBS, EMR, we're pushing those to the Edge because those are more- >> We got two minutes left. I want to get the Outposts kind of update. I remember when Outposts launched. It was really a seminal moment for re:Invent. Hybrid. "Oh, Andy Jassy said hybrid." Yeah. "I'll never say hybrid." But now hybrid's kind of translated into all cloud operations. Now you got local zones. A lot's changed from Amazon Web Services standpoint since Outposts launched. Local zones, things are happening. 5G, DISH. Now what's the status of Outposts? Are you guys happy with it? What has it morphed into? Is it still the same game? What is Outposts today, vis-a-vis what people may think it is or isn't? >> Yeah, we've been focusing in what we're talking about, building out a number of services that customers request, but also being in more and more places. So I think we're in more than 60, now, countries with Outposts. We've seen very good adoption. We've seen very good feedback. You know, half of my EBCs have been on Outposts, but this year, I think that one of the most exciting announcements were the Outposts servers. So the smaller form factors that enable an additional use cases, like for example, retail or even building your 5G networks. You know, one of our partners, Mavenir, is moving their 5G core, so the smarts of the network that does all the routing, on Outposts servers, and we can distribute those all over the place. So, we're keeping on the innovation. We're keeping on the expansion. And we've been getting very good customer feedback- >> So all steam ahead, full steam ahead? >> Full steam ahead plus 10%. (John laughs) >> All right, guys. Thank you so much, George. Really appreciate it. We're seeing the cloud expand. The definition is growing, kind of like the universe, John. Dave Vellante for John John Furrier. You're watching "theCube" at AWS re:Invent, the leader in high tech coverage globally. We'll be right back.

>>Hi, buddy. Welcome back to the keeps coverage of AWS 2021. Re-invent you're watching the cube and I'm really excited. We're going to go outside the storage box. I like to say with my lawn Thompson Bukovac, who's the vice-president of block and object storage and Wayne Duso was a VP of storage edge and data governance guys. Great to see you again, we saw you at storage day, the 15 year anniversary of AWS, of course, the first product service ever. So awesome to be here. Isn't it. Wow. >>So much energy in the room. It's so great to see customers learning from each other, learning from AWS, learning from the things that you're observing as well. >>A lot of companies decided not to do physical events. I think you guys are on the right side of history. We're going to show you, you weren't exactly positive. How many people are going to show up. Everybody showed. I mean, it's packed house here, so >>Number 10. Yeah. >>All right. So let's get right into it. Uh, news of the week. >>So much to say, when you want to kick this off, >>We had a, we had a great set of announcements that Milan, uh, talked about yesterday, uh, in her talk and, and a couple of them in the file space, specifically a new, uh, member of the FSX family. And if you remember that the FSA, Amazon FSX is, uh, for customers who want to run fully managed versions of third party and open source file systems on AWS. And so yesterday we announced a new member it's FSX for open ZFS. >>Okay, cool. And there's more, >>Well, there's more, I mean, one of the great things about the new match file service world and CFS is it's powered by gravity. >>It is taught by Gravatar and all of the capabilities that AWS brings in terms of networking, storage, and compute, uh, to our customers. >>So this is really important. I want the audience to understand this. So I I've talked on the cube about how a large proportion let's call it. 30% of the CPU cycles are kind of wasted really on things like offloads, and we could be much more efficient, so graviton much more efficient, lower power and better price performance, lower cost. Amazon is now on a new curve, uh, cycles are faster for processors, and you can take advantage of that in storage it's storage users, compute >>That's right? In fact, you have that big launch as well for luster, with gravity. >>We did in fact, uh, so with, with, uh, Yasmin of open CFS, we also announced the next gen Lustre offering. And both of these offerings, uh, provide a five X improvement in performance. For example, now with luster, uh, customers can drive up to one terabyte per second of throughput, which is simply amazing. And with open CFS, right out of, right out of the box at GA a million IOPS at sub-millisecond latencies taking advantage of gravitas, taking advantage of our storage and networking capabilities. >>Well, I guess it's for HPC workloads, but what's the difference between these days HPC, big data, data intensive, a lot of AI stuff, >>All right. You to just, there's a lot of intersection between all of those different types of workloads they have, as you said, and you know, it all, it all depends on it all matters. And this is the reason why having the suite of capabilities that the, if you would, the members of the family is so important to our guests. >>We've talked a lot about, it's really can't think about traditional storage as a traditional storage anymore. And certainly your world's not a box. It's really a data platform, but maybe you could give us your point of view on that. >>Yeah, I think, you know, if, if we look, if we take a step back and we think about how does AWS do storage? Uh, we think along multiple dimensions, we have the dimension that Wayne's talking about, where you bring together the power of compute and storage for these managed file services that are so popular. You and I talked about, um, NetApp ONTAP. Uh, we went into some detail on that with you as well, and that's been enormously popular. And so that whole dimension of these managed file services is all about where is the customer today and how can we help them get to the cloud? But then you think about the other things that we're also imagining, and we're, re-imagining how customers want to grow those applications and scale them. And so a great example here at reinvent is let's just take the concept of archive. >>So many people, when they think about archive, they think about taking that piece of data and putting it away on tape, putting it away in a closet somewhere, never pulling it out. We don't think about archive like that archive just happens to be data that you just aren't using at the moment, but when you need it, you need it right away. And that's why we built a new storage class that we launched just yesterday, Dave, and it's called glacier instead of retrieval, it has retrieval and milliseconds, just like an Esri storage class has the same pricing of four tenths of a cent as glacier archive. >>So what's interesting at the analyst event today, Adam got a question about, and somebody was poking at him, you know, analysts can be snarky sometimes about, you know, price, declines and so forth. And he said, you know, one of the, one of the things that's not always shown up and we don't always get credit for lowering prices, but we might lower costs. And there's the archive and deep archive is an example of that. Maybe you could explain that point of view. >>Yeah. The way we look at it is that our customers, when they talk to us about the cost of storage, they talked to us about the total cost of the storage, and it's not just storing the data, it's retrieving it and using it. And so we have done an amazing amount across all the portfolio around reducing costs. We have glacier answer retrieval, which is 68% cheaper than standard infrequent access. That's a big cost reduction. We have EBS snapshots archive, which we introduced yesterday, 75% cheaper to archive a snapshot. And these are the types of that just transform the total cost. And in some cases we just eliminate costs. And so the glacier storage class, all bulk retrievals of data from the glacier storage class five to 12 hours, it's now free of charge. If you don't even have to think about, we didn't even reduce it. We just eliminated the cost of that data retrieval >>And additive to what Milan said around, uh, archiving. If you look at what we've done throughout the entire year, you know, a interesting statistic that was brought up yesterday is over the course of 2021, between our respective teams, we've launched over 105 capabilities for our customers throughout this year. And in some of them, for instance, on the file side for EFS, we launched one zone which reduced, uh, customer costs by 47%. Uh, you can now achieve on EFS, uh, cost of roughly 4.30 cents per gigabyte month on, uh, FSX, we've reduced costs up to 92%, uh, on Lustre and FSX for windows and with the introduction of ONTAP and open CFS, we continue those forward, including customers ability to compress and Dedoose against those costs. So they ended up seeing a considerable savings, even over what our standard low prices are. >>100 plus, what can I call them releases? And how can you categorize those? Are they features of eight? Do they fall into, >>Because they range for major services, like what we've launched with open ZFS to major features and really 95 of those were launched before re-invent. And so really what you have between the different teams that work in storage is you have this relentless drive to improve all the storage platforms. And we do it all across the course of the year, all across the course of the year. And in some cases, the benefit shows up at no cost at all to a customer. >>Uh, how, how did this, it seems like you're on an accelerated pace, a S3 EBS, and then like hundreds of services. I guess the question is how come it took so long and how is it accelerating now? Is it just like, there was so much focus on compute before you had to get that in place, or, but now it's just rapidly accessing, >>I I'll tell you, Dave, we took the time to count this year. And so we came to you with this number of 106, uh, that acceleration has been in place for many years. We just didn't take the time to couch. Correct. So this has been happening for years and years. Wayne and I have been with AWS for, for a long time now for 10 plus years. And really that velocity that we're talking about right now that has been happening every single year, which is where you have storage today. And I got to tell you, innovation is in our DNA and we are not going to stop now >>So 10 years. Okay. So it was really, the first five years was kind of slow. And then >>I think that's true at all. I don't think that try, you know, if you, if you look at, uh, the services that we have, we have the most complete portfolio of any cloud provider when it comes to storage and data. And so over the years, we've added to the foundation, which is S3 and the foundation, which is EBS. We've come out with a number of storage services in the, in the file space. Now you have an entire suite of persistent data stores within AWS and the teams behind those that are able to accelerate that pace. Just to give you an example, when I joined 10 years ago, AWS launched within that year, roughly a hundred and twenty, a hundred and twenty eight services or features our teams together this year have launched almost that many, just in those in, just in this space. So AWS continues to accelerate the storage teams continue to accelerate. And as my line said, we just started counting >>The thing. And if you think about those first five years, that was laying the baseline to launch us three, to launch EBS, to get that foundation in place, get lifecycle policies in place. But really, I think you're just going to see an even faster acceleration that number's going up. >>No, I that's what I'm saying. It does appear that way. And you had to build a team and put teams in place. And so that's, you know, part of the equation. But again, I come back to, it's not even, I don't even think of it as storage anymore. It's it's data. People are data lake is here to stay. You might not like the term. We always use the joke about a data ocean, but data lake is here to say 200,000 data lakes. Now we heard Adam talk about, uh, this morning. I think it was Adam. No, it was Swami. Do you want a thousand data lakes in your customer base now? And people are adding value to that data in new ways, injecting machine intelligence, you know, SageMaker is a big piece of that. Tying it in. I know a lot of customers are using glue as catalogs and which I'm like, wow, is glue a catalog or, I mean, it's just so flexible. So what are you seeing customers do with that base of data now and driving new business value? Because I've said last decade plus has been about it transformation. And now we're seeing business transformation. Maybe you could talk about that a little bit. >>Well, the base of every data lake is going to be as three yesterday has over 200 trillion objects. Now, Dave, and if you think about that, if you took every person on the planet, each of those people would have 26,000 S3 objects. It's gotten that big. And you know, if you think about the base of data with 200 trillion plus objects, really the opportunity for innovation is limitless. And you know, a great example for that is it's not just business value. It's really the new customer experiences that our customers are inventing the NFL. Uh, they, you know, they have that application called digital athlete where, you know, they started off with 10,000 labeled images or up to 20,000 labeled images now. And they're all using it to drive machine learning models that help predict and support the players on the field when they start to see things unfold that might cause injury. That is a brand new experience. And it's only possible with vast amounts of data >>Additive to when my line said, we're, we're in you talk about business transformation. We are in the age of data and we represent storage services. But what we really represent is what our customers hold one of their most valuable assets, which is their data. And that set of data is only growing. And the ability to use that data, to leverage that data for value, whether it's ML training, whether it's analytics, that's only accelerated, this is the feedback we get from our customers. This is where these features and new capabilities come from. So that's, what's really accelerating our pace >>Guys. I wish we had more time. I'd have to have you back because we're on a tight clock here, but, um, so great to see you both especially live. I hope we get to do more of this in 2022. I'm an optimist. Okay. And keep it right there, everybody. This is Dave Volante for the cube you're leader in live tech coverage, right back.

>>Mhm. Mhm. >>We're here with the Cube covering Calm Vault Connections 21. We're gonna look at the data protection space and how cloud computing has advanced the way we think about backup recovery and protecting our most critical data. Ranga Rajagopalan, who is the vice president of products at Con vault and Stephen Orban, who's the General manager of AWS marketplace and control services gents. Welcome to the cube. Good to see you. >>Thank you. Always A pleasure to see you here >>steve. Thanks for having us. Very >>welcome, Stephen, let's start with you. Look the cloud has become a staple of digital infrastructure. I don't know where we'd be right now without being able to access enterprise services I. T. Services remotely. Um But specifically how our customers looking at backup and recovery in the cloud, is it a kind of a replacement for existing strategies? Is it another layer of protection? How are they thinking about that? >>Yeah. Great question. David again, thank thanks for having me. And I think you know, look if you look back to 15 years ago when the founders of AWS had the hypothesis that many enterprises governments and developers we're gonna want access to on demand pay as you go I. T. Resources in the cloud. Uh None of us would have been able to predict that it would have Matured and um you know become the staple that it has today over the last 15 years. But the reality is that a lot of these enterprise customers, many of whom have been doing their own IT infrastructure for the last 10, 20 or multiple decades do have to kind of figure out how they deal with the change management of moving to the cloud. And while a lot of our customers um will initially come to us because they're looking to save money or costs, almost all of them decided to stay and go big because of the speed at which they are able to innovate on behalf of their customers and when it comes to storage and backup, that just plays right into where they're headed. And there's a variety of different techniques that customers use, whether it be, you know, a lift and shift for a particular set of applications or a data center where they do very much. Look at how can they replace the backup and recovery that they have on premises in the cloud using solutions like, but we're partnering with console to do or completely reimagining their architecture for net new developments that they can really move quickly for their customers. Um and and completely developing something brand new, where it is really a, you know, a brand new replacement and innovation for for for what they've done in the past. >>Great, thank you, Stephen Rachael, I want to ask you about the d were digital. Look, if you're not a digital business today, you're basically out of business. So, my question to you is how have you seen customers change the way they think about data protection during what I call the forced March to digital over the last 18, 19 months or customers, you know, thinking about data protection differently today >>definitely Dave and and thank you for having me and steven. Pleasure to join you on this cube interview first going back to stevens comments can't agree more. Almost every business that we talked with today has a cloud first strategy, a cloud transformation mandate and you know, the reality is back to your digital comment. There are many different paths to the hybrid multi cloud and different customers. You know, there are different parts of the journey. So I still was saying most often customers at least in the data protection perspective start the conversation by thinking here have all these tips. Can I start using cloud as my air gap long term retention target and before they realized they start moving their workloads into the cloud and none of the backup and record yesterday's are going to change. So you need to continue protecting the clothes, which is where the cloud native data protection comes in and then they start innovating around er, can I use cloud as media sites so that you know, I don't need to meet in the other side. So this year is all around us. Cloud transformation is all around us and and the real essence of this partnership between AWS and calm vault is essentially to dr and simplify all the paths to the club regardless of whether you're going to use it as a storage started or you know, your production data center, all your dear disaster recovery site. >>Yeah, it really is about providing that optionality for customers. I talked to a lot of customers and said, hey, our business resilience strategy was really too focused on D. R. I've talked to all the customers at the other end of the spectrum said we don't even have a D. R. Strategy now, we're using the cloud for that. So it's really all over the map and you want that optionality. So steven and then go ahead. >>Please, ransomware plays a big role in many of these considerations that greatly. It's unfortunately not a question of whether you're going to be hit by ransomware, it's almost we can like, what do you do when you're hit by ransomware and the ability to use the clothes scaled immediately, bring up the resources, use the cloud backups has become a very popular choice simply because of the speed with which you can bring the business back to normal our patients. The agility and the power that cloud brings to the table. >>Yeah, ransomware is scary. You don't, you don't even need a high school diploma to be a ransomware ist you can just go on the dark web and by ransomware as a service and do bad things and hopefully you'll end up in jail. Uh Stephen we know about the success of the AWS marketplace, uh you guys are partnering here. I'm interested in how that partnership, you know, kind of where it started and how it's evolving. >>Yeah, happy to highlight on that. So, look when >>we when we started >>Aws or when the founders of aws started aws, as I said 15 years ago we we realized very early on that while we were going to be able to provide a number of tools for customers to have on demand access to compute storage, networking databases that many, particularly enterprise and government government customers still use a wide range of tools and solutions from hundreds, if not in some cases thousands of different partners. I mean I talked to enterprises who literally use thousands of of different vendors to help them deliver their solutions for their customers. So almost 10 years ago, we're almost at our 10 year anniversary for AWS marketplace, we launched the first substantiation of AWS marketplace which allowed builders and customers to find try buy and then deploy third party software solutions running on amazon machine instances also noticed as armies natively right in their AWS and cloud accounts to complement what they were doing in the cloud. And over the last nearly 10 years we've evolved quite a bit to the point where we support software and multiple different packaging types, whether it be amazon machine instances, containers, machine learning models and of course SAS and the rise of software as a service. So customers don't have to manage the software themselves. But we also support data products through the AWS Data exchange and professional services for customers who want to get services to help them integrate the software into their environments. And we now do that across a wide range of procurement options. So what used to be pay as you go amazon machine instances now includes multiple different ways to contract directly, customer can do that directly with the vendor with their channel partner or using kind of our public e commerce capabilities. And we're super excited, um, over the last couple of months we've been partnering with calm vault to get their industry leading backup and recovery solutions listed on AWS marketplace, which is available for our collective customers now. So not only do they have access to convulse awesome solutions to help them protect against ransomware as we talked about and to manage their backup and recovery environments, but they can find and deploy that directly in one click right into their AWS accounts and consolidate their building relationship right on the AWS and voice. And it's been awesome to work with with Rhonda and the product teams and convo to really, um, expose those capabilities where converts using a lot of different AWS services to provide a really great native experience for our collective customers as they migrate to the cloud. >>Yeah, the marketplace has been amazing. We've watched it evolve over the past decade and, and, and it's a, it's a key characteristic of everybody has a cloud today. We're a cloud to butt marketplaces unique uh, in that it's the power of the ecosystem versus the resources of one and Ringo. I wonder from, from your perspective, if you could talk about the partnership with AWS from your view and then specifically you've got some hard news, I wonder if you could talk about that as well. >>Absolute. So the partnership has been extended for more than 12 years. Right. So aws and Commonwealth have been bringing together solutions that help customers solve the data management challenges and everything that we've been doing has been driven by the customer demand that we seek. Right customers are moving their workloads in the cloud. They're finding new ways of deploying their workloads and protecting them. Um, you know, earlier we introduced cloud native integration with the EBS API which has driven almost 70% performance improvements in backup and restores. And when you look at huge customers like coca cola who have standardized on AWS um, combo. That is the scale that they want to operate in. You manage around 1 50,000 snapshots 1200 ec, two instances across six regions. But with just one resource dedicated for the data management strategy. Right? So that's where the real built in integration comes into play and we've been extending it to make use of the cloud efficiencies like our management and auto scale and so on. Another aspect is our commitment to a radically simple customer experience and that's, you know, I'm sure Stephen would agree it's a big month for at AWS as well. That's really together with the customer demand which brought us together to introduce com ball into the AWS marketplace exactly the way Stephen described it. Now the heart announcement is coming back up and recovery is available in native this marketplace. So the exact four steps that Stephen mentioned, find, try buy and deploy everything simplified through the marketplace So that our aws customers can start using far more back of software in less than 20 minutes. A 60 year trial version is included in the product through marketplace and you know, it's a single click buy, we use the cloud formation templates to deploy. So it becomes a super simple approach to protect the AWS workloads and we protect a lot of them. Starting from easy to rds dynamodb document DB um, you know, the containers, the list just keeps going on. So it becomes a very natural extension for our customers to make it super simple to start using convert data protection for the w >>well the con vault stack is very robust. You have extremely mature stack. I want, I'm curious as to how this sort of came about and it had to be customer driven. I'm sure where your customers saying, hey, we're moving to the cloud, we had a lot of workloads in the cloud, we're calm vault customer. That intersection between calm vault and AWS customers. So again, I presume this was customer driven. but maybe you can give us a little insight and add some color to that. >>Everything in this collaboration has been customer driven. We were earlier talking about the multiple paths to chlorine vapor example and still might probably add more color from his own experience at our jones. But I'll bring it to reference Parsons who's a civil engineering leader. They started with the cloud first mandate saying we need to start moving all our backups to the cloud but we have wanted that bad actors might find it easy to go and access the backups edible is um, Conwell came together with the security features and com well brought in its own authorization controls and now we have moved more than 14 petabytes of backup data into the club and it's so robust that not even the backup administrator and go and touch the backups without multiple levels of authorization. Right. So the customer needs, whether it is from a security perspective performance perspective or in this case from a simplicity perspective is really what is driving this. And and the need came exactly like that. There are many customers who have no standardized on it because they want to find everything through the AWS marketplace. They want to use their existing, you know, the AWS contracts and also bring data strategy as part of that so that that's the real um, driver behind this. Um, Stephen and I hope actually announced some of the customers that I actively started using it. You know, many notable customers have been behind this uh, innovation, don't even, I don't know, I wanted to add more to that. >>I would just, I would, I would just add Dave, you know, look if I look back before I joined a W S seven years ago, I was the C I O at dow jones and I was leading a a fairly big cloud migration there over a number of years. And one of the impetus is for us moving to the cloud in the first place was when Hurricane Sandy hit, we had a real disaster recovery scenario in one of our New Jersey data centers um, and we had to act pretty quickly convert was, was part of that solution. And I remember very clearly Even back then, back in 2013, they're being options available to help us accelerate are moved to the cloud and just to reiterate some of the stuff that Rhonda was talking about consoles, done a great job over the last more than a decade, taking features from things like EBS and S three and EC two and some of our networking capabilities and embedding them directly into their services so that customers are able to more quickly move their backup and recovery workloads to the cloud. So each and every one of those features was as a result of, I'm sure combo working backwards from their customer needs just as we do at >>AWS >>and we're super excited to take that to the next level to give customers the option to then also by that right on their AWS invoice on AWS marketplace. >>Yeah, I mean, we're gonna have to leave it there steven, you've mentioned several times the sort of the early days of back then we were talking about gigabytes and terabytes and now we're talking about petabytes and beyond. Guys. Thanks so much. I really appreciate your time and sharing the news with us. >>Dave. Thanks for having us. >>All right. Keep it right there more from combat connections. 21. You're watching the >>cube. Mm hmm.

(Techno music plays in intro) >> We're here with theCUBE covering Commvault Connections 21. And we're going to look at the data protection space and how cloud computing has advanced the way we think about backup, recovery and protecting our most critical data. Ranga Rajagopalan who is the Vice President of products at Commvault, and Stephen Orban who's the General Manager of AWS Marketplace & Control Services. Gents! Welcome to theCUBE. Good to see you. >> Thank you, always a pleasure to see you Dave. >> Dave, thanks for having us. Great to be here. >> You're very welcome. Stephen, let's start with you. Look, the cloud has become a staple of digital infrastructure. I don't know where we'd be right now without being able to access enterprise services, IT services remotely, Um, but specifically, how are customers looking at backup and recovery in the cloud? Is it a kind of a replacement for existing strategies? Is it another layer of protection? How are they thinking about that? >> Yeah. Great question, Dave. And again, thanks. Thanks for having me. And I think, you know, look. If you look back to 15 years ago, when the founders of AWS had the hypothesis that many enterprises, governments, and developers were going to want access to on demand, pay as you go, IT resources in the cloud. None of us would have been able to predict that it would have matured and, um, you know become the staple that it has today over the last 15 years. But the reality is that a lot of these are enterprise customers. Many of whom have been doing their own IT infrastructure for the last 10, 20 or or multiple decades do have to kind of figure out how they deal with it. The change management of moving to the cloud, and while a lot of our customers will initially come to us because they're looking to save money or costs. Almost all of them decide to stay and go big because of the speed at which they're able to innovate on behalf of their customers. And when it comes to storage and backup, that just plays right into where they're headed and there's a variety of different techniques that customers use. Whether it be, you know, a lift and shift for a particular set of applications. Or a data center or where it, where they do very much look at how can they replace the backup and recovery that they have on premises in the cloud using solutions like what we're partnering with Commvault to do. Or completely re-imagining their architecture for net new developments that they can really move quickly for, for their customers and, and completely developing something brand new, where it is really a, um, you know a brand new replacement and innovation for, for, for what they've done in the past. >> Great. Thank you, Stephen. Ranga, I want to ask you about the D word, digital. Look, if you're not a digital business today, you're basically out of business. So my question to you Ranga is, is how have you seen customers change the way they think about data protection during what I call the forced March to digital over the last 18, 19 months? Are customers thinking about data protection differently today? >> Definitely Dave, and and thank you for having me and Stephen pleasure to join you on this CUBE interview. First, going back to Stephen's comments, can't agree more. Almost every business that we talk with today has a cloud first strategy, a cloud transmission mandate. And, you know, the reality is back to your digital comment. There are many different paths to the hybrid micro cloud. And different customers. You know, there are different parts of the journey. So as Stephen was saying, most often customers, at least from a data protection perspective. Start the conversation their thinking, hey, I have all these tapes, can I start using cloud as my air gap, long-term retention target. And before they realize they start moving their workloads into the cloud, and none of the backup and recovery facilities are going to change. So you need to continue protecting the cloud, which is where the cloud meta data protection comes in. And then they start innovating around DR Can I use cloud as my DR sites so that, you know, I don't need to meet in another site. So this is all around us, cloud transmissions, all around us. And, and the real essence of this partnership between AWS and Commvault is essentially to drive, and simplify all the paths to the cloud Regardless of whether you're going to use it as a storage target or, you know, your production data center or your DR. Disaster Recovery site. >> Yeah. So really, it's about providing that optionality for customers. I talked to a lot of customers and said, hey, our business resilience strategy was really too focused on DR. I've talked to all the customers at the other end of the spectrum said, we didn't even have a DR strategy. Now we're using the cloud for that. So it's a, it's really all over the map and you want that optionality. So Stephen, >> (Ranga cuts in) >> Go ahead, please. >> And sorry. Ransomware plays a big role in many of these considerations as well, right? Like, it's unfortunately not a question of whether you're going to be hit by ransomware. It's almost become like, what do you do when you're hit by ransomware? And the ability to use the cloud scale to immediately bring up the resources. Use the cloud backers has become a very popular choice simply because of the speed with which you can bring the business back to normal operations. The agility and the power that cloud brings to the table. >> Yeah. Ransomware is scary. You don't, you don't even need a high school degree diploma to be a ransomware-ist. You could just go on the dark web and buy ransomware as a service and do bad things. And hopefully you'll end up in jail. Stephen, we know about the success of the AWS Marketplace. You guys are partnering here. I'm interested in how that partnership, you know, kind of where it started and how it's evolving. >> Yeah. And happy to highlight on that. So look, when we, when we started AWS or when the founders of AWS started AWS, as I said, 15 years ago. We realized very early on that while we were going to be able to provide a number of tools for customers to have on demand access to compute storage, networking databases, that many particularly, enterprise and government government customers still use a wide range of tools and solutions from hundreds, if not in some cases, thousands of different partners. I mean, I talked to enterprises who who literally used thousands of of different vendors to help them deliver those solutions for their customers. So almost 10 years ago, we're almost at our 10 year anniversary for AWS Marketplace. We launched the first instantiation of AWS Marketplace, which allowed builders and customers to find, try, buy, and then deploy third-party software solutions running on Amazon Machine Instances, also known as AMI's. Natively, right in their AWS and cloud accounts to compliment what they were doing in the cloud. And over the last, nearly 10 years, we've evolved quite a bit. To the point where we support software in multiple different packaging types. Whether it be Amazon Machine Instances, containers, machine learning models, and of course, SAS and the rise of software as a service, so customers don't have to manage the software themselves. But we also support a data products through the AWS data exchange and professional services for customers who want to get services to help them integrate the software into their environments. And we now do that across a wide range of procurement options. So what used to be pay as you go Amazon Machine Instances now includes multiple different ways to contract directly. The customer can do that directly with the vendor, with their channel partner or using kind of our, our public e-commerce capabilities. And we're super excited, um, over the last couple of months, we've been partnering with Commvault to get their industry leading backup and recovery solutions listed on AWS Marketplace. Which is available for our collective customers now. So not only do they have access to Commvault's awesome solutions to help them protect against ransomware, as we talked about and, and to manage their backup and recovery environments. But they can find and deploy that directly in one click right into their AWS accounts and consolidate their, their billing relationship right on the AWS invoice. And it's been awesome to work with with Ranga and the, and the product teams at Commvault to really expose those capabilities where Commvault's using a lot of different AWS services to, to provide a really great native experience for our collective customers as they migrate to the cloud. >> Yeah. The Marketplace has been amazing. We've watched it evolve over the past decade and it's just, it's a key characteristic of cloud. Everybody has a cloud today, right? Ah, we're a cloud too, but Marketplace is unique in, in, in that it's the power of the ecosystem versus the resources of one. And Ranga, I wonder if from your perspective, if you could talk about the partnership with AWS from your view, and and specifically you've got some hard news. Would, if you could, talk about that as well. >> Absolutely. So the partnership has been extending for more than 12 years, right? So AWS and Commvault have been bringing together solutions that help customers solve the data management challenges and everything that we've been doing has been driven by the customer demand that we see, right. Customers are moving their workloads to the cloud. They are finding new ways of deploying the workloads and protecting them. You know, earlier we introduced cloud native integration with the EBS AVI's which has driven almost 70% performance improvements in backup and restore. When you look at huge customers like Coca-Cola, who have standardized on AWS and Commvault, that is the scale that they want to operate on. They manage around one through 3,000 snapshots, 1200 easy, two instances across six regions, but with just one resource dedicated for the data management strategy, right? So that's where the real built-in integration comes into play. And we've been extending it to make use of the cloud efficiencies like power management and auto-scale, and so on. Another aspect is our commitment to a radically simple customer experience. And that's, you know, I'm sure Stephen would agree. It's a big mantra at AWS as well. That's really, together, the customer demand that's brought us together to introduce combo into the AWS Marketplace, exactly the way Stephen described it. Now the hot announcement is calmer, backup and recovery is available in AWS Marketplace. So the exact four steps that Stephen mentioned: find, try, buy, and deploy everything simplified to the Marketplace so that our AWS customers can start using our more backup software in less than 20 minutes. A 60 day trial version is included in the product through Marketplace. And, you know, it's a single click buy. We use the cloud formation templates to deploy. So it becomes a super simple approach to protect the AWS workloads. And we protect a lot of them starting from EC2, RDS DynamoDB, DocumentDB, you know, the, the containers, the list just keeps going on. So it becomes a very natural extension for our customers to make it super simple, to start using Commvault data protection for the AWS workloads. >> Well, the Commvault stack is very robust. You have an extremely mature stack. I want to, I'm curious as to how this sort of came about? I mean, it had to be customer driven, I'm sure. When your customers say, hey, we're moving to the cloud, we had a lot of workloads in the cloud. We're a Commvault customer, that intersection between Commvault and AWS customer. So, so again, I presume this was customer driven, but maybe you can give us a little insight and add some color to that, Ranga. >> Every everything, you know, in this collaboration has been customer driven. We were earlier talking about the multiple paths to cloud and a very good example, and Stephen might probably add more color from his own experience at Dow Jones, but I I'll, I'll bring it to reference Parsons. Who's, you know, civil engineering leader. They started with the cloud first mandate saying, we need to start moving all our backups to the cloud, but we averted that bad actors might find it easy to go and access the backups. AWS and Commvault came together with AWS security features and Commvault brought in its own authorization controls. And now we are moved more than 14 petabytes of backup data into the cloud, and it's sort of as that, not even the backup administrators can go and patch the backups without multiple levels of authorization, right? So the customer needs, whether it is from a security perspective, performance perspective, or in this case from a simplicity perspective is really what is driving us and, and the need came exactly like that. There are many customers who have now standardized on AWS, they want to find everything related to this Marketplace. They want to use their existing, you know, the AWS contracts and also bring data strategy as part of that. So that, that's the real driver behind this. Stephen and I were hoping that we could actually announce some of the customers that have actively started using it. You know, many notable customers have been behind this innovation. And Stephen I don't know if you wanted to add more to that. >> I would just, I would just add Dave, you know, like if I look back before I joined AWS seven years ago, I was the CIO at Dow Jones. And I was leading a, a fairly big cloud migration there over a number of years. And one of the impetuses for us moving to the cloud in the first place was when Hurricane Sandy hit, we had a real disaster recovery scenario in one of our New Jersey data centers. And we had to act pretty quickly. Commvault was, was part of that solution. And I remember very clearly, even back then, back in 2013, there being options available to help us accelerate our move to the cloud. And, and just to reiterate some of the stuff that Ranga was talking about, you know, Commvault's done a great job over the last, more than a decade. Taking features from things like EBS, and S3, and TC2 and some of our networking capabilities and embedding them directly into their services so that customers are able to, you know, more quickly move their backup and recovery workloads to the cloud. So each and every one of those features was, is a result of, I'm sure, Commvault working backwards from their customer needs just as we do at AWS. And we're super excited to take that to the next level, to give customers the option to then also buy that right on their AWS invoice on AWS Marketplace. >> Yeah. I mean, we're going to have to leave it there. Stephen you've mentioned this several times, there's sort of the early days of AWS. We went back then we were talking about gigabytes and terabytes, and now we're talking about petabytes and beyond. Guys thanks so much. We really appreciate your time and sharing the news with us. >> Dave, thanks for having us. >> All right, keep it right there more from Commvault Connections 21, you're watching theCUBE.