>> Narrator: From theCUBE studios in Palo Alto in Boston, connecting with thought leaders all around the world. This is a CUBE conversation. >> As you know by now, Jeff Bezos, CEO of Amazon, is stepping aside from his CEO role and AWS CEO, Andy Jassy, is being promoted to head all of Amazon. Bezos, of course, is going to remain executive chairman. Now, 15 years ago, next month, Amazon launched it's simple storage service, which was the first modern cloud offering. And the man who wrote the business plan for AWS, was Andy Jassy, and he's navigated the meteoric rise and disruption that has seen AWS grow into a $45 billion company that draws off the vast majority of Amazon's operating profits. No one in the media has covered Jassy more intimately and closely than John Furrier, the founder of SiliconANGLE. And John joins us today to help us understand on theCUBE this move and what we can expect from Jassy in his new role, and importantly what it means for AWS. John, thanks for taking the time to speak with us. >> Hey, great day. Great to see you as always, we've done a lot of interviews together over the years and we're on our 11th year with theCUBE and SiliconANGLE. But I got to be excited too, that we're simulcasters on Clubhouse, which is kind of cool. Love Clubhouse but not since the, in December. It's awesome. It's like Cube radio. It's like, so this is a Cube talk. So we opened up a Clubhouse room while we're filming this. We'll do more live hits in studio and syndicate the Clubhouse and then take questions after. This is a huge digital transformation moment. I'm part of the digital transformation club on Clubhouse which has almost 5,000 followers at the moment and also has like 500 members. So if you're not on Clubhouse, yet, if you have an iPhone go check it out and join the digital transformation club. Android users you'll have to wait until that app is done but it's really a great club. And Jeremiah Owyang is also doing a lot of stuff on digital transformation. >> Or you can just buy an iPhone and get in. >> Yeah, that's what people are doing. I can see all the influences are on there but to me, the digital transformation, it's always been kind of a cliche, the consumerization of IT, information technology. This has been the boring world of the enterprise over the past, 20 years ago. Enterprise right now is super hot because there's no distinction between enterprise and society. And that's clearly the, because of the rise of cloud computing and the rise of Amazon Web Services which was a side project at AWS, at Amazon that Andy Jassy did. And it wasn't really pleasant at the beginning. It was failed. It failed a lot and it wasn't as successful as people thought in the early days. And I have a lot of stories with Andy that he told me a lot of the inside baseball and we'll share that here today. But we started covering Amazon since the beginning. I was as an entrepreneur. I used it when it came out and a huge fan of them as a company because they just got a superior product and they have always had been but it was very misunderstood from the beginning. And now everyone's calling it the most important thing. And Andy now is becoming Andy Jassy, the most important executive in the world. >> So let's get it to the, I mean, look at, you said to me over holidays, you thought this might have something like this could happen. And you said, Jassy is probably in line to get this. So, tell us, what can you tell us about Jassy? Why is he qualified for this job? What do you think he brings to the table? >> Well, the thing that I know about Amazon everyone's been following the Amazon news is, Jeff Bezos has a lot of personal turmoil. They had his marriage fail. They had some issues with the smear campaigns and all this stuff going on, the run-ins with Donald Trump, he bought the Washington post. He's got a lot of other endeavors outside of Amazon cause he's the second richest man in the world competing with Elon Musk at Space X versus Blue Origin. So the guy's a billionaire. So Amazon is his baby and he's been running it as best he could. He's got an executive team committee they called the S team. He's been grooming people in the company and that's just been his mode. And the rise of AWS and the business performance that we've been documenting on SiliconANGLE and theCUBE, it's just been absolutely changing the game on Amazon as a company. So clearly Amazon Web Services become a driving force of the new Amazon that's emerging. And obviously they've got all their retail business and they got the gaming challenges and they got the studios and the other diversified stuff. So Jassy is just, he's just one of those guys. He's just been an Amazonian from day one. He came out of Harvard business school, drove across the country, very similar story to Jeff Bezos. He did that in 1997 and him and Jeff had been collaborating and Jeff tapped him to be his shadow, they call it, which is basically technical assistance and an heir apparent and groomed him. And then that's how it is. Jassy is not a climber as they call it in corporate America. He's not a person who is looking for a political gain. He's not a territory taker, but he's a micromanager. He loves details and he likes to create customer value. And that's his focus. So he's not a grandstander. In fact, he's been very low profile. Early days when we started meeting with him, he wouldn't meet with press regularly because they weren't writing the right stories. And everyone is, he didn't know he was misunderstood. So that's classic Amazon. >> So, he gave us the time, I think it was 2014 or 15 and he told us a story back then, John, you might want to share it as to how AWS got started. Why, what was the main spring Amazon's tech wasn't working that great? And Bezos said to Jassy, going to go figure out why and maybe explain how AWS was born. >> Yeah, we had, in fact, we were the first ones to get access to do his first public profile. If you go to the Google and search Andy Jassy, the trillion dollar baby, we had a post, we put out the story of AWS, Andy Jassy's trillion dollar baby. This was in early, this was January 2015, six years ago. And, we back then, we posited that this would be a trillion dollar total addressable market. Okay, people thought we were crazy but we wrote a story and he gave us a very intimate access. We did a full drill down on him and the person, the story of Amazon and that laid out essentially the beginning of the rise of AWS and Andy Jassy. So that's a good story to check out but really the key here is, is that he's always been relentless and competitive on creating value in what they call raising the bar outside Amazon. That's a term that they use. They also have another leadership principle called working backwards, which is like, go to the customer and work backwards from the customer in a very Steve Job's kind of way. And that's been kind of Jobs mentality as well at Apple that made them successful work backwards from the customer and make things easier. And that was Apple. Amazon, their philosophy was work backwards from the customer and Jassy specifically would say it many times and eliminate the undifferentiated heavy lifting. That was a key principle of what they were doing. So that was a key thesis of their entire business model. And that's the Amazonian way. Faster, cheaper, ship it faster, make it less expensive and higher value. While when you apply the Amazon shipping concept to cloud computing, it was completely disrupted. They were shipping code and services faster and that became their innovation strategy. More announcements every year, they out announced their competition by huge margin. They introduced new services faster and they're less expensive some say, but in the aggregate, they make more money but that's kind of a key thing. >> Well, when you, I was been listening to the TV today and there was a debate on whether or not, this support tends that they'll actually split the company into two. To me, I think it's just the opposite. I think it's less likely. I mean, if you think about Amazon getting into grocery or healthcare, eventually financial services or other industries and the IOT opportunity to me, what they do, John, is they bring in together the cloud, data and AI and they go attack these new industries. I would think Jassy of all people would want to keep this thing together now whether or not the government allows them to do that. But what are your thoughts? I mean, you've asked Andy this before in your personal interviews about splitting the company. What are your thoughts? >> Well, Jon Fortt at CNBC always asked the same question every year. It's almost like the standard question. I kind of laugh and I ask it now too because I liked Jon Fortt. I think he's an awesome dude. And I'll, it's just a tongue in cheek, Jassy. He won't answer the question. Amazon, Bezos and Jassy have one thing in common. They're really good at not answering questions. So if you ask the same question. They'll just say, nothing's ever, never say never, that's his classic answer to everything. Never say never. And he's always said that to you. (chuckles) Some say, he's, flip-flopped on things but he's really customer driven. For example, he said at one point, no one should ever build a data center. Okay, that was a principle. And then they come out and they have now a hybrid strategy. And I called them out on that and said, hey, what, are you flip-flopping? You said at some point, no one should have a data center. He's like, well, we looked at it differently and what we meant was is that, it should all be cloud native. Okay. So that's kind of revision, but he's cool with that. He says, hey, we'll revise based on what customers are doing. VMware working with Amazon that no one ever thought that would happen. Okay. So, VMware has some techies, Raghu, for instance, over there, super top notch. He worked with Jassy, directly in his team Sanjay Poonen when they went to business school together, they cut a deal. And now Amazon essentially saved VMware, in my opinion. And Pat Gelsinger drove that deal. Now, Pat Gelsinger, CEO, Intel, and Pat told me that directly in candid conversation off theCUBE, he said, hey, we have to make a decision either we're going to be in cloud or we're not going to be in cloud, we will partner. And I'll see, he was Intel. He understood the Intel inside mentality. So that's good for VMware. So Jassy does these kinds of deals. He's not afraid he's got a good stomach for business and a relentless competitor. >> So, how do you think as you mentioned Jassy is a micromanager. He gets deep into the technology. Anybody who's seen his two hour, three hour keynotes. No, he has a really fine grasp of the technology across the entire stack. How do you think John, he will approach things like antitrust, the big tech lash of the unionization of the workforce at Amazon? How do you think Jassy will approach that? >> Well, I think one of the things that emerges Jassy, first of all, he's a huge sports fan. And many people don't know that but he's also progressive person. He's very progressive politically. He's been on the record and off the record saying things like, obviously, literacy has been big on, he's been on basically unrepresented minorities, pushing for that, and certainly cloud computing in tech, women in tech, he's been a big proponent. He's been a big supporter of Teresa Carlson. Who's been rising star at Amazon. People don't know who Teresa Carlson is and they should check out her. She's become one of the biggest leaders inside Amazon she's turned around public sector from the beginning. She ran that business, she's a global star. He's been a great leader and he's been getting, forget he's a micromanager, he's on top of the details. I mean, the word is, and nothing gets approved without Andy, Andy seeing it. But he's been progressive. He's been an Amazon original as they call it internally. He's progressive, he's got the business acumen but he's perfect for this pragmatic conversation that needs to happen. And again, because he's so technically strong having a CEO that's that proficient is going to give Amazon an advantage when they have to go in and change how DC works, for instance, or how the government geopolitical landscape works, because Amazon is now a global company with regions all over the place. So, I think he's pragmatic, he's open to listening and changing. I think that's a huge quality >> Well, when you think of this, just to set the context here for those who may not know, I mean, Amazon started as I said back in 2006 in March with simple storage service that later that year they announced EC2 which is their compute platform. And that was the majority of their business, is still a very large portion of their business but Amazon, our estimates are that in 2020, Amazon did 45 billion, 45.4 billion in revenue. That's actually an Amazon reported number. And just to give you a context, Azure about 26 billion GCP, Google about 6 billion. So you're talking about an industry that Amazon created. That's now $78 billion and Amazon at 45 billion. John they're growing at 30% annually. So it's just a massive growth engine. And then another story Jassy told us, is they, he and Jeff and the team talked early on about whether or not they should just sort of do an experiment, do a little POC, dip their toe in and they decided to go for it. Let's go big or go home as Michael Dell has said to us many times, I mean, pretty astounding. >> Yeah. One of the things about Jassy that people should know about, I think there's some compelling relative to the newest ascension to the CEO of Amazon, is that he's not afraid to do new things. For instance, I'll give you an example. The Amazon Web Services re-invent their annual conference grew to being thousands and thousands of people. And they would have a traditional after party. They called a replay, they'd have a band like every tech conference and their conference became so big that essentially, it was like setting up a live concert. So they were spending millions of dollars to set up basically a one night concert and they'd bring in great, great artists. So he said, hey, what's been all this cash? Why don't we just have a festival? So they did a thing called Intersect. They got LA involved from creatives and they basically built a weekend festival in the back end of re-invent. This was when real life was, before COVID and they turned into an opportunity because that's the way they think. They like to look at the resources, hey, we're already all in on this, why don't we just keep it for the weekend and charge some tickets and have a good time. He's not afraid to take chances on the product side. He'll go in and take a chance on a new market. That comes from directly from Bezos. They try stuff. They don't mind failing but they put a tight leash on measurement. They work backwards from the customer and they are not afraid to take chances. So, that's going to board well for him as he tries to figure out how Amazon navigates the contention on the political side when they get challenged for their dominance. And I think he's going to have to apply that pragmatic experimentation to new business models. >> So John I want you to take on AWS. I mean, despite the large numbers, I talked about 30% growth, Azure is growing at over 50% a year, GCP at 83%. So despite the large numbers and big growth the growth rates are slowing. Everybody knows that, we've reported it extensively. So the incoming CEO of Amazon Web Services has a TAM expansion challenge. And at some point they've got to decide, okay, how do we keep this growth engine? So, do you have any thoughts as to who might be the next CEO and what are some of their challenges as you see it? >> Well, Amazon is a real product centric company. So it's going to be very interesting to see who they go with here. Obviously they've been grooming a lot of people. There's been some turnover. You had some really strong executives recently leave, Jeff Wilkes, who was the CEO of the retail business. He retired a couple of months ago, formerly announced I think recently, he was probably in line. You had Mike Clayville, is now the chief revenue officer of Stripe. He ran all commercial business, Teresa Carlson stepped up to his role as well as running public sector. Again, she got more power. You have Matt Garman who ran the EC2 business, Stanford grad, great guy, super strong on the product side. He's now running all commercial sales and marketing. And he's also on the, was on Bezos' S team, that's the executive kind of team. Peter DeSantis is also on that S team. He runs all infrastructure. He took over for James Hamilton, who was the genius behind all the data center work that they've done and all the chip design stuff that they've innovated on. So there's so much technical innovation going on. I think you still going to see a leadership probably come from, I would say Matt Garman, in my opinion is the lead dog at this point, he's the lead horse. You could have an outside person come in depending upon how, who might be available. And that would probably come from an Andy Jassy network because he's a real fierce competitor but he's also a loyalist and he likes trust. So if someone comes in from the outside, it's going to be someone maybe he trusts. And then the other wildcards are like Teresa Carlson. Like I said, she is a great woman in tech who's done amazing work. I've profiled her many times. We've interviewed her many times. She took that public sector business with Amazon and changed the game completely. Outside the Jedi contract, she was in competitive for, had the big Trump showdown with the Jedi, with the department of defense. Had the CIA cloud. Amazon set the standard on public sector and that's directly the result of Teresa Carlson. But she's in the field, she's not a product person, she's kind of running that group. So Amazon has that product field kind of structure. So we'll see how they handle that. But those are the top three I think are going to be in line. >> So the obvious question that people always ask and it is a big change like this is, okay, in this case, what is Jassy going to bring in? And what's going to change? Maybe the flip side question is somewhat more interesting. What's not going to change in your view? Jassy has been there since nearly the beginning. What are some of the fundamental tenets that he's, that are fossilized, that won't change, do you think? >> I think he's, I think what's not going to change is Amazon, is going to continue to grow and develop their platform business and enable more SaaS players. That's a little bit different than what Microsoft's doing. They're more SaaS oriented, Office 365 is becoming their biggest application in terms of revenue on Microsoft side. So Amazon is going to still have to compete and enable more ecosystem partners. I think what's not going to change is that Bezos is still going to be in charge because executive chairman is just a code word for "not an active CEO." So in the corporate governance world when you have an executive chairman, that's essentially the person still in charge. And so he'll be in charge, will still be the boss of Andy Jassy and Jassy will be running all of Amazon. So I think that's going to be a little bit the same, but Jassy is going to be more in charge. I think you'll see a team change over, whether you're going to see some new management come in, Andy's management team will expand, I think Amazon will stay the same, Amazon Web Services. >> So John, last night, I was just making some notes about notable transitions in the history of the tech business, Gerstner to Palmisano, Gates to Ballmer, and then Ballmer to Nadella. One that you were close to, David Packard to John Young and then John Young to Lew Platt at the old company. Ellison to Safra and Mark, Jobs to Cook. We talked about Larry Page to Sundar Pichai. So how do you see this? And you've talked to, I remember when you interviewed John Chambers, he said, there is no rite of passage, East coast mini-computer companies, Edson de Castro, Ken Olsen, An Wang. These were executives who wouldn't let go. So it's of interesting to juxtapose that with the modern day executive. How do you see this fitting in to some of those epic transitions that I just mentioned? >> I think a lot of people are surprised at Jeff Bezos', even stepping down. I think he's just been such the face of Amazon. I think some of the poll numbers that people are doing on Twitter, people don't think it's going to make a big difference because he's kind of been that, leader hand on the wheel, but it's been its own ship now, kind of. And so depending on who's at the helm, it will be different. I think the Amazon choice of Andy wasn't obvious. And I think a lot of people were asking the question who was Andy Jassy and that's why we're doing this. And we're going to be doing more features on the Andy Jassy. We got a tons, tons of content that we've we've had shipped, original content with them. We'll share more of those key soundbites and who he is. I think a lot of people scratching their head like, why Andy Jassy? It's not obvious to the outsiders who don't know cloud computing. If you're in the competing business, in the digital transformation side, everyone knows about Amazon Web Services. Has been the most successful company, in my opinion, since I could remember at many levels just the way they've completely dominated the business and how they change others to be dominant. So, I mean, they've made Microsoft change, it made Google change and even then he's a leader that accepts conversations. Other companies, their CEOs hide behind their PR wall and they don't talk to people. They won't come on Clubhouse. They won't talk to the press. They hide behind their PR and they feed them, the media. Jassy is not afraid to talk to reporters. He's not afraid to talk to people, but he doesn't like people who don't know what they're talking about. So he doesn't suffer fools. So, you got to have your shit together to talk to Jassy. That's really the way it is. And that's, and he'll give you mind share, like he'll answer any question except for the ones that are too tough for him to answer. Like, are you, is facial recognition bad or good? Are you going to spin out AWS? I mean these are the hard questions and he's got a great team. He's got Jay Carney, former Obama press secretary working for him. He's been a great leader. So I'm really bullish on, is a good choice. >> We're going to jump into the Clubhouse here and open it up shortly. John, the last question for you is competition. Amazon as a company and even Jassy specifically I always talk about how they don't really focus on the competition, they focus on the customer but we know that just observing these folks Bezos is very competitive individual. Jassy, I mean, you know him better than I, very competitive individual. So, and he's, Jassy has been known to call out Oracle. Of course it was in response to Larry Ellison's jabs at Amazon regarding database. But, but how do you see that? Do you see that changing at all? I mean, will Amazon get more publicly competitive or they stick to their knitting, you think? >> You know this is going to sound kind of a weird analogy. And I know there's a lot of hero worshiping on Elon Musk but Elon Musk and Andy Jassy have a lot of similarities in the sense of their brilliance. They got both a brilliant people, different kinds of backgrounds. Obviously, they're running different things. They both are builders, right? If you were listening to Elon Musk on Clubhouse the other night, what was really striking was not only the magic of how it was all orchestrated and what he did and how he interviewed Robin Hood. He basically is about building stuff. And he was asked questions like, what advice do you give startups? He's like, if you need advice you shouldn't be doing startups. That's the kind of mentality that Jassy has, which is, it's not easy. It's not for the faint of heart, but Elon Musk is a builder. Jassy builds, he likes to build stuff, right? And so you look at all the things that he's done with AWS, it's been about enabling people to be successful with the tools that they need, adding more services, creating things that are lower price point. If you're an entrepreneur and you're over the age of 30, you know about AWS because you know what, it's cheaper to start a business on Amazon Web Services than buying servers and everyone knows that. If you're under the age of 25, you might not know 50 grand to a hundred thousand just to start something. Today you get your credit card down, you're up and running and you can get Clubhouses up and running all day long. So the next Clubhouse will be on Amazon or a cloud technology. And that's because of Andy Jassy right? So this is a significant executive and he continue, will bring that mindset of building. So, I think the digital transformation, we're in the digital engine club, we're going to see a complete revolution of a new generation. And I think having a new leader like Andy Jassy will enable in my opinion next generation talent, whether that's media and technology convergence, media technology and art convergence and the fact that he digs music, he digs sports, he digs tech, he digs media, it's going to be very interesting to see, I think he's well-poised to be, and he's soft-spoken, he doesn't want the glamorous press. He doesn't want the puff pieces. He just wants to do what he does and he puts his game do the talking. >> Talking about advice at startups. Just a quick aside. I remember, John, you and I when we were interviewing Scott McNealy former CEO of Sun Microsystems. And you asked him advice for startups. He said, move out of California. It's kind of tongue in cheek. I heard this morning that there's a proposal to tax the multi-billionaires of 1% annually not just the one-time tax. And so Jeff Bezos of course, has a ranch in Texas, no tax there, but places all over. >> You see I don't know. >> But I don't see Amazon leaving Seattle anytime soon, nor Jassy. >> Jeremiah Owyang did a Clubhouse on California. And the basic sentiment is that, it's California is not going away. I mean, come on. People got to just get real. I think it's a fad. Yeah. This has benefits with remote working, no doubt, but people will stay here in California, the network affects beautiful. I think Silicon Valley is going to continue to be relevant. It's just going to syndicate differently. And I think other hubs like Seattle and around the world will be integrated through remote work and I think it's going to be much more of a democratizing effect, not a win lose. So that to me is a huge shift. And look at Amazon, look at Amazon and Microsoft. It's the cloud cities, so people call Seattle. You've got Google down here and they're making waves but still, all good stuff. >> Well John, thanks so much. Let's let's wrap and let's jump into the Clubhouse and hear from others. Thanks so much for coming on, back on theCUBE. And many times we, you and I've done this really. It was a pleasure having you. Thanks for your perspectives. And thank you for watching everybody, this is Dave Vellante for theCUBE. We'll see you next time. (soft ambient music)

>>from around the globe. It's the Cube with digital coverage of HP Green Lake day made possible by Hewlett Packard Enterprise. Okay, we're not gonna dive right into some of the news and get into the Green Lake Announcement details. And with me to do that is Keith White is the senior vice president and general manager for Green Lake Cloud Services and Hewlett Packard Enterprise. Keith, thanks for your time. Great to see you. >>Hey, thanks so much for having me. I'm really excited to be here. >>You're welcome. And so listen, before we get into the hard news, can you give us an update on just Green Lake and the business? How's it going? >>You bet. No, it's fantastic. And thanks, you know, for the opportunity again. And hey, I hope everyone's at home staying safe and healthy. It's been a great year for HP Green Lake. There's a ton of momentum that we're seeing in the market place. Uh, we've booked over $4 billion of total contract value to date, and that's over 1000 customers worldwide, and frankly, it's worldwide. It's in 50 50 different countries, and this is a variety of solutions. Variety of workloads. So really just tons of momentum. But it's not just about accelerating the current momentum. It's really about listening to our customers, staying ahead of their demands, delivering more value to them and really executing on the HB Green Lake. Promise. >>Great. Thanks for that and really great detail. Congratulations on the progress, but I know you're not done. So let's let's get to the news. What do people need to know? >>Awesome. Yeah, you know, there's three things that we want to share with you today. So first is all about it's computing. So I could go into some details on that were actually delivering new industry work clothes, which I think will be exciting for a lot of the major industries that are out there. And then we're expanding RHP capabilities just to make things easier and more effective. So first off, you know, we're excited to announce today, um, acceleration of mainstream as adoption for high performance computing through HP Green Lake. And you know, in essence, what we're really excited about is this whole idea of it's a. It's a unique opportunity to write customers with the power of an agile, elastic paper use cloud experience with H. P s market. See systems. So pretty soon any enterprise will be able to tackle their most demanding compute and did intensive workloads, power, artificial intelligence and machine learning initiatives toe provide better business insights and outcomes and again providing things like faster time to incite and accelerated innovation. So today's news is really, really gonna help speed up deployment of HPC projects by 75% and reduced TCO by upto 40% for customers. >>That's awesome. Excited to learn more about the HPC piece, especially. So tell us what's really different about the news today From your perspective. >>No, that's that's a great thing. And the idea is to really help customers with their business outcomes, from building safer cars to improving their manufacturing lines with sustainable materials. Advancing discovery for drug treatment, especially in this time of co vid or making critical millisecond decisions for those finance markets. So you'll see a lot of benefits and a lot of differentiation for customers in a variety of different scenarios and industries. >>Yeah, so I wonder if you could talk a little bit mawr about specifically, you know exactly what's new. Can you unpack some of that for us? >>You bet. Well, what's key is that any enterprise will be able to run their modeling and simulation work clothes in a fully managed because we manage everything for them pre bundled. So we'll give folks this idea of small, medium and large H p e c h piece services to operate in any data center or in a cold a location. These were close air, almost impossible to move to the public cloud because the data so large or it needs to be close by for Leighton see issues. Oftentimes, people have concerns about I p protection or applications and how they run within that that local environment. So if customers are betting their business on this insight and analytics, which many of them are, they need business, critical performance and experts to help them with implementation and migration as well as they want to see resiliency. >>So is this a do it yourself model? In other words, you know the customers have toe manage it on their own. Or how are you helping there? >>No, it's a great question. So the fantastic thing about HP Green Lake is that we manage it all for the customer. And so, in essence, they don't have to worry about anything on the back end, we can flow that we manage capacity. We manage performance, we manage updates and all of those types of things. So we really make it. Make it super simple. And, you know, we're offering these bundled solutions featuring RHP Apollo systems that are purpose built for running things like modeling and simulation workloads. Um, and again, because it's it's Green Lake. And because it's cloud services, this provides itself. Service provides automation. And, you know, customers can actually, um, manage however they want to. We can do it all for them. They could do some on their own. It's really super easy, and it's really up to them on how they want to manage that system. >>What about analytics? You know, you had a lot of people want to dig deeper into the data. How are you supporting that? >>Yeah, Analytics is key. And so one of the best things about this HPC implementation is that we provide unopened platform so customers have the ability to leverage whatever tools they want to do for analytics. They can manage whatever systems they want. Want to pull data from so they really have a ton of flexibility. But the key is because it's HP Green Lake, and because it's HP es market leading HPC systems, they get the fastest they get the it all managed for them. They only pay for what they use, so they don't need to write a huge check for a large up front. And frankly, they get the best of all those worlds together in order to come up with things that matter to them, which is that true business outcome, True Analytics s so that they could make the decisions they need to run their business. >>Yeah, that's awesome. You guys clearly making some good progress here? Actually, I see it really is a game changer for the types of customers that you described. I mean, particularly those folks that you like. You said You think they can't move stuff into the cloud. They've got to stay on Prem. But they want that cloud experience. I mean, that's that's really exciting. We're gonna have you back in a few minutes to talk about the Green Lake Cloud services and in some of the new industry platforms that you see evolving >>awesome. Thanks so much. I look forward to it. >>Yeah, us too. So Okay, right now we're gonna check out the conversation that I had earlier with Pete Ungaro and Addison Snell on HPC. Let's watch welcome everybody to the spotlight session here green. Late day, We're gonna dig into high performance computing. Let me first bring in Pete Ungaro, Who's the GM for HPC and Mission Critical solutions, that Hewlett Packard Enterprise. And then we're gonna pivot Addison Snell, who is the CEO of research firm Intersect 3. 60. So, Pete, starting with you Welcome. And really a pleasure to have you here. I want to first start off by asking you what is the key trends that you see in the HPC and supercomputing space? And I really appreciate if you could talk about how customer consumption patterns are changing. >>Yeah, I appreciate that, David, and thanks for having me. You know, I think the biggest thing that we're seeing is just the massive growth of data. And as we get larger and larger data sets larger and larger models happen, and we're having more and more new ways to compute on that data. So new algorithms like A. I would be a great example of that. And as people are starting to see this, especially they're going through a digital transformations. You know, more and more people I believe can take advantage of HPC but maybe don't know how and don't know how to get started on DSO. They're looking for how to get going into this environment and many customers that are longtime HBC customers, you know, just consume it on their own data centers. They have that capability, but many don't and so they're looking at. How can I do this? Do I need to build up that capability myself? Do I go to the cloud? What about my data and where that resides. So there's a lot of things that are going into thinking through How do I start to take advantage of this new infrastructure? >>Excellent. I mean, we all know HPC workloads. You're talking about supporting research and discovery for some of the toughest and most complex problems, particularly those that affecting society. So I'm interested in your thoughts on how you see Green Lake helping in these endeavors specifically, >>Yeah, One of the most exciting things about HPC is just the impact that it has, you know, everywhere from, you know, building safer cars and airplanes. Thio looking at climate change, uh, to, you know, finding new vaccines for things like Covic that we're all dealing with right now. So one of the biggest things is how do we take advantage event and use that to, you know, benefit society overall. And as we think about implementing HPC, you know, how do we get started? And then how do we grow and scale as we get more and more capability? So that's the biggest things that we're seeing on that front. >>Yes. Okay, So just about a year ago, you guys launched the Green Lake Initiative and the whole, you know, complete focus on as a service. So I'm curious as to how the new Green Lake services the HPC services specifically as it relates to Greenlee. How do they fit in the H. P s overall high performance computing portfolio and the strategy? >>Yeah, great question. You know, Green Lake is a new consumption model for eso. It's a very exciting We keep our entire HPC portfolio that we have today, but extend it with Green Lake and offer customers you know, expanded consumption choices. So, you know, customers that potentially are dealing with the growth of their data or they're moving toe digital transformation applications they can use green light just easily scale up from workstations toe, you know, manage their system costs or operational costs, or or if they don't have staff to expand their environment. Green Light provides all of that in a manage infrastructure for them. So if they're going from like a pilot environment up into a production environment over time, Green Lake enables them to do that very simply and easily without having toe have all that internal infrastructure people, computer data centers, etcetera. Green Lake provides all that for them so they can have a turnkey solution for HBC. >>So a lot easier entry strategies. A key key word that you use. There was choice, though. So basically you're providing optionality. You're not necessarily forcing them into a particular model. Is that correct? >>Yeah, 100%. Dave. What we want to do is just expand the choices so customers can buy a new choir and use that technology to their advantage is whether they're large or small. Whether they're you know, a startup or Fortune 500 company, whether they have their own data centers or they wanna, you know, use a Coehlo facility whether they have their own staff or not, we want to just provide them the opportunity to take advantage of this leading edge resource. >>Very interesting, Pete. It really appreciate the perspective that you guys have bring into the market. I mean, it seems to me it's gonna really accelerate broader adoption of high performance computing, toe the masses, really giving them an easier entry point I want to bring in now. Addison Snell to the discussion. Addison. He's the CEO is, I said of Intersect 3 60 which, in my view, is the world's leading market research company focused on HPC. Addison, you've been following the space for a while. You're an expert. You've seen a lot of changes over the years. What do you see is the critical aspect in the market, specifically as it relates toward this as a service delivery that we were just discussing with Pete and I wonder if you could sort of work in their the benefits in terms of, in your view, how it's gonna affect HPC usage broadly. Yeah, Good morning, David. Thanks very much for having me, Pete. It's great to see you again. So we've been tracking ah lot of these utility computing models in high performance computing for years, particularly as most of the usage by revenue is actually by commercial endeavors. Using high performance computing for their R and D and engineering projects and the like. And cloud computing has been a major portion of that and has the highest growth rate in the market right now, where we're seeing this double digit growth that accounted for about $1.4 billion of the high performance computing industry last year. But the bigger trend on which makes Green like really interesting is that we saw an additional about a billion dollars worth of spending outside what was directly measured in the cloud portion of the market in in areas that we deemed to be cloud like, which were as a service types of contracts that were still utility computing. But they might be under a software as a service portion of the budget under software or some other managed services type of contract that the user wasn't reported directly is cloud, but it was certainly influenced by utility computing, and I think that's gonna be a really dominant portion of the market going forward. And when we look at growth rate and where the market's been evolving, so that's interesting. I mean, basically, you're saying this, you know, the utility model is not brand new. We've seen that for years. Cloud was obviously a catalyst that gave that a boost. What is new, you're saying is and I'll say it this way. I'd love to get your independent perspective on this is so The definition of cloud is expanding where it's you know, people always say it's not a place, it's an experience and I couldn't agree more. But I wonder if you could give us your independent perspective on that, both on the thoughts of what I just said. But also, how would you rate H. P. E s position in this market? Well, you're right, absolutely, that the definition of cloud is expanding, and that's a challenge when we run our surveys that we try to be pedantic in a sense and define exactly what we're talking about. And that's how we're able to measure both the direct usage of ah, typical public cloud, but also ah more flexible notion off as a service. Now you asked about H P E. In particular, And that's extremely relevant not only with Green Lake but with their broader presence in high performance computing. H P E is the number one provider of systems for high performance computing worldwide, and that's largely based on the breath of H. P s offerings, in addition to their performance in various segments. So picking up a lot of the commercial market with their HP apology and 10 plus, they hit a lot of big memory configurations with Superdome flex and scale up to some of the most powerful supercomputers in the world with the HP Cray X platforms that go into some of the leading national labs. Now, Green Light gives them an opportunity to offer this kind of flexibility to customers rather than committing all it wants to a particular purchase price. But if you want to do position those on a utility computing basis pay for them as a service without committing to ah, particular public cloud. I think that's an interesting role for Green Lake to play in the market. Yeah, it's interesting. I mean earlier this year, we celebrated Exa scale Day with support from HP, and it really is all about a community and an ecosystem is a lot of camaraderie going on in the space that you guys are deep into, Addison says. We could wrap. What should observers expect in this HPC market in this space over the next a few years? Yeah, that's a great question. What to expect because of 2020 has taught us anything. It's the hazards of forecasting where we think the market is going. When we put out a market forecast, we tend not to look at huge things like unexpected pandemics or wars. But it's relevant to the topic here because, as I said, we were already forecasting Cloud and as a service, models growing. Any time you get into uncertainty, where it becomes less easy to plan for where you want to be in two years, three years, five years, that model speaks well to things that are cloud or as a service to do very well, flexibly, and therefore, when we look at the market and plan out where we think it is in 2020 2021 anything that accelerates uncertainty actually is going. Thio increase the need for something like Green Lake or and as a service or cloud type of environment. So we're expecting those sorts of deployments to come in over and above where we were already previously expected them in 2020 2021. Because as a service deals well with uncertainty. And that's just the world we've been in recently. I think there's a great comments and in a really good framework. And we've seen this with the pandemic, the pace at which the technology industry in particular, of course, HP specifically have responded to support that your point about agility and flexibility being crucial. And I'll go back toe something earlier that Pete said around the data, the sooner we can get to the data to analyze things, whether it's compressing the time to a vaccine or pivoting our business is the better off we are. So I wanna thank Pete and Addison for your perspectives today. Really great stuff, guys. Thank you. >>Yeah, Thank you. >>Alright, keep it right there from, or great insights and content you're watching green leg day. Alright, Great discussion on HPC. Now we're gonna get into some of the new industry examples and some of the case studies and new platforms. Keith HP, Green Lake It's moving forward. That's clear. You're picking up momentum with customers, but can you give us some examples of platforms for industry use cases and some specifics around that? >>You know, you bet, and actually you'll hear more details from Arwa Qadoura she leads are green like the market efforts in just a little bit. But specifically, I want to highlight some examples where we provide cloud services to help solve some of the most demanding workloads on the planet. So, first off in financial services, for example, traditional banks are facing increased competition and evolving customer expectations they need to transform so that they can reduce risk, manage cop and provided differentiated customer experience. We'll talk about a platform for Splunk that does just that. Second, in health care institutions, they face the growing list of challenges, some due to the cove in 19 Pandemic and others. Years in the making, like our aging population and rise in chronic disease, is really driving up demands, and it's straining capital budgets. These global trance create a critical need for transformation. Thio improve that patient experience and their business outcomes. Another example is in manufacturing. They're facing many challenges in order to remain competitive, right, they need to be able to identify new revenue streams run more efficiently from an operation standpoint and scale. Their resource is so you'll hear more about how we're optimizing and delivery for manufacturing with S. A P Hana and always gonna highlight a little more detail on today's news how we're delivering supercomputing through HP Green Lake It's scale and finally, how we have a robust ecosystem of partners to help enterprises easily deploy these solutions. For example, I think today you're gonna be talking to Skip Bacon from Splunk. >>Yeah, absolutely. We sure are. And some really great examples there, especially a couple industries that that stood out. I mean, financial services and health care. They're ripe for transformation and maybe disruption if if they don't move fast enough. So Keith will be coming back to you a little later today to wrap things up. So So thank you. Now, now we're gonna take a look at how HP is partnering with Splunk and how Green Lake compliments, data rich workloads. Let's watch. We're not going to dig deeper into a data oriented workload. How HP Green Lake fits into this use case and with me, a Skip Bacon vice president, product management at Splunk Skip. Good to see >>you. Good to see you as well there. >>So let's talk a little bit about Splunk. I mean, you guys are a dominant player and security and analytics and you know, it's funny, Skip, I used to comment that during the big data, the rise of big data Splunk really never positioned themselves is this big data player, and you know all that hype. But But you became kind of the leader in big data without really, even, you know, promoting it. It just happened overnight, and you're really now rapidly moving toward a subscription model. You're making some strategic moves in the M and a front. Give us your perspective on what's happening at the company and why customers are so passionate about your software. >>Sure, a great, great set up, Dave. Thanks. So, yeah, let's start with the data that's underneath big data, right? I think I think it is usual. The industry sort of seasons on a term and never stops toe. Think about what it really means. Sure, one big part of big data is your transaction and stuff, right? The things that catch generated by all of your Oracle's USC Cheops that reflect how the business actually occurred. But a much bigger part is all of your digital artifacts, all of the machine generated data that tells you the whole story about what led up to the things that actually happened right within the systems within the interactions within those systems. That's where Splunk is focused. And I think what the market is the whole is really validating is that that machine generated data those digital artifacts are a tely least is important, if not more so, than the transactional artifacts to this whole digital transformation problem right there. Critical to showing I t. How to get better developing and deploying and operating software, how to get better securing these systems, and then how to take this real time view of what the business looks like as it's executing in the software right now. And hold that up to and inform the business and close that feedback loop, right? So what is it we want to do differently digitally in order to do different better on the transformation side of the house. So I think a lot of splints. General growth is proof of the value crop and the need here for sure, as we're seeing play out specifically in the domains of ICTs he operations Dev, ops, Cyber Security, right? As well as more broadly in that in that cloak closing the business loop Splunk spin on its hair and growing our footprint overall with our customers and across many new customers, we've been on its hair with moving parts of that footprints who and as a service offering and spawn cloud. But a lot of that overall growth is really fueled by just making it simpler. Quicker, faster, cheaper, easier toe operates Plunkett scale because the data is certainly not slowing down right. There's more and more and more of it every day, more late, their potential value locked up in it. So anything that we can do and that our partners conducive to improve the cost economics to prove the agility to improve the responsiveness of these systems is huge. That that customer value crop and that's where we get so excited about what's going on with green life >>Yeah, so that makes sense. I mean, the digital businesses, a data business. And that means putting data at the core. And Splunk is obviously you keep part of that. So, as I said earlier, spunk your leader in this space, what's the deal with your HP relationship? You touched on that? What should we know about your your partnership? And what's that solution with H h p E? What's that customer Sweet spot. >>Yep. Good. All good questions. So we've been working with HP for quite a while on on a number of different fronts. This Green lake peace is the most interesting and sort of the intersection of, you know, purist intersection of both of these threads of these factories, if you will. So we've been working to take our core data platform deployed on an enterprise operator for kubernetes. Stick that a top H P s green like which is really kubernetes is a service platform and go prove performance, scalability, agility, flexibility, cost economics, starting with some of slugs, biggest customers. And we've proven, you know, alot of those things In great measure, I think the opportunity you know, the ability to vertically scale Splunk in containers that taught beefy boxes and really streamline the automation, the orchestration, the operations, all of that yields what, in the words of one of our mutual customers, literally put it as This is a transformational platform for deploying and operating spot for us so hard at work on the engineering side, hard at work on the architectural referencing, sizing, you know, capacity planning sides, and then increasing really rolling up our sleeves and taking the stuff the market together. >>Yeah, I mean, we're seeing the just the idea of cloud. The definition of cloud expanding hybrid brings in on Prem. We talked about the edge and and I really We've seen Splunk rapidly transitioning its pricing model to a subscription, you know, platform, if you will. And of course, that's what Green Lakes all about. What makes Splunk a good fit for Green Lake and vice versa? What does it mean for customers? >>Sure, So a couple different parts, I think, make make this a perfect marriage. Splunk at its core, if you're using it well, you're using it in a very iterative discovery driven kind of follow you the path to value basis that makes it a little hard to plan the infrastructure and decides these things right. We really want customers to be focused on how to get more data in how to get more value out. And if you're doing it well, those things, they're going to go up and up and up over time. You don't wanna be constrained by size and capacity planning, procurement cycles for infrastructure. So the Green Lake model, you know, customers got already deployed systems already deployed, capacity available in and as the service basis, very fast, very agile. If they need a next traunch of capacity to bring in that next data set or run, that next set of analytics right it's available immediately is a service, not hey, we've got to kick off the procurement cycle for a whole bunch more hardware boxes. So that flexibility, that agility or key to the general pattern for using Splunk and again that ability to vertically scale stick multiple Splunk instances into containers and load more and more those up on these physical boxes right gives you great cost economics. You know, Splunk has a voracious appetite for data for doing analytics against that data less expensive, we can make that processing the better and the ability to really fully sweat, you know, sweat the assets fully utilize those assets. That kind of vertical scale is the other great element of the Green Lake solution. >>Yes. I mean, when you think about the value prop for for customers with Splunk and HP green, that gets a lot of what you would expect from what we used to talk about with the early days of cloud. Uh, that that flexibility, uh, it takes it away. A lot of the sort of mundane capacity planning you can shift. Resource is you talked about, you know, scale in a in a number of of use cases. So that's sort of another interesting angle, isn't it? >>Yeah. Faster. It's the classic text story. Faster, quicker, cheaper, easier, right? Just take in the whole whole new holy levels and hold the extremes with these technologies. >>What do you see? Is the differentiators with Splunk in HP, Maybe what's different from sort of the way we used to do things, but also sort of, you know, modern day competition. >>Yeah. Good. All good. All good questions. So I think the general attributes of splinter differentiated green Laker differentiated. I think when you put them together, you get this classic one plus one equals three story. So what? I hear from a lot of our target customers, big enterprises, big public sector customers. They can see the path to these benefits. They understand in theory how these different technologies would work together. But they're concerned about their own skills and abilities to go building. Run those and the rial beauty of Green Lake and Splunk is this. All comes sort of pre design, pre integrated right pre built HP is then they're providing these running containers as a service. So it's taking a lot of the skills and the concerns off the customers plate right, allowing them to fast board to, you know, cutting edge technology without any of the wrist. And then, most importantly, allowing customers to focus their very finite resource is their peoples their time, their money, their cycles on the things that are going to drive differentiated value back to the business. You know, let's face facts. Buying and provisioning Hardware is not a differentiating activity, running containers successfully, not differentiating running the core of Splunk. Not that differentiating. He can take all of those cycles and focus them instead on in the simple mechanics. How do we get more data in? Run more analytics on it and get more value out? Right then you're on the path to really delivering differentiated, you know, sustainable competitive basis type stuff back to the business, back to that digital transformation effort. So taking the skills out, taking the worries out, taking the concerns about new tech, out taking the procurement cycles, that improving scalability again quicker, faster, cheaper. Better for sure. >>It's kind of interesting when you when you look at the how the parlance has evolved from cloud and then you had Private Cloud. We talk a lot about hybrid, but I'm interested in your thoughts on why Splunk and HP Green Light green like now I mean, what's happening in the market that makes this the right place and in the right time, so to speak. >>Yeah, again, I put cloud right up there with big data is one of those really overloaded terms. Everything we keep keep redefining as we go if we define it. One way is as an experience instead of outcomes that customers looking for right, what does anyone of our mutual customers really want Well, they want capabilities that air quick to get up and running that air fast, to get the value that are aligned with how the price wise, with how they deliver value to the business and that they can quickly change right as the needs of the business and the operation shift. I think that's the outcome set that people are looking thio. Certainly the early days of cloud we thought were synonymous with public cloud. And hey, the way that you get those outcomes is you push things out. The public cloud providers, you know, what we saw is a lot of that motion in cases where there wasn't the best of alignment, right? You didn't get all those outcomes that you were hoping for. The cost savings weren't there or again. These big enterprises, these big organizations have a whole bunch of other work clothes that aren't necessarily public cloud amenable. But what they want is that same cloud experience. And this is where you see the evolution in the hybrid clouds and into private clouds. Yeah, any one of our customers is looking across the entirety of this landscape, things that are on Prem that they're probably gonna be on Prem forever. Things that they're moving into private cloud environments, things that they're moving into our growing or expanding or landing net new public cloud. They want those same outcomes, the same characteristics across all of that. That's a lot of Splunk value. Crop is a provider, right? Is we can go monitor and help you operate and developed and secure exactly all of that, no matter where it's located. Splunk on Green Lake is all about that stack, you know, working in that very cloud native way even where it made sense for customers to deploy and operate their own software. Even if this want, they're running over here themselves is hoping the modern, secure other work clothes that they put into their public cloud environments. >>Well, it Z another key proof point that we're seeing throughout the day here. Your software leader, you know, HP bring it together. It's ecosystem partners toe actually deliver tangible value. The customers skip. Great to hear your perspective today. Really appreciate you coming on the program. >>My pleasure. And thanks so much for having us take care. Stay well, >>Yeah, Cheers. You too. Okay, keep it right there. We're gonna go back to Keith now. Have him on a close out this segment of the program. You're watching HP Green Lake Day on the Cube. All right, We're So we're seeing some great examples of how Green Lake is supporting a lot of different industries. A lot of different workloads we just heard from Splunk really is part of the ecosystem. Really? A data heavy workload. And we're seeing the progress. HPC example Manufacturing. We talked about healthcare financial services, critical industries that are really driving towards the subscription model. So, Keith, thanks again for joining us. Is there anything else that we haven't hit that you feel are audience should should know about? >>Yeah, you bet. You know, we didn't cover some of the new capabilities that are really providing customers with the holistic experience to address their most demanding workloads with HP Green Lake. So first is our Green Lake managed security services. So this provides customers with an enterprise grade manage security solution that delivers lower costs and frees up a lot of their resource is the second is RHP advisory and Professional Services Group. So they help provide customers with tools and resource is to explore their needs for their digital transformation. Think about workshops and trials and proof of concepts and all of that implementation. Eso You get the strategy piece, you get the advisory piece, and then you get the implementation piece that's required to help them get started really quickly. And then third would be our H. P s moral software portfolio. So this provides customers with the ability to modernize their absent data unify, hybrid cloud and edge computing and operationalized artificial intelligence and machine learning and analytics. >>You know, I'm glad that you brought in the sort of machine intelligence piece in the machine learning because that's, ah, lot of times. That's the reason why people want to go to the cloud at the same time you bring in the security piece a lot of reasons why people want to keep things on Prem. And, of course, the use cases here. We're talking about it, really bringing that cloud experience that consumption model on Prem. I think it's critical critical for companies because they're expanding their notion of cloud computing really extending into hybrid and and the edge with that similar experience or substantially the same experience. So I think folks are gonna look at today's news as real progress. We're pushing you guys on some milestones and some proof points towards this vision is a critical juncture for organizations, especially those look, they're looking for comprehensive offerings to drive their digital transformations. Your thoughts keep >>Yeah, I know you. You know, we know as many as 70% of current and future APS and data are going to remain on Prem. They're gonna be in data centers, they're gonna be in Colo's, they're gonna be at the edge and, you know, really, for critical reasons. And so hybrid is key. As you mentioned, the number of times we wanna help customers transform their businesses and really drive business outcomes in this hybrid, multi cloud world with HP Green Lake and are targeted solutions. >>Excellent. Keith, Thanks again for coming on the program. Really appreciate your time. >>Always. Always. Thanks so much for having me and and take Take care of. Stay healthy, please. >>Alright. Keep it right there. Everybody, you're watching HP Green Lake day on the Cube

>> Hi, my name is Andy Clemenko. I'm a Senior Solutions Engineer at StackRox. Thanks for joining us today for my talk on labels, labels, labels. Obviously, you can reach me at all the socials. Before we get started, I like to point you to my GitHub repo, you can go to andyc.info/dc20, and it'll take you to my GitHub page where I've got all of this documentation, socials. Before we get started, I like to point you to my GitHub repo, you can go to andyc.info/dc20, (upbeat music) >> Hi, my name is Andy Clemenko. I'm a Senior Solutions Engineer at StackRox. Thanks for joining us today for my talk on labels, labels, labels. Obviously, you can reach me at all the socials. Before we get started, I like to point you to my GitHub repo, you can go to andyc.info/dc20, and it'll take you to my GitHub page where I've got all of this documentation, I've got the Keynote file there. YAMLs, I've got Dockerfiles, Compose files, all that good stuff. If you want to follow along, great, if not go back and review later, kind of fun. So let me tell you a little bit about myself. I am a former DOD contractor. This is my seventh DockerCon. I've spoken, I had the pleasure to speak at a few of them, one even in Europe. I was even a Docker employee for quite a number of years, providing solutions to the federal government and customers around containers and all things Docker. So I've been doing this a little while. One of the things that I always found interesting was the lack of understanding around labels. So why labels, right? Well, as a former DOD contractor, I had built out a large registry. And the question I constantly got was, where did this image come from? How did you get it? What's in it? Where did it come from? How did it get here? And one of the things we did to kind of alleviate some of those questions was we established a baseline set of labels. Labels really are designed to provide as much metadata around the image as possible. I ask everyone in attendance, when was the last time you pulled an image and had 100% confidence, you knew what was inside it, where it was built, how it was built, when it was built, you probably didn't, right? The last thing we obviously want is a container fire, like our image on the screen. And one kind of interesting way we can kind of prevent that is through the use of labels. We can use labels to address security, address some of the simplicity on how to run these images. So think of it, kind of like self documenting, Think of it also as an audit trail, image provenance, things like that. These are some interesting concepts that we can definitely mandate as we move forward. What is a label, right? Specifically what is the Schema? It's just a key-value. All right? It's any key and pretty much any value. What if we could dump in all kinds of information? What if we could encode things and store it in there? And I've got a fun little demo to show you about that. Let's start off with some of the simple keys, right? Author, date, description, version. Some of the basic information around the image. That would be pretty useful, right? What about specific labels for CI? What about a, where's the version control? Where's the source, right? Whether it's Git, whether it's GitLab, whether it's GitHub, whether it's Gitosis, right? Even SPN, who cares? Where are the source files that built, where's the Docker file that built this image? What's the commit number? That might be interesting in terms of tracking the resulting image to a person or to a commit, hopefully then to a person. How is it built? What if you wanted to play with it and do a git clone of the repo and then build the Docker file on your own? Having a label specifically dedicated on how to build this image might be interesting for development work. Where it was built, and obviously what build number, right? These kind of all, not only talk about continuous integration, CI but also start to talk about security. Specifically what server built it. The version control number, the version number, the commit number, again, how it was built. What's the specific build number? What was that job number in, say, Jenkins or GitLab? What if we could take it a step further? What if we could actually apply policy enforcement in the build pipeline, looking specifically for some of these specific labels? I've got a good example of, in my demo of a policy enforcement. So let's look at some sample labels. Now originally, this idea came out of label-schema.org. And then it was a modified to opencontainers, org.opencontainers.image. There is a link in my GitHub page that links to the full reference. But these are some of the labels that I like to use, just as kind of like a standardization. So obviously, Author's, an email address, so now the image is attributable to a person, that's always kind of good for security and reliability. Where's the source? Where's the version control that has the source, the Docker file and all the assets? How it was built, build number, build server the commit, we talked about, when it was created, a simple description. A fun one I like adding in is the healthZendpoint. Now obviously, the health check directive should be in the Docker file. But if you've got other systems that want to ping your applications, why not declare it and make it queryable? Image version, obviously, that's simple declarative And then a title. And then I've got the two fun ones. Remember, I talked about what if we could encode some fun things? Hypothetically, what if we could encode the Compose file of how to build the stack in the first image itself? And conversely the Kubernetes? Well, actually, you can and I have a demo to show you how to kind of take advantage of that. So how do we create labels? And really creating labels as a function of build time okay? You can't really add labels to an image after the fact. The way you do add labels is either through the Docker file, which I'm a big fan of, because it's declarative. It's in version control. It's kind of irrefutable, especially if you're tracking that commit number in a label. You can extend it from being a static kind of declaration to more a dynamic with build arguments. And I can show you, I'll show you in a little while how you can use a build argument at build time to pass in that variable. And then obviously, if you did it by hand, you could do a docker build--label key equals value. I'm not a big fan of the third one, I love the first one and obviously the second one. Being dynamic we can take advantage of some of the variables coming out of version control. Or I should say, some of the variables coming out of our CI system. And that way, it self documents effectively at build time, which is kind of cool. How do we view labels? Well, there's two major ways to view labels. The first one is obviously a docker pull and docker inspect. You can pull the image locally, you can inspect it, you can obviously, it's going to output as JSON. So you going to use something like JQ to crack it open and look at the individual labels. Another one which I found recently was Skopeo from Red Hat. This allows you to actually query the registry server. So you don't even have to pull the image initially. This can be really useful if you're on a really small development workstation, and you're trying to talk to a Kubernetes cluster and wanting to deploy apps kind of in a very simple manner. Okay? And this was that use case, right? Using Kubernetes, the Kubernetes demo. One of the interesting things about this is that you can base64 encode almost anything, push it in as text into a label and then base64 decode it, and then use it. So in this case, in my demo, I'll show you how we can actually use a kubectl apply piped from the base64 decode from the label itself from skopeo talking to the registry. And what's interesting about this kind of technique is you don't need to store Helm charts. You don't need to learn another language for your declarative automation, right? You don't need all this extra levels of abstraction inherently, if you use it as a label with a kubectl apply, It's just built in. It's kind of like the kiss approach to a certain extent. It does require some encoding when you actually build the image, but to me, it doesn't seem that hard. Okay, let's take a look at a demo. And what I'm going to do for my demo, before we actually get started is here's my repo. Here's a, let me actually go to the actual full repo. So here's the repo, right? And I've got my Jenkins pipeline 'cause I'm using Jenkins for this demo. And in my demo flask, I've got the Docker file. I've got my compose and my Kubernetes YAML. So let's take a look at the Docker file, right? So it's a simple Alpine image. The org statements are the build time arguments that are passed in. Label, so again, I'm using the org.opencontainers.image.blank, for most of them. There's a typo there. Let's see if you can find it, I'll show you it later. My source, build date, build number, commit. Build number and get commit are derived from the Jenkins itself, which is nice. I can just take advantage of existing URLs. I don't have to create anything crazy. And again, I've got my actual Docker build command. Now this is just a label on how to build it. And then here's my simple Python, APK upgrade, remove the package manager, kind of some security stuff, health check getting Python through, okay? Let's take a look at the Jenkins pipeline real quick. So here is my Jenkins pipeline and I have four major stages, four stages, I have built. And here in build, what I do is I actually do the Git clone. And then I do my docker build. From there, I actually tell the Jenkins StackRox plugin. So that's what I'm using for my security scanning. So go ahead and scan, basically, I'm staging it to scan the image. I'm pushing it to Hub, okay? Where I can see the, basically I'm pushing the image up to Hub so such that my StackRox security scanner can go ahead and scan the image. I'm kicking off the scan itself. And then if everything's successful, I'm pushing it to prod. Now what I'm doing is I'm just using the same image with two tags, pre-prod and prod. This is not exactly ideal, in your environment, you probably want to use separate registries and non-prod and a production registry, but for demonstration purposes, I think this is okay. So let's go over to my Jenkins and I've got a deliberate failure. And I'll show you why there's a reason for that. And let's go down. Let's look at my, so I have a StackRox report. Let's look at my report. And it says image required, required image label alert, right? Request that the maintainer, add the required label to the image, so we're missing a label, okay? One of the things we can do is let's flip over, and let's look at Skopeo. Right? I'm going to do this just the easy way. So instead of looking at org.zdocker, opencontainers.image.authors. Okay, see here it says build signature? That was the typo, we didn't actually pass in. So if we go back to our repo, we didn't pass in the the build time argument, we just passed in the word. So let's fix that real quick. That's the Docker file. Let's go ahead and put our dollar sign in their. First day with the fingers you going to love it. And let's go ahead and commit that. Okay? So now that that's committed, we can go back to Jenkins, and we can actually do another build. And there's number 12. And as you can see, I've been playing with this for a little bit today. And while that's running, come on, we can go ahead and look at the Console output. Okay, so there's our image. And again, look at all the build arguments that we're passing into the build statement. So we're passing in the date and the date gets derived on the command line. With the build arguments, there's the base64 encoded of the Compose file. Here's the base64 encoding of the Kubernetes YAML. We do the build. And then let's go down to the bottom layer exists and successful. So here's where we can see no system policy violations profound marking stack regimes security plugin, build step as successful, okay? So we're actually able to do policy enforcement that that image exists, that that label sorry, exists in the image. And again, we can look at the security report and there's no policy violations and no vulnerabilities. So that's pretty good for security, right? We can now enforce and mandate use of certain labels within our images. And let's flip back over to Skopeo, and let's go ahead and look at it. So we're looking at the prod version again. And there's it is in my email address. And that validated that that was valid for that policy. So that's kind of cool. Now, let's take it a step further. What if, let's go ahead and take a look at all of the image, all the labels for a second, let me remove the dash org, make it pretty. Okay? So we have all of our image labels. Again, author's build, commit number, look at the commit number. It was built today build number 12. We saw that right? Delete, build 12. So that's kind of cool dynamic labels. Name, healthz, right? But what we're looking for is we're going to look at the org.zdockerketers label. So let's go look at the label real quick. Okay, well that doesn't really help us because it's encoded but let's base64 dash D, let's decode it. And I need to put the dash r in there 'cause it doesn't like, there we go. So there's my Kubernetes YAML. So why can't we simply kubectl apply dash f? Let's just apply it from standard end. So now we've actually used that label. From the image that we've queried with skopeo, from a remote registry to deploy locally to our Kubernetes cluster. So let's go ahead and look everything's up and running, perfect. So what does that look like, right? So luckily, I'm using traefik for Ingress 'cause I love it. And I've got an object in my Kubernetes YAML called flask.doctor.life. That's my Ingress object for traefik. I can go to flask.docker.life. And I can hit refresh. Obviously, I'm not a very good web designer 'cause the background image in the text. We can go ahead and refresh it a couple times we've got Redis storing a hit counter. We can see that our server name is roundrobing. Okay? That's kind of cool. So let's kind of recap a little bit about my demo environment. So my demo environment, I'm using DigitalOcean, Ubuntu 19.10 Vms. I'm using K3s instead of full Kubernetes either full Rancher, full Open Shift or Docker Enterprise. I think K3s has some really interesting advantages on the development side and it's kind of intended for IoT but it works really well and it deploys super easy. I'm using traefik for Ingress. I love traefik. I may or may not be a traefik ambassador. I'm using Jenkins for CI. And I'm using StackRox for image scanning and policy enforcement. One of the things to think about though, especially in terms of labels is none of this demo stack is required. You can be in any cloud, you can be in CentOs, you can be in any Kubernetes. You can even be in swarm, if you wanted to, or Docker compose. Any Ingress, any CI system, Jenkins, circle, GitLab, it doesn't matter. And pretty much any scanning. One of the things that I think is kind of nice about at least StackRox is that we do a lot more than just image scanning, right? With the policy enforcement things like that. I guess that's kind of a shameless plug. But again, any of this stack is completely replaceable, with any comparative product in that category. So I'd like to, again, point you guys to the andyc.infodc20, that's take you right to the GitHub repo. You can reach out to me at any of the socials @clemenko or andy@stackrox.com. And thank you for attending. I hope you learned something fun about labels. And hopefully you guys can standardize labels in your organization and really kind of take your images and the image provenance to a new level. Thanks for watching. (upbeat music) >> Narrator: Live from Las Vegas It's theCUBE. Covering AWS re:Invent 2019. Brought to you by Amazon Web Services and Intel along with it's ecosystem partners. >> Okay, welcome back everyone theCUBE's live coverage of AWS re:Invent 2019. This is theCUBE's 7th year covering Amazon re:Invent. It's their 8th year of the conference. I want to just shout out to Intel for their sponsorship for these two amazing sets. Without their support we wouldn't be able to bring our mission of great content to you. I'm John Furrier. Stu Miniman. We're here with the chief of AWS, the chief executive officer Andy Jassy. Tech athlete in and of himself three hour Keynotes. Welcome to theCUBE again, great to see you. >> Great to be here, thanks for having me guys. >> Congratulations on a great show a lot of great buzz. >> Andy: Thank you. >> A lot of good stuff. Your Keynote was phenomenal. You get right into it, you giddy up right into it as you say, three hours, thirty announcements. You guys do a lot, but what I liked, the new addition, the last year and this year is the band; house band. They're pretty good. >> Andy: They're good right? >> They hit the queen notes, so that keeps it balanced. So we're going to work on getting a band for theCUBE. >> Awesome. >> So if I have to ask you, what's your walk up song, what would it be? >> There's so many choices, it depends on what kind of mood I'm in. But, uh, maybe Times Like These by the Foo Fighters. >> John: Alright. >> These are unusual times right now. >> Foo Fighters playing at the Amazon Intersect Show. >> Yes they are. >> Good plug Andy. >> Headlining. >> Very clever >> Always getting a good plug in there. >> My very favorite band. Well congratulations on the Intersect you got a lot going on. Intersect is a music festival, I'll get to that in a second But, I think the big news for me is two things, obviously we had a one-on-one exclusive interview and you laid out, essentially what looks like was going to be your Keynote, and it was. Transformation- >> Andy: Thank you for the practice. (Laughter) >> John: I'm glad to practice, use me anytime. >> Yeah. >> And I like to appreciate the comments on Jedi on the record, that was great. But I think the transformation story's a very real one, but the NFL news you guys just announced, to me, was so much fun and relevant. You had the Commissioner of NFL on stage with you talking about a strategic partnership. That is as top down, aggressive goal as you could get to have Rodger Goodell fly to a tech conference to sit with you and then bring his team talk about the deal. >> Well, ya know, we've been partners with the NFL for a while with the Next Gen Stats that they use on all their telecasts and one of the things I really like about Roger is that he's very curious and very interested in technology and the first couple times I spoke with him he asked me so many questions about ways the NFL might be able to use the Cloud and digital transformation to transform their various experiences and he's always said if you have a creative idea or something you think that could change the world for us, just call me he said or text me or email me and I'll call you back within 24 hours. And so, we've spent the better part of the last year talking about a lot of really interesting, strategic ways that they can evolve their experience both for fans, as well as their players and the Player Health and Safety Initiative, it's so important in sports and particularly important with the NFL given the nature of the sport and they've always had a focus on it, but what you can do with computer vision and machine learning algorithms and then building a digital athlete which is really like a digital twin of each athlete so you understand, what does it look like when they're healthy and compare that when it looks like they may not be healthy and be able to simulate all kinds of different combinations of player hits and angles and different plays so that you could try to predict injuries and predict the right equipment you need before there's a problem can be really transformational so we're super excited about it. >> Did you guys come up with the idea or was it a collaboration between them? >> It was really a collaboration. I mean they, look, they are very focused on players safety and health and it's a big deal for their- you know, they have two main constituents the players and fans and they care deeply about the players and it's a-it's a hard problem in a sport like Football, I mean, you watch it. >> Yeah, and I got to say it does point out the use cases of what you guys are promoting heavily at the show here of the SageMaker Studio, which was a big part of your Keynote, where they have all this data. >> Andy: Right. >> And they're data hoarders, they hoard data but the manual process of going through the data was a killer problem. This is consistent with a lot of the enterprises that are out there, they have more data than they even know. So this seems to be a big part of the strategy. How do you get the customers to actually wake up to the fact that they got all this data and how do you tie that together? >> I think in almost every company they know they have a lot of data. And there are always pockets of people who want to do something with it. But, when you're going to make these really big leaps forward; these transformations, the things like Volkswagen is doing where they're reinventing their factories and their manufacturing process or the NFL where they're going to radically transform how they do players uh, health and safety. It starts top down and if the senior leader isn't convicted about wanting to take that leap forward and trying something different and organizing the data differently and organizing the team differently and using machine learning and getting help from us and building algorithms and building some muscle inside the company it just doesn't happen because it's not in the normal machinery of what most companies do. And so it always, almost always, starts top down. Sometimes it can be the Commissioner or CEO sometimes it can be the CIO but it has to be senior level conviction or it doesn't get off the ground. >> And the business model impact has to be real. For NFL, they know concussions, hurting their youth pipe-lining, this is a huge issue for them. This is their business model. >> They lose even more players to lower extremity injuries. And so just the notion of trying to be able to predict injuries and, you know, the impact it can have on rules and the impact it can have on the equipment they use, it's a huge game changer when they look at the next 10 to 20 years. >> Alright, love geeking out on the NFL but Andy, you know- >> No more NFL talk? >> Off camera how about we talk? >> Nobody talks about the Giants being 2 and 10. >> Stu: We're both Patriots fans here. >> People bring up the undefeated season. >> So Andy- >> Everybody's a Patriot's fan now. (Laughter) >> It's fascinating to watch uh, you and your three hour uh, Keynote, uh Werner in his you know, architectural discussion, really showed how AWS is really extending its reach, you know, it's not just a place. For a few years people have been talking about you know, Cloud is an operational model its not a destination or a location but, I felt it really was laid out is you talked about Breadth and Depth and Werner really talked about you know, Architectural differentiation. People talk about Cloud, but there are very-there are a lot of differences between the vision for where things are going. Help us understand why, I mean, Amazon's vision is still a bit different from what other people talk about where this whole Cloud expansion, journey, put ever what tag or label you want on it but you know, the control plane and the technology that you're building and where you see that going. >> Well I think that, we've talked about this a couple times we have two macro types of customers. We have those that really want to get at the low level building blocks and stitch them together creatively however they see fit to create whatever's in their-in their heads. And then we have the second segment of customers that say look, I'm willing to give up some of that flexibility in exchange for getting 80% of the way there much faster. In an abstraction that's different from those low level building blocks. And both segments of builders we want to serve and serve well and so we've built very significant offerings in both areas. I think when you look at microservices um, you know, some of it has to do with the fact that we have this very strongly held belief born out of several years of Amazon where you know, the first 7 or 8 years of Amazon's consumer business we basically jumbled together all of the parts of our technology in moving really quickly and when we wanted to move quickly where you had to impact multiple internal development teams it was so long because it was this big ball, this big monolithic piece. And we got religion about that in trying to move faster in the consumer business and having to tease those pieces apart. And it really was a lot of impetus behind conceiving AWS where it was these low level, very flexible building blocks that6 don't try and make all the decisions for customers they get to make them themselves. And some of the microservices that you saw Werner talking about just, you know, for instance, what we-what we did with Nitro or even what we did with Firecracker those are very much about us relentlessly working to continue to uh, tease apart the different components. And even things that look like low level building blocks over time, you build more and more features and all of the sudden you realize they have a lot of things that are combined together that you wished weren't that slow you down and so, Nitro was a completely re imagining of our Hypervisor and Virtualization layer to allow us, both to let customers have better performance but also to let us move faster and have a better security story for our customers. >> I got to ask you the question around transformation because I think that all points, all the data points, you got all the references, Goldman Sachs on stage at the Keynote, Cerner, I mean healthcare just is an amazing example because I mean, that's demonstrating real value there there's no excuse. I talked to someone who wouldn't be named last night, in and around the area said, the CIA has a cost bar like this a cost-a budget like this but the demand for mission based apps is going up exponentially, so there's need for the Cloud. And so, you see more and more of that. What is your top down, aggressive goals to fill that solution base because you're also a very transformational thinker; what is your-what is your aggressive top down goals for your organization because you're serving a market with trillions of dollars of spend that's shifting, that's on the table. >> Yeah. >> A lot of competition now sees it too, they're going to go after it. But at the end of the day you have customers that have a demand for things, apps. >> Andy: Yeah. >> And not a lot of budget increase at the same time. This is a huge dynamic. >> Yeah. >> John: What's your goals? >> You know I think that at a high level our top down aggressive goals are that we want every single customer who uses our platform to have an outstanding customer experience. And we want that outstanding customer experience in part is that their operational performance and their security are outstanding, but also that it allows them to build, uh, build projects and initiatives that change their customer experience and allow them to be a sustainable successful business over a long period of time. And then, we also really want to be the technology infrastructure platform under all the applications that people build. And we're realistic, we know that you know, the market segments we address with infrastructure, software, hardware, and data center services globally are trillions of dollars in the long term and it won't only be us, but we have that goal of wanting to serve every application and that requires not just the security operational premise but also a lot of functionality and a lot of capability. We have by far the most amount of capability out there and yet I would tell you, we have 3 to 5 years of items on our roadmap that customers want us to add. And that's just what we know today. >> And Andy, underneath the covers you've been going through some transformation. When we talked a couple of years ago, about how serverless is impacting things I've heard that that's actually, in many ways, glue behind the two pizza teams to work between organizations. Talk about how the internal transformations are happening. How that impacts your discussions with customers that are going through that transformation. >> Well, I mean, there's a lot of- a lot of the technology we build comes from things that we're doing ourselves you know? And that we're learning ourselves. It's kind of how we started thinking about microservices, serverless too, we saw the need, you know, we would have we would build all these functions that when some kind of object came into an object store we would spin up, compute, all those tasks would take like, 3 or 4 hundred milliseconds then we'd spin it back down and yet, we'd have to keep a cluster up in multiple availability zones because we needed that fault tolerance and it was- we just said this is wasteful and, that's part of how we came up with Lambda and you know, when we were thinking about Lambda people understandably said, well if we build Lambda and we build this serverless adventure in computing a lot of people were keeping clusters of instances aren't going to use them anymore it's going to lead to less absolute revenue for us. But we, we have learned this lesson over the last 20 years at Amazon which is, if it's something that's good for customers you're much better off cannibalizing yourself and doing the right thing for customers and being part of shaping something. And I think if you look at the history of technology you always build things and people say well, that's going to cannibalize this and people are going to spend less money, what really ends up happening is they spend less money per unit of compute but it allows them to do so much more that they ultimately, long term, end up being more significant customers. >> I mean, you are like beating the drum all the time. Customers, what they say, we encompass the roadmap, I got that you guys have that playbook down, that's been really successful for you. >> Andy: Yeah. >> Two years ago you told me machine learning was really important to you because your customers told you. What's the next traunch of importance for customers? What's on top of mind now, as you, look at- >> Andy: Yeah. >> This re:Invent kind of coming to a close, Replay's tonight, you had conversations, you're a tech athlete, you're running around, doing speeches, talking to customers. What's that next hill from if it's machine learning today- >> There's so much I mean, (weird background noise) >> It's not a soup question (Laughter) And I think we're still in the very early days of machine learning it's not like most companies have mastered it yet even though they're using it much more then they did in the past. But, you know, I think machine learning for sure I think the Edge for sure, I think that um, we're optimistic about Quantum Computing even though I think it'll be a few years before it's really broadly useful. We're very um, enthusiastic about robotics. I think the amount of functions that are going to be done by these- >> Yeah. >> robotic applications are much more expansive than people realize. It doesn't mean humans won't have jobs, they're just going to work on things that are more value added. We're believers in augmented virtual reality, we're big believers in what's going to happen with Voice. And I'm also uh, I think sometimes people get bored you know, I think you're even bored with machine learning already >> Not yet. >> People get bored with the things you've heard about but, I think just what we've done with the Chips you know, in terms of giving people 40% better price performance in the latest generation of X86 processors. It's pretty unbelievable in the difference in what people are going to be able to do. Or just look at big data I mean, big data, we haven't gotten through big data where people have totally solved it. The amount of data that companies want to store, process, analyze, is exponentially larger than it was a few years ago and it will, I think, exponentially increase again in the next few years. You need different tools and services. >> Well I think we're not bored with machine learning we're excited to get started because we have all this data from the video and you guys got SageMaker. >> Andy: Yeah. >> We call it the stairway to machine learning heaven. >> Andy: Yeah. >> You start with the data, move up, knock- >> You guys are very sophisticated with what you do with technology and machine learning and there's so much I mean, we're just kind of, again, in such early innings. And I think that, it was so- before SageMaker, it was so hard for everyday developers and data scientists to build models but the combination of SageMaker and what's happened with thousands of companies standardizing on it the last two years, plus now SageMaker studio, giant leap forward. >> Well, we hope to use the data to transform our experience with our audience. And we're on Amazon Cloud so we really appreciate that. >> Andy: Yeah. >> And appreciate your support- >> Andy: Yeah, of course. >> John: With Amazon and get that machine learning going a little faster for us, that would be better. >> If you have requests I'm interested, yeah. >> So Andy, you talked about that you've got the customers that are builders and the customers that need simplification. Traditionally when you get into the, you know, the heart of the majority of adoption of something you really need to simplify that environment. But when I think about the successful enterprise of the future, they need to be builders. how'l I normally would've said enterprise want to pay for solutions because they don't have the skill set but, if they're going to succeed in this new economy they need to go through that transformation >> Andy: Yeah. >> That you talk to, so, I mean, are we in just a total new era when we look back will this be different than some of these previous waves? >> It's a really good question Stu, and I don't think there's a simple answer to it. I think that a lot of enterprises in some ways, I think wish that they could just skip the low level building blocks and only operate at that higher level abstraction. That's why people were so excited by things like, SageMaker, or CodeGuru, or Kendra, or Contact Lens, these are all services that allow them to just send us data and then run it on our models and get back the answers. But I think one of the big trends that we see with enterprises is that they are taking more and more of their development in house and they are wanting to operate more and more like startups. I think that they admire what companies like AirBnB and Pintrest and Slack and Robinhood and a whole bunch of those companies, Stripe, have done and so when, you know, I think you go through these phases and eras where there are waves of success at different companies and then others want to follow that success and replicate it. And so, we see more and more enterprises saying we need to take back a lot of that development in house. And as they do that, and as they add more developers those developers in most cases like to deal with the building blocks. And they have a lot of ideas on how they can creatively stich them together. >> Yeah, on that point, I want to just quickly ask you on Amazon versus other Clouds because you made a comment to me in our interview about how hard it is to provide a service to other people. And it's hard to have a service that you're using yourself and turn that around and the most quoted line of my story was, the compression algorithm- there's no compression algorithm for experience. Which to me, is the diseconomies of scale for taking shortcuts. >> Andy: Yeah. And so I think this is a really interesting point, just add some color commentary because I think this is a fundamental difference between AWS and others because you guys have a trajectory over the years of serving, at scale, customers wherever they are, whatever they want to do, now you got microservices. >> Yeah. >> John: It's even more complex. That's hard. >> Yeah. >> John: Talk about that. >> I think there are a few elements to that notion of there's no compression algorithm for experience and I think the first thing to know about AWS which is different is, we just come from a different heritage and a different background. We ran a business for a long time that was our sole business that was a consumer retail business that was very low margin. And so, we had to operate at very large scale given how many people were using us but also, we had to run infrastructure services deep in the stack, compute storage and database, and reliable scalable data centers at very low cost and margins. And so, when you look at our business it actually, today, I mean its, its a higher margin business in our retail business, its a lower margin business in software companies but at real scale, it's a high volume, relatively low margin business. And the way that you have to operate to be successful with those businesses and the things you have to think about and that DNA come from the type of operators we have to be in our consumer retail business. And there's nobody else in our space that does that. So, you know, the way that we think about costs, the way we think about innovation in the data center, um, and I also think the way that we operate services and how long we've been operating services as a company its a very different mindset than operating package software. Then you look at when uh, you think about some of the uh, issues in very large scale Cloud, you can't learn some of those lessons until you get to different elbows of the curve and scale. And so what I was telling you is, its really different to run your own platform for your own users where you get to tell them exactly how its going to be done. But that's not the way the real world works. I mean, we have millions of external customers who use us from every imaginable country and location whenever they want, without any warning, for lots of different use cases, and they have lots of design patterns and we don't get to tell them what to do. And so operating a Cloud like that, at a scale that's several times larger than the next few providers combined is a very different endeavor and a very different operating rigor. >> Well you got to keep raising the bar you guys do a great job, really impressed again. Another tsunami of announcements. In fact, you had to spill the beans earlier with Quantum the day before the event. Tight schedule. I got to ask you about the musical festival because, I think this is a very cool innovation. It's the inaugural Intersect conference. >> Yes. >> John: Which is not part of Replay, >> Yes. >> John: Which is the concert tonight. Its a whole new thing, big music act, you're a big music buff, your daughter's an artist. Why did you do this? What's the purpose? What's your goal? >> Yeah, it's an experiment. I think that what's happened is that re:Invent has gotten so big, we have 65 thousand people here, that to do the party, which we do every year, its like a 35-40 thousand person concert now. Which means you have to have a location that has multiple stages and, you know, we thought about it last year and when we were watching it and we said, we're kind of throwing, like, a 4 hour music festival right now. There's multiple stages, and its quite expensive to set up that set for a party and we said well, maybe we don't have to spend all that money for 4 hours and then rip it apart because actually the rent to keep those locations for another two days is much smaller than the cost of actually building multiple stages and so we thought we would try it this year. We're very passionate about music as a business and I think we-I think our customers feel like we've thrown a pretty good music party the last few years and we thought we would try it at a larger scale as an experiment. And if you look at the economics- >> At the headliners real quick. >> The Foo Fighters are headlining on Saturday night, Anderson Paak and the Free Nationals, Brandi Carlile, Shawn Mullins, um, Willy Porter, its a good set. Friday night its Beck and Kacey Musgraves so it's a really great set of um, about thirty artists and we're hopeful that if we can build a great experience that people will want to attend that we can do it at scale and it might be something that both pays for itself and maybe, helps pay for re:Invent too overtime and you know, I think that we're also thinking about it as not just a music concert and festival the reason we named it Intersect is that we want an intersection of music genres and people and ethnicities and age groups and art and technology all there together and this will be the first year we try it, its an experiment and we're really excited about it. >> Well I'm gone, congratulations on all your success and I want to thank you we've been 7 years here at re:Invent we've been documenting the history. You got two sets now, one set upstairs. So appreciate you. >> theCUBE is part of re:Invent, you know, you guys really are apart of the event and we really appreciate your coming here and I know people appreciate the content you create as well. >> And we just launched CUBE365 on Amazon Marketplace built on AWS so thanks for letting us- >> Very cool >> John: Build on the platform. appreciate it. >> Thanks for having me guys, I appreciate it. >> Andy Jassy the CEO of AWS here inside theCUBE, it's our 7th year covering and documenting the thunderous innovation that Amazon's doing they're really doing amazing work building out the new technologies here in the Cloud computing world. I'm John Furrier, Stu Miniman, be right back with more after this short break. (Outro music)