Oh from Las Vegas it's the cube covering AWS reinvents 2018 brought to you by Amazon Web Services Intel and their ecosystem partners well good morning welcome back to AWS reinvent this is day three of our coverage here on the cube we made it we have survived the show here that been a great show and still a lot of energy out here on the show floor Justin Morin John wall's we're with loose Ernie who is the CEO and founder of New Relic and and Luffy look just over your left shoulder there's that really impressive New Relic Pavillion you've got there we've been admiring it all week so that's a great show for us and you know our our theme this yours is billed fast and break nothing because that's really the objective of moving to the cloud is building software that customers value as rapidly as possible when you're building stuff fast there's risk and so how do you build fast with breaking nothing it's measuring everything in real time everything in that environment seeing exactly what's going on so you can make sure the stuff you're building works for your customers and that's what we do for so many people were adopting the Amazon Cloud kind of reminds me of John Wooden yield UCLA basketball coach had said be quick but don't hurry that's all right so that's right so it was all about pace and I understand putting that culture in the team so how do you put that culture and into with your well I you know it's it's one of the great truths how can you manage what you can't measure so we're a company that makes it trivially easy to measure software infrastructure digital customer experience our customers come to us every day and say what I love about New Relic is within seconds of setting up my account and and deploying the agent all of a sudden production is lit up I can see what's going on that measurement helps our customers have more confidence moving to the cloud faster deploying more frequently delivering customer value more rapidly now one of the themes that we've had over the last couple of days and John and I were talking just before we came on this morning that complexity yeah we've been hearing that time and time the amount of change it's happening so quickly and we've got all of these different systems we got micro services we've got containers we've got serverless it's a really complicated environment yeah how do you help the humans understand how how do you get them to understand what's going on in this really complex environment that's moving so fast you're you're absolutely hitting on the key challenge and what we're great at what our customers tell us they love about us is we simplify that complexity and and there's how do we simplify it well we have a deep understanding of how these systems work and we've fought very hard about how do you surface the interesting information that's most relevant to understanding the health and application and really in that moment when there's a problem how do you make it as easy as possible to understand the cause that problem as rapidly as possible this is like our customers they're right in the you know right in the pit of the most high pressure situations when there's a production issue every second counts every second counts you got to find that issue as rapidly as possible and what our customers tell us is they're sick of having to juggle around between three four five many of our customers have dozens of tools that are intended to watch production they turned a new rally platform cause it's all in one platform and when seconds matter you don't want to be switching between tools and context to understand what the nature the problem is and that's that's super important it's kind of like we all become pack rats in a way right yeah we save things we just keep putting them in this room and this room in this room and it comes time to kind of clean up or yeah get our act together and that's what you're doing for people is helping them get their act together absolutely and once you've got an understanding of how the system provides you go from overly cautious and timid to confident and with that confidence you can start playing offense with software we talk about all the time 15 20 years ago IT leaders thought of software as a defensive mechanism when I say defense I mean it's a way to reduce costs how do I reduce the cost of billing how do I reduce the cost of handling a support call now it's offense it's the growth engine for these companies right the digital customer experience is driving top-line growth and so when you're confident your ability to move fast with your software you're actually participating to growth your company that's why it's so strategic that's why the cloud is growing so rapidly so if you've got a customer who's not with you really clearly you want them to they should be going with you what if what does it feel like to go from not having New Relic in there and dealing with this complexity and having those struggles and then as you've put in New Relic for the first time what's what's that onboarding experience feel like I once was blind and now I see John Newton America it's truly that our customers tell us that before I discovered new relic I had no idea was going on production and it was opinions that we're telling us what was going on and when you've got a bunch of teams working on a complex system and there's a problem and it's like the loudest opinions gonna determine how you go forward that results in chaos and it results in organizational misalignment and with data all of a sudden people are lying on how you move forward yeah so with all that data that's there I mean that that can actually be complex itself if I'm trying to see everything all at once that that can be overwhelming so how do you help customers dial in on what's actually important within this this sea of information that they can now now look at well you know we have a variety of ways in which we approach that problem um the first is an opinionated user interface okay we have more experience in the realm you know my first company I founded in 1998 created the category of application performance management and so I've been thinking about this problem might ease the think about this problem for a long time we come to our customers with an opinion on what matters in the application environment but even then beyond that we're layering on well AI but we call it applied intelligence because artificial intelligence people overuse the term and honestly our customers don't care whether we're using a collaborative filter or good old-fashioned algorithms but they want to split more smarts in our platform to tell them what's anomalous tell them what's abnormal tell them what to pay attention to in this sea of data you really collects about 15 million data points every second off of our customers applications and infrastructure and digital customer experiences 15 million data points every second coming to the New Relic Cloud and we analyze all of it in real time to service to our customers what's important what's anomalous and what's interesting yeah so let's get into that let's go about what's anomalous and what's interesting yeah how do you differentiate that because as you said out of 15 million data points every second yeah I mean you're gonna develop trends but but it's by the time you evaluate it seems like one set of data you're off to a completely different set of data and you're right this is a very dynamic environment well the combination of an understanding of how applications work in general but then the flexibility to recognize you know how an e-commerce application might be very different from a Content application like USA Today networks is a big New Relic customer and so we need to provide enough of a platform that our customers can give New Relic some guidance on the nature of their application and and and we can discover its architecture and we can discover things about it but we we really can't discover its business purpose and so there's a combination of what we do out of the box with the customizability that that get our customers the point where the software's doing the work for them you're on so having been in the show now for three four days what have you seen around here what a customer's looking at that they're gonna bring it bring it on to their environment next what are some of the things I think you know lambda is coming mainstream right right and so when we think about where where the world is going you know micro services are going to be here for a while just like all the other technologies you said like the packrat analogy is true but future in the future when someone starts a brand new project they won't even think about infrastructure they'll just think about their code and new relics philosophy on visibility is you start with the software because the software is that the whole the business logic the whole point of all this infrastructure is to run software and so our most important starting point for visibility is the software itself we just made an announcement this week about delivering the first product that automatically instrument lambda to tell you if your lambda function is misbehaving exactly how is it doing that and so as the world continually moves from the old IT used to obsess on infrastructure and and and and new ideas is obsesses on how do we deliver more software faster and that that aligns very well with what we're great what our philosophy is on delivering his ability it starts and ends with the software and it feels like people are going into lambda really quite quickly because absolutely moving with some meetings this morning that they were saying that there's enterprises in particular may not have actually jumped onto the container bandwagon yet but they've looking at laminate is going you know what we're just gonna skip leapfrog to that yeah I'm seeing quite a bit of that containers still have an awful lot of value there they're wonderful lightweight ways to host what used to be on you know in a virtualized environment and get that isolation all that benefit kubernetes is also a big deal we made an acquisition of a company called coast scale that we announced last quarter that accelerates our capability to do work in kubernetes environments we're always inspired by what our customers are doing to accelerate how they build their software and that inspires us to make sure our platforms continually their tool a choice to make sure they can see the entire environment so you're getting as much for them as they're getting from you absolutely it's a great partnership we have with our customers we learn from them and then we provide them with thought leadership on how do you think about making sure you're seeing the entire environment so you can spend more time delivering great software and less time debugging it excellent well let's get back to that great booth of your awesome great for being with us we're sharing our a relic story and success on the the last day of the show all right well mate ok all right excellent right loser T joining us you from New Relic back with more here with AWS reinvent you're watching the cube from Las Vegas

>> Live from Las Vegas, it's theCUBE. Covering AWS re:Invent 2018, brought to you by Amazon Web Services, Intel, and their ecosystem partners. >> Welcome back here at AWS re:Invent. Day three of our coverage here on theCUBE. We have been here since Tuesday, bringing you all kind of sights and insights from the show floor here. Some 40 guests that we've had on this set alone. Have a person that's actually four sets around here. There's a lot of content to capture. A lot of excitement in the air. And I'm John, that's Rebecca. I don't have to tell you that, you know that. We're joined by Ankit Khandelwal, who's the Senior Director of Engineering to Kyvos Insights. Good to see you, Ankit. >> Thank you, good to be here. >> And Ajay Anand, who's the Vice President of Products and Marketing at Kyvos as well. Thank you for joining us gentlemen. We appreciate the time. >> It's good to be back with you. >> All right, so share a little bit, just for folks at home who are watching and may not be familiar with Kyvos. I doubt there are many. (Rebecca laughing) But just in case, share with us a little bit, and with them, your core mission. >> Yeah, so what Kyvos does is we deliver the capability of doing instant business intelligence on data at a massive scale, either on-premises or in the cloud. So, one of the big problems people have is when they're trying to connect from their BI tools to huge amounts of data, it takes a long time for the data to come back into the tool. As they are dragging and dropping, they don't get that interactive response. So we solve that by building a BI consumption layer on top of the big data. And what that enables you to do is, you know, once we've pre-processed that data and built multi-dimensional cubes, then you can get that interactive response time, right. So the core technology is OLAP, which has been around for a long time. But what we do is we make OLAP scale to huge amounts of data and really take advantage of the capabilities of the cloud, or big clusters, and on-premises environments, and really scale out with the cloud. >> Can you give us some examples of who your customers are and the kind of specific problems you're solving for them? >> Sure, some of our customers have spoken publicly about us, so I can share what they said. Walgreens spoke about us at the Tableau Conference just a couple of weeks ago. And they're solving problems that they had never imagined they'd be able to solve before. Dealing with hundreds of billions of rows of data and getting instant responses. And these customers are building multi-dimensional cubes at a scale that's never been done before. 100 terabyte cubes. Walgreens is an example of that. Verizon has spoken about us at other conferences as well. >> Ankit, I'd like to know what your take is on, as we were just talking about, the volume that you're dealing with here. Like never before. How do you help your customers figure out what matters? What's important and what's not, because most, or I shouldn't say, much of what they generate really doesn't matter, and yet there are some valuable nuggets in there that they are still trying to extract and then analyze appropriately. So how do you help them with that job? >> Yeah, so you know what happens is organizations and enterprises keep getting more and more data. They take it to a data lake. Now, the data on the ground wasn't enough, and now you have other services which helps you get the data from even space. Andy announced that you can get data from satellite. So all this data. Now once that data reaches the data lake, the next challenge that comes to, or in front of a business user is, how do you really get the ROI out of it? Now when I say ROI, basically know I am talking about ROI of data. And the ROI of data actually improves, comes only when, the data goes in the hands of the business user. So that's the times Kyvos comes into the picture because you want your data and you want your business users to analyze it. It has to be super fast and that's what Kyvos does, number one, and number two, the business users want their data to see in a way that they want. So basically, Kyvos helps you to actually define a semantic layer, put a business view on top of your data. So that a business user actually sees the data the way they want. So those are the things that Kyvos provides and helps the business user to actually get the insights out of the data. >> So this week at AWS, you launched Version 5. Tell our viewers a little bit more about what Version 5 entails, some of the capacities. >> Right, so one big thing is the capability to do Elastic OLAP in the cloud. So the OLAP capability being able to really leverage the infrastructure cost-effectively, scale out to deal with big loads and scale it down as you're building these multi-dimensional cubes. So really being able to deal with the infrastructure cost-effectively and deal with massive amounts of data as you're building these cubes. So you can decide, I want to build a 100 terabyte cube and just spin up the right amount of infrastructure that you need to build that cube and then shrink it down. So that elastic capability both for cube building as well as querying. At Walgreens, they talk about dealing with hundreds and thousands of users both internal and external all connecting to this data using Tableau or some other BI tool, and being able to deliver that instant response to them. So having that elastic capability is the new capability we're offering. >> I think the point is, as Andy was talking about in his yesterday's keynote, if you can do it fast then why not do it fast? I think that's where cloud comes into the picture. That with our Kyvos 5 release, once you set up your Kyvos on the cloud, it could actually use that scalability or the elasticity of the cloud for its benefit and for the benefit of the customer. As the load increases, is that the complexity increases. We could actually scale out and deliver the performance that we promised to deliver. And then once the load actually reduces then we could again reduces the resources that we're consuming and that's how we actually reduce the cost that is borne by the customer. So essentially, that is again, you're now giving them better ROI on the hardware that they're investing on. >> So how do you pump the breaks a little bit on the speed? I mean, in terms of making sure that you're in control? Because speed's one thing, right, very important to have, but we need reliability, you need accuracy, latency is not as much of an issue, but how do you, pump the brakes might not be the right description, but how do you ensure that speed is not an inhibitor and it's actually a facilitator? >> There's a whole bunch of enterprise capabilities that we have to provide. Dealing with the resilience so that it's always available to their business users. Dealing with concurrency as you really scale out with the large numbers of users. Dealing with security, right. So as I mentioned, at Walgreens they've got external users as well as internal users, all accessing the same cube, and they all need to see only what they're allowed to see, right. So we maintain that security, right from the user to the data, and we keep track of who's allowed to see what and expose only that. So all of those capabilities are built into the product. >> And as an engineer, I can actually say that again I would take the code from Warner this morning that, hey, you really architecture it well. So architected the product right from the beginning to not only deliver the performance but also to be scalable, deliver performance at a scale. To be secure and then in order to be reliable, fault ordering. So those things are inherently built into the product but then putting a patch on top of the product. >> We're hearing so much at this conference that many enterprises have really had the ah-ha moment. I need to go to the cloud. The security, the governance, those concerns are really falling by the wayside. So what's next? I mean, now that we have so many companies migrating, where do we go from here? >> I think, what we are seeing is a lot of companies are still in the process of migrating. So they've had on-premises infrastructures. Now they're moving to a hybrid cloud and then moving to potentially everything in the cloud. So delivering a seamless experience to the business user is extremely important. Business users shouldn't have to care whether the data is on premises or in a hybrid cloud or in the cloud itself. They should get that same interactive response, the same familiar user interface, and that's what our BI layer provides. By delivering that consumption layer that sits the same way on premises as it was in the cloud. It's a completely seamless experience for the user. >> And I think the performance or the skills still presents a problem. The thing is, how can you make it easy to use for the user? How can I make it smarter? So I think that's where we are going towards with our latest releases, with Kyvos 5. We're bring certain capabilities into the product so that the user doesn't have to bother about how do you really create that semantic layer. The product is smart enough to tell there what should be included in there and what to leave out of it. So smartness is one area which we are moving towards so that we can help the business user to get the performance at a scale with a lot of ease of use. >> I assume you guys have been here for a day or two, correct? >> Yes. >> Right, you met with a lot of customers. I again would assume, right? >> Right. >> So what is your take-away going to be from those direct conversations you've had here in terms of what you take back to Kyvos and maybe start putting into practice? What are you hearing about, this is my next roadblock, this is my next barrier, this is what I'm going to come to you to help me fix. >> We heard Andy's talk this morning or was it maybe Warner. >> Yesterday, Warner this morning, yeah. >> So Warner's talk where they talk about, 95% of what goes into AWS comes from feedback from their customers, and that's true with us to a large extent. We learn from our customers, as they deploy these cubes and their environments, but what's important to them. What are the critical areas that we need to overcome. Really understanding their business use cases and making sure that we build that smartness into the product so we can see what kind of intelligence are they looking to gather, what kind of analysis are they looking to do. And then we use that to build the smartness into the cube. So that the user doesn't need to figure this out themselves. So that's one of the new capabilities that we are providing and we're continuing to work on, is to build more and more smartness into the product. So it helps the user go where they want to go. >> And I think as we go to cloud, specifically AWS, how can we really use the services required by the cloud and then how can we really provide a layer of extraction on top of what is already there, so that then it becomes really easy for the user to use whatever we are providing. >> Right. >> Great. Yeah, just, and I don't want to convolute this with things that I don't need and time and effort. It's all about money at the end of the day, right? Save me money, save me time. >> Well, it's not just saving money but really the topline benefit, right. So expanding the business opportunity. So, we've got a bank that's doing risk analysis as they look for new investments. It used to take them days to do that risk analysis before they could make a decision. Now they can do it in seconds. So their ability to make a decision much faster and react to market conditions, really opens the door for them for much greater business opportunity and revenue. So it's not just cost savings that's driving this. It's taking advantage of the opportunity. >> You bet. >> Because if the queries don't really come fast. Let's say you as a person sitting here and you fire a query and then it takes a lot of time, and you go back and then have a cup of coffee and then come back. Your chain of thought's actually broken. So you cannot explore from the data otherwise you could integrate it'll actually come within seconds. >> Gentlemen, thank you for being here with us. I hope the show's gone well for you. It sure does sound like it's been a success, and we look forward to seeing you down the road. >> Great. >> Thank you. >> Good to be here. >> Thanks. >> From Kyvos. >> Back with more in just a bit here on theCUBE. You're watching AWS re:Invent. (bright music)

>> Live from Las Vegas, it's theCUBE covering AWS re:Invent 2018 brought to you by Amazon Web Services, Intel and, their Ecosystem Partners. >> Okay, welcome back everyone. Day three, we're live in Las Vegas for AWS re:Invent 2018. It's our sixth year covering Amazon re:Invent and AWS, Amazon Web Services meteoric rise in value, profitability, market share, just a rising tide floating all boats. I'm here with Dave Vellante. We're kicking off day three analyzing, you know, Vernon's keynote. Things start to wind down. Yesterday was kind of the big day with Andy Jassy. Dave, after yesterday it's pretty clear that there's a couple big mega trends that people are talking about. One AWS Outpost, okay, that is going to be a one year conversation about what that means, what implications. I mean basically if you're a Cloud-native company you order a data center and Amazon Prime will deliver it in two days, why would anyone want to buy hardware again from HPE or other companies? This is a huge risk, huge challenge, a huge shot across the bow to the industry because this essentially the thing. This is essentially Cloud in a box. Put it in, plug it in, we'll service, turn it on and it works and developers can just do their thing, that's amazing. So I think that's going to be a very hotly-contested topic throughout, at least one year until they ship that and all the posturing and jockeying's going to go on there. And then the other thing that was interesting was there was a lot of coolness, the F1, Racing car with analytics. You had Lockheed Martin with space satellite provisioning, that was pretty cool. And, you know, you got robots and IoT. That's cool, you got space, you got robots, you got, you know, sports cars all using analytics, all using AI, all using large-scale compute storage and networking, very elastic, all with all kinds of new tools and reference engines, but Jerry Chen laid it out from Greylock yesterday around the strategy. Amazon drives the cost down on the infrastructure side and bring the API concept up to AI and bring the marketplace together. So, a lot of action. Today we're going to see the impact and the fallout of that. What's your thoughts? >> Well, first of all John, there's so much to talk about. I want to say, so Werner Vogels this morning gave the keynote. When, when I first joined, you know this industry, we, IBM was everything, IBM was the dominant player. So we used to pour over IBM system and technology guides, and IBM white papers, because they set the technical standard for the industry and they shared that knowledge obviously with their customers to inspire them to buy more stuff, but they were giving back to the community as well to help people understand architectures and core computer science. Listening to Werner Vogels today, Amazon is now the beacon of technology in the industry. He went through the worse day of his life, which was December 12, 2004 when their Oracle Database went down for 12 hours because of a bug in the code and because they were pushing it beyond its limits. And so he described how they solved that problem over a multi-year effort and really got heavy into the technology of database, and recovery, and it was actually quite fascinating. But my takeaway was Amazon is now the company that is setting the technical direction of the industry for the next wave of Cloud-based applications. So that was actually really fascinating. We heard similar things on S3 and S3 recovery, even though they're still using some Oracle stuff it was really, really fascinating to see and very, very impressive. So that's one. As you say, there's so much to talk about. The IoT pieces, John, I really like what Amazon is doing with IoT. They're coming at it from a bottoms up approach, what do I mean by that? Do you remember when mobile first came out Microsoft basically said, hey we're going to put Windows on a phone, top down. We're going to take our existing IT Desktop standards, we're going to push 'em down to mobile, didn't work. And I see a lot of IT companies trying to do that with IoT today, not Amazon. Amazon's saying, look we're going to go bottoms up and serve the operation's technology people with a software development platform that's secure, that allows it, that's fully managed and allows them to build applications for IoT. I think it's the right approach. >> I think the other thing that's coming out is a Tweet here from Bobby Allen who we know from theCUBE days. I, you know, when we, I shared a Tweet about, you know, the future of the converged infrastructure on the outpost he says, software should be where tech companies differentiation value lies. This is back to our beating of the drum about software, software, software, you know. Andy Bechtolsheim, the Rembrandt of motherboards, Pat Gelsinger calls him, said, he's the founder of Arista, hardware's easy, software's hard. Software's where the action is. What Amazon's doing is essentially pushing large-scale platform capabilities and trying to make that as cheap and affordable as possible, the range of services, while creating a new shim layer around API concepts and microservices up the stack to enable people to write software faster, more compelling, more meaningful, and to iterate, and this is resonating with customers, Dave, because if I'm a business I got to write software, okay. I don't want to be in the running data center business because the data center powers the business. So the end doesn't justify the means in that regard. You say, hey, I need a data center to power my top-line revenue which is either going to be software-based or some sort of Edge network scenario, or even a human interface wearable or whatever. Software is the key. So if Amazon can continue to push the cost structure the lock-in spec is locked in because the better value so if it's going to be 80% less cost, and you call that a lock-in spec? A lot of lock-in spec, it's not like a technical lock-in spec, that's just called value. >> I'm locked in to Google Search. I mean, you know, I don't know what to tell ya. I'm not going to use any alternative search I'm just familiar with it, I like it, it's better. >> But software's the key, your thoughts. >> Okay, so, my thoughts on lock-in are, lock-in is one of the most overstated concepts in the business. I'm not saying that lock-in doesn't happen, it does happen, it happens everywhere. It happens across open-source. You do open-source you're locked-in to your developers. I've done research on this John and my research shows that 15% of the buyers really make primary decisions based on whether or not they're going to be locked-in. 85% look at the business value and they trade that off against lock-in so, you know, yeah, buyer beware, blah, blah, blah, but I think it's just really overstated. Yes, it's a Cloud, mother of all lock-ins, but what's the value that you get out of it? Speaking about another lock-in. I want to talk about Intel a little bit because the press has been like chirping about, about Intel and alternative processors, and the arm-based stuff that Amazon is doing. >> Well hold on, let's just set the table on this conversation. Intel announced a series of proprietary processors, their own silicon, you know the-- >> Amazon you mean. >> I mean Amazon, yeah, proprietary processors that are specific to certain workloads, inference engines, and other things around network-- >> Based on the Annapurna acquisition of 2015, a small Israeli-based company that they acquired. >> Yeah, so the press, I've been sharing on, oh, chips must be confronting Intel, your thoughts. >> Yeah, so here's the deal. Look it, Intel is massive and they do a huge amount of business with the Cloud players. Now, here's the thing about Intel, it's really, I've observed Intel for decades. Intel wants a level playing field amongst its customer base and so it wants a lot of different Cloud suppliers even though there's three, four, five, you know, worldwide, there's, there's many dozens, and hundreds of Cloud players out there. Intel wants to support them all. They're an arms dealer, right? They love all their customers and so, so what they do is they sprinkle around the innovation in the industry, they try to open up their architecture such that people can, you know, write software to their architecture and they try to support all their customers. We see it at all the shows. You see it at Lenovo, you see it at Dell, you see it here at AWS, you see at Google, Intel is everywhere and they are by far the biggest supplier. Now, Amazon, of course, has to have alternatives, right? They care about data-center power, you know, they do buy some stuff AMD, why not, why wouldn't you second-source some of this stuff? They do a lot of work with Invidia, ARM has its place, and so, but it's a rounding error in the grand scheme in the market. Now why people get excited is they say, okay, ARM now has a foot in the door, oh, Intel's in trouble. Intel obviously still a dominant player. I think it's, you know-- >> Is Intel in trouble? >> The press likes to glom onto that. Intel's like the dominant player in the microprocessor business and it has to move, and it has to move fast. I would not say Intel is in trouble, I'd say it continues to be the dominant player in the data center. It's got opportunities for alternative processors like Invidia. Intel strategy is to put as much function on the DI as possible and to grab that function, it's always the way it's behaved. You see people like Invidia trying to create opportunities, and doing a very good job of it, and so, there's white space there. It's competition, we love competition, right? >> Here's my, here's my. >> Intel needs some competition frankly. >> Here's my take. One, Intel pays, Amazon pays Intel a lot of money. >> Huge amount of money. >> So it's not like Intel's hurting, Intel's not in trouble. Here's why Intel's not in trouble. One, the Cloud service provider business that Raejeanne runs, she was on theCube yesterday, is growing significantly. A new total adjustable market, they call TAM expansion, is happening. >> So, you know, if you're looking at microprocessors it's not a one, or few, suppliers, it's a total TAM expansion and of course with that expansion of the market Intel's going to take a big chunk of the shares, so they are not in trouble, Amazon pays them a lot of money, they're a big-time supplier to AWS, check. Two, Intel is on a cadence on processor design that spans years. And Raejeanne and other Intel executives have spoken to us off the record, and here on theCUBE that hey, you know, sometimes there's use cases where they're not responding fast enough that are outside they're operating cycles, but as Raejeanne said, Amazon makes them get better, okay? So, they have to manage that, but there's no way Intel's in trouble. I think the press are using this as, to create link bait, for news that is sensational. But, yeah, I mean, on the surface you go, oh, chip, Intel, oh that's Intel's business, it must be bad for Intel. So, yeah, Amazon made their own processor. They got some specific things they want to build specialized processors for like GP Alternative, or inference engines that are tied to the stack, why wouldn't they? Why wouldn't they? >> What Intel will do, what Intel will do is they'll learn from that and they'll respond with functionality for maybe others, or maybe they'll earn Amazon's business, we'll see, but yield to your point, you know, Intel's exposure to the desktop and the laptop, a lot of people wrote about that, that Intel is, the (mumbles) entry is Intel's business, they're so huge, the cost of doing what they do, Intel's such a strategic supplier to so many companies and as we talked to Raejeanne about yesterday the Cloud has completely changed that dynamic and actually brought more suppliers. The data center consolidation that you've seen has been offset by the Cloud explosions, that's a good trend for Intel. And of course the mobile dynamic, you know more about that then I do, but, everybody said mobile's going to kill Intel, it obviously didn't happen. >> Look it, Intel, Intel's smart, they've been around, they're going to not miss the ball. They got a big team that services a lot of these big players. >> Are they still paranoid in your opinion? >> I think they are. >> I do too. >> I do too, I mean I, look it, Intel is, have a cadence of Moore's law. They have a execution style that's somewhat similar to AWS, they've very strict about how they execute and they have a great execution engine. So I would bet the farm that Intel's talking to Amazon and saying, what do you need for us to be better? And if Amazon does what they do best, which is tell them what they need, Intel will deliver. So I'm kind of not worried about Intel on that front. I think in the short term maybe this processor doesn't fit for that, but, that's why GPUs became popular, floating point was a unique thing that CPUs didn't do well on so a GPU comes out, there it is. And we're going to see processors like data-processing units, Pradeep Sindu, former founder of Juniper's, got a venture called, Fungible, that's building a data-processing unit. It's a dedicated chip to serve analytic workloads. These are specialized silicon chips that are going to come on faster, and, to the marketplace. So , just because there's more chips doesn't mean Intel dies 'cause if the TAM expands it's a, it's an overall bigger market so their share might not be as dominant on a smaller market, but it's-- >> You know, I got a, I got to come back to your John Chambers interview. I've watched it a couple times now and I would recommend people would go to, thecube.net, and see John Furrier's interview with John Chambers. The great companies of this industry have survived, you know, I talked about paranoia, Andy Grove, they've survived because they were not dogmatic about the past. So for the past several decades this industry has marched to the cadence of Moore's law and that was obviously very favorable to Intel. Well, that's changing, and it's changed, the innovation engine now, you've called it the innovation sandwich, which is data, machine intelligence applied to that data, in the scale of Cloud. So Intel has to pivot to that to take advantage of that and that's exactly what they're doing. So the great companies of the future, the Microsoft's, the Intel's, the AWS's, they survive because they can evolve. It's the Wang's that didn't, they denied, it was the PC-- >> They were entitled. >> The digital, right. They thought they were entitled and the point that John Chambers made is there's no entitlement and he kept referring to Boston 128, it used to be the Silicon Valley. And the leading executives today, of companies like, like Cisco, like Intel, like Microsoft, can see a vision to the future and they change when they have to change. >> So companies that are entitled, who are they (chuckling)? >> Wow, that' a really-- >> Is Oracle entitled? >> A good question. >> HPE, Dell? >> I think Oracle absolutely acts as though they're entitled and they're bunkering down into their red stack. Now, you know I've often said, don't bet against Larry Ellison, and I wouldn't make that bet against Larry Ellison, but his TAM is confined to Oracle customers. He's not currently going after, non-Oracle customers in my opinion at least not with a strategy that's obvious to me. And I think that's part of the reason why Thomas Kurian left the company is I think they had a battle about that, at least that's what my sources tell me. I haven't talked to him directly, I actually don't know him, but I know people who know him and have worked with him. HPE, I think HPE is more confused as to what the next step is. When they split the company apart they kind of gave up on software, they gave up on an integrated-supply chain. Mike Odell took the other approach, and thanks to VMware he's got a wining strategy. So, I think today's leading executives realize that they have to change. Look at Ginni Rometty, remember IBM was in trouble in my opinion because Watson failed, and their Cloud strategy essentially failed. So they just made a 34 billion dollar acquisition, a Red Hat, which is a bold move. And that, again, demonstrated a company who said, okay, hey it's not working, we have to pivot and we have to invest and go forward. >> Alright Dave, great kickoff day three. Andy Jassy coming up at the end of the day and he's going to do his annual, kind of, end of the last day roundup on theCUBE, kind of lean back, talk about what's going on and how he feels from the quotes, what people missed, what people got, and do a full review of re:Invent 2018. Day three kicks off here, CUBE, two sets on the floor gettin' all the content. We already have over a hundred videos. We'll have 500 total video assets, go to siliconangle.com and check out the blog there. A lot of stories flowing, a lot of flow, a lot of demand for the content. Stay with us for more after this short break.

>> Live from Las Vegas, it's theCUBE, covering AWS re:Invent 2018. Brought to you by Amazon Web Services, Intel, and their ecosystem partners. (upbeat music) >> Welcome back, here on theCUBE, (mumbles) to continue our coverage at AWS re:Invent with Sands. This is actually one of seven sites all around town, that are hosting various sessions. We heard a lot our guests saying, "it's so exciting." There's this spot for this particular expertise. Then I boo, Uber across town, I go to this spot, because that's how big this show's become, and how dynamic this show has become. We are on day three, and I'm here with Rebecca Knight, and also joined by Eric Boerger, who is a technology specialist at McAfee. Hello Eric good to see you. >> Hello, thanks for having me today, this is wonderful. >> You bet, well we've had a couple of your colleagues on already. I mean Markus Strauss is one who comes to mind. Talk about the database you're on the cloud side of things, cloud security. >> I am. I'm a technology specialist here at McAfee. My role is to help our customers as they're moving into the cloud, understanding where their security pitfalls may be, and implementing the right technologies and security tools to help make sure that their transition into the cloud is as secure as possible. >> So what's the big picture on that? Alright so security first and foremost in the cloud, that's probably, well certainly one of the big questions people have right. >> Absolutely, that tends to be the biggest question is, "how can I make sure that as I'm doing this transition to the cloud, that I'm not just throwing assets out there, and finding that I have issues later, but how can I bake security into them from the beginning." And that's really where we at McAfee are trying to sit back and identify where customers are having their challenges, and make sure that our tools are able to be positioned and developed correctly to address those issues. >> So what are some of the most common challenges that you see? >> So some of the most common challenges that we see in terms of problems are misconfigured accounts. That's a very common issue that we see in a lot of breach reports. Somebody setup a data repository, doesn't put the right security mechanisms in place, and all of a sudden now all of the confidential data that's been breached. >> Out the door. >> A second problem we see is a lot of, especially within the IAS space, organizations are standing up new instances of workloads, and the security teams aren't necessarily being informed that they're actually putting these workloads, or computer assets online, so now they're coming online without any protections, or any audit capability in place to make sure they're meeting their own security best practices guidelines that their organizations may have developed. >> Yeah we were talking earlier with probably one of your competitors actually, and they were talking about breaches. We're talking about. They said, "Their estimation 90 percent, are created, or made possible by mistakes." >> Absolutely. >> I mean, you agree with that? Is that our... >> I cannot agree anymore with that. Because the problem is, is that, the ability and the agility of the cloud, is both a positive, it allows us to be extremely flexible and agile as we're developing, but it also allows us to move so fast that we may be outpacing what our own knowledge levels are for being able to secure those. And that's tended to be one of the biggest hindrances that we see, is a developer gets enabled to go through and create a MS3 Bucket, put a lot of data in there, but at the same point they don't implement any tools behind it, or any security behind that. So it's not necessarily their fault, it's just they don't understand what security requirements are to implement in the cloud. >> And that's where you come in. So talk a little bit about your solutions and about how you approach the problem. >> Absolutely. So we have a wide variety of solutions here at McAfee, to help address those issues. That's everything from our Skyhigh McAfee Casb product, to help do account identifications and discovery of rogue accounts. And then some of our tools, like our virtual network IPS. That's able to do packet level inspection to apply a deeper level of security onto those systems. And then of course our Cloud Workload Security Product. That's something that is able to help you discover any of those rogue assets, and identify systems that may have already been breached based upon the network communication that's already occurring on those systems. >> Yeah you're kind of this cat and mouse game, aren't you, in terms of security, because you're trying to stay one step ahead of some actors who are very skilled at maintaining an edge. >> Absolutely. >> I mean how do you sleep at night Eric? >> So moving to the cloud is an area that once you feel that... Once you have the right tools in place, it'll help you actually sleep a lot easier, knowing that there's audit tools in the background, that are able to continuously monitor your workloads, identify if you have misconfigured accounts, if you have systems that are missing, needed information. You may have a requirement to have something like an integrity monitoring tool in place for some of your workloads, and this is a, with our tools, we can actually monitor and tell you if you're out of compliance with any of those baseline requirements. >> So how do you help the companies, the customers that want to move to the cloud, but also be sort of a hybrid, or maybe keep some of their stuff on PRIM, how do you make it easier for them? >> And that's a very common question that we hear over and over is, "I want to move to the cloud, but I'm not ready to go all in yet." So what we've actually done, is we've developed a lot of same discovery tools, can be used on premise. So that as they're building out their private clouds, whether it's in an open sac implementation, or via VMware, we can still do the same discovery, the same identification of misconfigured workloads. Now that also brings us to, as they move more into the cloud, it's already there, it's able to help them with their hybrid environment space, and that can either be managed on premise or from the cloud directly. So that when they're ready to move all their management infrastructure to the cloud, our tools are already there and ready for them. >> Now you're really good at what you do, but as you know, you're not the only game in town. >> We're not. >> So what's your differentiation then in terms of your cloud offering? What do you think this is what McAfee does better than anybody else? >> So what we feel that we really do better than anybody else, is be able to integrate a full security picture in a unified console management. So this is giving us the ability to do deployment of our own tool sets. Being able to do things such as integration with our Skyhigh product, and being able to pull back from the Casb view to help pull in a unified view. That's where we really feel that we've got a lot of unique factors in the cloud space to help our customers as they're moving. Plus the ability to be not just cloud focused, but still hybrid. Being able to protect those private data centers. We see a lot of companies who are going pure cloud, but they say, "Well if you had something on a premise, we don't care about it anymore, because it's not in the cloud." We feel with our background and our strengths in security we can really help address those concerns. >> So you're a technology specialist, that is your job title, >> It is. >> but in so many of these migrations and big digital transformations, the technology is really the easy part. And what's so much harder is getting the people onboard with the changes. Getting them to adopt and embrace and keep using the solutions. First of all, do you see this kind of resistance, and then also how do you overcome those challenges? >> Absolutely, the challenge is getting people to adopt to the cloud, and then continually be integrative with the newest tools that are coming available from the security standpoint and side is always a problem. The developers are very agile, they want to move at the speed of development. Which means going back and talking to security and saying, "hey by the way, I'm doing these things," doesn't always happen. So this is where we want to be able to give you a continuous monitoring ability to say hey, "somebody went through and stood something up." Security was completely outside of the loop. Bring them back in so that they can get the visibility, the alerting. And this is even where we've created some new features, that we announced on stage yesterday to be able to be integrated with the Amazon security hub. This is where we really feel that being able to help augment as Amazon's developing tools providing our security insight, to make sure that once again, as the developers are taking advantage of some of the newest features, we're there with them. >> And what was the driver of that? I mean how did you get to that point? >> So this is part of our partnership with Amazon. We actually have a great foundational relationship where we have a lot of our products have gone through a best practices review. And we have well architecture review stamps on a lot of the products that we have in the marketplace. This is due to the tight security integrations that we've had work with Amazon. That we're invited to be one of the first partners into the security hub, and you're going to see this out of additional products as we move forward with our new capabilities in the cloud. >> Yeah I hate to, I mean we have just a few minutes left, and I hate to dive into a big topic here, but on the other side of that security coin is compliance. Right, you got to be concerned about that. It's governments, you got to be concerned about that. And that's a whole new can of worms especially today with whether you're dealing with company concerns, state, federal concerns, and even European concerns. >> Absolutely, and the data privacy is another major concern with the compliance. It's not just what do I have, but how is it being used, how's it being utilized, and that's where with some of our products we've actually gone through and have build our full DLP engine into discovery of any of your data that exists within the cloud. So if you put data in as three, we can go through, scan it, identify if there's any PII data, alert upon it, give you controls of that. And then from a workload perspective side, we have tools that can go through and feed in your own templates. To say that I need to be PCI compliant, I need to meet HIPAA compliance. Be able to audit that workload, and give a continuance summary report back to the management teams to say hey, "I have auditors coming in, how am I in compliance, and then tell me what I need to do to address those gaps that I found from my cloud workloads." >> Solving problems. >> Solving problems. >> That's what it's all about right there. >> He's the best, that's right. >> Alright, I want you around more often. (laughing) We got a lot of problems to be solved, we appreciate it Eric, thank you for your time here at AWS re:Invent. >> Thank you very much for the time today. >> Good to have you, thanks for the McAfee story. Back with more from Las Vegas right after this. You're watching theCUBE. (upbeat music)

>> Live from Las Vegas. It's theCUBE covering AWS re:Invent 2018 brought to you by Amazon web services, Intel and their ecosystem partners. >> Good to have you here on theCUBE, as we continue our coverage at AWS re:Invent. We're at day three here in Las Vegas in the Sands Expo Hall D, and we got about a half hour. Come by and say hi to us if you would. I'm here with Rebecca Knight, John Walls, and two gentleman here to join us. One from GitLab, Brendan Jung, who is the vice president of alliances. Brendan, good to see you sir. >> Thank you for having us. >> And Alex Hale, platform engineering at Beacon Platform. >> Hello, Alex, how are you doing? >> Not bad, I'm surviving the whole experience. >> It's a test! >> Well, let's talk about the whole experience (mumbles) What have you picked up this week? >> I've picked up that AWS is going very much into this sort of enterprise space. We saw that theme last year, and I think this year it's even more so that they're really catering towards how enterprise and then big organizations are getting in. And I think that's been a big. You can see it in how they're doing their storage strategies, how they're doing their network strategies, and how they're just really targeting towards security, and compliance, and governance. And I think that's a big theme that's from last year to this year, and I think it's going to continue on. >> Yeah, they've been waving a big flag for sure telling the enterprise it's safe to come onboard the public cloud's open for ya. >> Yes. >> Oh yeah for sure. >> Brendan, if you would, you were telling a story that you worked at Google for quite some time. >> I was, yes. >> Worked on some fairly high profile projects >> there, and you've been >> Yes. at GitLab for five months now. Instant transition for ya? >> Five months, yes. >> What was behind that? >> So a couple of it is, I mean when we get down to it sometimes you're either a builder or a runner just in the way you're oriented. And I'm a builder, so the biggest thing was love building that from the ground up with Google. Amazing team they did amazing job. We got to do a lot of really fun things. Was looking for something kind of new, and I'd worked with GitLab since I ran the partner organization for a lot of the partners at Google. I had worked with them for a number of years and it's rare when you work regularly with the company that you get surprised. So the kind of the point that I was like, "Oh, I really need to look into this more deeply," is I've done detailed work with GitLab for years. And I was in a meeting with Sid, our CEO. And he kind of, "Hey, you know what we're up to." And I'm like, "Oh, of course I know what we're up to." Right, cuz that's you always answer that. I mean you don't answer the question, "No, I have no idea what you're up to." We met four weeks ago, of course I know what you're up to. And he's really humble. But simply like oh hey, you want to see me insert. Hey, this is what we're working on. Slides across the floors to report, and he's like, oh, in the CI space, under three years we went from no product to the very best of the business. Beat out Microsoft, and CloudBees, and all these. And I was like wait, I didn't know you were in the CI space. I shouldn't say this publicly, >> Alright it's alright. >> but I went like I didn't know that. >> It's okay. You got the job. >> No, I'm safe, but the ability that's just the speed that the company moves. Everyone says it, but when you can go that fast with that kind of quality, I was like I got to dig deeper. And so we just kind of went down that path, and it's been quite an adventure. >> Good. >> Obviously, Microsoft buying GitHub has made for a whole lot of discussions in a whole lot of different ways for us. And competition's good, so it's been a lot of fun. >> Well, we definitely want to talk about the GitLab and Beacon Platform partnership, but I want to first ask you, Alex. Tell our viewers a little bit more about the Beacon Platform. >> So Beacon Platform is a company that came out of the financial services from the large banks; the Goldman Sachs, the J.P. Morgans, the Bank of Americas. And in those places, internally they have to have this quite open source like culture where there is people contributing in the same codebase, there's a lifecycle of how things are done, and it's rapid moving. And people don't associate them with large banks, but there is these products out there. In fact, some of the Goldman Sachs partners refer to those as the golden source, so they secret source. And if large banks can do it, why can't someone else. So we've taken those experiences that people have done for years to build these communities, best practices, and prescriptions, and turn it into a product. So we've taken the same model of here is a set of financial tooling, and infrastructure, and toolboxes to make financial applications. And we've brought it to the smaller bunch; so your insurance companies, even your large banks, Komodo used firms, insurance people. They can take our platform, and then bring their own analytics, and then build financial applications that they want on top of it and whilst doing so be ensured that they're compliant with security. We've done the governance for you. We've done the security for you. All you have to do is put your good ideas to use and make applications. >> So give us some examples of the business problems that this platform solves. >> So typically in the financial space, the people that have the great ideas are pawns, and they're by nature mathematicians. They're not developers. They're not UX people. They're not UI designers. They're certainly not security people. And yet they are are the people that are driving the core business and the value. And so the question is how do we make them be productive? How do we make sure that their lives are easier? Which means that you give them an idea. You give them a lifecycle for software that they can start saying, "Ooh, I've got an idea. I'll hack it up." And when it's hacked, they can publish it. It comes out the other end, and all the reporting is underneath there. Their security is there. The compliance is there. All the authentication is there. And that idea is now being actualized in the matter of days, weeks rather than months and years. And that means that our customers can take these ideas that they've been working on or just conceiving and turn it into reality in a very short amount of time. And then be comfortable that whole platform itself remains secure, compliant, and all the same thing that Amazon is actually counting to us. >> You know it seems like if your focus, your core competence, was or is financial services. I mean you're starting at a very high level of demand client, right? >> Yes. >> And appropriately so, and so there are a lot of lessons that migrate to other businesses that I assume are quite attractive to them, >> Yes. >> because if you mention your client, BOA, if they've got comfort, I have comfort. Right, because how much of that do you see that the experiences that you've developed or that you have put them through translate in a very positive way to other sectors? >> We've found out some of our customers are starting off in the cloud, and they're making their cloud journey. They're financial companies that want to take the journey to the cloud, but don't really know how to. And so we as a company which has already running on the cloud, as a company we don't actually own a physical single server. We're all on the cloud, all in. And they, our customers, come to us to say, "How are you in the cloud? What do you do? "You have the experience. You've worked at these places. "How does that all work?" And so we give them a sort of in the same way that out platform does. Prescriptive advice on how things are going to be done. And our customers come along with us on the journey. And so we take the customers on their cloud journey whereas our customers are taking us on their needs, and bringing their needs, and what they need to us to say, "I want to build an application like this. "What more do I need to do? What do I have to do?" And so it's a very collaborative relationship doing our customers to say, "I can help you in the cloud space. "You can help us in the financial ideas space, "and together we can actually make applications." Whatever we build ourselves, becomes we can resell it to others whilst the customers intellectual property can stay with them. It's a really interesting collaboration of. >> Symbiotic in many respects, right? >> Yes. >> You're leaning on them. And what about the relationship between the two of you again in terms of. >> Sure yeah, so as much as Beacon is very financial services focused, we're a DevOps tool and end DevOps tool for anyone, right. So in many ways what Beacon is doing is taking what GitLab's done about builing that whole tool chain, 'cause there's really a tool chain crisis out there. If you start looking at what needs to be set up for a developer, they want to live in their IDE, do their development, and publish as he said. But you start looking at what that needs to be set up after that, you're talking often times on a company 12, 15 other steps to go through. And that was kind of our aha was there's an opportunity to treat that as one full application as a DevOps tool set across the entire board. Started down that journey really like three years ago, and that's kind of I think we kind of match up. The similar story; they wrap all the important financial data, all the other things that matter to a bank, right. And they're got to whole bunch of extra tooling, extra data, extra services. But at the core of it, they also leveraged GitLab both as a tool to develop their own product and also to offer it as a tool possibly to their own customers, right. So their other customers need to develop. They need a DevOps toolset, so we work back and forth a whole lot on this. They move so fast. It's been amazing, and so every time we sit down we're like wait, what if we did, okay cool let's iterate. And we can turn that around. We ship every month to our customers. You can run it anywhere you want. The majority of our customers, they love the fact that they can run anywhere. Which in fact while Beacon does runs on Amazon, their customer bases have to run on (mumbles), right? And while we're seeing that hybrid become more and more common which is great, that's the truth that's been there forever. That's the world that we've lived, they live everyday and have lived for a long time, and so it's kind of fun to come here and see that be like yes, oh yeah that does exist, and we're kind of like yeah that's existed for a long time. >> Everybody caught up. >> Right yeah, we're there and there's always going to be reasons for that on both directions. And so we work really well together on that side, and they push us hard. Right, so we're actually right on stage. We're sitting there in just this morning, he's like hey, you finally (mumbles). You know I've got all these merge requests that he wants in our product. (mumbles) opens, it's open. Everyone in the world, anyone that watches this, go put a merge request on GitLab. We're going to track it. You're going to know where it lands. You're going to know when it gets delivered. So and if you want to write the code, you can write it and it's in. So it's been actually a ton of fun. >> And have at it, right? >> Yes. >> Well if the relationship's working good to see. >> Yes. >> And you're five months in, and I'm sure the one year anniversary's right around the corner for you. I'll try to be able to wait. >> Be here before you'll know it right? >> Hell yeah. >> (mumbles) thanks for joining us. Good to have you here on theCUBE, and look forward to hearing about this continuous success down the road I'm sure. >> Thank you >> Thank you so much. >> (mumbles) having us. >> Thank you both. Back with more here on theCUBE. You're watching this live at AWS re:Invent Las Vegas. (techno music)

live from Las Vegas it's the cube covering AWS reinvent 2018 brought to you by Amazon Web Services Intel and their ecosystem partners welcome back to Las Vegas everybody I'm Dave Villeneuve my co-host David Flair you want to the cube the leader in live tech coverage this is our third day of coverage at AWS reinvent 2018 our sixth year covering this event that keeps getting bigger and bigger Dave at 53,000 people amazing place is still jam we still barely have our voices 18 Cockroft is here he's a vice president of cloud architecture and strategy very well known in the industry q Balam thanks so much for coming back on thank you yeah it's the I've been to all of the reinvents we've been far as the customer and then we've been off of one but we watched remotely and hung on every word you know back when there wasn't a lot of information about a DMS now it's like too much information to process it's gonna take us months to sort through it all but at any rate it's it's a phenomenal opportunity for us to to learn to share to inspire folks and you do with some great work talk a little bit about you know some of the fun stuff you're working on and in your current role yeah I have a few different things I do one is one part of my role as I go around the world giving keynotes AWS summits but mostly I call it doing one of Ogle's impressions his deck and I get to presented around the world so we have to digest all of this stuff into a 90-minute deck that we can take to around the world that's a you know what do you leave out there's some it's it's harder and harder every year so that's a lot of fun but the team that I run for AWS I mean recruiting and running is around open-source right and we do we sponsor various events we members of various foundations we make contributions to projects and have been helping that by hiring people from the open-source communities into AWS to help help some of the edge over service teams with their launches of open-source related projects so what I've got what's been happening this year is had like a hundred blog posts related to open source lots of tweets lots of activity lots of events like ask on all things open in coupe car so be there in a couple of weeks exciting to you guys probably again but this week there are a few of the launches where we got quite deeply involved we did a blog posts on the open source blog most at the same time as Jeff fires okay here's the service and here's the open source part of it this is how you contribute and this is what's going on so we've had some fun with that so but it was it two years ago when we first met you've just been on the job for about a month about that particular time and you laid out what you wanted to do in terms of from your previous experience about how you wanted to turn AWS into a an open-source contributor how would you rate yourself in two years I think we've made some good progress really made me a AWS was making contributions to open source but had nobody talking about it and nobody know it was nobody's job to go out and explain what we were doing so that what part of the problem two years ago it was actually more happening so most people knew about but we were just not telling the story and it said it wasn't coming across well and the culture and the culture I mean it was spotty like some parts of AWS were doing a lot of open source other parts we're kind of not really seeing it as a priority so by talking a lot more about it we kind of get a more uniform acceptance across AWC huge organized just there but Amazon as a whole we are actually telling that story the story a much broader story than just AWS and be able to bring that and get everyone go oh this i see everyone doing it so i should be doing that so it helps create the the the leadership for more teams to follow and what we've seen in with you know really the first year building the team the last year kind of getting the content flowing and getting the processes kind of working to get all the all of the different events and blog posts and out the outbound part grips getting increasing number of contributions and launches so now Corrado was a few weeks ago so it you need us launch but that was that was an example that was it's a lot a lot happened from my team from Aaron Gupta my team his a Java champion he used to be at Sun he was a worked at Red Hat on J bar so he's like he knows everybody in Java has great credibility across the Java community and he said we should launch this product in Belgium at like midnight or so you know West Coast time and let's fly in James Gosling and like to a secret like get him on stage without anyone knowing he's gonna do it and do the introduction so it's like this totally crazy idea and it came off beautifully and we even had the the you know the Oracle Java people saying nice things about it the contributions to open JDK just just a really nice example of figuring it out all that get everybody on board get everything done right and then say here's something that matters to the community that we can contribute it'll show up on the rooftop complete thanks the star power thing but mincing James to do it was a right around a lot of credit for that that particular launch but you know this is the kind of people I have on my team and we're like we're pulling them in and pointing them at okay can you help this team figure out how to take this open-source project to market now I mean that was a major contribution to the open-source community and it was just in time wasn't it but another slight view would might be that you and Oracle should have been working this out until not leaving it until the last minute but I mean we were doing this work anyway right okay we're effectively self-supporting our own version of Java or internally we were getting better performance and better sooner bug fixes on open JDK so it made a decision to just move to the open JDK dream and we were just unhooking our internal use of the of the other the other options we have home mix you know a very large organization along for you acquire lots of different versions and flavors of Java you notice this one language so we like clean it up let's get JDK 8 and 10 we're self supporting it and then we announce to our cave will support our Amazon Linux version right and the final step was like the customers were saying please just like supportive on my laptop and anywhere else I need it and the thing we didn't announce then we didn't make a big thing out and arm support we didn't we kind of it was in there by default we didn't talk about it because the ARM chips came out this week so hey and part of it was also have exactly the same version of Java now on all of the Amazon Linux is even the the Intel AMD and arm so that helps the compatibility for people kind of going well it's a different processor architectures ties together so it was all part of the thinking if you didn't want to tip your hand on the announcement this young is right ok so I think sometimes a AWS is misunderstood partly from its own doing I mean you just mentioned you contribute a lot to open-source but you never talked about it generally when AWS doesn't have something to say they don't say a lot about it so others are left to you know make the narrative you come on you've now got an open-source agenda can you just sort of summarize what that motivation is and what the objectives are well we have you know lots of different pieces of this but you have service teams saying I'm gonna launch this product and there's an open source component to it can you help and sometimes that means I hire someone in my team to specialize in that area sometimes it's just our consulting with the team we may know connecting them to the open-source community so that's one piece of it is having that if you think about CN CF in particular cloud native computing foundation that's got lots of projects if you think about the AWS service teams no one team really owns the scope of CN CF but my team has that ownership for CN CF as a whole we have the board seat position and we say ok we have the serval as people over here we've got some entertaining things over here there's some Linux kernel virtualization bits here we can reach out to lots of different teams across AWS but act as a central point where you have something about open-source you want to talk about with with AWS or Amazon even as a whole you can come to us and we'll find the right people and we'll help you make those connections so part of it is acting as an on-ramp for the sort of buffer between the internal the external concerns of the communities there's somewhere to go and partly just getting contributions out there and what we could gain criticized for not making enough contributions well we've been making more and we're making more and we'll just keep making more contributions until people give credit for it and that's that's the if you're like what's the strategy contribute more and then tell people point at it and hope the people like what we did and take the input no it's the customer driven thing right we're gonna do what our customers ask us to do and their customer community focus on the things we want to do and we've been contributing to spinnaker the the Netflix OSS project we made some serious contributions to that in the this year firecracker myths which talk about that a bit and the Robo maker that those are all areas where we've been working with firecracker is particularly interesting isn't it I mean that's a major contribution of improving the performance and capability of those micro VMs yeah can you talk about that a little bit yeah it's the baby it's interesting because it's a piece of software pretty much no one will ever see your use it's the thing you run on the bare metal but lets you run your container Dee that lets you run your container on top right well it's deep down in the guts of the system there's this piece of code but we we kind of there's a few reasons we're using it particularly in production now with its supporting some of our production use of Fargate and lambda there in the middle it's not a hundred centraal out but there's a good chunk of the capacity running on it and that's where it turns out to be useful and just to cook how long we have to get into this but if you think about a customer running a lambda function we would put create a VM with that lambda function in it if they wanted a second lambda function we put it alongside that one no the customer comes and we start a new VM for them and we start a lambda function in that VMs take a while to start up so you have cancer pre-made some sitting there waiting but these are big VMs and we're putting lots of little functions in them what what firecracker lets you do is start a separate micro VM for every function and safely put all of the customers on one machine so you start packing them in it's a much more efficient way to run your capacity our utilization of those machines supporting lambda is vastly higher than having a machine with a bunch of empty space in it that we're trying to weight running for running for the customer so it's that efficiency is the thing and then the speed of starting a VM it's a very it's a very cut-down VM so it's 125 milliseconds with just to start the VM which is incredibly fast when you think hey give me a VM on ec2 it's you know they're in kinda like 30 seconds to a few minutes like I get 12 terabyte VM takes a little while to boot up but you don't have to pay for it till it finished including my good things about these huge machines right how about Robo maker can you talk a little bit about that and it's important so a rubber makers interesting on the open source blog which we posted on Slate on Sunday night early on Monday morning I did an interview with Brian Goerke who's the founder of the open robotics foundation and what we've done there is it's kind of an extension of sage maker if you think about that being AI if you've got these eight where I can deploy an AI model what is the AI model I want to do it wants to read something from the real world and modified the real word so it's a read from a camera or at some of the sensor and then control motors and servos and that's what Robo maker does it wraps the intelligence you can build with sage maker with the robotic operating system that has actually a library of actuators and a library of algorithms control algorithms you've got little brain in the middle and you've got a new robot that does something and we had the the Robo racer low racing car to which where all of these things come together to make an old toy race car that we can drive around tracks which is a whole other topic we get into but what interviewed Brian on what is the history of Rose the robotic operating system where did it come from you know what is the hard thing about running in it turns out the hard thing with Rose wasn't building the robots it was simulating the robots and the simulators quite a CPU intensive job it's graphics intensive you got this virtual world you're running and VR worlds are quite intensive and getting that installed and running was the hard part so what what what robot maker is is that as the service it's this simulator is called gazebo just a funny name so gazebo as a service is the actual service that effectively were charging for with a free tier so you can play with it and then we charge you for the sort of simulation units like how much computing time you're using when the rest of it is all you know cloud9 for the front end and deployment of fleets of data to fleets the robots and updating them and managing them but they're interesting thing is this is getting into like the people that the field of the first robotic thing is high schools high school robotic competitions they're interested yeah universities are interested in a university solar so we kind of it's not just for commercial production robots it's the whole training thing we're getting into STEM education if kids like playing with robots it's like Center and we're pulling all this in so now you can go home and take these like the latest most advanced AI algorithms that used to have to be doing a PhD at Stanford to be playing with and play with your kid you know over Christmas and see what you can come up with really simplifying the whole software development side of that when you look at the Dean came in competitions we're just awesome yeah all the kids they could have gravitate to the hardware cuz they can touch the software was really hard and and and this is gonna I think take a new level is particularly enough and it's all open source yeah you can go yes oh you've got this robot there no no I pointed them somebody who's complaining that we'd done it and no it was some proprietary robot thingy with the toy cars and I pointed them at the github URL it's that you can go build this thing it's all open source you can put anything else you want on it but the robot cars robot has rolls on it the robotic operating system H maker Robo maker all combined together and they're off running races and having all having fun now you guys are both Formula one fans yeah and you guys have been having some you know profile of Formula One folks here you got the little the mini vehicle riff on that really open source but I have another like thing I'm doing on the site it turns out the over the last year or so we started looking for opportunities to do sports sponsorship with a particular focus on Europe and the rest of the world we had a few US sports where they I don't know something with balls I like I like sports with wheels so about the middle of last year like this June we announced the deal with Formula One which is a multi-part deal part of the deal was just take them to the cloud that they have some data centers stuff they were running at a space and their data center is like no they wanted to do a technology refresh so for all the reasons that everyone else is moving to cloud we moved the sports core infrastructure to cloud over some number of years right so that's a process for starting and part of that is the archive of all Formula One races it's a treasure trove like 67 years of archive of everything they've got all the videos were digitizing it we're gonna figure out what to do what you know we've got to process it to label everything anyway so that's one thing and then we went turned up it we all turned up at Silverstone in the UK at that race it was the week after the announcement and that race we have a do as logos turning up on the screen because another piece was sponsorship so we start sponsoring the core video feed that Formula One uses to the world and that's 500 million fans watch Formula One so now 500 million fans for the next few years they're going to see a dope race logos on screen around the analytical insights of what is going on in the sport the odd rear tires are overheating you went round a corner this fast here's the pit stop strategy so we brand advertising associate with a high-technology sport and analytical insights and that's why we did that deal and they get all of our technology AI a lot of help helping them migrate and then the third thing we did that I got involved with was I'd already done a few CIO summits at Formula One races along the way so I was kind of like trying to poke my way into this thing that was happening I'm not involved in sponsorship set up right so hang on if you've done that thing yet and then them so we decided to do some executive events around Formula one so we'll pick a few races we'll have some you know corporate hospitality like things but when you put a bunch of senior executives together for a few days they share they solve each other's problems and you just get out of the way and they know the people that have solved one problem will share it with the other so it's a really it's like a tiny reinvent right here everyone is sharing if you sit next to someone what problem have you sold you can find stuff out so this is a concentrated version of that and we retired it in Monza earlier this year went great amazing I mean it's fun and it you know next to the business so it finally was like can we get someone on the car on Reba okay who's in Abu Dhabi on Saturday can we get them on Sunday night for the launch for the robot slut no this is like top guy in Formula One got here from Abu Dhabi if by Wednesday morning I'm just happy that they got here yeah that was that was a huge tire cube team we've watched your career you've been somebody who you know shares his knowledge and done some great work so thank you so much for coming back in the cube like that congratulations on all your great work Andy Jesse's coming up next we're excited about that keeper right to everybody we'll be back with our next guest Andy Jesse CEO of AWS right - this short break [Music]

>> Live from Las Vegas, it's theCUBE. Covering AWS re:Invent 2018. Brought to you by Amazon Web Services, Intel. And their ecosystem partners. >> It's good to have you back here on theCUBE as we continue our day three coverage of AWS re:Invent. This is our 7th year at this show by the way, and it was just a little itty bitty thing some seven years ago. It's going to almost 40 thousand plus this year, and I think most of them are still here enjoying day three. Rebecca Knight with John Walls, and we're now joined by Dan Potter, who is the vice president of product management, and marketing at Attunity. Dan, good to see ya. >> Great to be back at theCUBE. >> You're a CUBE alumn, >> I am a CUBE alumn. >> we should say. >> Yes I am. >> And you were with Rebecca last year, two Bostonians, so again, I'll try to interject when I can, right? (Dan laughs) >> You don't speak our language fella. We can translate. >> It's alright Dan, it's okay. >> We were saying, before we got started here, you go to a lot of shows, right? >> Yes. >> And so, every one has it's own personality, it has it's own rhythm, it's own vibe. I mean, how would you characterize what you're seeing here? Especially, here we are day three, and it's still alive and thriving. >> It is absolutely overwhelming. This is my 3rd. Every year it grows. But I just seem to spend my days going from hotel to hotel, you know, to try to hit the sessions you want to, I feel like I'm always in an Uber, it's just so big, and the keynotes, there are so many new solutions that they're rolling out, it's just, the scale is so impressive. >> So what keeps you coming back? I mean, is it the chance to see so many customers in one place? Is it to hear the dizzying number of announcements from Andy Jassy? >> So I loved Andy's presentation, and the keynote this morning was great. For us, all of our customers are moving to the Cloud. I mean, Amazon really is the pioneer of people, and their transformation to the Cloud, and the success that customers are having with the Amazon platform is just astounding, and to see, over the last few years, how organizations have overcome some of the technical barriers, some of the perceptual, the regulatory barriers, they're all gone now, and this wave of movement to Amazon, and to Google and to Azure, it's real and it's happening and it's only accelerating. So it's exciting for us, you know, we're a vendor of data integration solutions. So we help customers move their data into the Cloud, and it's been great business for us, but it's been really fun connecting with our customers who we've gone through multiyear journeys with them as they're moving to the Cloud. So it's fun to see the success that they're having now with all the new technologies in the Amazon stack, it's great. >> So I want to ask you about the trends in the marketplace, what you're seeing, what you're hearing, as you've said, the security, the regulatory, the concerns are pretty much gone now. >> They are. >> They've had this aha moment. >> The Cloud is where I want to be. >> Yes. >> So what else are you seeing? >> Well, things continue to change, so if you look over the last few years, if you look at what's happening, all of those barriers are removed, but the technology stack it's still very much in motion in a positive way. New products are being introduced. Like today if you look at the announcement of a managed Kafka service. So one of the big trends we see is the move for realtime analytics, and to empower realtime analytics you need realtime data movement infrastructure, and Kafka is becoming an integral part of our customers data integration fabric. So that trend to realtime analytics, and having services like Kafka now on the Amazon platform, really important. >> And you got to Hadoop play, right? I mean you're working with Hadoop, you're working with Kafka as you point out. >> For sure. >> Yeah so. >> Well Hadoop's a great example of some of the changes that have happened over the last few years. Five years ago it was all Hadoop, and then all of a sudden the data lake strategy was Hadoop, and S3, and now it's Hadoop, S3, and it's Snowflake. There's so many different technologies that are really purposed to solve very particular pain points, this is the excitement for customers to be able to have this array of different technologies, and done right, if they have an architecture that supports them in moving that data where and when it's needed in whatever time frame, and structuring that information so it's analytics ready, that's the value, and that's some of the real innovations that you've seen over the last few years as this has all started to mature. >> Yeah, well I mean, take me through the data decision if you will. When am I going to leave on-prem? When am I going to move into the public cloud? As the volume of data grows, right? We're talking about trillions of processes within seconds. That's a big nut to crack for a lot of people. Why do I leave put on my Legacy system? Why do I move over? How reliable is it? What's the latency factor here? How do I make sure everybody gets to it, who needs to get to it, if it's over here, and over here? >> Exactly. >> So take us through that. >> So there are two big use cases that we see. One is analytics workloads. The Cloud is a perfect place for analytics. It allows you to create a very large data lake, bring in all kinds of hetero-genius data, bring it together, perform realtime transformation, and deliver analytics ready data to a wide variety of different business users and use cases. So the Cloud is really well purpose fit for analytics. If you look at all of the innovations that you've seen this week, a lot in AI and machine learning, a lot in realtime analytics. I mean this is the elasticity of the Cloud, and the storage capabilities, and the cost benefits of being able to store lots of information, and to be able to run different processes, analytic processes, when you need those, scale up and scale down, perfect fit for analytics. So that one is an absolute no brainer. We see a lot of people, this is the 1st choice for them as they're moving their analytic processes. The 2nd one we see is customers who have core transactional systems, like mainframe systems, you see this a lot in finance, big banks, insurance companies, these are 20 year old. >> I don't want to leave the mainframe, right? >> Not only are they not leaving the mainframe, but they're continuing to invest in the mainframe, and the mainframe is optimized for those transaction processing systems. But what they're not optimized for is how do I build new customer facing, web based applications, mobile applications, and the Cloud is the perfect environment to do that. So the way that we marry those two things together, and the big trend here is this is where realtime synchronization of data comes in. Every time there's an update on that mainframe system we can move that changed data to the Cloud in realtime. So if you're a bank, and you want to provide a web based interface, let me check my account balance, I need a realtime view, but you don't want to write that application against the mainframe, it's too expensive, the processing of a mainframe is too expensive. So if I can replicate that data into the Cloud, and I've got this whole modern array of tools in the Cloud, and I can take modern approaches, like microservices architectures, so I can have different optimized smaller databases that are purposed for different types of mobile apps, or web apps, that's the other trend that we're seeing. So that's kind of bridging that Legacy gap, and to your question of, what data do I leave on-prem? And what do I move to the Cloud? Those core transaction processing systems, they may never move to the Cloud, or in our lifetime we may not see those. Other databases, other applications are lift and shift moving to the Cloud. So things that are a more modern architecture we're seeing a lot of lift and shift directly to the Cloud. But it's going to be a mix for some time. >> So I understand you have a new launch of Attunity for data lakes on AWS, >> We do, yeah. >> tell our viewers a little more about that. >> So this is exciting. So I'll step back for a moment. We provide realtime data integration, and we move that changed data from on-prem into the Cloud. Moving the data is the 1st step, and it's an absolute requirement. But what really needs to happen in order to get the value from your data lake and cloud, you need to be able to not just move the data but shape that data, and make it purpose fit and analytics ready. So if our use case is analytics, and I want to be able to shape this data into a data mart, or I want to create an operational data store for realtime reporting or I'm a data scientist, I need a historic data store on a subset of information. Those are the analytic ready data sets that need to be created, and we're doing that end-to-end data pipeline. So realtime data movement, shaping that data, making it analytics ready and fully automating that process. So it's a streaming data pipeline process that is really leveraging the best of your core transactional systems, mainframe, SAP, Oracle, Legacy apps, files, and moving that to the Cloud in realtime so you can take advantage of all the wonderful capabilities on the Amazon platform. >> So you've been talking a lot about the changes in the data integration space, and sort of what we're seeing. What are your biggest challenges, and biggest opportunities as you're looking to 2019? >> So the biggest challenge is that there's a lot of moving parts, ya know? If you look at, again, you look at the last five years, and how many things have changed as an enterprise architect, they must scratch their head every morning and say what else Is going to change? I thought we had this figured out. So it's a challenge for us because there's a lot of different targets to support. Different clouds, Multicloud, multiple technologies, but that's also the opportunity. The opportunity here is that for us to play that role, and to help customers move data where and when they need it to whatever technology, we're completely agnostic. So if a new technology comes up, like a Snowflake. Great cloud data warehouse built on top of S3. We've seen a lot of customer interest in that, and that's been recent, the last two years out of nowhere. But very large enterprise customers have said, I want to jump on Snowflake. So for them to very quickly say, alright, now I'm going to point my data in addition to Hadoop on-prem, I'm going to point it into the Amazon Cloud, load it into Snowflake, automatically build out that data warehouse for me, and let's get real value. That's the opportunity and the excitement for us. It's never stale, there's always lots of work to do, and the types of impact that it's having on our customers, again it's really transformative to watch them go from the traditional monolithic, slow, traditional warehousing processes to more dynamic, realtime spinning up data marts for business users very very quickly so business users can have better insights, faster, make better decisions quicker, that has the impact that these organizations have been looking for, and that's why they're investing so much in the Cloud, so they can have that business impact, and we're really starting to see that. >> It's almost good new, bad news, right? The good news is things will always change. >> Yeah. >> The bad news is things will always change. >> Absolutely. >> But that's what makes it fun. Every year you come here and it's just, there's a buzz. (Rebecca laughs) There's always something exciting, and there's been some great announcements over the last few days, including ours, and it's been fun. >> It has been fun. >> Alright, Dan thanks for being with us. >> Happy to be here. >> Great to have you once again on theCUBE. >> Thanks for having me. >> See you soon I hope, down the road. >> I hope. >> Dan Potter joining us here on theCUBE. Back with more from AWS re:Invent after a short break.

>> Live from Las Vegas, it's theCUBE, covering AWS re:Invent 2018, brought to you by Amazon Web Services, Intel, and their ecosystem partners. >> Hi everybody, welcome back to Las Vegas. I'm Dave Vellante with theCUBE, the leader in live tech coverages. This is day three from AWS re:Invent, #reInvent18, amazing. We have four sets here this week, two sets on the main stage. This is day three for us, our sixth year at AWS re:Invent, covering all the innovations. Markus Strauss is here as a Product Manager for database security at McAfee. Markus, welcome. >> Hi Dave, thanks very much for having me. >> You're very welcome. Topic near and dear to my heart, just generally, database security, privacy, compliance, governance, super important topics. But I wonder if we can start with some of the things that you see as an organization, just general challenges in securing database. Why is it important, why is it hard, what are some of the critical factors? >> Most of our customers, one of the biggest challenges they have is the fact that whenever you start migrating databases into the cloud, you inadvertently lose some of the controls that you might have on premise. Things like monitoring the data, things like being able to do real time access monitoring and real time data monitoring, which is very, very important, regardless of where you are, whether you are in the cloud or on premise. So these are probably really the biggest challenges that we see for customers, and also a point that holds them back a little, in terms of being able to move database workloads into the cloud. >> I want to make sure I understand that. So you're saying, if I can rephrase or reinterpret, and tell me if I'm wrong. You're saying, you got great visibility on prem and you're trying to replicate that degree of visibility in the cloud. >> Correct. >> It's almost the opposite of what you hear oftentimes, how people want to bring the cloud while on premise. >> Exactly. >> It's the opposite here. >> It's the opposite, yeah. 'Cause traditionally, we're very used to monitoring databases on prem, whether that's native auditing, whether that is in memory monitoring, network monitoring, all of these things. But once you take that database workload, and push it into the cloud, all of those monitoring capabilities essentially disappear, 'cause none of that technology was essentially moved over into the cloud, which is a really, really big point for customers, 'cause they cannot take that and just have a gap in their compliance. >> So database discovery is obviously a key step in that process. >> Correct, correct. >> What is database discovery? Why is it important and where does it fit? >> One of the main challenges most customers have is the ability to know where the data sits, and that begins with knowing where the database and how many databases customers have. Whenever we talk to customers and we ask how many databases are within an organization, generally speaking, the answer is 100, 200, 500, and when the actual scanning happens, very often the surprise is it's a lot more than what the customer initially thought, and that's because it's so easy to just spin off a database, work with it, and then forget about it, but from a compliance point of view, that means you're now sitting there, having data, and you're not monitoring it, you're not compliant. You don't even know it exists. So data discovery in terms of database discovery means you got to be able to find where your database workload is and be able to start monitoring that. >> You know, it's interesting. 10 years ago, database was kind of boring. I mean it was like Oracle, SQL Server, maybe DB2, maybe a couple of others, then all of a sudden, the NoSQL explosion occurred. So when we talk about moving databases into the cloud, what are you seeing there? Obviously Oracle is the commercial database market share leader. Maybe there's some smaller players. Well, Microsoft SQL Server obviously a very big... Those are the two big ones. Are we talking about moving those into the cloud? Kind of a lift and shift. Are we talking about conversion? Maybe you could give us some color on that. >> I think there's a bit of both, right? A lot of organizations who have proprietary applications that run since many, many years, there's a certain amount of lift and shift, right, because they don't want to rewrite the applications that run on these databases. But wherever there is a chance for organizations to move into some of their, let's say, more newer database systems, most organizations would take that opportunity, because it's easier to scale, it's quicker, it's faster, they get a lot more out of it, and it's obviously commercially more valuable as well, right? So, we see quite a big shift around NoSQL, but also some of the open source engines, like MySQL, ProsgreSQL, Percona, MariaDB, a lot of the other databases that, traditionally within the enterprise space, we probably wouldn't have seen that much in the past, right? >> And are you seeing that in a lot of those sort of emerging databases, that the attention to security detail is perhaps not as great as it has been in the traditional transaction environment, whether it's Oracle, DB2, even certainly, SQL Server. So, talk about that potential issue and how you guys are helping solve that. >> Yeah, I mean, one of the big things, and I think it was two years ago, when one of the open source databases got discovered essentially online via some, and I'm not going to name names, but the initial default installation had admin as username and no password, right? And it's very easy to install it that way, but unfortunately it means you potentially leave a very, very big gaping hole open, right? And that's one of the challenges with having open source and easily deployable solutions, because Oracle, SQLServer, they don't let you do that that quickly, right? But it might happen with other not as large database instances. One of the things that McAfee for instance does is helps customers making sure that configuration scans are done, so that once you have set up a database instance, that as an organization, you can go in and can say, okay, I need to know whether it's up to patch level, whether we have any sort of standard users with standard passwords, whether we have any sort of very weak passwords that are within the database environment, just to make sure that you cover all of those points, but because it's also important from a compliance point of view, right? It brings me always back to the compliance point of view of the organization being the data steward, the owner of the data, and it has to be our, I suppose, biggest point to protect the data that sits on those databases, right? >> Yeah, well there's kind of two sides of the same coin. The security and then compliance, governance, privacy, it flips. For those edicts, those compliance and governance edicts, I presume your objective is to make sure that those carry over when you move to the cloud. How do you ensure that? >> So, I suppose the biggest point to make that happen is ensure that you have one set of controls that applies to both environments. It brings us back to the hybrid point, right? Because you got to be able to reuse and use the same policies, and measures, and controls that you have on prem and be able to shift these into the cloud and apply them to the same rigor into the cloud databases as you would have been used to on prem, right? So that means being able to use the same set of policies, the same set of access control whether you're on prem or in the cloud. >> Yeah, so I don't know if our folks in our audience saw it today, but Werner Vogels gave a really, really detailed overview of Aurora. He went back to 2004, when their Oracle database went down because they were trying to do things that were unnatural. They were scaling up, and the global distribution. But anyway, he talked about how they re-architected their systems and gave inside baseball on Aurora. Huge emphasis on recovery. So you know, being very important to them, data accessibility, obviously security is a big piece of that. You're working with AWS on Aurora, and RDS as well. Can you talk specifically about what you're doing there as a partnership? >> So, AWS has, I think it was two days ago, essentially put the Aurora database activity stream into private preview, which is essentially a way for third party vendors to be able to read a activity stream off Aurora, enabling McAfee, for instance, to consume that data and bring customers the same level of real-time monitoring to the database as the servers were, as were used to on prem or even in a EC2 environment, where it's a lot easier because customers have access to the infrastructure, install things. That's always been a challenge within the database as the servers were because that access is not there, right? So, customers need to have an ability to get the same level of detail, and with the database activity stream and the ability for McAfee to read that, we give customers the same ability with Aurora PostgreSQL at the moment as customers have on premise with any of the other databases that we support. >> So you're bringing your expertise, some of which is really being able to identify anomalies, and scribbling through all this noise, and identifying the signal that's dangerous, and then obviously helping people respond to that. That's what you're enabling through that connection point. >> Correct, 'cause for organizations, using something like Aurora is a big saving, and the scalability that comes with it is fantastic. But if I can't have the same level of data control that I have on premise, it's going to stop me as an organization, moving critical data into that, 'cause I can't protect it, and I have to be able to. So, with this step, it's a great first step into being able to provide that same level of activity monitoring in real time as we're used to on prem. >> Same for RDS, is that pretty much what you're doing there? >> It's the same for RDS, yes. There is a certain set level of, obviously, you know, we go through before things go into GA but RDS is part of that program as well, yes. >> So, I wonder if we can step back a little bit and talk about some of the big picture trends in security. You know, we've gone from a world of hacktivists to organized crime, which is very lucrative. There are even state sponsored terrorism. I think Stuxnet is interesting. You probably can't talk about Stuxnet. Anyway-- >> No, not really. >> But, conceptually, now the bar is raised and the sophistication goes up. It's an arms race. How are you keeping pace? What role does data have? What's the state of security technology? >> It's very interesting, because traditionally, databases, nobody wanted to touch the areas. We were all very, very good at building walls around and being very perimeter-oriented when it comes to data center and all of that. I think that has changed little bit with the, I suppose the increased focus on the actual data. Since a lot of the legislations have changed since the threat of what if GDPR came in, a lot of companies had to rethink their take on protecting data at source. 'Cause when we start looking at the exfiltration path of data breaches, almost all the exfiltration happens essentially out of the database. Of course, it makes sense, right? I mean I get into the environment through various different other ways, but essentially, my main goal is not to see the network traffic. My main goal as any sort of hacker is essentially get onto the data, get that out, 'cause that's where the money sits. That's what essentially brings the most money in the open market. So being able to protect that data at source is going to help a lot of companies make sure that that doesn't happen, right? >> Now, the other big topic I want to touch on in the minute we have remaining is ransomware. It's a hot topic. People are talking about creating air gaps, but even air gaps, you can get through an air gap with a stick. Yeah, people get through. Your thoughts on ransomware, how are you guys combating that? >> There is very specific strains, actually, developed for databases. It's a hugely interesting topic. But essentially what it does is it doesn't encrypt the whole database, it encrypts very specific key fields, leaves the public key present for a longer period of time than what we're used to see on the endpoint board, where it's a lot more like a shotgun approach and you know somebody is going to pick it up, and going to pay the $200, $300, $400, whatever it is. On the database side, it's a lot more targeted, but generally it's a lot more expensive, right? So, that essentially runs for six months, eight months, make sure that all of the backups are encrypted as well, and then the public key gets removed, and essentially, you have lost access to all of your data, 'cause even the application that access the data can't talk to the database anymore. So, we have put specific controls in place that monitor for changes in the encryption level, so even if only one or two key fields starting to get encrypted with a different encryption key, we're able to pick that up, and alert you on it, and say hey, hang on, there is something different to what you usually do in terms of your encryption. And that's a first step to stopping that, and being able to roll back and bring in a backup, and change, and start looking where the attacker essentially gained access into the environment. >> Markus, are organizations at the point where they are automating that process, or is it still too dangerous? >> A lot of it is still too dangerous, although, having said that, we would like to go more into the automation space, and I think it's something as an industry we have to, because there is so much pressure on any security personnel to follow through and do all of the rules, and sift through, and find the needle in the haystack. But especially on a database, the risk of automating some of those points is very great, because if you make a mistake, you might break a connection, or you might break something that's essentially very, very valuable, and that's the crown jewels, the data within the company. >> Right. All right, we got to go. Thanks so much. This is a really super important topic. >> Appreciate all the good work you're doing. >> Thanks for having me. >> You're very welcome. All right, keep it right there, everybody. You're watching theCUBE. We'll be right back, right after this short break from AWS re:Invent 2018, from Las Vegas. We'll be right back. (techno music)

>> Live from Las Vegas. It's the Cube. Covering AWS re:Invent 2018. Brought to you by Amazon Web Services, Intel and their ecosystem partners. >> And welcome back to Las Vegas. Good afternoon to you. No matter where you're watching, here in the US, we know it is afternoon. As we wind up our coverage for day three at AWS re:invent here on the Cube. One of seven venues we're in right now that's hosting various satellite events. Right now we're in the Sands Expo. Rebecca Knight, John Walls, with Russ Currie. The vice president of Enterprise Strategy at NetScout. Russ, good to see you sir. >> Nice to see you again. >> I've got to be careful. I've got two Bostonian's of sorts here. >> Sorry, sorry. >> So if I don't get something on the accent, you just let me know (laughs) >> We'll talk amongst ourselves. >> Sorry if your sports inferiority complex is.. We're the champions, whatever >> Russ, if you would, first off, your take about what you're seeing here. Because, here we are, day three. As you know, you've been to a lot of shows. Day three, kind of, usually hits a different gear, right? >> Right >> Slows down a little bit. There's still a lot of excitement here. There's still a lot of people around. This show has a little different vibe to it. >> It really does. It's interesting because it becomes a little bit more serious, I think. At this point, in day three for this show, it's now, people are really kind of, they've been exposed to an awful lot in the last three days. And they're really saying, "Okay, now I really want to understand the nuts and bolts of it", and they're spending a little bit more time sitting and learning, understanding what you have to offer them in terms of your solution sense. So it's been an awful lot of fun. Also we did a couple of speaking engagements, so it's really good getting the folks that went and saw our guys speak and seeing them come into the booth and say, 'I want to talk more about that'. >> Well, I want to talk more about that, so you have a new marketing campaign, but first for the viewers who are not familiar with NetScout, you're a Fortune 500 company, but tell us a little more about who you are and what you do. >> Right, so what we do is we provide visibility into the communications between servers and clients and basically see all of the traffic that traverses the network and whether the network is in a public cloud, private cloud, or an on-prem environment, and by looking at that traffic we're able to understand the performance of the services that are being delivered and ensure the security performance of those servers. But right in that perspective we give IT the tools they need to get quicker to the mean time to knowledge, identifying where a problem might be or where a risk may exist and being able to solve those tough problems. >> So it's been a year since you've been on the Cube, I know the esteemed John Walls interviewed you. >> We go way back, yes. >> What's new this year? What sort of advancements, progressions have you implemented? >> So last year when we came in was really our first entry into the public cloud environment and our first entry into AWS, since then we've got a lot of really good traction, a lot of embracing of our technology, we partnered more closely with AWS and got ourselves onto the marketplace. We also enhanced our partnership with VMware and now a part of their NetX integration so we have high levels of integration into both of those platforms, which of course is strong to this entire audience. We've introduced new features and functionality into our product to be able to provide greater visibility, even going deeper into understanding the way the applications are functioning and also added some more security profiling into our products and being able to identify threats as they come into the enterprise network and also as they go out ,so, it's been interesting, it's been a lot of fun. >> You talk about the hybrid cloud and obviously we're hearing that here, this week right, so AWS is obviously slightly shifting its perspective a bit, you know, in terms of on-prem and dealing with the public cloud as well, mind that merger. Your clients, is their any arm twisting that you still have to do or are people buying into it a little more wholeheartedly now in terms of the public cloud and that you've addressed these security concerns? >> I think actually we've become an enabler in often times for our customers, to move to the cloud with competence, where they were a little bit concerned that as they move into the cloud, what kind of investment in tools are they going to have to make? What are they going to potentially lose as they put their workloads into the cloud ? Do they lose a degree of visibility and control? And what we've been able to do is ensure that they have that same experience no matter where they deploy. We were talking earlier about one of our customers that's in the travel and entertainment business and they have been using our gear on cruise ships and in their on-prem data center, but expanded themselves into AWS to extend their capabilities and provide a better user experience for those on ship and now what they really have was the ability to have visibility from ship to shore to cloud and have that perspective and have the confidence that they're delivering a high quality experience to their customers. >> Ship to shore to cloud, not every company can say that. >> Exactly. >> But speaking of motto's, you have a new marketing campaign, visibility without borders. What does that mean? What are you trying to evoke their with your customers? >> What we we're really trying to look at there is the ability to provide visibility no matter where you're deployed. If you have a deployment in a public cloud environment like AWS, you want to have that same level of visibility in your on-prem environment, you want to have it no matter where you have a workload, wherever you have an instance that you want to manage. You want to be able to have that same perspective, one of the things we talk about a little bit, is the idea that, providing a single pane of glass into the service insurance experience and I think that often times, when people try to get to that single pane of glass, they end up with more of a single glass of pain. (laughing) You know, they're trying to aggregate so much stuff that it really doesn't come together too well. >> Right. >> But because we focus in on the data source itself then it just provides that continuity regardless of where they deploy. >> Alright and the importance of visibility, obviously when you're talking about end to end right now, whether you're on-prem or whether you're in the public cloud you're not particular, right? >> Right. >> As a user, I just want to see my operation from start to finish and I don't care where it is. >> Exactly, providing that end to end perspective and being able to understand how I'm delivering services, what the customer experiences, no matter where I deploy and especially when we look at taking advantage of some of the elastic compute capabilities and the like that exists in the cloud, you want to ensure that you're actually getting what you paid for as well, you want to have those controls in place, knowing that what you're delivering is meaningful and impacting the business in a positive way as opposed to, potentially, in a negative way, and spending too much for something that doesn't improve anything in terms of the customer experience. >> Right. >> So the customers, when they want to talk about return on investment, what excites them most? What kind of things are you showing them that is delighting them? >> Often times it's really about mean time to knowledge, we spend a lot of time pointing fingers at each other when we're trying to solve a problem instead of pointing our fingers at the problem. And that's really what we try to focus in on, really getting down into the real details of why something is not performing properly, not, what might be performing improperly. So being able to really get down to that detail and get the right people working on the right problems, I often talk about it in terms of getting the right information, to the right person at the right time, to do the right thing. And if you're able to do that, you're going to provide a better user experience to your customers. >> You mention that a lot of your personnel, a lot of your folks here have been speaking, talking to various groups, I always find that interesting right, because, it's usually the Q&A. >> Yes. >> That when things pop off. So, if you had to generalize about the kind of feedback you're getting from those sessions in terms of the questions, the concerns, the challenges, what are you hearing from folks out there? >> It's kind of funny, one of the things that we get a lot of times is, "You really can do this?" you know, "Is this real what you're showing us?", it's like, yes, this is actual traffic we're showing you exactly what we're seeing. >> Yeah. >> And then they are often pretty amazed at our ability to bring this all into something that visualizes these complex applications that they're delivering across multiple different environments and they have that ah-ah moment where they go, "Oh gosh I really need this, you know, this is really that end to end view that I've been looking for for so long, but I really can't get what I use, a bunch of disparate tools, to try and bring that together" >> So that means, what you just described, is really the definition of innovation, which is providing customers with things that they want, that they didn't even know they wanted. How do you stay innovative? I mean here we are at AWS, Amazon, one of the most innovative companies on the planet and in the history of industry. >> Absolutely. >> How does a company, you're based in Westford, Massachusetts, how do you stay on the cutting edge? >> We spend an enormous amount of time working with our customers and listening to them in terms of where they're going, what their plans are, what new technologies might they be implementing, what are their major initiatives, we regularly reach out and we have constant contact with them to get that feedback and make sure that we're developing solutions that are meaningful to them, it's really about, not what feature can I deliver but what can I provide as value, that's going to make their lives better. Because, as an IT person, it's a tough job right? You're usually the person that people look at and say "Why isn't this working?". >> Right. >> And not being able to have an answer to that, is not a good position to be in. (laughter) Right, so what we're really trying to do is provide them with that answer and give them that ability to be able to answer the tough questions and solve those tough problems. >> Talking about finger pointing, it happens right? >> It does, you know. So what we're really all about is making sure that they're able to get the problem solved as quickly as possible. One of the interesting things I've been hearing from our customers too is that they're looking to this concept of a versatilist, rather than having just a straight forward specialist coming in and work on problems, having people that are a little bit broader in terms of their capabilities and looking at things not only from the perspective, say I'm a network guy, I'm going to look at the network and the app guys going to look at the app. >> Right. >> You got to cross pollinate a little bit and provide that ability to see both sides of that problem, so that's starting to happen. >> Certainly presents a challenge for your workforce right? All of a sudden, you've got to be a little smarter and where a lot of different hats. >> Exactly. >> Versatilist, I like that. You heard it here first. >> Yeah. >> Well, Russ, if you're going to go and ship the shorter cloud, you let us know? OK? >> OK. (laughing) >> Because we want to take that journey with you, alright? >> Love to. >> Thanks for being with us again, good to see you. >> Thank you, it was a pleasure. >> You bet, safe trip home. Back with more here from AWS re:Invent, you are watching us live on the Cube.

>> Live, from Las Vegas, it's theCUBE covering AWS re:Invent 2018. Brought to you by Amazon Web Services, Intel, and their ecosystem partners. >> Hey, welcome back everyone. Live, Cube here in Las Vegas for AWS re:Invent. I'm John Furrier with my co-host, Dave Vellante. Day three of wall to wall coverage, holding our voices together, excited for our next guest, Shayn Hawthorne, general manager at AWS, for the exciting project around the Ground Station, partnership with Lockheed Martin. Really kind of outside the box, announced on Tuesday, not at the keynote, but this is a forward thinking real project which satellites can be provisioned like cloud computing resources. Totally innovative, and will change the nature of edge computing, feeding connectivity to anything. So, thanks for joining us. >> Thank you guys for having me. You're right, my voice is going out this week too. We've been doing a lot of talking. (John laughs) >> Great service. This is really compelling, 'cause it changes the nature of the network. You can feed connectivity, 'cause power and connectivity drive everything. Power, you got battery. Connectivity, you got satellite. Totally obvious, now that you look at it, but, not before this. Where did it come from? How did it all start? >> You know, it came from listening to our customers. Our customers have been talking with us and they had a number of challenges in getting the data off of their satellites and down to the ground. So, we listened to these customers and we listened to the challenges they were experiencing in getting their data to the ground, having access to ground stations, having the ability at the network level, to move the data around the world quickly to where they wanted to process it. And then also, having complex business process logic and other things that were required to help them run their satellite downlinks and uplinks. And then finally, the ability to actually have AWS services right there where the data came down into the cloud, so that you could do great things with that data within milliseconds of it hitting the ground. >> So it's a essentially satellite as a service with a back end data capability, data ingestion, analytics, and management capability. That, how'd that idea come about? I mean, it just underscores the scale of AWS. And I'm thinking about other things that you might be able to, where'd the idea come from? How was it germinated? >> Well and actually, let me just say one thing, we actually would call it Ground Station as the service. It's the Ground Station on the surface of the earth that communicates with the satellite. It allows us to get the data off the satellite or send commands up to it. And so, like I was saying, we came up the idea by talking to our customers, and so we went into, I think this is an incredible part of working at Amazon, because we actually follow through with our leadership principals. We worked backwards from the customer. We actually put together a press release and a frequently asked questions document, a PR/FAQ, in a traditional six page format. And we started working it through our leadership and it got all the way to the point that Andy and the senior leadership team within AWS made the decision that they were going to support our idea and the concept and the architecture that we had come up with to meet these customers' requirements, we actually were able to get to that by about March of 2018. By the end of March, Andy had even had us go in and talk with Jeff. He gave us the thumbs up as well, and after six months, we've already procured 24 antennas. We've already built two Ground Stations in the United States and we've downlinked over hundreds of contacts with satellites, bringing Earth imagery down and other test data to prove that this system works. Get it ready for preview. >> It's unbelievable, because you're basically taking the principals of AWS, which is eliminating the heavy lifting, applying that to building Ground Stations, presumably, right, so, the infrastructure that you're building out, do you have partners that you're working with, are there critical players there, that are enabling this? >> Yeah, it's really neat. We've actually had some really great partnerships, both with helping us build AWS Ground Station, as well as partners that helped us learn what the customers need. Let me tell you, first off, about the partnership that we've had with Lockheed Martin to develop a new innovative antenna system that will collaboratively come together with the parabolic reflectors that AWS Ground Station uses. They've been working on this really neat idea that gives them ability to downlink data all over the entire United States in a very resilient way, which means if some of their Ground Stations antennas in Verge don't work, due to man made reasons or due to natural occurrences, then we're actually able to use the rest of the network to still continue to downlink data. And then, we complimentary bring in AWS Astra for certain types of downlinks and then also to provide uplink commanding to other satellites. The other customer partnership that we've worked with was working with the actual customers who are going to use AWS Ground Station, like DigitalGlobe, Black Sky, Capella SAR, HawkEye 360, who all provided valuable inputs to us about exactly what do they need in a Ground Station. They need the ability to rapidly downlink data, they need the ability to pay by the minute so that there are actually able to use variable expense to pay for satellite downlinks instead of capital expenses to go out and build it. And then by doing that, we're able to offer them a product that's 80% cheaper than if they'd had to go out and build a complete network similar to what we built. And, they're able to, like I said before, access great AWS services like Rekognition, or SageMaker, so that they can make sense of the data that they bring down to the Earth. >> It's a big idea and I'm just sort of curious as to, how and if you, sort of, validated it. How'd ya increase the probability that it was actually going to, you know, deliver a business return? Can you talk about that process? >> Well, we were really focused on validating that we could meet customer challenges and really give them the data securely and reliably with great redundancy. So we validated, first off by, we built our antennas and the Ground Stations in the previous software. We finished over a month and a half ago, and we've been rigorously testing it with our customer partners and then letting them validate that the information we've provided back to them was 100% as good as what they would've received on their own network, and we tested it out, and we've actually got a number of pictures and images downloaded over at our kiosk that were all brought in on AWS Ground Station, and its a superb products over there. >> So Shayn, how does it work? You write this press release, this working backwards document, describe that process. Was that process new to you? Had you done it at other companies? How did you find it? Was it a useful process, obviously it was, 'cause you got the outcome you're looking for, but, talk a little bit more about that approach. >> Yeah, it's actually very cool, I've only been at AWS for a year and a half. And so, I would say that my experience at AWS so far completely validates working backwards from customers. We were turned on to the idea by talking to our customers and the challenges they said. I started doing analysis after the job was assigned to me by Dave Nolton, my boss, and I started putting together the first draft of our PR/FAQ, started engaging with customers immediately. Believe it or not, we went through 28 iterations of the PR/FAQ before we even got to Andy. Everybody in our organization took part in helping to make it better, add in, ask hard questions, ensure that we were really thinking this idea through and that we were obsessing on the customer. And then after we got to Andy, and we got through approving that, it probably went through another 28 iterations before we got to Jeff. And then we went through talking with him. He asked additional hard questions to make sure that we were doing the right for the customer and that we were putting together the right kind of product. And finally we've been iterating it on it ever since until we launched it couple of days ago. >> Sounds like you were iterating, raising the bar, and it resonated with customers. >> Totally. And even as part of getting out of it-- >> That's Amazon's language of love. >> And then your engineering resource, you know, if people are asking you hard questions, you obviously need engineering folks to validate that it's doable. At what point do you get that engineering resource, how does that all work? >> Well, it's neat. In my division, Region Services Division, we actually were supporting it completely from within the division, all the way until we got approval from Andy. And then we actually went in and started hiring very good skills. To show you what kind of incredible people we have at Amazon, we only had to hire about 10% space expertise from outside of the company. We were actually able to bring together 80-90% of the needed skills to build AWS Ground Station from people who've been working at Amazon.com and AWS. And we came together, we really learned quickly, we iterated, failed fast, put things together, changed it. And we were able to deliver the product in time. The whole cloth made from our own expertise. >> So just to summarize, from idea to actual, we're going to do this, how long did that take? >> I'd say that took about three months. From idea to making a decision, three months. From decision to have a preview product that we could launch at re:Invent, six months. >> That's unbelievable. >> It is. >> If you think about something of this scope. >> And it was a joy, I mean it was an incredible to be a part of something like this. It was the best work I've ever done in my life. >> Yeah, space is fun. >> It is. >> Shayn, thanks for coming on theCUBE, sharing your story and insight, we love this. We're going to keep following it. And we're going see you guys at the Public Sector Summits, and all the events you guys are at, so, looking forward to seeing and provisioning some satellite. >> I'm looking forward to showing you what we do next. So thank you for having me. >> Great. We'll get a sneak peak. >> Congratulations. >> This is theCUBE here in Las Vegas, we'll be back with more coverage after this short break. (futuristic music)

(upbeat music) >> Live from Las Vegas, it's theCUBE covering AWS re:Invent 2018. Brought to you by Amazon Web Services, Intel, and their ecosystem partners. >> Okay, welcome back everyone. Live coverage here in Las Vegas for Amazon re:Invent 2018. Day three, we're winding down over 150 videos. We'll have over 500 clips. Losing the voice. Dave Vellante, my co-host. Suzi analyst tech that we're going to extract theCUBE insights, James Kobielus. David Floyer from Wikibon. Jim you've been prolific on the blogs, Siliconangle.com, great stories. David you've got some research. What's your take? Jim, you're all over what's going on in the news. What's the impact? >> Well I think what this years re:Invent shows is that AWS is doubling down on A.I. If you look at the sheer range of innovative A.I. capabilities they've introduced into their portfolio, in terms of their announcements, it's really significant. A. They have optimized tense or flow for their cloud. B. They now have an automated labeling, called Ground Truth, labeling capability that leverages mechanical turf, which has been an Amazon capability for a while. They've also got now the industries first, what's called reinforcement learning plug-in to their data science tool chain, in this case Sage Maker, reinforcement learning is becoming so important for robotics, and gaming, and lots of other applications of A.I., and I'm just scratching the surface. So they've announced a lot of things, and David can discuss other things, but I'm seeing the depth of A.I. Their investment in it shows that they've really got their fingers on what enterprises are doing, and will be doing to differentiate themselves with this technology over the next five to ten years. >> What's an area that you see that people are getting? Clearly A.I. What areas are people missing that's compelling that you've observed here? >> When you say people are missing, you mean the general...? >> Journalists. >> Oh. >> Audience. There's so much news. >> Yeah. Yeah. >> Where are the nuggets that are hidden in the news? (laughing) What are you seeing that people might not see that's different? >> Getting back to the point I was raising, which is that robotics is becoming a predominant application realm for A.I. Robotics, outside the laboratory, or outside of the industrial I.O.T., robots are coming into everything, and there's a special type of A.I. you build into robots, re-enforcement learning is a big part of it. So I think the general, if you look at the journalists, they've missed the fact that I've seen in the past couple of years, robotics and re-enforcement learning are almost on the verge of being mainstream in the space, and AWS gets it. Just the depth of their investments. Like Deep Racer, that cute little autonomous vehicle that they rolled out here at this event, that just shows that they totally get it. That will be a huge growth sector. >> David Floyer, outpost is their on premises cloud. You've been calling this for I don't know how many years, >> (laughing) Three years. >> Three years? >> Yeah. What's the impact? >> And people said, no way Foyer's wrong (laughing). >> So you get vindication but... >> And people, in particular in AWS. (laughing) >> So you're right. So you're right, but is it going to be out in a year? >> Yeah, next in 2019. >> Will this thing actually make it to the market? And if it does what is the impact? Who wins and who loses? >> Well let's start with will it get to the market? Absolutely. It is outposts, AWS Outposts, is the name. It is taking AWS in the cloud and putting it on premise. The same API's. The same services. It'll be eventually identical between the two. And that has enormous increase in the range, and the reach that AWS and the time that AWS can go after. It is a major, major impact on the marketplace, puts pressure on a whole number of people, the traditional vendors who are supplying that marketplace of the moment, and in my opinion it's going to be wildly successful. People have been waiting that, wanting that, particularly in the enterprise market. They reasons for it are simple. Latency, low latency, you've got to have the data and the compute very close together. Moving data is very, very expensive over long distances, and the third one is many people want, or need to have the data in certain places. So the combination is meeting the requirements, they've taken a long time to get there. I think it's going to be, however wildly successful. It's going to be coming out in 2019. They'll have their alpha, their betas in the beginning of it. They'll have some announcements, probably about mid 2019. >> Who's threatened by this? Everybody? Cisco? HP? Dell? >> The integration of everything, storage, networking, compute, all in the same box is obviously a threat to all suppliers within that. And their going to have to adapt to that pretty strongly. It's going to be a declining market. Declining markets are good if you adapt properly. A lot of people make a lot of money from, like IBM, from mainframe. >> It's a huge threat to IBM. >> You're playing it safe. You're not naming names. (laughing) Okay, I'll rephrase. What's your prediction? >> What's my prediction on? >> Of the landscape after this is wildly successful. >> The landscape is that the alternatives is going to be a much, much smaller pie, and only those that have volume, and only those that can adapt to that environment are going to survive. >> Well, and let's name names. So who's threatened by this? Clearly Dell, EMC, is threatened by this. >> HP. >> HP, New Tanix, the VX rat guys, Lenovo is in there. Are they wiped out? No, but they have to respond. How do they respond? >> They have to respond, yeah. They have to have self service. They have to have utility pricing. They have to connect to the cloud. So either they go hard after AWS, connecting AWS, or they belly up to Microsoft >> With Azure Stack, >> Microsoft Azure. that's clearly going to be their fallback place, so in a way, Microsoft with Azure Stack is also threatened by this, but in a way it's goodness for them because the ecosystem is going to evolve to that. So listen, these guys don't just give up. >> No, no I know. >> They're hard competitors, they're fighters. It's also to me a confirmation of Oracle's same same strategy. On paper Oracle's got that down, they're executing on that, even though it's in a narrow Oracle world. So I think it does sort of indicate that that iPhone for the enterprise strategy is actually quite viable. If I may jump in here, four things stood out to me. The satellite as a service, was to me amazing. What's next? Amazon with scale, there's just so many opportunities for them. The Edge, if we have time. >> I was going to talk about the Edge. >> Love to talk about the Edge. The hybrid evolution, and Open Source. Amazon use to make it easy for the enterprise players to complete. They had limited sales and service capabilities, they had no Open Source give back, they were hybrid deniers. Everything's going to go into the public cloud. That's all changed. They're making it much, much more difficult, for what they call the old guard, to compete. >> So that same way the objection? >> Yeah, they're removing those barriers, those objections. >> Awesome. Edge. >> Yeah, and to comment on one of the things you were talking about, which is the Edge, they have completely changed their approach to the Edge. They have put in Neo as part of Sage Maker, which allows them to push out inference code, and they themselves are pointing out that inference code is 90% of all the compute, into... >> Not the training. >> Not the training, but the inference code after that, that's 90% of the compute. They're pushing that into the devices at the Edge, all sorts of architectures. That's a major shift in mindset about that. >> Yeah, and in fact I was really impressed by Elastic Inference for the same reasons, because it very much is a validation of a trend I've been seeing in the A.I. space for the last several years, which is, you can increasingly build A.I. in your preferred visual, declarative environment with Python code, and then the abstraction layers of the A.I. Ecosystem have developed to a point where, the ecosystem increasingly will auto-compile to TensorFlow, or MXNet, or PyTorch, and then from there further auto-compile your deployed trained model to the most efficient format for the Edge device, for the GP, or whatever. Where ever it's going to be executed, that's already a well established trend. The fact that AWS has productized that, with this Elastic Inference in their cloud, shows that not only do they get that trend, they're just going to push really hard. I'm making sure that AWS, it becomes in many ways, the hub of efficient inferencing for everybody. >> One more quick point on the Edge, if I may. What's going on on the Edge reminds me of the days when Microsoft was trying to take Windows and stick it on mobile. Right, the windows phone. Top down, I.T. guys coming at it, >> Oh that's right. >> and that's what a lot of people are doing today in IT. It's not going to work. What Amazon is doing see, we're going to build an environment that you can build applications on, that are secure, you can manage them from a bottoms up approach. >> Yeah. Absolutely. >> Identifying what the operations technology developers want. Giving them the tools to do that. That's a winning strategy. >> And focusing on them producing the devices, not themselves. >> Right. >> And not declaring where the boundaries are. >> Spot on. >> Very very important. >> Yep. >> And they're obviously inferencing, you get most value out of the data if you put that inferencing as close as you possibly can to that data, within a camera, is in the camera itself. >> And I eluded to it earlier, another key announcement from AWS here is, first of all the investment in Sage Maker itself is super impressive. In the year since they've introduced it, look at they've already added, they have that slide with all the feature enhancements, and new modules. Sage Maker Ground Truth, really important, the fully managed service for automating labeling of training datasets, using Mechanical Turk . The vast majority of the costs in a lot of A.I. initiatives involves human annotators of training data, and without human annotated training data you can't do supervised learning, which is the magic on a lot of A.I, AWS gets the fact that their customers want to automate that to the nth degree. Now they got that. >> We sound like Fam boys (laughing). >> That's going to be wildly popular. >> As we say, clean data makes good M.L., and good M.L. makes great A.I. >> Yeah. (laughing) >> So you don't want any dirty data out there. Cube, more coverage here. Cube insights panel, here in theCUBE at re:Invent. Stay with us for more after this short break. (upbeat music)

(light electronic music) >> Live from Las Vegas, it's The Cube covering AWS re:Invent 2018. Brought to you by Amazon Web Services, Intel and their ecosystem partners. >> We are back in Las Vegas here at AWS re:Invent alone with Rebecca Knight and I'm John Walls and I know what you're thinking. Email, oh my god, email. The avalanche, the problems that are causes here folks in IT. Well, I tell you what, Chris McFadden is here to solve your problems. (mumbles) engineering at SparkPost. Chris good to see you this afternoon, thanks for joining us. Good to see you, I'm happy to be on The Cube. >> Yeah, great. >> It's my third time at re:Invent, but first time on The Cube so happy to be here. >> Welcome. >> So a Cube rookie. >> (laughs) >> We ever find, to leave you with it on the way out, remind me to get it for you. Alright, so tell us about SparkPost first off, about, we talk about email, what your primary focus is and just the challenges that you are trying to solve to your clients. >> Sure, SparkPost is the leading email delivery provider. So our customers send over five trillion emails a year. That's over 37% of the world's commercial email. That's obviously a lot of email. So we're focused on B2C email and what that means is that any app who has the need to send email, we help with getting that email on time into the inbox. That really helps product managers and product teams with ensuring that they can get the right performance, the analytics and also the human services to make sure that they can get customers to adopt their service, grow engagement and ultimately revenues. >> I understand you have a new product, SparkPost Signals, tell our viewers a little bit more. >> Yeah, so I'm very excited to talk about SparkPost Signal. So as everybody knows, your email is super important to people, and with email being such a high ROI for most companies, when you have a different email performance that could really impact a company's revenue as well. So I'm excited to talk about SparkPost Signals because what that could really help with is being able to provide some dashboards and tools so that you can have more data driven predictive, actionable insight so that ordinary customers can have that kind of email expertise at their fingertips really to be able to then boost their performance. So I can certainly talk about some of the particular challenges that this would solve for people. So in particular, we have a health score and also a spam chart reporting. So for example, what could happen is, if you or maybe somebody in the organization that you don't even know about, they could go out and acquire an email list. More email addresses, the better. >> Sure. >> The next thing you know, you end up landing on spam traps, you're getting blocked, you're email's not going out. So it's better off to get early notice about whether there's some sort of problem so then you can actually react and correct the problem before it starts impacting your business. >> So is it a delivery problem or challenge or is it a firewall challenge or problem. Kind of, how do you balance that out because you, it seems like it's a little bit of both actually or it could be a little bit of both. >> So email is a very much an open network. There's no one particular tech company really owns it so anybody can send any email. That's why most email that's sent is actually spam. So on the ISP side, these are the internet service providers who are Gmail or Hotmail that are actually receiving the email, they are very protective of their users. So what that means is that if you buy email addresses or you're sending too much to people and they say, I don't want this email, then the ISPs can actually say, you know, you're doing this too much, you're being abusive and we're actually going to start blocking you so none of your email is actually then going to get delivered. So none of your password resets, none of your auto-confirmations, none of your marketing email. So you have to be very, you have to have very good email sending practices otherwise you run into trouble. So for most customers from most companies we work with, they're expertise is elsewhere, you know. They're in social media, they're in banking, >> Marketing >> whatever it is. They don't necessarily know all the best ways to be able to manage their email streams. >> And yet email is mission critical to their businesses. >> Exactly >> This product launches in January but you've already been testing the waters a bit with some of your customers. What are you hearing, what are they saying? >> So we've heard a lot of very good things. The usual response from customers is when can we get it, you know. So we're frantically working to roll this out. But we've actually, when we were doing the demos with customers, we were actually showing them real data so this wasn't hypothetical. We were actually showing them real data with their own health scores, with their spam trap reports. Also showing, which is really interesting, their engagement cohorts. So what that means is that if customers, or companies that work us are not sending to their most engaged users but are also sending to users that don't actually engage much at all, then that can actually hurt their overall deliverability and engagement so when we show them these cohort reports, showing them that if you actually are sending more to your more engaged users, ultimately your engagement and revenue's going to go up. So we've actually worked, even before Signal is a product, we've worked with customers to do this. We have some very high-profile customers who've actually reduces the volume of email they've sent through is but their actual engagement has gone through the roof as well as their revenue. We've also worked with customers and that's more on the engagement cohort reporting. On the other side, when it comes to span trap reporting, we've had customers who've actually run into problems where they inadvertently started emailing to addresses that are on spam traps. Spam traps if you don't know are essentially bogus email addresses that are out there, like honeypots and if you email them, then it tells the spam trap owner that you obviously didn't get a real person to subscribe to this or to opt in so you're obviously following bad practices and I'll report you to maybe a blacklist which will then prevent all of your email being delivered. So we were able to work with that customer to really identify the rate of spam trap hits that they have and they were able to clean up their own practices based on that and then get back in business and actually have better engagement for what they're doing. >> So you're here at AWS, so there's a public cloud play here somewhere. Is this about a customer migration, are you educating people and bringing them along as well for the public cloud experience. I mean, what are you doing here. >> Right, so we have our cloud services and that's built on AWS. We've been in AWS for over four years now and we love coming here and learning about a lot of the new technology. We also have a booth here, we're providing our own services. What we also have is that ewe had an on-premise product, Momentum and PowerMTA and both of those products are heavily used throughout the industry for sending email. So we have a number of customers who are coming to us and saying, we're looking to move to the cloud. So we can either help them move their mail streams to SparkPost which can be very convenient or if they want to continue to run their own MTAs and some of their own infrastructure, possibly maybe they're a bank or maybe it's just not the right time for them then we're able to look at other options. Potentially things like hybrid analytics and that's a way for them to be able to get the addition analytics and things like SparkPost Signals but without actually moving everything. But I'm definitely very encouraged. Yesterday's keynote had Guardian and that's quite an ambitious project to be able to move to the cloud so I'm very excited. We're also, SparkPost is one of their SAS providers that they chose to use in part of their migration. So rather than continue to try to run their own infrastructure, they said, here's an API, I trust SparkPost, they've got the right security, support services to be able to get the job done. >> I'm curious about the future and sort of, will email always be an integral part of doing business for companies and how SparkPost is thinking about its future business model. >> Right, so email's been dead about 20 years. >> Supposedly, that's what they keep saying. (laughs) >> However, every year, email volumes keep growing. Everybody has an email address, really it's the preferred method of communication even among millennials nowadays. Emails also again, it's an open platform so it's not controlled by the big tech companies so it's very ubiquitous. It's also a good system of record and also there's certain things that don't really make sense to send over push or SMS. So email continues to be a (mumbles) for companies both in triggered email as well as marketing email. So we have a number of customers who are in these next generation martech vendors who are providing even more services. They use us as the back end for doing that delivery but they're seeing even more demand for again, on the marketing side and again, there's more and more apps being built. There's more and more opportunities there. They all need to send email and we see certainly with SparkPost Signals and otherwise, that with the smart use of data, there really becomes an even better opportunity to grow those relationships with your customers. So rather than just being a transaction, that's an opportunity for a relationship building interaction. >> A value add. >> Right. >> Well, five trillion emails, I think half of them, I think I've sent in half of those these days so maybe you and I aught to talk 'cause (mumbles) Thanks for the time. Thanks for coming here on The Cube and again, leave you with a parting gift, please, >> Thank you, I appreciate it >> by all means. Chris McFadden joined us here and we'll be back with more from AWS re:invent, we are live on The Cube from Las Vegas. (light electronic music)

>> Live from Las Vegas, it's theCUBE. Covering AWS re:Invent 2018. Brought to you by Amazon web services, intel, and their ecosystem partners. >> Welcome back everyone to theCUBE's live coverage of AWS re:Invent, here at the Venetian in Las Vegas. I'm your host, Rebecca Knight, along with my co-host John Furrier. We're joined by Clement Pang. He is the co-founder of Wavefront by VMware. Welcome. >> Thank you Thank you so much. >> It's great to have you on the show. So, I want you tell our viewers a little bit about Wavefront. You were just purchased by VMware in May. >> Right. >> What do you do, what is Wavefront all about? >> Sure, we were actually purchased last year in May by VMware, yeah. We are an operational analytics company, so monitoring, I think is you could say what we do. And the way that I always introduce Wavefront is kind of a untold secret of Silicon Valley. The reason I said that is because in the, well, just look at the floor. You know, there's so many monitoring companies doing logs, APM, metrics monitoring. And if you really want to look at what do the companies in the Valley really use, right? I'm talking about companies such as Workday, Watts, Groupon, Intuit, DoorDash, Lyft, they're all companies that are customers of Wavefront today. So they've obviously looked at all the tools that are available on the market, on the show floor, and they've decided to be with Wavefront, and they were with us before the acquisition, and they're still with us today, so. >> And they're the scale-up guys, they have large scale >> That's right, yeah, container, infrastructure, running clouds, hybrid clouds. Some of them are still on-prem data centers and so we just gobble up all that data. We are platform, we're not really opinionated about how you get the data. >> You call them hardcore devops. >> Yes, hardcore devops is the right word, yeah. >> Pushing the envelope, lot of new stuff. >> That's right. >> Doing their own innovation >> So even serverless and all the ML stuff that that's been talked about. They're very pioneering. >> Alright, so VMware, they're very inquisitive on technology, very technology buyers. Take a minute to explain the tech under the covers. What's going on. >> Sure, so Wavefront is a at scale time series database with an analytics engine on top of it. So we have actually since expanded beyond just time series data. It could be distributed histograms, it could be tracing, it includes things like events. So anything that you could gather up from your operation stack and application metrics, business metrics, we'll take that data. Again, I just said that we are unopinionated so any data that you have. Like sometimes it could be from a script , it could be from your serverless functions. We'll take that data, we'll store it, we'll render it and visualize it and of course we don't have people looking at charts all day long. We'll alert you if something bad is going on. So teams just really allow the ability to explore the data and just to figure out trends, correlations and just have a platform that scales and just runs reliably. >> With you is Switzerland. >> Yeah, basically I think that's the reason why VMware is very interested, is cause we work with AWS, work with Azure, work with GCP and soon to be AliCloud and IBM, right. >> Talk about why time series data is now more on board. We've got, we've had this conversation with Smug, we saw the new announcement by Amazon. So 'cause if you 're doing real-time, time matters and super important. Why is it important now, why are people coming to the realization as the early adopters, the pioneers. >> That's right, I think I used to work at Google and I think Google, very early on I realized that time series is a way to understand complex systems, especially if you have FMR workloads and so I think what companies have realized is that logs is just very voluminous, it's very difficulty to wield and then traditional APM products, they tend to just show you what they want to show you, like what are the important paying points that you should be monitoring and with Wavefront, it's just a tool that understands time series data and if you think about it, most of the data that you gather out of your operational environment is timer series data. CPU, memory, network, how many people logging in, how many errors, how many people are signing up. We certainly have our customer like Lyft. You know, how many of you are getting Rise, how many credit cards are off. You know all of that information drives, should we pay someone because a certain city, nobody is getting picked up and that's kind of the dimension that you want to be monitoring on, not on the individual like, okay this base, no network even though we monitor those of course. >> You know, Clement, I got to talk to you about the supporting point because we've been covering real time, we've been covering IoT, we've been doing a ton of stuff around looking at the importance of data and having data be addressable in real-time. And the database is part of the problem and also the overall architecture of the holistic operating environment. So to have an actual understanding of time series is one. Then you actually got to operationalize it. Talk about how customers are implementing and getting value out of time series data and how they differentiate that with data leagues that they might spin up as well as the new dupe data in it. Some might not be valuable. All this is like all now coming together. How do people do that? >> So I think there were a couple of dimensions to that. So it's scalability is a big piece. So you have to be able to take in enormous amount of data, (mumbles) data leagues can do that. It has to be real-time, so our latency from ingestion to maturalization on a chart is under our second So if you're a devops team, you're spinning up containers, you can't go blind for even 10 seconds or else you don't know what's going on with your new service that you just launched. So real-time is super important and then there's analytics. So you can't, you can see all the data in real-time but if it's like millions of time series coming in, it's like the matrix, you need to have some way to actually gather some insights out of that data. SO I think that's what we are good at. >> You know a couple of years ago, we were doing Open Compute, a summit that Facebook puts on, you eventually worked with Google so I see he's talking about the cutting edge tech companies. There's so much data going onto the scale, you need AI, you got to have machines so some of the processing, you can't have this manual process or even scrips, you got to have machines that take care of it. Talk about the at-scale component because as the tsunami of data continues to grow, I mean Amazon's got a satellite, Lockheed Martin, that's going to light up edge computing, autonomous vehicles, pentabytes moving to the cloud, time series matters. How do people start thinking about machine learning and AI, what do you guys do. >> So I think post-acquisition I would say, we really double down on looking at AI and machine learning in our system. We, because we don't down sample any of the data that we collect, we have actually the raw data coming in from weather sensors, from machines, from infrastructure, from cloud and we just is able to learn on that because we understand incidence, we understand anomalies. So we can take all of that data and punch it through different kinds of algorithms and figures out, maybe we could just have the computer look at the incoming time series data and tell you if its anomalist, right. The holy grail for VMware I think, is to have a self-driving data center and what that means is you have systems that understands, well yesterday there was a reinforcement learning announcement by Amazon. How do we actually apply those techniques so that we have the observability piece and then we have some way to in fact change against the environment and then we figure out, you know, just let the computer just do it. >> I love this topic, you should come into our studio, if I'm allowed to, we'll do a deep dive on this because there's so many implications to the data because if you have real-time data, you got to have the streaming data come in, you got to make sense of it. The old networking days, we call it differentiate services. You got to differentiate of the data. Machine learning, if the data's good, it works great, but data sucks, machine learning doesn't go well so if I want that dynamic of managing the data so you don't have to do all this cleaning. How do people get that data verified, how do they set up the machine learning. >> Sure, it still required clean data because I mean, it's garbage in, garbage out >> Not dirty data >> So, but the ability for us, for machine learning in general to understand anything in a high dimensional space is for it to figure out, what are the signals from a lot of the noise. A human may require to be reduces in dimensionality so that they could understand a single line, a single chart that they could actually have insights out of. Machines can technically look at hundreds or even tens of thousands of series and figures out, okay these are the two that are the signals and these are the knobs that I could turn that could affect those signals. So I think with machine learning, it actually helps with just the voluminous nature of the data that we're gathering. And figuring out what is the signal from the noise. >> It's a hard problem. So talk about the two functionalities you guys just launched. What's the news, what are you doing here at AWS. >> So the most exciting thing that we launched is our distributed tracing offering. We call it a three-dimensional micro service observability. So we're the only platform that marry metrics, histograms and distributed tracing in a single platform offering. So it's certainly at scale. As I said, it's reliable, it has all the analytical capabilities on top of it, but we basically give you a way to quickly dive down into a problem and realize what the root cause is and to actually see the actual request at it's context. Whether it's troubleshooting , root cause analysis, performance optimization. So it's a single shop kind of experience. You put in our SDK, it goes ahead and figures out, okay you're running Java, you're running Jersey or Job Wizard or Spring Boot and then it figures out, okay these are the key metrics you should be looking at. If there are any violations, we show you the actual request including multiple services that are involved in that request and just give you an out of the box turn keyway to understand at scale, microservice deployments, where are the pain points, where is latency coming from, where are the errors coming from. So that's kind of our first offering that we're launching. Same pricing mode, all that. >> So how are companies going to use this? What kind of business problem is this solving. >> So as the world transitions to a deployment architecture that mostly consists of Microservices, it's no longer a monolytic app, it's no longer an end-tier application. There are a lot of different heterogeneous languages, frameworks are involved, or even AWS. Cloud services, SAS services are involved and you just have to have some way to understand what is goin on. The classic example I have is you could even trace things like an actual order and how it goes through the entire pipeline. Someone places the orders, a couple days later there's someone who, the orders actually get shipped and then it gets delivered. You know, that's technically a trace. It could be that too. You could send that trace to us but you want to understand, so what are the different pieces that was involved. It could be code or it could be like a vendor. I could be like even a human process. All of that is a distributed tracing atom and you could actually send it to Wavefront and we just help you stitch that picture together so you could understand what's really going on. >> What's next for you guys. Now you're part of VMware. What's the investment area, what are you guys looking at building, what's the next horizon? >> So I think, obviously the (mumbles) tracing, we still have a lot to work on and just to help teams figure out, what do they want to see kind of instantly from the data that we've gathered. Again, we just have gathered data for so long, for so many years and at the full resolution so why can't we, what insights can develop out of it and then as I said, we're working on AI and ML so that's kind of the second launch offering that we have here where you know, people have been telling us, it's great to have all the analytics but if I don't have any statistical background to anything like that, can you just tell me, like, I have a chart, a whole bunch of lines, tell me just what I should be focusing on. So that's what we call the AI genie and so you just apply, call it a genie I guess, and then you would basically just have the chart show you what is going wrong and the machines that are going wrong, or maybe a particular service that's going wrong, a particular KPI that's in violation and you could just go there and figure out what's-- >> Yeah, the genie in the bottle. >> That's right (crosstalk) >> So final question before we go. What's it like working for VMware start-up culture. You raised a lot of money doing your so crunch based reports. VMware's cutting edge, they're a part with Amazon, bit turn around there, what's it like there? >> It's a very large company obviously, but they're, obviously as with everything, there's always some good points and bad points. I'll focus on the good. So the good things are there's just a lot of people, very smart people at VMware. They've worked on the problem of virtualization which was, as a computer scientist, I just thought, that's just so hard. How do you run it like the matrix, right, it's kind of like and a lot of very smart people there. A lot of the stuff that we're actually launching includes components that were built inside VMware based on their expertise over the years and we're just able to pull, it's just as I said, a lot of fun toys and how do we connect all of that together and just do an even better job than what we could have been as we were independent. >> Well congratulations on the acquisition. VMware's got the radio event we've covered. We were there, you got a lot of engineers, a lot of great scientists so congratulations. >> Thank you so much. >> Great, Clement thanks so much for coming on theCUBE. >> Thank you so much Rebecca. >> I'm Rebecca Knight for John Furrier. We will have more from AWS re:Invent coming up in just a little bit. (light electronic music)

>> Live from Las Vegas, it's theCUBE, covering AWS re:Invent 2018, brought to you buy Amazon Web Services, Intel and their ecosystem partners. And welcome back here at AWS re:Invent. We are live in Las Vegas, day three of our coverage right here on the Cube, and we continue our discussion now with Justin Warren and John Walls, with Matt Yanchyshyn, who is the director of solutions architecture at AWS. >> That's right. >> Good morning. Good to see you, sir. >> Thanks for having me. >> And Nick Cayou, vice president of the global ecosystem at Pivotal. And, good to see you this morning, Nick. >> Good morning, thanks for having me. >> All right, first off let's just get your take on what's happening here. We were talking a little but before we got started about here we are, day three, well day four if you count the partner conferences, but last day of the show, and there's still a lot of excitement in the air. >> All the energy out here. >> The show floor's still packed. What have you guys seen this week that's kind of stood out in your mind, Matt? >> Well, I mean people stick around for the third day because Werner Vogels is like a hero for so many people here and so, you know, a lot of buzz is to see his keynote this morning. You know, one thing I've been really excited about is all the announcements around machine learning this week. There's just been an incredible amount of innovation, and people are really excited about the DeepRacer and the DeepRacer league announced this morning, so that, you know, the momentum we're seeing and the excitement around machine learning is really cool to see. >> And from your perspective, Nick? >> I'm joining the marathon towards the middle. I came in last night. Matt and I had dinner. But I think the most impactful announcement I saw coming out of AWS was probably the Outposts announcement, sort of the commitment to hybrid, which, and I know Matt played a big role in kind of pioneering that and so that's super exciting, and I just can't believe how many people have stuck around. I mean, we're on the last day of this thing, and it's like, you know, people are staying after the party. They won't leave the house. >> Yeah, exactly right. Well, at four O'clock they're going to have important things that we're going to think about. DeepRacer, by the way, we've had a couple of guests on. That was a really cool idea about taking literally a small, toy truck, if you will, but programming it and doing some, not reflective learning, but reinforced learning with it, and then actually taking it into practice and putting these cars on tracks and having a yearlong competition. So we'll kind of see next year, how that works out. >> Yeah. >> AWS and Pivotal, all right. So what are the two of aligned with now? What brings the two of you here, and the two companies together? >> Yeah, well, I mean, I think first of all, as companies we have a lot in common, certainly how we think about customers. We're both really sort of customer-obsessed companies. But, you know what I see a lot, I work with partners all day long, and we want to make it easy for both our customers and our partners to embrace modern DevOps, like all these enterprises are going through DevOps transformation, and any tools and partnerships we can create to make that journey easier is really a priority for me and my team. >> Okay, and then from the Pivotal side of the fence? >> Yeah, I would say largely it's our customers. You know, a large portion of our clients have chosen to run Pivotal Cloud Foundry, which is sort of our flagship platform, as a service on AWS. Going back to, you know, tune of 2014 was the first public IaaS we supported after Vsphere, so, you know, I think our customers are pushing us to work together, and I think we've met that challenge. You know, one of the things we're here to talk about from a Pivotal perspective is all the work we've done with Amazon to expose Amazon services to our platform through this technology called a service broker, that you know, over the past six months, Amazon engineers and Pivotal engineers have worked kind of assiduously to deliver to market, and now it's getting in the hands of customers. You know, after this session we're going to go speak with about 50 customers in a private room about how they're deploying Cloud Foundry on AWS and utilizing the service broker to be more productive and drive more innovation of services into their developer community. >> So what are some of the services customers are attracted to? What are they pushing you to put into this service broker? What do they want to do with that? Maybe you could give us a bit of a flavor of that? >> So we came out initially a couple months ago with 18 services that we support, so things like S3, RDS, some of the Hadoop offerings. You know, I think we're going to see the basics, the S3s, probably consumed first, but we're working. We're actually putting some ideas together to see how we can build kind of reference architectures and paradigms to let our customers know how to take advantage of these services like machine learning or some of the Hadoop offerings, etc. >> Yeah, I mean, we started out with some of the IoT integrations already for the service brokers, but I agree. We're starting with the core services, the databases, DynamoDB, RDS, S3, etc. And we're starting to layer in more services over time. >> Well you've got to start with the basics so that you can then build upon that. >> Exactly. >> Which is what Amazon has a long history of doing. You know, you started with EC2 and then you grew beyond S3 and now we have services like SageMaker and things that drive the car with DeepRacer, so it would be nice if we could actually do training models using Pivotal Cloud Foundry. >> Well actually, nothing's stopping us from using PCF. One of the things I love about it is with Cloud Foundry you can use the Service Brokers. It makes it easier for you to adopt AWS services, but nothing's stopping you from using any AWS service, and it's one of actually the great parts of the partnership, so you're not limited to what we have service brokers for. >> Yeah. So, enterprises have been going on this cloud journey for some time, and Amazon's been around for a long time. AWS has had these services for a while, Pivotal as well. Where are we seeing customers? Where's the momentum for customers, where they're transforming their businesses, and we're hearing a lot about hybrid cloud here at the show. Where are enterprises putting their workloads? What are they looking at putting workloads into hybrid as compared to putting things over into public cloud or using Pivotal Cloud Foundry for? >> I guess I'll take it from my angle first. So, you know, approximately 70% of our customers are still running their workloads on prem, right? That doesn't mean to say that they're not expanding those applications out to Amazon, for example, and I think the key trend we're seen is, you know, cloud is becoming more of an operating model, and what we focus on is teaching our clients how to build and rebuilt software. The big sort of surface area below the iceberg for us right now is all of the enterprise applications, legacy monoliths that need to be kind of decomposed and moved into a cloud operating model, modernized through things like data services that we can expose through our platform to something like AWS. And, you know, it's starting to shift. We were talking earlier about the Outpost and how I think the goal is to kind of meet customers where they are together, if that's the best way to put it. >> Yeah. >> Both Amazon and Pivotal. >> Yeah, I mean with the size of customers we're working with, like Comcast and Liberty Mutual and US Air Force, it's not like a single jump into the cloud. It's a migration, a lot of different workloads, a lot of different divisions of these companies. So it's sort of a continuum, and so different companies are at different stages of their migration and adoption of the cloud all over different parts of the business, so I think the hybrid story is really meeting that need. You have some divisions that are going to jump right into server lists and IoT, and then you have other parts of the company that maybe, you know, have a mainframe that they're still tied to, so there's always going to be some of these dependencies, and so I think hybrid story allows us to sort of address all different parts of the companies we work with. >> So what are the factors then? If I'm looking at, you know, a hybrid cloud solution, how do you help people decide what to put where? Because, you know, you got it on prem, it becomes, you know, a heave, right? To move some things over, and so, could be easier to I guess, take the lightest lift and go from there, but that's not necessarily the best route to go, so how do you help people with that kind of decision? >> Yeah, I mean, we believe in the fullness of time that customers will eventually move everything to the cloud but, you know, in the meantime, like I said, it's going to be a multiyear journey for a lot of these big customers. So like if you take, you know, a Liberty Mutual or a Comcast, these are very large companies, and we work with them to find teams and workloads within, and that comes down to people a lot of the time. You know, different teams may be at a different point of sort of agility in terms of DevOps, and if they're able to adapt their software. If their software runs on x86 infrastructure and if they're already using CICD for example and if they're used to containers, then they're going to be good candidates. So I always look to the people and then the products and then decide what they're going to migrate in that order. >> Yeah, and I would say that, you know, there's a lot of big enterprises that are looking to shut down data centers and they've already made a decision to fundamentally move infrastructure to AWS for example, right? And a lot of times we'll be brought in after the fact if you will, to deliver that developer experience on top of an already made, fundamentally an outsourcing decision, so all the reasons, you know, cost, complexity, flexible finances, consumption-based pricing, a lot of that kind of substrate decision has already been made, and we're generally coming in and saying, okay, now let's look at the application architecture. Are there things like latency and/or regulatory requirements that would require you to keep this on prem versus moving completely to the public cloud? Are there services? So, you know, could you move off of legacy middleware for example, on prem, and take advantage of, you know, refactoring and moving applications into the public cloud to improve your cost structure there? There's a myriad of issues. I think we would generally agree. A lot of times we get guidance from our customers in their respective market segment as to what's most important to them. >> So looking ahead trying to sketch out the vision of what we're going to see in the future, what do you think that customers are going to be asking for you, next year, two years out? >> Well, I think we've had a great reception for a lot of the templates and the automation that we've co-engineered. You know, Nick was talking about a lot of the co-engineering. So we have something called the AWS Quick Starts that allow you to deploy Pivotal Cloud Foundry really quickly, and so we've had really good reception from customers. >> Yep. >> Like, things that we can make it easier for them to deploy Pivotal and just sort of explore using AWS. We're going to double down on those efforts. More service brokers, more Quick Starts, more Automation more self-service for customers to they can get started with pivotal, you know, quickly. >> Yeah, and I'd add we're also, we support a product we launched about three quarters ago, Pivotal Container Service, on AWS, and so I think we'll see by virtue of the partnership with VMware, a lot more customer demand to run PKS, you know, on AWS, on Outposts, on VM cloud for AWS, and all the variants of the VMware and Amazon partnership as well. >> Yeah, like you said, meeting customers where they are. >> That's right, yeah. >> Well you're about to meet Cisco >> (laughs) that's right. >> So, good luck with that, and I'm sure you're going to get a very positive earful, which is always a good thing and continue that great work with them. Gentlemen, thanks for being with us. >> Thanks for having us. >> Appreciate the time. >> Thank you. >> Back with more AWS re:Invent. We're live here in Las Vegas at the Sands expo, and you're watching theCUBE.

>> Live, from Las Vegas, it's theCUBE, covering AWS re:Invent, 2018 brought to you by Amazon Web Services, Intel, and their ecosystem partners. >> Well, good morning. Welcome back, or good afternoon for that matter, if you're watching out on the East Coast. Good to have you have here on theCUBE as we continue our coverage here in Las Vegas. We're at the Sands Expo, Hall D to be exact, one of seven sites that are hosting the AWS re:Invent John Wallace here with Justin Warren. We're now joined by Ankur Shah, who is the vice president of Products, a public cloud security, Palo Alto Networks, and, Ankur, good to see you this morning. >> Yeah, happy to be here. >> Thank you for being with us. And Richard Wise, who is the cloud security engineer, or a cloud security engineer at Robert Half. Good morning to you, Richard. >> Good morning. >> Well, first off, let's tell us about Robert Half. So, you're a recruiting firm in a partnership with Palo Alto, but fill in a few more blanks for folks at home who might not know exactly what you do. >> Sure, we're a staffing and recruiting firm. We have offices worldwide. We have roughly 15,000 full-time employees. We also have many, many temporary employees, and, of course, we do recruiting. Many people I've met here at the conference, in fact, got their first job or one job in the past through Robert Half. And we also-- >> That's makes you a really popular guy-- >> Yes. when the show closes. >> And we also have Protiviti, our prestigious consulting arm. >> Okay, so now, about your partnership. How did you find Palo Alto, or how did Palo Alto find you? And talk about maybe that relationship, how it's developed and where it stands today. What are they doing for you? >> Sure, well, we found Palo Alto about two years ago. We're about seven years into our cloud journey, but it became very clear at a point in time that we needed to get a better handle on how we were managing and securing it. We were doing all the right things but we didn't have the visibility we needed, so we brought in Evident to do that. Also, compliance is very important to us, and the tools allowed us to ensure that we were conforming to all of the compliance standards that we needed to. >> So, maybe Ankur, you can get us in here. Explain how did this partnership get started? >> Yeah, so Robert Half is kind of prototypical customer for us at Palo Alto Networks. Customers moving to cloud. AWS is obviously one of the biggest clouds, so all our customers are migrating, a lot of their, you know, shutting down their data centers, and moving the work loads and applications to the cloud, but as they move to the cloud, they want to make sure that they have the visibility and the security controls to make sure that they are not in the news. So, that's how the partnership started. A lot of customers, just like Robert Half, starts with kind of, you know, I'd like to get a visibility into what's happening in my cloud environment, detect advance data breeches, like cryptojacking, stolen access keys, things of that nature, so that's how we kind of started this partnership. We've been kind of helping them kind of move more and more applications and more and more workloads in their AWS environments, and it's been a really amazing partnership. We've gotten some amazing feedback from them that has helped mature the product over the years. >> What's one of the more surprising things that you've noticed as part of this journey. What's something that you didn't realize that this was going to be a benefit to this partnership, and then, once you actually had Palo Alto come in there, it's like, oh wow, this is amazing. >> Well, there were a couple of things. First off, their RQL, the RedLock Query Language, is very powerful and flexible, and let's us take our compliance and security to the next level, but was really impressed when we first started talking to RedLock and Palo Alto, even before we had purchased the product, we saw some opportunities for product improvements, suggested them, and before we purchased it, within a couple of weeks, they were there. >> Wow. >> Yeah. >> That's pretty fast of all those cycles. I mean, that's what we're here for is rapid innovation. They're trying to change things at the speed of cloud. So, how do you do that safely and securely? Maybe you can tell us how does Palo Alto help do this rapid innovation but still keep everything really secure. >> Yeah, so our DNAs, obviously, network security is where the company started. Over a year now, the company has doubled down on public cloud security, and a lot of emphasis on, sort of, securing customers' cloud environment, helping a lot of customers migrate their applications into the cloud, and from a security standpoint, we look at it from different angles. One is kind of the basic configuration management aspects, making sure that customers don't leave open s3 buckets, permissive security groups, things of that nature. Above and beyond that, we also perform network analytics, so things like triple jacking, data exploration attempts. The platform is able to detect those kinds of advanced threats. Privileged activity monitoring, and anomaly detection is another thing we do, and last but not the least, host monitoring and host security aspects. That's something we do really, really well in the cloud as well, so when you combine all of that stuff, gives customers 360 visibility, as well as security for all things in the cloud. >> I'm sorry. Richard, how hard is your job these days? (laughing) And I mean that with all due respect. We've talked a lot about complexity. We've talked a lot about speed. We've talked a lot about versatility, and high demand, and all these things. Corner office is making demands on you, right? I mean, how tough is it to be in your shoes? >> If it was easy, it wouldn't be fun. I've been working in cloud about as long as Robert Half has, about seven years, and moving into the security role, it's been an incredibly interesting challenge. Yes, it's hard. I do stay up at night on occasion worrying about, did I check this, did I check that? I'm fortunate that our management has a really good understanding of the importance of security and of cloud, and I've gotten a lot of support in my role there so, in that respect, it hasn't been too hard. >> And where is it that security, in terms of a deployment? So, you think about function, right, right? >> Yeah. >> What are we going to get done here? But is it a close second, is it a tie? Because, especially in your business, I mean, you have a lot of personal information with which you're working that you've got to protect. >> Absolutely, so, people trust us with their data. We have personal information for many, many people, and we take very seriously our responsibility to manage and protect that. One of the things that we've done with Palo Alto's tools is ensuring that we're compliant with all of the various standards like ISO 27001, and compliance is kind of like brushing your teeth, right. Everybody needs to do it, and somebody doesn't want to be friends with somebody who doesn't brush their teeth. So, we ensure that we brush our teeth using tools like Palo Alto's. We can demonstrate to people that we're brushing our teeth. >> Right. >> With the innovation of RedLock now, we're able to take that to the next level, so we're not only brushing our teeth now, but we're also grooming our hair. >> You're technologically flossing as well, I'm sure. >> We are, we are. >> So, Ankur, I think that makes you the dentist of cloud security. (laughing) >> So, you've got people brushing their teeth, they're flossing. What comes next? What should they be looking at? Should they be going beyond just hygiene factors, and is there something they can do that's more than just brushing their teeth? >> Yeah, so I touched upon some of those areas. So, I think it all starts with the basic hygiene that we've talked about it, right. So, you got to do it. That's the, kind of, the fundamental, but the next-gen attacks are not going to be very simple, right, because the cloud fundamentally increases the attack factor, right, so the malicious actor, they're smarter, right. So, like I mentioned, things like cryptojacking, stolen access keys, a lot of the next-gen breeches are going to happen in the cloud, so customers have to constantly understand the kind of AWS services that they're adopting, understand the security implications, make sure they have the security guard rails, and like I mentioned, that once they understand that, look at it more holistically, both from, sort of, the basic hygiene perspective, as well as from network security, user activity, as well host monitoring perspective. Once they cover all of that stuff, you know, hopefully they'll have good teeth forever. (laughing) >> Strong cloud teeth. I don't think that's a phrase I wouldn't have thought I'd say until today. >> You know, we hear a lot about the cat and mouse game in security, right? You're trying to stay one step ahead of bad actors who are spending a lot of time, and a lot of resources, and a lot of energy to stay a step ahead of you. So, in today's world, how do you really win that battle? How do you predict where the next wrong turn is going to come, if you will, or where that invasion's going to try to occur, and prevent that, or are you in a prophylactic state all the time where it's about seeing where that action's going, and then trying to stop it once you've learned of it? See what I mean? It's a conundrum that I think you find yourself in. >> You know, I think 90% of the problems that happen where bad actors get hold of your sensitive data is because of common, silly mistakes. So, making sure that there is a user training across the board, not just security teams. Now, DevOps teams have to be part of the equation as well. They need to be trained, and coached, and understanding the security implications of their day-to-day operations. Once you train the users, you'll find that a lot of these problems will go away because most of these actors are using simple techniques to get into the customer's cloud environment because those mistakes are being made. So, start with the user training. Obviously, you need third party tooling and technologies like Palo Alto Networks to make sure you have that security guard rails all the time. Beyond that, you know, you just have to hire a lot of smart people like Richard just to insure that you're ahead of the game, thinking two steps in advance, yeah. >> It's about locking the door. >> Yeah. >> Yeah, and I want to touch on a couple of the things that Ankur said. He talked about building security into DevOps. So, there's this concept we call shifting left where you're trying to build security more upfront into the development and deployment process before you even get into the wild, and that's something Palo Alto is helping us with. The other thing is, we cannot hire enough people to keep up with the pace at which we're scaling our cloud environments, so we need tooling and automation like RedLock in order to ensure that we can get visibility and control on this vast set of resources with just a small number of people. >> Yeah. >> So necessity driving invention in that case, right? >> Yes. >> You need it. Well, gentlemen, thanks for the time. We appreciate the conversation. I feel like I need to go brush or floss. (laughing) >> Yeah, thanks for having us. >> Very self-conscious all of a sudden, but thank you both. >> Thanks for having us. >> Brilliant discussion. Back with more from AWS re:Invent. You're watching theCUBE here in Las Vegas. (energetic electronic music)