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

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

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

>> 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)

>> Announcer: Live from Nashville, Tennessee, it's theCUBE, covering Commvault GO, 2018. Brought to you by, Commvault. >> Welcome back to Nashville, Tennessee, this is Commvault Go and you're watching theCUBE, I'm Stu Miniman, joined by my co-host, Keith Townsend And we're going to get a little cloudy. Happy to welcome to the program, Sabina Joseph, who's the Global Segment Director with Amazon Web Services, welcome back to the program. >> Thank you very much for having us here, >> Miniman: And also welcome to the program, first time, Jeanna James, who's the Worldwide Cloud Alliances Leader with Commvault, thanks for joining us. >> Thank you for having us. >> Alright, so, we're looking at the ecosystem that Commvaults have, Sabina, why don't you give us a little bit on the history, and what's going on, between Amazon, and Commvault. >> I think I'm going to have Jeanna kind of kick that off, and then we will >> sure! Yeah! >> Add some comments! >> I'll take that, so we started our relationship over five years ago, and it's been a strong and growing relationship since that time. We started off with S3 integration, and we write natively to Amazon S3, and now our integration points have just become deeper and wider, so, S3, S3IA, Glacier, Snowball, we have full support across the Amazon services, and, about three years ago, Amazon started the storage Competency Program, and Commvault is a storage Competency Partner, and so with that launch, we started to do more on the go to market side, so we started off with that integration, and the technology side, and now today are expanding more on the go to market, and Sabina you want to talk a a little bit about that? >> Absolutely, thank you, Jeanna. Thank you for that question. So our collaboration indeed started five years ago, and Commvault has always embraced our best practices around technology and go to market. They've always focused on getting the technical integrations with our services right, prior to engaging on go to market and sales initiatives. They have launched a joint practices website on their webpages, which talks about our collaboration, our solutions, and also jointly validated reference architectures. We engaged early on in the channel. In addition, when AWS is about to launch services and new features, we engage Commvault's technical team early on, and wherever possible, Commvault has always participated in our beta launches. This is actually one of the reasons why Commvault has a wide integration across Amazon S3, S3IA, Glacier, Glacier Vault Lock, and different versions of Snowball. >> Yeah, so, Sabina, those of us that watch the industry, watching this storage segment, and how AWS relates to it has been one of the most fascinating stories there. At this conference, we're really enjoying getting to talk to some of the customers, we know that Amazon's always listening very much to the customers, what can you tell us about what you're hearing from the customers, and how is that impacting the focus of what you're doing together? >> Well, as you know, AWS is very focused on the customer, and Commvault has always embraced this vision, making sure to launch solutions that mutually delight our customers. Every year, our technical and our executive teams meet, to set the initiatives for the year, both on the business and the technical front. This is on of the reasons why solutions such as data disaster recovery, healthcare data protection solutions, and AIML solutions, really speak to Commvault's commitment to the Cloud, and we are also very open with each other on recommendations. They have given us recommendations on our services, and we have done the same with Commvault, and we very much welcome these suggestions. All of this has laid a very strong foundation for our collaboration, and we look forward, and we will expect to see continued strong growth in the coming years. >> So, data, we've heard it said time and time again, the new currency, super important, Amazon obviously a leader in Cloud storage, talk to us about what's happening around data protection, data management, at AWS Cloud. >> Well, when we talk to our customers, one of the very first workloads, there in fact moving into the Cloud is backup of data, and with this cloud-first initiative in mind, they are embracing cloud-based solutions around data protection and data management. As you might be aware, the amount of data that customers are needing to protect is growing two-fold every two years, and challenges around ransomware means that traditional industries, and heavily regulated industries, like financial services, healthcare, are moving data into the Cloud because of our collaboration for over five years, Commvault has a wide array of solutions to address these customer needs available on AWS globally. >> Yes, and just to add to that, with AWS over the last two years, we've seen 100% growth year over year, and we continue to expect additional growth >> absolutely >> with AWS and our customer base, and typically, what we see, is customers will start with backup and recovery and sending backup data into the could, and then once they get that data into the Cloud they start to use it. Let's test disaster recovery incident, and see if it works? Wow, it worked, great! Once it works, then they start moving more clothes into the Cloud, and protecting the data across regions, and all over the world, and so that's one of the great benefits that we have with Amazon and Commvault together. >> Congrats on the progress that you've been making, sounds like you've got some good proof points. As this is maturing, what feedback are you getting from customers, what are they asking you to do, to expand this partnership even further? >> Thank you for that question, as Jeanna knows, customers are always looking for a wide integration of Commvault solutions across our services. They want to use the rich features that Commvault has on premises, in the hybrid architecture model, and also for workloads that are running completely on AWS, and once this data moves into the Cloud they want to do more with this data. This is actually one of the reasons why we are working together, to have Commvault integrate across our machine learning services, like transcribe, translate, which means that customers can extract more value from this data, improve their time to market, and potentially even create net new solutions using this data. >> So from a Commvault perspective, we see, just like Sabina said, more and customers going through digital transformations, and when they go through those digital transformations, they've been sold on things like, we want to lower cost, and we want to have more agility with our business, and one of our big customers that's here today, Dow Jones, talks about that story, where they've gotten rid of a lot of their data centers, moved a lot of their infrastructure into the Cloud and so they've been able to become more agile as a business because of moving to the Cloud with Commvault and AWS, so, we hope that you'll take some time and hear some of the customers' stories out there, while you're here. >> Yeah, we'll listen to customers, and as customers are making that digital business transformation, what have you been hearing, or what are some of the trends you're seeing, and what are customers thinking about, and specifically in this collaboration, what are you guys thinking about when it comes to digital transformation and the impact on data protection? >> You want to start with that? So, again, lowering cost, scalability, global infrastructure, those are the big things for the digital transformation that we see customers wanting to embrace, and with Commvault, one of the big differentiators, I think, for the enterprise customers out there who are global, is they typically do have both an on-prem environment as well as an in Cloud environment, and even if they have an all in strategy, there is time between that, moving all into the Cloud where they need to be able to cover both the on-prem and in the Cloud workloads, and so Commvault really brings that together, we also work together with our HyperScale Appliance for those customers who want to have on-prem and in the Cloud so overall, it's simplicity, the ability to manage the data, wherever it needs to be, that's where Commvault and AWS really do well and shine. >> Alright, so, for people that are at this show, what flavor are they getting of AWS, or their sessions, or their labs, what's that kind of Cloud experience at this show? >> Well, we have a number of sessions that we are jointly presenting together at, focus around AIML, future SAAS solutions, and also healthcare data protection solutions. And in fact, at this show, we are launching over 2100 EC2 instances, every day at this show, through the hundreds of labs that Commvault has running. For customers and partners, you can come and try out the Commvault solutions on AWS for free at these labs, and for those of you listening out there, we are giving away two Alexas at each of our sessions. >> Wow. So, I think, still we're about eight weeks out, right, from the big show? >> Oh, my team's deep in planning already, I mean, this is a great show, but Amazon is one of the biggest shows that we do every year. What should we expect to see, this year? >> Well as you said, our team is preparing very hard, to make sure that we are providing value to the customers, and partners, attending re:INVENT, and there will be a number of announcements, we're looking forward to having our advanced technology partner and our storage competency partner, Commvault, at re:INVENT again this year. >> And we're excited to be there, so I hope that everybody who's here with us today, will join us at re:INVENT in November, and it's sure to be a great show. >> Alright, yeah, be sure to join theCUBE and over 50,000 of your closest friends >> (laughs) >> in the Cloud in Las Vegas the week right after Thanksgiving, if you haven't already, register quickly, because it will sell out, >> Townsend: That's right >> get your hotel, because they will sell out, what I'm saying is, it's a big show, so, we're excited to be there, for Keith Townsend, I'm Stu Miniman, we'll be be back here with more coverage, from Commvault GO in Nashville, Tennessee, thanks for watching theCUBE. >> Jeanna: Alright. (electronic music)

>> Narrator: Live from Orlando, Florida. It's theCUBE! Covering .conf18. Brought to you by Splunk. >> Welcome back to Orlando, everybody. Splunk .conf18. This is theCUBE, the leader in live tech coverage. I'm Dave Vellante with my co-host, Stu Miniman. Carnival Cruise Lines is back. We heard from them yesterday, we heard them on the main stage of .conf. CEO is up there with Doug Merritt. Sheldon White is here. He's an enterprise architect at Carnival Cruise Line And Alex Taberras, who's the director of threat intelligence at Carnival. Gents, welcome to theCUBE. >> Thank you. >> Doing a lot of talk on security today. They've lined us up, which is great. We love the conversation. So much to learn. Alex, I'll start with you. When you think about security and threat intelligence, what are the big changes that you've seen over the last, whatever, pick a time. Half a decade? Decade? Couple of years even. >> Alex: So, it's just the amount of threats that are coming in now and how fast they're coming in, right? We can't seem to be keeping up with everything that's happening in the environment, everything that's happening outside, trying to get into our environment and cause all that damage, right? So, that's why Splunk is awesome, right? I get to see everything come in, real time. I'm able to quickly pinpoint any action I need to take, send it to my team and have them immediate right away. >> So, Sheldon, yesterday we had ship and shore from Carnival and he was talking about really different problems. You know, the folks on the ship, they got 250 thousand people on the ocean at any one point in time collecting data, trying to make a better experience, keep them connected. Folks on the shore, obviously, websites and things like that. Where do you fit into that mix of ship and shore? >> Sheldon: Right, so there's an entire value stream that we map out as enterprise architects. And so, what we do there is analyze all the customer touch points. And then we aggregate all of that information into a pipeline that we then address our audiences with those critical KPIs. Operational and infrastructure, the entire stack. >> Dave: You guys obviously have very strong relationship with Splunk. We heard from your CEO, Arnold Donald, right? >> Alex: Correct. >> Interesting name, I haven't messed that up yet so. (laughing) And so, where did that relationship start? Did it start in SecOps? Did it start in IT operations management? >> Alex: So, it really started in Devops, right? And they started... They purchased Splunk, I think back in like 2007, 2008. And they started looking at it, right? And I think I was talking to one of our other architects and it was one gig is what we started at, right? Now, we're upwards of 600 gigs. Just for security. So, it started there and it just kind of morphed into this huge relationship where we're partnering and touching all aspects of our business with Splunk. You know, and the Cloud and everything else. >> So, we heard, I don't know if you guys saw the key notes today, but we saw some announcements building on yesterday's Splunk next announcement. We heard some business workflow and some industrial IOT. I would think both of those are relevant for you guys. Not industrial IOT, but your IOT. Do you see Splunk permeating further into the organization? I guess, the answer's yes. You kind of already said that. But I'm interested in what role you guys play in facilitating that ? Are you kind of champions, evangelist, experts, consultants? How does that work? How do you see that (mumbles)? >> Sheldon: So, we see ourselves as internal consultants. We have our internal customers that depend on our guidance and our end-to-end view of the business processes. So, and now as enter our Cloud journey, into the second year of our Cloud journey, just we're able to accelerate our time to value for our internal customers to gain even greater insights into what's happening ship and shore. >> Dave: I wonder how, if you can talk about, how enterprise architecture has changed over the last decade even. You know, it used to be you were trying to harden the two tier or three tier architecture and harden top, don't touch it, it works. And then, of course, we all know, it created a lot of different stove pipes and a lot of data was locked into those stove pipes. That's changed, obviously. Cloud, now the Edge. Maybe because you guys were always sort of a distributed data company, you approached it differently. But I wondered if you could gives us (mumbles)? >> Sheldon: No, that's an interesting question. Because the evolution is not so much enterprise architect as it is eco system architect, right? So, now you have these massively distributed systems. So, you're really managing an eco system of internal and third party. And then all the relevant touch points, right? Like Alex mentioned, all that perimeters constantly shifting now. So, yeah, our focus is always aligning with the on-time business process and our internal customers. >> Yeah, wonder if we could dig into the Cloud a little. Alex, can we start with you? How does Cloud fit into your world of security? >> Alex: So, for me, the Cloud, as far as Splunk goes, it allows me to expand and contract as needed, right? So before, we used to have our on premise hardware, very finite RAM memory, I mean, disk space everything. So now, with the Cloud, I'm able to expand my environment as I move across all my North American brands, European brands, to be able to gather all that data, look at it and take action on it, right? >> Stu: And Sheldon, you're using AWS. We see they're, every software provider lives in AWS. It's often in the marketplace. We been seeing a lot this week that there's a deeper partnership. There's actually a lot of integration. Maybe give us your viewpoint on what you've seen on how Splunk and AWS work together to meet your requirements. >> Yeah. So, that's an interesting evolution as well of that partnership, right? So, you're starting to see things like the S3 API integration. So that you're removing storage from the critical path. And now that opens up different scale of possibilities, right? And internal opportunities. But yes, as you can see, leveraging the machine learning toolkit. I saw that one coming. It's going to be interesting to see how that keeps evolving, right? And also, like I was speaking to Alex, about the natural language capability. So, that also is well brought into the dimension of how our senior leadership with interact with these operational platforms. >> Yeah, I got to thank you. You're going to have your customer's natural language has to get into some of their rooms. It's definitely future. >> Sheldon: Oh, it's going to be apart of that value chain. Yeah, for sure. >> Dave: How does the S3 API integration affect you guys? Obviously, you got to put Syntax in an object store, which is going to scale. What does that mean for you guys? >> Sheldon: So, using the Splunk developer Cloud, we could develop all sorts of solutions to manage it intelligently how our storage, right? In near real time. So, we can completely automate and that end-to-end just integration with Splunk, how it ingest, how long that data stays relevant and how we offload it into things like Glacier. >> Dave: In the enablement, there is the S3 API. So, you're taking advantage of all the AWS automation tooling. >> Sheldon: Correct. >> Is that right? >> Sheldon: Correct. >> Alright. >> Sheldon: That's another example of that side integration. Not only with the S3 API. Lex, for the natural language. Obviously, TensorFlow and the machine learning toolkit. So, I think you're going to see that type of... those type of capabilities expanding as Splunk evolves. Next year, I'm sure they're going to have a ton of more, you know, announcements around how this evolution continues, right? >> Dave: So, you know, I was interested in the TensorFlow and Spark integration. And Stu and I were talking in an earlier segment. It's great, developers love that. We saw a lot of demos today that was like, looks so simple. Anybody could do it. Even I might be able to do it. But as practitioners of Splunk, is it really going to be that easy? Are business users actually going to be able to pick this stuff up and what are they going to have to do in order to take advantage of Splunk? Some training involved? >> Sheldon: Right, right. >> What's the learning curve going to be like? >> Sheldon: That's a great question, because there's a dual focus to this, right? First, is offloading from the developer. All that heavy lifting of creating this user interface and the dashboards, per say. Now, its all API driven. So, as you saw, maybe in the keynote this morning, that within the demo, was an API driven dashboard came together in several minutes. But one is offloading that and the second part is just enabling the business user with other capabilities, like natural language process. And they don't necessarily need to be on that screen. They can get acception reporting through emails and voice commands. So, training is also part of it, obviously. So, it's a multifaceted approach to leveraging these new capabilities. >> Dave: Are you guys responsible for the physical infrastructure of your ships? I mean, is that part of your purview? Okay. So, really there's is an industrial IOT component big time for you guys. >> Absolutely. >> Alex: And there's a huge push now for Maritime security, right? We saw what happened with Maersk and NotPetya virus, right? So, how it took them out of operation for about three weeks. So, this IOT is very, I think, awesome, right? I was speaking to some of the Splunk guys yesterday about it. How we could leverage that on our ships to gather that data, right, from our SCADA systems. And from our bridge and engine control systems to be able to view any kind of threat. Any kind of vulnerability that we might be seeing in the environment. How we can control that and how we can predict anything from happening, right? So, that's going to be very key to us. >> Dave: So, Splunk is going to take that data right off the machines. Which Stu and I were talking, that to us is a huge advantage. So many IT companies are coming and saying, "Hey! We're going to put a box at the edge". That's nice, but what about the data? So, Splunk's starting with the data, but it's the standards of that data. They're really driven by engineers and operations technology folks. Is Splunk sort of standard agnostic? Can they be able to ingest that data? What has to be done for you guys to take advantage of that? >> So, we'll have to ingest that data. And we'll have to, you know, look at it and see what we're seeing, right? This is all brand new to us as well. >> Dave: Right. >> Right. This whole Maritime thing has risen up in the past year, year and a half. So, we're going to have to look at the data and then kind of figure out what we want to see. Normalize it, you know, we'll probably get some PS services or something to assist us. Some experts. And then we just go from there, right? We build our dashboards and our reports. >> Dave: And predictive maintenance is a huge use case for you guys. >> Alex: Absolutely. >> I mean, to me, it's as important as the airlines. >> Alex: Absolutely, yes. >> So, I would think, anytime you... Well, first of all, real time during a journey. But anytime that journey is completed, you must bring in the inspectors and, I'm sure, very time consuming and precise. >> So, I know that some of our senior leadership, especially in the Maritime space, has now looking towards Splunk to do some of that predictive maintenance. To make sure that we have that right nuts and bolts, right? Per say, on the ship. To be able to fix any issue that might arise at sea while we're on there. >> Dave: Now, it's expect that the drive is going to be for human augmentation and of drive efficiency. >> Alex: Correct. >> You're not just going to trust the machines right out of the box. No way, right? >> Alex: No. But it's empowering those engineers, right? As we see with some of the dashboards that they're coming up with at the keynote. Empowering some of the those engineers that are in the engine room. That are in bridge. To be able to see those issues come up, right? And be able to track. >> Dave: Plus, I would imagine this is the kind of thing like an airline pilot. You're double checking, you're triple checking. So, you might catch misses earlier on in the cycle. >> Alex: Yeah. I could see it having huge impact. >> Stu: Yeah. Sheldon, I was just thinking through the other next announcement. I wonder if Splunk business flows sounds like something that might fit into your data pipeline? Get insights, understand satisfaction. Seems like it might be a fit. Is that of interest to you? >> Sheldon: Yeah, it sure is. Because we definitely want to, since we've evolved with kind of fragmented systems. We still have main frames, we still have whole call center environment that we need to ensure that it's parts of the end-to-end guest experience. So, for sure, we're getting into the whole early adopter program on the process flow. >> Yeah. Can you give us little insight? What kind of back and forth do you have with Splunk? What sort of things are you asking that would help make your jobs easier going forward? >> So, going forward, I know they're addressing a lot so the ingestion and data standardization. And now, with the decoupling of the storage, which is awesome, makes our lives a lot easier. But the evolution of the natural language and the integration with AWS natively is huge for us, as well as our Cloud program matures. And we start enabling Serverless architectures, for example. So, yeah. No, it's a very important part. >> Stu: Yeah. I mean, Serverless is actually something we're pretty interested. What are some of the early places that you're finding value there? >> Well, many people don't know this, but Carnival's also one of the largest travel agencies in the United States. So, we have the whole... Well, it's the whole global air travel platform that we're currently migrating to a Serverless architecture, integrates with Sabre. So, we're looking at things like open trace for that. And I know that our friends at Splunk are enabling capabilities for that type of management. >> Dave: And what's the business impact of Serverless there? You're just better utilization of resources? Faster time to value? Maybe you could describe. >> Yeah. Near real time processing. Scaling up and scaling down seasonally. Our key aspects of that. Removing the constraints of CPU and storage and-- >> Dave: Alex, has it changed the security paradigm at all? Serverless? How does it change it? >> Alex: So, it does. It let's me not have to worry so much about on premise stuff, right? As I did before. So, that helps a lot, right? And being able to scale up and down quickly as much data as we're ingesting is very key for us. >> Dave: You guys are heavy into Cloud, it's obvious. I wonder if you could share with us how you decide, kind of, what goes? If you're not all in on Cloud, right? It's not 100 percent Cloud? >> Sheldon: No, we could never be all in. >> No. >> Dave: And we've put forth that notion for years. We call it "true private cloud". That what you want to do is bring the Cloud experience to your data, wherever that data lives. There's certain data and workloads that you're not just going to put into the Cloud. >> Sheldon: That's correct. >> So, you would confirm that. That's the case. Like, you just said it. >> Correct. >> Dave: You're never going to put some of these workloads on Cloud. >> Well, we have floating data centers. So, we'll always be in a hybrid model. But there is a decision framework around how we create those application, migration pipelines. And the complexity and interdependencies between these platforms, some are easier to move than others. So, yeah. No, we're quite aware of-- >> Dave: And so, my follow up question is are you trying to bring that Cloud experience to those... to the floating data centers, wherever possible? And how is the industry doing? If you had a grade them in terms of their success. I mean, you certainly hear this from the big tech suppliers. "Oh, yes! We've got private Cloud" and "It's just like the public Cloud". And we know it's not and it doesn't have to be. >> Sheldon: Right. >> But if it can substantially mimic that public Cloud experience, it's a win for you guys. So, how is the industry doing in your view? >> So, I think it's a crawl, walk, run type of thing. Obviously, you have these floating cities and satellite bandwidth is a precious resource that we have to use wisely, right? So, we definitely are Edge computing strategy is evolving rapidly. What do we act upon at the Edge? What do we send to the Cloud? When do we send it? There also some business drivers behind this. For example, one of our early Cloud forays was in replicating a guest activity aboard the ship. So, we know if somebody buys a margarita off the coast of Australia, we know it five seconds later. And then, we could act upon that data. Casino or whatever data it may be in near real time. >> So, a lot of data stays at the floating data center, obviously. >> Correct. >> Much of it comes back to the Cloud. When it comes back to the Cloud is a decision, 'cause of the expense of the bandwidth. What do you do? You part the ship at the data center and put a big fire hose in there? (laughing) >> Alex: I wish it was that easy. >> You got a bunch of disc drives that you just take and load up? That's got to be a challenge. >> So, there business requirements, right? So, we have to figure out what application is more important, right? So, usually like our ship property management system, right. Where we have all our guests data, as far as their names, birth dates, all that stuff. That takes priority over a lot of other things, right. So, we have to use, like Sheldon said, that bandwidth wisely. 'Cause we don't really own a lot of the ports that we go into. So, we can't, just like you say, plug in a cable and move on, right? We still rely heavily on our satellites. So, bandwidth is our number on constraint and we have to, you know, we share it with our revenue generating guests as well. So, obviously, they take priority and a lot of factors go into that. >> Dave: And data's not shrinking. So, I'll give you guys the last word, if you could just sort of summarize, in your view, some of the big challenges that you're going to try to apply Splunk towards solving in the next near to mid term. >> Alex: Well, I'm more security focused. So, for me, its just making sure that I can get that data as fast as possible. I know that I saw yesterday at the keynote, the mobile app. That for me is going to be like one of the things I'm going to go like, research right away, right? 'Cause for me, its' getting that alert right away when something's going on, so that I can mitigate quickly, move fast and stop those threats from hitting our environment. >> Dave: Sheldon? >> Yes, I think the challenges are, like you mentioned earlier, about the stove pipes and how organizations evolve. Now, with this massive influx of data, that just making sense of it from a people, technology and processes standpoint. So that we could manage the chaos, so to speak, right? And make sure that we have an orderly end-to-end view of all the activity on the ships. >> Dave: Well, thank you guys. Stu and I are like kids in a candy shop, 'cause we getting to talk to so many customers this week. So, we really appreciate your time and your insights and the inspiration for your peers. So, thank you. >> Oh, thank you very much. >> Alex: Thank you for having us. >> Dave: You're welcome. Alright, keep it right there everybody. Stu and I will be back right after this short break. You're watching theCUBE Live from .conf18. Be right back. (techno music)

>> Narrator: Live from Orlando, Florida, it's theCUBE covering .conf18. Brought to you by Splunk. >> Welcome back to Orlando, everybody, of course home of Disney World. I'm Dave Vellante with Stu Miniman. We're here covering Splunk's Conf18, #conf, sorry, #splunkconf18, I've been fumbling that all week, Stu. Maybe by day two I'll have it down. But this is theCUBE, the leader in live tech coverage. Phillip Adams is here, he's the CTO and lead architect for the National Ignition Facility. Thanks for coming on. >> Thanks for having me. >> Super-interesting off-camera conversation. You guys are basically responsible for keeping the country's nuclear arsenal functional and secure. Is that right? >> Phillip: And effective. >> And effective. So talk about your mission and your role. >> So the mission of the National Ignition Facility is to provide data to scientists of how matter behaves under high pressures and high temperatures. And so what we do is basically take 192 laser beams of the world's largest laser in a facility about the size of three football fields and run that through into a target the size of a B.B. that's filled with deuterium and tritium. And that implosion that we get, we have diagnostics around that facility that collect what's going on for that experiment and that data goes off to the scientists. >> Wow, okay. And what do they do with it? They model it? I mean that's real data, but then they use it to model real-world nuclear stores? >> Some time back if you actually look on Google Earth and you look over Nevada you'll see a lot of craters in the desert. And we aren't able to do underground nuclear testing anymore, so this replaces that. And it allows us to be able to capture, by having a small burning plasma in a lab you can either simulate what happens when you detonate a nuclear warhead, you can find out what happens, if you're an astrophysicist, understand what happens from the birth of a star to full supernova. You can understand what happens to materials as they get subjected to, you know, 100 million degrees. (laughs) >> Dave: For real? >> Phillip: For real. >> Well, so now some countries, North Korea in particular, up until recently were still doing underground testing. >> Correct. >> Are you able to, I don't know, in some way, shape or form, monitor that? Or maybe there's intelligence that you can't talk about, but do you learn from those? Or do you already know what's going on there because you've been through it decades ago? >> There are groups at the lab that know things about things but I'm not at liberty to talk about that. (laughs) >> Dave: (chuckles) I love that answer. >> Stu: Okay. >> Go ahead, Stu. >> Maybe you could talk a little bit about the importance of data. Your group's part of Lawrence Livermore Labs. I've loved geeking out in my career to talk to your team, really smart people, you know, some sizeable budgets and, you know, build, you know, supercomputers and the like. So, you know, how important is data and, you know, how's the role of data been changing the last few years? >> So, data's very critical to what we do. That whole facility is designed about getting data out. And there are two aspects of data for us. There's data that goes to the scientists and there's data about the facility itself. And it's just amazing the tremendous amount of information that we collect about the facility in trying to keep that facility running. And we have a whole just a line out the door and around the corner of scientists trying to get time on the laser. And so the last thing IT wants to be is the reason why they can't get their experiment off. Some of these experimentalists are waiting up to like three, four years to get their chance to run their experiment, which could be the basis of their scientific career that they're studying for that. And so, with a facility that large, 66 thousand control points, you can consider it 66 thousand IOT points, that's a lot of data. And it's amazing some days that it all works. So, you know, by being able to collect all that information into a central place we can figure out which devices are starting to misbehave, which need servicing and make sure that the environment is functional as well as reproducible for the next experiment. >> Yeah well you're a case-in-point. When you talk about 66 thousand devices, I can't have somebody going manually checking everything. Just the power of IOT, is there predictive things that let you know if something's going to break? How do you do things like break-fix? >> So we collect a lot of data about those end-point devices. We have been collecting them and looking at that data into Splunk and plotting that over time, all the way from, like, capacitors to motor movements and robot behavior that is going on in the facility. So you can then start getting trends for what average looks like and when things start deviating from norm and set a crew of technicians that'll go in there on our maintenance days to be able to replace components. >> Phillip what are you architecting? Is it the data model, kind of the ingest, the analyze, the dissemination, the infrastructure, the collaboration platform, all of the above? Maybe you could take us inside. >> I am the infrastructure architect, the lead infrastructure architect, so I have other architects that work with me, for database, network, sys admin, et cetera. >> Okay, and then so the data, presumably, informs what the infrastructure needs to looks like, right, i.e. where the data is, is it centralized, de-centralized, how much is it, et cetera. Is that a fair assertion? >> I would say the machine defines what the architecture needs to look like. The business processes change for that, you know, in terms of like, well how do you protect and secure a SCADA environment, for example. And then for the nuances of trying to keep a machine like that continually running and separated and segregated as need be. >> Is what? >> As need be. >> Yeah, what are the technical challenges of doing that? >> Definitely, you know, one challenge is that the Department of Energy never really shares data to the public. And for, you know, it's not like NASA where you take a picture and you say, here you go, right. And so when you get sensitive information it's a way of being able to dissect that out and say, okay well now we've got to use our community of folks that now want to come in remotely, take their data and go. So we want to make sure we do that in a secure manner and also that protects scientists that are working on a particular experiment from another scientist working on their experiment. You know, we want to be able to keep swim lanes, you know, very separated and segregated. Then you get into just, you know, all of these different components, IT, the general IT environment likes to age out things every five years. But our project is, you know, looking at things on a scale of 30 years. So, you know, the challenges we deal with on a regular basis for example are protocols getting decommissioned. And not all the time because, you know, the protocol change doesn't mean that you want to spend that money to redesign that IOT device anymore, especially when you might have a warehouse full of them and then back-up, yeah. >> So obviously you're trying to provide access to those who have the right to see it, like you say, swim lanes get data to the scientists. But you also have a lot of bad guys who would love to get their hands on that data. >> Phillip: That's right. >> So how do you use, I presume you use Splunk at least in part in a security context, is that right? >> Yeah, we have a pretty sharp cyber security team that's always looking at the perimeter and, you know, making sure that we're doing the right things because, you know, there are those of us that are builders and there are those that want to destroy that house of cards. So, you know, we're doing everything we can to make sure that we're keeping the nation's information safe and secure. >> So what's the culture like there? I mean, do you got to be like a PhD to work there? Do you have to have like 15 degrees, CS expert? I mean, what's it like? Is it a diverse environment? Describe it to us. >> It is a very diverse environment. You've got PhD's working with engineers, working with you know, IT people, working with software developers. I mean, it takes an army to making a machine like this work and, you know, it takes a rigid schedule, a lot of discipline but also, you know, I mean everybody's involved in making the mission happen. They believe in it strongly. You know, for myself I've been there 15 years. Some folks have been there working at the lab 35 years plus, so. >> All right, so you're a Splunk customer but what brings you to .conf? You know, what do you look to get out of this? Have you been to these before? >> Ah yes, you know, so at .conf, you know, I really enjoy the interactions with other folks that have similar issues and missions that we do. And learning what they have been doing in order to address those challenges. In addition staying very close with technology, figuring out how we can leverage the latest and greatest items in our environment is what's going to make us not only successful but a great payoff for the American taxpayer. >> So we heard from Doug Merritt this morning that data is messy and that what you want to be able to do is be able to organize the data when you need to. Is that how you guys are looking at this? Is your data messy? You know, this idea of schema on read. And what was life like, and you may or may not know this, kind of before Splunk and after Splunk? >> Before Splunk, you know, we spent a lot of time in traditional data warehousing. You know, we spent a lot of time trying to figure out what content we wanted to go after, ETL, and put that data sets into rows and tables, and that took a lot of time. If there was a change that needed to happen or data that wasn't on-boarded, you couldn't get the answer that you needed. And so it took a long time to actually deliver an answer about what's going on in the environment. And today, you know one of the things that resonated with me is that we are putting data in now, throwing it in, getting it into an index and, you know, almost at the speed of thought, then being able to say, okay, even though I didn't properly on-board that data item I can do that now, I can grab that, and now I can deliver the answer. >> Am I correct that, I mean we talk to a lot of practitioners, they'll tell you that when you go back a few years, their EDW they would say was like a snake swallowing a basketball. They were trying to get it to do things that it really just wasn't designed to do, so they would chase intel every time intel came up with a new chip, hey we need that because we're starved for horsepower. At the same time big data practitioners would tell you, we didn't throw out our EDW, you know, it has its uses. But it's the right tool for the right job, the horses for courses as they say. >> Phillip: Correct. >> Is that a fair assessment? >> That is exactly where we're in. We're in very much a hybrid mode to where we're doing both. One thing I wanted to bring up is that the message before was always that, you know, the log data was unstructured content. And I think, you know, Splunk turned that idea on its head and basically said there is structure in log data. There is no such thing as unstructured content. And because we're able to rise that information up from all these devices in our facility and take relational data and marry that together through like DB Connect for example, it really changed the game for us and really allowed us to gain a lot more information and insight from our systems. >> When they talked about the enhancements coming out in 7.2 they talked about scale, performance and manageability. You've got quite a bit of scale and, you know, I'm sure performance is pretty important. How's Splunk doing? What are you looking for them to enhance their environment down the road, maybe with some of the things they talked about in the Splunk Next that would make your job easier? >> One of the things I was really looking forward to that I see that the signs are there for is being able to roll off buckets into the cloud. So, you know, the concept of being able to use S3 is great, you know, great news for us. You know, another thing we'd like to be able to do is store longer-lived data sets in our environment in longer time series data sets. And also annotate a little bit more, so that, you know, a scientist that sees a certain feature in there can annotate what that feature meant, so that when you have to go through the process of actually doing a machine-learning, you know, algorithm or trying to train a data set you know what data set you're trying to look for or what that pattern looks like. >> Why the S3, because you need a simple object store, where the GET PUT kind of model and S3 is sort of a de facto standard, is that right? >> Pretty much, yeah, that and also, you know, if there was a path to, let's say, Glacier, so all the frozen buckets have a place to go. Because, again, you never know how deep, how long back you'll have to go for a data set to really start looking for a trend, and that would be key. >> So are you using Glacier? >> Phillip: Not very much right now. >> Yeah, okay. >> There are certain areas my counterparts are using AWS quite a bit. So Lawrence Livermore has a pretty big Splunk implementation out on AWS right now. >> Yeah, okay, cool. All right, well, Phillip thank you so much for coming on theCUBE and sharing your knowledge. And last thoughts on conf18, things you're learning, things you're excited about, anything you can talk about. >> (laughs) No, this is a great place to meet folks, to network, to also learn different techniques in order to do, you know, data analysis and, you know, it's been great to just be in this community. >> Dave: Great, well thanks again for coming on. I appreciate it. >> Thank you. >> All right, keep it right there, everybody. Stu and I will be right back with our next guest. We're in Orlando, day 1 of Splunk's conf18. You're watching theCUBE.

>> From the Regency Center in San Francisco, it's theCUBE, covering Serverlessconf, San Francisco, 2018. Brought to you by SiliconANGLE Media. >> Hi, I'm Stu Miniman, and you're watching theCUBE here at Serverlessconf, 2018 in San Francisco. Happy to welcome to the program Michael Garski, who's the director of platform engineering at Fender. Thanks so much for joining me. >> Thanks, Stu. Thanks for having me on. >> All right, so, luckily, I don't need to introduce Fender because I think most of our audience will be familiar with, you know, Fender, guitars, music, all that stuff, but we're going to talk a little bit about the tech side. >> Okay. >> Even though, let me ask, there's a question I usually ask. Most companies, you know, going through the digital transformation, lots of changes there. How does digital impact Fender? >> Digitally, Fender started a digital division in late 2015 and it was a focus on all-new digital products to complement our well-known physical products. Since then we've launched Fender Mod Shop, where a user can order a customized guitar online, have it delivered in a month. We have a single sign-on solution across all of our web and mobile applications, a guitar tuner, we have connected amplifiers, with companion apps to control amplifiers remotely. And our flagship product is Fender Play, which is an instructional app which allows the user to learn to play guitar, ukulele, and coming soon, bass. >> Love it. I'm guessing that has something to do with what you're involved with on the cloud and Serverless side to enable those technologies on the mobile side. >> Exactly. We've fully embraced AWS Lambda to support all of the services for the web and mobile applications. >> Okay, so A Cloud Guru's a training company and we've talked to them extensively as to why Serverless was a good fit for them, and enabled them to do it, but bring us through what led to your adoption of AWS Lambda, give us a little bit about what kind of technologies you were using before, and how you got to this solution. >> Well, we started out building services and go, just standard EC2 based microservices, and then we started tinkering a bit with Lambda. We had to adjust the product catalog from SAP. They could deliver a file, drop it into an S3 bucket, so it was simple enough to create a function that can process that file and ingest it into elastic search. From there, we used custom authorizers with API Gateway mapping templates to save custom tunings for users, and then as we started building for Tone and Play, Tone especially is a very limited audience. It's whoever buys the amplifiers. So we're not talking millions of people, it's going to be hundreds of thousands. So, it was a very good use case to go ahead and do that. Same thing with Play, we're starting a new business that's a great model for us, that we can just pay per usage. >> All right, so, yeah it sounds like you were using cloud and the usage model fit for what Serverless was built for, correct? >> Exactly, yes. >> All right, how much is management aware of, you know, kind of the underlying technology? Is your group, kind of just allowed free reign to kind of deal with this? Or are there anything you need to go to the CFO, and be like, well, you know our billings going to change a little bit compared to what you might have known in the past? >> It's, we pretty much have free reign. And our biggest AWS expense is actually what we pay for, in AWS Glacier for storage for the raw footage, of all the 4K footage from, instructional video shoots, and Lambda on top of that is simply a rounding error. >> Yeah, excellent. And the mobile apps that you've built, are there trials on there? Is everybody up to sign-up to be able to use it? Is it a freemium model or is it a paid model? >> The Tuner is a completely free application. There is an in-app purchase for cord and scale libraries, and some pro features of the tuner. Custom tunings are free. The Play application comes with a 30-day free trial, so user can sign up either on the web, or via the Google or Apple app stores on their mobile device. >> Okay, so, with that kind of model, I would think that Lambda would be nice. There's, you know, you said your expenses aren't that high using this kind of service. >> No, not at all, like I, in the month of June, we spent, I think it was like $132 for 68 million Lambda invocations. And to kind of put that in perspective a bit, it's what we pay for some EC2 services, EC2 instances that support our legacy authentication service, but we're also moving that over to Cognito now so we can get rid of all the EC2 instances. >> Okay, when you started using this technology, how'd you first learn about it? How'd you get up to speed on it? Tell us a little bit about kind of, training adoption. >> It was a lot of experimentation. So, we have it set up where we use one account for our QA and production environments and another account for our development environment. All the engineers on the team have free-reign to do whatever they want to in the development environment. They can spin up whatever they need to. So we just started playing around with things and experimenting. Like, let's hook up Lambda function to API Gateway, oh, this is going to work really well! And just kind of proceeded down that path. >> All right, great, and any learnings, anything that you tried playing with and said, like wow, this just isn't going to be a fit for what I need? Tell us, you know, what worked, what didn't? >> I would say about the only thing we found that really doesn't fit within Lambda and Serverless would be really very low latency applications. You're doing an auto complete for a search system. You want that snappy. It's, humans observe, I think it's about 100 milliseconds things seemed instantaneous, and that's going to be very challenging to get from API Gateway Lambda to get that consistently. >> Okay, great. And you're speaking here at the conference, how'd that end up happening, what are you looking to share with your peers? >> How it happened was I submitted a talk for a conference and then Drew from A Cloud Guru approached me and asked me to submit I had to tell him I already did, so they went ahead and approved it. And, I'm sharing what we've done and built at Fender Digital, and sort of what we found as far as tools for monitoring, performance optimization, as well as some things to really be cautious of when you're dealing with Lambda, especially with regards to concurrency controls. >> 'Kay, great and, how have you found the show so far? You were at the keynote, got about 500 people here. >> Yeah, it's really interesting. I'd really like the focus all on Serverless. You see, go to a lot of conferences, there might be one or two talks that kind of focus on that. It's nice to have something completely focused in that space. >> All right, and, you know, from a maturity standpoint, are there things that you're looking for in the roadmap from Amazon? They've been baking Serverless kind of into all of their services, so do you expect to stay on Lambda, or are there other services that kind of, you know FAZ or Serverless built into it that you might be using? >> We expect to stay on Lambda for the near term. I don't, we don't have any plans or looking at anything else like Azure or Google Cloud functions, our intention is to stay with AWS. They have a lot of other services, their new machine learning services, we use DynamoDB quite extensively, and so we're probably going to stick with them. >> Yeah, but inside Amazon, they've been expanding their Serverless portfolio as it was. >> Oh, yeah. >> And I remember, I was at the show when Lambda was announced, and then, you know it's Aurora with Serverless underneath and all those, so do you expect to adopt some of those other services that have AWS Serverless kind of baked into it as opposed to just using, kind of a Lambda tool. >> Absolutely, especially with, you just mentioned the Aurora Serverless model. That's one that we're taking a look at and evaluating as we've got some data in DynamoDB, but as requirements have shifted in the business over time it's really, it's becoming very difficult to model in DynamoDB, so we're going to kind of take a look at that, and possibly move to Aurora Serverless. >> I'm curious, how does Fender, does Fender think of the data involved? Is that something that, you mentioned AI, some of these, is that something that you'll be able to take the data and leverage that potentially even make new business revenue streams out of that in the future? >> We're doing some of that already by just watching user, analyzing user behavior so we can improve our products internally. And we're looking at adding more features to where we can really understand what people are doing, and then make our products better. >> All right. Michael, want to give you the final word. For your peers out there that might be saying hey, I've heard of Serverless, I'm kind of thinking at it, what advice would you give them? >> Just dive in, get started, don't hesitate. It's, it doesn't cost you anything, really to experiment with it. That model works very, very nice. >> Yeah, and it's one of the things that's great. It used to be you would take a lot of period of time and some big investment to be able to try a technology out or maybe you would get some demo, but Serverless is pretty easy to get started on. >> Exactly. Especially if you're using a framework like say, Serverless framework, or maybe using AWS. Excuse me, AWS's Serverless application model, it really helps as far as setting up all the resources that your function needs as well. >> All right well, Michael really appreciate you riffing with us on your deployments with Serverless and hope your peers will definitely check it out. All right, lots more coverage here from The Serverless Conference here in San Fransisco. I'm Stu Miniman, and thanks for watching theCUBE. (electronic music)

>> Announcer: Live from the Moscone Center, it's The Cube covering AWS Summit San Francisco 2018. Brought to you by Amazon Web Services. >> Welcome back to our exclusive Cube coverage here at AWS, Amazon Web Services Summit 2018 in San Francisco. I'm John Furrier with my cohost, Stu Miniman. We have a special guest. We have an influencer, authority figure on AWS, Corey Quinn, editor of Last Week in AWS, also has got a podcast called Screaming, >> Corey: In the Cloud. >> Screaminginthecloud.com just launched. Corey, great to have you on. Thanks for joining us. >> No, thank you for letting me indulge my ongoing love affair with the sound of my own voice. (laughing) >> Well we love to have you on and again, love the commentary on the keynote on Twitter. Lot of action, we were in the front row, kind of getting all the scene. Okay, if you're going to write the newsletter next week for what happened this week, if this week was last week, next week, what's your take on this? Because again, Amazon keeps pounding the freight train that's just the cadence of AWF announcements. But they're laying it out clear. They're putting up the numbers. They're putting out the architecture. They're putting out machine learning. It's more than developers right now. What's your analysis, what's your take of what's happening this week? >> I think that certain trends are continuing to evolve that we've seen before where it used to be that if you're picking an entire technology that you're going to bet your business on, what you're going to build on next. It used to be which vendor do I pick, which software do I pick? Now even staying purely within the AWS ecosystem, that question still continues to grow. Oh so I want to use a database, great. I have 12 of them that I can choose between. And whatever I pick, the consensus is unanimous, I'm wrong. So there needs to be, I still think there needs to be some thoughtful analysis done as far as are these services solving different problems. If so, what are the differentiating points? Right now, I think the consensus emerges that when you look into a product or service offering from AWS, the first reaction all of us feel is to some extent confusion. I'm lost, I'm scared. I don't really know what's going on. And whatever I'm about to do, I feel like I'm about to do it badly. >> Yes, scale is the big point. I want to get your reaction. Matt Wood, Dr. Matt Wood, Cube alum, been on many times, he nailed it I thought when he said, look it, machine learning and data analysis was on megabytes and gigabytes, they're offering petaflop level compute, high performance, and then Werner Vogels has also said something around the services where, you can open things up in parallel scale. So, what's your reaction to that, as you look at that and say whoa, I've got a set of services I can launch in parallel, and the scale of leveraging that petaflops. I mean, this is kind of like the new, you know, compute model. Your reaction is it real? Are customers ready for it? Where are we in that evolutionary customer journey? Are they still cavemen trying to figure out how to make fire and make the wheel? I mean where are we with this? >> I think that we see the same thing continuing to emerge as far as patterns go, where they talk about, yes there's this service. Just start using it and it scales forever. And that's great in theory, but in practice, all of the demos, all of the quick starts, all of the examples, paint by numbers examples that they'll give you, tend to be at very small scale. And yes, it works really well when you have effectively five instances all playing together. When you have 5,000 of those instances, a lot of sharp edges start to emerge. Scale becomes a problem. Fail overs take far longer. And let's not even talk about what the bill does at that point. Additionally once you're at that point, it's very difficult to change course. If I write a silly blog, and effectively baby seals get more hits than this thing does, it's not that difficult for me to migrate that. Whereas if I'm dealing with large scale production traffic that's earning me money on a permanent basis, moving that is no longer trivial or in some cases feasible at all. >> Yeah Corey, how does anybody reasonably make a decision as to how they're going to build something because tomorrow, everything might change. You said oh okay great, I had my environment and I kind of you know, built my architecture a certain way, oh wait there's a new container service. Oh, and start building a, oh wait now there's the orchestrated version of that that I need to change to. Oh wait, now there's a serverless built way that kind of does it in a similar way. So you know, it seems like it used to be the best time to do things would've been two months ago, but now I should do it now. Now the answer is, the best time for me to do things would be if I could wait another quarter, but really I have to get started now. >> I tend to put as much on future Corey as I possibly can. The problem is that at one time I could've sat here and said the same thing to you about, oh virtualization is the way to go. You should migrate your existing bare metal servers there. And then from virtualization to Cloud and Cloud to containers. Then containers to serverless. And this narrative doesn't ever change. It's oh what you're doing is terrible and broken. The lords of thought have decried that now it's time to do this differently, and that's great, but what's the business use case for doing it? Well, we did this thing that effectively people get on stage at keynotes and make fun of us for now, so we should really change it. Okay maybe, but why? Is there a business value driving that decision? And I think that gets lost in the weeds of the new shiny conference ware that gets trotted out. >> Well I mean Amazon's not, I mean they're being pretty forthright. I mean, you can't deny what Intuit put out there today. The Intuit head of machine learning and data science laid out old way, new way. Classic case of old way, new way. Eight months, six to eight months, ton of cluster, you-know-what going on as things changed it. They're just data scientists. They're not back-end developers. They went to one week. Nine months to one week. That's undeniable right? I mean how do you, I mean that's a big company but, that seems to be the big enchilada that Amazon's going for, not the pockets of digital disruption. You know what I'm saying? So it's like, how do you square that out? I mean how do you think about that? >> Cloudability had a great survey that they released the results of somewhat recently where they were discussing that something like four or five of the, or I'm sorry 85% of the global spend on AWS went to four or five services that all have been around for a long time. RDS, EC2, S3, PBS, Data Transfer. And so as much as people talk about this and you're seeing pockets of this, it's not the common gaze by a wide margin. People don't get up on stage and talk about, well I have these bunch of EC2 instances behind a low balancer, storing data on S3 and that's good enough for me, because that's not interesting anymore. People know how to do that. Instead, they're talking about these far future things that definitely add capability, but do come at a cost-- >> I mean it's the classic head room. It's like here's some head room, but at the end of the day it's EC2, S3, Kinesis, Redshift, bunch of services that's U.S that seem to dominate. The question I want to ask you is that they always flaunt out the, every year it changes, Kinesis was at one point the fastest growing service in the history of AWS. Now it's Aurora. We made a, I made a prediction on the opening that a SageMaker will be the fastest growing service, because there just seemed to be so much interest in turn-key machine learning. It's hard as you-know-what to do it. >> I agree. >> Your thoughts on SageMaker? >> In one of my issues a few weeks back, I wound up asking, so who's using SageMaker and for what? And the response was ridiculous. What astounded me was that no two answers were alike as far as what the use case was. But they all started the same way. I'm not a data scientist, but. So this is something that's becoming-- >> John: What does that mean to you? What does that tell you? >> It tells me that everyone thinks they're unqualified to be playing around in the data science world, but they're still seeing results. >> But Corey I wonder because you know, think back a few years ago. That's what part of the promise of big data, is we have all this data and we're going to be able to have the business analysts rather than you know, some PhD sort this out. And machine learning is more right. We want to have these tools and we want to democratize data, you know. Data is the new bacon. It's the new oil. Data's the new everything. So you know, machine learning, you think this is all vapor and promise, or do you think it's real? >> I think big data is very real and very important. Ask anyone who sells storage by the gigabyte. And they will agree with me. In practice I think it's one of those areas where the allure is fascinating but the implementation is challenging. Okay we have history going back 20 years of every purchase someone has ever made in our book store. That's great, why do I still wind up getting recommendations? >> Well yeah and I guess, I want to talk that it was the, I see it more as, everything that was big data is now kind of moving to the ML and AI stage. Because big data didn't deliver on it, will this new wave deliver on the promise of really extracting value from my data? And it's things like this, live data. It's doing things now with my data, not the historical, lots of different types of data that we were trying to do with like the Hadoops of the world. >> Got ya. I think it's a great move because either yes it will or no it won't, but if it doesn't, you're going to see emergent behaviors of so why didn't it work? Well we don't understand the model that this system has constructed, so we can't even tell you why it's replacing the character I with some weird character that's unprintable, so let alone why we decide to target a segment of customers who never buys anything. So it does become defensible from that perspective. Whether there's something serious there that's going to wind up driving a revolution in the world of technology, I think it's too soon to say and I wouldn't dare to predict. But I will be sarcastic about it either way. >> Okay well let's get sarcastic for a second. I wan to talk to you about some moves other people are making. We'll get to the competition in a minute but Salesforce required MuleSoft. That got a lot of news and we were speculating on our studio session this week or last week with the CEO of Rubric that it's great for Salesforce. It can bring structured data in, on PRIM and the Cloud. Salesforce is one big SaaS platform. Amazon is trying to SaaS-ify business through the Cloud. So, but one of the things that's missing from MuleSoft is the unstructured data. So the question for you is, how are you seeing and how is your community looking at the role of the data as a strategic asset in a modern stack, one, both structured and unstructured data, is that becoming, even happening or is it more like, well we don't even know what it means. Your thoughts? >> I think that there's been a long history of people having data in a variety of formats and being able to work with that does require some structure. That's why we're seeing things emerging around S3's, increasing capabilities, being able to manipulate data at rest. We're seeing that with S3 and Glacier Select. We're seeing it with Athena which is named after the goddess of spending money on Cloud services, and there's a number of different tooling options that are, okay we're not going to move three x-abytes of data in so we have to do something with where it is. As far as doing any form of analysis on it, there needs to be some structure to it in order for that to make sense. From that perspective, MuleSoft was a brilliant acquisition. The question is, is what is SalesForce going to do with that? They have a history of acquisition, some of which have gone extremely well. Others of which we prefer not to talk about in polite company. >> It comes back down to the IDE thing. How many IDE's does Salesforce have now? I mean it's a huge number. >> I'm sure there's three more since we've started talking. (laughing) >> Yeah so Corey, you brought up, you know, money. So you know, the trillion dollar, what feedback are you getting from the community? You know there's always, well I get on Amazon and then my bills continue to grow and continue to grow. Same thing at Salesforce by the way if you use them. So you know, there's always as you gain power, people will push back against it. We saw with with Mike Hichwa with Oracle. I hear it some but it's not an overriding thing from when I talk to customers about Amazon. But I'm curious what you're hearing. Where are the customers feeling they're getting squeezed? Where is it you know, phenomenal? What are you seeing kind of on the monetary side of Cloud? >> In my day job, I solve one problem. I fix the horrifying AWS bill, both in terms of dollars and cents as well as analysis and allocation. And what astonishes me, and I'm still not sure how they did it. It's that AWS has somehow put the onus onto the customer. If you or I go out and we buy a $150,000 Ferrari, we wake up with a little bit of buyer's remorse of dear lord, that was an awful lot of money. When you do the equivalent in AWS, you look at that, and instead of blaming the vendor for overcharging, instead we feel wow, I'm not smart enough. I haven't managed that appropriately. Somehow it's my fault that I'm writing what looks like a phone number of a check every month over to AWS. >> John: It creeps up on you. >> It does. It's the boiling a frog problem. And by the time people start to take it seriously, there's a lot of ill will. There's a sense of, our team is terrible, and wasn't caring about this. But you don't ever cost-optimize your way to success. That's something you do once you have something that's up and working and viable. You don't start to build a product day one for the least possible amount of money and expect to attain any success. >> Well let's talk about that real quick to end the segment because I think that's a really important thing. Success is a double-edged sword. The benefit of the Cloud is to buy what you need, get proof of concept going, get some fly wheels going or whatever, virtuous circle of the application. But at some point, you hit a tipping point of oh shit this is working. And then the bill is huge. Better than over-provisioning and having a failed product. So where's that point with you guys or with your customers? Is there like analytics you do? Is that more of a subjective qualitative thing? You say, okay are you successful? Now let's look at it. So how do you deal with customers? 'Cause I can imagine that success is, it becomes the opportunity but also the problem. >> I think it's one of those, you know it when you see it type of moments, where if a company is spending $80,000 a month on their Cloud environment and could be spending 40, that's more interesting to a company that's three people than it is to an engineering team of 50. At that point, sorry they're embezzling more than that in office supplies every month. So that's not the best opportunity to start doing an optimization pass. More important than both of those scales to me has always been about understanding the drivers of it. So what is it that's costing that? Is it a bunch of steady state things that aren't doing work most of the time? Well, maybe there's an auto-scaling story in there. Maybe there's a serverless opportunity. Maybe nobody's using that product and it's time to start looking at rolling it in to something. >> They've left the lights on right? So to speak. >> Exactly. >> The server's are still up. Wait a minute, take them down. So, writing code, analytics, is that the answer? >> All of the above. In a vacuum, if you spin up an instance today, and don't touch it again, you will retire before that instance does. And it will continue to charge you every hour of every day. Understanding and being able to attribute who spun that up, when was it done, why was it done, and what project is it tied to? Is it some failed experiment someone did who hasn't worked here in six months? Or is that now our master database? We kind of need to know in either direction what that looks like. >> Alright before we wrap, you got to tell us, what do we expect to hear from your podcast? >> Good question. My podcast generally focuses on one-on-one conversations with people doing interesting things in the world of Cloud, which is vague enough for me to get away with almost anything as far as it goes. It's less sarcastic and snarky than some of my other work, and more at the why instead of the how. I'm not going to sit here and explain how to use an ABI. There are people far better at that than I am. But I will talk about why you might use a service, and what problem it reports to solve. >> Alright Corey, great to have you on. Uh the Screaming Pod, Screaming Cloud, >> Corey: ScreamingInTheCloud.com >> ScreamingInTheCloud.com, it's a podcast. Corey thanks for coming on and sharing the commentary, the insight on AWS, the how and the why, the Cube breaking down. All the action here in Moscone Western San Francisco, AWS 2018 Summit, back after more, after this short break. (spacey music)