>>Okay, welcome back everyone to the cubes coverage here in Las Vegas for AWS re Mars, Remar stands for machine learning, automation, robotics, and space. Part of thehow is reinforces security. And the big show reinvent at the end of the year is the marquee event. Of course, the queues at all three and more coverage here. We've got a great guest here. Ryan re practice lead data analytics, machine learning at mission cloud. Ryan. Thanks for joining me. Absolutely >>Glad. >>So we were talking before he came on camera about mission cloud. It's not a mission as in a space mission. That's just the name of the company to help people with their mission to move to the cloud. And we're a space show to make that it's almost like plausible. I can see a mission cloud coming someday. >>Yeah, absolutely. >>You got >>The name. We got it. We're ready. >>You guys help customers get to the cloud. So you're working with all the technologies on AWS stack and people who are either lifting and shifting or cloud native born in the cloud, right? Absolutely. >>Yeah. I mean, we often see some companies talk about lift and shift, but you know, we try to get them past that because often a lift and shift means like, say you're on Oracle, you're bringing your Oracle licensing, but a lot of companies want to, you know, innovate and migrate more than they want to lift and shift. So that's really what we're seeing in market. >>You see more migration. Yeah. Less lift and shift. >>Yeah, exactly. Because they, they're trying to get out of an Oracle license. Right. They're seeing if that's super expensive and you know, you can get a much cheaper product on AWS. >>Yeah. What's the cutting up areas right now that you're seeing with cloud Amazon. Cause you know, Amazon, you know, is at their, their birthday, you know, dynamo you to sell with their 10th birthday. Where are they in your mind relative to the enterprise in terms of the services and where this goes next in terms of the on-prem you got the hybrid model. Everyone sees that, but like you got outpost. Mm. Not doing so as good as say EKS or other cool serverless stuff. >>Yeah. I mean, that's a great question. One of the things that's you see from AWS is really innovation, right? They're out there, they have over 400 microservices. So they're looking at all the different areas you have on the cloud and that people are trying to use. And they're creating these microservices that you string together, you architect them all up so that you can create what you're looking for. One of the big things we're seeing, right, is with SageMaker. A lot of people are coming in, looking for ML projects, trying to use all the hype that you see around that doing prediction, NLP and computer vision are super hot right now we've helped a lot of companies, you know, start to build out these NLP models where they're doing, you know, all kinds of stuff you use. 'em in gene research, you know, they're trying to do improvements in drugs and therapeutics. It's really awesome. And then we do some eCommerce stuff where people are just looking at, you know, how do I figure out what are similar things on similar websites, right. For, for search companies. So >>Awesome. Take me through the profile of your customer. You have the mix of business. Can you break down the, the target of the small, medium size enterprise, large all the above. >>Yeah. So mission started working with a lot of startups and SMBs and then as we've grown and become, you know, a much larger company that has all the different focus areas, we started to get into enterprise as well and help a lot of pretty well known enterprises out there that are, you know, not able to find the staff that they need and really want to get into >>The cloud. I wanted to dig into the staffing issues and also to the digital transformation journey. Okay. It okay. We all kind of know what's turning into the more dashboards, more automation, DevOps, cloud, native applications. All good. Yeah. And I can see that journey path. Now the reality is how do you get people who are gonna be capable of doing the ML, doing the DevOps dev sec ops. But what about cyber security? I mean is a ton of range of issues that you gotta be competent on to kind of survive in this multi-disciplined world, just to the old days of I'm the top of rack switch guy is over. >>Absolutely. Yeah. You know, it's a really good question. It's really hard. And that's why, you know, AWS has built out that partner ecosystem because they know companies can't hire enough people to do that. You know, if you look at just a migration into a data lake, you know, on-prem often you had one guy doing it, but if you want to go to the cloud, it's like you said, right, you need a security guy. You need to have a data architect. You need to have a cloud architect. You need to have a data engineer. So, you know, in the old days maybe you needed one guy. Now you have to have five. And so that's really why partners are valuable to customers is we're able to come in, bring those resources, get everything done quickly, and then, you know, turn >>It over. Yeah. We were talking again before we came on camera here live, you, you guys have a service led business, but the rise of MSPs managed service providers is huge. We're seeing it everywhere mainly because the cloud actually enables that you're seeing it for things like Kubernetes, serverless, certain microservices have certain domain expertise and people are making a living, providing great managed services. You guys have managed services. What's that phenomenon. Do you agree with it? And how do you, why did that come about and what, how does it keep going? Is it a trend or is it a one trick pony? >>I think it's a trend. I mean, what you have, it's the same skills gap, right? Is companies no longer want that single point of failure? You know, we have a pool model with our managed services where your team's working with a group of people. And so, you know, we have that knowledge and it's spread out. And so if you're coming in and you need help with Kubernetes, we got a Kubernetes guy in that pool to help you, right. If you need, you know, data, we got a data guy. And so it just makes it a lot easier where, Hey, I can pay the same as one guy and get a whole team of like 12 people that can be interchangeable onto my project. So, you know, I think you're gonna see managed services continue to rise and companies, you know, just working in that space. >>Do you see a new skill set coming? That's kind of got visibility right now, but not full visibility. That's going to be needed. I asked this because the environment's changing for the better obviously, but you're seeing companies that are highly valued, like data bricks, snowflake, they're getting killed on valuation. So they gotta have a hard time retaining talent. In my opinion, my opinion probably be true, but you know, you can't, you know, if you're data breach, you can't raise that 45 billion valuation try to hire senior people. They're gonna be underwater from day one. So there's gonna be a real slow down in these unicorns, these mega unicorns, deck, unicorns, whatever they're called because they gotta refactor the company, stock equity package. They attract people. So they gotta put them on a flat foot. And the next question is, do they actually have the juice, the goods to go to the new market? That's another question. So what I mean, what's your take on you're in the trenches. You're in the front lines. >>Yeah, that's a great question. I mean, and it's hard for me to think about whether they have the juice. I think snowflake and data bricks have been great for the market. They've come in. They've innovated, you know, snowflake was cloud native first. So they were built for the cloud. And what that's done is push all the hyperscalers to improve their products, right. AWS has gone through and you know, drastically over the last three years, improved Redshift. Like, I mean it's night and day from three years ago. Did, >>And you think snowflake put that pressure on them? >>Snowflake. Absolutely. Put that pressure on them. You know, I don't know whether they would've gotten to that same level if snowflake wasn't out there stealing market share. But now when you look at it, Redshift is much cheaper than snowflake. So how long are people gonna pay that tax to have snowflake versus switching over snowflakes? >>Got a nice data. Clean room, had some nice lock in features. Only on snowflake. The question is, will that last clean room? I see you smiling. Go ahead. >>Clean. Room's a concept that was actually made by Google. I know Snowflake's trying to capture it as their own, but, but Google's the one that actually launched the clean room concept because of marketing and, and all of that. >>Google also launches semantic layer, which Snowflake's trying to copy that. Does that, what does that mean to you when you hear the word semantic layer? What does that mean? >>And semantic layer just is really all about meta tags, right? How am I going through to figure out what data do I actually have in my data lake so that I can pull it for whatever I'm trying to do, whether it's dashboarding or whether it's machine learning. You're just trying to organize your data better. >>Ryan, you should be a cue post. You're like a masterclass here in, in it and cloud native. I gotta ask you since you're here, since we're having the masterclass being put in a clinic here, lot of clients are confused between how to handle the control plane and the data plane cause machine learning right now is at an all time high. You're seeing deep racer. You're seeing robotic space, all driving by machine learning. SW. He said it today, the, the companion coder, right? The, the code whisperer, that's only gonna get stronger. So machine learning needs data. It feeds on data. So everyone right now is trying to put data in silos. Okay? Cause they think, oh, compliance, you gotta create a data plane and a control plane that makes it highly available. So that can be shared >>Right >>Now. A lot of people are trying to own the data plane and some are trying to own the control plane or both. Right? What's your view on that? Because I see customers say, look, I want to own my own data cause I can control it. Control plane. I can maybe do other things. And some are saying, I don't know what to do. And they're getting forced to take both to control plane and a data plane from a vendor, right? What's your, what's your reaction to that? >>So it's pretty interesting. I actually was presenting at a tech target conference this week on exactly this concept, right, where we're seeing more and more words out there, right? It was data warehouse and it was data lake and it's lake house. And it's a data mesh and it's a data fabric. And some of the concepts you're talking about really come into that data, match data fabric space. And you know, what you're seeing is data's gonna become a product right, where you're gonna be buying a product and the silos yes. Silos exist. But what, what companies have to start doing is, and this is the whole data mesh concept is, Hey yes, you finance department. You can own your silo, but now you have to have an output product. That's a data product that every other part of your company can subscribe to that data product and use it in their algorithms or their dashboard so that they can get that 360 degree view of the customer. So it's really, you know, key that, you know, you work within your business. Some business are gonna have that silo where the data mesh works. Great. Others are gonna go. >>And what do you think about that? Because I mean, my thesis would be, Hey, more data, better machine learning. Right. Is that the concept? >>So, or that's a misconception or, >>Okay. So what's the, what's the rationale to share the data like that and data mission. >>So having more of the right data here, it is improves. Just having more data in general, doesn't improve, right? And often the problem is in the silos you're getting to is you don't have all the data you want. Right. I was doing a big project about shipping and there's PII data. When you talk about shipping, right? Person's addresses, that's owned by one department and you can't get there. Right. But how am I supposed to estimate the cost of shipping if I can't get, you know, data from where a person lives. Right. It's just >>Not. So none of the wrinkle in the equation is latency. Okay. The right data at the right time is another factor is that factored into data mesh versus these other approaches. Because I mean, you can, people are streaming data. I get that. We're seeing a lot of that. But talking about getting data fast enough before the decisions are made, is that an issue or is this just BS? >>I'm going with BS. Okay. So people talk about real time real. Time's great if you need it, but it's really expensive to do. Most people don't need real time. Right. They're really looking for, I need an hourly dashboard or I need a daily dashboard. And so pushing into real time, just gonna be an added expense that you don't >>Really need. Like cyber maybe is that not maybe need real time. >>Well, cyber security add. I mean, there's definitely certain applications that you need real time, >>But don't over invest in fantasy if you don't need an an hour's fine. Right, >>Right. Yeah. If you're, if you're a business and you're looking at your financials, do you need your financials every second? Is that gonna do anything for you? Got >>It. Yeah. Yeah. And so this comes back down to data architecture. So the next question I asked, cause I had a great country with the Fiddler AI CEO, CEO earlier, and he was at Facebook and then Pinterest, he was a data, you know, an architect and built everything. He said themselves. We were talking about all the stuff that's available now are all the platforms and tools available to essentially build the next Facebook if someone wanted to from scratch. I mean, hypothetically thought exercise. So the ability to actually ramp up and code a complete throwaway and rebuild from the ground up is possible. >>Absolutely. >>And so the question is, okay, how do you do it? How long would it take? I mean, in an ideal scenario, not, you know, make some assumptions here, you got the budget, you got the people, how long to completely roll out a brand new platform. >>Now it's funny, you asked that because about a year ago I was asked that exact same question by a customer that was in the religious space that basically wanted to build a combination of Facebook, Netflix, and Amazon altogether for the religious space, for religious goods and you know, church sermons, we estimated for him about a year and about $9 million to do it. >>I mean, that's a, that's a, a round these days. Yeah. Series a. So it's possible. Absolutely. So enterprises, what's holding them back, just dogma process, old school legacy, or are people taking the bold move to take more aggressive, swiping out old stuff and just completely rebuilding? Or is it a talent issue? What's the, what's the enterprise current mode of reset, >>You know, I think it really depends on the enterprise and their aversion to risk. Right. You know, some enterprises and companies are really out there wanting to innovate, you know, I mean there's companies, you know, an air conditioning company that we worked with, that's totally, you know, nest was eaten all their business. So they came in and created a whole T division, you know, to, to chase that business, that nest stole from them. So I think it, I think often a company's not necessarily gonna innovate until somebody comes in and starts stealing their >>Lunch. You know, Ryan, Andy, Jess, we talked about this two reinvents ago. And then Adam Eski said the same thing this year on a different vector, but kind of building on what Andy Jessey said. And it's like, you could actually take new territory down faster. You don't have to kill the old, no I'm paraphrasing. You don't have to kill the old to bring in the new, you can actually move on new ideas with a clean sheet of paper if you have that builder mindset. And I think that to me is where I'm seeing. And I'd love to get your reaction because if you see an opportunity to take advantage and take territory and you have the right budget time and people, you can get it. Oh absolutely. It's gettable. So a lot of people have this fear of, oh, we're, that's not our core competency. And, and they they're the frog and boiling water. >>You know, my answer to that is I think part of it's VCs, right? Yeah. VCs have come in and they see the value of a company often by how many people you hire, right. Hire more people. And the value is gonna go up. But often as a startup, you can't hire good people. So I'm like, well, why are you gonna go hire a bunch of random people? You should go to a firm like ours that knows AWS and can build it quickly for you, cuz then you're gonna get to the market faster versus just trying to hire a bunch of people in >>Someone. Right. I really appreciate you coming on. I'd love to have you back on the cube again, sometime your expertise and your insights are awesome. Give a commercial for the company, what you guys are doing, who you're looking for, what you want to do, hiring or whatever your goals are. Take a minute to explain what you guys are doing and give a quick plug. >>Awesome. Yeah. So mission cloud, you know, we're a premier AWS consulting firm. You know, if you're looking to go to AWS or you're in AWS and you need help and support, we have a full team, we do everything. Resell, MSP professional services. We can get you into the cloud optimize. You make everything run as fast as possible. I also have a full machine learning team. Since we're here at re Mars, we can build you models. We can get 'em into production, can make sure everything's smooth. The company's hiring. We're looking to double in size this year. So, you know, look me up on LinkedIn, wherever happy to, to take, >>You mentioned the cube, you get a 20% discount. He's like, no, I don't approve that. Thanks for coming on the key. Really appreciate it. Again. Machine learning swaping said on stage this, you can be a full time job just tracking just the open source projects. Never mind all the different tools and like platform. So I think you're gonna have a good, good tailwind for your business. Thanks for coming on the queue. Appreciate it. Ryan Reese here on the queue. I'm John furry more live coverage here at re Mars 2022. After this short break, stay with us.

(upbeat music) >> Hello, everyone. Welcome to "theCUBE's" coverage of the International Women's Showcase, 2022. I'm your host, Lisa Martin. I'm pleased to be joined by my next guest, Madhura DasGupta Sinha, the founder and CEO of Aspire For Her. Madhura, it's great to have you on the program. >> It's lovely to be here on this program. Thank you for having me, Lisa >> Tell me a little bit about your background. >> Lisa, I have been a banker for the last 25 years but the last two years of my journey have been professionally and personally the most satisfying and fulfilling. On 8th of March, 2020, I started Aspire For Her. So today is our second birthday. >> Lisa: Happy birthday. >> Thank you, Lisa >> Tell us a little bit about Aspire For Her >> It's been a wonderful journey. >> Yeah, what was the genesis of it? You're obviously very passionate about it but talk to us about the Genesis of Aspire For Her. >> Thank you for the question. I was looking at gender data emanating from India and that left me fairly disturbed and distressed, why? Well, I was looking at the economic participation of women and I realized that we are absolutely at the bottom of a list of 156 countries. I felt someone needs to do something about this problem and I thought that someone could be me. >> And so two years ago you launched Aspire For Her. Talk to me about what that has achieved in its first two years and now embarking on year three. >> Well, I think our journey has been absolutely fascinating Today we have more than 120,000 members, mentors, supporters across the globe, across 60 different countries. We have more than 150 women leaders who are mentors at Aspire For Her, we have about 50 organizations that are working with us jointly and partnering with us in our journey to motivate more women to enter and stay in the workforce. Our vision is to add more than 1 million women to the workforce by 2025 and 10 million women to the workforce by 2030 and we want to do that by using the power of networks and communities. >> Those are really lofty goals, but fantastic. You mentioned and across 60 countries so far and we're talking about just on your second birthday, all of that you've accomplished. Talk to me a little bit about some of the mentors and how did you find some of these people? >> Well, Lisa, we use a unique five point model to change mindsets, and the first pillar in that model is mentors and role models. Because we notice that four out of five women have no successful, professional women role models in their immediate network. We give them access. So these mentors are CEOs, CXOs, women leaders who have built businesses who want to give back and they come to us and want to be part of Aspire For Her. They are a big part of our equation for success. The second pillar that we work on is learning opportunities and we work with organizations like Amazon and many others to ensure that our members stand head over shoulders over others when they are being looked at for jobs and recruitment opportunities. The third pillar that we work on is what we call career previews. Now, if you are wanting to get women excited about careers we have to understand one thing, if she can see it, she can be it. That's the mantra that we follow as we open up doors and windows of women's minds to new age career options. The fourth pillar that we work on is what we call a peer community. And what we notice is that the community connects with each other, motivates each other and elevates each other and collectively finds solutions to problems. The fifth pillar that we work with is what we call 3E, employment, entrepreneurship, or education. We want every woman in our country and across the globe to be in 3E. We want every woman to be financially independent because financial independence is the cornerstone of all other forms of independence and that is how we can break all biases. >> That is fantastic. The five point model, how it leads of the 3E's. Something you said really resonated with me and that is: if she can see it, she can be it. And we often say, we can't be what we can't see but I love this spin that you've taken on that, you've put that positive mindset, if she can see it, we want to enable her to see it across the globe. As you talked about your goals of a million women in the workforce by 2025 which is just a few years down the road, you're well on your way to accomplishing that. Talk to me about some of the data. I know you have some interesting data from McKinsey that really supported the genesis of Aspire For Her. >> Yes, Lisa, in fact, there's a report for the "Power Of Parity" report which McKinsey publishes from time to time and I notice some very interesting data in that. McKinsey says, "If we have a little more "than 10% women more in the workforce "this will be a trillion dollar opportunity for India. "A 27% increase in our GDP." So if we get more women to work, it essentially means that they will add to their families, to their country, to their society, to the world. >> So the data is there showing just a 10% increase in women in the workforce leads to a 27% increase in India's GDP. We're talking about India alone here. Talk to me about how are you working with companies like AWS to help Aspire For Her achieve it's lofty goals. >> AWS has been an absolutely wonderful partner for us. And let me start by talking about the She Dares community, their focus on diversity and their thought leadership has been absolutely wonderful for us. Well, the She Dares community is meant for all women who want to be in tech careers whether today they're in school or in college or they're working in non-tech fields, but are interested in technology as a career option or they're taking a break and they wish to come back into the workforce. The AWS She Dares community welcomes all women like this. It's very inclusive, all embracive and that's what we love about building the community with AWS. We just started two months ago and today we have more than 10,000 members in India and we've had some fantastic stories also emanating from the She Dares community in AWS. >> I love that. You've 10,000 members in two months, the Aspire For Her program, not only does it have lofty goals but you've got a really fast growth trajectory. Share a story with me, if you will of a woman that that is in the She Dares program and where she came from and where she is now. >> Yes, let me share the story of Usha and we just shared this at the launch of AWS, just a couple of days back, Lisa. So Usha worked for just two years and the next 16 years of her life, she devoted to bringing up her family. A few years back, her husband suffered Parkinson's disease and she realized that the entire weight of the family was on her so she decided to join She Dares. She decided to sign up for the AWS cloud certification program. How did she do it? Well, she had the entire family's burden on her. She worked night and day, but somehow she squeezed out hours during the night where she would sit and study and ensured that she got certified. Remember, this was a woman who just spent two years in the workforce and the next 16 years, she had absolutely no connection with anything that was even remotely career oriented. But after getting certified and getting motivated by the community of She Dares, she decided to give it a shot and apply for a job with AWS. Two days ago, she got her offer letter. So today, she's proud-- >> What a fantastic story going from two years in the workforce, 16 years taking care of her family then the burden is on her with her husband falling ill and she finds this opportunity. I love the message there. How do you talk to women who might be in similar situations to Usha going, "I haven't been in the workforce "for a really long time, Tech seems intimidating." How do you help them achieve the courage to go forward >> Lisa, it's the same five point model that we use. If she can see it, she can be it. If she can see a role model like Usha, a woman who has been out of the workforce for a long time finds the confidence, finds her voice and finds the ability to just rise up above that adversity and ensure that she jumps right back into the workforce. >> And is Aspire For Her focused on STEM only, or are you focused on all industries for women? >> We are focused on all industries for women and we like to look at fairly new age careers as well. So whether it's an Instagram influencer, whether it's somebody who's opened patisserie for the best brownies in town, we like to celebrate all women and all their career paths, but STEM is a very important part of what we do because we know that the STEM skills gap in India and globally is a very serious problem and if we train women and reskill women in STEM, they will automatically gravitate towards those roles which will open up in the India of tomorrow. >> Are you able to reach young girls like say in primary school and high school as well, is this open to women of all ages? >> It's open to women of all ages. We like to start at the age 16 because that's when women start taking career decisions whether it's about writing competitive exams or whether it's about looking at which colleges they will get into so we like to start at 16 and there's really no age limit. >> That's fantastic that there's no age limit but also starting young. One of the things that we know about the tech industry is the percentage of women in technical roles is quite low, I believe it's below 25% and has been for quite some time. We see that in a lot of countries that drop off around the high school, 16 year age, how do you help attract these young girls to be interested in not just STEM but in creating a career for herself? >> So we like telling a lot of stories, Lisa, and there are constant nudges and triggers on our platform. So today I'm speaking with you and I'm sure that this will be beamed across our platforms as well, And people will look at Lisa and say, "Hey Lisa is doing this fantastic thing as a host. "And she's working with this great organization. "Why can we not be like Lisa?" And that's the way in which we motivate folks. And we try to ensure that every woman with a career story comes in and is able to share her journey, her path with our larger community whether that's through mentorship sessions, whether that's through role modeling, whether it's through coaching, whether it's through many fireside chats that we have, we have a lot of workshops and webinars. We are a COVID baby so we are very digital and we love technology. So that's how we try to create the community, ensure that there is enough excitement going every minute of the day. It's a very buzzing, humming, active community and we ensure that finally, everyone has that one thing in mind: I have to be financially independent and I cannot ever give up on my career. >> I love that: Be financially independent and not give up on my career. You must be obviously, very intentionally, you launched Aspire For Her, you mentioned two years ago today, on the 8th of March, 2020 right in the very onset of COVID but also on International Women's Day. Talk to me a little bit about why that was so important to launch on that day in International Women's history month. >> Well, when I was looking at the problem that was staring at women in India there's another interesting piece of statistic that's struck, which was that the percentage of women in the workforce has been declining steadily in India. And I thought that someone needed to do something about that problem, and I thought that someone could be me. I'm not a great one for symbols but I thought that if we launch it on Women's day, this will be a constant reminder for us to strive harder to get to those numbers quicker than we have set ourselves up for. That's the reason why I decided when the world was talking about women, it's a great idea for this to be like a conscience keeper for us. >> Perfect timing. Well, congratulations on all of the success that you have achieved in just a short two year time period. I can't wait to see what year three brings and sign me up to be a mentor. I'm a woman in STEM, I'm a woman that hosts this program. I would love to get involved and help encourage girls and other women to follow their passion. >> That is so amazing, Lisa, you are on and we'd love to welcome you aboard as a mentor >> Oh, excellent! Lucky me, my lucky day. Madhura, thank you so much for talking with us about Aspire For Her, and again, congratulations on all of your success. >> Thank you. >> And Madhura, you've got one final message for AWS employees that you want to leave, what is that? >> Thank you, Lisa, for the question, there is a message that I'd like to leave for all AWS employees across the globe, join us, be a part of our movement, it takes about three minutes to sign up for Aspire For Her. Please be a part of the change that you wish to see. Thank you. >> Well, Madhura again, it's been a pleasure talking to you. Congratulations on the success, the momentum that you have achieved in such a short time period. We appreciate your insights and your time. >> Thank you so much, Lisa, thank you, thank you, and I am going to send you the form to become a mentor as well (chuckling). >> I'm in, sign me up. >> Thank you >> For Madhura DasGupta Sinha, I'm, Lisa Martin, you're watching "theCUBE's" coverage of International Women's Showcase, 2022. (upbeat music)

(bright upbeat music) >> Welcome to theCUBE's, continuous coverage of AWS re:Invent 2021. We're here live running one of the most important and largest technology events of the year. It's all about AWS and AWS's ecosystem partners. We are joined by Jay Mozo, Director of Transformation Services, TEKsystems Global Services, alumni of AWS, >> Yep. >> David: I got that, right? >> Yep. >> David: And Ted Swinyar, you're Director of Solutions 1Strategy. Who's going to tell me what the relationship is between 1Strategy and TEKsystems? Like I don't already know what it is since you came and essentially announced the magic, here on our stage in 2019. Ted, you want to start off with a little background since you were acquired. >> Ted: Yeah, I'll jump in. >> How did that go? >> So 1Strategy is a TEKsystems Global Services Company, and we're an AWS premier partner. We've got competencies and DevOps, migration, data and analytics, machine learning. And we're really excited this year to be focusing also on the security competency as well. >> So you've been laser focused on AWS forever? >> Ted: Day one. >> Day one. >> Ted: You know that's been our core focus, and together with TEKsystems Global Services, we're able to bring that dedicated and specialized focus on cloud transformation now at scale. And that's really exciting. >> So TEKsystems, you do it all? >> Yep. >> AWS laser-focused, sounds like a great combination. >> Ted And Jay: Yeah. >> And our focus is you know, how we bring that deep AWS specialized expertise together with proven methodologies, the proprietary deployment strategies to take the customer to the next step on their cloud journey. Whether they're just getting started, whether they're in a migration or whether they're already a veteran at AWS looking to take the next step. >> So Jay talk about the last two years. >> Jay: Yeah. >> You've been in this two years obviously very interesting times we've been living through. How has the combination gone? >> Oh it's been great again that expertise, that deep AWS expertise, that's what our customers (indistinct), they would expect from us, right? And we truly are passionate about accelerating business transformation for our customers, right? And our goal is really simple, we bring in real-world expertise, just like an AWS expertise that 1Strategy brought and we solve complex problems whether they're business, technology, or even just people talent, right? The whole talent around this whole ecosystem, we heard Adam talk about it even earlier today, right? Talent is a challenge. So we're very obsessed with technology, right? But we're even more than that we're obsessed with our customers, right? We're at 80% of the fortune 500, more than 6,000 customers, and that obviously grew with our 1Strategy partners here. And we really consider ourselves with 1Strategy as all in one kind of full stack integration partner, right? Well we meet our customers where they are and we work side by side with them to transform their business, again very passionate about that. >> So what do these engagements look like? Are you approaching the customer from an AWS perspective in partnership with AWS? So AWS services, AWS technology, bridging that divide specifically, or are you coming in from sort of a TEKsystems overall perspective and then identifying the areas where AWS is a fit and bringing in 1Strategy? Or is it a mixture of both? What does that look like? >> It's a mixture of both for sure. We do a lot of partnering with AWS, right? Especially with 1Strategy. And we come to the table a lot with AWS together and we have that kind of joint feeling with AWS. And when AWS isn't at the table in the beginning, if it makes sense to go on the AWS platform, we bring them to the table. But it's really around focusing on what you're bringing up, it's focusing on the customer and what they need. And again, we have our kind of business modernization framework that we lean on, that really drives that conversation, so we can figure out very quickly, you know, how to help them and which platform is going to help them. And obviously, you know, AWS more and more, right? They're coming out with all these services, even a higher level services. And the conversations with our customers are really along those lines, right? How do we kind of help them leverage these services, right? So they can really achieve the agility that they need. >> So in the last two years, aside from the pandemic, global economy, what are some of the things in cloud that maybe you didn't anticipate? Now you're coming in from a specialist perspective, Laser focused on AWS, more the generalist, let's take care of anything the customer might need. Are there areas where you are surprised by the pace or a lack of pace in terms of movement to cloud? What have the last two years looked like from that perspective? >> Well I'll say one of the big things has been the change in data. The data is a lifeblood of every organization and what looks like normal data today, would be alien for some businesses going back two years ago. And as the entire world has gone through a business transformation, there's been just more and more data coming at customers faster and faster, the acceleration there has been just tremendous. And one of the things we see, customers are just drowning in data, you know how they're able to leverage AWS from a technology standpoint to build a data strategy, has to be married with that data-driven culture. And we're seeing more and more customers really getting that. I thought Adam made an incredible point this morning, he called out 85% of the workers surveyed, in the past couple of years are saying, I need to understand technology more. And that's absolutely something we're seeing in the marketplace. That investment in your team, enablement training as well as having the solid foundation and an ability to move toward an agile approach is becoming more and more critical for our customers. >> So you mentioned Adam's keynote, one of the things that was called out, was the idea that there are 475 different kinds of instances available from AWS. So let's get tactical for a minute, pretend like I'm a CEO at a customer site. I know that I want to be in the cloud, I know I want to leverage what the cloud has to offer. How do you guys figure out which ones of these 475 instances I'm going to be leveraging? Do you have like multisided dungeons and dragons dice that you throw, (murmuring) or is there some science behind it? >> Oh man that and the dart board definitely the way to go. No, the idea for every engagement is always focused on what the outcome for the customer is at the end of the day and work backwards from that. So depending on whether they're focused on an ML workload, or whether they're focused on a more, business line application, working backwards to understand what is the outcome they're trying to drive and then building the right technology stack, working backwards to support that. Whether it's taking advantage of any number of the instance types, taking advantage of serverless or any of the really incredible container options that are available in the marketplace today. >> So we're obviously here at AWS re:Invent, 1Strategy is an AWS specialist, TEKsystems multicloud? >> Jay: Yep. >> Fair to say? >> Jay: Yep. >> The world is a multicloud place, I think it's okay to acknowledge that. So if I'm looking to engage with TEKsystems, I can count on AWS being brought in and AWS expertise being brought in when it's appropriate, because it's not the only thing you do? >> Jay: Right, that's right. >> How do you manage that? Who decides whether a workload is better suited for AWS and the 1Strategy folks versus say GCP or Azure? >> Yeah, definitely again, (indistinct) right on it, right? We start with what the customer needs and their outcomes, right. We take an approach around really helping them understand their value stream, right? So if we get our customers to understand their value stream, that really serves as a context, as I mentioned before for business and delivery agility, right? And when we focus there and work backwards from there, we can really figure out all the different pieces. And like you said, it's a multicloud world now, right? For with many of our customers demand their value streams and some of their value stream components or systems or processes, they might live on different things. But, we don't jump to those right out of the gate, right? We jump to understanding where they are in their journey, where they're at with their value stream. We do a lot of dive deep and aligned to really understand where they're at. And then we craft those things actually in partnership with our customer, right? Because they might have things going on in their organization that might lean towards, GCP for some things and AWS for some other things. So we take all of that in as we start to figure out, which platform really is best for them. But again, like Ted mentioned, we with that working backwards mentality. >> So how do you see the change that's happened over time, in I would call it the AWS posture or attitude towards the concept of hybrid cloud technology? I think there was a time when AWS would have said, you know what everything that matters, everything that's born now will be born in the cloud, all net new things will be in the cloud. All the legacy stuff, we'll just sort of let it wither on the vine. It was mentioned in the keynote today that maybe five to 15% of I.T spend is in the cloud today, that's 85% or so leftover. Do you find yourself working in more of an increasingly hybrid environment these days? What's your perspective on hybridity? I think I may have just made that word up. (chuckles) >> Yeah it's absolutely the reality, and it reflects where every customer is in their cloud journey. You know you've got some customers that are just born in the cloud startups, getting you know everything Greenfield, brand new in the cloud. Whereas you've got others, one of our customers just celebrated recently their hundredth birthday. Obviously they have a significant legacy domain and we always need to focus on meeting a customers where they're at. There's no exact match between customer and customer, it's all about understanding where they are, how we can help them get to the next step, whether that's taking advantage of something like outpost, you know the really cool 5G, the private 5G that was announced this morning. Really exciting. >> David: Very interesting. >> Ted And Jay: Yeah. >> We were talking about that beforehand, how that might support industry 4.0 and some of the really interesting opportunities in that regard. Wavelength, another great example, the reality is AWS has gone into the data center now with things like outposts. It's even gone into space with things like ground station, so it's everywhere that our customers are. >> You mentioned 5G from a TEKsystems perspective, what do you do? Do you spin up a 5G practice? Do you scour universities for 5G graduates? How do you keep up with the pace of developments that are coming from AWS let alone the rest of the tech sector? >> Yeah, and again that 5G is a good example, right? And we're going to kind of follow again where our customer are and where the trends going. But we instantly see with these higher level services, where some of these used cases, some of these solutions are going to go, right? We were even talking again that conversation about, the things we can do from an industry perspective, right? And really align all of these technologies to again be very innovative, right? Adam talked about pathfinders and again, we're going to seek out those pathfinders. And now with all of these services coming out of AWS, we're going to be able to do some incredible things in the future with them. >> Yeah it's amazing to see the things that have been unlocked and unshackled by advances in technology. Were there any things that surprised you Ted, coming out of the keynote today, announcements, some of these things are sort of telegraphed in advance. But hardware advances, we talked about 5G, anything that kind of took you off guard a bit or... >> I was really excited by all the move to serverless analytics, Redshift server lists, EMR with serverless MSK serverless, democratization of data. Again coming back to the pathfinders theme, going all the way back to the very beginning, how we can bring that data forward and lowering those bars. Whether you're focused on ML with the SageMaker announcements, and SageMaker canvas, being able to bring all these people together and empower them with data. I see that as again, a lifeblood of every organization and the more that you can bring that out and make it available, the more powerful and the more flexible every company is going to be. >> When you're an AWS services partner, it's a bit like being at a buffet, an endless buffet where new treats are piled on the table each year. I thought it was amazing that one of the important points had to do with the development of Silicon. There are a lot of folks who would say that the underlying hardware no longer matters, nobody cares. AWS realizes that as a foundation it is really important, it's up to folks like you to translate that technical value into business value obviously. If this whole tech thing doesn't work out for us, what if we opened a nightclub here in Vegas and we called it hybridity? >> (Jay laughing) I like >> Love it. >> I like the sound of it, I'm going to look it up and see if it's actually a word. >> Lets patent it. (murmuring) >> We got it all three of us. So anytime organizations come together, there are cultural issues. So you've got AWS specialist, more of a generalist organization and you're going out and you're engaging customers that are having their own cultural issues. What are some of the bigger obstacles that are in the way of leveraging technology? 'Cause you've mentioned it's all about the customer perspective it's not just the technology. What are the things that are still getting in the way now that might surprise people who think that everyone's already in cloud? >> Yeah, I can go first, Ted you can jump in. Yeah culture is, again, it's a big thing, that's why it's built into our business modernization program, culture, continuous learning and Adam mentioned that too. We see challenges obviously from a learning perspective. We really, really need to key in on, not just the technologies they have to learn, but also modern practices, right? And that's going to be a big part of all these things. And definitely these higher level services are going to abstract a lot of those issues for our customers which is great. But it's still not going to displace just the constant you brought up, the constant change and all these services that come out. So I think we focus on a culture and really understanding how to move an organization to the right mindsets and the right practices, right? And that's really the key in terms of their overall business transformation. >> So I think the headline for this segment is going to be awesome two years for TEKsystems and 1Strategy. Jay and Ted, thank you so much for being here on theCUBE with us. I hope you have a great rest of the week here in Las Vegas, it's amazing to be here in person, fantastic. They've done a really good job of keeping us all safe with the protocols in place. Hope to see you again, I guess we'll be shooting for a 2022 update to see how you guys are doing. With that I'd like to thank all of you for joining us on theCUBE here at AWS re:Invent 2021. I'm Dave Nicholson and again thanks for joining us on theCUBE. We are the leader in hybrid technology event coverage. (bright music)

>>Yeah. Hello and welcome back to the cubes coverage of AWS public sector summit here in Washington D. C. We're live on the ground for two days. Face to face conference and expo hall and everything here but keith brooks who is the director and head of technical business development for a dress government Govcloud selling brains 10th birthday. Congratulations. Welcome to the cube. Thank you john happy to be E. C. 2 15 S three is 9.5 or no, that maybe they're 10 because that's the same day as sqs So Govcloud. 10 years, 20 years. What time >>flies? 10 years? >>Big milestone. Congratulations. A lot of history involved in Govcloud. Yes. Take us through what's the current situation? >>Yeah. So um let's start with what it is just for the viewers that may not be familiar. So AWS Govcloud is isolated. AWS cloud infrastructure and services that were purposely built for our U. S. Government customers that had highly sensitive data or highly regulated data or applications and workloads that they wanted to move to the cloud. So we gave customers the ability to do that with AWS Govcloud. It is subject to the fed ramp I and D O D S R G I L four L five baselines. It gives customers the ability to address ITAR requirements as well as Seaga's N'est ce MMC and Phipps requirements and gives customers a multi region architecture that allows them to also designed for disaster recovery and high availability in terms of why we built it. It starts with our customers. It was pretty clear from the government that they needed a highly secure and highly compliant cloud infrastructure to innovate ahead of demand and that's what we delivered. So back in august of 2011 we launched AWS GovCloud which gave customers the best of breed in terms of high technology, high security, high compliance in the cloud to allow them to innovate for their mission critical workloads. Who >>was some of the early customers when you guys launched after the C. I. A deal intelligence community is a big one but some of the early customers. >>So the Department of Health and Human Services, the Department of Veterans Affairs, the Department of Justice and the Department of Defense were all early users of AWS GovCloud. But one of our earliest lighthouse customers was the Nasa jet propulsion laboratory and Nasa Jpl used AWS GovCloud to procure Procure resources ahead of demand which allowed them to save money and also take advantage of being efficient and only paying for what they needed. But they went beyond just I. T. Operations. They also looked at how do they use the cloud and specifically GovCloud for their mission programs. So if you think back to all the way to 2012 with the mars curiosity rover, Nasa Jpl actually streamed and processed and stored that data from the curiosity rover on AWS Govcloud They actually streamed over 150 terabytes of data responded to over 80,000 requests per second and took it beyond just imagery. They actually did high performance compute and data analytics on the data as well. That led to additional efficiencies for future. Over there >>were entire kicking they were actually >>hard core missing into it. Mission critical workloads that also adhere to itar compliance which is why they used AWS GovCloud. >>All these compliance. So there's also these levels. I remember when I was working on the jetty uh stories that were out there was always like level for those different classifications. What does all that mean like? And then this highly available data and highly high availability all these words mean something in these top secret clouds. Can you take us through kind of meetings >>of those? Yeah absolutely. So it starts with the federal compliance program and the two most popular programs are Fed ramp and Dodi srg fed ramp is more general for federal government agencies. There are three levels low moderate and high in the short and skinny of those levels is how they align to the fisma requirements of the government. So there's fisma low fisma moderate fisma high depending on the sensitivity of the government data you will have to align to those levels of Fed ramp to use workloads and store data in the cloud. Similar story for D. O. D. With srg impact levels to 45 and six uh impacts levels to four and five are all for unclassified data. Level two is for less sensitive public defense data levels. Four and five cover more sensitive defense data to include mission critical national security systems and impact level six is for classified information. So those form the basis of security and compliance, luckily with AWS GovCloud celebrating our 10th anniversary, we address Fed ramp high for our customers that require that and D. O. D impact levels to four and five for a sensitive defense guy. >>And that was a real nuanced point and a lot of the competition can't do that. That's real people don't understand, you know, this company, which is that company and all the lobbying and all the mudslinging that goes on. We've seen that in the industry. It's unfortunate, but it happens. Um, I do want to ask you about the Fed ramp because what I'm seeing on the commercial side in the cloud ecosystem, a lot of companies that aren't quote targeting public sector are coming in on the Fed ramp. So there's some good traction there. You guys have done a lot of work to accelerate that. Any new, any new information to share their. >>Yes. So we've been committed to supporting the federal government compliance requirements effectively since the launch of GovCloud. And we've demonstrated our commitment to Fed ramp over the last number of years and GovCloud specifically, we've taken dozens of services through Fed ramp high and we're 100% committed to it because we have great relationships with the Fed ramp, Jabor the joint authorization board. We work with individual government agencies to secure agency A. T. O. S. And in fact we actually have more agency A. T. O. S. With AWS GovCloud than any other cloud provider. And the short and skinny is that represents the baseline for cloud security to address sensitive government workloads and sensitive government data. And what we're seeing from industry and specifically highly regulated industries is the standard that the U. S. Government set means that they have the assurance to run control and classified information or other levels of highly sensitive data on the cloud as well. So Fed ramp set that standard. It's interesting >>that the cloud, this is the ecosystem within an ecosystem again within crossover section. So for instance um the impact of not getting Fed ramp certified is basically money. Right. If you're a supplier vendor uh software developer or whatever used to being a miracle, no one no one would know right bed ramp. I'm gonna have to hire a whole department right now. You guys have a really easy, this is a key value proposition, isn't it? >>Correct. And you see it with a number of I. S. V. S. And software as the service providers. If you visit the federal marketplace website, you'll see dozens of providers that have Fed ramp authorized third party SAAS products running on GovCloud industry leading SAAS companies like Salesforce dot com driven technology Splunk essay PNS to effectively they're bringing their best of breed capabilities, building on top of AWS GovCloud and offering those highly compliant fed ramp, moderate fed ramp high capabilities to customers both in government and private industry that need that level of compliance. >>Just as an aside, I saw they've got a nice tweet from Teresa Carlson now it's plunk Govcloud yesterday. That was a nice little positive gesture uh, for you guys at GovCloud, what other areas are you guys moving the needle on because architecturally this is a big deal. What are some areas that you're moving the needle on for the GovCloud? >>Well, when I look back across the last 10 years, there were some pretty important developments that stand out. The first is us launching the second Govcloud infrastructure region in 2018 And that gave customers that use GovCloud specifically customers that have highly sensitive data and high levels of compliance. The ability to build fault tolerant, highly available and mission critical workloads in the cloud in a region that also gives them an additional three availability zones. So the launch of GovCloud East, which is named AWS GovCloud Us East gave customers to regions a total of six availability zones that allowed them accelerate and build more scalable solutions in the cloud. More recently, there is an emergence of another D O D program called the cybersecurity maturity model, C M M C and C M M C is something where we looked around the corner and said we need to Innovate to help our customers, particularly defense customers and the defense industrial based customers address see MMC requirements in the cloud. So with Govcloud back in December of 2020, we actually launched the AWS compliant framework for federal defense workloads, which gives customers a turnkey capability and tooling and resources to spin up environments that are configured to meet see MMC controls and D. O. D. Srg control. So those things represent some of the >>evolution keith. I'm interested also in your thoughts on how you see the progression of Govcloud outside the United States. Tactical Edge get wavelength coming on board. How does how do you guys look at that? Obviously us is global, it's not just the jet, I think it's more of in general. Edge deployments, sovereignty is also going to be world's flat, Right? I mean, so how does that >>work? So it starts back with customer requirements and I tie it back to the first question effectively we built Govcloud to respond to our U. S. Government customers and are highly regulated industry customers that had highly sensitive data and a high bar to meet in terms of regulatory compliance and that's the foundation of it. So as we look to other customers to include those outside of the US. It starts with those requirements. You mentioned things like edge and hybrid and a good example of how we marry the two is when we launched a W. S. Outpost in Govcloud last year. So outpost brings the power of the AWS cloud to on premises environments of our customers, whether it's their data centers or Coehlo environments by bringing AWS services, a. P. I. S and service and points to the customer's on premises facilities >>even outside the United States. >>Well, for Govcloud is focused on us right now. Outside of the U. S. Customers also have availability to use outpost. It's just for us customers, it's focused on outpost availability, geography >>right now us. Right. But other governments gonna want their Govcloud too. Right, Right, that's what you're getting at, >>Right? And it starts with the data. Right? So we we we spent a lot of time working with government agencies across the globe to understand their regulations and their requirements and we use that to drive our decisions. And again, just like we started with govcloud 10 years ago, it starts with our customer requirements and we innovate from there. Well, >>I've been, I love the D. O. D. S vision on this. I know jet I didn't come through and kind of went scuttled, got thrown under the bus or whatever however you want to call it. But that whole idea of a tactical edge, it was pretty brilliant idea. Um so I'm looking forward to seeing more of that. That's where I was supposed to come in, get snowball, snowmobile, little snow snow products as well, how are they doing? And because they're all part of the family to, >>they are and they're available in Govcloud and they're also authorized that fed ramp and Gov srg levels and it's really, it's really fascinating to see D. O. D innovate with the cloud. Right. So you mentioned tactical edge. So whether it's snowball devices or using outposts in the future, I think the D. O. D. And our defense customers are going to continue to innovate. And quite frankly for us, it represents our commitment to the space we want to make sure our defense customers and the defense industrial base defense contractors have access to the best debris capabilities like those edge devices and edge capable. I >>think about the impact of certification, which is good because I just thought of a clean crows. We've got aerospace coming in now you've got D O. D, a little bit of a cross colonization if you will. So nice to have that flexibility. I got to ask you about just how you view just in general, the intelligence community a lot of uptake since the CIA deal with amazon Just overall good health for eight of his gum cloud. >>Absolutely. And again, it starts with our commitment to our customers. We want to make sure that our national security customers are defense customers and all of the customers and the federal government that have a responsibility for securing the country have access to the best of breed capability. So whether it's the intelligence community, the Department of Defense are the federal agencies and quite frankly we see them innovating and driving things forward to include with their sensitive workloads that run in Govcloud, >>what's your strategy for partnerships as you work on the ecosystem? You do a lot with strategy. Go to market partnerships. Um, it's got its public sector pretty much people all know each other. Our new firms popping up new brands. What's the, what's the ecosystem looks like? >>Yeah, it's pretty diverse. So for Govcloud specifically, if you look at partners in the defense community, we work with aerospace companies like Lockheed martin and Raytheon Technologies to help them build I tar compliant E. R. P. Application, software development environments etcetera. We work with software companies I mentioned salesforce dot com. Splunk and S. A. P. And S. To uh and then even at the state and local government level, there's a company called Pay It that actually worked with the state of Kansas to develop the Icann app, which is pretty fascinating. It's a app that is the official app of the state of Kansas that allow citizens to interact with citizens services. That's all through a partner. So we continue to work with our partner uh broad the AWS partner network to bring those type of people >>You got a lot of MST is that are doing good work here. I saw someone out here uh 10 years. Congratulations. What's the coolest thing uh you've done or seen. >>Oh wow, it's hard to name anything in particular. I just think for us it's just seeing the customers and the federal government innovate right? And, and tie that innovation to mission critical workloads that are highly important. Again, it reflects our commitment to give these government customers and the government contractors the best of breed capabilities and some of the innovation we just see coming from the federal government leveraging the count now. It's just super cool. So hard to pinpoint one specific thing. But I love the innovation and it's hard to pick a favorite >>Child that we always say. It's kind of a trick question I do have to ask you about just in general, the just in 10 years. Just look at the agility. Yeah, I mean if you told me 10 years ago the government would be moving at any, any agile anything. They were a glacier in terms of change, right? Procure Man, you name it. It's just like, it's a racket. It's a racket. So, so, but they weren't, they were slow and money now. Pandemic hits this year. Last year, everything's up for grabs. The script has been flipped >>exactly. And you know what, what's interesting is there were actually a few federal government agencies that really paved the way for what you're seeing today. I'll give you some examples. So the Department of Veterans Affairs, they were an early Govcloud user and way back in 2015 they launched vets dot gov on gov cloud, which is an online platform that gave veterans the ability to apply for manage and track their benefits. Those type of initiatives paved the way for what you're seeing today, even as soon as last year with the U. S. Census, right? They brought the decennial count online for the first time in history last year, during 2020 during the pandemic and the Census Bureau was able to use Govcloud to launch and run 2020 census dot gov in the cloud at scale to secure that data. So those are examples of federal agencies that really kind of paved the way and leading to what you're saying is it's kind >>of an awakening. It is and I think one of the things that no one's reporting is kind of a cultural revolution is the talent underneath that way, the younger people like finally like and so it's cooler. It is when you go fast and you can make things change, skeptics turned into naysayers turned into like out of a job or they don't transform so like that whole blocker mentality gets exposed just like shelf where software you don't know what it does until the cloud is not performing, its not good. Right, right. >>Right. Into that point. That's why we spend a lot of time focused on education programs and up skilling the workforce to, because we want to ensure that as our customers mature and as they innovate, we're providing the right training and resources to help them along their journey, >>keith brooks great conversation, great insight and historian to taking us to the early days of Govcloud. Thanks for coming on the cube. Thanks thanks for having me cubes coverage here and address public sector summit. We'll be back with more coverage after this short break. Mhm. Mhm mm.

>> Welcome to the AWS Startup Showcase: New Breakthroughs in DevOps, Data Analytics, and Cloud Management Tools. I'm Lisa Martin. I'm pleased to welcome JT Giri, the CEO and founder of nOps, to the program. JT, welcome. It's great to have you. >> Thank you, Lisa. Glad to be here. >> Talk to me about nOps. This was founded in 2017, you're the founder. What do you guys do? >> Yeah. So just a little bit background on myself. You know, I've been migrating companies to AWS ever since EC2 was in beta. And you know, in the beginning I had to convince people like, "Hey, you should move to cloud." And the question people used to ask me, like, "Is cloud secure?" I'm glad no one is asking that question anymore. So, as I was building and migrating customers to the cloud, one of the things I realized very early on, is just cloud, there are so many resources, so many teams provisioning resources, then how do you align with your business goals? So we created nOps so that, for a mission, how do you are you build a platform where you make sure every single change and every single resource in the cloud is aligned with the business needs, right? Like we really helped people to make the right trade-offs. >> So you mentioned you've been doing this since EC2 was in beta, and we just celebrated, with AWS, EC2's 15th birthday. So you've been doing this awhile. You don't look old enough, but you've been doing this for awhile. So one of the things that I read on the website, I always love to understand messaging, that nOps says about itself, "The first cloud ops platform "designed to sync revenue growth across your teams." Talk to me about how you do that. >> Yeah. So one of the problems we see in the market right now, there are a lot of tools, there are a lot of dashboards that shows like, "Hey, you have this many issues, "here's the opportunity to fix issues. "And here are the security issues." We're more focused on how do we take those issues from a backlog and fixing those issues. Right? So our focus is more on operationalizing, so your teams could actually own that, prioritize, and actually remediate those issues. So that's where we focus our energy. >> Got it. Let's talk about cloud ops now, and how it varies or differs from traditional cloud management. >> Yeah, I think, like I mentioned, cloud management seems to be more like visibility. And everyone knows that there are challenges in their cloud environment. But when you focus more on the operation side, what we really try to do, from an issue, how do you actually fix that issue? How do you prioritize? How do you make the right trade-offs. Right? Trade offs is important because we make a lot of decisions in the cloud when you're building your infrastructure. Sometime you might have to prioritize for costs, sometime you might have to prioritize based on the SLA. You might have to add more resources to hit your SLAs. So we really help you to prioritize. And we build sort of accountability. You know, you can create roles. Most of the time, what we noticed, I truly believe that if it's everyone's responsibility, it's no one's responsibility. You know? So what we do is we help, within the tool, to establish clear roles and responsibilities. And we show audit log of people reviewing and fixing security issues. And we show audit log of people fixing and reviewing cost issues. That's one way we're trying to bring accountability. >> I like what you said, if everyone's responsible, then really no one is. And that seems to be a persistent problem that we see in businesses across industries, is just still that challenge with aligning IT and business. And especially with the dynamics of the market, JT, that we've seen in the last 18 months, things are moving so quickly. Talk to me about how you guys have been helping companies, especially in the last 18 months, with such change to get that alignment. So that that visibility and those clear roles are established and functional. >> Yeah. You know, what we really do is obviously listen to the customers. Right? And one of the challenges we hear over and over is like, you know, I know I have issues in the cloud environment that I really need help prioritizing. And they're really looking for a framework where they can come in and say, "Okay these are the people who are responsible for security. "These are the people who are responsible for the cost." So as part of onboarding with nOps, that's one of the things you do, you define your workloads. By the way, we automatically create your workload across all your accounts. And then we allow you to move resources around if you like. But then one of the first thing we do is assign roles and responsibilities for each one of these workloads. Oh, it's been incredible to see, when you have that kind of accountability, people actually do make sure that the resources are aligned with the business needs. >> So are you seeing, I mean, that's kind of a cultural shift. That changed management is a challenging process. How are you seeing that evolve in organizations who've been used to doing things maybe in a little bit of a blinders on kind of mode? >> Yeah. Well, changed management is an area where we spent a lot of time, because in cloud, changed management is almost like a fire hose. Right? There's so many changes and you could have 20 people or 20 different teams making changes. I think what people really want is sort of root cause analysis. Like, "Hey, this is what changed here. "Here's why it changed. "And here's how actions we could take, or you could take." So this is where we focus on this, where nOps focuses on. We really help people to show the root cause analysis, these three, four things, these three, four changes are related to this cost increase or these security issues. And we show like a clear path on taking action on those issues. >> That's critical. The ability to show the paths, to take the action to remediate or make any changes, course corrections. As we've learned in the last 18 months, real time is no longer for so many industries, a nice-to-have. The ability to be able to pivot on the fly is a survival and thriving mechanism. So that is really key. I do want to talk about the relationship with nOps and AWS. Here we are at the AWS startup showcase. Give me a little overview on the partnership. >> It's been an incredible. Like I said, I have a long history of working with AWS, and I started a consulting company, a very, very successful one. And so I have years of working with AWS partner teams. I think it's incredible. We were the first company in this, maybe not first, maybe very early. We were part of this Well-Architected framework. And when I came out of that training, the Well-Architected training, I was so excited. I was like, "Wow, this is amazing." You know? Because, to me, whenever you're building infrastructure, you really are making trade-offs. You know, sometime you optimize for cost, sometime you optimize for reliability. So it has been incredible to work with the Well-Architected team. Or Amazon also has this, another program, called FTR: Foundational Technical Review. We've been working closely with that team. So yeah, it's been amazing to collaborate with AWS. >> It sounds pretty synergistic. Have you had a chance influence infrastructure, and some of the technical direction? >> Oh, absolutely. Yeah. We work very closely. One of the cool thing about AWS is that they do take customers' feedback very, very seriously. And, Lisa, also other way around. Right? If AWS is going to build something, having that insight into the roadmap is very beneficial. Because if they're doing it, there's no point of us trying to reinvent the wheel. So that kind of synergy is very helpful. >> That's excellent. Let's talk about customers, now. I always loved talking about customer use cases and outcomes. You guys have a great story with Uber. Walk us through what the challenges were, how nOps came in, what you deployed, and how the business is being impacted positively. >> Yeah, I think Uber and all the enterprises, they sort of have the same challenge, right? There are many teams provisioning infrastructure. How do you make sure all those resources are aligned with your business needs? And in addition to that, not only you have different teams provisioning resources, there are different workloads. And these workloads have different requirements. Right? Some are production workloads, some are just maybe task workloads. So one of the things Uber did, they really embraced sort of nOps' way of managing infrastructure, building accountability, sharing these dashboards with all the different teams. And it was incredible, because within first 30 days they were able to save up to 15%. This was in their autonomous vehicle unit. And they spent a lot of money. And having to see that kind of cost saving, it was just amazing. And we see this over and over. And so like when customers are using platform, it's just incredible how much cost savings are there. >> So Uber, you said, in their autonomous vehicle department saved 15% in just the first 30 days alone. And you said that's a common positive business outcome that you're seeing from customers across industries, is that immediate cost savings. Tell me a little bit more about that as a differentiator of nOps' business. >> Yeah. Because as I mentioned earlier, one of the things we do, we bring accountability. Right? Most of the time when people, before nOps, maybe there are resources that are not accounted for. There is not clear owners, there's no budgets, there's no chargebacks. So I do think that's a huge differentiator of nOps, because, as part of onboarding, as you establish these roles and these responsibilities, you find so much unaccounted resources. And sometimes you don't even need those resources, and you shut them down. And those are the easiest next steps. Right? Like, you don't need to architect, you just shut it down. Like no one needs these resources. So that, I do believe, that's our strength. And we were able to demonstrate this over and over, this, on average, 15-30% cost saving in the first month or so. >> That's excellent. That's a lot of what customers, especially these days, are looking for, is cost optimization across the organization. What are some of the things that you've seen, that nOps has experienced in the last 18 months, with so much acceleration? Anything that surprised you, any industries that you see as really leading edge here, or prime candidates for your technology? >> Yeah. A couple of things. We see a lot of partners, a lot of other consulting company, leveraging nOps as a part of their offering. That's been amazing, we have a lot of partners who really leverage nOps as a go to market and ongoing management of their customers. And I do see that shift from the customer side as well. I think the complexity of cloud continues to kind of increase, like you just mentioned, it sounds like from last 18 months, it accelerated even more. How do you stay up to date, you know? And how do you always make sure that you're following best practices? So companies bring in partners to help them implement solutions. And then these partners are leveraging tools like nOps. And we've seen a lot of momentum around that. >> Tell me a little bit about how partners are leveraging nOps. What are some of the synergistic benefits on both sides? >> Yeah, so normally partners leverage nOps, you know, they will use it for Well-Architected assessments. And, you know, I've personally done a lot of these Well-Architected assessments. And, you know, early on, I kind of learned that, assessments are only good if you're able to move forward with fixing issues in the customer's environment. So what we really do, we really help customers, or sorry, we really help partners to actually do these Well-Architected assessments automatically. We auto discover issues, and then we help them to create proposals so they can present it to the customers like, "Hey, here are the five things we can help you with, "and here's how much it will cost." And, you know, we really streamline that whole process. And it's amazing that some partners used to take like days to do these assessments. Now they can do it an hour. And we also increase the close rate on SoW's because they are a lot more clear. You know, like here are the issues and here's how we can help you to fix those issues. >> You got some great business metrics there, in terms of speed and reduction in cost, reduction in speed. But it sounds like what you're doing is helping those partners build a business case for their customers far more efficiently and more clearly than they've ever been able to do before. >> Absolutely. Yeah, yeah. And... >> Go ahead. >> Yeah, so absolutely. Before nOps, everyone is using spreadsheets most of the time. Right? It's spreadsheets to collect information, and emails back and forth. And after the partner's start using nOps, they use nOps to facilitate these assessments. And once they have these customers as ongoing customers, they use nOps for checks and balances to make sure they're constantly aligned. Right? And we have a lot of success of having real revenue impact on partners' business, by leveraging nOps. >> Excellent. That's true value and true trust there. Last question. Where can you point folks, a CTA or URL that you want people to go to to learn more about nOps? >> Yeah. Basically just go to nops.io and just put on signup. Yeah. I love doing this stuff. I love talking to the customers. Feel free to reach out to me, as well: jt@nops. I would love to have a conversation. But yeah, just nops.io is the best place to get started. >> Awesome, nops.io. And I can hear enthusiasm for this, and your genuineness comes through the zoom screen here, JT. I totally thought that the whole time. Thank you for talking to me about nOps, how you guys are helping organizations really embrace cloud ops and evolve from traditional cloud management tools. We appreciate your time. >> Thanks, Lisa. >> For JT Giri, I'm Lisa Martin. You're watching the AWS Startup Showcase.

>>mhm >>Welcome to this cube conversation here in Palo alto California. I'm john Kerry host of the cube. We've got a great awesome conversation with the Ceo and co founder of harness a hot startup jodi Benson who is the co founder and Ceo but also the co founder of unusual ventures which is a really awesome venture capital firm, doing some great work investment but also they have great content over there for entrepreneurs and for people in the community And of course he's also the founder of big labs, his playground. If you're building out new applications also well known for being the founder of Ap dynamics of super successful billion dollar exit as a startup, Salto, Cisco now doing a lot of things and driving harness, solving big problems. So joe t mouthful intro there, you've done a lot. Congratulations on your an amazing entrepreneur career and now your next uh next next opportunities harness among other things. So congratulations. Thank you for coming. >>Thank you john and glad to be here. >>You guys are solving a big problem in software delivery. Obviously software changing the world. You're seeing open source projects increasing in order of magnitude enterprises jumping on open source in general adoption, large scale with cloud software is being delivered faster than ever before and with cloud scale and now edge this huge challenges around how software deployed, managed maintained. You got, we're talking about space to how do you do break fix in space, all these things are happening at a massive scale across the world. You are solving a big problem. So take a minute to explain what harnesses doing, why you guys exist, why you jumping in into this venture. >>Sure. Yeah. You know what harness mission is to simplify supper delivery and make it uh top notch for everyone. Like if you look at like you know the likes of google and facebook and netflix and amazon these companies are mastered the process of software delivery like and your engineers write code and the code is shipped to the end users and they can do it like multiple times a day at their scale and you know at the complexity that they have but most other business in the world they all want to be software companies but it's extremely, extremely hard for them to get there and I saw this firsthand when I was at epidemics as you know as Ceo last there we're about 12 1300 employees in the company and we had about about 3 50 or so engineers in the company For every 10 or 12 engineers, we had one person whose job was to write automation and scripting and tooling for trying to ships off you know uh you know all kind of scripting kind of stuff. We'll write scripts and chef and puppet and sensible and to deploy in aws and whatnot. And you know one day we're doing the math were like you know we have you know about overall about 30 people whose job was to do devops engineering by writing automation etc to deploy somewhere and I would do the math like you know, one engineer cost is 200 k loaded cost at six million a year that you're spending six million a year just writing deployment, scripting, you know, and even with that we were nowhere close to world class like world class is in like what you would think you could ship every day, we chip on demand, you could, you know, you could deploy software, ship software all of that right? And that was the, you know, I looked at that as a problem inside of dynamics and all they have done with customers, I would talk to like large banks, insurance companies and retailers and telcos and I would hear the same challenge like you know, we hear about devops, we go to the all these devops conferences and events and we see the same 10 companies, you know presenting how the home grew some kind of a devops system for software delivery etc. And you know, I mean that was like, you know, we just, we cannot survive with this like and as the world we need to have uh the right kind of platforms for software delivery and simplify this so that everyone could become as good as a google netflix amazon etcetera that stand of our mission at harness that can we take every business in the world, you know and in a few weeks or a few months, can we get them as sophisticated and good in terms of their dueling for software delivery as a google facebook amazon, those kind of companies would be and that's, that's what we're doing. So >>It's a great ambition and by the way it's a bold move and it's needed. I'll tell you, it's interesting. You mentioned some of those commentary about shipping code at that speed Facebook Google. They had that they had they were forced to do that and again they have all that benefit the mainstream enterprise doesn't. But if you even go back 20 years ago, 15 years ago, that's when Amazon was born. You see two and S three is celebrating their 15th birthday. Software. Yeah, hyper scale has had some good moves there. But the average business went from craft, you know, waterfall QA department go back a little bit slower. I won't say slow motion but manageable now with the speed of shipping and the speed of the scale, that's a huge issue. What kind of pressure do you see that putting on the developer, the individual, not just the system because you got the system of development and the devil and the developers themselves. >>I think the developers have have done quite well to this. I feel like, you know, if you look at the software development part of itself, you know the agile development has been happening for quite some time. So developers have learned how to ship things fast and like in a week sprint or a two week sprint or in in kind of faster cycles. They have moved off from the waterfall kind of models like many years ago now. So that's the suffering development side of things then you have the infrastructure side of things which is the like any province in infrastructure fast. Can you get hardware fast? That's the, you know, the cloud has done that well where the challenges the process, the developers are writing code fast enough these days and you have the, you know, the infrastructure itself could be prov isn't and maintained and and and change fast enough but how do you bring it all together and there is the entire process around it. That's not moving fast enough. So that's where the bottom language. So I feel the, you know, and the process is not good. The developer experience becomes really bad bad because developers are waiting for the process to go and you know, they write some code and the code is sitting on the shelf and they are waiting for things. >>Uh they get all pissed off and mad. What's the holdup? Why what's the process? And then security shifting left, wait a minute to go back and rewrite code. This is huge. I want to just get back and just nail it quickly if you don't mind honing in on the value proposition. What is the harness value proposition? What is the pitch, what are you, what are you offering? What are you solving? Can you nail in on that real quick? >>Sure. So what harness is swallowing is simplifying that software delivery by plane, so developer writes code and that code goes goes through a bunch of steps so a bunch of steps which is uh you know you build the code then you you know test the code, you know, then you do integration tests, then you you know go through your security checks, then you go through a compliance checks, then you go through more dusting, then you're deploying a staging environment, then you go one to do a bunch of things on it. Then you start deploying in production environment but in production you will deploy on like a small part of production, verify everything is working well, it's not working well, you'll roll it back, it's working well then you deploy two more things. This entire process could take like weeks for people to do and this is mostly automated, you know in kind of uh uh you know this kind of random scripts here and there etcetera. So we simplify the entire process that you could describe your process in the language, I just described like you know in a very descriptive declarative kind of way like this is the process I want to achieve and hardness will automatically create your pipelines for this. This kind of process and most of these pipelines have a lot of heavy use of intelligence and um L two, it could go from one step to another, like, so many times, like when you say, you know, deploy the guard and and and 1% of my production environment and see everything is working well and if everything is working well, go to the next 10%. But how do you figure out if everything is working well and that's where the intelligence and um El comes in like, you know, what we learn, what is a normal behavior of your application, how does a normal part of the code works like, you know, there, what's the performance behavior, what is a functional behavior? What errors it is? And if everything is good then you go to the next step so that entire cycle harness automatically, uh you know, uh managers and its automated, you know, if you get governance, you get like, you know, high degree of automation, you get a high degree of, you know, security, you get high degree of like, you know, uh uh you know, quality around him. And so it's it's think of like the, the Ci cd has a lot of developers know and know this process is is ci cd on steroids available to you, Right? So you >>sound like you're making it easier on the Ci cd pipeline process, standing it up, detecting it, prototyping it, if you will, for lack of a better description, get get used to the pipeline and then move it out, roll it out and build your own in a way >>that, is that what is that what you're doing? It's like, you know, a lot of these complex ci city pipelines, what people need, you know, it can take them like three months, six months to to put it uh you know, put it together the harness, it's like an hour, an hour, you could put it together, you know, very, very sophisticated uh Ci cd pipeline and the pipeline is, you know, automated is is, you know, it's it's intelligent around like, you know, what is the normal behavior of your of your applications? Uh It's it's just so phenomenally different than how people have done ci cd before that we simplify the process. Automate the process, you know, and make it manageable and very ready to get involved. >>It's funny you mentioned the three weeks weeks it could take to do the csd pipeline. Of course, that doesn't factor in the what happens when you roll it out, people start complaining, playing with it, breaking it, then you gotta go back and do it again. I mean, that's real and that's a real problem, I mean, can you just going to give a taste of the scar tissue that goes on there. What's some of the what are some of the what some of the pain points that you solve? >>Yeah. So, I think the that is that really becomes the core of the pain point, like, you know, people need, like high amount of dependability, easy to change things, you know, it's we call it like the lack of intelligent automation, you know, and the and this heavy amount of developer toil that the developers have to do so much work around around making all of this work like you know it has to be simplified. So that's that's where our value product comes in like you know, it's it's you know uh you can get like a visual builder and like minutes you can build out the entire process which is your job stability at city pipeline or you could also do like a declarative Yamil interface and just like you know in a few lines just right up whatever process you would want and we would review should be shipped with all kind of integrations with every cloud environment, every monitoring system, every system, every kind of testing process, every kind of security scanning so you can just drag and drop and in minutes eur, europe and running, it just creates so much velocity in this entire process. And also this manageability that people have struggled with >>morale to I mean you can imagine the morale developers go up significantly when you start seeing that the developer productivity has always been a big thing but this intelligent automation conversations huge. Some people have it, some people don't, people say they have it, what is how can you, how can the company figure out uh if someone's really got the real deal when it comes to intelligent automation because again, automation is the is key into devops. >>Yeah, I think I I almost started like you know like if you look at the generational evolution of things like the the first generation was uh you know developer writes code and then it will give you will give it to some some mighty at men who will go and deploy the code, run some commands and do things like tradition to was writing scripts that you're right, a lot of scripts that was automation but it was kind of dumb our dimension and that's how we have, you know that that's where the industry is so actually break now even most of it, the third generation is when the automation is you don't write scripts to you know uh to automate things, you tell our system what you want to achieve and it generates automation for you, right? And that's what we call intelligent automation. Where it's all declarative and all the you don't have to maintain a lot of you know scripts etcetera because they are, you know, they can't keep up with it. You know, you have to change the process all the time and if you change the process, it doesn't work, it becomes completely, you know, uh you know, it becomes very fragile to manage it. So that's that's really where intelligent automation comes in, you know, I look at like, you know, if you can have like uh like you look at like a wrestler, you know, making cars the entire assembly line is automated, but it's, but it's if you want to change something in the assembly line, even that process is automated and it's very simple. Right? So it's and that's what gives them so much uh you know, uh you know, uh let's say control and manageability around the manufacturing process. So the software delivery, uh you know, by assembly line, which is the software software by ci cd piper and really should be a more sophisticated and more intelligent as well now. And that's that's an exhibition, >>jodi. You're also pointing out something that we cover a lot on the cube and we've been writing about is how modern software practices are changing, where this team makeup or whatever its speed is key, but also getting data. Everyone who's successful with cloud and cloud scale and now you got the edge opening up and like I said, even space is going to be programmable, Everything's programmable. And the key is to get the data from the use cases right, get something deployed, look at it, get some data and then double down and make it better. That's a modern approach, not build it and then rebuild it and tear it down and rebuild it, which you're kind of leaning into this idea of let's get some delivery going, let's structure it and then feed it more so that the developers can iterate with with, with the pipeline and this is this again, can scale, can you talk about that? Can you comment on your reaction to that? >>Yeah, definitely. That's exactly how we look at it. Like, you know, you uh you want developers to kind of like say they want to do a, you know, automated process to deploy in their communities infrastructure in matter of minutes, you should be able to get started, but now it's like, you know, there's so much data that comes into it. Like, you know that you have monitoring systems systems like ab dynamics and you're like and data dog and you're logging systems your Splunk and elastic and you know, some logic, you have your, you know, different kind of testing systems here, your security scanning, so there's so much data in it. They're like, you know, terabytes and terabytes of data from it. So when you start doing your deployments, we could also come seem all of the data and see like what was the impact of those deployments or court changes in each of these monitoring, dusting, logging gonna systems and you know, what, how the data changes and then now is that based on that we can learn like, you know, what should be your ideal process and what will break in your process and that's that's the how harness platform works. That's the core of that intelligent automation networks, they're expanding it now to bring a few more of the devops use cases into it Also like the one is cloud cost management because when you, when you, you know, uh you know when we started shipping, there's a lot of people would tell us like, you know, you're you're doing a great job helping us managing the quality, which we always were concerned about like when we're deploying things so you know, security, you know, functionality etcetera. But cloud cost is a big challenge as well. You have your paying like tens and tens of millions of dollars to the cloud providers. And when developers do things in an automated way, it could increase without cost suddenly and we don't know what to do how to manage that. So that's the, you know, we we introduced a new model called cloud cost management to as part of the develops software delivery process that every time you're shipping code and we also figure out like, you know, what with impact on on your on your podcast, you know, can we automate the, you know, uh if there is there is too much impact, can we automate the, you know, the roll back around it, you know, can you get and you can you can we stop the delivery process at that point, can we help you troubleshoot and, you know, reduce the cost down? So that's, you know, that's cost becomes another another another dimension to it. Uh you know, then we recently just added uh you know, the next level that's managing feature Flags. And a lot of the time software developers are adding feature flags to like this feature would be given to this consumer and like, you know, and this feature will be given to this consumer until you test it out through uh test kind of thing and like, you know, what is the impact of, you know, uh turning a feature on versus off, you know, we're bringing that into the same ci cd pipeline. So it's kind of an integrated approach to this uh you know, our intelligently automated biplane instead of these uh small point approaches that just very hard to manage. >>I mean the level of data involved the creature flag for instance, the great is an amazing thing because that allows you to do things that used to be extremely difficult to provision. I mean just picking the color of icon, for instance, this kind of blue, I mean I was just, you hear about this, these kinds of things happening at scale and the date is pretty accurate when it comes in. So I think that's an example of the kind of speed and agility that developers want and the question I want to ask you though on that point because this opens up the whole next conversation, you guys have a modern approach and so much traction and you've recently raised big rounds of funding as you go to the market place, your experienced entrepreneur and uh and Ceo you've seen the waves before. What's the big wave that you're on now? What's the big momentum tailwind for harness? Is it the fact that you're creating value for developers or is it the system that you're integrating into with the intelligence to make things smarter and more scalable? What's the or is it all the above? Can you just share what that that story is? >>Yeah, I think it's, it's, it's really, really both of them. But you know, what are our business case when you go to people who tell them like say, if you're you know, 200 developers. uh, you know, we can give you the world's best software delivery tooling at the cost of half to one developer. Right? So like, you know, so which is like 44, 200 person organization at like 200 to 200 to $300,000 a year. They will get the best software delivery tooling better than a Google Facebook Amazon kind of companies very, very quickly. So our, our entire value prop is built on that like a developer experience gets much better. The productivity gets much better. Developers on an average are spending like 20-30% of the time on deployment, delivery-related toil, like unnecessary stuff that we deal with. So it's only 30% more efficiency gain for the developers. Their quality of life gets better that they don't need to worry about like weekends and nights to babysit your deployments and you know, things breaking and troubleshooting things all the time. Right? So that's that's a that's a big big value. But as a business you get much more velocity your innovation velocity is much higher. You know your risk on your, you know your consumers is much lower because your quality of the of of you know how your ship becomes becomes better. So our business case of like you know at the past of like 1-2 develops engineers will get you the best develops uh you know tooling in the world possible. You know it's not a hard business case for us to make, right? That's that's what we we we look at, it becomes pretty pretty obvious for you know as people try our product, you know the business case >>you don't have to really pass the I. Q. Test to figure this one out, okay everyone's happier and you have more options to scale and make more money in new opportunities not just existing business. I mean the feature flagging these new features you can build a new value and take more territory if you're a business or whatever your objective is so clear value. Can you give an example of some recent successes you've had or or traction points that you think is worth notable that people can get their arms around. >>Yeah definitely like you know we are we're helping a lot of uh you know a lot of customers you know doing uh like completely changing their uh their uh their process of software delivery, you know, 11 recent example, uh nationwide insurance, you know, nationwide insurance, you know, moving from their data center kind of approach to public cloud and to communities and to microservices, like a major cloud native re architecture and in a very ambitious aggressive project to do it, you know, in a in a in a short period of time and harness becomes a platform for them to kind of, you know, uh to remove all the bottom leg around the process, the software delivery process. You know, they obviously they still have to do the developer side of things and they have to do the cloud infrastructure side of things, which is they're doing. But the entire process of how you bring together, you know, harness becomes accelerated around it. So a lot of these kind of stories that we when we kind of create this fundamental transformation for our for our for our customers, you know, uh you know, moving to to a public cloud, you know, moving to microservices, moving to communities, you know, re architect things, but they become much faster. Cloud native higher, you know, a true software company and you know, I would say that's that's something we we we we take a they can take a lot of pride in, I think are always our biggest challenge is uh is to is to is to evangelize and and convince the market that this is possible to do with the product, because historically people have got told like, you know, the only way you can do this kind of software delivery processes and tooling is by engineering it on your own. So everyone wants us on the path of writing their own, you know, and and it's very hard for every, every company in the world to become very good in writing your own software delivery, tooling and processes and systems, etcetera. Right? So it's uh and that's it. So, you know, there is still that that education and evangelism needs to be done, that, you know, there is uh there is no point, you're trying to do it on your own, you can get a platform that can do it all for you and you can focus on the your core business of, you know, what you want to innovate on. >>And I think the Devil's movement hasn't been pioneered and you have to hand roll everything and that's the way it was. But now, as the mainstream market picks this up, you're standing on the shoulders of those pioneers, you are one of them. It's awesome to see this modern approach because it's really playing out in real time again, you've done that before, joe t so it's impressive and, you know, you've seen the movie and developed and the earlier versions pre devops. So, so as cloud native comes and start scaling it's going to be for the rest of us. So, great, great that you're providing the platform and the tools and software. I got to ask you if you don't mind because a lot of people are looking at ways for modern approaches to organizing their teams, how would you define the modern devops movement? You look at devops one point. Oh, we got here. Okay, cloud, cloud native, cloud scale, modern applications, pipe lining. Now, we're looking at a whole another level of confluence of uh of integration and speed. How would you define the modern devops movement? >>Yeah, I think that's a that's a very good question. I think that the core of modern devops, what I would call it develops to point to me is developers self service. It was like the first generation of develops was they create this kind of a devoPS team and then the developers will give all the, you know, delivery related stuff that develops team and the devops team starts to become a bottle, like everywhere now, like in the developed steam job is to build a ci pipeline and the city pipeline and the deployment scripts and you know, do like, you know, you want to do a canary deployment, they have to figure it out how to do it, they have to do, like, you know, you are uh you know, all sort of things that the that needs to be done, you create a central develops team and you give it to them and they become like, you know, uh become a big bottleneck, we look at the modern develops or the next generation and develops has to be done around focusing on the developer experience that and making it all self service for the developers. So you have, you have, let's say you are definitely in for a micro service and it's like, you know 57 engineers, you know, modeling a micro service you want like that, they can go and say this is for our micro service, you know, in a matter of minutes or hours, they can engineer the process without having to lean on a central deVOPS team and to do all the work for them and that's you know, by by maybe a modeler or in some kind of mammal interface or something. That's very easy for them, their experience is so easy that they can manage it themselves without the central deVOPS team have to write it all or cut it all and manage it all. But at the same time the center deVOPS teams, job becomes a bar and governance that can they define the guardrails, that they can define the guardrails on like, you know, you have to have this level of security before something goes into production, you have to have this level of quality before something goes into production, you have to have like, you know, uh this, your cost could not be more than this, right? So you define, so in this instance, instead of the center develops team is doing all the work themselves on writing all the stuff they define the guard rails and it becomes a very easy cell service experience of the developers should do things within those, those guard rails. This is what the modern never actually, >>that's awesome and also accelerate more business value And you're nailing it joe t thank you for coming on and great. Uh, the Ceo on the cube ceo and co founder harness harness dot IO. You guys got free trials, free downloads. You got a great, uh, by as you go model also. Um, you're an entrepreneur at heart. Uh, co founder of unusual ventures, Big Labs appdynamics. Now harness. Congratulations. Thanks for coming on. >>Hey, thank you john. >>Okay, this is a cube conversation. I'm john for here in Palo alto California with the cube. Thanks for watching.

(light music) >> Welcome to this session at the Amazon EC2 15th birthday event. I'm your host, Lisa Martin. I'm joined by Elaine Harvey, director and technical advisor at AWS. Elaine, welcome to the program. It's great to see you. >> Thank you, Lisa. I'm really glad to be here. >> So here we are celebrating EC2's 15th birthday, probably back in the day, so many customers and many industries couldn't imagine how they would be using the service. Talk to me about how long you've been involved in EC2 and some of the growth and the maturation of the service that you've seen. >> Yeah, I mean, I joined EC2 about eight years ago and it was big then, but much smaller than it is now. And it's grown in so many directions, both in the scale, the instances that we offer, as well as the types of instances, the various types of hardware effectively that we offer for customers to support their workload. It's just grown in so many dimensions. It's really exciting. >> I see here 80 availability zones. 25 regions, local zones in Boston, Dallas, Denver, Houston, Miami, Philadelphia, and nine new locals zones coming just this year. Talk to me a little bit about that. >> So really, what we are trying to do is get compute where customers needed. So we've already had these presences around the world. And with this expansion, we're trying to bring the EC2 offering to customers with much lower latency. And that's why we're doing local zones, regions, availability zones in so many places. So customers can have that compute with low latency to help them interact with their customers. >> I know since its inception, AWS has always been so customer centric, it's always day one there, but prior to joining AWS, as you said, eight years ago, you were involved in a number of startups. One of the things that we consistently hear is how instrumental EC2 has been in reinventing the startup space. What can you tell me about that involvement that it's had? >> Yeah, I mean, the great thing was, I was an EC2 customer before I worked at EC2. So I had been in the startup community for almost 25 years before joining Amazon. And I had been through that life cycle of a startup where you begin, you need some capacity, you need some computers to run your stuff on and eventually you reach a size and you have to go figure out all the hard work. Where am I going to put them? Do I need a data center? What kind of network connectivity do I need? And not only that, you have to invest a lot of money, which startups very rarely have in the early days into buying the equipment you need, just so you could run your business. Do the thing you're really trying to do for your customer. EC2 is a game changer. So I started using EC2 at one of the startups I was at before coming here. Actually I had two prior startups before coming to EC2. And the ability to just get capacity when you needed it, you didn't have to go buy computers. You didn't have to have data center contracts. You just said, I need a hundred of these. And suddenly you had a hundred of the instance you were asking for, completely game changing, especially for a startup where you just don't have that capital to invest. And frankly, you don't want to spend your time dealing with data centers when that's not your business, your business is to serve your customers. >> And I can't imagine the last year and a half, we've seen such acceleration of digital business transformation, how startups and enterprises alike would have fared without having the ability to quickly turn on services like EC2 in this time. >> Yeah, yeah. It was just amazing. During COVID times, we definitely saw that rush of everybody trying to go online companies that had been already starting down that path, going online, scaling more. And suddenly it went from zero to 100 in March and everybody had to go online and it was super exciting to be part of EC2 and be able to enable everybody in the world to do that. >> Incredible amount of acceleration, but also maturation and growth in the whole portfolio of AWS. We've talked about that a number of times on The Cube in the last six or eight months or so, you mentioned nine new availability zones coming in 2021. You've been involved in the regional and the local zone build out. Talk to me about how these regional zones, these availability zones are helping enterprises to run their businesses and applications worldwide with the high availability that their customers are demanding. >> Yeah, yeah. So there's the book the location aspect. So we do need to be worldwide because our customers are worldwide. So we need to be where they need to be. And so that's how we think about the growth of our regions and availability zones and now local zones with lower latency to end customers. There's another aspect to availability zones and regions that is super important for our customers availability, foundationally we treat those as fault zones. So their fault boundaries beyond which customers will not experience faults. So for example, the fundamental way that we think about designing our services isolates faults between regions and between availability zones and customers can use that in their designs such that they'll have a Multi AZ behavior and we contain faults along those boundaries so they can design with that in mind, and their applications can be fault tolerant, relying on those foundational fault domains effectively. >> That's even becoming more and more important as consumers become more and more demanding that services are just available. And you can get anything with the click of a link on your phone. That high availability is really no longer a nice to have what EC2 is delivering, it's table stakes for an organization I can imagine in any industry. >> Absolutely, absolutely. Our customers totally rely on that so that they can serve their customers consistently and reliably. >> It's a tremendous amount of growth Elaine, in the first 15 years, you said you've been with EC2 on this side now working for it for eight years, but had a lot of experience with it before when it was probably in its infancy as a startup customer. What are some of the things that excite you most about the direction in which EC2 is going? >> Yeah, I think we are steadily providing more and more flexibility to our customers. So we are providing them with new instance types to suit their particular workloads. So we're getting more into a variety of offerings that customers can use to achieve the outcomes they want. That's exciting. I think probably the thing that excites me the most though, is the work we're doing around custom silicon. So our Graviton, Inferentia, Trainium chips where we are building custom silicon for a number of reasons. A big factor of that is we are giving our customers the ability to have a much better ROI on compute to cost for their workload. So we're trying to make it more and more cost efficient for our customers to do what they want. The thing that really excites me about it, though, I'll tell you the secret thing that excites me about it is not very well known, but Graviton is not only cost to compute higher efficiency, but it is also power to compute higher efficiency. So it's a greener option. So if a customer for a given workload wanted to reduce their carbon footprint, they can move to Graviton and it consumes substantially less power for the same workload. And that makes me really excited. >> That is exciting and something that I think everybody can wrap their heads around. I was reading something about EC2 and Graviton paving the way for another important initiative, and that's telecommunications, some of the big news, that Dish Network is coming out saying we're going to be building our 5g core network on AWS. A lot of work going on there in telecommunications. >> Yeah. Yeah. That's very exciting. And in line with our overall strategy to get much closer to the end customers, again, to reduce that latency, whether those customers are on a 5g network or on the internet, what we want the ability for our customers to be able to provide compute and their applications wherever their customers are. >> Well Elaine, thank you so much for joining me on the EC2 15th birthday event. A lot of innovation has gone on in the first 15 years. We know what you're excited about and I'm sure, can't even imagine what the next five, 10 or 15 years will hold for EC2, its services and the customers that it delights. We thank you for joining us today. >> Thanks so much, Lisa. >> Elaine Harvey, I Lisa Martin, thanks for watching today's session. (light music)

(soft electronic music) >> Welcome to this session of the Amazon EC2 15th Birthday Event. I'm your host, Lisa Martin. I'm joined by Joshua Burgin, General Manager of AWS Outposts at AWS. Joshua, welcome back to the program. Thank you, it's great to be here again. >> So 15th birthday, a tremendous amount has gone on in the last 15 years, but I want to understand what brought you to AWS? What excited you about cloud and EC2, in particular? >> Yeah, I mean, that's a, it's a great question and it's kind of a fun story. I actually worked at Amazon back in the 90s for three years as a software engineer when I don't think anybody you asked back then would have said that cloud was in our future. And so I'd kind of obviously kept in touch with people over the years and I was working at a customer who, interestingly enough, had moved off of AWS thinking that they could build a better cloud. And then of course, over the years, found out that it's actually quite difficult and was in process of moving back to AWS. And so I reconnected with some of the senior leaders who I was still friendly with and they said, you know, come back in, the water's fine, there's still a lot of opportunity. And it's, it's really been true, right? There's been just a tremendous amount of growth in the last seven years that I've been back and obviously, over the last 15 years for EC2, in general. >> Well, this 15th birthday not only marks a big milestone for AWS, but also for the cloud computing world that it serves globally. Talk to me a little bit about the impact over the last seven years you've been there and 15 years of EC2's life. >> Well, I mean, we've really been transforming every industry that you could possibly imagine as everyone's had to develop a plan to move to the cloud to take advantage of the opportunities for innovation, for cost efficiency, for developer efficiency, for operational improvements. And so EC2 was one of the foundational services inside of AWS and, you know, a lot of things are built on top of it, and so it's been really great to work with all of these different customers in financial services, in Telco, in gaming, you know, healthcare, you name it, all around the world. >> So 15 years ago, EC2 obviously started quite small. Can you talk to us about some of the early trends that are emerging from the hybrid space? >> Yeah, I mean, we're fond of saying here that it's still day one and that's very true for the outposts and the hybrid business, in general, at AWS. The early trends, if I had to kind of bundle them together, would be that first of all, people are operating in more places than they ever thought they would have to. These are big customers, manufacturing, Telco, healthcare, public sector customers, people in gaming, they serve customers around the world. That's a trend that's kind of, irregardless of industry, that's what we're seeing. And so of course, having an outpost available everywhere, we're up to 60 countries now, having local zones in many countries which we hope is our longterm plan, having wavelength zones with lots of partners, you know, that's why we're doing those things 'cause customers are telling us that we need to operate everywhere. It's actually the reason we went from one availability zone or excuse me, three availability zones in one region 15 years ago, to 25 regions in 80 availability zones. And of course, hybrid is building on top of that. The other thing we're seeing, you know, real specifically for hybrid is low latency, local data processing, and data residency. Across every industry, those are the needs that are driving people to adopt hybrid technology and they're the ones pushing us forward here, at AWS to innovate on their behalf. >> Talk to me about some of the innovation in the last few years alone, that customers are helping drive where those regulations are becoming more and more critical. We're seeing more importance on security and ensuring that customer data is secure, protected, but also accessible. >> Yeah, absolutely, I mean, we're fond of saying at AWS that security is job zero. You know, we take it incredibly seriously, even though, of course, it's a shared responsibility model where we secure the underlying infrastructure and then provide tooling and services on top of that for customers to create the level of security that's appropriate for their application. Obviously, a government workload or a banking workload is different than a mobile game, even of course as customer data needs to be secured in all situations. So with outposts and with local zones, what we're giving people the ability to do is ensure that their compute and their storage are in whatever country or municipality or city or state that they need them to be. So you could take something as diverse as a bank or a healthcare company where they might need to have that compute and storage literally in a specific facility because of regulations, or in a specific state, you know, that's kind of happening around the world. You also see something you might not have thought about, but customer is in the iGaming space, so that's mobile betting. Tipico and FanDuel are a couple of early examples of those for outposts where as it becomes legal, at least in more states in the United States and more places in Europe, the regulations are requiring that the cloud computing, if they want to use it, is placed in a specific place. So the only way you can do that is either, of course, if we had a region everywhere, which we don't, or if you have something like outposts, otherwise you'd be forced to revert to like a bare metal solution and kind of take on all that heavy burden yourself. Your developers would be less efficient because they'd be using AWS in one place and bare metal kind of hardware somewhere else. So, you know, it's still really early, but I've been pleased to kind of see that kind of adoption across those diverse industries. >> It is really early, as you said. The philosophy at Amazon AWS is it's day one. Give me some feedback from customers now where, you know, we, we see a lot of different reports that suggest where businesses are, enterprises are in terms of cloud adoption. What are some of the things that you're seeing where you really think hybrid is going to be an absolute game changer? >> Yeah, I mean, one example that comes to mind is Telco which is one of the biggest industries with the smallest amount of cloud adoption to date. And so I think a lot of that was driven by specific requirements in that industry that required on-prem components for that ultra low latency. You can imagine they needed the compute and the storage to be at the cell site or distributed around the United States or other countries. And so that's where you have examples now with Dish Networks where we just announced a strategic partnership with them. They're going to be using this combination of the new small form factor outposts that we're releasing later this year. They're about the size of a pizza box or a couple of pizza boxes. They're also going to be using our network of local zones that we're building out, 15 of them across the United States, and they'll be using our regions for workloads that are, of course, less latency sensitive, and that can kind of be run centrally. So it's really kind of one of the best examples I can think of where people that were held back by the technology, by the offerings are now enabled to move really quickly. And so I think you're going to see a lot in that space and other industries where before they had to kind of not move to the cloud because a portion of their workload needed to remain on-prem, and now we're delivering a continuum of offerings, including, you know, to the very smallest locations. >> Let's look forward into the next decade. As barriers to adoption are being removed daily, you mentioned Dish Network. I saw that they're going to build their 5G, their core 5G network on AWS. That's huge, that's a big signal for the telecommunications industry. But what are some of the things that you think we're going to be able to open this book and there will maybe a crystal ball in the next decade can expect. >> Yeah, I mean, if I had a crystal ball, my roadmap would be perfect. >> Wouldn't it? >> It would be, it would be great. So if anybody's offering one of those I'm, I'm taking. But what I think you'll see is that, that the day one metaphor is going to continue. As big as AWS has become, and I think we're really proud of the accomplishments and innovation we've delivered for customers over the last 15 years, as I mentioned, we started with one instance type and one region, and now we have over 400 instance types in EC2. That's a lot of choice for people and that's just EC2, right? We have another 185 or 200 services these days, I can barely keep up with them which is exciting in its own right. And so the reason is that we're doing all that innovation is that customers are telling us what they want and a lot of that is, although they're driven to move to the cloud and they really want to move there quickly, somewhere between 75 and 90% of technology spending is still in the traditional hardware-software space. So again, I'd like you to think about that. 15 years in, you know, at the run rate that we're at, and obviously with other people in this space, there's still so much more to go that has already moved to the cloud. So I think you'll see more new instance types, more locations, more form factors, you know, from Outpost and us using Outpost to deliver infrastructure like local zones and wavelength which are built on top of Outposts, and so we don't force people to pick and choose between moving to the cloud and running the kinds of workloads they're already running. We want to be driven by the customer not force them into a narrow way of working that we think is best. That's probably the hallmark of AWS is giving people the choice. They can use EC2 and manage their own databases, they can use RDS or one of our, you know, 14 purpose-built databases, depending on what their application needs. And that's true across the board. Storage, compute, machine learning, container services, hybrid offerings, of course, which I manage for the AWS business, we're going to continue to do that. So the choice is going to proliferate, the performance is going to continue to improve, we're going to continue to bring down pricing and increase price for performance, and we're going to hopefully make things easier and more cost-effective for people, whether that's for their developers or their finance people, so that they can innovate on behalf of their customers versus handling all that undifferentiated muck and heavy lifting of managing the infrastructure themselves. >> That customer centricity has always been key to AWS. Just some of what you said, I think we can expect to see a ton more from AWS, announcements, customer-driven choices for customers. Joshua, thank you for joining me today. Happy 15th birthday to Amazon EC2. >> Thank you so much for having me. It's great to be here. >> For Joshua Burgin, I'm Lisa Martin. You're watching theCUBE. (soft electronic music)

(upbeat rhythmic music) >> Everyone, I'm John Furrier with theCUBE here at Palo Alto on a remote interview for a special video interview. The EC2 15th birthday party celebration event. Raj Pai, who's the Vice President of EC2 Product Management AWS is here with me. Congratulations on Amazon Web Services, EC2 with the compute. What a journey. 15 years old. Soon we got the keys to the car at a couple more years. So Raj, great to see you. You guys have been doing great work. Congratulations. >> Thank you. It's great being here. It's super exciting for me too. I can't believe it's 15 years and you know that big, we're still at the very beginning as you know, that we often say. >> The building blocks that have been there from the beginning really set the table, and it's just been fun to watch the innovation on behalf of customers that you guys have done at AWS and more, and for entrepreneurs and for developers, it just continues to be great and the edge is right on the corner. Wavelength, all the great stuff. But let's talk about the specific topic here that I really want to drill into is that as you look at the 15th year and birthday for EC2, okay? You're looking at the future as well. You're looking at the past, present and future. And one of the things that's most compelling about recent re-invent was the Graviton performance numbers are amazing. You guys have been building custom silicon for a while. You also worked with Intel and AMD. What is it about? What's the huge investment for you guys? Where do you started to see some returns? Are you seeing returns? And then why did AWS decide to build its own processors? >> Yeah, now, that's a really good question. And I mean, like with everything else we do in AWS, it's all about innovating on behalf of our customers. And one of the things our customers are telling us, that they continue to tell us is they want to see better performance at lower prices. And we've been able to deliver that with our hardware partners for the last 15 years. But as we've understood the workloads that run on EC2 and AWS, we saw an opportunity. Like, what if we were going to go and design our own processor that was really optimized for the sort of workload that customers run on the Cloud? And make design decisions when designing the CPU and the system and the chip around the CPU that does things like bring a lot more core local cache and speed up the parts of the operations that really benefit real-world workload. So, this isn't about benchmarks. It's about how do real world workloads perform and how do we build systems that optimize that performance? And with Graviton, we were able to hit the nail on the head. We were also very pleasantly surprised when we got our first chips off the line. And we're seeing that a customer, like about 40% performance improvement at significantly lower cost. And that's super exciting. And that's one of the reasons we're getting so much interest from our customers. >> I got to say as a geek and a tech nerd, I love the silicon development. And there's benefits there, also the performance is there. The thing that also is pretty obvious that's happening is and the world seeing it is the shift towards ARM-based computing. What kinds of customers and use cases are you seeing adopt to Graviton? And what kind of workloads were they running on? What are the things that surprise you guys, that didn't surprise me. Did you guys always talk about the upcheck and how everyone's leveraging it? What are some of the examples? Take us through some of the customers, use cases, workloads. What's surprising you and what's going on with Graviton? >> Yes, so I think that the biggest surprise for us is how broadly applicable it's been. So one of the things we did, we launched with reinvent is like we have different form factors of compute. We have memory-optimized instances that are good for databases and in memory caches. We have compute optimized for HPC and workloads that really take advantage of the performance of the chip and then we have general purpose workloads. And we we introduced Graviton variants of all those instance families And we're actually seeing the same sort of performance benefits across workload. So, and it's one of the reasons why companies like Metrol, and Snap and SmugMug, they move one workload over, they see the performance benefit and before you know it, they're starting to move workloads and mass over across kind of that spectrum. So, I think that's one of the biggest surprises is that Graviton seems to do well across a wide range and we're going to keep on introducing it more and more of instance families, because we've seen this uptick well. >> You're seeing a lot of people move to the Graviton. You mentioned a few of those early adopters who were pushing the envelope, and they're always kind of trotted out there as examples at reinvent, which is always fun to see what they're working on next. And now is that people see the Graviton2 instances, okay, the architecture's different, higher performance. How much effort do our customers typically need to move to Graviton2 instances? And what are some of the benefits they're seeing on performance and price performance? Can you talk about that transition? Because that's natural evolution for them. >> Yeah. It's actually a lot less than they originally think. So, some of the hardest effort is just getting them over the line to try it. So, one of the things that we tell our customers who are considering Graviton is it just takes one or two developers take one workload and go off for a couple of weeks and just try reporting it to Graviton. And more often than not, they come back to us in four or five days. They're like, it works. And we just had to do some testing and verification, but we were able to afford it because, you know, the operating system support was there, the ISP support was there and the tools that they use, and they're using most cases, modern programming languages like Python or Go or Java or PhD where, you know, interpret the language and it just run. And so there's very little lift in comparison to what people think it's going to be. And that's one of the reasons that, you know, one of the big announcements we made in the last few weeks is what we're calling the Graviton challenge, right? So it's a set of blueprints for customers to essentially have best practices on how to in four days take, you know, a piece of code and piece of that workload and execute it and run it and migrate it to the Graviton. And we're seeing a lot of interest in that as people in the community realize how easy that actually is. >> What are some of the cool price performance things that are emerging? Obviously it makes sense if you don't really need it, don't pay for it, but you have that option. A lot of people are going there. Is there a wave you see coming that Graviton2 is going to be really set up for that you kind of see some early signals coming in, Raj? Because, I can see the 64 bit. I can see where Graviton fits today. Obviously, performance is key. Is it certain things that are emerging? What's the main problems that it solves? >> Well, I think anything that's a multi-threaded architecture is going to do really well in Graviton because of the, we have really densely packed 64 course. And so you're going to see things like microservices and containers and workloads that are more, that are able to take advantage of that parallel execution do really, really well. And so, we say 40% performance improvement, but like, when our customers have gone and tried this, they've seen upwards of 50% depending on the workload. So yeah, it's going to be more your multi-threaded application. There's some applications that may not be a fit, like it can give a legacy, you know, for example, like, there's some software that hasn't yet been moved over and we're going to continue to invest super heavily in our whole ecosystem of hardware, for the longterm. So I think that because there's a great option and we just encourage them to try it. And then they'll learn from their experience what works and what doesn't. >> Wow. 15th birthday. Still growing up and it's starting to get more mature. You're the VP of Product Management. You have the keys to the kingdom. So, you have wide-ranging responsibilities. Share with us if you can. I know that you really can't say much, but try to give a little bit of teaser. You got Wavelength. I can see the dots connecting at the edge. You got Outposts, so we see all that emerging. I can almost imagine that this is going to get stronger. What should people think about? Where's the headroom for EC2 with Graviton and Graviton2? >> Yeah, I know. I think like, a new architect (mumbles) yourself. But like, our goal is to have AWS kind of everywhere our customers are. And that means the full power of AWS. So, I think you're going to see more and more of us having EC2 in compute capacity, wherever customers need it. That could be in an Outpost. That could be on their 5G network. That could be in a city right next to them, right? And you're going to see us continue to offer the variety, the selection of instances and platforms in all those locations as well. So, I think the key for us is to be ubiquitous and have compute power everywhere our customers need it, in the form factors they need it. >> That's awesome. Congratulations. I love the power. You can't go wrong with sending computers where the data is, where the customers are. AWS, Amazon Web Services. Building their own custom silicon with Graviton2 processors. This is EC2 continuing to grow up. Raj Pai, Vice President of EC2 Product Management. Thank you for coming on and sharing the update and congratulations on the 15th birthday to EC2. >> Yeah, thanks for having me. It's been great. Have a great Friday. >> All right. Great. I'm Jeffrey with theCUBE. You're watching theCUBE coverage of EC2's 15th birthday event. Thanks for watching. (soft rhythmic music)

>>Mhm >>Welcome to the cube where we're celebrating the EC 2/15 birthday anniversary. My name is Dave Volonte and we're joined right now by Sandy carter, Vice President of AWS. Welcome Sandy, it's great to see you again, >>David. So great to see you too. Thanks for having me on the show today. >>Very welcome. We were last physically together. I think it was reinvent 2019. Hopefully I'll see you before 2022. But first happy birthday to EC two. I mean, it's hard to imagine back in 2006, the degree to which EC two would impact our industry. Sandy, >>I totally agree. You know, I joined a W S about 4.5 years ago in EC two and it's, it's even amazing to see what's just happened in the last 4.5 years. So I'm with you. Nobody really expected the momentum, but EC two has really shone brightly in value to our customers. >>You know, we've done the public sector summit, you know, many times. It's a great event. Things are a little different in public sector as you well know. So talk about the public sector momentum with EC two and that journey. What have you seen? >>Yeah, so it's a great question day. So I had to go back in the time vault. You know, public sector was founded in 2010 and we were actually founded by the amazon process writing a paper setting up a two pizza team, which happened to be six people. And that journey really started with a lot of our public sector customers thinking that we don't know about the cloud. So we might want to do a pilot or just look at non mission critical workloads now public sector and I know you know this day but public sector is more than just government, it has education, not for profit healthcare and now space. But everybody at that time was very skeptical. So we had to really work hard to migrate some workloads over. And one of our very first non mission critical workloads was the U. S. Navy. Um and what they did was the Navy Media Services actually moved images over to EC two. Now today that seems like oh that's pretty easy. But back then that was a big monumental reference. Um and we had to spend a lot of time on training and education to win the hearts and souls of our customers. So back then we had half of the floor and Herndon Washington, we just had a few people and that room really became a training room. We trained our reps, we trained our customers um research drive. A lot of our early adopters accounts like Nasa and jpl. And um then when cloud first came out and governments that started with the U. S. A. And we announced Govcloud, you know, things really picked up, we had migration of significant workloads. So if you think back to that S. A. P. And just moving media over um with the Navy, the Navy and S. A. P. Migrated their largest S A P E R P solution to the cloud in that time as well. Um, then we started international. Our journey continued with the UK International was UK and us was us. Then we added a P. J. And latin America and Canada. And then of course the partner team which you know, is very close to my heart. Partners today are about 73% of our overall public sector business. And it started out with some interesting small pro program SVS being very crucial to that, accelerating adoption. And then of course now the journey has continued with Covid. That has really accelerated that movement to the cloud. And we're seeing, you know, use of ec two to really help us drive by the cute power needed for A I N. M. L. And taking all that data in from IOT and computing that data. And are they are. Um, and we're really seeing that journey just continue and we see no end in sight. >>So if we can stay in the infancy and sort of the adolescent years of public sector, I mean, remember, I mean as analysts, we were really excited about, you know, the the the introduction of of of of EC two. But but there was a lot of skepticism in whatever industry, financial services, healthcare concerns about security, I presume it was similar in public sector, but I'm interested in how you you dealt with those challenges, how you you listen to folks, you know, how did you drive that leadership to where it is today? >>Yeah, you're right. The the first questions were what is the cloud? Doesn't amazon sell books? What is this clown thing? Um, what is easy to, what is easy to stand for and then what the heck is an instance? You know, way back when there was one instance, it didn't even have a name. And today of course we have over 400 instant types with different names for each one. Um and the big challenges you asked about challenges, the big challenges that we had to face. Dave were first and foremost, how do we educate? Um we had to educate our employees and then we had to educate our customers. So we created these really innovative hands on training programmes, white boarding um, sessions that we needed. They were wildly popular. So we really have to do that and then also prove security as you know. So you asked how we listen to our customers and of course we followed the amazon way we work backwards from where we were. So at that time, customers needed education. And so we started there um, data was really important. We needed to make customer or data for government more available as well. So for instance, we first started hosting the Census Bureau for instance. Um and that was all on EC two. So we had lots of early adopters and I think the early adopters around EC two really helped us to remember. I said that the UK was our international office for a while. So we had NIH we had a genomes project and the UK Ministry of Justice as well. And we had to prove security out. We had to prove how this drove a structured GovCloud and then we had to also prove it out with our partners with things like helping them get fed ramped or other certifications. I'll for that sort of thing as well. And so we really lead in those early days through that education and training. Um we lead with pilots to show the potential of the possible and we lead with that security setting those security standards and those compliance certifications, always listening to the customer, always listening to the partner, knowing how important the partners we're going to be. So for example, recovery dot gov was the first government wide system that moved to the cloud. Um the recovery transparency board was first overseeing that Recovery act spending, which included stimulus tracking website. I don't know if you remember that, but they hosted the recovery dot gov On amazon.com using EC two. And that site quickly made information available to a million visitors per hour and at that time, that was amazing. And the cost savings were significant. We also launched Govcloud. You'd asked about GovCloud earlier and that federal cloud computing strategy when the U. S. Government came out with cloud first and they had to consider what is really going to compel these federal agencies to consider cloud. They had Public-sector customers had 70 requirements for security and safety of the data that we came out with Govcloud to open up all those great opportunities. And I think Dave we continue to leave because we are customer obsessed uh you know, still supporting more security standards and compliance sort than any other provider. Um You know, now we lead with data not just data for census or images for the US Navy, but we've got now data in space and ground station and data at scale with customers like Finra who's now doing 100 billion financial transactions. Not just that one million from the early days. So it has been a heck of a ride for public sector and I love the way that the public sector team really used and leveraged the leadership principles. Re invent and simplify dive deep. Be obsessed with the customers start where they are. Um and make sure that you're always always always listening to what they need. >>You know, it's interesting just observing public sector. It's not uncommon, especially because of the certifications that some of the services, you know come out after they come out for the commercial sector. And I remember years ago when I was at I. D. C. I was kind of the steward of the public sector business. And that was a time when everybody was trying to focus in public sector on commercial off the shelf software. That was the big thing. And they want to understand, they wanted to look at commercial use cases and how they could apply them to government. And when I dug in a little bit and met with generals and like eight different agencies, I was struck by how many really smart people and the things that they were doing. And I said at the time, you know, a lot of my commercial clients could learn a lot from you. And so the reason I bring that up is because I saw the same thing with Govcloud because there was a lot of skepticism in various industries, particularly regulated industries, financial services, healthcare. And then when Govcloud hit and the CIA deal hit, people said, whoa CIA, they're like the most security conscious industry or organization in the world. And so I feel as though in a way public sector led that that breakthrough. So I'm wondering when you think about EC two today and the momentum that it has in the government, Are there similar things that you see? Where's the momentum today in public sector? >>You are right on target day? I mean that CIA was a monumental moment and that momentum with ever increasing adoption to the cloud has continued in public sector. In fact today, public sector is one of our fastest growing areas. So we've got um, you know, thousands of startups or multiple countries that were helping out today to really ignite that innovation. We have over 4000 government agencies, 9000 education agencies. Um 2000 public sector partners from all over the globe. 24,000 not for profit organizations. And what I see is the way that they're using EC two um is is leading the pack now, especially after Covid, you know, many of these folks accelerated their journey because of Covid. They got to the cloud faster and now they are doing some really things that no one else is doing like sending an outpost postbox into space or leveraging, you know robots and health care for sure. So that momentum continues today and I love that you were the champion of that you know way back when even when you were with I. D. C. >>So I want to ask you, you sort of touched on some interesting use cases, what are some of the more unusual ones and maybe breakthrough use cases that you see? >>Oh so yeah we have a couple. So one is um I mentioned it earlier but there is a robot now that is powered by IOT and EC two and the robot helps to take temperature and and readings for folks that are entering the hospital in latin America really helped during Covid, one of my favorites. It actually blew the socks off of verne or two and you know that's hard to do is a space startup called lunar outpost and they are synthesizing oxygen on mars now that's, that's driven by Ec two. That's crazy. Right? Um, we see state governments like new york, they've got this vision zero traffic and they're leveraging that to prevent accidents all through new york city. I used to live in new york city. So this is really needed. Um, and it continues like with education, we see university of Illinois and Splunk one of our partners, they created a boarding pass for students to get back to school. So I have a daughter in college. Um, and you know, it's really hard for her to prove that she's had the vaccine or that she's tested negative on the covid test. They came out with a past of this little boarding pass, just like you used to get on an airplane to get into different classes and labs and then a couple of my favorites and you guys actually filmed the Cherokee nation. So the Cherokee nation, the chief of the Cherokee nation was on our silicon um show and silicon angles show and the cube featured them And as the chief talked about how he preserves the Cherokee language. And if you remember the Cherokee language has been used to help out the US in many different ways and Presidio. One of our partners helped to create a game, a super cool game that links in with unity To help teach that next generation the language while they're playing a game and then last but not least axle three d out of the UK. Um, they're using easy to, to save lives. They've created a three D imaging process for people getting ready to get kidney transplants and they have just enhanced that taken the time frame down for months. Now today's that they can actually articulate whether the kidney transplant will work. And when I talked to roger their Ceo, they're doing R. O. L return on life's not return on investment. So those are just some of the unusual and breakthrough use cases that we see powered by E. C. To >>Sandy. I'll give you the last word. Your final closing comments. >>Well, my final closing comments are happy birthday to ec two celebrating 15 years. What a game changer and value added. It has been the early days of Ec two. Of course we're about education like what is the cloud? Why is a bookseller doing it. But um, easy to really help to create a new hub of value Now. We've got customers moving so fast with modernization using a I. M and M. L. Containers survivalists. Um, and all of these things are really changing the game and leveling it up as we increased that business connection. So I think the future is really bright. We've only just begun. We've only just begun with EC two and we've only just begun with public sector. You know, our next great moments are still left to come. >>Well, Sandy, thanks so much. Always Great to see you. Really appreciate your time. >>Thank you so much. Dave. I really appreciate it. And happy birthday again to E. C. To keep >>It right there were celebrating Ec 2's 15th birthday right back. >>Mhm.

(bright music) >> Welcome to this session of the AWS EC2 15th birthday event. I'm your host, Lisa Martin. I'm joined by Meena Gowdar, the principal product manager for AWS Outposts at AWS. Meena, welcome to the program. >> Thanks Lisa. It's great to be joining here today. >> So you were the first product manager hired to lead the development of the Outpost service. Talk to us about back in the day. The vision of Outpost at that time. >> Yeah, Outpost vision has always been to extend the AWS experience to customers on premises location, and provide a truly consistent hybrid experience, with the same AWS services, APIs and suite of tools available at the region. So we launched Outpost to support customers' workloads that cannot migrate to the region. These are applications that are sensitive to latency, such as manufacturing, workloads, financial trading workloads. Then there are applications that do heavy edge data processing, like image assisted diagnostics and hospitals for example, or smart cities that are fitted with cameras and sensors that gather so much data. And then another use case was regarding data residency that need to remain within certain jurisdictions. Now that AWS cloud is available in 25 regions and we have seven more coming, but that doesn't cover every corner of the world, and customers want us to be closer to their end-users. So Outpost allows them to bring the AWS experience where customer wants us to be. To answer your question about the use case evolution, along the way, in addition to the few that I just mentioned, we've seen a couple of surprises. The first one is application migration. It is an interesting trend from large enterprises that could run applications in the cloud, but must first rearchitect their applications to be cloud ready. These applications need to go through modernization while remaining in close proximity to other dependent systems. So by using Outpost, customers can modernize and containerize using AWS services, while they continued to remain on premises before moving to the region. Here, Outpost acts as a launchpad, serving them to make that leap to the region. We were also surprised by the different types of data residency use cases that customers are thinking about Outposts. For example, iGaming, as sports betting is a growing trend in many countries, they're also heavily regulated requiring providers to run their applications within state boundaries. Outposts allows application providers to standardize on a common AWS infrastructure and deploy the application in as many locations as they want to scale. >> So a lot of evolution and it's short time-frame, and I know that as we're here talking about the EC2 15th birthday, Amazon EC2 Core to AWS, but it's also at the core of Outposts, how does EC2 work on Outposts? >> The simple answer is EC2 works just the same as Outposts does in the region, so giving customers access to the same APIs, tools, and metrics that they are familiar with. With Outposts, customers will access the capacity, just like how they would access them in an availability zone. Customers can extend their VPC from the region and launch EC2 instances using the same APIs, just like how they would do in the region. So they also get to benefit all the tools like auto-scaling, CloudWatch metrics, Flow Logs that they are already familiar with. So the other thing that I also want to share is, at GA, we launched Outposts with the Gen 5 Intel Cascade Lake Processor based instances, that's because they run on AWS Nitro Systems. The Nitro Systems allows us to extend the AWS experience to customers location in a secure manner, and bring all the capabilities to manage and virtualize the underlying compute storage and network capabilities, just the way we do that in the region. So staying true to that Outpost product vision, customers can experience the same sort of EC2 feature sets like EC2 placement groups on demand, capacity, reservations, sharing through resource access managers, IM policies, and security groups so it really is the same EC2. >> I imagine having that same experience, the user experience was a big advantage for customers that were in the last 18 months rapidly transforming and digitizing their businesses. Any customer examples pop up that to you that really speak to, we kept this user experience the same, it really helped customers pivot quickly when the pandemic struck. >> It almost feels like we haven't missed a beat Outpost being a fully managed service that can be rolled into customer's data center, has been a huge differentiator. Especially at a time where customers have to be nimble and ready to respond to their customers or end users. If at all, we've seen the adoption accelerate in the last 12 to 18 months, and that is reflected through our global expansion. We currently support 60 countries worldwide, and we've seen customers deploying Outposts and migrating more applications to run on Outpost worldwide. >> Right. So lots of evolution going on as I mentioned a minute ago. Talk to me about some of the things that you're most excited about. What do you think is coming down the pike in the next 6 to 10 months? >> We're excited about expanding the core EC2 instance offerings, especially bringing our own Graviton Arm processor based instances on Outposts, because of the AWS nitro systems. Most easy to instances that launch in the region will also become available on Outpost. Again, back to the vision to provide a consistent hybrid experience for AWS customers. We're also excited about the 1U and 2U Outpost server form factors, which we will launch later this year. The Outpost service will support both the Intel Ice Lake Processor based instances, and also Graviton Processor based instances. So customers who can't install and, you know, 42U form factor Outposts, can now bring AWS experience in retail stores, back office, and other remote locations that are not traditional data centers. So we're very excited about our next couple of years, and what we are going to be launching for customers. >> Excellent. Meena, Thank you for joining me today for the EC2 15th birthday, talking about the vision of outposts. Again, you were the first product manager hired to lead the development of that. Pretty exciting. What's gone on then the unique use cases that have driven its evolution, and some of the things that are coming down the pike. Very exciting. Thank you for your time. >> Thank you, Lisa, >> For Meena Gowdar, I'm Lisa Martin. Thanks for watching. (bright music)

>>Mhm Hello, I'm jennifer with the cube. We're here at Rogers vice president of EC two Product Manager, NWS raj. Thanks for coming off its quick cube conversation. Um Congratulations on your 15th birthday of E C two. You get the keys to the kingdom of one of the hottest products. The most important product you look at. I look at our billets. Ec two is the highest, it's always the best everyone focuses on. It's the compute a lot of other goodness with amazon cloud. Thanks for coming on. >>Thank you. Thanks for having me. >>So, can you break down the graviton two processor overview? Why is custom Silicon important and why should architects and developers understand the opportunity with graviton to these are the other opportunities within 80 bucks. What's the, what's the magic do it we should that they think about as the architect their cloud. >>Yeah. So, I mean, I think why it's important is what you said like so much uh the workloads that they're running at the end of the day is running on EC two, whether it's running on Ec two directly or running on one of the other AWS services that's built on a C two and when you have, when you're able to, when we're able to innovate and deliver a very significant price performance advantage, not just lowers their costs. So like there, It's hardly a day of industry where you're able to go and do a pretty simple migration and get a 40% price performance improvement and that's huge and I think that's why this is, you know, raising a lot of interest. Is that um, customers, I found it relatively easy to go and do this migration and get that benefit. >>That's awesome mirage. I gotta ask you ec two offers more than 400 instant types with different combinations of compute memory, networking and storage, which is obviously the backbone of the cloud. A lot of people that are coming in learning about clouds, what does it mean that there's all these instances that because it's just more combinations, different workloads, why 400 instance types? What does that mean for someone learning about clouds? Does it mean anything to you actually? Would you explain the difference of instance types of 400 of them? >>Yeah. So, I mean when you think about an instance type, it's essentially configuration of a virtual machine, there's a certain amount of memory, there's a certain amount of processing power. Uh there could be a certain amount of disk and workloads, uh, the different ratios of these uh, dimensions, these characteristics. So by offering selection across a wide variety of instances were really able to optimize the compute that particular workload needs. The customers could essentially uh, increase their performance and have a more optimized price for what they want to get done. So ultimately, that's what that's what it's about having the right form factor for a given workload and the more configurations that we have, the more we're able to tune for those workloads. >>It's like having a driver riding a car you want the driver type to match the road, match the engine. So the instance has to match the profile of the app, the workload and kind of, and is that kind of where you're getting at getting met? You can do that. >>Yeah. And you know, and one of the things that we're also investing in at the same time as tools to enable customers to realize and learn what the right instance is. So, you know, we launched about a year ago uh capability called compute optimizer that lets customers look at their workloads, you know, in flight essentially and make recommendations saying, hey, instead of this instance, you know, you could Move to um this other instance type and save 50% or you know, as an example. So, um, you know, part of it, creating the selection and the other part of it is creating the tools. So customers, do you know what the right fit is for them so that they can really optimize their thin >>Well Roger, I really preach this is going to ask me anything guru question, but here's the simple one. What is gravitas to, at the end of the day when someone asks you what is graviton too? >>Yeah. So I mean grandma can do is a processor, it's a chip, it's a CPU um and so what that means essentially is and it's an arm. Basic. So um, you know, with, with are just like you have intel and AMG processors, these are the, the circuitry and the computer that does the work. Right. And um with, with Gravitas on we support arm which is a different architecture set but one that has been around long enough and it's pretty ubiquitous across mobile devices and servers now. So the operating systems that you know, you know all the Linux operating system, the tools that you know, they all work and are able to run on Graviton too. So this means that when you have applications, you can very easily take it from the same AMG or intel X 86 platform and move it over and just get the efficiencies that gravity to offers with lower power envelope and higher performance >>there it is many master class here at raj. Pie Vice President Ec two product management laying down the graviton to knowledge and for folks learning about cloud and architects really want to know the difference. It's a 40% performance improvement, lower power envelope, 20% less than cost. I believe something those range about right about in the same territory there. So basically high performance, lower costs, better power. So for workloads that demanded you got the option raj. Thank you for sharing. Thank you. All right. I'm john for, with the cube Thanks for watching. Mhm mm

>>Hi lisa martin here with the cubes coverage of demon 2021. I've got to alumni joining me. Please welcome back to the cube Danny. Alan beam's ceo Danny. It's great to see you. >>I am delighted to be here lisa. >>Excellent brian Schwartz is here as well. Google director outbound product management brian welcome back to the program. Uh >>thanks for having me again. Excited to be >>here. Excited to be here. Yes, definitely. We're gonna be talking all about what Demon google are doing today. But let's go ahead and start Danny with you. Seems vision is to be the number one trusted provider of backup and recovery solutions for the, for for modern data protection. Unpack that for me, trust is absolutely critical. But when you're talking about modern data protection to your customers, what does that mean? >>Yeah. So I always, I always tell our customers there's three things in there that are really important. Trust is obviously number one and google knows this. You've been the most trusted search provider uh, forever. And, and so we have 400,000 customers. We need to make sure that our products work. We need to make sure they do data protection, but we need to do it in a modern way. And so it's not just back up and recovery, that's clearly important. It's also all of the automation and orchestration to move workloads across infrastructures, move it from on premises to the google cloud, for example, it also includes things like governance and compliance because we're faced with ransomware, malware and security threats. And so modern data protection is far more than just back up. It's the automation, it's the monitoring, it's a governance and compliance. It's the ability to move workloads. Um, but everything that we look at within our platform, we focus on all of those different characteristics and to make sure that it works for our customers. >>One of the things that we've seen in the last year, Danny big optic in ransom were obviously the one that everyone is the most familiar with right now. The colonial pipeline. Talk to me about some of the things that the team has seen, what your 400,000 customers have seen in the last 12 months of such a dynamic market, a massive shift to work from home and to supporting SAS for clothes and things like that. What have you seen? >>Well, certainly the employees working from home, there's a massive increase in the attack surface for organizations because now, instead of having three offices, they have, you know, hundreds of locations for their end users. And so it's all about protecting their data at the same time as well. There's been this explosion in malware and ransomware attacks. So we really see customers focusing on three different areas. The first is making sure that when they take a copy of their data, that it is actually secure and we can get into, you know, a mutability and keeping things offline. But really taking the data, making sure it's secure. The second thing that we see customers doing is monitoring their environment. So this is both inspection of the compute environment and of the data itself. Because when ransomware hits, for example, you'll see change rates on data explode. So secure your data monitor the environment. And then lastly make sure that you can recover intelligently is let us say because the last thing that you want to do if you're hit by ransomware is to bring the ransomware back online from a backup. So we call this security cover re secure, restore. We really see customers focusing on those three areas >>And that restoration is critical there because as we know these days, it's not if we get hit with ransomware, it's really a matter of when. Let's go ahead now and go into the google partnership, jenny talked to me about it from your perspective, the history of the strength of the partnership, all that good stuff. >>Yeah. So we have a very deep and long and lengthy relationship with google um, on a number of different areas. So for example, we have 400,000 customers. Where do they send their backups? Most customers don't want to continue to invest in storage solutions on their premises. And so they'll send their data from on premises and tear it into google cloud storage. So that's one integration point. The second is when the running workloads within the clouds. So this is now cloud native. If you're running on top of the google cloud platform, we are inside the google America place and we can protect those workloads. A third area is around the google vm ware engine, there's customers that have a hybrid model where they have some capacity on premises and some in google using the VM ware infrastructure and we support that as well. That's a third area and then 1/4 and perhaps the longest running um, google is synonymous with containers and especially kubernetes, they were very instrumental in the foundations of kubernetes and so r K 10 product which does data protection for kubernetes is also in the google America place. So a very long and deep relationship with them and it's to the benefit of our customers. >>Absolutely. And I think I just saw the other day that google celebrated the search engine. It's 15th birthday. I thought what, what did we do 16 years ago when we couldn't just find anything we wanted brian talked to me about it from Google's perspective of being partnership. >>Yeah, so as Danny mentioned, it's really multifaceted, um it really starts with a hybrid scenario, you know, there's still a lot of customers that are on their journey into the cloud and protecting those on premises workloads and in some senses, even using beams capabilities to move data to help migrate into the cloud is I'd say a great color of the relationship. Um but as Danny mentioned increasingly, more and more primary applications are running in the cloud and you know, the ability to protect those and have, you know, the great features and capabilities, uh you know, that being provides, whether it be for GCB er VM where you know, capability and google cloud or things like G k e R kubernetes offering, which has mentioned, you know, we've been deep and wide in kubernetes, we really birthed it many, many years ago um and have a huge successful business in, in the managing and hosting containers, that having the capabilities to add to those. It really adds to our ecosystem. So we're super excited about the partnership, we're happy to have this great foundation to build together with them into the future. >>And Danny Wien launched, just been in february a couple of months ago, being backup for google cloud platform. Talk to us about that technology and what you're announcing at them on this year. >>Yeah, sure. So back in february we released the first version of the VM backup for G C p product in the marketplace and that's really intended to protect of course, i as infrastructure as a service workloads running on top of G C p and it's been very, very successful. It has integration with the core platform and what I mean by that is if you do a backup in G C P, you can do you can copy that back up on premises and vice versa. So it has a light integration at the data level. What we're about to release later on this summer is version two of that product that has a deep integration with the VM platform via what we call the uh team service platform, a PS themselves. And that allows a rich bidirectional uh interaction between the two products that you can do not just day one operations, but also day to operations. So you can update the software, you can harmonize schedules between on premises and in the cloud. It really allows customers to be more successful in a hybrid model where they're moving from on premises to the cloud. >>And that seems to be really critically important. As we talk about hybrid club all the time, customers are in hybrid. They're living in the hybrid cloud for many reasons, whether it's acquisition or you know, just the nature of lines of business leveraging their cloud vendor of choice. So being able to support the hybrid cloud environment for customers and ensure that that data is recoverable is table stakes these days. Does that give them an advantage over your competition Danny? >>It does. Absolutely. So customers want the hybrid cloud experience. What we find over time is they do trend towards the cloud. There's no question. So if you have the hybrid experience, if they're sending their data there, for example, a step one, step two, of course, is just to move the workload into the cloud and then step three, they really start to be able to unleash their data. If you think about what google is known for, they have incredible capabilities around machine learning and artificial intelligence and they've been doing that for a very long time. So you can imagine customers after they start putting their data there, they start putting their workloads here, they want to unlock it into leverage the insights from the data that they're storing and that's really exciting about where we're going. It's, they were early days for most customers. They're still kind of moving and transitioning into the cloud. But if you think of the capabilities that are unlocked with that massive platform in google, it just opens up the ability to address big challenges of today, like climate change and sustainability and you know, all the health care challenges that we're faced with it. It really is an exciting time to be partnered with Google >>Ryan. Let's dig into the infrastructure in the architecture from your perspective, help us unpack that and what customers are coming to you for help with. >>Yeah. So Danny mentioned, you know the prowess that google has with data and analytics and, and a, I I think we're pretty well known for that. Uh, there's a tremendous opportunity for people in the future. Um, the thing that people get just right out of the box is the access to the technology that we built to build google cloud itself. Just the scale and, and technology, it's, you know, it's, it's a, you know, just incredible. You know, it's a fact that we have eight products here at google that have a billion users and when you have, you know, most people know the search and maps and gmail and all these things. When you have that kind of infrastructure, you build a platform like google cloud platform and you know, the network as a perfect example, the network endpoints, they're actually close to your house. There's a reason our technology is so fast because you get onto the google private network, someplace really close to where you actually live. We have thousands and thousands of points of presence spread around the world and from that point forward you're riding on our internal network, you get better quality of service. Uh the other thing I like to mention is, you know, the google cloud storage, that team is built on our object storage. It's uh it's the same technology that underpins Youtube and other things that most people are familiar with and you just think about that for a minute, you can find the most obscure Youtube video and it's gonna load really fast. You know, you're not going to sit there waiting for like two minutes waiting for something to load and that same under underlying technology underpins GCS So when you're going to go and you know, go back to an old restore, you know, to do a restore, it's gonna load fast even if you're on one of the more inexpensive storage classes. So it's a really nice experience for data protection. It has this global network properties you can restore to a different region if there was ever a disaster, there's just the scale of our foundation of infrastructure and also, you know, Danny mentioned if we're super proud about the investments that google has made for sustainability, You know, our cloud runs on 100% renewable energy at the cloud at our scale. That's a lot of, that's a lot of green energy. We're happy to be one of the largest consumers of green energy out there and make continued investments in sustainability. So, you know, we think we have some of the greenest data centers in the world and it's just one more benefit that people have when they come to run on Google Cloud. >>I don't know what any of us would do without google google cloud platform or google cloud storage. I mean you just mentioned all of the enterprise things as well as the at home. I've got to find this really crazy, obscure youtube video but as demanding customers as we are, we want things asAP not the same thing. If you know, an employee can't find a file or calendar has been deleted or whatnot. Let's go in to finish our time here with some joint customer use case examples. Let's talk about backing up on prem workloads to google cloud storage using existing VM licensing Danny. Tell us about that. >>Yeah. So one of the things that we've introduced at beam is this beam, universal licensing and it's completely portable license, you can be running your workloads on premises now and on a physical system and then you can, you know, make that portable to go to a virtual system and then if you want to go to the cloud, you can send that data up to the work load up to the cloud. One of the neat things about this transition for customers from a storage perspective, we don't charge for that. If you're backing up a physical system and sending your your back up on premises, you know, we don't charge for that. If you want to move to the cloud, we don't charge for that. And so as they go through this, there's a predictability and and customers want that predictability so much um that it's a big differentiating factor for us. They don't want to be surprised by a bill. And so we just make it simple and seamless. They have a single licensing model and its future proof as they move forward on the cloud journey. They don't have to change anything. >>Tell me what you mean by future proof as a marketer. I know that term very well, but it doesn't mean different things to different people. So for means customers in the context of the expansion of partnership with google the opportunities, the choices that you're giving customers to your customers, what does future proof actually delivered to them? >>It means that they're not locked into where they are today. If you think about a customer right now that's running a workload on premises maybe because they have to um they need to be close to the data that's being generated or feeding into that application system. Maybe they're locked into that on premises model. Now they have one of two choices when their hardware gets to the end of life. They can either buy more hardware which locks them into where they are today for the next three years in the next four years Or they can say, you know what, I don't want to lock into that. I want to model the license that is portable that maybe 12 months from now, 18 months from now, I can move to the cloud and so it future proof some, it doesn't give them another reason to stay on premises. It allows them the flexibility that licensing is taken off the table because it moves with you that there's zero thought or consideration and that locks you into where you are today. And that's exciting because it unlocks the capabilities of the cloud without being handicapped if you will by what you have on premises. >>Excellent. Let's go to the second uh use case lift and shift in that portability brian. Talk to us about it from your perspective. >>Yeah, so we obviously constantly in discussions with our customers about moving more applications to the cloud and there's really two different kind of approach is the lift and shift and modernization. You know, do you want to change and run on kubernetes when you come to the cloud as you move it in? In some cases people want to do that or they're gonna obviously build a new application in the cloud. But increasingly we see a lot of customers wanting to do lift and shift, they want to move into the cloud relatively quickly. As Danny said, there's like compelling events on like refreshes and in many cases we've had a number of customers come to us and say look we're going to exit our data centers. We did a big announcement Nokia, they're gonna exit 50 data centers in the coming years around the world and just move that into the cloud. In many cases you want to lift and shift that application to do the migration with his little change as possible. And that's one of the reasons we've really invested in a lot of enterprise, more classic enterprise support type technologies. And also we're super excited to have a really wide set of partners and ecosystem like the folks here at Wien. So the customers can really preserve those technologies, preserve that operational experience that they're already familiar with on prem and use that in the cloud. It just makes it easier for them to move to the cloud faster without having to rebuild as much stuff on the way in. >>And that's critical. Let's talk about one more use case and that is native protection of workloads that run on g c p Danny. What are you enabling customers to do there? >>Well? So we actually merged the capabilities of two different things. One is we leverage the native Api is of G C p to take a snapshot and we merge that with our ability to put it in a portable data format. Now. Why is that important? Because you want to use the native capabilities of G CPU want to leverage those native snapshots. The fastest way to recover a file or the fastest way to recover of'em is from the G C p snapshot. However, if you want to take a copy of that and move it into another locale or you want to pull it back on premises for compliance reasons or put it in a long term storage format, you probably want to put it in GCS or in our portable storage format. And so we merge those two capabilities, the snapshot and back up into a single product. And in addition to that, one of the things that we do, again, I talked about predictability. We tell customers what that policy is going to cost them because if for example a customer said, well I like the idea of doing my backups in the cloud, but I want to store it on premises. We'll tell them, well if you're copying that data continually, you know what the network charges look like, What the CPU and compute charges look like, What do the storage costs looks like. So we give them the forecast of what the cost model looks like even before they do a single backup. >>That forecasting has got to be key, as you said with so much unpredicted things that we can't predict going on in this world the last year has taught us that with a massive shift, the acceleration of digital business and digital transformation, it's really critical that customers have an idea of what their costs are going to be so that they can make adjustments and be agile as they need the technology to be. Last question Bryant is for you, give us a view uh, and all the V mon attendees, what can we expect from the partnership in the next 12 >>months? You know, we're excited about the foundation of the partnership across hybrid and in cloud for both VMS and containers. I think this is the real beginning of a long standing relationship. Um, and it's really about a marriage of technology. You think about all the great data protection and orchestration, all the things that Danny mentioned married with the cloud foundation that we have at scale this tremendous network. You know, we just signed a deal with SpaceX in the last couple of days to hook their satellite network up to the google cloud network, you know, chosen again because we just have this foundational capability to push large amounts of data around the world. And that's you know, for Youtube. We signed a deal with Univision, same type of thing, just massive media uh, you know, being pushed around the world. And if you think about it that that same foundation is used for data protection. Data protection. There's a lot of data and moving large sets of data is hard. You know, we have just this incredible prowess and we're excited about the future of how our technology and beans. Technology is going to evolve over time >>theme and google a marriage of technology Guys, thank you so much for joining me, sharing what's new? The opportunities that demand google are joined me delivering to your joint customers. Lots of great step. We appreciate your time. >>Thanks lisa >>For Danielle in and Brian Schwartz. I'm Lisa Martin. You're watching the cubes coverage of Lehman 2021.

>>mhm Yes, Welcome back to the cubes coverage of red hat summit 2021 virtual, which we were in person this year but we're still remote. We still got the Covid coming around the corner. Soon to be in post. Covid got a great guest here, Clayton Coleman architect that red hat cuba love and I've been on many times expanded role again this year. More cloud, more cloud action. Great, great to see you. Thanks for coming on. >>It's a pleasure >>to be here. So great to see you were just riffing before we came on camera about distributed computing uh and the future of the internet, how it's all evolving, how much fun it is, how it's all changing still. The game is still the same, all that good stuff. But here at Red had some and we're gonna get into that, but I want to just get into the hard news and the real big, big opportunities here you're announcing with red hat new managed cloud services portfolio, take us through that. >>Sure. We're continuing to evolve our open shift managed offerings which has grown now to include um the redhead open shift service on amazon to complement our as your redhead open shift service. Um that means that we have um along with our partnership on IBM cloud and open ship dedicated on both a W S and G C P. We now have um managed open shift on all of the major clouds. And along with that we are bringing in and introducing the first, I think really the first step what we see as uh huh growing and involving the hybrid cloud ecosystem on top of open shift and there's many different ways to slice that, but it's about bringing capabilities on top of open shift in multiple environments and multiple clouds in ways that make developers and operation teams more productive because at the heart of it, that's our goal for open shift. And the broader, open source ecosystem is do what makes all of us safer, more, uh, more productive and able to deliver business value? >>Yeah. And that's a great steak you guys put in the ground. Um, and that's great messaging, great marketing, great value proposition. I want to dig into a little bit with you. I mean, you guys have, I think the only native offering on all the clouds out there that I know of, is that true? I mean, you guys have, it's not just, you know, you support AWS as your and I B M and G C P, but native offerings. >>We do not have a native offering on GCPD offered the same service. And this is actually interesting as we've evolved our approach. You know, everyone, when we talk about hybrid, Hybrid is, um, you know, dealing with the realities of the computing world, We live in, um, working with each of the major clouds, trying to deliver the best immigration possible in a way that drives that consistency across those environments. And so actually are open shift dedicated on AWS service gave us the inspiration a lot of the basic foundations for what became the integrated Native service. And we've worked with amazon very closely to make sure that that does the right thing for customers who have chosen amazon. And likewise, we're trying to continue to deliver the best experience, the best operational reliability that we can so that the choice of where you run your cloud, um, where you run your applications, um, matches the decisions you've already made and where your future investments are gonna be. So we want to be where customers are, but we also want to give you that consistency. That has been a hallmark of um of open shift since the beginning. >>Yeah. And thanks for clarifying, I appreciate that because the manage serves on GCB rest or native. Um let me ask about the application services because Jeff Barr from AWS posted a few weeks ago amazon celebrated their 15th birthday. They're still teenagers uh relatively speaking. But one comment he made that he that was interesting to me. And this applies kind of this cloud native megatrend happening is he says the A. P. I. S are basically the same and this brings up the hybrid environment. You guys are always been into the api side of the management with the cloud services and supporting all that. As you guys look at this ecosystem in open source. How is the role of A PS and these integrations? Because without solid integration all these services could break down and certainly the open source, more and more people are coding. So take me through how you guys look at these applications services because many people are predicting more service is going to be on boarding faster than ever before. >>It's interesting. So um for us working across multiple cloud environments, there are many similarities in those mps, but for every similarity there is a difference and those differences are actually what dr costs and drive complexity when you're integrating. Um and I think a lot of the role of this is, you know, the irresponsible to talk about the role of an individual company in the computing ecosystem moving to cloud native because as many of these capabilities are unlocked by large cloud providers and transformations in the kinds of software that we run at scale. You know, everybody is a participant in that. But then you look at the broad swath of developer and operator ecosystem and it's the communities of people who paper over those differences, who write run books and build um you know, the policies and who build the experience and the automation. Um not just in individual products or an individual clouds, but across the open source ecosystem. Whether it's technologies like answerable or Terror form, whether it's best practices websites around running kubernetes, um every every part of the community is really involved in driving up uh driving consistency, um driving predictability and driving reliability and what we try to do is actually work within those constraints um to take the ecosystem and to push it a little bit further. So the A. P. I. S. May be similar, but over time those differences can trip you up. And a lot of what I think we talked about where the industry is going, where where we want to be is everyone ultimately is going to own some responsibility for keeping their services running and making sure that their applications and their businesses are successful. The best outcome would be that the A. P. R. S are the same and they're open and that both the cloud providers and the open source ecosystem and vendors and partners who drive many of these open source communities are actually all working together to have the most consistent environment to make portability a true strength. But when someone does differentiate and has a true best to bring service, we don't want to build artificial walls between those. I mean, I mean, that's hybrid cloud is you're going to make choices that make sense for you if we tell people that their choices don't work or they can't integrate or, you know, an open source project doesn't support this vendor, that vendor, we're actually leaving a lot of the complexity buried in those organizations. So I think this is a great time to, as we turn over for cloud. Native looking at how we, as much as possible try to drive those ap is closer together and the consistency underneath them is both a community and a vendor. And uh for red hat, it's part of what we do is a core mission is trying to make sure that that consistency is actually real. You don't have to worry about those details when you're ignoring them. >>That's a great point. Before I get into some architectural impact, I want to get your thoughts on um, the, this trends going on, Everyone jumps on the bandwagon. You know, you say, oh yeah, I gotta, I want a data cloud, you know, everything is like the new, you know, they saw Snowflake Apollo, I gotta have some, I got some of that data, You've got streaming data services, you've got data services and native into the, these platforms. But a lot of these companies think it's just, you're just gonna get a data cloud, just, it's so easy. Um, they might try something and then they get stuck with it or they have to re factor, >>how do you look >>at that as an architect when you have these new hot trends like say a data cloud, how should customers be thinking about kicking the tires on services like that And how should they think holistically around architect in that? >>There's a really interesting mindset is, uh, you know, we deal with this a lot. Everyone I talked to, you know, I've been with red hat for 10 years now in an open shift. All 10 years of that. We've gone through a bunch of transformations. Um, and every time I talked to, you know, I've talked to the same companies and organizations over the last 10 years, each point in their evolution, they're making decisions that are the right decision at the time. Um, they're choosing a new capability. So platform as a service is a great example of a capability that allowed a lot of really large organizations to standardize. Um, that ties into digital transformation. Ci CD is another big trend where it's an obvious wind. But depending on where you jumped on the bandwagon, depending on when you adopted, you're going to make a bunch of different trade offs. And that, that process is how do we improve the ability to keep all of the old stuff moving forward as well? And so open api is open standards are a big part of that, but equally it's understanding the trade offs that you're going to make and clearly communicating those so with data lakes. Um, there was kind of the 1st and 2nd iterations of data lakes, there was the uh, in the early days these capabilities were knew they were based around open source software. Um, a lot of the Hadoop and big data ecosystem, you know, started based on some of these key papers from amazon and google and others taking infrastructure ideas bringing them to scale. We went through a whole evolution of that and the input and the output of that basically let us into the next phase, which I think is the second phase of data leak, which is we have this data are tools are so much better because of that first phase that the investments we made the first time around, we're going to have to pay another investment to make that transformation. And so I've actually, I never want to caution someone not to jump early, but it has to be the right jump and it has to be something that really gives you a competitive advantage. A lot of infrastructure technology is you should make the choices that you make one or two big bets and sometimes people say this, you call it using their innovation tokens. You need to make the bets on big technologies that you operate more effectively at scale. It is somewhat hard to predict that. I certainly say that I've missed quite a few of the exciting transformations in the field just because, um, it wasn't always obvious that it was going to pay off to the degree that um, customers would need. >>So I gotta ask you on the real time applications side of it, that's been a big trend, certainly in cloud. But as you look at hybrid hybrid cloud environments, for instance, streaming data has been a big issue. Uh any updates there from you on your managed service? >>That's right. So one of we have to manage services um that are both closely aligned three managed services that are closely aligned with data in three different ways. And so um one of them is redhead open shift streams for Apache Kafka, which is managed cloud service that focuses on bringing that streaming data and letting you run it across multiple environments. And I think that, you know, we get to the heart of what's the purpose of uh managed services is to reduce operational overhead and to take responsibilities that allow users to focus on the things that actually matter for them. So for us, um managed open shift streams is really about the flow of data between applications in different environments, whether that's from the edge to an on premise data center, whether it's an on premise data center to the cloud. And increasingly these services which were running in the public cloud, increasingly these services have elements that run in the public cloud, but also key elements that run close to where your applications are. And I think that bridge is actually really important for us. That's a key component of hybrid is connecting the different locations and different footprints. So for us the focus is really how do we get data moving to the right place that complements our API management service, which is an add on for open ship dedicated, which means once you've brought the data and you need to expose it back out to other applications in the environment, you can build those applications on open shift, you can leverage the capabilities of open shift api management to expose them more easily, both to end customers or to other applications. And then our third services redhead open shift data science. Um and that is a, an integration that makes it easy for data scientists in a kubernetes environment. On open shift, they easily bring together the data to make, to analyze it and to help route it is appropriate. So those three facets for us are pretty important. They can be used in many different ways, but that focus on the flow of data across these different environments is really a key part of our longer term strategy. >>You know, all the customer checkboxes there you mentioned earlier. I mean I'll just summarize that that you said, you know, obviously value faster application velocity time to value. Those are like the checkboxes, Gardner told analysts check those lower complexity. Oh, we do the heavy lifting, all cloud benefits, so that's all cool. Everyone kind of gets that, everyone's been around cloud knows devops all those things come into play right now. The innovation focuses on operations and day to operations, becoming much more specific. When people say, hey, I've done some lift and shift, I've done some Greenfield born in the cloud now, it's like, whoa, this stuff, I haven't seen this before. As you start scaling. So this brings up that concept and then you add in multi cloud and hybrid cloud, you gotta have a unified experience. So these are the hot areas right this year, I would say, you know, that day to operate has been around for a while, but this idea of unification around environments to be fully distributed for developers is huge. >>How do you >>architect for that? This is the number one question I get. And I tease out when people are kind of talking about their environments that challenges their opportunities, they're really trying to architect, you know, the foundation that building to be um future proof, they don't want to get screwed over when they have, they realize they made a decision, they weren't thinking about day to operation or they didn't think about the unified experience across clouds across environments and services. This is huge. What's your take on this? >>So this is um, this is probably one of the hardest questions I think I could get asked, which is uh looking into the crystal ball, what are the aspects of today's environments that are accidental complexity? That's really just a result of the slow accretion of technologies and we all need to make bets when, when the time is right within the business, um and which parts of it are essential. What are the fundamental hard problems and so on. The accidental complexity side for red hat, it's really about um that consistent environment through open shift bringing capabilities, our connection to open source and making sure that there's an open ecosystem where um community members, users vendors can all work together to um find solutions that work for them because there's not, there's no way to solve for all of computing. It's just impossible. I think that is kind of our that's our development process and that's what helps make that accidental complexity of all that self away over time. But in the essential complexity data is tied the location, data has gravity data. Lakes are a great example of because data has gravity. The more data that you bring together, the bigger the scale the tools you can bring, you can invest in more specialized tools. I've almost do that as a specialization centralization. There's a ton of centralization going on right now at the same time that these new technologies are available to make it easier and easier. Whether that's large scale automation um with conflict management technologies, whether that's kubernetes and deploying it in multiple sites in multiple locations and open shift, bringing consistency so that you can run the apps the same way. But even further than that is concentrating, mhm. More of what would have typically been a specialist problem, something that you build a one off around in your organization to work through the problem. We're really getting to a point where pretty soon now there is a technology or a service for everyone. How do you get the data into that service out? How do you secure it? How do you glue it together? Um I think of, you know, some people might call this um you know, the ultimate integration problem, which is we're going to have all of this stuff and all of these places, what are the core concepts, location, security, placement, topology, latency, where data resides, who's accessing that data, We think of these as kind of the building blocks of where we're going next. So for us trying to make investments in, how do we make kubernetes work better across lots of environments. I have a coupon talk coming up this coupon, it's really exciting for me to talk about where we're going with, you know, the evolution of kubernetes, bringing the different pieces more closely together across multiple environments. But likewise, when we talk about our managed services, we've approached the strategy for managed services as it's not just the service in isolation, it's how it connects to the other pieces. What can we learn in the community, in our services, working with users that benefits that connectivity. So I mentioned the open shift streams connecting up environments, we'd really like to improve how applications connect across disparate environments. That's a fundamental property of if you're going to have data uh in one geographic region and you didn't move services closer to that well, those services I need to know and encode and have that behavior to get closer to where the data is, whether it's one data lake or 10. We gotta have that flexibility in place. And so those obstructions are really, and to >>your point about the building blocks where you've got to factor in those building blocks, because you're gonna need to understand the latency impact, that's going to impact how you're gonna handle the compute piece, that's gonna handle all these things are coming into play. So, again, if you're mindful of the building blocks, just as a cloud concept, um, then you're okay. >>We hear this a lot. Actually, there's real challenges in the, the ecosystem of uh, we see a lot of the problems of I want to help someone automate and improved, but the more balkanize, the more spread out, the more individual solutions are in play, it's harder for someone to bring their technology to bear to help solve the problem. So looking for ways that we can um, you know, grease the skids to build the glue. I think open source works best when it's defining de facto solutions that everybody agrees on that openness and the easy access is a key property that makes de facto standards emerged from open source. What can we do to grow defacto standards around multi cloud and application movement and application interconnect I think is a very, it's already happening and what can we do to accelerate it? That's it. >>Well, I think you bring up a really good point. This is probably a follow up, maybe a clubhouse talk or you guys will do a separate session on this. But I've been riffing on this idea of uh, today's silos, tomorrow's component, right, or module. If most people don't realize that these silos can be problematic if not thought through. So you have to kill the silos to bring in kind of an open police. So if you're open, not closed, you can leverage a monolith. Today's monolithic app or full stack could be tomorrow's building block unless you don't open up. So this is where interesting design question comes in, which is, it's okay to have pre existing stuff if you're open about it. But if you stay siloed, you're gonna get really stuck >>and there's going to be more and more pre existing stuff I think, you know, uh even the data lake for every day to lake, there is a huge problem of how to get data into the data lake or taking existing applications that came from the previous data link. And so there's a, there's a natural evolutionary process where let's focus on the mechanisms that actually move that day to get that data flowing. Um, I think we're still in the early phases of thinking about huge amounts of applications. Microservices or you know, 10 years old in the sense of it being a fairly common industry talking point before that we have service oriented architecture. But the difference now is that we're encouraging and building one developer, one team might run several services. They might use three or four different sas vendors. They might depend on five or 10 or 15 cloud services. Those integration points make them easier. But it's a new opportunity for us to say, well, what are the differences to go back to? The point is you can keep your silos, we just want to have great integration in and out of >>those. Exactly, they don't have to you have to break down the silos. So again, it's a tried and true formula integration, interoperability and abstracting away the complexity with some sort of new software abstraction layer. You bring that to play as long as you can paddle with that, you apply the new building blocks, you're classified. >>It sounds so that's so simple, doesn't it? It does. And you know, of course it'll take us 10 years to get there. And uh, you know, after cloud native will be will be galactic native or something like that. You know, there's always going to be a new uh concept that we need to work in. I think the key concepts we're really going after our everyone is trying to run resilient and reliable services and the clouds give us in the clouds take it away. They give us those opportunities to have some of those building blocks like location of geographic hardware resources, but they will always be data that spread. And again, you still have to apply those principles to the cloud to get the service guarantees that you need. I think there's a completely untapped area for helping software developers and software teams understand the actual availability and guarantees of the underlying environment. It's a property of the services you run with. If you're using a disk in a particular availability zone, that's a property of your application. I think there's a rich area that hasn't been mined yet. Of helping you understand what your effective service level goals which of those can be met. Which cannot, it doesn't make a lot of sense in a single cluster or single machine or a single location world the moment you start to talk about, Well I have my data lake. Well what are the ways my data leg can fail? How do we look at your complex web of interdependencies and say, well clearly if you lose this cloud provider, you're going to lose not just the things that you have running there, but these other dependencies, there's a lot of, there's a lot of next steps that we're just learning what happens when a major cloud goes down for a day or a region of a cloud goes down for a day. You still have to design and work around those >>cases. It's distributed computing. And again, I love the space where galactic cloud, you got SpaceX? Where's Cloud X? I mean, you know, space is the next frontier. You know, you've got all kinds of action happening in space. Great space reference there. Clayton, Great insight. Thanks for coming on. Uh, Clayton Coleman architect at red Hat. Clayton, Thanks for coming on. >>Pretty pleasure. >>Always. Great chat. I'm talking under the hood. What's going on in red hats? New managed cloud service portfolio? Again, the world's getting complex, abstract away. The complexities with software Inter operate integrate. That's the key formula with the cloud building blocks. I'm john ferry with the cube. Thanks for watching. Yeah.

(upbeat music) >> Welcome to this special cloud virtual event, theCUBE on cloud. This is our continuing editorial series of the most important stories in cloud. We're going to explore the cutting edge most relevant technologies and companies that will impact business and society. We have special guests from Jeff Barr, Michael Liebow, Jerry Chen, Ben Haynes, Michael skulk, Mike Feinstein from AWS all today are presenting the top startups in the AWS ecosystem. This is the AWS showcase of startups. I'm showing with Dave Vellante. Dave great to see you. >> Hey John. Great to be here. Thanks for having me. >> So awesome day today. We're going to feature a 10 grade companies amplitude, auto grid, big ID, cordial Dremio Kong, multicloud, Reltio stardog wire wheel, companies that we've talked to. We've researched. And they're going to present today from 10 for the rest of the day. What's your thoughts? >> Well, John, a lot of these companies were just sort of last decade, they really, were keyer kicker mode, experimentation mode. Now they're well on their way to hitting escape velocity which is very exciting. And they're hitting tens of millions dollars of ARR, many are planning IPO's and it's just it's really great to see what the cloud has enabled and we're going to dig into that very deeply today. So I'm super excited. >> Before we jump into the keynote (mumbles) our non Huff from AWS up on stage Jeremy is the brains behind this program that we're doing. We're going to do this quarterly. Jeremy great to see you, you're in the global startups program at AWS. Your job is to keep the crops growing, keep the startups going and keep the flow of innovation. Thanks for joining us. >> Yeah. Made it to startup showcase day. I'm super excited. And as you mentioned my team the global startup program team, we kind of provide white glove service for VC backed startups and help them with go to market activities. Co-selling with AWS and we've been looking for ways to highlight all the great work they're doing and partnering with you guys has been tremendous. You guys really know how to bring their stories to life. So super excited about all the partner sessions today. >> Well, I really appreciate the vision and working with Amazon this is like truly a bar raiser from theCUBE virtual perspective, using the virtual we can get more content, more flow and great to have you on and bring that the top hot startups around data, data ops. Certainly the most important story in tech is cloud scale with data. You you can't look around and seeing more innovation happening. So I really appreciate the work. Thanks for coming on. >> Yeah, and don't forget, we're making this a quarterly series. So the next one we've already been working on it. The next one is Wednesday, June 16th. So mark your calendars, but super excited to continue doing these showcases with you guys in the future. >> Thanks for coming on Jeremy. I really appreciate it,. Dave so I want to just quick quickly before we get Jeff up here, Jeff Barr who's a luminary guests for us this week who has been in the industry has been there from the beginning of AWS the role of data, and what's happened in cloud. And we've been watching the evolution of Amazon web services from the beginning, from the startup market to dominate in the enterprise. If you look at the top 10 enterprise companies Amazon wasn't on that list in 2010 they weren't even bringing the top 10 Andy Jassy's keynote at reinvent this past year. Highlighted that fact, I think they were number five or four as vendor in just AWS. So interesting to see that you've been reporting and doing a lot of analysis on the role of data. What's your analysis for these startups and as businesses need to embrace the new technologies and be on the right side of history not part of that old guard, incumbent failed model. >> Well, I think again, if you look back on the early days of cloud, it was really about storage and networking and compute infrastructure. And then we collected all this data and now you're seeing the next generation of innovation and value. We're going to talk to Michael Liebow about this is really if you look at all the value points in the leavers, it's all around data and data is going through a massive change in the way that we think about it, that we talk about it. And you hear that a lot. Obviously you talk about the volumes, the giant volumes but there's something else going on as AWS brings the cloud to the edge. And of course it looks at the data centers, just another edge device, data is getting highly decentralized. And what we're seeing is data getting into the hands of business owners and data product builders. I think we're going to see a new parlance emerge and that's where you're seeing the competitive advantage. And if you look at all the real winners these days in the marketplace especially in the digital with COVID, it all comes back to the data. And we're going to talk about that a lot today. >> One of the things that's coming up in all of our cube interviews, certainly we've seen, I mean we've had a great observation space across all the ecosystems, but the clear thing that's coming out of COVID is speed, agility, scale, and data. If you don't have that data you are going to be a non-player. And I think I heard some industry people talking about the future of how the stock market's going to work and that if you're not truly in market with an AI or machine learning data value play you probably will be shorted on the stock market or delisted. I think people are looking at that as a table stakes competitive advantage item, where if you don't have some sort of data competitive strategy you're going to be either delisted or sold short. And that's, I don't think delisted but the point is this table-stakes Dave. >> Well, I think too, I think the whole language the lingua franca of data is changing. We talk about data as an asset all the time, but you think about it now, what do we do with assets? We protect it, we hide it. And we kind of we don't share it. But then on the other hand, everybody talks about sharing the data and that is a huge trend in the marketplace. And so I think that everybody is really starting to rethink the whole concept of data, what it is, its value and how we think about it, talk about it, share it make it accessible, and at the same time, protect it and make it governed. And I think you're seeing, computational governance and automation really hidden. Couldn't do this without the cloud. I mean, that's the bottom line. >> Well, I'm super excited to have Jeff Barr here from AWS as our special keynote guests. I've been following Jeff's career for a long, long time. He's a luminaries, he's a technical, he's in the industry. He's part of the community, he's been there from the beginning AWS just celebrate its 15th birthday as he was blogging hard. He's been a hardcore blogger. I think Jeff, you had one of the original ping service. If I remember correctly, you were part of the web services foundational kind of present at creation. No better guests to have you Jeff thanks for coming up on our stage. >> John and Dave really happy to be here. >> So I got to ask you, you've been blogging hard for the past decade or so, going hard and your job has evolved from blogging about what's new with Amazon. A couple of building blocks a few services to last reinvent them. You must have put out I don't know how many blog posts did you put out last year at every event? I mean, it must have been a zillion. >> Not quite a zillion. I think I personally wrote somewhere between 20 and 25 including quite a few that I did in the month or so run up to reinvent and it's always intense, but it's always really, really fun. >> So I've got to ask you in the past couple of years, I mean I quoted Andy Jassy's keynote where we highlight in 2010 Amazon wasn't even on the top 10 enterprise players. Now in the top five, you've seen the evolution. What is the big takeaway from your standpoint as you look at the enterprise going from Amazon really dominating the start of a year startups today, you're in the cloud, you're born in the cloud. There's advantage to that. Now enterprises are kind of being reborn in the cloud at the same time, they're building these new use cases rejuvenating themselves and having innovation strategy. What's your takeaway? >> So I love to work with our customers and one of the things that I hear over and over again and especially the last year or two is really the value that they're placing on building a workforce that has really strong cloud skills. They're investing in education. They're focusing on this neat phrase that I learned in Australia called upskilling and saying let's take our set of employees and improve their skill base. I hear companies really saying we're going to go cloud first. We're going to be cloud native. We're going to really embrace it, adopt the full set of cloud services and APIs. And I also see that they're really looking at cloud as part of often a bigger picture. They often use the phrase digital transformation, in Amazon terms we'd say they're thinking big. They're really looking beyond where they are and who they are to what they could be and what they could grow into. Really putting a lot of energy and creativity into thinking forward in that way. >> I wonder Jeff, if you could talk about sort of how people are thinking about the future of cloud if you look at where the spending action is obviously you see it in cloud computing. We've seen that as the move to digital, serverless Lambda is huge. If you look at the data it's off the charts, machine learning and AI also up there containers and of course, automation, AWS leads in all of those. And they portend a different sort of programming model a different way of thinking about how to deploy workloads and applications maybe different than the early days of cloud. What's driving that generally and I'm interested in serverless specifically. And how do you see the next several years folding out? >> Well, they always say that the future is the hardest thing to predict but when I talked to our enterprise customers the two really big things that I see is there's this focus that says we need to really, we're not simply like hosting the website or running the MRP. I'm working with one customer in particular where they say, well, we're going to start on the factory floor all the way up to the boardroom effectively from IOT and sensors on the factory floor to feed all the data into machine learning. So they understand that the factory is running really well to actually doing planning and inventory maintenance to putting it on the website to drive the analytics, to then saying, okay, well how do we know that we're building the right product mix? How do we know that we're getting it out through the right channels? How are our customers doing? So they're really saying there's so many different services available to us in the cloud and they're relatively easy and straightforward to deploy. They really don't think in the old days as we talked about earlier that the old days where these multi-year planning and deployment cycles, now it's much more straightforward. It's like let's see what we can do today. And this week and this month, and from idea to some initial results is a much, much shorter turnaround. So they can iterate a lot more quickly which is just always known to produce better results. >> Well, Jeff and the spirit of the 15th birthday of AWS a lot of services have been built from the original three. I believe it was the core building blocks and there's been a lot of history and it's kind of like there was a key decoupling of compute from storage, those innovations what's the most important architectural change if any has happened or built upon those building blocks with AWS that you could share with companies out there as many people are coming into the cloud not just lifting and shifting and having that innovation but really building cloud native and now hybrid full cloud operations, day two operations. However you want to look at it. That's a big thing. What architecturally has changed that's been innovative from those original building blocks? >> Well, I think that the basic architecture has proven to be very, very resilient. When I wrote about the 15 year birthday of Amazon S3 a couple of weeks ago one thing that I thought was really incredible was the fact that the same APIs that you could have used 15 years ago they all still work. The put, the get, the list, the delete, the permissions management, every last one of those were chosen with extreme care. And so they all still work. So one of the things you think about when you put APIs out there is in Amazon terms we always talk about going through a one-way door and a one way door says, once you do it you're committed for the indefinite future. And so you we're very happy to do that but we take those steps with extreme care. And so those basic building blocks so the original S3 APIs, the original EC2 APIs and the model, all those things really worked. But now they're running at this just insane scale. One thing that blows me away I routinely hear my colleagues talking about petabytes and exabytes, and we throw around trillions and quadrillions like they're pennies. It's kind of amazing. Sometimes when you hear the scale of requests per day or request per month, and the orders of magnitude are you can't map them back to reality anymore. They're simply like literally astronomical. >> If I can just jump in real quick Dave before you ask Jeff, I was watching the Jeff Bezos interview in 1999 that's been going around on LinkedIn in a 60 minutes interview. The interviewer says you are reporting that you can store a gigabyte of customer data from all their purchases. What are you going to do with that? He basically nailed the answer. This is in 99. We're going to use that data to create, that was only a gig. >> Well one of the things that is interesting to me guys, is if you look at again, the early days of cloud, of course I always talked about that in small companies like ours John could have now access to information technology that only big companies could get access to. And now you've seen we just going to talk about it today. All these startups rise up and reach viability. But at the same time, Jeff you've seen big companies get the aha moment on cloud and competition drives urgency and that drives innovation. And so now you see everybody is doing cloud, it's a mandate. And so the expectation is a lot more innovation, experimentation and speed from all ends. It's really exciting to see. >> I know this sounds hackneyed and overused but it really, really still feels just like day one. We're 15 plus years into this. I still wake up every morning, like, wow what is the coolest thing that I'm going to get to learn about and write about today? We have the most amazing customers, one of the things that is great when you're so well connected to your customers, they keep telling you about their dreams, their aspirations, their use cases. And we can just take that and say we can actually build awesome things to help you address those use cases from the ground on up, from building custom hardware things like the nitro system, the graviton to the machine learning inferencing and training chips where we have such insight into customer use cases because we have these awesome customers that we can make these incredible pieces of hardware and software to really address those use cases. >> I'm glad you brought that up. This is another big change, right? You're getting the early days of cloud like, oh, Amazon they're just using off the shelf components. They're not buying these big refrigerator sized disc drives. And now you're developing all this custom Silicon and vertical integration in certain aspects of your business. And that's because workload is demanding. You've got to get more specialized in a lot of cases. >> Indeed they do. And if you watch Peter DeSantis' keynote at re-invent he talked about the fact that we're researching ways to make better cement that actually produces less carbon dioxide. So we're now literally at the from the ground on up level of construction. >> Jeff, I want to get a question from the crowd here. We got, (mumbles) who's a good friend of theCUBE cloud Arate from the beginning. He asked you, he wants to know if you'd like to share Amazon's edge aspirations. He says, he goes, I mean, roadmaps. I go, first of all, he's not going to talk about the roadmaps, but what can you share? I mean, obviously the edge is key. Outpost has been all in the news. You obviously at CloudOps is not a boundary. It's a distributed network. What's your response to-- >> Well, the funny thing is we don't generally have technology roadmaps inside the company. The roadmap is always listen really well to customers not just where they are, but the customers are just so great at saying, this is where we'd like to go. And when we hear edge, the customers don't generally come to us and say edge, they say we need as low latency as possible between where the action happens within our factory floors and our own offices and where we might be able to compute, analyze, store make decisions. And so that's resulted in things like outposts where we can put outposts in their own data center or their own field office, wavelength, where we're working with 5G telecom providers to put computing storage in the carrier hubs of the various 5G providers. Again, with reducing latency, we've been doing things like local zones, where we put zones in an increasing number of cities across the country with the goal of just reducing the average latency between the vast majority of customers and AWS resources. So instead of thinking edge, we really think in terms of how do we make sure that our customers can realize their dreams. >> Staying on the flywheel that AWS has built on ship stuff faster, make things faster, smaller, cheaper, great mission. I want to ask you about the working backwards document. I know it's been getting a lot of public awareness. I've been, that's all I've learned in interviewing Amazon folks. They always work backwards. I always mentioned the customer and all the interviews. So you've got a couple of customer references in there check the box there for you. But working backwards has become kind of a guiding principles, almost like a Harvard Business School case study approach to management. As you guys look at this working backwards and ex Amazonians have written books about it now so people can go look at, it's a really good methodology. Take us back to how you guys work back from the customers because here we're featuring 10 startups. So companies that are out there and Andy has been preaching this to customers. You should think about working backwards because it's so fast. These companies are going into this enterprise market your ecosystem of startups to provide value. What things are you seeing that customers need to think about to work backwards from their customer? How do you see that? 'Cause you've been on the community side, you see the tech side customers have to move fast and work backwards. What are the things that they need to focus on? What's your observation? >> So there's actually a brand new book called "Working Backwards," which I actually learned a lot about our own company from simply reading the book. And I think to me, a principal part of learning backward it's really about humility and being able to be a great listener. So you don't walk into a customer meeting ready to just broadcast the latest and greatest that we've been working on. You walk in and say, I'm here from AWS and I simply want to learn more about who you are, what you're doing. And most importantly, what do you want to do that we're not able to help you with right now? And then once we hear those kinds of things we don't simply write down kind of a bullet item of AWS needs to improve. It's this very active listening process. Tell me a little bit more about this challenge and if we solve it in this way or this way which one's a better fit for your needs. And then a typical AWS launch, we might talk to between 50 and 100 customers in depth to make sure that we have that detailed understanding of what they would like to do. We can't always meet all the needs of these customers but the idea is let's see what is the common base that we can address first. And then once we get that first iteration out there, let's keep listening, let's keep making it better and better and better as quickly. >> A lot of people might poopoo that John but I got to tell you, John, you will remember this the first time we ever met Andy Jassy face-to-face. I was in the room, you were on the speaker phone. We were building an app on AWS at the time. And he was asking you John, for feedback. And he was probing and he pulled out his notebook. He was writing down and he wasn't just superficial questions. He was like, well, why'd you do it that way? And he really wanted to dig. So this is cultural. >> Yeah. I mean, that's the classic Amazon. And that's the best thing about it is that you can go from zero startups zero stage startup to traction. And that was the premise of the cloud. Jeff, I want to get your thoughts and commentary on this love to get your opinion. You've seen this grow from the beginning. And I remember 'cause I've been playing with AWS since the beginning as well. And it says as an entrepreneur I remember my first EC2 instance that didn't even have custom domain support. It was the long URL. You seen the startups and now that we've been 15 years in, you see Dropbox was it just a startup back in the day. I remember these startups that when they were coming they were all born on Amazon, right? These big now unicorns, you were there when these guys were just developers and these gals. So what's it like, I mean, you see just the growth like here's a couple of people with them ideas rubbing nickels together, making magic happen who knows what's going to turn into, you've been there. What's it been like? >> It's been a really unique journey. And to me like the privilege of a lifetime, honestly I've like, you always want to be part of something amazing and you aspire to it and you study hard and you work hard and you always think, okay, somewhere in this universe something really cool is about to happen. And if you're really, really lucky and just a million great pieces of luck like lineup in series, sometimes it actually all works out and you get to be part of something like this when it does you don't always fully appreciate just how awesome it is from the inside, because you're just there just like feeding the machine and you are just doing your job just as fast as you possibly can. And in my case, it was listening to teams and writing blog posts about their launches and sharing them on social media, going out and speaking, you do it, you do it as quickly as possible. You're kind of running your whole life as you're doing that as well. And suddenly you just take a little step back and say, wow we did this kind of amazing thing, but we don't tend to like relax and say, okay, we've done it at Amazon. We get to a certain point. We recognize it. And five minutes later, we're like, okay, let's do the next amazingly good thing. But it's been this just unique privilege and something that I never thought I'd be fortunate enough to be a part of. >> Well, then the last few minutes we have Jeff I really appreciate you taking the time to spend with us for this inaugural launch of theCUBE on cloud startup showcase. We are showcasing 10 startups here from your ecosystem. And a lot of people who know AWS for the folks that don't you guys pride yourself on community and ecosystem the global startups program that Jeremy and his team are running. You guys nurture these startups. You want them to be successful. They're vectoring out into the marketplace with growth strategy, helping customers. What's your take on this ecosystem? As customers are out there listening to this what's your advice to them? How should they engage? Why is these sets of start-ups so important? >> Well, I totally love startups and I've spent time in several startups. I've spent other time consulting with them. And I think we're in this incredible time now wheres, it's so easy and straightforward to get those basic resources, to get your compute, to get your storage, to get your databases, to get your machine learning and to take that and to really focus on your customers and to build what you want. And we see this actual exponential growth. And we see these startups that find something to do. They listen to one of their customers, they build that solution. And they're just that feedback cycle gets started. It's really incredible. And I love to see the energy of these startups. I love to hear from them. And at any point if we've got an AWS powered startup and they build something awesome and want to share it with me, I'm all ears. I love to hear about them. Emails, Twitter mentions, whatever I'll just love to hear about all this energy all those great success with our startups. >> Jeff Barr, thank you for coming on. And congratulations, please pass on to Andy Jassy who's going to take over for Jeff Bezos and I saw the big news that he's picking a successor an Amazonian coming back into the fold, Adam. So congratulations on that. >> I will definitely pass on your congratulations to Andy and I worked with Adam in the past when AWS was just getting started and really looking forward to seeing him again, welcoming back and working with him. >> All right, Jeff Barr with AWS guys check out his Twitter and all the social coordinates. He is pumping out all the resources you need to know about if you're a developer or you're an enterprise looking to go to the next level, next generation, modern infrastructure. Thanks Jeff for coming on. Really appreciate it. Our next guests want to bring up stage Michael Liebow from McKinsey cube alumni, who is a great guest who is very timely in his McKinsey role with a paper he and his colleagues put out called cloud's trillion dollar prize up for grabs. Michael, thank you for coming up on stage with Dave and I. >> Hey, great to be here, John. Thank you. >> One of the things I loved about this and why I wanted you to come on was not only is the report awesome. And Dave has got a zillion questions, he want us to drill into. But in 2015, we wrote a story called Andy Jassy trillion dollar baby on Forbes, and then on medium and silken angle where we were the first ones to profile Andy Jassy and talk about this trillion dollar term. And Dave came up with the calculation and people thought we were crazy. What are you talking about trillion dollar opportunity. That was in 2015. You guys have put this together with a serious research report with methodology and you left a lot on the table. I noticed in the report you didn't even have a whole section quantified. So I think just scratching the surface trillion. I'd be a little light, Dave, so let's dig into it, Michael thanks for coming on. >> Well, and I got to say, Michael that John's a trillion dollar baby was revenue. Yours is EBITDA. So we're talking about seven to X, seven to eight X. What we were talking back then, but great job on the report. Fantastic work. >> Thank you. >> So tell us about the report gives a quick lowdown. I got some questions. You guys are unlocking the value drivers but give us a quick overview of this report that people can get for free. So everyone who's registered will get a copy but give us a quick rundown. >> Great. Well the question I think that has bothered all of us for a long time is what's the business value of cloud and how do you quantify it? How do you specify it? Because a lot of people talk around the infrastructure or technical value of cloud but that actually is a big problem because it just scratches the surface of the potential of what cloud can mean. And we focus around the fortune 500. So we had to box us in somewhat. And so focusing on the fortune 500 and fast forwarding to 2030, we put out this number that there's over a trillion dollars worth of value. And we did a lot of analysis using research from a variety of partners, using third-party research, primary research in order to come up with this view. So the business value is two X the technical value of cloud. And as you just pointed out, there is a whole unlock of additional value where organizations can pioneer on some of the newest technologies. And so AWS and others are creating platforms in order to do not just machine learning and analytics and IOT, but also for quantum or mixed reality for blockchain. And so organizations specific around the fortune 500 that aren't leveraging these capabilities today are going to get left behind. And that's the message we were trying to deliver that if you're not doing this and doing this with purpose and with great execution, that others, whether it's others in your industry or upstarts who were motioning into your industry, because as you say cloud democratizes compute, it provides these capabilities and small companies with talent. And that's what the skills can leverage these capabilities ahead of slow moving incumbents. And I think that was the critical component. So that gives you the framework. We can deep dive based on your questions. >> Well before we get into the deep dive, I want to ask you we have startups being showcased here as part of the, it will showcase, they're coming out of the ecosystem. They have a lot of certification from Amazon and they're secure, which is a big issue. Enterprises that you guys talk to McKinsey speaks directly to I call the boardroom CXOs, the top executives. Are they realizing that the scale and timing of this agility window? I mean, you want to go through these key areas that you would break out but as startups become more relevant the boardrooms that are making these big decisions realize that their businesses are up for grabs. Do they realize that all this wealth is shifting? And do they see the role of startups helping them? How did you guys come out of them and report on that piece? >> Well in terms of the whole notion, we came up with this framework which looked at the opportunity. We talked about it in terms of three dimensions, rejuvenate, innovate and pioneer. And so from the standpoint of a board they're more than focused on not just efficiency and cost reduction basically tied to nation, but innovation tied to analytics tied to machine learning, tied to IOT, tied to two key attributes of cloud speed and scale. And one of the things that we did in the paper was leverage case examples from across industry, across-region there's 17 different case examples. My three favorite is one is Moderna. So software for life couldn't have delivered the vaccine as fast as they did without cloud. My second example was Goldman Sachs got into consumer banking is the platform behind the Apple card couldn't have done it without leveraging cloud. And the third example, particularly in early days of the pandemic was Zoom that added five to 6,000 servers a night in order to scale to meet the demand. And so all three of those examples, plus the other 14 just indicate in business terms what the potential is and to convince boards and the C-suite that if you're not doing this, and we have some recommendations in terms of what CEOs should do in order to leverage this but to really take advantage of those capabilities. >> Michael, I think it's important to point out the approach at sometimes it gets a little wonky on the methodology but having done a lot of these types of studies and observed there's a lot of superficial studies out there, a lot of times people will do, they'll go I'll talk to a customer. What kind of ROI did you get? And boom, that's the value study. You took a different approach. You have benchmark data, you talked to a lot of companies. You obviously have a lot of financial data. You use some third-party data, you built models, you bounded it. And ultimately when you do these things you have to ascribe a value contribution to the cloud component because fortunate 500 companies are going to grow even if there were no cloud. And the way you did that is again, you talk to people you model things, and it's a very detailed study. And I think it's worth pointing out that this was not just hey what'd you get from going to cloud before and after. This was a very detailed deep dive with really a lot of good background work going into it. >> Yeah, we're very fortunate to have the McKinsey Global Institute which has done extensive studies in these areas. So there was a base of knowledge that we could leverage. In fact, we looked at over 700 use cases across 19 industries in order to unpack the value that cloud contributed to those use cases. And so getting down to that level of specificity really, I think helps build it from the bottom up and then using cloud measures or KPIs that indicate the value like how much faster you can deploy, how much faster you can develop. So these are things that help to kind of inform the overall model. >> Yeah. Again, having done hundreds, if not thousands of these types of things, when you start talking to people the patterns emerge, I want to ask you there's an exhibit tool in here, which is right on those use cases, retail, healthcare, high-tech oil and gas banking, and a lot of examples. And I went through them all and virtually every single one of them from a value contribution standpoint the unlocking value came down to data large data sets, document analysis, converting sentiment analysis, analytics. I mean, it really does come down to the data. And I wonder if you could comment on that and why is it that cloud is enabled that? >> Well, it goes back to scale. And I think the word that I would use would be data gravity because we're talking about massive amounts of data. So as you go through those kind of three dimensions in terms of rejuvenation one of the things you can do as you optimize and clarify and build better resiliency the thing that comes into play I think is to have clean data and data that's available in multiple places that you can create an underlying platform in order to leverage the services, the capabilities around, building out that structure. >> And then if I may, so you had this again I want to stress as EBITDA. It's not a revenue and it's the EBITDA potential as a result of leveraging cloud. And you listed a number of industries. And I wonder if you could comment on the patterns that you saw. I mean, it doesn't seem to be as simple as Negroponte bits versus Adam's in terms of your ability to unlock value. What are the patterns that you saw there and why are the ones that have so much potential why are they at the top of the list? >> Well, I mean, they're ranked based on impact. So the five greatest industries and again, aligned by the fortune 500. So it's interesting when you start to unpack it that way high-tech oil, gas, retail, healthcare, insurance and banking, right? Top. And so we did look at the different solutions that were in that, tried to decipher what was fully unlocked by cloud, what was accelerated by cloud and what was perhaps in this timeframe remaining on premise. And so we kind of step by step, expert by expert, use case by use case deciphered of the 700, how that applied. >> So how should practitioners within organizations business but how should they use this data? What would you recommend, in terms of how they think about it, how they apply it to their business, how they communicate? >> Well, I think clearly what came out was a set of best practices for what organizations that were leveraging cloud and getting the kind of business return, three things stood out, execution, experience and excellence. And so for under execution it's not just the transaction, you're not just buying cloud you're changing their operating model. And so if the organization isn't kind of retooling the model, the processes, the workflows in order to support creating the roles then they aren't going to be able, they aren't going to be successful. In terms of experience, that's all about hands-on. And so you have to dive in, you have to start you have to apply yourself, you have to gain that applied knowledge. And so if you're not gaining that experience, you're not going to move forward. And then in terms of excellence, and it was mentioned earlier by Jeff re-skilling, up-skilling, if you're not committed to your workforce and pushing certification, pushing training in order to really evolve your workforce or your ways of working you're not going to leverage cloud. So those three best practices really came up on top in terms of what a mature cloud adopter looks like. >> That's awesome. Michael, thank you for coming on. Really appreciate it. Last question I have for you as we wrap up this trillion dollar segment upon intended is the cloud mindset. You mentioned partnering and scaling up. The role of the enterprise and business is to partner with the technologists, not just the technologies but the companies talk about this cloud native mindset because it's not just lift and shift and run apps. And I have an IT optimization issue. It's about innovating next gen solutions and you're seeing it in public sector. You're seeing it in the commercial sector, all areas where the relationship with partners and companies and startups in particular, this is the startup showcase. These are startups are more relevant than ever as the tide is shifting to a new generation of companies. >> Yeah, so a lot of think about an engine. A lot of things have to work in order to produce the kind of results that we're talking about. Brad, you're more than fair share or unfair share of trillion dollars. And so CEOs need to lead this in bold fashion. Number one, they need to craft the moonshot or the Marshot. They have to set that goal, that aspiration. And it has to be a stretch goal for the organization because cloud is the only way to enable that achievement of that aspiration that's number one, number two, they really need a hardheaded economic case. It has to be defined in terms of what the expectation is going to be. So it's not loose. It's very, very well and defined. And in some respects time box what can we do here? I would say the cloud data, your organization has to move in an agile fashion training DevOps, and the fourth thing, and this is where the startups come in is the cloud platform. There has to be an underlying platform that supports those aspirations. It's an art, it's not just an architecture. It's a living, breathing live service with integrations, with standardization, with self service that enables this whole program. >> Awesome, Michael, thank you for coming on and sharing the McKinsey perspective. The report, the clouds trillion dollar prize is up for grabs. Everyone who's registered for this event will get a copy. We will appreciate it's also on the website. We'll make sure everyone gets a copy. Thanks for coming, I appreciate it. Thank you. >> Thanks, Michael. >> Okay, Dave, big discussion there. Trillion dollar baby. That's the cloud. That's Jassy. Now he's going to be the CEO of AWS. They have a new CEO they announced. So that's going to be good for Amazon's kind of got clarity on the succession to Jassy, trusted soldier. The ecosystem is big for Amazon. Unlike Microsoft, they have the different view, right? They have some apps, but they're cultivating as many startups and enterprises as possible in the cloud. And no better reason to change gears here and get a venture capitalist in here. And a friend of theCUBE, Jerry Chen let's bring them up on stage. Jerry Chen, great to see you partner at Greylock making all the big investments. Good to see you >> John hey, Dave it's great to be here with you guys. Happy marks.Can you see that? >> Hey Jerry, good to see you man >> So Jerry, our first inaugural AWS startup showcase we'll be doing these quarterly and we're going to be featuring the best of the best, you're investing in all the hot startups. We've been tracking your careers from the beginning. You're a good friend of theCUBE. Always got great commentary. Why are startups more important than ever before? Because in the old days we've talked about theCUBE before startups had to go through certain certifications and you've got tire kicking, you got to go through IT. It's like going through security at the airport, take your shoes off, put your belt on thing. I mean, all kinds of things now different. The world has changed. What's your take? >> I think startups have always been a great way for experimentation, right? It's either new technologies, new business models, new markets they can move faster, the experiment, and a lot of startups don't work, unfortunately, but a lot of them turned to be multi-billion dollar companies. I thing startup is more important because as we come out COVID and economy is recovery is a great way for individuals, engineers, for companies for different markets to try different things out. And I think startups are running multiple experiments at the same time across the globe trying to figure how to do things better, faster, cheaper. >> And McKinsey points out this use case of rejuvenate, which is essentially retool pivot essentially get your costs down or and the next innovation here where there's Tam there's trillion dollars on unlock value and where the bulk of it is is the innovation, the new use cases and existing new use cases. This is where the enterprises really have an opportunity. Could you share your thoughts as you invest in the startups to attack these new waves these new areas where it may not look the same as before, what's your assessment of this kind of innovation, these new use cases? >> I think we talked last time about kind of changing the COVID the past year and there's been acceleration of things like how we work, education, medicine all these things are going online. So I think that's very clear. The first wave of innovation is like, hey things we didn't think we could be possible, like working remotely, e-commerce everywhere, telemedicine, tele-education, that's happening. I think the second order of fact now is okay as enterprises realize that this is the new reality everything is digital, everything is in the cloud and everything's going to be more kind of electronic relation with the customers. I think that we're rethinking what does it mean to be a business? What does it mean to be a bank? What does it mean to be a car company or an energy company? What does it mean to be a retailer? Right? So I think the rethinking that brands are now global, brands are all online. And they now have relationships with the customers directly. So I think if you are a business now, you have to re experiment or rethink about your business model. If you thought you were a Nike selling shoes to the retailers, like half of Nike's revenue is now digital right all online. So instead of selling sneakers through stores they're now a direct to consumer brand. And so I think every business is going to rethink about what the AR. Airbnb is like are they in the travel business or the experience business, right? Airlines, what business are they in? >> Yeah, theCUBE we're direct to consumer virtual totally opened up our business model. Dave, the cloud premise is interesting now. I mean, let's reset this where we are, right? Andy Jassy always talks about the old guard, new guard. Okay we've been there done that, even though they still have a lot of Oracle inside AWS which we were joking the other day, but this new modern era coming out of COVID Jerry brings this up. These startups are going to be relevant take territory down in the enterprises as new things develop. What's your premise of the cloud and AWS prospect? >> Well, so Jerry, I want to to ask you. >> Jerry: Yeah. >> The other night, last Thursday, I think we were in Clubhouse. Ben Horowitz was on and Martine Casado was laying out this sort of premise about cloud startups saying basically at some point they're going to have to repatriate because of the Amazon VIG. I mean, I'm paraphrasing and I guess the premise was that there's this variable cost that grows as you scale but I kind of shook my head and I went back. You saw, I put it out on Twitter a clip that we had the a couple of years ago and I don't think, I certainly didn't see it that way. Maybe I'm getting it wrong but what's your take on that? I just don't see a snowflake ever saying, okay we're going to go build our own data center or we're going to repatriate 'cause they're going to end up like service now and have this high cost infrastructure. What do you think? >> Yeah, look, I think Martin is an old friend from VMware and he's brilliant. He has placed a lot of insights. There is some insights around, at some point a scale, use of startup can probably run things more cost-effectively in your own data center, right? But I think that's fewer companies more the vast majority, right? At some point, but number two, to your point, Dave going on premise versus your own data center are two different things. So on premise in a customer's environment versus your own data center are two different worlds. So at some point some scale, a lot of the large SaaS companies run their own data centers that makes sense, Facebook and Google they're at scale, they run their own data centers, going on premise or customer's environment like a fortune 100 bank or something like that. That's a different story. There are reasons to do that around compliance or data gravity, Dave, but Amazon's costs, I don't think is a legitimate reason. Like if price is an issue that could be solved much faster than architectural decisions or tech stacks, right? Once you're on the cloud I think the thesis, the conversation we had like a year ago was the way you build apps are very different in the cloud and the way built apps on premise, right? You have assume storage, networking and compute elasticity that's independent each other. You don't really get that in a customer's data center or their own environment even with all the new technologies. So you can't really go from cloud back to on-premise because the way you build your apps look very, very different. So I would say for sure at some scale run your own data center that's why the hyperscale guys do that. On-premise for customers, data gravity, compliance governance, great reasons to go on premise but for vast majority of startups and vast majority of customers, the network effects you get for being in the cloud, the network effects you get from having everything in this alas cloud service I think outweighs any of the costs. >> I couldn't agree more and that's where the data is, at the way I look at it is your technology spend is going to be some percentage of revenue and it's going to be generally flat over time and you're going to have to manage it whether it's in the cloud or it's on prem John. >> Yeah, we had a quote on theCUBE on the conscious that had Jerry I want to get your reaction to this. The executive said, if you don't have an AI strategy built into your value proposition you will be shorted as a stock on wall street. And I even went further. So you'll probably be delisted cause you won't be performing with a tongue in cheek comment. But the reality is that that's indicating that everyone has to have AI in their thing. Mainly as a reality, what's your take on that? I know you've got a lot of investments in this area as AI becomes beyond fashion and becomes table stakes. Where are we on that spectrum? And how does that impact business and society as that becomes a key part of the stack and application stack? >> Yeah, I think John you've seen AI machine learning turn out to be some kind of novelty thing that a bunch of CS professors working on years ago to a funnel piece of every application. So I would say the statement of the sentiment's directionally correct that 20 years ago if you didn't have a web strategy or a website as a company, your company be sure it, right? If you didn't have kind of a internet website, you weren't real company. Likewise, if you don't use AI now to power your applications or machine learning in some form or fashion for sure you'd be at a competitive disadvantage to everyone else. And just like if you're not using software intelligently or the cloud intelligently your stock as a company is going to underperform the rest of the market. And the cloud guys on the startups that we're backing are making AI so accessible and so easy for developers today that it's really easy to use some level of machine learning, any applications, if you're not doing that it's like not having a website in 1999. >> Yeah. So let's get into that whole operation side. So what would you be your advice to the enterprises that are watching and people who are making decisions on architecture and how they roll out their business model or value proposition? How should they look at AI and operations? I mean big theme is day two operations. You've got IT service management, all these things are being disrupted. What's the operational impact to this? What's your view on that? >> So I think two things, one thing that you and Dave both talked about operation is the key, I mean, operations is not just the guts of the business but the actual people running the business, right? And so we forget that one of the values are going to cloud, one of the values of giving these services is you not only have a different technology stack, all the bits, you have a different human stack meaning the people running your cloud, running your data center are now effectively outsource to Amazon, Google or Azure, right? Which I think a big part of the Amazon VIG as Dave said, is so eloquently on Twitter per se, right? You're really paying for those folks like carry pagers. Now take that to the next level. Operations is human beings, people intelligently trying to figure out how my business can run better, right? And that's either accelerate revenue or decrease costs, improve my margin. So if you want to use machine learning, I would say there's two areas to think about. One is how I think about customers, right? So we both talked about the amount of data being generated around enterprise individuals. So intelligently use machine learning how to serve my customers better, then number two AI and machine learning internally how to run my business better, right? Can I take cost out? Can I optimize supply chain? Can I use my warehouses more efficiently my logistics more efficiently? So one is how do I use AI learning to be a more familiar more customer oriented and number two, how can I take cost out be more efficient as a company, by writing AI internally from finance ops, et cetera. >> So, Jerry, I wonder if I could ask you a little different subject but a question on tactical valuations how coupled or decoupled are private company valuations from the public markets. You're seeing the public markets everybody's freaking out 'cause interest rates are going to go up. So the future value of cash flows are lower. Does that trickle in quickly into the private markets? Or is it a whole different dynamic? >> If I could weigh in poly for some private markets Dave I would have a different job than I do today. I think the reality is in the long run it doesn't matter as much as long as you're investing early. Now that's an easy answer say, boats have to fall away. Yes, interest rates will probably go up because they're hard to go lower, right? They're effectively almost zero to negative right now in most of the developed world, but at the end of the day, I'm not going to trade my Twilio shares or Salesforce shares for like a 1% yield bond, right? I'm going to hold the high growth tech stocks because regardless of what interest rates you're giving me 1%, 2%, 3%, I'm still going to beat that with a top tech performers, Snowflake, Twilio Hashi Corp, bunch of the private companies out there I think are elastic. They're going to have a great 10, 15 year run. And in the Greylock portfolio like the things we're investing in, I'm super bullish on from Roxanne to Kronos fear, to true era in the AI space. I think in the long run, next 10 years these things will outperform the market that said, right valuation prices have gone up and down and they will in our careers, they have. In the careers we've been covering tech. So I do believe that they're high now they'll come down for sure. Will they go back up again? Definitely, right? But as long as you're betting these macro waves I think we're all be good. >> Great answer as usual. Would you trade them for NFTs Jerry? >> That $69 million people piece of artwork look, I mean, I'm a longterm believer in kind of IP and property rights in the blockchain, right? And I'm waiting for theCUBE to mint this video as the NFT, when we do this guys, we'll mint this video's NFT and see how much people pay for the original Dave, John, Jerry (mumbles). >> Hey, you know what? We can probably get some good bang for that. Hey it's all about this next Jerry. Jerry, great to have you on, final question as we got this one minute left what's your advice to the people out there that either engaging with these innovative startups, we're going to feature startups every quarter from the in the Amazon ecosystem, they are going to be adding value. What's the advice to the enterprises that are engaging startups, the approach, posture, what's your advice. >> Yeah, when I talk to CIOs and large enterprises, they often are wary like, hey, when do I engage a startup? How, what businesses, and is it risky or low risk? Now I say, just like any career managing, just like any investment you're making in a big, small company you should have a budget or set of projects. And then I want to say to a CIO, Hey, every priority on your wish list, go use the startup, right? I mean, that would be 10 for 10 projects, 10 startups. Probably too much risk for a lot of tech companies. But we would say to most CIOs and executives, look, there are strategic initiatives in your business that you want to accelerate. And I would take the time to invest in one or two startups each quarter selectively, right? Use the time, focus on fewer startups, go deep with them because we can actually be game changers in terms of inflecting your business. And what I mean by that is don't pick too many startups because you can't devote the time, but don't pick zero startups because you're going to be left behind, right? It'd be shorted as a stock by the John, Dave and Jerry hedge fund apparently but pick a handful of startups in your strategic areas, in your top tier three things. These really, these could be accelerators for your career. >> I have to ask you real quick while you're here. We've got a couple minutes left on startups that are building apps. I've seen DevOps and the infrastructure as code movement has gone full mainstream. That's really what we're living right now. That kind of first-generation commercialization of DevOps. Now DevSecOps, what are the trends that you've seen that's different from say a couple of years ago now that we're in COVID around how apps are being built? Is it security? Is it the data integration? What can you share as a key app stack impact (mumbles)? >> Yeah, I think there're two things one is security is always been a top priority. I think that was the only going forward period, right? Security for sure. That's why you said that DevOps, DevSecOps like security is often overlooked but I think increasingly could be more important. The second thing is I think we talked about Dave mentioned earlier just the data around customers, the data on premise or the cloud, and there's a ton of data out there. We keep saying this over and over again like data's new oil, et cetera. It's evolving and not changing because the way we're using data finding data is changing in terms of sources of data we're using and discovering and also speed of data, right? In terms of going from Basser real-time is changing. The speed of business has changed to go faster. So I think these are all things that we're thinking about. So both security and how you use your data faster and better. >> Yeah you were in theCUBE a number of years ago and I remember either John or I asked you about you think Amazon is going to go up the stack and start developing applications and your answer was you know what I think no, I think they're going to enable a new set of disruptors to come in and disrupt the SaaS world. And I think that's largely playing out. And one of the interesting things about Adam Selipsky appointment to the CEO, he comes from Tableau. He really helped Tableau go from that sort of old guard model to an ARR model obviously executed a great exit to Salesforce. And now I see companies like Salesforce and service now and Workday is potential for your scenario to really play out. They've got in my view anyway, outdated pricing models. You look at what's how Snowflake's pricing and the consumption basis, same with Datadog same with Stripe and new startups seem to really be a leading into the consumption-based pricing model. So how do you, what are your thoughts on that? And maybe thoughts on Adam and thoughts on SaaS disruption? >> I think my thesis still holds that. I don't think Selipsky Adam is going to go into the app space aggressively. I think Amazon wants to enable next generation apps and seeing some of the new service that they're doing is they're kind of deconstructing apps, right? They're deconstructing the parts of CRM or e-commerce and they're offering them as services. So I think you're going to see Amazon continue to say, hey we're the core parts of an app like payments or custom prediction or some machine learning things around applications you want to buy bacon, they're going to turn those things to the API and sell those services, right? So you look at things like Stripe, Twilio which are two of the biggest companies out there. They're not apps themselves, they're the components of the app, right? Either e-commerce or messaging communications. So I can see Amazon going down that path. I think Adam is a great choice, right? He was a longterm early AWS exact from the early days latent to your point Dave really helped take Tableau into kind of a cloud business acquired by Salesforce work there for a few years under Benioff the guy who created quote unquote cloud and now him coming home again and back to Amazon. So I think it'll be exciting to see how Adam runs the business. >> And John I think he's the perfect choice because he's got operations chops and he knows how to... He can help the startups disrupt. >> Yeah, and he's been a trusted soldier of Jassy from the beginning, he knows the DNA. He's got some CEO outside experience. I think that was the key he knows. And he's not going to give up Amazon speed, but this is baby, right? So he's got him in charge and he's a trusted lieutenant. >> You think. Yeah, you think he's going to hold the mic? >> Yeah. We got to go. Jerry Chen thank you very much for coming on. Really appreciate it. Great to see you. Thanks for coming on our inaugural cube on cloud AWS startup event. Now for the 10 startups, enjoy the sessions at 12:30 Pacific, we're going to have the closing keynote. I'm John Ferry for Dave Vellante and our special guests, thanks for watching and enjoy the rest of the day and the 10 startups. (upbeat music)

>> From around the globe, it's theCUBE with digital coverage of AWS re:Invent 2020. Special coverage sponsored by AWS Worldwide Public Sector. >> Hello, welcome back to theCUBES coverage, of AWS re:Invent 2020 virtual. This is theCUBE virtual, I'm John Furrier, your host. We're not there in person this year because of the pandemic, but we're doing the remote. This is special coverage of the public sector, we got two great guests, Manpreet Mattu, who was the Worldwide Public Sector of Startups and Venture Capital team with AWS, and Michael Jackson who's the leader, general manager of Public Health and Venture Capital and Startups. Gentlemen, thanks for joining me. Thanks for coming up. >> Okay, it's my pleasure, thanks for having. >> I loved love welcome to theCUBE. I just want to say that Amazon never forgets the startups, that's where are they were born and bred it's been a startup. It's always day one as the expression goes, but truly even with the success, not just in the enterprise and starts within public sector, it's still a startup agility mindset, just want to call that out and say congratulations. Okay, let's get into it. Tell us about your roles and your backgrounds and why you're here. >> So, I believe so, I'm the head of AWS Public Sector, VC and Startups team, and our mission really is to help our public sector customers, adopt innovation that is built by the startups. I've been with AWS for about two and a half years. And prior to that, I was in a similar role with Booz Allen, helping our public sector customers, adopt innovation data as well. >> Michael. >> Yeah, so I am the general manager of Public Health, for on the Venture Capital and Startups team. My career here at AWS began just over four years ago. I was brought on to the state and local government team, initially building the public health practice from inception, and I also built and led our U S elections business. And I'm really excited now to transition into this global role, to lead our public health VC and startups practice, and really democratize access to innovation for our startups in the healthcare space. >> Well, great journey. You guys are converging, the VC and startup teams are coming together. A lot of macro trends certainly are tailwinds for you guys. Obviously, the pandemic is forcing, more accelerated modern applications in public sector, and we've been covering more and more success stories, of the change happening quickly. As access to capital continues to be great, and agility with the cloud, how has that impacted your teams and your approach? Can you guys share how that's changed this year? Because there's more pressure now to be digital, there's more opportunities, there's more still capital flowing, how has it impacted your roles? >> Now, so at the very high level, Amazon invests in companies because, we want those companies to be successful. And AWS itself makes a substantial investment, in agility, the startup customers success. We have things like service credits and things like, business nurturing programs that we have built over the course of the last seven, eight years. For example, over the past, you had a loan, Amazon has provided more than a billion dollars in credits, through AWS Activate program, to help startups grow and scale their businesses. And not only that a total of more than three and a half billion dollars in credit to more than 140,000 startups, over the last seven years, all through the course of the Activate program. From more so, on the healthcare side, I would want, certainly MJ to also, speak through or speak to, the challenges that the health system has faced in the COVID times, and how AWS is helping the provider, healthcare providers and the startups, really achieve success, and help the patient populations on that note. >> Michael, weighing on this new programs, you guys are launching in the impact healthcare, I see where we're seeing the frontline workers, I mean, it's everyone seeing it on TV and the newspaper, and it's impacting friends and family, give us the update. >> Absolutely, so we're here today to launch a new program. We call it the Healthcare Acceleration program. And basically, there are two halves to the program, with an undercurrent or a recurring undercurrent, I should say. Just really quickly before I touch on that though, I'd be remissed if I didn't make note of the fact that, you're right capital is still flowing, and it's a really big deal particularly, as healthcare and public health becomes such a priority, but one of the strategic imperatives of our team's role, similar to the way we democratize access to innovation for startups, we also find it really important to democratize access, to resources for founders, underrepresented founders, so, that everyone can have a level playing field, and equal access to those resources and funding, and things of that nature. Getting back to some of the healthcare priorities, in particular, I don't have to tell you about, this pandemic where on the third, and possibly the deadliest wave losing over 1000 Americans per day. And so, not only are we interested in helping our customers, our enterprise customers inject innovation from startups so that they can address clinical aspects, of the pandemic and beyond, but there are underlying rippling societal implications as well. Things that have been exacerbated by the pandemic. Things like mental health, behavioral health, including substance use abuse, clinical clinician burnout, things like social determinants of health, which lead to disproportionately impacted demographics. So, there's a whole lot to unpack and I'm sure we will, but at the highest level, that's what we're looking to help, our enterprise customers address, with the help of our innovative high potential startups. >> I mean, strategic focus, just go a little bit further on how important this is, because, programs are needed, there is burnout, okay. >> Yeah. >> You have mental health, physical health, everything in between. What are you guys launching? What's new? What can people take away right now from AWS, and what startups and when, 'cause a lot of people are changing their focus. I was seeing people leave their jobs, to have to get on this new mission. They're seeing the pain, there's a lot of entrepreneurial energy, happening right now here. Go further, please. >> So, you touched right on it. So, there are two sides. I mentioned there are two halves, and an underlying current, right? So, the two halves are the supply and the demand. The supply side is what we refer to as the startups, vetted high potential, high growth startups, in the health tech space, that we can help to accelerate their go to market, right? We can pair them with mentorship, credits, we call it the 4Cs. There's capital, mapping them potentially to investors, who are interested into accelerating their growth. There's code, technical support, whether it's cloud formation templates, or technical expertise, connections such as other startups, incubators, accelerators, etcetera, and finally mapping them to customers. So, that's, what's in it for the startups. And then on the other side, the enterprise side, again, there are so many enterprises from payers to providers and others who are looking to accelerate their efforts, to digitally transform their enterprise. And so, by partnering with AWS, and the Healthcare Acceleration program, they can trust that there are AWS powered startups, that are vetted and prepared, to inject that sense of urgency, that sense of innovation. And the underlying current, the dots that are being connected is, workforce modernization or economic development, because in many cases, you're right, people are losing their jobs, people are looking at ways that they can, modernize the workforce is locally leverage local talent. And so, entrepreneurship is a great way, to stimulate the local economy, and help older workers or workers who are looking to transition into a more relevant occupations, to do just that. So, this is an all encompassing program. >> Let's get into this health accelerator from AWS. This is something that is on the table, AWS Health Accelerator, who are the stakeholders, and what are the benefits of this program? >> Well, I mean, before we actually, go to the accelerator for me, I think there's this focus on the healthcare, as an industry, as a vertical, is very important to talk about. The industry is experiencing transformation. It is experiencing disruption and the COVID-19 pandemic, has only accelerated that. If you made, it has sort of magnified some of the stressors, which were already there in the system. If you combine that with the sort of the undercurrent that MJ mentioned from a technological perspective, the delivery of healthcare globally is going digital. So, you see technology is like artificial intelligence, machine learning, big data, augmented reality, IoT based variables. All of these technologies are coming together, to enable applications, such as remote diagnostics, patient monitoring, predictive prescriptive healthcare. And we truly feel that this presents a tremendous opportunity to improve the patient experience, and more importantly, the patient outcomes, using these technologies, and these newly enabled applications through those technologies. And as an example, in the U S alone, there are 22 key healthcare AI use cases, that are projected to grow by, or to approximately around $22 billion by 2025. So, in AWS, we are collaborating with the wide spectrum of healthcare providers, with public health organizations, with government agencies, all around the globe to support their effort, to cope with the rippling effects of the COVID-19. And arguably, many of them are visible to us today, but I would argue that many many are not even yet, have been begun to understand by us and by our customers. So, that is the reason why we want to put some emphasis, on healthcare from a public sector standpoint. >> Yeah, that's a great call-out Manpreet, I want to just highlight that, maybe get an additional commentary because, the old days it was just the institution, the hospital and then you're done. And then it was okay, hospital plus the caregiver, the doctors, and the workers, and now the patient. So, holistically, you're calling out the big picture, the patient care, right. Their families, their environment, the caregivers, and the institution, and now the supply chain, all of it integrated together. That's where the action is. And that's where the data comes in, that's where cloud scale can come in. Is that right? Am I getting that right there? >> Yeah, that's absolutely. I'm sorry Manpreet. >> Welcome MJ, go on. >> I was going to say you're absolutely right. In fact, we like to look at it almost like a bullseye, right? So, at the center of the bullseye, like you said, usually, the first stakeholder that comes to mind, is the provider or the coordinator of care. Outside of there, you have the payer, outside of there, you have researchers. And in any even further outside still are your regulators, your healthcare agencies at the local state, and federal levels, including military health. So, it's a rippling effect of customers on that side, as well as you asked about stakeholders on the startup side, there's also a bullseye of influence. Starting with the founder herself, the founder, and her executive team, moving out from there to the startup, as an organization outside from there, we've got incubators and accelerators that are in place, to help accelerate that growth as well. And then farther out you've got investors, VCs, and investors, and so on both sides, supply and demand we're looking to tap into, and accelerate the growth, and make connections between the two. >> Yeah, (indistinct) but when I, in back in real life, when we used to go to games, you walk into the stadium, you buy your ticket with your phone, you go to your seat, concessions guys, deliver things there for you, the fan experience, the players are there. I mean, why can't we have that in healthcare? I was just everything is happening, right. Go for good, yeah. And I think that's the Nirvana, hopefully soon. >> We're working on it. >> Good stuff. I know, I just love the vision, I think is so relevant and super important. Now, let's get into this health accelerator. What's this all about? Let's get into that. >> So, the health accelerator will be, a multi-week on-demand program. Where we're going to map high potential vetted startups, to a number of resources, right. I mentioned before that there will be mentorship, there will be technical experts who will be able to, take these startups who have established some presence, but we want to accelerate their ability to go deeper specifically into public health, throughout that ecosystem that I just described, right? Starting with providers and coordinators, payers, researchers, regulators. We want to give them a way to go deep into this, heavily regulated industry, so that they can not only have access to the innovation that many startups would not otherwise, like Manpreet mentioned machine learning AI, but they also have access to the resources, to ensure their success. >> What kind of problems are you guys trying to solve with this? I mean, is there a specific vetting process, is there a criteria? Is there a bar to all over share some specifics? >> Yeah, absolutely. So, for the past few years, a lot of the major change challenges, for our public health customers have been the same, but they require a new approach. And I like to call our approach the HIGH FIVE. So, some of those challenges that have been traditionally, lingering for the past few years, equal social determinants of health. Social determinants, when we talk about that, we not only refer to the nonclinical contributors to a person's overall wellness. So, you think about issues like food deserts or recidivism homelessness, all of that transportation to access to care, right, all of that contributes. But then there's also disparities and health outcomes. When you think about socioeconomic differences, rural health, ethnic and racial minorities, so, that all factors into social determinants of health. Then there's also aging. Now, these are the strategic pillars that we like to focus on, or that we are focusing on. When I mentioned aging every day in the U S, 10,000 people celebrate their 65th birthday. Many of those individuals are suffering from comorbidities, from hypertension, diabetes, cancer, and now the lingering impact of COVID-19. And so, as these aging individuals continue to live longer, the goal is to improve the quality of their life as well. And so, many of them look to technology to age independently at home, etcetera. So, that's our second strategic pillar. The third, is mental and behavioral health. So, when I talk about mental health, I mean, everything from mild depression, all the way through suicide prevention, and especially these days with COVID-19, we see a lot of clinicians suffering from burnout. And so, it's important, that we take care of the frontline workers, those healthcare providers, and even outside of COVID-19, you think about the ways that the patient population, has continued to expand, and the growth within the provider market has not, or the pool of providers has not nearly expanded at the same rate. We've got people living longer, we've got more people than ever insured. And so, we need to leverage technology to help a stagnant, number of providers to treat a growing pool of patients, without sacrificing the quality of care. And then finally, we've got environmental health. From air quality to water purity. It's important to understand the correlation between, the environment and the health care of our population. So, those are the pillars. I know I mentioned the HIGH FIVE, the fifth is not specific to healthcare. I touched on it a little bit earlier, but the fifth is, it is democratizing access to innovation, to resources, specifically for founders from underrepresented communities. >> And that's great insight, Michael great, great Schaeffer pointed that out. Manpreet take us on the final word here. Venture Capital, Startups, AWS, what's the current state share with us, the current worldview from your perspective. >> Oh, so, bringing home this point that MJ mentioned, the strategic plan of focus areas. And if you, look at all those strategic areas there's, you can really sort of put those into two buckets. One is the patient side of the bucket, and then there's the provider side of the bucket, or the caretaker side of the bucket. And if the patient side, what we want to do is work with startups that are, really working across a broad spectrum of use cases, but to solve those two key challenges of the, one on the patient's side and other on the provider side. Then the end goal of providing patient experience, and patient outcomes. For the patient side, it's the patient experience, patient engagement, patient outcomes. So, the startups looking on those sides, on those use cases of criteria. And then we have the provider side where, we want to ensure that the providers have the right set of technologies, the right set of solutions, right set of innovation, to help them where healthcare operations. You have all seen in COVID times, how the provider systems are getting overwhelmed. And that's where the healthcare operations comes into play. Clinical decision support. Now, many patients cannot get to the hospitals. So, how do we provide through our startup partners for startup customers, those solutions where remote diagnostics, remote imaging or remote health delivery could be provided. Things like predictive and prescriptive health solutions. How can we work with our startups to provide, those sort of solutions to the providers, to again, at the end, the better the outcome of the patients, right? So, that's what we were looking at. And that's what this program is all about. Working with public sector provider side of the house and the customers understanding, and helping them understand the need as well, and then bringing the right set of startup solutions, and help solve those challenges that they are facing, and the patients are facing as well. MJ, I'm sure you want to close it out, with some thoughts too. >> Okay. >> Absolutely, I would just close it with this, our goal, like Manpreet said, is to match the high potential startups, with the, the enterprises who are desiring those solutions, and success for us, we'll have three traits. It will be valuable, meaning that there will be a true alignment between what our startups offer and what the market needs. It will be measurable, so that we can quantify the improvement and outcomes. And finally, it will be sustainable. So, beyond COVID-19 beyond the opioid crisis, beyond any situation or condition, we look to bring solutions to market through our startups, that are going to truly sustain a transformative approach to modernizing public health enterprises. >> Great job again, and important work and DevOps, impacting healthcare in all kinds of ways. And it's super important work. I'm glad you guys are doing it, and it's going to develop out beautifully, and if I can give you a high five, Michael, I'll give you a high five off in-person, but remotely, >> Virtual. >> Get virtual high five great program. We're going to spread the word, good work. >> Thank you. >> Thanks for doing it, I appreciate it. >> Thank you very much for your time. >> Okay, it's theCUBE coverage virtual, we are theCUBE virtual bringing all the coverage, super important work being done in public sector, cloud enabling it, great people important, and of course, happening at re:Invent. Thanks for watching. (upbeat music)