(upbeat music) >> Welcome back friends. It's theCUBE LIVE in Las Vegas at the Venetian Expo, covering the first full day of AWS re:Invent 2022. I'm Lisa Martin, and I have the privilege of working much of this week with Dave Vellante. >> Hey. Yeah, it's good to be with you Lisa. >> It's always good to be with you. Dave, this show is, I can't say enough about the energy. It just keeps multiplying as I've been out on the show floor for a few minutes here and there. We've been having great conversations about cloud migration, digital transformation, business transformation. You name it, we're talking about it. >> Yeah, and I got to say the soccer Christians are really happy. (Lisa laughing) >> Right? Because the USA made it through. So that's a lot of additional excitement. >> That's true. >> People were crowded around the TVs at lunchtime. >> They were, they were. >> So yeah, but back to data. >> Back to data. We have a couple of guests here. We're going to be talking a lot with customer challenges, how they're helping to overcome them. Please welcome Kevin Zawodzinski, VP of Sales Engineering at COMMVAULT. >> Thank you. >> And Paul Meighan, Director of Product Management at AWS. Guys, it's great to have you on the program. Thank you for joining us. >> Thanks for having us. >> Thanks for having us. >> Isn't it great to be back in person? >> Paul: It really is. >> Kevin: Hell, yeah. >> You cannot replicate this on virtual, you just can't. It's nice to see how excited people are to be back. There's been a ton of buzz on our program today about Adam's keynote this morning. Amazing. A lot of synergies with the direction, Paul, that AWS is going in and where we're seeing its ecosystem as well. Paul, first question for you. Talk about, you know, in the customer environment, we know AWS is very customer obsessed. Some of the main challenges customers are facing today is they really continue this business transformation, this digital transformation, and they move to cloud native apps. What are some of those challenges and how do you help them eradicate those? >> Well, I can tell you that the biggest contribution that we make is really by focusing on the fundamentals when it comes to running storage at scale, right? So Amazon S3 is unique, distributed architecture, you know, it really does deliver on those fundamentals of durability, availability, performance, security and it does it at virtually unlimited scale, right? I mean, you guys have talked to a lot of storage folks in the industry and anyone who's run an estate at scale knows that doing that and executing on those fundamentals day after day is just super hard, right? And so we come to work every day, we focus on the fundamentals, and that focus allows customers to spend their time thinking about innovation instead of on how to keep their data durably stored. >> Well, and you guys both came out of the storage world. >> Right. >> Yeah, yeah. >> It was a box world, (Kevin laughs) and it ain't no more. >> Kevin: That's right, absolutely. >> It's a service and a service of scale. >> Kevin: Yeah. So architecture matters, right? >> Yeah. >> Yeah. >> Paul, talk a little bit about, speaking of innovation, talk about the evolution of S3. It's been around for a while now. Everyone knows it, loves it, but how has AWS architected it to really help meet customers where they are? >> Paul: Right. >> Because we know, again, there's that customer first focus. You write the press release down the road, you then follow that. How is it evolving? >> Well, I can tell you that architecture matters a lot and the architecture of Amazon S3 is pretty unique, right? I think, you know, the most important thing to understand about the architecture of S3 is that it is truly a regional service. So we're laid out across a minimum of 3 Availability Zones, or AZs, which are physically separated and isolated and have a distance of miles between them to protect against local events like floods and fires and power interruption, stuff like that. And so when you give us an object, we distribute that data across that minimum of 3 Availability Zones and then within multiple devices within each AZ, right? And so what that means is that when you store data with us, your data is on storage that's able to tolerate the failure of multiple devices with no impact to the integrity of your data, which is super powerful. And then again, super hard to do when you're trying to roll your own. So that's sort of a, like an overview of the architecture. In terms of how we think about our roadmap, you know, 90% of our roadmap comes directly from what customers tell us matters, and that's a tenant of how we think about customer obsession at AWS and it really is how we drive a roadmap. >> Right, so speaking of customers Kevin, what are customers asking you guys- >> Yeah. >> for, how does it relate to what you're doing with S3? >> Yeah, it's a wonderful question and one that is actually really appropriate for us being at re:Invent, right? So we got, last three years we've had customers here with us on stage talking about it. First of all, 3 years ago we did a virtual session, unfortunately, but glad to be back as you mentioned, with Coca-Cola and theirs was about scale and scope and really about how can we protect hundreds of thousands of objects, petabyte to data, in a simple and secure way, right. Then last year we actually met with a ACT, Inc. as well and co-presented with them and really talked about how we could protect modern workloads and their modern workloads around whether it was Aurora or as well as EKS and how they continue to evolve as well. And, last but not least it's going to be, this year we're talking with Illinois State University as well about how they're going to continue to grow, adapt and really leverage AWS and ourselves to further their support of their teachers and their staff. So that is really helping us quite a bit to continue to move forward. And the things we're doing, again, with our customer base it's really around, focused on what's important to them, right? Customer obsession, how are we working with that? How are we making sure that we're listening to them? Again, working with AWS to understand how can we evolve together and really ultimately their journeys. As you heard, even with those 3 examples they're all very different, right? And that's the point, is that everybody's at a different point in the journey. They're at a different place from a modernization perspective. So we're helping them evolve, as they're helping us evolve as well, and transform with AWS. >> So very mature COMMVAULT stack, the S3 bucket and all the other capabilities. Paul, you just talked about coming together- >> Right. >> Dave: for your customers. >> Yeah, yeah, absolutely. And just, you know, we were talking the other day, Paul and I were talking the other day, it's been, you know, we've worked with AWS, with integration since 2009, right? So a long time, right? I mean, for some that may not seem like a long time ago, but it is, right? It's, you know, over a decade of time and we've really advanced that integration considerably as well. >> What are some of the things that, I don't know if you had a chance to see the keynote this morning? >> Yeah, a little bit. >> What are some of the things that there was, and in fact this is funny, funny data point for you on data. One of my previous guests told me that Adam Selipsky spent exactly 52 minutes talking about data this morning. 52 minutes. >> Okay. >> That there's a data point. But talk about some of the things that he talked about, the direction AWS is going in, obviously new era in the last year. Talk about what you heard and how you think that will evolve the COMMVAULT-AWS relationship. >> Yeah, I think part of that is about flexibility, as Paul mentioned too, architecture matters, right? So as we evolve and some of the things that we pride ourselves on is that we developed our systems and our software and everything else to not worry about what do I have to build to today but how do I continue to evolve with my customer base? And that's what AWS does, right? And continues to do. So that's really how we would see the data environment. It's really about that integration. As they grow, as they add more features we're going to add more features as well. And we're right there with them, right? So there's a lot of things that we also talk about, Paul and I talk about, around, you know, how do we, like Graviton3 was brought up today around some of the innovations around that. We're supporting that with Auto Scale right now, right? So we're right there releasing, right when AWS releasing, co-developing things when necessary as well. >> So let's talk about security a little bit. First of all, what is COMMVAULT, right? You're not a security company but you're an adjacency to security. It's sort of, we're rethinking security. >> Kevin: Yep. >> including data protection, not a bolt-on anymore. You guys both have a background in that world and I'm sure that resonates. >> Yeah. >> So what is the security play here? What role does COMMVAULT play? I think we know pretty well what role AWS plays, but love to hear, Paul, your thoughts as well on security. >> Yeah, I'll start I guess. >> Go on Paul. >> Okay. Yeah, so on the security side of things, there's a quite a few things. So again, on the development side of things, we do things like file anomaly detection, so seeing patterns in data. We talked a lot about analytics as well in the keynote this morning. We look at what is happening in the customer environment, if there's something odd or out of place that's happening, we can detect that and we'll notify people. And we've seen that, we have case studies about that. Other things we do are simple, simple but elegant. Is with our security dashboard. So we'll use our security dashboard to show best practices. Are they using Multi-Factor Authentication? Are you viewing password complexity? You know, things like that. And allows people to understand from a security landscape perspective, how do we layer in protection with their other systems around security. We don't profess to be the security company, or a security company, but we help, you know, obviously add in those additional layers. >> And obviously you're securing, you know, the S3 piece of it. >> Mmmhmm. >> You know, from your standpoint because building it in. >> That's right. And we can tell you that for us, security is job zero. And anyone at AWS will tell you that, and not only that but it will always be our top priority. Right from the infrastructure on down. We're very focused on our shared responsibility model where we handle security from the hypervisor, or host operating system level, down to the physical security of the facilities in which our services run and then it's our customer's responsibility to build secure applications, right. >> Yeah. And you talk about Graviton earlier, Nitro comes into play and how you're, sort of, fencing off, you know, the various components of the system from the operating system, the VMs, and then that is designed in and that's a new evolution that it comes as part of the package. >> Yeah, absolutely. >> Absolutely. >> Paul, talk a little bit about, you know, security, talking about that we had so many conversations this year alone about the threat landscape and how it's dramatically changing, it's top of mind for everybody. Huge rise in ransomware attacks. Ransomware is now, when are we going to get hit? How often? What's the damage going to be? Rather than, are we going to get hit? It's, unfortunately it's progressed in that direction. How does ensuring data security impact how you're planning the roadmap at AWS and how are partners involved in shaping that? >> Right, so like I said, you know, 90% of our roadmap comes from what customers tell us matters, right? And clearly this is an issue that matters very much to customers right now, right? And so, you know, we're certainly hearing that from customers, and COMMVAULT, and partners like COMMVAULT have a big role to play in helping customers to secure and protect their applications, right? And that's why it's so critical that we come together here at re:Invent and we have a bunch of time here at the show with the COMMVAULT technical folks to talk through what they're hearing from customers and what we're hearing. And we have a number of regular touch points throughout the year as well, right? And so what COMMVAULT gets from the relationship is, sort of, early access and feedback into our features and roadmap. And what we get out of it really is that feedback from that large number of customers who interface with Amazon S3 through COMMVAULT. Who are using S3 as a backup target behind COMMVAULT, right? And so, you know, that partnership really allows us to get close to those customers and understand what really matters to them. >> Are you doing joint engineering, or is it more just, hey here you go COMMVAULT, here's the tools available, go, go build. Can you address that? >> Yeah, no, absolutely. There's definitely joint engineering like even things around, you know, data migration and movement of data, we integrate really well and we talk a lot about, hey, what are you, like as Paul mentioned, what are you seeing out there? We actually, I just left a conversation about an hour ago where we're talking about, you know, where are we seeing placement of data and how does that matter to, do you put it on, you know, instant access, or do you put it on Glacier, you know, what should be the best practices? And we tell them, again, some of the telemetry data that we have around what do we see customers doing, what's the patterns of data? And then we feed that back in and we use that to create joint solutions as well. >> You know, I wonder if we could talk about cloud, you know, optimization of cloud costs for a minute. That's obviously a big discussion point in the hallways with customers. And on your earnings call you guys talked about specifically some customers and they specifically mentioned, for example, pushing storage to lower cost tiers. So you brought up Glacier just then. What are you seeing in the field in that regard? How are customers taking advantage of that? And where does COMMVAULT play in, sort of, helping make that decision? >> You want to take part one or you want me to take it? >> I can take part one. I can tell you that, you know, we're very focused on helping customers optimize costs, however necessary, right? And, you know, we introduced intelligent hearing here at the show in 2019 and since launch it's helped customers to reduce costs by over $750 million, right? So that's a real commitment to optimizing costs on behalf of customers. We also launched, you know, later in 2020, Glacier Deep Archive, which is the lowest cost storage in the cloud. So it's an important piece of the puzzle, is to provide those storage options that can allow customers to match the workloads that are, that need to be on folder storage to the appropriate store. >> Yeah, and so, you know, S3 is not this, you know, backup and recovery system, not an archiving system and, you know, in terms of, but you have that intelligence in your platform. 'Cause when I heard that from the earnings call I was like, okay, how do customers then go about deciding what they can, you know, when it's all good times, like yeah, who cares? You know, just go, go, go. But when you got to tighten the belt, how do you guys? >> Yeah, and that goes back to understanding the data pattern. So some of that is we have intelligence and artificial intelligence and everything else and machine learning within our, so we can detect those patterns, right? We understand the patterns, we learn from that and we help customers right size, right. So ultimately we do see a blend, right? As Paul mentioned, we see, you know, hey I'm not going to put everything on Glacier necessarily upfront. Maybe they are, it all depends on their workloads and patterns. So we use the data that we collect from the different customers that we have to share those best practices out and create, you know, the right templates, so to speak, in ways for people to apply it. >> Guys, great joint, you talked about the joint engineering, joint go to market, obviously a very strong synergistic partnership between the two. A lot of excitement. This is only day one, I can only imagine what's going to be coming the next couple of days. But I have one final question for you, but I have same question for both of you. You had the chance to create your own bumper sticker, so you get a shiny new car and for some reason you want to put a bumper sticker on it. About COMMVAULT, what would it say? >> Yeah, so for me I would say comprehensive, yet simple, right? So ultimately about giving you all the bells and whistles but if you want to be very simple we can help you in every shape and form. >> Paul, what's your bumper sticker say about AWS? >> I would say that AWS starts with the customer and works backwards from there. >> Great one. >> Excellent. Guys- >> Kevin: Well done. >> it's been a pleasure to have you on the program. Thank you- >> Kevin: Thank you. >> for sharing what's going on, the updates on the AWS-COMMVAULT partnership and what's in it for customers. We appreciate it. >> Dave: Thanks you guys. >> Thanks a lot. >> Thank you. >> All right. For our guests and Dave Vellante, I'm Lisa Martin. You're watching theCUBE, the leader in live enterprise and emerging tech coverage. (upbeat 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.

>>Hey everyone, and welcome back to The Cube's live coverage of AWS Reinvented 2022 Live from the Venetian Expo in Las Vegas. We're happy to be back. This is first full day of coverage over here last night. We've got three full days of coverage in addition to last night, and there's about 50,000 people here. This event is ready, people are ready to be back, which is so exciting. Lisa Martin here with Paul Gill and Paul, it's great to be back in person. Great to be hosting with you >>And likewise with you, Lisa. I think the first time we hosted again, >>It is our first time exactly. >>And we come here to the biggest event that the cube ever does during the year. >>It's the Super Bowl of the >>Cube. It's it's elbow to elbow out there. It's, it's, it's full tackle football, totally on the, on the floor of reinvent. And very exciting. This, you know, I've been to a lot of conferences going back 40 years, long as I can remember. Been going to tech conferences. This one, the, the intensity, the excitement around this is really unusual. People are jazzed, they're excited to be here, and that's great to see, particularly coming back from two years of isolation. >>Absolutely. The energy is so palpable. Even yesterday, evening, afternoon when I was walking in, you just feel it with all the people here. You know, we talk to so many different companies on the Q Paul. Every company these days has to be a data company. The most important thing about data is making sure that it's backed up and it's protected, that it's secure, that it can be recovered if anything happens. So we're gonna be having a great conversation next about data resiliency with one of our alumni. >>And that would be Rick Scott, Rick, excuse me, Rick Scott, >>Rick Clark. Rick Clark, say Rick Scott, cloud sales Veritas. Rick, welcome back >>To the program. Thank you. Thank you so much. It's a pleasure being here, you know, thank you so much. You're definitely very excited to myself and 40,000 of my closest cousins and friends all in one place. Yep. Or I could possibly go wrong, right? So >>Yeah, absolutely nothing. So, Rick, so Veritas has made some exciting announcements. Talk to us about some of the new things that you've >>Unveiled. Yeah, we've been, we've been incredibly busy and, you know, the journey that we've been on, one of the big announcement that we made about three or four weeks ago is the introduction, really, of a brand new cloud native data management platform that we call Veritas Alta. And this is a journey that we've been on for the better part of seven years. We actually started it with our, our flex appliances. We continued, that was a containerization of our traditional net backup business in, into a highly secured appliance that was loved by our customers. And we continued that theme and that investment into what we call a scale out and scale up form factor appliance as well, what we called flex scale. And then we continued on that investment theme, basically spending over a billion dollars over that seven year journey in our cloud native. And we call that basically the Veritas altar platform with our cloud native platform. And I think if you really look at what that is, it truly is a data management platform. And I emphasize the term cloud native. And so our traditional technologies around data protection, obviously application resiliency and digital compliance or data compliance and governance. We are the only, the first and only company in the world to provide really a cloud optimized, cloud native platform, really, that addresses that. So it's been fun, it's been a fun journey. >>Talk a little bit about the customer experience. I see over 85% of the Fortune 100 trust Veritas with their data management. That's >>A big number. Yeah. Yeah. It's, it is incredible actually. And it really comes back to the Veritas older platform. We sort of built that with, with four tenants in mind, all driving back to this very similar to AWS's customer obsession. Everything we do each and every day of our waiting moments is a Veritas employee is really surrounds the customer. So it starts with the customer experience on how do they find us to, how do they procure our solutions through things like AWS marketplace and how do they deploy it? And the second thing is around really cost optimization, as we know, you know, to, to say that companies are going through a digital transformation and moving workloads to the cloud. I mean, I've got customers that literally were 20% in cloud a year ago and 80% a year later, we've never seen that kind of velocity. >>And so we've doubled down on this notion of cost optimization. You can only do that with these huge investments that I talked about. And so we're a very profitable company. We've been around, got a great heritage of over 30 years, and we've really taken those investments in r and d to provide that sort of cloud native technology to ultimately make it elastic. And so everything from will spin up and spin down services to optimize the cloud bill for our customers, but we'll also provide the greatest workload support. You know, obviously on-prem workloads are very different from cloud workloads and it's almost like turning the clock back 20 years to see all of those new systems. There's no standard API like s and MP on the network. And so we have to talk to every single PAs service, every single DB PAs, and we capture that information and protect it. So it's really has been a phenomenal journey. It's been great. >>You said this, that that al represents a shift from clouds from flex scale to cloud native. What is the difference there? >>The, the main difference really is we took, you know, obviously our traditional product that you've known for many media years, net backup. It's got, you know, tens of millions of lines of code in that. And we knew if we lifted and shifted it up into the cloud, into an I AEs infrastructure, it's just not, it obviously would perform extremely well, but it wasn't cost optimized for our customer. It was too expensive to to run. And so what we did is we rewrote with microservices and containerization, Kubernetes huge parts of that particular product to really optimize it for the cloud. And not only have we done it for that technology, what we now call alter data protection, but we've done it across our entire port portfolio. That was really the main change that we made as part of this particular transition. And >>What have you done to prepare customers for that shift? Is this gonna be a, a drop in simple upgrade for them? >>Absolutely. Yeah. In fact, one of the things that we introduced is we, we invest still very heavily with regards to our OnPrem solutions. We're certainly not abandoning, we're still innovating. There's a lot of data still OnPrem that needs to move to the cloud. And so we have a unique advantage of all of the different workload supports that we provide OnPrem. We continue that expansion into the cloud. So we, we create it as part of the Veritas AL Vision, a technology, we call it AL view. So it's a single painter glass across both OnPrem and cloud for our customers. And so now they can actually see all of their data protection, all our application availability, single collect, all through that single unified interface, which is really game changing in the industry for us. >>It's game changing for customers too, because customers have what generally six to seven different backup technologies in their environment that they're having to individually manage and provision. So the, the workforce productivity improvements I can imagine are, are huge with Veritas. >>Yeah. You you nailed it, right? You must have seen my script, but Absolutely. I mean, I look at the analogy of, you think about the airlines, what's one of the first things airlines do with efficiency? South Southwest Airlines was the best example, a standardized on the 7 37, right? And so all of their pilots, all of their mechanics, all know how to operate the 7 37. So we are doing the same thing with enterprise data protection. So whether you're OnPrem at the edge or in the cloud or even multi-cloud, we can provide that single painter glass. We've done it for our customers for 30 plus years. We'll continue to do it for another 30 something years. And so it's really the first time with Veritas altar that, that we're, we're coming out with something that we've invested for so long and put, put such a huge investment on that can create those changes and that compelling solution for our customers. So as you can see, we're pretty pumped and excited about it. >>Yes, I can >>Use the term data management to describe Alta, and I want to ask about that term because I hear it a lot these days. Data management used to be database, now data management is being applied to all kinds of different functions across the spectrum. How do you define data management in Veritas >>Perspective? Yeah, there's a, we, we see it as really three main pillars across the environment. So one is protection, and we'll talk a little bit about this notion of ransomware is probably the number one use case. So the ability to take the most complex and the biggest, most vast applications. SAP is an example with hundreds of different moving parts to it and being able to protect that. The second is application resiliency. If, if you look at the cloud, there's this notion of, of responsibility, shared responsibility in the cloud. You've heard it, right? Yep. Every single one of the cloud service providers, certainly AWS has up on their website, this is what we protect, here's the demarcation line, the line in the sand, and you, the customer are responsible for that other level. And so we've had a technology, you previously knew it as InfoScale, we now call it alter application resiliency. >>And it can provide availability zone to availability zone, real time replication, high availability of your mission critical applications, right? So not only do we do the traditional backups, but we can also provide application resiliency for mission critical. And then the third thing really from a data management standpoint is all around governance and compliance. You know, ac a lot of our customers need to keep data for five, 10 years or forever. They're audited. There's regulations and different geographies around the world. And, and those regulations require them to be able to really take control of their cloud, take control of their data. And so we have a whole portfolio of solutions under that data compliance, data government. So back to your, your question Paul, it's really the integration and the intersection of those three main pillars. We're not a one trick pony. We've been at this for a long time, and they're not just new products that we invented a couple of months ago and brought to market. They're tried and tested with eight 80,000 customers and the most complex early solutions on the planet that we've been supporting. >>I gotta ask you, you know, we talked about those three pillars and you talked about the shared responsibility model. And think of that where you mentioned aws, Salesforce, Microsoft 365, Google workspace, whatnot. Are you finding that most customers aren't aware of that and haven't been protecting those workloads and then come to you and saying, Hey guys, guess what, this is what this is what they're responsible for. The data is >>You Yeah, I, it's, it's our probably biggest challenge is, is one of awareness, you know, with the cloud, I mean, how many times have you spoken to someone? You just put it in the cloud. Your applications, like the cloud providers like aws, they'll protect everything. Nothing will ever go down. And it's kind like if you, unless your house was ever broken into, you're probably not gonna install that burglar alarm or that fire alarm, right? Hopefully that won't be an event that you guys have to suffer through. So yeah, it's definitely, it wasn't till the last year or so the cloud service providers really published jointly as to where is their responsibility, right? So a great example is an attack vector for a lot of corporations is their SAS applications. So, you know, whether it it's your traditional SA applications that is available that's available on the web to their customers as a sas. >>And so it's certainly available to the bad actors. They're gonna, where there's, there's gonna be a point they're gonna try to get in. And so no matter what your resiliency plan is, at the end of the day, you really need to protect it. And protection isn't just, for example, with M 365 having a snapshot or a recycle bin, that's just not good enough. And so we actually have some pretty compelling technology, what we call ALTA SAS protection, which covers the, pretty much the, the gamut of the major SAS technologies to protect those and make it available for our customers. So yeah, certainly it's a big part of it is awareness. Yeah. >>Well, I understand that the shared responsibility model, I, I realize there's a lot of confusion about that still, but in the SaaS world that's somewhat different. The responsibility of the SaaS provider for protecting data is somewhat different. How, how should, what should customers know about that? >>I think, you know, the, the related to that, if, if you look at OnPrem, you know, approximately 35 to 40% of OnPrem enterprise data is protected. It's kind of in a long traditional problem. Everyone's aware of it. You know, I remember going to a presentation from IBM 20 something years ago, and someone held their push hand up in the room about the dis drives and says, you need to back it up. And the IBM sales guy said, no, IBM dis drives never crash. Right? And so fast forward to here we are today, things have changed. So we're going through almost a similar sort of changes and culture in the cloud. 8% of the data in the cloud is protected today, 8%. That's incredible. Meaning >>That there is independent backup devoted >>To that data in some cases, not at all. And something many cases, the customer just assumes that it's in the cloud, therefore it's always available. I never have to worry about protecting it, right? And so that's a big problem that we're obviously trying to, trying to solve. And we do that all under the umbrella of ransomware. That's a huge theme, huge investment that, that Veritas does with regards to providing that resiliency for our >>Customers. Ransomware is scary. It is becoming so prolific. The bad actors have access to technologies. Obviously companies are fighting them, but now ransomware has evolved into, no longer are we gonna get hit, it's when, yeah, it's how often it's what's the damage going to be. So the ability to help customers recover from ransomware, that resiliency is table stakes for businesses in any industry these days. Does that, that one of the primary pain points that your customers are coming to you with? >>It's the number one pain point. Yeah, it's, it's incredible. I mean, there's not a single briefing that our teams are doing customer meetings where that term ransomware doesn't come up as, as their number one use case. Just to give you something, a couple of statistics. There's a ransomware attack attack that happens 11 times a second right around the globe. And this isn't just, you know, minor stuff, right? I've got friends that are, you know, executives of large company that have been hit that have that some, you know, multimillion dollar ransom attack. So our, our play on this is, when you think about it, is data protection is the last line of defense. Yes. And so if they break through, it's not a case, Lisa, as you mentioned, if it's a case of when Yeah. And so it's gonna happen. So one of the most important things is knowing how do you know you have a gold copy, a clean copy, and you can recover at speed in some cases. >>We're talking about tens of thousands of systems to do that at speed. That's in our dna. We've been doing it for many, many years. And we spoke through a lot of the cyber insurance companies on this particular topic as well. And what really came back from that is that they're actually now demanding things like immutable storage, malware detection, air gaping, right? Anomaly detection is sort of core technologies tick the box that they literally won't ensure you unless you have those core components. And so what we've done is we've doubled down on that investment. We use AI in ML technologies, particularly around the anomaly detection. One of the, the, the unique and ne differentiators that Verto provides is a ransomware resiliency scorecard. Imagine the ability to save uran a corporation. We can come in and run our analytics on your environment and kind of give you a grade, right? Wouldn't you prefer that than waiting for the event to take place to see where your vulnerability really is? And so these are some of the advantages that we can actually provide for our customers, really, really >>To help. Just a final quick question. There is a, a common perception, I believe that ransomware is an on premise problem. In fact, it is also a cloud problem. Is that not right? >>Oh, absolutely. I I think that probably the biggest attack vector is in the cloud. If it's, if it's OnPrem, you've certainly got a certain line of defense that's trying to break through. But, you know, you're in the open world there. Obviously with SAS applications in the cloud, it's not a case of if, but when, and it's, and it's gonna continue to get, you know, more and more prevalent within corporations. There's always gonna be those attack factors that they find the, the flash wounds that they can attack to break through. What we are concentrating on is that resiliency, that ability for customers to recover at speed. We've done that with our traditional appliances from our heritage OnPrem. We continue to do that with regard to resiliency at speed with our customers in the cloud, with partners like aws >>For sure. Almost done. Give me your 30 seconds on AWS and Veritas. >>We've had a partnership for the better part of 10 years. It's incredible when you think about aws, where they released the elastic compute back in 2006, right? We've been delivering data protection, a data management solutions for, for the better part of 30 years, right? So, so we're, we're Junos in our space. We're the leader in, in data protection and enterprise data protection. We were on-prem. We, we continue to be in the cloud as AWS was with the cloud service provided. So the synergies are incredible. About 80 to 85% of our, our joint customers are the same. We take core unique superpowers of aws, like AWS outposts and AWS Glacier Instant retrieval, for example, those core technologies and incorporate them into our products as we go to Mark. And so we released a core technology a few months ago, we call it ultra recovery vault. And it's an air gap, a mutable storage, worm storage, right Once, right? You can't change it even when the bad actors try to get in. They're independent from the customer's tenant and aws. So we manage it as a managed backup service for our customers. Got it. And so our customers are using that to really help them with their ransomware. So it's been a tremendous partnership with AWS >>Standing 10 years of accounting. Last question for you, Rick. You got a billboard on the 1 0 1 in Santa Clara, right? By the fancy Verto >>1 0 1? >>Yeah. Right. Well, there's no traffic. What does that billboard say? What's that bumper sticker about? Vertus, >>I think, I think the billboard would say, welcome to the new Veritas. This is not your grandfather's old mobile. We've done a phenomenal job in, in the last, particularly the last three or four years, to really reinvent ourselves in the cloud and the investments that we made are really paying off for our customers today. So I'm excited to be part of this journey and excited to talk to you guys today. >>Love it. Not your grandfather's Veritas. Rick, thank you so much for joining Paula, me on the forgot talking about what you guys are doing, how you're helping customers, really established that cyber of resiliency, which is absolutely critical these days. We appreciate your >>Time. My pleasure. Thank you so much. >>All right, for our guest and Paul Gilland, I'm Lisa Martin, you're watching the Queue, which as you know is the leader in live enterprise and emerging check coverage.

(upbeat music) >> We're here on theCube covering AWS Storage Day 2022. Kevin Miller joins us. He's the vice president and general manager of Amazon S3. Hello, Kevin, good to see you again. >> Hey Dave, it's great to see you as always. >> It seems like just yesterday we were celebrating the 15th anniversary of S3, and of course the launch of the modern public cloud, which started there. You know, when you think back Kevin, over the past year, what are some of the trends that you're seeing and hearing from customers? What do they want to see AWS focus more on? What's the direction that you're setting? >> Yeah, well Dave, really I think there's probably three trends that we're seeing really pop this year. I think one just given the kind of macroeconomic situation right now is cost optimization. That's not a surprise. Everyone's just taking a closer look at what they're using, and where they might be able to pair back. And you know, I think that's a place that obviously S3 has a long history of helping customers save money. Whether it's through our new storage classes, things like our Glacier Instant Retrieval, storage class that we launched to reinvent last year. Or things like our S3 storage lens capability to really dig in and help customers identify where their costs are are being spent. But so certainly every, you know, a lot of customers are focused on that right now, and for obvious reasons. I think the second thing that we're seeing is, just a real focus on simplicity. And it kind of goes hand in hand with cost optimization, because what a lot of customers are looking for is, how do I take the staff that I have, and do more this year. Right, continue to innovate, continue to bring new applications or top line generating revenue applications to the market, but not have to add a lot of extra headcount to do that. And so, what they're looking for is management and simplicity. How do I have all of this IT infrastructure, and not have to have people spending a lot of their time going into kind of routine maintenance and operations. And so that's an area that we're spending a lot of time. We think we have a lot of capability today, but looking at ways that we can continue to simplify, make it easier for customers to manage their infrastructure. Things like our S3 intelligent tiering storage class, which just automatically gives cost savings for data that's not routinely accessed. And so that's a big focus for us this year as well. And then I think the last and probably third thing I would highlight is an emerging theme or it's been a theme, but really continuing to increase in volume, is all around sustainability. And you know, our customers are looking for us to give them the data and the assurances for them, for their own reports and their own understanding of how sustainable is my infrastructure. And so within AWS, of course, you know we're on a path towards operating with 100% renewable energy by 2025. As well as helping the overall Amazon goal of achieving net zero carbon by 2040. So those are some big lofty goals. We've been giving customers greater insights with our carbon footprint tool. And we think that, you know the cloud continues to be just a great place to run and reduce customer's carbon footprint for the similar you know, storage capacity or similar compute capacity. But that's just going to continue to be a trend and a theme that we're looking at ways that we can continue to help customers do more to aggressively drive down their carbon footprint. >> I mean, it makes sense. It's like you're partnering up with the cloud, you know, you did same thing on security, you know, there's that shared responsibility model, same thing now with ESG. And on the macro it's interesting Kevin, this is the first time I can remember where, you know it used to be, if there's a downturn it's cost optimization, you go to simplicity. But at the same time with digital, you know, the rush to digital, people still are thinking about, okay how do I invest in the future? So but let's focus on cost for a moment then we'll come back to sort of the data value. Can you tell us how AWS helps customers save on storage, you know, beyond just the price per terabyte actions that you could take. I mean I love that, you guys should keep doing that. >> Absolutely. >> But what other knobs are you turning? >> Yeah, right and we've had obviously something like 15 cost reductions or price reductions over the years, and we're just going to continue to use that lever where we can, but it's things like the launch of our Glacier Instant Retrieval storage class that we did last year at Reinvent, where that's now you know, 4/10ths of a cent per gigabyte month. For data that customers access pretty infrequently maybe a few times a year, but they can now access that data immediately and just pay a small retrieval fee when they access that data. And so that's an example of a new capability that reduces customer's total cost of ownership, but is not just a straight up price reduction. I mentioned S3 Intelligent-Tiering, that's another case where, you know, when we launch Glacier Instant Retrieval, we integrated that with Intelligent-Tiering as well. So we have the archive instant access tier within Intelligent-Tiering. And so now data that's not accessed for 90 days is just automatically put into AIA and and then results in a reduced storage cost to customers. So again, leaning into this idea that customers are telling us, "Just do, you know what should be done "for my data to help me reduce cost, can you just do it, "and sort of give me the right defaults." And that's what we're trying to do with things like Intelligent-Tiering. We've also, you know, outside of the S3 part of our portfolio, we've been adding similar kinds of capabilities within some of our file services. So things like our, you know elastic file service launched a one zone storage class as well as an intelligent tiering capability to just automatically help customers save money. I think in some cases up to 92% on their their EFS storage costs with this automatic intelligent tiering capability. And then the last thing I would say is that we also are just continuing to help customers in other ways, like I said, our storage lens is a great way for customers to really dig in and figure out. 'Cause you know, often customers will find that they may have, you know, certain data sets that someone's forgotten about or, they're capturing more data than they expected perhaps in a logging application or something that ends up generating a lot more data than they expected. And so storage lens helps them really zoom in very quickly on, you know this is the data, here's how frequently it's being accessed and then they can make decisions about use that data I keep, how long do I keep it? Maybe that's good candidates to move down into one of our very cold storage classes like Glacier Deep Archive, where they they still have the data, but they don't expect to need to actively retrieve it on a regular basis. >> SDL bromide, if you can measure it, you can manage it. So if I can see it, visualize it, that I can take actions. When you think about S3- >> That's right. it's always been great for archival workloads but you made some updates to Glacier that changed the way that we maybe think about archive data. Can you talk about those changes specifically, what it means for how customers should leverage AWS services going forward? >> Yeah, and actually, you know, Glacier's coming up on its 10 year anniversary in August, so we're pretty excited about that. And you know, but there's just been a real increase in the pace of innovation, I think over the last three or four years there. So we launched the Glacier Deep Archive capability in 2019, 2018, I guess it was. And then we launched Glacier Instant Retrieval of course last year. So really what we're seeing is we now have three storage classes that cover are part of the Glacier family. So everything from millisecond retrieval for that data, that needs to be accessed quickly when it is accessed, but isn't being accessed, you know, regularly. So maybe a few times a year. And there's a lot of use cases that we're seeing really quickly emerge for that. Everything from, you know, user generated content like photos and videos, to big broadcaster archives and particularly in media and entertainment segment. Seeing a lot of interest in Glaciers Instant Retrieval because that data is pretty cold on a regular basis. But when they want to access it, they want a huge amount of data, petabytes of data potentially back within seconds, and that's the capability we can provide with Glacier Instant Retrieval. And then on the other end of the spectrum, with Glacier Deep Archive, again we have customers that have huge archives of data that they be looking to have that 3-AZ durability that we provide with Glacier, and make sure that data is protected. But really, you know expect to access it once a year if ever. Now it could be a backup copy of data or secondary or tertiary copy of data, could be data that they just don't have an active use for it. And I think that's one of the things we're starting to see grow a lot, is customers that have shared data sets where they may not need that data right now but they do want to keep it because as they think about, again these like new applications that can drive top line growth, they're finding that they may go back to that data six months or nine months from now and start to really actively use it. So if they want that option value to keep that data so they can use it down the road, Glacier Deep Archive, or Glacier Flexible Retrieval, which is kind of our storage class right in the middle of the road. Those are great options for customers to keep the data, keep it safe and secure, but then have it, you know pretty accessible when they're ready to get it back. >> Got it, thank you for that. So, okay, so customers have choices. I want to get into some of the competitive differentiators. And of course we were talking earlier about cost optimization, which is obviously an important topic given the macro environment you know, but there's more. And so help us understand what's different about AWS in terms of helping customers get value from their data, cost reduction as a component of value, part of the TCO, for sure. But just beyond being a cloud bit bucket, you know just a storage container in the cloud, what are some of the differentiators that you can talk to? >> Yeah, well Dave, I mean, I think that when it comes to value, I think there's tremendous benefits in AWS, well beyond just cost reduction. I think, you know, part of it is S3 now has built, I think, an earned reputation for being resilient, for storing, you know, at massive scale giving customers that confidence that they will be able to scale up. You know, we store more than 200 trillion objects. We regularly peak at over 100 million requests per second. So customers can build on S3 and Glacier with the confidence that we're going to be there to help their applications grow and scale over time. And then I think that in all of the applications both first party and third party, the customers can use, and services that they can use to build modern applications is an incredible benefit. So whether it's all of our serverless offerings, things like Lambda or containers and everything we have to manage that. Or whether it's the deep analytics and machine learning capabilities we have to help really extract, you know value and insight from data in near real time. You know, we're just seeing an incredible number of customers build those kinds of applications where they're processing data and feeding their results right back into their business right away. So I'm just going to briefly mention a couple, like, you know one example is ADP that really helps their customers measure, compare and sort of analyze their workforce. They have a couple petabytes of data, something like 25 billion individual data points and they're just processing that data continuously through their analytics and machine learning applications to then again, give those insights back to their customers. Another good example is AstraZeneca. You know, they are processing petabytes and petabytes of genomic sequencing data. And they have a goal to analyze 2 million genomes over the next four years. And so they're just really scaling up on AWS, both from a pure storage point of view, but more importantly, from all of the compute and analytics capability on top that is really critical to achieving that goal. And then, you know, beyond the first party services we have as I mentioned, it's really our third party, right? The AWS partner network provides customers an incredible range of choice in off the shelf applications that they can quickly provision and make use of the data to drive those business insights. And I think today the APN has something like 100,000 partners over in 150 countries. And we specifically have a storage competency partner where customers can go to get those applications that directly work, you know, on top of their data. And really, like I said, drive some of that insight. So, you know, I think it's that overall benefit of being able to really do a lot more with their data than just have it sit idle. You know, that's where I think we see a lot of customers interested in driving additional value. >> I'm glad you mentioned the ecosystem, and I'm glad you mentioned the storage competency as well. So there are other storage partners that you have, even though you're a head of a big storage division. And then I think there's some other under the cover things too. I've recently wrote, actually have written about this a lot. Things like nitro and rethinking virtualization and how to do, you know offloads. The security that comes, you know fundamentally as part of the platform is, I think architecturally is something that leads the way in the industry for sure. So there's a lot we could unpack, but you've fundamentally changed the storage market over the last 16 years. And again, I've written about this extensively. We used to think about storage in blocks or you got, you know, somebody who's really good in files, there were companies that dominated each space with legacy on-prem storage. You know, when you think about object storage Kevin, it was a niche, right? It was something used for archival, it was known for its simple, get put syntax, great for cheap and deep storage, and S3 changed that. Why do you think that's happened and S3 has evolved, the object has evolved the way it has, and what's the future hold for S3? >> Yeah I mean, you know, Dave, I think that probably the biggest overall trend there is that customers are looking to build cloud native applications. Where as much of that application is managed as they can have. They don't want to have to spend time managing the underlying infrastructure, the compute and storage and everything that goes around it. And so a fully managed service like S3, where there's no provisioning storage capacity, there's, you know we provide the resiliency and the durability that just really resonates with customers. And I think that increasingly, customers are seeing that they want to innovate across the entire range of business. So it's not about a central IT team anymore, it's about engineers that are embedded within lines of business, innovating around what is critical to achieve their business results. So, you know, if they're in a manufacturing segment, how can we pull data from sensors and other instrumentation off of our equipment and then make better decisions about when we need to do predictive maintenance, how quickly we can run our manufacturing line, looking for inefficiencies. And so we've developed around our managed offerings like S3, we've just developed, you know, customers who are investing and executing on plans and you know transformations. That really give them, you know put digital technology directly into the line of business that they're looking for. And I think that trend is just going to continue. People sometimes ask me, well "I mean, 16 years, you know, isn't S3 done?" And I would say, "By no stretcher are we done." We have plenty of feedback from customers on ways that we can continue to simplify, reduce the kinds of things they need to do, when they're looking for example and rolling out new security policies and parameters across their entire organization. So raising the bar there, finding, you know, raising the bar on how they can efficiently manage their storage and reduce costs. So I think we have plenty of innovation ahead of us to continue to help customers provide that fully managed capability. >> Yeah I often say Kevin, the next 10 years ain't going to be like the last in cloud. So I really thank you for coming on theCube and sharing your insights, really appreciate it. >> Absolutely Dave, thanks for having me. >> You're welcome. Okay keep it right there for more coverage of AWS Storage Day 2022 in theCube. (calm bright music)

>>Hello. Welcome back to our super cloud 22 event. I'm John F host the cue with my co-host Dave ante. Extracting the signal from noise. We're proud to have two amazing cube alumnis here. We got Sanja Putin. Who's now the CEO of cohesive the emo Aaron who's the CTO. Co-founder also former CEO Cub alumni. The father of hyper-converged welcome back to the cube I endorsed the >>Cloud. Absolutely. Is the father. Great >>To see you guys. Thank thanks for coming on and perfect timing. The new job taking over that. The helm Mo it at cohesive big news, but part of super cloud, we wanna dig into it. Thanks for coming on. >>Thank you for having >>Us here. So first of all, we'll get into super before we get into the Supercloud. I want to just get the thoughts on the move Sanjay. We've been following your career since 2010. You've been a cube alumni from that point, we followed that your career. Why cohesive? Why now? >>Yeah, John David, thank you first and all for having us here, and it's great to be at your event. You know, when I left VMware last year, I took some time off just really primarily. I hadn't had a sabbatical in probably 18 years. I joined two boards, Phillips and sneak, and then, you know, started just invest and help entrepreneurs. Most of them were, you know, Indian Americans like me who were had great tech, were looking for the kind of go to market connections. And it was just a wonderful year to just de to unwind a bit. And along the, the way came CEO calls. And I'd asked myself, the question is the tech the best in the industry? Could you see value creation that was signi significant and you know, three, four months ago, Mohit and Carl Eschenbach and a few of the board members of cohesive called me and walk me through Mo's decision, which he'll talk about in a second. And we spent the last few months getting to know him, and he's everything you describe. He's not just the father of hyperconverge. And he wrote the Google file system, wicked smart, built a tech platform better than that second time. But we had to really kind of walk through the chemistry between us, which we did in long walks in, in, you know, discrete places so that people wouldn't find us in a Starbucks and start gossiping. So >>Why Sanjay? There you go. >>Actually, I should say it's a combination of two different decisions. The first one was to, for me to take a different role and I run the company as a CEO for, for nine years. And, you know, as a, as a technologist, I always like, you know, going deep into technology at the same time, the CEO duties require a lot of breadth, right? You're talking to customers, you're talking to partners, you're doing so much. And with the way we've been growing the with, you know, we've been fortunate, it was becoming hard to balance both. It's really also not fair to the company. Yeah. So I opted to do the depth job, you know, be the visionary, be the technologist. And that was the first decision to bring a CEO, a great CEO from outside. >>And I saw your video on the site. You said it was your decision. Yes. Go ahead. I have to ask you, cuz this is a real big transition for founders and you know, I have founder artists cuz everyone, you know, calls me that. But being the founder of a company, it's always hard to let go. I mean nine years as CEO, it's not like you had a, you had a great run. So this was it timing for you? Was it, was it a structural shift, like at super cloud, we're talking about a major shift that's happening right now in the industry. Was it a balance issue? Was it more if you wanted to get back in and in the tech >>Look, I, I also wanna answer, you know, why Sanja, but, but I'll address your question first. I always put the company first what's right for the company. Is it for me to start get stuck the co seat and try to juggle this depth and Brad simultaneously. I mean, I can stroke my ego a little bit there, but it's not good for the company. What's best for the company. You know, I'm a technologist. How about I oversee the technology part in partnership with so many great people I have in the company and I bring someone kick ass to be the CEO. And so then that was the second decision. Why Sanja when Sanjay, you know, is a very well known figure. He's managed billions of dollars of business in VMware. You know, been there, done that has, you know, some of the biggest, you know, people in the industry on his speed dial, you know, we were really fortunate to have someone like that, come in and accept the role of the CEO of cohesive. I think we can take the company to new Heights and I'm looking forward to my partnership with, with Sanja on this. >>It it's we, we called it the splash brothers and >>The, >>In the vernacular. It doesn't matter who gets the ball, whether it's step clay, we shoot. And I think if you look at some of the great partnerships, whether it was gates bomber, there, plenty of history of this, where a founder and a someone who was, it has to be complimentary skills. If I was a technologist myself and wanted to code we'd clash. Yeah. But I think this was really a match me in heaven because he, he can, I want him to keep innovating and building the best platform for today in the future. And our customers tell one customer told me, this is the best tech they've seen since VMware, 20 years ago, AWS, 10 years ago. And most recently this was a global 100 big customers. So I feel like this combination, now we have to show that it works. It's, you know, it's been three, four months. My getting to know him, you know, I'm day eight on the job, but I'm loving it. >>Well, it's a sluman model too. It's more modern example. You saw, he did it with Fred Ludy at service now. Yes. And, and of course at, at snowflake, yeah. And his book, you read his book. I dunno if you've read his book, amp it up, but app it up. And he says, I always you'll love this. Give great deference to the founder. Always show great respect. Right. And for good reason. So >>In fact, I mean you could talk to him, you actually met to >>Frank. I actually, you know, a month or so back, I actually had dinner with him in his ranch in Moana. And I posed the question. There was a number of CEOs that went there and I posed him the question. So Frank, you know, many of us, we grow being deaf guys, you know? And eventually when we take on the home of our CEO, we have to do breadth. How do you do it? And he's like, well, let me tell you, I was never a death guy. I'm a breath guy. >>I'm like, >>That's my answer. Yeah. >>So, so I >>Want the short story. So the day I got the job, I, I got a text from Frank and I said, what's your advice the first time CEO, three words, amp it up, >>Amp it up. Right? Yeah. >>And so you're always on brand, man. >>So you're an amazing operator. You've proven that time and time again at SAP, VMware, et cetera, you feel like now you, you, you wanna do both of those skills. You got the board and you got the operations cuz you look, you know, look at sloop when he's got Scarelli wherever he goes, he brings Scarelli with him as sort of the operator. How, how do you, how are you thinking >>About that? I mean it's early days, but yeah. Yeah. Small. I mean I've, you know, when I was, you know, it was 35,000 people at VMware, 80, 90,000 people at SAP, a really good run. The SAP run was 10 to 20 billion innovative products, especially in analytics and VMware six to 12 end user computing cloud. So I learned a lot. I think the company, you know, being about 2000 employees plus not to mayor tomorrow, but over the course next year I can meet everybody. Right? So first off the executive team, 10 of us, we're, we're building more and more cohesiveness if I could use that word between us, which is great, the next, you know, layers of VPs and every manager, I think that's possible. So I I'm a people person and a customer person. So I think when you take that sort of extroverted mindset, we'll bring energy to the workforce to, to retain the best and then recruit the best. >>And you know, even just the week we, we were announced that this announcement happened. Our website traffic went through the roof, the highest it's ever been, lots of resumes coming in. So, and then lots of customer engagement. So I think we'll take this, but I, I feel very good about the possibilities, because see, for me, I didn't wanna walk into the company to a company where the technology risk was high. Okay. I feel like that I can go to bed at night and the technology risk is low. This guy's gonna run a machine at the current and the future. And I'm hearing that from customers. Now, what I gotta do is get the, the amp it up part on the go to market. I know a little thing or too about >>That. You've got that down. I think the partnership is really key here. And again, nine use the CEO and then Sanja points to our super cloud trend that we've been looking at, which is there's another wave happening. There's a structural change in real time happening now, cloud one was done. We saw that transition, AWS cloud native now cloud native with an kind of operating system kind of vibe going on with on-premise hybrid edge. People say multi-cloud, but we're looking at this as an opportunity for companies like cohesive to go to the next level. So I gotta ask you guys, what do you see as structural change right now in the industry? That's disruptive. People are using cloud and scale and data to refactor their business models, change modern cases with cloud native. How are you guys looking at this next structural change that's happening right now? Yeah, >>I'll take that. So, so I'll start by saying that. Number one, data is the new oil and number two data is exploding, right? Every year data just grows like crazy managing data is becoming harder and harder. You mentioned some of those, right? There's so many cloud options available. Cloud one different vendors have different clouds. There is still on-prem there's edge infrastructure. And the number one problem that happens is our data is getting fragmented all over the place and managing so many fragments of data is getting harder and harder even within a cloud or within on-prem or within edge data is fragmented. Right? Number two, I think the hackers out there have realized that, you know, to make money, it's no longer necessary to Rob banks. They can actually see steal the data. So ransomware attacks on the rise it's become a boardroom level discussion. They say there's a ransomware attack happening every 11 seconds or so. Right? So protecting your data has become very important security data. Security has become very important. Compliance is important, right? So people are looking for data management solutions, the next gen data management platform that can really provide all this stuff. And that's what cohesive is about. >>What's the difference between data management and backup. Explain that >>Backup is just an entry point. That's one use case. I wanna draw an analogy. Let's draw an analogy to my former company, Google right? Google started by doing Google search, but is Google really just a search engine. They've built a platform that can do multiple things. You know, they might have started with search, but then they went down to roll out Google maps and Gmail and YouTube and so many other things on that platform. So similarly backups might be just the first use case, but it's really about that platform on which you can do more with the data that's next gen data management. >>But, but you am, I correct. You don't consider yourself a security company. One of your competitors is actually pivoting and in positioning themselves as a security company, I've always felt like data management, backup and recovery data protection is an adjacency to security, but those two worlds are coming together. How do you see >>It? Yeah. The way I see it is that security is part of data management. You start maybe by backing with data, but then you secure it and then you do more with that data. If you're only doing security, then you're just securing the data. You, you gotta do more with the data. So data management is much bigger. So >>It's a security is a subset of data. I mean, there you go. Big TA Sanjay. >>Well, I mean I've, and I, I, I I'd agree. And I actually, we don't get into that debate. You know, I've told the company, listen, we'll figure that out. Cuz who cares about the positioning at the bottom? My email, I say we are data management and data security company. Okay. Now what's the best word that describes three nouns, which I think we're gonna do management security and analytics. Okay. He showed me a beautiful diagram, went to his home in the course of one of these, you know, discrete conversations. And this was, I mean, he's done this before. Many, if you watch on YouTube, he showed me a picture of an ice big iceberg. And he said, listen, you know, if you look at companies like snowflake and data bricks, they're doing the management security and mostly analytics of data. That's the top of the iceberg, the stuff you see. >>But a lot of the stuff that's get backed archive is the bottom of the iceberg that you don't see. And you try to, if you try to ask a question on age data, the it guy will say, get a ticket. I'll come back with three days. I'll UNIV the data rehydrate and then you'll put it into a database. And you can think now imagine that you could do live searches analytics on, on age data that's analytics. So I think the management, the security, the analytics of, you know, if you wanna call it secondary data or backed up data or data, that's not hot and live warm, colder is a huge opportunity. Now, what do you wanna call one phrase that describes all of it. Do you call that superpower management security? Okay, whatever you wanna call it. I view it as saying, listen, let's build a platform. >>Some people call Google, a search company. People, some people call Google and information company and we just have to go and pursue every CIO and every CSO that has a management and a security and do course analytics problem. And that's what we're doing. And when I talk to the, you know, I didn't talk to all the 3000 customers, but the biggest customers and I was doing diligence. They're like this thing has got enormous potential. Okay. And we just have to now go focus, get every fortune 1000 company to pick us because this problem, even the first use case you talk back up is a little bit like, you know, razor blades and soap you've needed. You needed it 30 years ago and you'll need it for 30 years. It's just that the tools that were built in the last generation that were companies formed in 1990s, one of them I worked for years ago are aids are not built for the cloud. So I think this is a tremendous opportunity where many of those, those, those nos management security analytics will become part of what we do. And we'll come up with the right phrase for what the companies and do course >>Sanjay. So ma and Sanja. So given that given that's this Google transition, I like that example search was a data problem. They got sequenced to a broader market opportunity. What super cloud we trying to tease out is what does that change over from a data standpoint, cuz now the operating environments change has become more complex and the enterprises are savvy. Developers are savvy. Now they want, they want SAS solutions. They want freemium and expanding. They're gonna drive the operations agenda with DevOps. So what is the complexity that needs to be abstracted away? How do you see that moment? Because this is what people are talking about. They're saying security's built in, driven by developers. Developers are driving operations behavior. So what is the shift? Where do you guys see this new? Yeah. Expansive for cohesive. How do you fit into super cloud? >>So let me build up from that entry point. Maybe back up to what you're saying is the super cloud, right? Let me draw that journey. So let's say the legacy players are just doing backups. How, how sad is it that you have one silo sitting there just for peace of mind as an insurance policy and you do nothing with the data. If you have to do something with the data, you have to build another silo, you have to build another copy. You have to manage it separately. Right. So clearly that's a little bit brain damaged. Right. So, okay. So now you take a little bit of, you know, newer vendors who may take that backup platform and do a little bit more with that. Maybe they provide security, but your problem still remains. How do you do more with the data? How do you do some analytics? >>Like he's saying, right. How do you test development on that? How do you migrate the data to the cloud? How do you manage it? The data at scale? How do you do you provide a unified experience across, across multiple cloud, which you're calling the super cloud. That's where cohesive goes. So what we do, we provide a platform, right? We have tentacles in on-prem in each of the clouds. And on top of that, it looks like one platform that you manage. We have a single control plane, a UI. If you may, a single pin of glass, if, if you may, that our customers can use to manage all of it. And now it looks, starts looking like one platform. You mentioned Google, do you, when you go to, you know, kind Google search or a URL, do you really care? What happens behind the scenes mean behind the scenes? Google's built a platform that spans the whole world. No, >>But it's interesting. What's behind the scenes. It's a beautiful now. And I would say, listen, one other thing to pull on Dave, on the security part, I saw a lot of vendors this day in this space, white washing a security message on top of backup. Okay. And CSO, see through that, they'll offer warranties and guarantees or whatever, have you of X million dollars with a lot of caveats, which will never paid because it's like escape clause here. We won't pay it. Yeah. And, and what people really want is a scalable solution that works. And you know, we can match every warranty that's easy. And what I heard was this was the most scalable solution at scale. And that's why you have to approach this with a Google type mindset. I love the fact that every time you listen to sun pitch, I would, what, what I like about him, the most common word to use is scale. >>We do things at scale. So I found that him and AUR and some of the early Google people who come into the company had thought about scale. And, and even me it's like day eight. I found even the non-tech pieces of it. The processes that, you know, these guys are built for simple things in some cases were better than some of the things I saw are bigger companies I'd been used to. So we just have to continue, you know, building a scale platform with the enterprise. And then our cloud product is gonna be the simple solution for the masses. And my view of the world is there's 5,000 big companies and 5 million small companies we'll push the 5 million small companies as the cloud. Okay. Amazon's an investor in the company. AWS is a big partner. We'll talk about I'm sure knowing John's interest in that area, but that's a cloud play and that's gonna go to the cloud really fast. You not build you're in the marketplace, you're in the marketplace. I mean, maybe talk about the history of the Amazon relationship investing and all that. >>Yeah, absolutely. So in two years back late 2020, we, you know, in collaboration with AWS who also by the way is an investor now. And in cohesive, we rolled out what we call data management as a service. It's our SaaS service where we run our software in the cloud. And literally all customers have to do is just go there and sign on, right? They don't have to manage any infrastructure and stuff. What's nice is they can then combine that with, you know, software that they might have bought from cohesive. And it still looks like one platform. So what I'm trying to say is that they get a choice of the, of the way they wanna consume our software. They can consume it as a SAS service in the cloud. They can buy our software, manage it themselves, offload it to a partner on premises or what have you. But it still looks like that one platform, what you're calling a Supercloud >>Yeah. And developers are saying, they want the bag of Legos to compose their solutions. That's the Nirvana they want to get there. So that's, it has to look the same. >>Well, what is it? What we're calling a Superlo can we, can we test that for a second? So data management and service could span AWS and on-prem with the identical experience. So I guess I would call that a Supercloud I presume it's not gonna through AWS span multiple clouds, but, but >>Why not? >>Well, well interesting cuz we had this, I mean, so, okay. So we could in the future, it doesn't today. Well, >>David enough kind of pause for a second. Everything that we do there, if we do it will be customer driven. So there might be some customers I'll give you one Walmart that may want to store the data in a non AWS cloud risk cuz they're competitors. Right. So, but the control plane could still be in, in, in the way we built it, but the data might be stored somewhere else. >>What about, what about a on-prem customer? Who says, Hey, I, I like cohesive. I've now got multiple clouds. I want the identical experience across clouds. Yeah. Okay. So, so can you do that today? How do you do that today? Can we talk >>About that? Yeah. So basically think roughly about the split between the data plane and the control plane, the data plane is, you know, our cohesive clusters that could be sitting on premises that could be sitting in multiple data centers or you can run an instance of that cluster in the cloud, whichever cloud you choose. Right. That's what he was referring to as the data plane. So collectively all these clusters from the data plane, right? They stored the data, but it can all be managed using the control plane. So you still get that single image, the single experience across all clouds. And by the way, the, the, the, the cloud vendor does actually benefit because here's a customer. He mentioned a customer that may not wanna go to AWS, but when they get the data plane on a different cloud, whether it's Azure, whether it's the Google cloud, they then get data management services. Maybe they're able to replicate the data over to AWS. So AWS also gains. >>And your deployment model is you instantiate the cohesive stack on each of the regions and clouds, is that correct? And you building essentially, >>It all happens behind the scenes. That's right. You know, just like Google probably has their tentacles all over the world. We will instantiate and then make it all look like one platform. >>I mean, you should really think it's like a human body, right? The control planes, the head. Okay. And that controls everything. The data plane is large because it's a lot of the data, right? It's the rest of the body, that data plane could be wherever you want it to be. Traditionally, the part the old days was tape. Then you got disk. Now you got multiple clouds. So that's the way we think about it. And there on that piece of it will be neutral, right? We should be multi-cloud to the data plane being every single place. Cause it's customer demand. Where do you want your store data? Air gapped. On-prem no problem. We'll work with Dell. Okay. You wanna be in a particular cloud, AWS we'll work then optimized with S3 and glacier. So this is where I think the, the path to a multi-cloud or Supercloud is to be customer driven, but the control plane sits in Amazon. So >>We're blessed to have a number of, you know, technical geniuses in here. So earlier we were speaking to Ben wa deja VI, and what they do is different. They don't instantiate an individual, you know, regions. What they do is of a single global. Is there a, is there an advantage of doing it the way the cohesive does it in terms of simplicity or how do you see that? Is that a future direction for you from a technology standpoint? What are the trade offs there? >>So you want to be where the data is when you said single global, I take it that they run somewhere and the data has to go there. And in this day age, correct >>Said that. He said, you gotta move that in this >>Day and >>Age query that's, you know, across regions, look >>In this day and age with the way the data is growing, the way it is, it's hard to move around the data. It's much easier to move around the competition. And in these instances, what have you, so let the data be where it is and you manage it right there. >>So that's the advantage of instantiating in multiple regions. As you don't have to move the >>Data cost, we have the philosophy we call it. Let's bring the, the computation to the data rather than the data to >>The competition and the same security model, same governance model, same. How do you, how do you federate that? >>So it's all based on policies. You know, this overarching platform controlled by, by the control plane, you just, our customers just put in the policies and then the underlying nuts and bolts just take care >>Of, you know, it's when I first heard and start, I started watching some of his old videos, ACE really like hyperconverged brought to secondary storage. In fact, he said, oh yeah, that's great. You got it. Because I first called this idea, hyperconverged secondary storage, because the idea of him inventing hyperconverge was bringing compute to storage. It had never been done. I mean, you had the kind of big VC stuff, but these guys were the first to bring that hyperconverge at, at Nutanix. So I think this is that same idea of bringing computer storage, but now applied not to the warm data, but to the rest of the data, including a >>Lot of, what about developers? What's, what's your relationship with developers? >>Maybe you talk about the marketplace and everything >>He's yeah. And I'm, I'm curious as to do you have a PAs layer, what we call super PAs layer to create an identical developer experience across your Supercloud. I'm gonna my >>Term. So we want our customers not just to benefit from the software that we write. We also want them to benefit from, you know, software that's written by developers by third party people and so on and so forth. So we also support a marketplace on the platform where you can download apps from third party developers and run them on this platform. There's a, a number of successful apps. There's one, you know, look like I said, our entry point might be backups, but even when backups, we don't do everything. Look, for instance, we don't backup mainframes. There is a, a company we partner with, you know, and their software can run in our marketplace. And it's actually used by many, many of our financial customers. So our customers don't get, just get the benefit of what we build, but they also get the benefit of what third parties build. Another analogy I like to draw. You can tell. And front of analogy is I drew an analogy to hyperscale is like Google. Yeah. The second analogy I like to draw is that to a simple smartphone, right? A smartphone starts off by being a great phone. But beyond that, it's also a GPS player. It's a, it's a, it's a music player. It's a camera, it's a flashlight. And it also has a marketplace from where you can download apps and extend the power of that platform. >>Is that a, can we think of that as a PAs layer or no? Is it really not? You can, okay. You can say, is it purpose built for what you're the problem that you're trying to solve? >>So we, we just built APIs. Yeah. Right. We have an SDK that developers can use. And through those APIs, they get to leverage the underlying services that exist on the platform. And now developers can use that to take advantage of all that stuff. >>And it was, that was a key factor for me too. Cause I, what I, you know, I've studied all the six, seven players that sort of so-called leaders. Nobody had a developer ecosystem, nobody. Right? The old folks were built for the hardware era, but anyones were built for the cloud to it didn't have any partners were building on their platform. So I felt for me listen, and that the example of, you know, model nine rights, the name of the company that does back up. So there's, there's companies that are built on and there's a number of others. So our goal is to have a big tent, David, to everybody in the ecosystem to partner with us, to build on this platform. And, and that may take over time, but that's the way we're build >>It. And you have a metadata layer too, that has the intelligence >>To correct. It's all abstract. That that's right. So it's a combination of data and metadata. We have lots of metadata that keeps track of where the data is. You know, it allows you to index the data you can do quick searches. You can actually, you, we talking about the control plan from that >>Tracing, >>You can inject a search that'll through search throughout your multi-cloud environment, right? The super cloud that you call it. We have all that, all that goodness sounds >>Like a Supercloud John. >>Yeah. I mean, data tracing involved can trace the data lineage. >>You, you can trace the data lineage. So we, you know, provide, you know, compliance and stuff. So you can, >>All right. So my final question to wrap up, we guys, first of all, thanks for coming on. I know you're super busy, San Jose. We, we know what you're gonna do. You're gonna amp it up and, you know, knock all your numbers out. Think you always do. But what I'm interested in, what you're gonna jump into, cuz now you're gonna have the creative license to jump in to the product, the platform there has to be the next level in your mind. Can you share your thoughts on where this goes next? Love the control plane, separate out from the data plane. I think that plays well for super. How >>Much time do you have John? This guy's got, he's got a wealth. Ditis keep >>Going. Mark. Give us the most important thing you're gonna focus on. That kind of brings the super cloud and vision together. >>Yeah. Right away. I'm gonna, perhaps I, I can ion into two things. The first one is I like to call it building the, the machine, the system, right. Just to draw an analogy. Look, I draw an analogy to the us traffic system. People from all walks of life, rich, poor Democrats, Republicans, you know, different states. They all work in the, the traffic system and we drive well, right. It's a system that just works. Whereas in some other countries, you know, the system doesn't work. >>We know, >>We know a few of those. >>It's not about works. It's not about the people. It's the same people who would go from here to those countries and, and not dry. Well, so it's all about the system. So the first thing I, I have my sights on is to really strengthen the system that we have in our research development to make it a machine. I mean, it functions quite well even today, but wanna take it to the next level. Right. So that I wanna get to a point where innovation just happens in the grassroots. And it just, just like >>We automations scale optic brings all, >>Just happens without anyone overseeing it. Anyone there's no single point of bottleneck. I don't have to go take any diving catches or have you, there are people just working, you know, in a decentralized fashion and innovation just happens. Yeah. The second thing I work on of course is, you know, my heart and soul is in, you know, driving the vision, you know, the next level. And that of course is part of it. So those are the two things >>We heard from all day in our super cloud event that there's a need for an, an operating system. Yeah. Whether that's defacto standard or open. Correct. Do you see a consortium around the corner potentially to bring people together so that things could work together? Cuz there really isn't no stand there. Isn't a standards bodies. Now we have great hyperscale growth. We have on-prem we got the super cloud thing happening >>And it's a, it's kind of like what is an operating system? Operating system exposes some APIs that the applications can then use. And if you think about what we've been trying to do with the marketplace, right, we've built a huge platform and that platform is exposed through APIs. That third party developers can use. Right? And even we, when we, you know, built more and more services on top, you know, we rolled our D as we rolled out, backup as a service and a ready for thing security as a service governance, as a service, they're using those APIs. So we are building a distributor, putting systems of sorts. >>Well, congratulations on a great journey. Sanja. Congratulations on taking the hem. Thank you've got ball control. Now you're gonna be calling the ball cohesive as they say, it's, >>It's a team. It's, you know, I think I like that African phrase. If you want to go fast, you go alone. If you wanna go far, you go together. So I've always operated with the best deal. I'm so fortunate. This is to me like a dream come true because I always thought I wanted to work with a technologist that frees me up to do what I like. I mean, I started as an engineer, but that's not what I am today. Right? Yeah. So I do understand the product and this category I think is right for disruption. So I feel excited, you know, it's changing growing. Yeah. No. And it's a, it requires innovation with a cloud scale mindset and you guys have been great friends through the years. >>We'll be, we'll be watching you. >>I think it's not only disruption. It's creation. Yeah. There's a lot of white space that just hasn't been created yet. >>You're gonna have to, and you know, the proof, isn't the pudding. Yeah. You already have five of the biggest 10 financial institutions in the us and our customers. 25% of the fortune 500 users, us two of the biggest five pharmaceutical companies in the world use us. Probably, you know, some of the biggest companies, you know, the cars you have, you know, out there probably are customers. So it's already happening. >>I know you got an IPO filed confidentially. I know you can't talk numbers, but I can tell by your confidence, you're feeling good right now we are >>Feeling >>Good. Yeah. One day, one week, one month at a time. I mean, you just, you know, I like the, you know, Jeff Bezos, Andy jazzy expression, which is, it's always day one, you know, just because you've had success, even, you know, if, if a and when an IPO O makes sense, you just have to stay humble and hungry because you realize, okay, we've had a lot of success in the fortune 1000, but there's a lot of white space that hasn't picked USS yet. So let's go, yeah, there's lots of midmarket account >>Product opportunities are still, >>You know, I just stay humble and hungry and if you've got the team and then, you know, I'm really gonna be working also in the ecosystem. I think there's a lot of very good partners. So lots of ideas brew through >>The head. Okay. Well, thank you so much for coming on our super cloud event and, and, and also doubling up on the news of the new appointment and congratulations on the success guys. Coverage super cloud 22, I'm sure. Dave ante, thanks for watching. Stay tuned for more segments after this break.

(bright upbeat music) >> Welcome back to theCUBE's coverage of VeeamON 2022. We're here at the Aria in Las Vegas. This is day two, Dave Vallante with David Nicholson. You know with theCUBE, we talked about the cloud a lot and the company that started the cloud, AWS. Jeanna James is here. She's the Global Alliance Manager at AWS and a data protection expert. Great to see you. Thanks for coming on theCUBE again. >> Thanks so much for having me, Dave. It's great to be here in person with everyone. >> Yes, you know, we've done a few events live more than a handful. Thanks a lot to AWS. We've done a number. We did the DC Summits. Of course, re:Invent was huge out here last year. That was right in between the sort of variant Omicron hitting. And it was a great, great show. We thought, okay, now we're back. And of course we're kind of back, but we're here and it's good to have you. So Veeam, AWS, I mean, they certainly embrace the cloud. What's your relationship there? >> Yeah, so Veeam is definitely a strong partner with AWS. And as you know, AWS is really a, you know, we have so many different services, and our customers and our partners are looking at how can I leverage those services and how do I back this up, right? Whether they're running things on premises and they want to put a copy of the data into Amazon S3, Amazon S3 Infrequent Access or Amazon S3 Glacier Deep Archive, all of these different technologies, you know Veeam supports them to get a copy from on-prem into AWS. But then the great thing is, you know, it's nice to have a copy of your data in the cloud but you might want to be able to do something with it once it gets there, right? So Veeam supports things like Amazon EC2 and Amazon EKS and EKS Anywhere. So those customers can actually recover their data directly into Amazon EC2 and EKS Anywhere. >> So we, of course, talked a lot about ransomware and that's important in that context of what you just mentioned. What are you seeing with the customers when you talk to them about ransomware? What are they asking AWS to do? Maybe we could start unpacking that a bit. >> Yeah, ransomware is definitely a huge topic today. We're constantly having that conversation. And, you know, five years ago there was a big malware attack that was called the NotPetya virus. And at that time it was based on Petya which was a ransomware virus, and it was designed to go in and, you know, lock in the data but it also went after the backup data, right? So it hold all of that data hostage so that people couldn't recover. Well, NotPetya was based on that but it was worse because it was the seek and destroy virus. So with the ransomware, you can pay a fee and get your data back. But with this NotPetya, it just went in, it propagated itself. It started installing on servers and laptops, anything it could touch and just deleting everything. And at that time, I actually happened to be in the hospital. So hospitals, all types of companies got hit by this attack. And my father had been rushed to the emergency room. I happened to be there. So I saw live what really was happening. And honestly, these network guys were running around shutting down laptops, taking them away from doctors and nurses, shutting off desktops. Putting like taping on pictures that said, do not turn on, right? And then, the nurses and staff were having to kind of take notes. And it was just, it was a mess, it was bad. >> Putting masks on the laptops essentially. >> Yeah, so just-- >> Disinfecting them or trying to. Wow, unplugging things from the network. >> Yes, because, you know, and that attack really demonstrated why you really need a copy of the data in the cloud or somewhere besides tape, right? So what happened at that time is if you lose 10 servers or something, you might be able to recover from tape, but if you lose a hundred or a thousand servers and all of your laptops, all in hours, literally a matter of hours, that is a big event, it's going to take time to recover. And so, you know, if you put a copy of the backup data in Amazon S3 and you can turn on that S3 Object Lock for immutability, you're able to recover in the cloud. >> So, can we go back to this hospital story? 'Cause that takes us inside the disaster potential. So they shut everything down, basically shut down the network so they could figure out what's going on and then fence it off, I presume. So you got, wow, so what happened? First of all, did they have to go manual, I mean? >> They had to do everything manually. It was really a different experience. >> Going back to the 1970s, I mean. >> It was, and they didn't know really how to do it, right? So they basically had kind of yellow notepads and they would take notes. Well, then let's say the doctor took notes, well, then the nurse couldn't read the notes. And even over the PA, you know, there was an announcement and it was pretty funny. Don't send down lab work request with just the last name. We need to know the first name, the last name, and the date of birth. There are multiple Joneses in this hospital so yeah (giggles). >> This is going to sound weird. But so when I was a kid, when you worked retail, if there was a charge for, you know, let's say $5.74 and, you know, they gave you, you know, amount of money, you would give them, you know, the penny back, count up in your head that's 75, give them a quarter and then give them the change. Today, of course, it works differently. The computer tells you, how much change to give. It's like they didn't know what to do. They didn't know how to do it manually 'cause they never had the manual process. >> That's exactly right. Some of the nurses and doctors had never done it manually. >> Wow, okay, so then technically they have to figure out what happened so that takes some time. However they do that. That's kind of not your job, right? I dunno if you can help with that or not. Maybe Amazon has some tooling to do that, probably does. And then you've got to recover from somewhere, not tape ideally. That's like the last resort. You put it on a Chevy Truck, Chevy Truck Access Method called CTAM, ship it in. That takes days, right? If you're lucky. So what's the ideal recovery. I presume it's a local copy somewhere. >> So the ideal-- >> It's fenced. >> In that particular situation, right? They had to really air gap so they couldn't even recover on those servers and things like that-- >> Because everything was infected on on-prem. >> Because everything was just continuing to propagate. So ideally you would have a copy of your data in AWS and you would turn on Object Lock which is the immutability, very simple check mark in Veeam to enable that. And that then you would be able to kick off your restores in Amazon EC2, and start running your business so. >> Yeah, this ties into the discussion of the ransomware survey where, you know, NotPetya was not seeking to extort money, it was seeking to just simply arrive and destroy. In the ransomware survey, some percentage of clients who paid ransom, never got their data back anyway. >> Oh my. >> So you almost have to go into this treating-- >> Huge percentage. >> Yeah, yeah, yeah. >> Like a third. >> Yeah, when you combine the ones where there was no request for ransom, you know, for any extorted funds, and then the ones where people paid but got nothing back. I know Maersk Line, the shipping company is a well studied example of what happened with NotPetya. And it's kind of chilling because what you describe, people running around shutting down laptops because they're seeing all of their peers' screens go black. >> Yes, that's exactly what's happening. >> And then you're done. So that end point is done at that point. >> So we've seen this, I always say there are these milestones in attacks. I mean, Stuxnet proved what a nation state could do and others learned from that, NotPetya, now SolarWinds. And people are freaking out about that because it's like maybe we haven't seen the last of that 'cause that was highly stealth, not a lot of, you know, Russian language in the malware. They would delete a lot of the malware. So very highly sophisticated island hopping, self forming malware. So who knows what's next? We don't know. And so you're saying the ideal is to have an air gap that's physically separate. maybe you can have one locally as well, we've heard about that too, and then you recover from that. What are you seeing in terms of your customers recovering from that? Is it taking minutes, hours, days? >> So that really de depends on the customers SLAs, right? And so with AWS, we offer multiple tiers of storage classes that provide different SLA recovery times, right? So if you're okay with data taking longer to recovery, you can use something like Amazon S3 Glacier Deep Archive. But if it's mission critical data, you probably want to put it in Amazon S3 and turn on that Object Lock for immutability sake. So nothing can be overwritten or deleted. And that way you can kick off your recoveries directly in AWS. >> One of the demos today that we saw, the recovery was exceedingly fast with a very small data loss so that's obviously a higher level SLA. You got to get what you pay for. A lot of businesses need that. I think it was like, I didn't think it was, they said four minutes data loss which is good. I'm glad they didn't say zero data loss 'cause there's really no such thing. So you've got experience, Jeanna, in the data protection business. How have you seen data protection evolve in the last decade and where do you see it going? Because let's face it, I mean when AWS started, okay, it had S3, 15 years ago, 16 years ago, whatever it was. Now, it's got all these tools as you mentioned. So you've learned, you've innovated along with your customers. You listened to your customers. That's your whole thing, customer obsession. >> That's right. >> What are they telling you? What do you see as the future? >> Definitely, we see more and more containerization. So you'll see with the Kasten by Veeam product, right? The ability to protect Amazon EKS, and Amazon EKS Anywhere, we see customers really want to take advantage of the ability to containerize and not have to do as much management, right? So much of what we call undifferentiated heavy lifting, right? So I think you'll see continued innovation in the area of containerization, you know, serverless computing. Obviously with AWS, we have a lot going on with artificial intelligence and machine learning. And, you know, the backup partners, they really have a unique capability in that they do touch a lot of data, right? So I think in the future, you know, things around artificial intelligence and machine learning and data analytics, all of those things could certainly be very applicable for folks like Veeam. >> Yeah, you know, we give a lot of, we acknowledge that backup is different from recovery but we often fall prey to making the mistake of saying, oh, well your data is available in X number of minutes. Well, that's great. What's it available to? So let's say I have backed up to S3 and it's immutable. By the way my wife keeps calling me and saying she wants mutability for me. (Jeanna laughs) I'm not sure if that's a good thing or not. But now I've got my backup in S3, begs the question, okay, well, now what do I do with it? Well, guess what you mentioned EC2. >> That's right. >> The ability exists to create a restore environment so that not only is the data available but the services are actually online and available-- >> That's right-- >> Which is what you want with EKS and Kasten. >> So if the customer is running, you know, Kubernetes, they're able to recover as well. So yes, definitely, I see more and more services like that where customers are able to recover their environment. It might be more than just a server, right? So things are changing. It's not just one, two, three, it's the whole environment. >> So speaking of the future, one of the last physical theCUBE interviews that Andy Jassy did with us. John Furrier and myself, we were asking about the edge and he had a great quote. He said, "Oh yeah, we look at the data center as just another edge node." I thought that was good classic Andy Jassy depositioning. And so it was brilliant. But nonetheless, we've talked a little bit about the edge. I was interviewing Verizon last week, and they told me they're putting outposts everywhere, like leaning in big time. And I was saying, okay, but outpost, you know, what can you do with outpost today? Oh, you can run RDS. And, you know, there's a few ecosystem partners that support it, and he's like, oh no, we're going to push Amazon. So what are you seeing at the edge in terms of data protection? Are customers giving you any feedback at this point? >> Definitely, so edge is a big deal, right? Because some workloads require that low latency, and things like outpost allow the customers to take advantage of the same API sets that they love in, you know, AWS today, like S3, right? For example. So they're able to deploy an outpost and meet some of those specific guidelines that they might have around compliance or, you know, various regulations, and then have that same consistent operational stance whether they're on-prem or in AWS. So we see that as well as the Snowball devices, you know, they're being really hardened so they can run in areas that don't have connected, you know, interfaces to the internet, right? So you've got them running in like ships or, you know, airplanes, or a field somewhere out in nowhere of this field, right? So lots of interesting things going on there. And then of course with IoT and the internet of things and so many different devices out there, we just see a lot of change in the industry and how data is being collected, how data's being created so a lot of excitement. >> Well, so the partners are key for outposts obviously 'cause you can't do it all yourself. It's almost, okay, Amazon now in a data center or an edge node. It's like me skating. It's like, hmm, I'm kind of out of my element there but I think you're learning, right? So, but partners are key to be able to support that model. >> Yes, definitely our partners are key, Veeam, of course, supports the outpost. They support the Snowball Edge devices. They do a lot. Again, they pay attention to their customers, right? Their customers are moving more and more workloads into AWS. So what do they do? They start to support those workloads, right? Because the customers also want that consistent, like we say, the consistent APIs with AWS. Well, they also want the consistent data protection strategy with Veeam. >> Well, the cloud is expanding. It's no longer just a bunch of remote services somewhere out there in the cloud. It's going to data centers. It's going out to the edge. It's going to local zones. You guys just announced a bunch of new local zones. I'm sure there are a lot of outposts in there, expanding your regions. Super cloud is forming right before our eyes. Jeanna, thanks so much for coming to theCUBE. >> Thank you. It's been great to be here. >> All right, and thank you for watching theCUBE's coverage. This is day two. We're going all day here, myself, Dave Nicholson, cohost. Check out siliconangle.com. For all the news, thecube.net, wikibon.com. We'll be right back right after this short break. (bright upbeat music)

(gentle music) (background chattering) >> Welcome to theCUBE's continuous coverage of AWS re:Invent 2021. I'm Dave Nicholson, and we are running one of the largest, most important hybrid events in the technology business. We've got two live sets here in Las Vegas, along with our two studios back home. And I'm absolutely delighted to have two fantastic guests with me. I'm joined by Stephen Manley, Chief Technology Officer from Druva. Stephen, welcome. >> Thanks, great to be here. >> Welcome back to theCUBE. >> I know. >> CUBE alumni. >> Love theCUBE. >> Along with Jake Burns, Enterprise Strategist from AWS, which I think stands for Amazon Web Services. >> You are correct, thank you. >> Fantastic, so the first question to you Jake is, well, first welcome, again, enterprise strategist, what does that mean exactly? >> Yeah, so- >> What do you do? (laughing) >> We're a team of former CIOs and CTOs who have all spent most of our time as customers and have all had large-scale success digitally transforming our organizations using the AWS Cloud. And now we work for AWS and we advise and work with some of our largest customers, share what worked for us, what didn't, and help them with the beginning stages of their cloud journey. >> Fantastic. >> And, Dave. Dave, you got to ask him, in the last year how many customers have you met? >> Oh, in the past year, I'm averaging about 150 to 200 different customers per year. >> Nice. >> So in the past three years, it's about 550. >> Nice. So can you remember all their names? Or do you do a lot of, "Hey, buddy. Hey, Sport." >> Jake: It's a lot harder with the masks on. >> Yes. >> But I recognize faces better than I remember the names. >> And Stephen, tell us about Druva. >> Yeah, so Druva, we are a SaaS data protection company. We built the first data resiliency cloud. So think of this as you might have data in endpoints, your data center, in AWS, in SaaS applications, and we're really shifting the discussion from, it's not just about backing it up, it's not just about protecting it anymore. It's about how do you recover it? how do you make sure your data is always on, always available to you? And that's really where we're trying to take the conversation. Is making sure that your data is there when you need it. >> And to be clear, this isn't just about resiliency for data that's in the cloud? This is also- >> Everywhere. >> on-premises? IT as well? >> On-premises, you might have VMs, you might have NAS servers, you might have Oracle databases on-prem, again, you might have endpoints. You might have Salesforce data, all of it. We want to make sure all your data's available to you. >> So let's focus on the relationship between Druva and AWS for a minute. It's always interesting to hear about success stories. Let's talk about inhibitors. What are the things that keep the two of you up at night? What are some of the things that... You talked about former CIOs and CTOs, CTOs like Stephen, you're working with existing CIOs and CTOs in all sorts of organizations, what are the things that are preventing them from leveraging cloud as well as they could be? Stephen, start with you on that. >> Yeah, I'll say the first thing is everybody right now is terrified of Ransomware, right? I met a CIO last night and he said, "My entire agenda for 2021, and now 2022 is security, security, security." And everyone is just searching for solutions to say, "How can I make sure that my environment is secure? How can I make sure my data is secure? Especially from these pretty much ubiquitous Ransomware attacks, because until I get that taken care of, it's really hard for me to get on these cloud transformation journeys." And so a lot of the discussion we have with them is, again, Druva in combination with AWS can actually help solve that Ransomware challenge for you so that instead of thinking it as, "Do one, and then you can do the cloud transformation." Let's put those two together, right? But for me, that's the number one thing, is people are just worried about how they're going to deal with security. >> So they're worried, but Jake, isn't it true, we'll do a little perimysium here. (laughing) Tell me the truth. >> All right. >> Isn't that the case that some people still think that effectively their money is safer under their mattress than in a bank? In other words, "I feel safer with on-prem IT than I do having it in some cloud somewhere." Are we still facing that sort of cultural divide between reality and perception? >> Yeah, there's definitely an education, widespread education effort going on right now. Training and certification, which AWS has a lot of experience with and has fantastic courses I went through when I was a customer, my team went through when we were a customer, we were able to get up-skilled very quickly. That fear of the unknown really the way to solve it is through information, through knowing how the cloud works. And it was so funny, I was just having a conversation right before this with an executive team of one of our largest customers and they were talking about how their CSO was dead set against the cloud and then one day did a complete 180. And we're seeing this all the time. When they realize what the cloud is, all the compliance and controls that we have, all of the redundancy that we have, all the benefits of being in the cloud. Then it seems to be like, there's just a moment where it clicks and then people become strong advocates. So there is still a lot of work to do in that area, but we find that people get it very quickly. >> Yeah, Stephen, you've had a long and illustrious career, I say that seriously. >> Stephen: There you go. >> And so you're living that bridging the divide between the old world of on-premises IT and cloud. What are you seeing in that regard in terms of where people's emotions are? >> Oh yeah, and that transformation that Jake talks about, I see it all the time where I'll sit down with a customer and it is exactly that, "Well, I have this on an appliance and because that appliance is under my control, I feel safer." And then we start talking about what the real threats are, that, let's face it Ransomware can come through your environment and it gets in anywhere and it can spread everywhere. And internal threats, internal bad actors, they can get at your appliances. And it very quickly shifts that conversation from, "Oh my gosh, how am I going to maintain all this? I have to do security patching, and upgrades, and I've got to watch everything." And Druva a sort of sits and says, "One of the great things that we had because we're built natively on AWS, a lot of the problems I worried about back when I built appliances are gone. I don't have to worry about capacity planning because AWS always gives me more. I don't have to worry about provisioning new equipment because it just automatically scales for me. I don't have to worry about a lot of the networking challenges that I used to have to worry about because it's built into the environment." And so a lot of what we talked to them about is, by taking these sort of daily routine things off the table, you can actually focus on the higher level value. You can focus on making your environment more secure because you're not just doing the basic blocking and tackling 'cause that's being done for you. And that really gets people sort of across that chasm. >> So you talk about basic block and tackle, in the keynote today, it was mentioned that there are 475 different types of instances within AWS. That gave me a little jolt to the heart because I was thinking back to Steve Jobs saying, "We can only have three of everything." And so sometimes with choice and with flexibility comes complexity. How does Druva manage the potential complexity that exists in the AWS space? How do you take what's best from AWS and deliver it to Druva customers to achieve what they want to achieve? >> Yeah, I think for us, that's really the benefit of being a SaaS provider is, we've designed a system from the ground up for AWS. And so, whether you're talking about the different storage types, where you've got S3, you've got Glacier, you've got Glacier Deep Archive. You have all the different instance types. You have different container services, ECS, EKS, there's all these choices. And frankly, it's something that we've spent a lot of time working on. And honestly, tons of people like Jake inside of AWS willing to help us. We characterize our workload and then they walk us through what's sort of the best practices so that we can deliver an end to end solution for the customer. So that, for our customers, it's just one simple cost, right? How much data are you storing? That's it, right? All the things happening in the background we take care of. And we take care of because we have AWS helping us design and implement this the best possible way. >> And so Jake, with all of the customer conversations that you've had, I'm sure we can guess what some of the themes have been over the last year or two with the pandemic and with things related to security. What are some of the other conversations that you're having with customers that people might not expect? >> Yeah. >> Based on what's going on? >> I think the biggest thing that would be surprising to most people is that vast majority of our conversations are about culture and about people, not about technology. We've gotten to a point where, and I've said this for a number of years, there's never been a better time to move to cloud, but that just keeps being more and more true as time goes on, as the technology gets more mature and as we have more and more examples of people who are very successful doing it. But like you said earlier, there are still some people who are used to the old way of doing things. So it's really largely an education issue, it's a culture issue. It's getting people to wrap their heads around this new way of doing things. And once they see that they get very excited about it. We very rarely see people who are kind of neutral about it. The very, very beginning stages, sometimes they're fearful. When they learn what it is they get very excited and they get very enthusiastic. And my advice to customers is to get your team excited and enthusiastic as early as possible, and they'll solve all of those process and technology problems very quickly and very easily. >> Now what are you seeing in terms of any skill gaps or skill divides? We, coming from a background where we're bridging the divide between sort of the legacy world and cloud. You have IT practitioners that have been doing this stuff for a long time. >> Right. >> That either need to move into the future or not. >> Right. >> Or you need to hire new people. Are there any challenges there in terms of finding the skill sets you need versus training up existing people? >> Yeah, so this is something I talk about a lot, and you do have a choice between hiring and trying to use the people you have and get them up skilled. I strongly favor the second. For one, it's very difficult to hire for cloud skills because it's in such high demand right now, but you use that to your advantage. And by training your staff, it's one of the kind of carrots you can use to get them excited about it. "You learn this, you will be valuable in the marketplace." And when you frame it that way, they get very excited to learn. And when you combine the training with the firsthand experience and give them opportunities to use it, and this could be everyone in the organization, it doesn't have to be like your engineering team or your infrastructure team. I had people in the help desk that learned how to become cloud engineers. When you give them that opportunity, and you give them the tools to do it, and the opportunity to use it with the training, it tends to be a much easier recipe for success. And then your problem becomes retention. But like I say, you're going to have either the problem of hiring or, retention, or you're going to have the problem of having people who don't have enough skills. I'd rather have the problem of retention. And if you have that capability of up-skilling people, then you don't really need to worry about it because there's more people all the time that are becoming more and more skilled. The other thing is, it's a lot easier to overlay cloud skills on top of people who already know your organization and your applications, than bring in new people- >> Sure. >> who have cloud skills, try to retain them and then teach them how your organization works. So there's a lot of advantages to using the people that you have, and the training is a lot easier than people think. >> So who were the people in those organizations that are making the decision to go with Druva? >> [Stephen} Right. >> And who are the people in organizations who are then managing Druva environments moving forward? Do you need a PhD in Druva- (laughing) >> Stephen: Right. >> to be able to manage an environment like that? >> I'll tell you one of the things that I talk to a lot of customers about that are going through sort of that, "How do I up skill?" Is, the first thing we try to remind them is, don't just about what you did on-premises, and then say, "And we're going to do the exact same thing in cloud." Because that is usually a path to either frustration or failure. "I had a physical appliance, I'm going to run a virtual appliance." That's not usually the right answer. So a lot of times we spend time walking them through, "Here's how you think differently. Again, cloud is dynamically scalable. You want something that breaks apart those limits. Cloud gives you 475 options, which means you have purchasing power that you never had as a company that you can have so many different options in front of you." So think of these not as how you thought of your on-premises environment, but think of it as a new way of doing things. And so what we find is the people who tend to be most attracted to Druva are those customers who are saying, "I'm spending too much time, effort, and money on my data protection environment." Which basically is everybody. Nobody wakes up and says, "I wish I could spend more time and money doing backup." And then in terms of who runs it, what we find is it often gets absorbed in sort of a cloud administrator task, right? Where they're looking more broadly across the organization. It's not just about backup, it's backup, it's disaster recovery, it's security, it's compliance because they're looking at the data as opposed to the infrastructure at that point. And that's where they can really start to grow their careers and have a lot bigger impact inside their companies. >> So I can tell that you're an awesome guy to have at a party, because you'll talk about all the risks that we face. >> Absolutely! >> Talking about data center fire drills, you're literally talking about fires and drills at that point. >> You got it. >> But so what's on the horizon for Druva? What are the things that you... When you look out into the future, in the area of resiliency, what are some of the things that you're thinking about? >> There's a couple of things for me. I think one of them, again, Ransomware is everywhere. And so many people right now are still focused on just, "Can I get a clean copy? Can I get a safe copy?" That's built into Druva. So, we're beyond that. The real focus for me is, how do we streamline your recovery process? Because for so many customers, they make this assumption that a Ransomware recovery is just like a disaster recovery. And it's not, it's not as if you just had a system outage. Someone has invaded your environment and you need to make sure that the data, the environment is clean before you recover. You're going to want clean sandboxes to play around with things before you put it in, you're going to need to work with your legal team. So a lot of what we're working with is helping them orchestrate at larger scale. I think the other area that gets really interesting is this notion of autonomous, right? We talk about self-driving cars. Again, nobody wants to spend time tuning and managing their backup environment. So as Druva moves forward it's, "How can we just do this automatically for you?" Again, we're built in the cloud, everything scales automatically. You as a customer shouldn't have to be doing anything. You shouldn't be babysitting this. Let us take care of it for you. So for me, those are the really two big things. It's cybersecurity, that full end to end recovery, and it's around the autonomous protection. >> So Jake, a reality check, anything that he just said that sounds like... (laughing) sounds out of line based on your experience talking to customers in the last year? >> Jake: No, I agree with that. And I think we're touching on something that's really powerful here, because you kind of alluded to the choice that people have in AWS and we're creating new services all the time and new features all the time, right? So these are building blocks that companies can use. And there's a lot of builders at a lot of companies that get very excited to see all these building blocks, and it's about using the right tool for the job. So by giving you more choices, we're giving you more of an opportunity to find the exact fit for the workload you have. But if you just want it to work, then we have this partner of ecosystems. Druva being one of our... My personal favorites (laughing) >> Love you , Jake. >> that build on AWS, use these very resilient, very secure building blocks to build something that's turnkey for a customer. So I think it's a great marriage and it benefits customers ultimately. So it makes us happy. >> All right, well 2022 we expect this gentlemen here to see at least 300 customers to meet his goal. That's what we're expecting from you, Jake. >> All right, I'm on it. >> Thanks to all for joining us here at theCUBE's, continuous coverage of AWS re:Invent 2021, I almost said 2022, live from Las Vegas. Stay tuned for much more from the leader in hybrid technology event programming, theCUBE. (gentle music)

(innovative music) >> Welcome back to theCUBE's continuous coverage of AWS re:Invent 2021. My name is Dave Vellante, and we are running one of the industry's most important and largest hybrid tech events of the year. Hybrid as in physical, not a lot of that going on this year. But we're here with the AWS ecosystem, AWS, and special thanks to AMD for supporting this year's editorial coverage of the event. We've got two live sets, two remote studios, more than a hundred guests on the program. We're going really deep, as we enter the next decade of Cloud innovation. We're super excited to be joined by Danny Allan, who's the Chief Technology Officer at Veeam, and James Kirschner who's the Engineering Director for Amazon S3. Guys, great to see you. >> Great to see you as well, Dave. >> Thanks for having me. >> So let's kick things off. Veeam and AWS, you guys have been partnering for a long time. Danny, where's the focus at this point in time? What are customers telling you they want you to solve for? And then maybe James, you can weigh in on the problems that customers are facing, and the opportunities that they see ahead. But Danny, why don't you start us off? >> Sure. So we hear from our customers a lot that they certainly want the solutions that Veeam is bringing to market, in terms of data protection. But one of the things that we're hearing is they want to move to Cloud. And so there's a number of capabilities that they're asking us for help with. Things like S3, things like EC2, and RDS. And so over the last, I'll say four or five years, we've been doing more and more together with AWS in, I'll say, two big categories. One is, how do we help them send their data to the Cloud? And we've done that in a very significant way. We support obviously tiering data into S3, but not just S3. We support S3, and S3 Glacier, and S3 Glacier Deep Archive. And more importantly than ever, we do it with immutability because customers are asking for security. So a big category of what we're working on is making sure that we can store data and we can do it securely. Second big category that we get asked about is "Help us to protect the Cloud-Native Workloads." So they have workloads running in EC2 and RDS, and EFS, and EKS, and all these different services knowing Cloud-Native Data Protection. So we're very focused on solving those problems for our customers. >> You know, James, it's interesting. I was out at the 15th anniversary of S3 in Seattle, in September. I was talking to Mai-Lan. Remember we used to talk about gigabytes and terabytes, but things have changed quite dramatically, haven't they? What's your take on this topic? >> Well, they sure have. We've seen the exponential growth data worldwide and that's made managing backups more difficult than ever before. We're seeing traditional methods like tape libraries and secondary sites fall behind, and many organizations are moving more and more of their workloads to the Cloud. They're extending backup targets to the Cloud as well. AWS offers the most storage services, data transfer methods and networking options with unmatched durability, security and affordability. And customers who are moving their Veeam Backups to AWS, they get all those benefits with a cost-effective offsite storage platform. Providing physical separation from on-premises primary data with pay-as-you-go economics, no upfront fees or capital investments, and near zero overhead to manage. AWS and APM partners like Veeam are helping to build secure, efficient, cost-effective backup, and restore solutions using the products you know and trust with the scale and reliability of the AWS Cloud. >> So thank you for that. Danny, I remember I was way back in the old days, it was a VeeamON physical event. And I remember kicking around and seeing this company called Kasten. And I was really interested in like, "You protect the containers, aren't they ephemeral?" And we started to sort of chit-chat about how that's going to change and what their vision was. Well, back in 2020, you purchased Kasten, you formed the Veeam KBU- the Kubernetes Business Unit. What was the rationale behind that acquisition? And then James, I'm going to get you to talk a little bit about modern apps. But Danny, start with the rationale behind the Kasten acquisition. >> Well, one of the things that we certainly believe is that the next generation of infrastructure is going to be based on containers, and there's a whole number of reasons for that. Things like scalability and portability. And there's a number of significant value-adds. So back in October of last year in 2020, as you mentioned, we acquired Kasten. And since that time we've been working through Kasten and from Veeam to add more capabilities and services around AWS. For example, we supported the Bottlerocket launch they just did and actually EKS anywhere. And so we're very focused on making sure that our customers can protect their data no matter whether it's a Kubernetes cluster, or whether it's on-premises in a data center, or if it's running up in the Cloud in EC2. We give this consistent data management experience and including, of course, the next generation of infrastructure that we believe will be based on containers. >> Yeah. You know, James, I've always noted to our audience that, "Hey AWS, they provide rich set of primitives and API's that ISV's like Veeam can take advantage of it." But I wonder if you could talk about your perspective, maybe what you're seeing in the ecosystem, maybe comment on what Veeam's doing. Specifically containers, app modernization in the Cloud, the evolution of S3 to support all these trends. >> Yeah. Well, it's been great to see Veeam expands for more and more AWS services to help joint customers protect their data. Especially since Veeam stores their data in Amazon S3 storage classes. And over the last 15 years, S3 has helped companies around the world optimize their work, so I'd be happy to share some insights into that with you today. When you think about S3 well, you can find virtually every use case across all industries running on S3. That ranges from backup, to (indistinct) data, to machine learning models, the list goes on and on. And one of the reasons is because S3 provides industry leading scalability, availability, durability, security, and performance. Those are characteristics customers want. To give you some examples, S3 stores exabytes the data across millions of hard drives, trillions of objects around the world and regularly peaks at millions of requests per second. S3 can process in a single region over 60 terabytes a second. So in summary, it's a very powerful storage offering. >> Yeah, indeed. So you guys always talking about, you know, working backwards, the customer centricity. I think frankly that AWS sort of change the culture of the entire industry. So, let's talk about customers. Danny do you have an example of a joint customer? Maybe how you're partnering with AWS to try to address some of the challenges in data protection. What are customers is seeing today? >> Well, we're certainly seeing that migration towards the Cloud as James alluded today. And actually, if we're talking about Kubernetes, actually there's a customer that I know of right now, Leidos. They're a fortune 500 Information Technology Company. They deal in the engineering and technology services space, and focus on highly regulated industry. Things like defense and intelligence in the civil space. And healthcare in these very regulated industries. Anyway, they decided to make a big investment in continuous integration, continuous development. There's a segment of the industry called portable DevSecOps, and they wanted to build infrastructure as code that they could deploy services, not in days or weeks or months, but they literally wanted to deploy their services in hours. And so they came to us, and with Kasten K10 actually around Kubernetes, they created a service that could enable them to do that. So they could be fully compliant, and they could deliver the services in, like I say, hours, not days or months. And they did that all while delivering the same security that they need in a cost-effective way. So it's been a great partnership, and that's just one example. We see these all the time, customers who want to combine the power of Kubernetes with the scale of the Cloud from AWS, with the data protection that comes from Veeam. >> Yes, so James, you know at AWS you don't get dinner if you don't have a customer example. So maybe you could share one with us. >> Yeah. We do love working backwards from customers and Danny, I loved hearing that story. One customer leveraging Veeam and AWS is Maritz. Maritz provides business performance solutions that connect people to results, ensuring brands deliver on their customer promises and drive growth. Recently Maritz moved over a thousand VM's and petabytes of data into AWS, using Veeam. Veeam Backup for AWS enables Maritz to protect their Amazon EC2 instances with the backup of the data in the Amazon S3 for highly available, cost-effective, long-term storage. >> You know, one of the hallmarks of Cloud is strong ecosystem. I see a lot of companies doing sort of their own version of Cloud. I always ask "What's the partner ecosystem look like?" Because that is a fundamental requirement, in my view anyway, and attribute. And so, a big part of that, Danny, is channel partners. And you have a 100 percent channel model. And I wonder if we could talk about your strategy in that regard. Why is it important to be all channel? How to consulting partners fit into the strategy? And then James, I'm going to ask you what's the fit with the AWS ecosystem. But Danny, let's start with you. >> Sure, so one of the things that we've learned, we're 15 years old as well, actually. I think we're about two months older, or younger I should say than AWS. I think their birthday was in August, ours was in October. But over that 15 years, we've learned that our customers enjoy the services, and support, and expertise that comes from the channel. And so we've always been a 100 percent channel company. And so one of the things that we've done with AWS is to make sure that our customers can purchase both how and when they want through the AWS marketplace. They have a program called Consulting Partners Private Agreements, or CPPO, I think is what it's known as. And that allows our customers to consume through the channel, but with the terms and bill that they associate with AWS. And so it's a new route-to-market for us, but we continue to partner with AWS in the channel programs as well. >> Yeah. The marketplace is really impressive. James, I wonder if you could maybe add in a little bit. >> Yeah. I think Danny said it well, AWS marketplace is a sales channel for ISV's and consulting partners. It lets them sell their solutions to AWS customers. And we focus on making it really easy for customers to find, buy, deploy, and manage software solutions, including software as a service in just a matter of minutes. >> Danny, you mentioned you're 15 years old. The first time I mean, the name Veeam. The brilliance of tying it to virtualization and VMware. I was at a VMUG when I first met you guys and saw your ascendancy tied to virtualization. And now you're obviously leaning heavily into the Cloud. You and I have talked a lot about the difference between just wrapping your stack in a container and hosting it in the Cloud versus actually taking advantage of Cloud-Native Services to drive further innovation. So my question to you is, where does Veeam fit on that spectrum, and specifically what Cloud-Native Services are you leveraging on AWS? And maybe what have been some outcomes of those efforts, if in fact that's what you're doing? And then James, I have a follow-up for you. >> Sure. So the, the outcomes clearly are just more success, more scale, more security. All the things that James is alluding to, that's true for Veeam it's true for our customers. And so if you look at the Cloud-Native capabilities that we protect today, certainly it began with EC2. So we run things in the Cloud in EC2, and we wanted to protect that. But we've gone well beyond that today, we protect RDS, we protect EFS- Elastic File Services. We talked about EKS- Elastic Kubernetes Services, ECS. So there's a number of these different services that we protect, and we're going to continue to expand on that. But the interesting thing is in all of these, Dave, when we do data protection, we're sending it to S3, and we're doing all of that management, and tiering, and security that our customers know and love and expect from Veeam. And so you'll continue to see these types of capabilities coming from Veeam as we go forward. >> Thank you for that. So James, as we know S3- very first service offered in 2006 on the AWS' Cloud. As I said, theCUBE was out in Seattle, September. It was a great, you know, a little semi-hybrid event. But so over the decade and a half, you really expanded the offerings quite dramatically. Including a number of, you got on-premise services things, like Outposts. You got other services with "Wintery" names. How have you seen partners take advantage of those services? Is there anything you can highlight maybe that Veeam is doing that's notable? What can you share? >> Yeah, I think you're right to call out that growth. We have a very broad and rich set of features and services, and we keep growing that. Almost every day there's a new release coming out, so it can be hard to keep up with. And Veeam has really been listening and innovating to support our joint customers. Like Danny called out a number of the ways in which they've expanded their support. Within Amazon S3, I want to call out their support for our infrequent access, infrequent access One-Zone, Glacier, and Glacier Deep Archive Storage Classes. And they also support other AWS storage services like AWS Outposts, AWS Storage Gateway, AWS Snowball Edge, and the Cold-themed storage offerings. So absolutely a broad set of support there. >> Yeah. There's those, winter is coming. Okay, great guys, we're going to leave it there. Danny, James, thanks so much for coming to theCUBE. Really good to see you guys. >> Good to see you as well, thank you. >> All right >> Thanks for having us. >> You're very welcome. You're watching theCUBE's coverage of 2021 AWS re:Invent, keep it right there for more action on theCUBE, your leader in hybrid tech event coverage, right back. (uplifting music)

>>Welcome back to the cubes coverage here in Washington D. C. For a W. S. Public sector summit. I'm john fraser host of the queues and in person event but of course we have remote guests. It's a hybrid event as well. Amazon is streaming amazon web services, streaming all the teams, some of the key notes of course all the cube interviews are free and streaming out there as well on the all the cube channels and all the social coordinates. Our next guest is Melissa Pavlik President and Ceo POV con joining me here to talk about predictive maintenance, bringing that to life for the U. S. Air Force melissa. Thanks for coming in remotely on our virtual cube here at the physical event. >>Excellent, thank you. Good morning >>Show. People have been been um face to face for the first time since 2019. A lot of people remote calling in checking things out kind of an interesting time, right? We're living in so uh what's your, what's your take on all this? >>Sure. I mean it's a new way of doing business, right? Um I will say, I guess for us as a company we always have been remote so it's not too much of a change but it is definitely challenging, especially trying to engage with such a large user community such as the United States Air Force who isn't always used to working as remotely. So it's definitely a unique challenge for sure. >>Well let's get into, I love this topic. You had a real success story. There is a case study with the U. S. Air Force, what's the relationship take us through what you guys are doing together? >>Sure. Absolutely. So we started working with the Air Force now about five years ago on this subject and predictive maintenance. Sometimes you might hear me catch myself and say CBM plus condition based maintenance. They're synonymous. They mean the exact same thing basically. But about five years ago the Air Force was contemplating how do we get into a space of getting ahead of unscheduled maintenance events? Um if the military they're big push always his readiness how do we improve readiness? So to do that it was a big ask of do we have the data to get ahead of failures? So we started on this journey about five years ago as I said and frankly we started under the radar we weren't sure if it was going to work. So we started with two platforms. And of course when I think a lot of people here predictive maintenance, they immediately think of sensor data and sensors are wonderful data but unfortunately especially in an entity such as the Air Force not all assets are censored. So it also opened up a whole other avenue of how do we use the data that they have today to be able to generate and get ahead of failures. So it did start a really great partnership working not only with the individual, I'll say Air Force entities that Air Force Lifecycle Management Center but we also worked across all the major commands, the individual units, supply control, logistics and everyone else. So it's been a really great team effort to bring together all of those but typically would be rather segregated operations together. >>Yeah, they're getting a lot of props lately on a lot of their projects across the board and this one particular, how did you guys specifically help them modernize and with their and get this particular maintenance thing off the ground? >>Absolutely. I think quite simply it was what really we put their existing data to work. We really wanted to get in there and think about they already had a ton of data. There wasn't a need to generate more. We're talking about petabytes of information. So how do we use that and put it into a focus of getting ahead of failure? We said we established basically three key performance parameters right from the beginning it was, we knew we wanted to increase availability which was going to directly improve readiness. We needed to make sure we were reducing mission aborts and we wanted to get ahead of any kind of maintenance costs. So for us it was really how do we leverage and embrace machine learning and ai paired with just big data analytics and how do we take frankly what is more of a World War Two era architecture and turn it into something that is in the information age. So our modernization really started with how do we take their existing data and turn it into something that is useful and then simultaneously how do we educate the workforce and helping them understand what truly machine learning and AI offer because I think sometimes there's everyone has their own opinions of what that means, but when you put it into action and you need to make sure that it's something that they can take action on, right, it's not just pushing a dot moving numbers around, it's really thinking about and considering how their operations are done and then infusing that with the data on the back end, >>it's awesome. You know the old workflows in the cloud, this is legit, I mean physical assets, all kinds of things and his legacy is also but you want the modernization, I was gonna ask you about the machine learning and ai component, you brought that up. What specifically are you leveraging their from the ai side of the machine learning side? >>Absolutely for us, most and foremost we're talking about responsible a i in this case because unfortunately a lot of the data in the Air Force is human entry, so it's manual, which basically means it's open and rife for a lot of error into that data. So we're really focused heavily on the data integrity, we're really focused on utilizing different types of machine learning because I think on the surface the general opinion is there's a lot of data here. So it would open itself naturally into a lot of potential machine learning techniques, but the reality situation is this data is not human understandable unless you are a prior maintainer, frankly, it's a lot of codes, there's not a whole lot of common taxonomy. So what we've done is we've looked at those supervised and unsupervised models, we've taken a whole different approach to infusing it with truly, what I would say arguably is the most important key element, domain expertise. You know, someone who actually understands what this data means. So that way we can in in End up with actionable output something that the air force can actually put into use, see the results coming out of it. And thus far it's been great. Air mobility command has come back and said we've been able to reduce their my caps, which are parts waiting for maintenance by 18%. That's huge in this space. >>Yeah, it's interesting about unsupervised and supervised machine learning. That's a big distinct because you mentioned there's a lot of human error going on. That's a big part. Can you explain a little bit more because that was that to solve the human error part or was it the mix and match because the different data sets, but why the why both machine learning modes. >>So really it was to address both items frankly. When we started down this path, we weren't sure we were going to find right, We went in with some hypotheses and some of those ended up being true and others were not. So it was a way for us to quickly adjust as we needed to again put the data into actionable use and make sure we were responsibly doing that. So for us a lot of it, because it's human understanding and human error that goes into this natural language processing is a really big area in this space. So for us, adjusting between and trying different techniques is really where we were able to discover and find out what was going to be the most effective and useful in this particular space as well as cost effective. Because for us there's also this resistance, you have to have resist the urge to want to monitor everything. In this case we're talking about really focusing on those top drivers and depending on the type of data that we had, depending on the users that we knew were going to get involved with it as well as I would say, the historical information, it really would help us dictate on supervised versus supervised and going the unsupervised route. In some cases there's just still not ready for that because the data is just so manual. Once we get to a point where there is more automation and more automated data collection, unsupervised will definitely no doubt become more valuable right now though, in order to get those actionable. That supervised modeling was really what we found to be the most valuable >>and that makes total sense. You've got a lot of head room to grow into with Unsupervised, which is actually harder as you as you know, everyone, everyone everyone knows that. But I mean that's really the reality. Congratulations. I gotta ask you on the AWS side what part do they play in all this? Obviously the cloud um their relationship with the Air Force as well, what's their what's their role in this particular maintenance solution? >>Sure, absolutely. And I'll just say, I mean we're really proud to be a partner network with them and so when we started this there was no cloud, so today a lot of opportunity or things we hear about in the Air Force where like cloud one platform one, those weren't in existence, you know, five years ago or so. So for us when we started down this path and we had to identify very quickly a format and a host location that would allow us not only handle large amounts of data but do all of the deep analysis we needed to AWS GovCloud is where that came in. Plus it also is awesome that they were already approved at I. L. Five to be able to host that we in collaboration with them host a nist 801 +71 environment. And so it's really allowed us to to grow and deliver this this impact out over 6000 users today on the Air Force side. So for us with a W. S. Has been a great partnership. They obviously have some really great native services that are inside their cloud as well as the pairing and easy collaboration among not only licensed products but also all that free and open source that's out there because again, arguably that's the best community to pull from because they're constantly evolving and working in the space. But a W has been a really great partner for us and of course we have some of our very favorite services I'm happy to talk about, but they've been really great to work with >>what's the top services. >>So for us, a lot of top services are like ec two's work spaces, of course S three and Glacier um are right up there, but you really enjoy working across glue Athena were really big on, we find a commercial service we're looking for that's not yet available in Govcloud. And we pull in our AWS partners and ask, hey, you know when it's going to get into the gulf cloud space and they move pretty quickly to get those in there. So recent months are definitely a theme in blue. Well, >>congratulations, great solution, I love this application because it highlights the power of the cloud, What's the future in store for the U. S. Air Force when it comes to predictive maintenance. >>Sure. I mean, I think at this point they are just going to continue adding additional top driver analyses you through our work for the past couple years. We've identified a lot of operational and functional opportunities for them. So there's gonna be some definitely foundational changing coming along, some enabling new technologies to get that data integrity more automated as well so that there isn't such a heavy lift on the downstream, we're talking about data cleansing, but I think as far as predictive maintenance goes, we're definitely going to see more and more improvements across the readiness level, getting rid of and eliminating that unscheduled event that drives a lot of the readiness concerns that are out there. And we're also hoping to see a lot more improvement and I'd say enhancement across the supply chain because we know that's also an area that really they could get ahead on your part of our other work as we developed a five year long range supply forecast and it's really been opening some eyes to see how they can better plan, not only on the maintenance side but also supporting maintenance from a logistics and supply, >>great stuff melissa. Great to have you on President Ceo Path Con, you're also the business owner. Um how's things going with the business? The pandemic looks like I'm gonna come out of it stronger. Got the tailwind with cloud technology. The modernization boom is here in, in Govcloud, 10 years celebrating Govcloud birthday here at this event. How's business house? How are you doing >>good. Everything has actually been, we were, I guess fortunate, as I mentioned the very beginning, we were remote companies. So fortunately for us the pandemic did not have that much of an operational hiccup and being that a lot of our clients are in the federal space, we were able to continue working and amazingly we actually grew during the pandemic. We added quite a bit of a personnel to the team and so we're looking forward to doing some more predictive maintenance across, not only explaining the Air Force but the other services as well. >>You know, the people who were Agile had some cloud action going on, we're productive and they came out stronger melissa. Great to have you on the cube. Thank you for coming in remotely and joining our face to face event from the interwebs. Thank you so much for coming on cuba >>All right, thank you, john have a great rest of your day. >>Okay. I'm john for here at the cube with a W. S. Public sector summit in person and remote bringing guest on. We've got the new capability of bringing remotes in. We do in person. I'll see you face to face hear the cube and it's like to be here at the public sector summit. Thanks for watching. Mhm. Mhm >>robert, Herjavec

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

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

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

(upbeat music) >> Welcome everybody to VeeamON 2021 you're watching theCUBE. My name is Dave Villante. You know in 2020 cyber adversaries they seize the opportunity to really up their game and target workers from home and digital supply chains. It's become increasingly clear to observers that we're entering a new era of cyber threats where infiltrating companies via so-called Island Hopping and stealthily living off the land meaning they're using your own tools and infrastructure to steal your data. So they're not signaling with new tools that they're in there. It's becoming the norm for sophisticated hacks. Moreover, these well-funded and really sophisticated criminals and nation States are aggressively retaliating against incident responses. In other words, when you go to fix the problem they're not leaving the premises they're rather they're tightening the vice on victims by holding your data ransom and threatening to release previously ex filtrated and brand damaging information to the public. What a climate in which we live today. And with me to talk about these concerning trends and what you can do about it as Gil Vega, the CISO of Veeam Gil great to see you. Thanks for coming on. >> Great to see you, Dave. Thanks for having me. >> Yeah. So, you know, you're hearing my intro. It's probably understating the threat. You are a Veeam's first CISO. So how do you see the landscape right now? >> That's right. Yeah. And I've been with the company for just over a year now, but my background is in financial services and spent a lot of time managing cybersecurity programs at the classified level in Washington DC. So I've gleaned a lot of scar tissue from lots of sophisticated attacks and responses. But today I think what we're seeing is really a one-upmanship by a sophisticated potentially nation state sponsored adversaries, this idea of imprisoning your data and charging you to release it is it's quite frightening. And as we've seen in the news recently it can have devastating impacts not only for the economy, but for businesses. Look at the gas lines in the Northeast right now because of the quality of a pipeline, a ransomware attack. I just, the government just released an executive order this morning, that hopes to address some of the some of the nation's unpreparedness for these sophisticated attacks. And I think it's time. And I think everyone's excited about the opportunity to really apply a whole of government approach, to helping critical infrastructure to helping and partnering with private sector and imposing some risks, frankly, on some of the folks that are engaged in attacking our country. >> A number of years ago, I often tell this story. I had the pleasure of interviewing Robert Gates the former Defense Secretary. And it was a while ago we were talking about cyber and he sits on a number of boards. And we were talking about how it's a board level issue. And, and we're talking about cyber crime and the like and nation States. And I said, well, wait, cyber warfare, even. And I said, "But don't we have the best cyber tech. I mean, can't we go on the offense?" And he goes, "Yeah, we do. And we can, but we have more to lose." And to your point about critical infrastructure, it's not just like, okay, we have the most powerful weapons. It's really we have the most valuable infrastructure and a lot to lose. So it's really a tricky game. And this notion of having to be stealthy in your incident response is relatively new. Isn't it? >> It is. It is. And you know, there are, you mentioned that and I was surprised you mentioned because a lot of people really don't talk about it as you're going into your response your adversaries are watching or watching your every move. You have to assume in these days of perpetual state of compromise in your environments, which means that your adversaries have access to your environment to the point that they're watching your incident responders communicate with one another and they're countering your moves. So it's sort of a perverse spin on the old mutually assured destruction paradigm that you mentioned the United States has the world's largest economy. And quite frankly the world's most vulnerable, critical infrastructure. And I would concur with Director Gates or Secretary Gates rather it is assessment that we've got to be awfully careful and measured in our approach to imposing risks. I think the government has worked for many years on defining red lines. And I think this latest attack on the colonial pipeline affecting the economy and people's lives and potentially putting people's lives at risk is towing also the close to that red line. And I'm interested to see where this goes. I'm interested to see if this triggers even a, you know a new phase of cyber warfare, retaliation, you know proactive defense by the National Security Community of the United States government. Be interesting to see how this plays out. >> Yeah, you're absolutely right though. You've got this sort of asymmetric dynamic now which is unique for the United States as soon as strongest defense in the world. And I wanted to get it to ransomware a bit. And specifically this notion of ransomware as a service it's really concerning where criminals can actually outsource the hack as a service and the bad guys will set up, you know, on the dark web they'll have, you know, help desks and phone lines. They'll do the negotiations. I mean, this is a really concerning trend. And obviously Veeam plays a role here. I'm wondering as a, as a SecOps pro what should we be doing about this? >> Yeah, you mentioned ransomware as a service, whereas RWS it's an incredibly pernicious problem perpetrated by sophisticated folks who may or may not have nation state support or alliances. I think at a minimum certain governments are looking the other way as it relates to these criminal activities. But with ransomware as a service, you're essentially having very sophisticated folks create very complex ransomware code and distributed to people who are willing to pay for it. And oftentimes take a part of the ransom as their payment. The, issue with obviously ransomware is you know the age old question, are you going to pay a ransom or are you not going to pay a ransom? The FBI says, don't do it. It only encourages additional attacks. The Treasury Department put out some guidance earlier earlier in the year, advising companies that they could be subject to civil or criminal penalties. If they pay a ransom and the ransom goes to a sanction density. So there's danger on all sides. >> Wow okay. But so, and then the other thing is this infiltrating via digital supply chains I call it Island Hopping and the like, we saw that with the solar winds hack and the scary part is, you know different malware is coming in and self forming and creating different signatures. Not only is it very difficult to detect, but remediating, you know, one, you know combined self formed malware it doesn't necessarily take care of the others. And so, you know, you've got this sort of organic virus, like thing, you know, create mutating and that's something that's certainly relatively new to me in terms of its prevalence your thoughts on that and how to do it. >> Yeah, exactly right. You know, the advent of the polymorphic code that changes the implementation of advanced artificial intelligence and some of this malware is making our job increasingly difficult which is why I believe firmly. You've got to focus on the fundamentals and I think the best answers for protecting against sophisticated polymorphic code is,are found in the NIST cybersecurity framework. And I encourage everyone to really take a close look at implementing that cybersecurity framework across their environments, much like we've done here, here at Veeam implementing technologies around Zero Trust again assuming a perpetual state of compromise and not trusting any transaction in your environment is the key to combating this kind of attack. >> Well, and you know, as you mentioned, Zero Trust Zero Trust used to be a buzzword. Now it's like become a mandate. And you know, it's funny. I mean, in a way I feel like the crypto guys I know there's a lot of fraud in crypto, but but anybody who's ever traded crypto it's like getting into Fort Knox. I mean, you got to know your customer and you've got to do a little transaction. I mean, it's really quite sophisticated in terms of the how they are applying cybersecurity and you know, most even your bank isn't that intense. And so those kinds of practices, even though they're a bit of a pain in the neck, I mean it's worth the extra effort. I wonder if you could talk about some of the best practices that you're seeing how you're advising your clients in your ecosystem and the role that Veeam can play in helping here. >> Yeah, absolutely. As I mentioned so many recommendations and I think the thing to remember here so we don't overwhelm our small and medium sized businesses that have limited resources in this area is to remind them that it's a journey, right? It's not a destination that they can continually improve and focus on the fundamentals. As I mentioned, things like multi-factor authentication you know, a higher level topic might be micro-segmentation breaking up your environment into manageable components that you can monitor a real time. Real time monitoring is one of the key components to implementing Zero Trust architecture and knowing exactly what good looks like in your environment in a situation where you've got real-time monitoring you can detect the anomalies, the things that shouldn't be happening in your environment and to spin up your response teams, to focus and better understand what that is. I've always been a proponent of identity and access management controls and a key focus. We've heard it in this industry for 25 years is enforcing the concept of least privilege, making sure that your privileged users have access to the things they need and only the things that they need. And then of course, data immutability making sure that your data is stored in backups that verifiably has not been changed. And I think this is where Veeam comes into the equation where our products provide a lot of these very easily configured ransomware protections around data and your ability to the ability to instantly back up things like Office 365 emails, you know support for AWS and Azure. Your data can be quickly restored in the event that an attacker is able to in prison that with encryption and ransom demands. >> Well, and so you've certainly seen in the CISOs that I've talked to that they've had to obviously shift their priorities, thanks to the force march to digital, thanks to COVID, but Identity access management, end point security cloud security kind of overnight, you know, Zero Trust. We talked about that and you could see that in some of these, you know, high flying security stocks, Okta Zscaler, CrowdStrike, they exploded. And so what's in these many of these changes seem to be permanent sort of you're I guess, deeper down in the stack if you will, but you, you compliment these toolings with obviously the data protection approach the ransomware, the cloud data protection, air gaps, immutability. Maybe you could talk about how you fit in with the broader, you know, spate of tools. I mean, your, my eyes bleed when you look at all the security companies that are out there. >> Yeah for sure. You know, I'm just going to take it right back to the NIST cybersecurity framework and the five domains that you really need to focus on. Identify, protect, detect, respond, and recover, you know and until recently security practitioners and companies have really focused on on the protect, identify and protect, right and defend rather where they're focused on building, you know, moats and castles and making sure that they've got this, you know hard exterior to defend against attacks. I think there's been a shift over the past couple of years where companies have recognized that the focus needs to be on and respond and recover activities, right? Assuming that people are going to breach or near breach, your entities is a safe way to think about this and building up capabilities to detect those breaches and respond effectively to those breaches are what's key in implementing a successful cybersecurity program where Veeam fits into this since with our suite of products that that can help you through the recovery process, right? That last domain of the NIST cybersecurity framework it'll allow you to instantaneously. As I mentioned before, restore data in the event of a catastrophic breach. And I think it provides companies with the assurances that while they're protecting and building those Zero Trust components into their environments to protect against these pernicious and well-resourced adversaries there's the opportunity for them to recover very quickly using the VM suite of tools? >> Well, I see, I think there's an interesting dynamic here. You're pointing out Gil. There's not no longer is it that, you know, build a moat the Queen's leaving her castle. I always say, you know there is no hardened perimeter anymore. And so you've seen, you know, the shift obviously from hardware based firewalls and you I mentioned those other companies that are doing great but to me, it's all about these layers and response is a big in recovery is a huge part of that. So I'm seeing increasingly companies like Veeam is a critical part of that, that security cyber data protection, you know, ecosystem. I mean, to me it's just as important as the frontline pieces of even identity. And so you see those markets exploding. I think it's, there's a latent value that's building in companies like Veeam that are a key part of those that data protection layer you think about you know, defense strategies. It's not just you, the frontline it's maybe it's airstrikes, maybe it's, you know, C etcetera. And I see that this market is actually a huge opportunity for for organizations like yours. >> I think you're right. And I think the proof is in, you know in the pudding, in terms of how this company has grown and what we've delivered in version 11 of our suite, including, you know features like continuous data protection, we talked about that reliable ransomware protection support for AWS S3 Glacier and Azure archive the expanded incident recovery, and then support for disaster recovery and backup as a service. You know, what I found most interesting in my year here at Veeam is just how much our administrators the administrators in our company and our customers companies that are managing backups absolutely love our products that ease of use the instant backup capabilities and the support they receive from Veeam. It's almost cultish in terms of how our customers are using these products to defend themselves in today's pretty intense cyber threat environment. >> Well, and you talked about the NIST framework, and again big part of that is recovery, because we talked about earlier about, do you pay the ransom or not? Well, to the extent that I can actually recover from having all my data encrypted then I've got obviously a lot more leverage and in many ways, I mean, let's face it. We all know that it's not a matter of if it's, when you get infiltrated. And so to the extent that I can actually have systems that allow me to recover, I'm now in a much much stronger position in many respects, you know and CISOs again, will tell you this that's where we're shifting our investments >> Right. And you've got to do all of them. It's not just there's no silver bullet, but but that seems to me to be just a a misunderstood and undervalued part of the equation. And I think there's tremendous upside there for companies like yours. >> I think you're right. I think what I'll just add to that is the power of immutability, right? Just verifiably ensuring that your data has not changed because oftentimes you'll have attackers in these low and slow live off the land types of attacks change your data and affect its integrity with the Veeam suite of tools. You're able to provide for immutable or unchanged verifiable data and your backup strategy which is really the first step to recovery after a significant event. >> And that's key because a lot of times the hackers would go right after the backup Corpus you know, they'll sometimes start there is that all the data, you know, but if you can make that immutable and again, it, you know there's best practices there too, because, you know if you're not paying the cloud service for that immutability, if you stop paying then you lose that. So you have to be very careful about, you know how you know, who has access to that and you know what the policies are there, but again, you know you can put in, you know so a lot of this, as you know, is people in process. It's not just tech, so I'll give you the last word. I know you got to jump, but really appreciate.. >> Yeah, sure. >> You know, the only, the only thing that we didn't mention is user awareness and education. I think that is sort of the umbrella key focus principle for any successful cybersecurity program making sure your people understand, you know how to deal with phishing emails. You know, ransomware is a huge threat of our time at 90% of ransomware malware is delivered by phishing. So prepare your workforce to deal with phishing emails. And I think you'll save yourself quite a few headaches. >> It's great advice. I'm glad you mentioned that because because bad user behavior or maybe uninformed user behaviors is the more fair way to say it. It will trump good security every time. Gil, thanks so much for coming to the CUBE and and keep fighting the fight. Best of luck going forward. >> Great. Thank you, Dave. >> All right. And thank you for watching everybody. This is Dave Villante for the CUBEs continuous coverage VeeamON 2021, the virtual edition. We will be right back. (upbeat music)

>>president >>so called big data promised to usher in a new era of innovation where companies competed on the basis of insights and agile decision making. There's little question that social media giants, search leaders and e commerce companies benefited. They had the engineering shops and the execution capabilities to take troves of data and turned them into piles of money. But many organizations were not as successful. They invested heavily in data architecture is tooling and hyper specialized experts to build out their data pipelines. Yet they still struggle today to truly realize they're busy. Did data in their lakes is plentiful but actionable insights aren't so much chaos. Search is a cloud based startup that wants to change this dynamic with a new approach designed to simplify and accelerate time to insights and dramatically lower cost and with us to discuss his company and its vision for the future is cuba Lem Ed Walsh had great to see you. Thanks for coming back in the cube. >>I always love to be here. Thank you very much. It's always a warm welcome. Thank you. >>Alright, so give us the update. You guys have had some big funding rounds, You're making real progress on the tech, taking it to market what's new with chaos surgery. >>Sure. Actually even a lot of good exciting things happen. In fact just this month we need some, you know, obviously announced some pretty exciting things. So we unveiled what we consider the industry first multi model data late platform that we allow you to take your data in S three. In fact, if you want to show the image you can, but basically we allow you to put your data in S three and then what we do is we activate that data and what we do is a full index of the data and makes it available through open a P. I. S. And the key thing about that is it allows your end users to use the tools are using today. So simply put your data in your cloud option charge, think Amazon S three and glacier think of all the different data. Is that a natural act? And then we do the hard work. And the key thing is to get one unified delic but it's a multi mode model access so we expose api like the elastic search aPI So you can do things like search or using cabana do log analytics but you can also do things like sequel, use Tableau looker or bring relational concepts into cabana. Things like joins in the data back end. But it allows you also to machine learning which is early next year. But what you get is that with that because of a data lake philosophy, we're not making new transformations without all the data movement. People typically land data in S. Three and we're on the shoulders of giants with us three. Um There's not a better more cost effective platform. More resilient. There's not a better queuing system out there and it's gonna cost curve that you can't beat. But basically so people store a lot of data in S. Three. Um But what their um But basically what you have to do is you E. T. L. Out to other locations. What we do is allow you to literally keep it in place. We index in place. We write our hot index to rewrite index, allow you to go after that but published an open aPI S. But what we avoid is the GTL process. So what our index does is look at the data and does full scheme of discovery normalization, were able to give sample sets. And then the refinery allows you to advance transformations using code. Think about using sequel or using rejects to change that data pull the dead apartheid things but use role based access to give that to the end user. But it's in a format that their tools understand cabana will use the elasticsearch ap or using elasticsearch calls but also sequel and go directly after data by doing that. You get a data lake but you haven't had to take the three weeks to three months to transform your data. Everyone else makes you. And you talk about the failure. The idea that Alex was put your data there in a very scalable resilient environment. Don't do transformation. It was too hard to structure for databases and data. Where else is put it there? We'll show you how value out Largely un delivered. But we're that last mile. We do exactly that. Just put it in s. three and we activated and activate it with a piece that the tools of your analysts use today or what they want to use in the future. That is what's so powerful. So basically we're on the shoulders of giants with street, put it there and we light it up and that's really the last mile. But it's this multi model but it's also this lack of transformation. We can do all the transformation that's all to virtually and available immediately. You're not doing extended GTL projects with big teams moving around a lot of data in the enterprise. In fact, most time they land and that's three and they move it somewhere and they move it again. What we're saying is now just leave in place well index and make it available. >>So the reason that it was interesting, so the reason they want to move in the S three was the original object storage cloud. It was, it was a cheap bucket. Okay. But it's become much more than that when you talk to customers like, hey, I have all this data in this three. I want to do something with it. I want to apply machine intelligence. I want to search it. I want to do all these things, but you're right. I have to move it. Oftentimes to do that. So that's a huge value. Now can I, are you available in the AWS marketplace yet? >>You know, in fact that was the other announcement to talk about. So our solution is one person available AWS marketplace, which is great for clients because they've been burned down their credits with amazon. >>Yeah, that's that super great news there. Now let's talk a little bit more about data. Like you know, the old joke of the tongue in cheek was data lakes become data swamps. You sort of know, see no schema on, right. Oh great. I can put everything into the lake and then it's like, okay, what? Um, so maybe double click on that a little bit and provide a little bit more details to your, your vision there and your philosophy. >>So if you could put things that data can get after it with your own tools on elastic or search, of course you do that. If you don't have to go through that. But everyone thinks it's a status quo. Everyone is using, you know, everyone has to put it in some sort of schema in a database before they can get access to what everyone does. They move it some place to do it. Now. They're using 1970s and maybe 1980s technology. And they're saying, I'm gonna put it in this database, it works on the cloud and you can go after it. But you have to do all the same pain of transformation, which is what takes human. We use time, cost and complexity. It takes time to do that to do a transformation for an user. It takes a lot of time. But it also takes a teams time to do it with dBS and data scientists to do exactly that. And it's not one thing going on. So it takes three weeks to three months in enterprise. It's a cost complexity. But all these pipelines for every data request, you're trying to give them their own data set. It ends up being data puddles all over this. It might be in your data lake, but it's all separated. Hard to govern. Hard to manage. What we do is we stop that. What we do is we index in place. Your dad is already necessary. Typically retailing it out. You can continue doing that. We really are just one more use of the data. We do read only access. We do not change that data and you give us a place in. You're going to write our index. It's a full rewrite index. Once we did that that allows you with the refinery to make that we just we activate that data. It will immediately fully index was performant from cabana. So you no longer have to take your data and move it and do a pipeline into elasticsearch which becomes kind of brittle at scale. You have the scale of S. Three but use the exact same tools you do today. And what we find for like log analytics is it's a slightly different use case for large analytics or value prop than Be I or what we're doing with private companies but the logs were saving clients 50 to 80% on the hard dollars a day in the month. They're going from very limited data sets to unlimited data sets. Whatever they want to keep an S. Three and glacier. But also they're getting away from the brittle data layer which is the loosen environment which any of the data layers hold you back because it takes time to put it there. But more importantly It becomes brittle at scale where you don't have any of that scale issue when using S. three. Is your dad like. So what what >>are the big use cases Ed you mentioned log analytics? Maybe you can talk about that. And are there any others that are sort of forming in the marketplace? Any patterns that you see >>Because of the multi model we can do a lot of different use cases but we always work with clients on high R. O. I use cases why the Big Bang theory of Due dad like and put everything in it. It's just proven not to work right? So what we're focusing first use cases, log analytics, why as by way with everything had a tipping point, right? People were buying model, save money here, invested here. It went quickly to no, no we're going cloud native and we have to and then on top of it it was how do we efficiently innovate? So they got the tipping point happens, everyone's going cloud native. Once you go cloud native, the amount of machine generated data that you have that comes from the environment dramatically. It just explodes. You're not managing hundreds or thousands or maybe 10,000 endpoints, you're dealing with millions or billions and also you need this insight to get inside out. So logs become one of the things you can't keep up with it. I think I mentioned uh we went to a group of end users, it was only 60 enterprise clients but we asked him what's your capture rate on logs And they said what do you want it to be 80%, actually 78 said listen we want eight captured 80 200 of our logs. That would be the ideal not everything but we need most of it. And then the same group, what are you doing? Well 82 had less than 50%. They just can't keep up with it and every everything including elastic and Splunk. They work harder to the process to narrow and keep less and less data. Why? Because they can't handle the scale, we just say landed there don't transform will make it all available to you. So for log analytics, especially with cloud native, you need this type of technology and you need to stop, it's like uh it feels so good when you stop hitting your head against the wall. Right? This detail process that this type of scale just doesn't work. So that's exactly we're delivering the second use case uh and that's with using elastic KPI but also using sequel to go after the same data representation. And we come out with machine learning. You can also do anomaly detection on the same data representation. So for a log uh analytic use case series devops setups. It's a huge value problem now the same platform because it has sequel exposed. You can do just what we use the term is agile B. I people are using you think about look or tableau power bi I uh metabolic. I think of all these toolsets that people want to give and uh and use your business or coming back to the centralized team every single week asking for new datasets. And they have to be set up like a data set. They have to do an e tail process that give access to that data where because of the way just landed in the bucket. If you have access to that with role based access, I can literally get you access that with your tool set, let's say Tableau looker. You know um these different data sets literally in five minutes and now you're off and running and if you want a new dataset they give another virtual and you're off and running. But with full governance so we can use to be in B I either had self service or centralized. Self service is kind of out of control, but we can move fast and the centralized team is it takes me months but at least I'm in control. We allow you do both fully governed but self service. Right. I got to >>have lower. I gotta excel. All right. And it's like and that's the trade off on each of the pieces of the triangle. Right. >>And they make it easy, we'll just put in a data source and you're done. But the problem is you have to E T L the data source. And that's what takes the three weeks to three months in enterprise and we do it virtually in five minutes. So now the third is actually think about um it's kind of a combination of the two. Think about uh you love the beers and diaper stories. So you know, think about early days of terror data where they look at sales out data for business and they were able to look at all the sales out data, large relational environment, look at it, they crunch all these numbers and they figured out by different location of products and the start of they sell more sticker things and they came up with an analogy which everyone talked about beers and diapers. If you put it together, you sell more from why? Because afternoon for anyone that has kids, you picked up diapers and you might want to grab a beer of your home with the kids. But that analogy 30 years ago, it's now well we're what's the shelf space now for approximate company? You know it is the website, it's actually what's the data coming from there. It's actually the app logs and you're not capturing them because you can't in these environments or you're capturing the data. But everyone's telling, you know, you've got to do an E. T. L. Process to keep less data. You've got to select, you got to be very specific because it's going to kill your budget. You can't do that with elastic or Splunk, you gotta keep less data and you don't even know what the questions are gonna ask with us, Bring all the app logs just land in S. three or glacier which is the most it's really shoulders of giants right? There's not a better platform cost effectively security resilience or through but to think about what you can stream and the it's the best queuing platform I've ever seen in the industry just landed there. And it's also very cost effective. We also compress the data. So by doing that now you match that up with actually relatively small amount of relational data and now you have the vaccine being data. But instead it's like this users using that use case and our top users are always, they start with this one then they use that feature and that feature. Hey, we just did new pricing is affecting these clients and that clients by doing this. We get that. But you need that data and people aren't able to capture it with the current platforms. A data lake. As long as you can make it available. Hot is a way to do it. And that's what we're doing. But we're unique in that. Other people are making GTL IT and put it in a in 19 seventies and 19 eighties data format called a schema. And we avoided that because we basically make S three a hot and elected. >>So okay. So I gotta I want to, I want to land on that for a second because I think sometimes people get confused. I know I do sometimes without chaos or it's like sometimes don't know where to put you. I'm like okay observe ability that seems to be a hot space. You know of course log analytics as part of that B. I. Agile B. I. You called it but there's players like elastic search their star burst. There's data, dogs, data bricks. Dream EOS Snowflake. I mean where do you fit where what's the category and how do you differentiate from players like that? >>Yeah. So we went about it fundamentally different than everyone else. Six years ago. Um Tom hazel and his band of merry men and women came up and designed it from scratch. They may basically yesterday they purposely built make s free hot analytic environment with open A. P. I. S. By doing that. They kind of changed the game so we deliver upon the true promises. Just put it there and I'll give you access to it. No one else does that. Everyone else makes you move the data and put it in schema of some format to get to it. And they try to put so if you look at elasticsearch, why are we going after? Like it just happens to be an easy logs are overwhelming. You once you go to cloud native, you can't afford to put it in a loose seen the elk stack. L is for loosen its inverted index. Start small. Great. But once you now grow it's now not one server. Five servers, 15 servers, you lose a server, you're down for three days because you have to rebuild the whole thing. It becomes brittle at scale and expensive. So you trade off I'm going to keep less or keep less either from retention or data. So basically by doing that so elastic we're not we have no elastic on that covers but we allow you to well index the data in S. Tree and you can access it directly through a cabana interface or an open search interface. Api >>out it's just a P. >>It's open A P. I. S. It's And by doing that you've avoided a whole bunch of time cost, complexity, time of your team to do it. But also the time to results the delays of doing that cost. It's crazy. We're saving 50-80 hard dollars while giving you unlimited retention where you were dramatically limited before us. And as a managed service you have to manage that Kind of Clunky. Not when it starts small, when it starts small, it's great once at scale. That's a terrible environment to manage the scale. That's why you end up with not one elasticsearch cluster, dozens. I just talked to someone yesterday had 125 elasticsearch clusters because of the scale. So anyway, that's where elastic we're not a Mhm. If you're using elastic it scale and you're having problems with the retired off of cost time in the, in the scale, we become a natural fit and you don't change what your end users do. >>So the thing, you know, they had people here, this will go, wow, that sounds so simple. Why doesn't everybody do this? The reason is it's not easy. You said tom and his merry band. This is really hard core tech. Um and it's and it's it's not trivial what you've built. Let's talk about your secret sauce. >>Yeah. So it is a patented technology. So if you look at our, you know, component for architecture is basically a large part of the 90% of value add is actually S. Three, I gotta give S three full kudos. They built a platform that we're on shoulders of giants. Um But what we did is we purpose built to make an object storage a hot alec database. So we have an index, like a database. Um And we basically the data you bring a refinery to be able to do all the advanced type of transformation but all virtually done because we're not changing the source of record, we're changing the virtual views And then a fabric allows you to manage and be fully elastic. So if we have a big queries because we have multiple clients with multiple use cases, each multiple petabytes, we're spending up 1800 different nodes after a particular environment. But even with all that we're saving them 58%. But it's really the patented technology to do this, it took us six years by the way, that's what it takes to come up with this. I come upon it, I knew the founder, I've known tom tom a stable for a while and uh you know his first thing was he figured out the math and the math worked out. Its deep tech, it's hard tech. But the key thing about it is we've been in market now for two years, multiple use cases in production at scale. Um Now what you do is roadmap, we're adding a P. I. So now we have elasticsearch natural proofpoint. Now you're adding sequel allows you open up new markets. But the idea for the person dealing with, you know, so we believe we deliver on the true promise of Data Lakes and the promise of Data lakes was put it there, don't focus on transferring. It's just too hard. I'll get insights out and that's exactly what we do. But we're the only ones that do that everyone else makes you E. T. L. At places. And that's the innovation of the index in the refinery that allows the index in place and give virtual views in place at scale. Um And then the open api is to be honest, uh I think that's a game. Give me an open api let me go after it. I don't know what tool I'm gonna use next week every time we go into account they're not a looker shop or Tableau Sharp or quick site shop there, all of them and they're just trying to keep up with the businesses. Um and then the ability to have role based access where actually can give, hey, get them their own bucket, give them their own refinery. As long as they have access to the data, they can go to their own manipulation ends up being >>just, >>that's the true promise of data lakes. Once we come out with machine learning next year, now you're gonna rip through the same embassy and the way we structured the data matrices. It's a natural fit for things like tensorflow pytorch, but that's, that's gonna be next year just because it's a different persona. But the underlining architecture has been built, what we're doing is trying to use case that time. So we worked, our clients say it's not a big bang. Let's nail a use case that works well. Great R. O. I great business value for a particular business unit and let's move to the next. And that's how I think it's gonna be really. That's what if you think about gardener talks about, if you think about what really got successful in data, where else in the past? That's exactly it wasn't the big bang, it was, let's go and nail it for particular users. And that's what we're doing now because it's multi model, there's a bunch of different use cases, but even then we're focusing on these core things that are really hard to do with other relational only environments. Yeah, I >>can see why you're still because you know, you haven't been well, you and I have talked about the api economy for forever and then you've been in the storage world so long. You know what a nightmare is to move data. We gotta, we gotta jump. But I want to ask you, I want to be clear on this. So you are your cloud cloud Native talked to frank's Lukman maybe a year ago and I asked him about on prem and he's like, no, we're never doing the halfway house. We are cloud all the >>way. I think >>you're, I think you have a similar answer. What what's your plan on Hybrid? >>Okay. We get, there's nothing about technology, we can't go on, but we are 100 cloud native or only in the public cloud. We believe that's a trend line. Everyone agrees with us, we're sticking there. That's for the opportunity. And if you can run analytics, There's nothing better than getting to the public cloud like Amazon and he was actually, that were 100 cloud native. Uh, we love S three and what would be a better place to put this is put the next three and we just let you light it up and then I guess if I'm gonna add the commercial and buy it through amazon marketplace, which we love that business model with amazon. It's >>great. Ed thanks so much for coming back in the cube and participating in the startup showcase. Love having you and best of luck. Really exciting. >>Hey, thanks again, appreciate it. >>All right, thank you for watching everybody. This is Dave Volonte for the cube. Keep it right there.

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

>> Narrator: From around the globe it's theCUBE, with digital coverage of AWS re:Invent 2020. Special coverage sponsored by AWS Global Partner Network. >> Hello and welcome to theCUBE Virtual and our coverage of AWS re:Invent 2020 with special coverage of APN partner experience. We are theCUBE Virtual and I'm your host, Justin Warren. And today I'm joined by Ed Walsh, CEO of ChaosSearch. Ed, welcome to theCUBE. >> Well thank you for having me, I really appreciate it. >> Now, this is not your first time here on theCUBE. You're a regular here and I've loved it to have you back. >> I love the platform you guys are great. >> So let's start off by just reminding people about what ChaosSearch is and what do you do there? >> Sure, the best way to say is so ChaosSearch helps our clients know better. We don't do that by a special wizard or a widget that you give to your, you know, SecOp teams. What we do is a hard work to give you a data platform to get insights at scale. And we do that also by achieving the promise of data lakes. So what we have is a Chaos data platform, connects and indexes data in a customer's S3 or glacier accounts. So inside your data lake, not our data lake but renders that data fully searchable and available for analysis using your existing tools today 'cause what we do is index it and publish open API, it's like API like Elasticsearch API, and soon SQL. So give you an example. So based upon those capabilities were an ideal replacement for a commonly deployed, either Elasticsearch or ELK Stack deployments, if you're hitting scale issues. So we talk about scalable log analytics, and more and more people are hitting these scale issues. So let's say if you're using Elasticsearch ELK or Amazon Elasticsearch, and you're hitting scale issues, what I mean by that is like, you can't keep enough retention. You want longer retention, or it's getting very expensive to keep that retention, or because the scale you hit where you have availability, where the cluster is hard to keep up running or is crashing. That's what we mean by the issues at scale. And what we do is simply we allow you, because we're publishing the open API of Elasticsearch use all your tools, but we save you about 80% off your monthly bill. We also give you an, and it's an and statement and give you unlimited retention. And as much as you want to keep on S3 or into Glacier but we also take care of all the hassles and management and the time to manage these clusters, which ends up being on a database server called leucine. And we take care of that as a managed service. And probably the biggest thing is all of this without changing anything your end users are using. So we include Kibana, but imagine it's an Elastic API. So if you're using API or Kibana, it's just easy to use the exact same tools used today, but you get the benefits of a true data lake. In fact, we're running now Elasticsearch on top of S3 natively. If that makes it sense. >> Right and natively is pretty cool. And look, 80% savings, is a dramatic number, particularly this year. I think there's a lot of people who are looking to save a few quid. So it'd be very nice to be able to save up to 80%. I am curious as to how you're able to achieve that kind of saving though. >> Yeah, you won't be the first person to ask me that. So listen, Elastic came around, it was, you know we had Splunk and we also have a lot of Splunk clients, but Elastic was a more cost effective solution open source to go after it. But what happens is, especially at scale, if it's fall it's actually very cost-effective. But underneath last six tech ELK Stack is a leucine database, it's a database technology. And that sits on our servers that are heavy memory count CPU count in and SSDs. So you can do on-prem or even in the clouds, so if you do an Amazon, basically you're spinning up a server and it stays up, it doesn't spin up, spin down. So those clusters are not one server, it's a cluster of those servers. And typically if you have any scale you're actually having multiple clusters because you don't dare put it on one, for different use cases. So our savings are actually you no longer need those servers to spin up and you don't need to pay for those seen underneath. You can still use Kibana under API but literally it's $80 off your bill that you're paying for your service now, and it's hard dollars. So it's not... And we typically see clients between 70 and 80%. It's up to 80, but it's literally right within a 10% margin that you're saving a lot of money, but more importantly, saving money is a great thing. But now you have one unified data lake that you can have. You used to go across some of the data or all the data through the role-based access. You can give different people. Like we've seen people who say, hey give that, help that person 40 days of this data. But the SecOp up team gets to see across all the different law. You know, all the machine generated data they have. And we can give you a couple of examples of that and walk you through how people deploy if you want. >> I'm always keen to hear specific examples of how customers are doing things. And it's nice that you've thought of drawn that comparison there around what what cloud is good for and what it isn't is. I'll often like to say that AWS is cheap to fail in, but expensive to succeed. So when people are actually succeeding with this and using this, this broad amount of data so what you're saying there with that savings I've actually got access to a lot more data that I can do things with. So yeah, if you could walk through a couple of examples of what people are doing with this increased amount of data that they have access to in EKL Search, what are some of the things that people are now able to unlock with that data? >> Well, literally it's always good for a customer size so we can go through and we go through it however it might want, Kleiner, Blackboard, Alert Logic, Armor Security, HubSpot. Maybe I'll start with HubSpot. One of our good clients, they were doing some Cloud Flare data that was one of their clusters they were using a lot to search for. But they were looking at to look at a denial service. And they were, we find everyone kind of at scale, they get limited. So they were down to five days retention. Why? Well, it's not that they meant to but basically they couldn't cost-effectively handle that in the scale. And also they're having scale issues with the environment, how they set the cluster and sharding. And when they also denial service tech, what happened that's when the influx of data that is one thing about scale is how fast it comes out, yet another one is how much data you have. But this is as the data was coming after them at denial service, that's when the cluster would actually go down believe it or not, you know right. When you need your log analysis tools. So what we did is because they're just using Kibana, it was easy swap. They ran in parallel because we published the open API but we took them from five days to nine days. They could keep as much as they want but nine days for denial services is what they wanted. And then we did save them in over $4 million a year in hard dollars, What they're paying in their environment from really is the savings on the server farm and a little bit on the Elasticsearch Stack. But more importantly, they had no outages since. Now here's the thing. Are you talking about the use case? They also had other clusters and you find everyone does it. They don't dare put it on one cluster, even though these are not one server, they're multiple servers. So the next use case for CloudFlare was one, the next QS and it was a 10 terabyte a day influx kept it for 90 days. So it's about a petabyte. They brought another use case on which was NetMon, again, Network Monitoring. And again, I'm having the same scale issue, retention area. And what they're able to do is easily roll that on. So that's one data platform. Now they're adding the next one. They have about four different use cases and it's just different clusters able to bring together. But now what they're able to do give you use cases either they getting more cost effective, more stability and freedom. We say saves you a lot of time, cost and complexity. Just the time they manage that get the data in the complexities around it. And then the cost is easy to kind of quantify but they've got better but more importantly now for particular teams they only need their access to one data but the SecOP team wants to see across all the data. And it's very easy for them to see across all the data where before it was impossible to do. So now they have multiple large use cases streaming at them. And what I love about that particular case is at one point they were just trying to test our scale. So they started tossing more things at it, right. To see if they could kind of break us. So they spiked us up to 30 terabytes a day which is for Elastic would even 10 terabytes a day makes things fall over. Now, if you think of what they just did, what were doing is literally three steps, put your data in S3 and as fast as you can, don't modify, just put it there. Once it's there three steps connect to us, you give us readability access to those buckets and a place to write the indexy. All of that stuff is in your S3, it never comes out. And then basically you set up, do you want to do live or do you want to do real time analysis? Or do you want to go after old data? We do the rest, we ingest, we normalize the schema. And basically we give you our back and the refinery to give the right people access. So what they did is they basically throw a whole bunch of stuff at it. They were trying to outrun S3. So, you know, we're on shoulders of giants. You know, if you think about our platform for clients what's a better dental like than S3. You're not going to get a better cross curve, right? You're not going to get a better parallelism. And so, or security it's in your, you know a virtual environment. But if you... And also you can keep data in the right location. So Blackboard's a good example. They need to keep that in all the different regions and because it's personal data, they, you know, GDPR they got to keep data in that location. It's easy, we just put compute in each one of the different areas they are. But the net net is if you think that architecture is shoulders of giants if you think you can outrun by just sheer volume or you can put in more cost-effective place to keep long-term or you think you can out store you have so much data that S3 and glacier can't possibly do it. Then you got me at your bigger scale at me but that's the scale we'r&e talking about. So if you think about the spiked our throughput what they really did is they try to outrun S3. And we didn't pick up. Now, the next thing is they tossed a bunch of users at us which were just spinning up in our data fabric different ways to do the indexing, to keep up with it. And new use cases in case they're going after everyone gets their own worker nodes which are all expected to fail in place. So again, they did some of that but really they're like you guys handled all the influx. And if you think about it, it's the shoulders of giants being on top of an Amazon platform, which is amazing. You're not going to get a more cost effective data lake in the world, and it's continuing to fall in price. And it's a cost curve, like no other, but also all that resiliency, all that security and the parallelism you can get, out of an S3 Glacier is just a bar none is the most scalable environment, you can build an environment. And what we do is a thin layer. It's a data platform that allows you to have your data now fully searchable and queryable using your tools >> Right and you, you mentioned there that, I mean you're running in AWS, which has broad experience in doing these sorts of things at scale but on that operational management side of things. As you mentioned, you actually take that off, off the hands of customers so that you run it on their behalf. What are some of the areas that you see people making in trying to do this themselves, when you've gone into customers, and brought it into the EKL Search platform? >> Yeah, so either people are just trying their best to build out clusters of Elasticsearch or they're going to services like Logz.io, Sumo Logic or Amazon Elasticsearch services. And those are all basically on the same ELK Stack. So they have the exact same limits as the same bits. Then we see people trying to say, well I really want to go to a data lake. I want to get away from these database servers and which have their limits. I want to use a data Lake. And then we see a lot of people putting data into environments before they, instead of using Elasticsearch, they want to use SQL type tools. And what they do is they put it into a Parquet or Presto form. It's a Presto dialect, but it into Parquet and structure it. And they go a lot of other way to, Hey it's in the data lake, but they end up building these little islands inside their data lake. And it's a lot of time to transform the data, to get it in a format that you can go after our tools. And then what we do is we don't make you do that. Just literally put the data there. And then what we do is we do the index and a polish API. So right now it's Elasticsearch in a very short time we'll publish Presto or the SQL dialect. You can use the same tool. So we do see people, either brute forcing and trying their best with a bunch of physical servers. We do see another group that says, you know, I want to go use an Athena use cases, or I want to use a there's a whole bunch of different startups saying, I do data lake or data lake houses. But they are, what they really do is force you to put things in the structure before you get insight. True data lake economics is literally just put it there, and use your tools natively to go after it. And that's where we're unique compared to what we see from our competition. >> Hmm, so with people who have moved into ChaosSearch, what's, let's say pick one, if you can, the most interesting example of what people have started to do with, with their data. What's new? >> That's good. Well, I'll give you another one. And so Armor Security is a good one. So Armor Security is a security service company. You know, thousands of clients doing great I mean a beautiful platform, beautiful business. And they won Rackspace as a partner. So now imagine thousand clients, but now, you know massive scale that to keep up with. So that would be an example but another example where we were able to come in and they were facing a major upgrade of their environment just to keep up, and they expose actually to their customers is how their customers do logging analytics. What we're able to do is literally simply because they didn't go below the API they use the exact same tools that are on top and in 30 days replaced that use case, save them tremendous amount of dollars. But now they're able to go back and have unlimited retention. They used to restrict their clients to 14 days. Now they have an opportunity to do a bunch of different things, and possible revenue opportunities and other. But allow them to look at their business differently and free up their team to do other things. And now they're, they're putting billing and other things into the same environment with us because one is easy it's scale but also freed up their team. No one has enough team to do things. And then the biggest thing is what people do interesting with our product is actually in their own tools. So, you know, we talk about Kibana when we do SQL again we talk about Looker and Tableau and Power BI, you know, the really interesting thing, and we think we did the hard work on the data layer which you can say is, you know I can about all the ways you consolidate the performance. Now, what becomes really interesting is what they're doing at the visibility level, either Kibana or the API or Tableau or Looker. And the key thing for us is we just say, just use the tools you're used to. Now that might be a boring statement, but to me, a great value proposition is not changing what your end users have to use. And they're doing amazing things. They're doing the exact same things they did before. They're just doing it with more data at bigger scale. And also they're able to see across their different machine learning data compared to being limited going at one thing at a time. And that getting the correlation from a unified data lake is really what we, you know we get very excited about. What's most exciting to our clients is they don't have to tell the users they have to use a different tool, which, you know, we'll decide if that's really interesting in this conversation. But again, I always say we didn't build a new algorithm that you going to give the SecOp team or a new pipeline cool widget that going to help the machine learning team which is another API we'll publish. But basically what we do is a hard work of making the data platform scalable, but more importantly give you the APIs that you're used to. So it's the platform that you don't have to change what your end users are doing, which is a... So we're kind of invisible behind the scenes. >> Well, that's certainly a pretty strong proposition there and I'm sure that there's plenty of scope for customers to come and and talk to you because no one's creating any less data. So Ed, thanks for coming out of theCUBE. It's always great to see you here. >> Know, thank you. >> You've been watching theCUBE Virtual and our coverage of AWS re:Invent 2020 with special coverage of APN partner experience. Make sure you check out all our coverage online, either on your desktop, mobile on your phone, wherever you are. I've been your host, Justin Warren. And I look forward to seeing you again soon. (soft music)