>>Hey, welcome back everyone to cube Cod's coverage and cloud native con the I'm John for your husband, David Nicholson cube analyst, cloud analyst. Co-host you got two great guests, KIPP alumni, Jerry Chen needs no introduction partner at Greylock ventures have been on the case many times, almost like an analyst chair. It's great to see you. I got guest analyst and Martin mal who's the CEO co-founder of Chronosphere just closed a whopping $200 million series C round businesses. Booming. Great to see you. Thanks for coming on. Thank you. Hey, first of all, congratulations on the business translations, who would have known that observability and distributed tracing would be a big deal. Jerry, you predicted that in 2013, >>I think we predicted jointly cloud was going to be a big deal with 2013, right? And I think the rise of cloud creates all these markets behind it, right. This, you know, I always say you got to ride a wave bigger than you. And, uh, and so this ride on cloud and scale is the macro wave and, you know, Marty and Robin cryosphere, they're just drafted behind that wave, bigger scale, high cardinality, more data, more apps. I mean, that's, that's where the fuck. >>Yeah. Martin, all kidding aside. You know, we joke about this because we've had conversations where the philosophy of you pick the trend is your friend that you know, is going to be happening. So you can kind of see the big waves coming, but you got to stay true to it. And one of the things that we talk about is what's the next Amazon impact gonna look like? And we were watching the rise of Amazon. You go, if this continues a new way to do things is going to be upon us. Okay, you've got dev ops now, cloud native, but observability became really a key part of that. It's like almost the, I call it the network management in the cloud. It's like in a new way, you guys have been very successful. There's a lot of solutions out there. What's different. >>Yeah. I'd say for Kearney sphere, there's really three big differences. The first thing is that we're a platform. So we're still an observability platform. And by that, I mean, we solved the problem end to end. If thinking about observability and monitoring, you want to know when something's wrong, you want to be able to see how bad it is. And then you want to able to figure out what the root cause is. Often. There are solutions that do a part of that, that that problem might solve a part of the problem really well for a platform that does the whole thing. And 10 that's that's really the first thing. Second thing is we're really built for not just the cloud, but cloud native environments. So a microservices architecture on container-based infrastructure. And that is something that, uh, we, we have saw coming maybe 20 17, 20 18, but luckily for us, we were already solving this problem at Uber. That's where myself, my co-founder were back in 20 14, 20 15. So we already had the sort of perfect technology to solve this problem ahead of where the, the trend was going in the industry and therefore a purpose-built solution for this type of environment, a lot more effective than a lot of the existing. >>It's interesting, Jerry, you know, the view investing companies that have their problem, that they have to solve themselves as the new thing, versus someone says, Hey, there's a market. Let's build a solution for something. I don't really know. Well, that's kind of what's going on here. Right? It's >>That's why we love founders. Like Martin Marna, rod that come out with these hyperscale comes Uber's like we say, they've seen the future. You know, like there were Uber, they looked at the existing solutions out there trying to scale Promethease or you know, data dogs and the vendors. And it didn't work. It fell over, was too expensive. And so Martin Rob saw solid future. Like, this is where the world's going. We're going to solve it. They built MP3. It became cryosphere. And um, so I don't take any credit for that. You know, I just look fine folks that can see the future. >>Yeah. But they were solving their problem. No one else had anything. There's no general purpose software that managed servers you could buy, you guys were cutting your teeth into solving the pain. You had Uber. When did you guys figure out like, oh, well this is pretty big. >>Uh, probably about 20 17, 20 18 with a rise in popularity of Kubernetes. That's when we knew, oh wait, the whole world is shifting to this. It's not, no one could really it to just goober and the big tech giants of the world. And that's when we really knew, okay. The whole, the whole whole world is shifting here. And again, it's, it's sheer blind luck that we already had the ideal solution for this particular environment. It wasn't planned it. Wasn't what we were planning for back then. But, um, yeah. Get everything. >>It makes a lot of difference. When you walk into a customer and say, we had this problem, I can empathize with you. Not just say we've got solved. Exactly. Jerry, how do they compete in the cloud? We always talk about how Amazon and Azure want to eat up anything that they see that might, you know, something on AWS. Um, this castle in the cloud opportunity here. Okay. >>In the cloud. I mean, you know, we talked last time about how to fight the big three, uh, Amazon Azure and, uh, and Google. And I think for sure they have basic offerings, right. You know, Google Stackdriver years ago, they've done basically for Pete's offerings, basic modern offerings. I think you have like basic, simple needs. It's a great way to get started, but customers don't want kind of a piecemeal solution all the time. They want a full product. Like Datadog shows a better user experience, but full product is going to, you know, the better mousetrap the world will beat a path to your door. So first you can build a better product versus these point solutions. Number two is at some scale and some level complexity, those guys can handle like the demanding users that current affairs handling right now, right? The door dash, the world. >>And finally don't want the Fox guarding the hen house. You know, you don't want to say like Amazon monitoring, you can't depend on Amazon service monitoring your Amazon apps or Google service monitor your Google apps, having something that is independent and multi-cloud, that can dual things, Marta said, you know, see a triage, fixed your issues is kind of what you want. And, um, that's where the market's skilling. So I do believe that cloud guys will have an offering the space, but in our castle and cloud research, we saw that, yeah, there's a plenty of startups being funded. There's plenty of opportunity. And that the scoreboard between Splunk Datadog and all these other companies, that there's a huge amount of market and value to be created in this piece. So, >>So with, at, at the time, when you, you know, uh, uh, necessity is the mother of invention, you're an Uber, you have a practical problem to solve and use you look around you and you see that you're not the only entity out there that has this problem. Where are we in that wave? So not everyone is at, cloud-scale not everyone has adopted completely Kubernetes and cloud native for everything. Are we just at the beginning of this wave? How far from the >>Beach are we, we think we're just at the beginning of this wave right now. Um, and if you think about most enterprises today, they're still using on, and they're not even in perhaps in the cloud at all right. Are you still using perhaps APM and solutions, uh, on premise? So, um, if you look at that wave, we're just at the beginning of it. But when, but when we talked to a lot of these companies and you ask them for their three year vision, Kubernetes is a huge piece of that because everyone wants to be multi-cloud everyone to be hybrid eventually. And that's going to be the enabler of that. So, uh, we're just in the beginning now, but it seems like an inevitable wave that is coming. >>So obviously people evaluated that exactly the way you're evaluating that. Right. Thus the funding, right. Because no one makes that kind of investment without thinking that there is a multiplier on that over time. So that's pretty, that's a pretty exciting place. >>Yeah. I think to your point, a lot of companies are running into that situation right now, and they're looking at existing solutions there for us. It was necessity because there wasn't anything out there now that there is a lot of companies are not using their sort of precious engineering resources to build their own there. They would prefer to buy a solution because this is something that we can offer to all the companies. And it's not necessarily a business differentiating technology for the businesses themselves >>Distributed tracing in that really platform. That's the news. Um, and you mentioned you've got this, a good bid. You do some good business. Is scale the big differentiator for you guys? Or is it the functionality? Because it sounds like with clients like door dash, and it looks a lot like Uber, they're doing a lot of stuff too, and I'm sure everyone needs the card. Other people doing the same kind of thing, that scale, massive amount of consumer data coming in on the edge. Yeah. Is that the differentiation or do you work for the old one, you know, main street enterprise, right. >>Um, that is a good part of the differentiation and for our product thus far before we had a distributor tracing for monitoring and metric data, that was the main differentiation is the sheer volume of data that gets produced so much higher, really excited about distributor tracing because that's actually not just a scale problem. It's, it's a space that everybody can see the potential distributor tracing yet. No one has really realized that potential. So our offering right now is fairly unique. It does things that no other vendors out there can do. And we're really excited about that because we think that that fundamentally solves the problem differently, not just at a larger scale, >>Because you're an expert, what is distributed tracing. >>Yeah. Uh, it's, it's, it's a great question. So really, if you look at this retracing, it captures the details of a particular request. So a particular customer interaction with your business and it captures how that request flows through your complex architecture, right? So you have every detail of that at every step of the way. And you can imagine this data is extremely rich and extremely useful to figure out what the underlying root causes of issues are. The problem with that is it's very bit boast. It's a lot of data gets produced. A ton of data gets produced, every interaction, every request. So one of the main issues are in this space is that people can't afford cost effectively to store all of this data. Right? So one of the main differentiators for our product is we made it cost efficient enough to store everything. And when you have all the data, you have far better analytics and you have >>Machine learning is better. Everything's better with data. That's right. Yeah. Great. What's the blind spot out. Different customers, as cybersecurity is always looking for corners and threats that some people say it's not what you want. It's what you don't see that kills you. That's, that's a tracing issue. That's a data problem. How do you see that evolving in your customer base clients, trying to get a handle of the visibility into the data? >>Yeah. Um, I think right now, again, it's, it's very early in this space of people are just getting started here and you're completely correct where, you know, you need that visibility. And again, this is why it's such a differentiator to have all the data. If you can imagine with only 10% of the data or 1% of data, how can you actually detect any of these particular issues? Right. So, uh, uh, data is key to solving that >>Feel great to have you guys on expert and congratulations on the funding, Jerry. Good to see you take a minute to give a plug for the company. What do you guys do? And actually close around the funding, told you a million dollars. Congratulations. What are you looking for for hiring? What are your milestones? What's on your plan plan. >>Yeah. Uh, so with the spanning, it's really to, to, uh, continue to grow the company, right? So we're sort of hiring, as I told you earlier, we are, uh, we grew our revenue this year by, by 10 X in the sense of the 10 months of this year, thus far. So our team hasn't really grown 10 X. So, so we, we need to keep up with that grid. So hiring across the board on engineering side, on the go to market side, and I just continue to >>Beat that. The headquarters, your virtual, if you don't mind, we've gone >>Completely distributed. Now we're mostly in the U S have a bunch of folks in Seattle and in New York, however, we going completely remote. So hiring anyone in the U S anywhere in Europe, uh, >>Oh, I got you here. What's your investment thesis. Now you got castles in the cloud, by the way, if you haven't seen the research from Greylock, Jerry and the team called castles in the cloud, you can Google it. What's your thesis now? What are you investing in? >>Yeah, it is. It is hard to always predict the next wave. I mean, my job is to find the right founders, but I'd say the three core areas are still the same one is this cloud disruption to Martin's point we're. So early days, the wave, I say, number two, uh, there's vertical apps, different SAS applications be finance, healthcare construction, all are changing. I think healthcare, especially the past couple of years through COVID, we've seen that's a market that needs to be digitized. And finally, FinTech, we talked about this before everything becomes a payments company, right? And that's why Stripe is such a huge juggernaut. You know, I don't think the world's all Stripe, but be it insurance payments, um, you know, stuff in crypto, whatever. I think fintechs still has a lot of, a lot of market to grow. >>It's making things easier. It's a good formula right now. If you can reduce complexity, it makes things easy in every market. You're going to seems to be the formula. >>And like the next great thing is making today's crappy thing better. Right? So the next, the next brace shows making this cube crappy thing. Yeah, >>We're getting better every day on our 11th season or year, I'm calling things seasons now, episodes and season for streaming, >>All the seasons drop a Netflix binge, watch them all the >>Cube plus and NFTs for our early videos. There'll be worth something because they're not that good, Jerry. How, of course you're great. Thank you. Thanks guys. Thanks for coming on it. Cubes coverage here in a physical event, 2021 cloud being the con CubeCon I'm John farrier and Dave Nicholson. Thanks for watching.

>>from around the globe. It's the Cube with digital coverage of AWS reinvent 2020 sponsored by Intel, AWS and our community partners. >>Hey, welcome back already, Jeffrey here with the Cube coming to you from Palo Alto studios today for our ongoing coverage of aws reinvent 2020. It's a digital event like everything else in 2020. We're excited for our next segment, so let's jump into it. We're joined in our next segment by Andrew Rafa. He is the principal and zero trust offering lead at the Light and Touche LLP. Andrew, great to see you. >>Thanks for having me. >>Absolutely. And joining him is Robbie Deval. He is the AWS cyber risk lead for Deloitte and Touche LLP. Robbie, Good to see you as well. >>Hey, Jeff, good to see you as well. >>Absolutely. So let's jump into it. You guys are all about zero trust and I know a little bit about zero trust I've been going to are safe for a number of years and I think one of the people that you like to quote analysts chase Cunningham from Forrester, who's been doing a lot of work around zero trust. But for folks that aren't really familiar with it. Andrew, why don't you give us kind of the 101? About zero trust. What is it? What's it all about? And why is it important? >>Sure thing. So is your trust is, um, it's a conceptual framework that helps organizations deal with kind of the ubiquitous nature of modern enterprise environments. Um, and then its course. Your trust commits to a risk based approach to enforcing the concept of least privileged across five key pillars those being users, workloads, data networks and devices. And the reason we're seeing is your trust really come to the forefront is because modern enterprise environments have shifted dramatically right. There is no longer a defined, clearly defined perimeter where everything on the outside is inherently considered, considered untrusted, and everything on the inside could be considered inherently trusted. There's a couple what I call macro level drivers that are, you know, changing the need for organizations to think about securing their enterprises in a more modern way. Um, the first macro level driver is really the evolving business models. So as organizations are pushing to the cloud, um, maybe expanding into into what they were considered high risk geography is dealing with M and A transactions and and further relying on 3rd and 4th parties to maintain some of their critical business operations. Um, the data and the assets by which the organization, um transact are no longer within the walls of the data center. Right? So, again, the perimeter is very much dissolved. The second, you know, macro level driver is really the shifting and evolving workforce. Um, especially given the pandemic and the need for organizations to support almost an entirely remote workforce nowadays, um, organizations, they're trying to think about how they revamp their traditional VPN technologies in order to provide connectivity to their employees into other third parties that need to get access to, uh, the enterprise. So how do we do so in a secure, scalable and reliable way and then the last kind of macro level driver is really the complexity of the I t landscape. So, you know, in legacy environment organizations on Lee had to support managed devices, and today you're seeing the proliferation of unmanaged devices, whether it be you know, B y o d devices, um, Internet of things, devices or other smart connected devices. So organizations are now, you know, have the need to provide connectivity to some of these other types of devices. But how do you do so in a way that, you know limits the risk of the expanding threat surface that you might be exposing your organization to by supporting from these connected devices? So those are some three kind of macro level drivers that are really, you know, constituting the need to think about security in a different >>way. Right? Well, I love I downloaded. You guys have, ah zero trust point of view document that that I downloaded. And I like the way that you you put real specificity around those five pillars again users, workloads, data networks and devices. And as you said, you have to take this kind of approach that it's kind of on a need to know basis. The less, you know, at kind of the minimum they need to know. But then, to do that across all of those five pillars, how hard is that to put in place? I mean, there's a There's a lot of pieces of this puzzle. Um, and I'm sure you know, we talk all the time about baking security and throughout the entire stack. How hard is it to go into a large enterprise and get them started or get them down the road on this zero trust journey? >>Yeah. So you mentioned the five pillars. And one thing that we do in our framework because we put data at the center of our framework and we do that on purpose because at the end of the day, you know, data is the center of all things. It's important for an organization to understand. You know what data it has, what the criticality of that data is, how that data should be classified and the governance around who and what should access it from a no users workloads, uh, networks and devices perspective. Um, I think one misconception is that if an organization wants to go down the path of zero trust, there's a misconception that they have to rip out and replace everything that they have today. Um, it's likely that most organizations are already doing something that fundamentally aligned to the concept of these privilege as it relates to zero trust. So it's important to kind of step back, you know, set a vision and strategy as faras What it is you're trying to protect, why you're trying to protect it. And what capability do you have in place today and take more of an incremental and iterative approach towards adoption, starting with some of your kind of lower risk use cases or lower risk parts of your environment and then implementing lessons learned along the way along the journey? Um, before enforcing, you know more of those robust controls around your critical assets or your crown jewels, if you >>will. Right? So, Robbie, I want to follow up with you, you know? And you just talked about a lot of the kind of macro trends that are driving this and clearly covert and work from anywhere is a big one. But one of the ones that you didn't mention that's coming right around the pike is five g and I o t. Right, so five g and and I o. T. We're going to see, you know, the scale and the volume and the mass of machine generated data, which is really what five g is all about, grow again exponentially. We've seen enough curves up into the right on the data growth, but we've barely scratched the surface and what's coming on? Five G and I o t. How does that work into your plans? And how should people be thinking about security around this kind of new paradigm? >>Yeah, I think that's a great question, Jeff. And as you said, you know, I UT continues to accelerate, especially with the recent investments and five G that you know pushing, pushing more and more industries and companies to adopt a coyote. Deloitte has been and, you know, helping our customers leverage a combination of these technologies cloud, Iot, TML and AI to solve their problems in the industry. For instance, uh, we've been helping restaurants automate their operations. Uh, we've helped automate some of the food safety audit processes they have, especially given the code situation that's been helping them a lot. We are currently working with companies to connect smart, wearable devices that that send the patient vital information back to the cloud. And once it's in the cloud, it goes through further processing upstream through applications and data. Let's etcetera. The way we've been implementing these solutions is largely leveraging a lot of the native services that AWS provides, like device manager that helps you onboard hundreds of devices and group them into different categories. Uh, we leveraged device Defender. That's a monitoring service for making sure that the devices are adhering to a particular security baseline. We also have implemented AWS green grass on the edge, where the device actually resides. Eso that it acts as a central gateway and a secure gateway so that all the devices are able to connect to this gateway and then ultimately connect to the cloud. One common problem we run into is ah, lot of the legacy i o t devices. They tend to communicate using insecure protocols and in clear text eso we actually had to leverage AWS lambda Function on the edge to convert these legacy protocols. Think of very secure and Q t t protocol that ultimately, you know, sense data encrypted to the cloud eso the key thing to recognize. And then the transformational shift here is, um, Cloud has the ability today to impact security off the device and the edge from the cloud using cloud native services, and that continues to grow. And that's one of the key reasons we're seeing accelerated growth and adoption of Iot devices on did you brought up a point about five G and and that's really interesting. And a recent set of investments that eight of us, for example, has been making. And they launched their AWS Waveland zones that allows you to deploy compute and storage infrastructure at the five G edge. So millions of devices they can connect securely to the computer infrastructure without ever having to leave the five g network Our go over the Internet insecurely talking to the cloud infrastructure. Uh, that allows us to actually enable our customers to process large volumes of data in a short, near real time. And also it increases the security of the architectures. Andi, I think truly, uh, this this five g combination with I o t and cloudy, I m l the are the technologies of the future that are collectively pushing us towards a a future where we're gonna Seymour smart cities that come into play driverless connected cars, etcetera. >>That's great. Now I wanna impact that a little bit more because we are here in aws re invent and I was just looking up. We had Glenn Goran 2015, introducing a W S s I O T Cloud. And it was a funny little demo. They had a little greenhouse, and you could turn on the water and open up the windows. But it's but it's a huge suite of services that you guys have at your disposal. Leveraging aws. I wonder, I guess, Andrew, if you could speak a little bit more suite of tools that you can now bring to bear when you're helping your customers go to the zero trust journey. >>Yeah, sure thing. So, um, obviously there's a significant partnership in place, and, uh, we work together, uh, pretty tremendously in the market, one of the service are one of solution offering that we've built out which we dub Delight Fortress, um is a is a concept that plays very nicely into our zero trust framework. More along the kind of horizontal components of our framework, which is really the fabric that ties it all together. Um s o the two horizontal than our framework around telemetry and analytics. A swell the automation orchestration. If I peel back the automation orchestration capability just a little bit, um, we we built this avoid fortress capability in order for organizations to kind of streamline um, some of the vulnerability management aspect of the enterprise. And so we're able through integration through AWS, Lambda and other functions, um, quickly identify cloud configuration issues and drift eso that, um, organizations cannot only, uh, quickly identify some of those issues that open up risk to the enterprise, but also in real time. Um, take some action to close down those vulnerabilities and ultimately re mediate them. Right? So it's way for, um, to have, um or kind of proactive approach to security rather than a reactive approach. Everyone knows that cloud configuration issues are likely the number one kind of threat factor for Attackers. And so we're able to not only help organizations identify those, but then closed them down in real time. >>Yeah, it's interesting because we hear that all the time. If there's a breach and if if they w s involved often it's a it's a configuration. You know, somebody left the door open basically, and and it really drives something you were talking about. Ravi is the increasing important of automation, um, and and using big data. And you talked about this kind of horizontal tele metrics and analytics because without automation, these systems are just getting too big and and crazy for people Thio manage by themselves. But more importantly, it's kind of a signal to noise issue when you just have so much traffic, right? You really need help surfacing. That signals you said so that your pro actively going after the things that matter and not being just drowned in the things that don't matter. Ravi, you're shaking your head up and down. I think you probably agree with this point. >>Yeah, yeah, Jeff and definitely agree with you. And what you're saying is truly automation is a way off dealing with problems at scale. When when you have hundreds of accounts and that spans across, you know, multiple cloud service providers, it truly becomes a challenge to establish a particular security baseline and continue to adhere to it. And you wanna have some automation capabilities in place to be able to react, you know, and respond to it in real time versus it goes down to a ticketing system and some person is having to do you know, some triaging and then somebody else is bringing in this, you know, solution that they implement. And eventually, by the time you're systems could be compromised. So ah, good way of doing this and is leveraging automation and orchestration is just a capability that enhances your operational efficiency by streamlining summed Emmanuel in repetitive tasks, there's numerous examples off what automation and orchestration could do, but from a security context. Some of the key examples are automated security operations, automated identity provisioning, automated incident response, etcetera. One particular use case that Deloitte identified and built a solution around is the identification and also the automated remediation of Cloud security. Miss Consideration. This is a common occurrence and use case we see across all our customers. So the way in the context of a double as the way we did this is we built a event driven architectures that's leveraging eight of us contribute config service that monitors the baselines of these different services. Azzan. When it detects address from the baseline, it fires often alert. That's picked up by the Cloudwatch event service that's ultimately feeding it upstream into our workflow that leverages event bridge service. From there, the workflow goes into our policy engine, which is a database that has a collection off hundreds of rules that we put together uh, compliance activities. It also matched maps back to, ah, large set of controls frameworks so that this is applicable to any industry and customer, and then, based on the violation that has occurred, are based on the mis configuration and the service. The appropriate lambda function is deployed and that Lambda is actually, uh, performing the corrective actions or the remediation actions while, you know, it might seem like a lot. But all this is happening in near real time because it is leveraging native services. And some of the key benefits that our customers see is truly the ease of implementation because it's all native services on either worse and then it can scale and, uh, cover any additional eight of those accounts as the organization continues to scale on. One key benefit is we also provide a dashboard that provides visibility into one of the top violations that are occurring in your ecosystem. How many times a particular lambda function was set off to go correct that situation. Ultimately, that that kind of view is informing. Thea Outfront processes off developing secure infrastructure as code and then also, you know, correcting the security guard rails that that might have drifted over time. Eso That's how we've been helping our customers and this particular solution that we developed. It's called the Lloyd Fortress, and it provides coverage across all the major cloud service providers. >>Yeah, that's a great summary. And I'm sure you have huge demand for that because he's mis configuration things. We hear about him all the time and I want to give you the last word for we sign off. You know, it's easy to sit on the side of the desk and say, Yeah, we got a big security and everything and you got to be thinking about security from from the time you're in, in development all the way through, obviously deployment and production and all the minutes I wonder if you could share. You know, you're on that side of the glass and you're out there doing this every day. Just a couple of you know, kind of high level thoughts about how people need to make sure they're thinking about security not only in 2020 but but really looking down the like another road. >>Yeah, yeah, sure thing. So, you know, first and foremost, it's important to align. Uh, any transformation initiative, including your trust to business objectives. Right? Don't Don't let this come off as another I t. Security project, right? Make sure that, um, you're aligning to business priorities, whether it be, you know, pushing to the cloud, uh, for scalability and efficiency, whether it's digital transformation initiative, whether it be a new consumer identity, Uh uh, an authorization, um, capability of china built. Make sure that you're aligning to those business objectives and baking in and aligning to those guiding principles of zero trust from the start. Right, Because that will ultimately help drive consensus across the various stakeholder groups within the organization. Uh, and build trust, if you will, in the zero trust journey. Um, one other thing I would say is focus on the fundamentals. Very often, organizations struggle with some. You know what we call general cyber hygiene capabilities. That being, you know, I t asset management and data classifications, data governance. Um, to really fully appreciate the benefits of zero trust. It's important to kind of get some of those table six, right? Right. So you have to understand, you know what assets you have, what the criticality of those assets are? What business processes air driven by those assets. Um, what your data criticality is how it should be classified intact throughout the ecosystem so that you could really enforce, you know, tag based policy, uh, decisions within, within the control stack. Right. And then finally, in order to really push the needle on automation orchestration, make sure that you're using technology that integrate with each other, right? So taken a p I driven approach so that you have the ability to integrate some of these heterogeneous, um, security controls and drive some level of automation and orchestration in order to enhance your your efficiency along the journey. Right. So those were just some kind of lessons learned about some of the things that we would, uh, you know, tell our clients to keep in mind as they go down the adoption journey. >>That's a great That's a great summary s So we're gonna have to leave it there. But Andrew Robbie, thank you very much for sharing your insight and and again, you know, supporting this This move to zero trust because that's really the way it's got to be as we continue to go forward. So thanks again and enjoy the rest of your reinvent. >>Yeah, absolutely. Thanks for your time. >>All right. He's Andrew. He's Robbie. I'm Jeff. You're watching the Cube from AWS reinvent 2020. Thanks for watching. See you next time.

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

>>Hi, everyone. Good afternoon. Thank you for joining this session. I feel honored to be invited to speak here today. And I also appreciate entity research Summit members for organ organizing and giving this great opportunity. Please let me give a quick introduction. First, I'm a Takashi from Marvin American population, and I'm leading technology scouting and global ation with digital health companies such as Business Alliance and Strategically Investment in North America. And since we started to focus on this space in 2016 our team is growing. And in order to bring more new technologies and services to Japan market Thesis year, we founded the new service theories for digital health business, especially, uh, in medical diagnosis space in Japan. And today I would like to talk how health care has been transformed for my micro perspective, and I hope you enjoy reasoning it. So what's happened since the US identify the first case in the middle of January, As everyone knows, unfortunately, is the damaged by this pandemic was unequal amongst the people in us. It had more determined tal impact on those who are socially and economically vulnerable because of the long, long lasting structural program off the U. S. Society and the Light Charity about daily case rating elevator country shows. Even in the community, the infection rate off the low income were 4.5 times higher than, uh, those of the high income and due to czar straight off the Corvette, about 14 million people are unemployed. The unique point off the U. S. Is that more than 60% of insurance is tied with employment, so losing a job can mean losing access to health care. And the point point here is that the Corvette did not create healthcare disparity but, uh nearly highlighted the underlying program and necessity off affordable care for all. And when the country had a need to increase the testing capacity and geographic out, treat the pharmacies and retails joined forces with existing stakeholders more than 90% off the U. S Corporation live within five miles off a community pharmacy such as CVS and Walgreen, so they can technically provide the test to everyone in all the community. And they also have a huge workforce memory pharmacist who are eligible to perform the testing scale, and this very made their potential in community based health care. Stand out and about your health has provided on alternative way for people to access to health care. At affordable applies under the unusual setting where social distancing, which required required mhm and people have a fear of infection. So they are afraid to take a public transportacion and visit >>the doctor the same thing supplied to doctor and the chart. Here is a number of total visit cranes by service type after stay at home order was issued across the U. S. By Ali April patient physical visits to doctor's offices or clinics declined by ALAN 70%. On the other hand, that share, or telehealth, accounted for 25% of the total total. Doctor's visit in April, while many states studied to re opening face to face visit is gradually recovering. And overall Tele Health Service did not offset the crime. Physician Physical doctor's visit and telehealth John never fully replace in person care. However, Telehealth has established a new way to provide affordable care, especially to vulnerable people, and I don't explain each player's today. But as an example, the chart shows the significant growth of the tell a dog who is one of the largest badger care and tell his provider, I believe there are three factors off paradox. Success under the pandemic. First, obviously tell Doc could reach >>the job between those patients and doctors. Majority of the patients who needed to see doctors who are those who have underlying health conditions and are high risk for Kelowna, Bilis and Secondary. They showed their business model is highly scalable. In the first quarter of this year, they moved quickly to expand their physical physicians network to increase their capacity and catch up growing demand. To some extent, they also contributed to create flexible job for the doctors who suffered from Lydia's appointment and surgery. They utilized. There are legalism to maximize the efficiency for doctors and doing so, uh, they have university maintained high quality care at affordable applies Yeah, and at the same time, the government recognize the body of about your care and de regulated traditional rules to sum up she m s temporary automated to pay a wide range of tell Her services, including hospital visit and HHS temporarily waived hip hop minorities for telehealth cases and they're changed allowed provider to use communication tools such as facetime and the messenger. During their appointment on August start, the government issued a new executive order to expand tell his services beyond the pandemic. So the government is also moving to support about your health care. So it was a quick review of the health care challenges and somewhat advancement in the pandemic. But as you understand, since those challenges are not caused by the pandemic, problems will stay remain and events off this year will continuously catalyze the transformation. So how was his cherished reshaped and where will we go? The topic from here can be also applied to Japan market. Okay, I believe democratization and decentralization healthcare more important than ever. So what does A. The traditional healthcare was defined in a framework over patient and a doctor. But in the new normal, the range of beneficiaries will be expanded from patient to all citizens, including the country uninsured people. Thanks to the technology evolution, as you can download health management off for free on iTunes stores while the range of the digital health services unable everyone to participate in new health system system. And in this slide, I put three essential element to fully realize democratization and decentralization off health care, health, literacy, data sharing and security, privacy and safety in addition, taken. In addition, technology is put at the bottom as a foundation off three point first. Health stimulus is obviously important because if people don't understand how the system works, what options are available to them or what are the pros and cons of each options? They can not navigate themselves and utilize the service. It can even cause a different disparity. Issue and secondary data must be technically flee to transfer. While it keeps interoperability ease. More options are becoming available to patient. But if data cannot be shared among stakeholders, including patient hospitals in strollers and budget your providers, patient data will be fragmented and people cannot yet continue to care which they benefited under current centralized care system. And this is most challenging part. But the last one is that the security aspect more players will involving decentralized health care outside of conventional healthcare system. So obviously, both the number of healthcare channels and our frequency of data sharing will increase more. It's create ah, higher data about no beauty, and so, under the new health care framework, we needed to ensure patient privacy and safety and also re examine a Scott write lines for sharing patient data and off course. Corbett Wasa Stone Catalyst off this you saved. But what folly. Our drivers in Macro and Micro Perspective from Mark Lowe. The challenges in healthcare system have been widely recognized for decades, and now he's a big pain. The pandemic reminded us all the key values. Misha, our current pain point as I left the church shores. Those are increasing the population, health sustainability for doctors and other social system and value based care for better and more affordable care. And all the elements are co dependent on each other. The light chart explained that providing preventive care and Alan Dimension is the best way threes to meet the key values here. Similarly, the direction of community based care and about your care is in line with thes three values, and they are acting to maximize the number of beneficiaries form. A micro uh, initiative by nonconventional players is a big driver, and both CBS and Walmart are being actively engaged in healthcare healthcare businesses for many years. And CBS has the largest walking clinic called MinuteClinic, Ottawa 1100 locations, and Walmart also has 20 primary clinics. I didn't talk to them. But the most interesting things off their recent innovation, I believe, is that they are adjusted and expanded their focus, from primary care to community health Center to out less to every every customer's needs. And CBS Front to provide affordable preventive health and chronic health monitoring services at 1500 CBS Health have, which they are now setting up and along a similar line would Mark is deploying Walmart Health Center, where, utilizing tech driven solutions, they provide affordable one stop service for core healthcare. They got less, uh, insurance status. For example, more than 40% of the people in U. S visit will not every big, so liberating the huge customer base and physical locations. Both companies being reading decentralization off health care and consumer device company such as Apple and Fitbit also have helped in transform forming healthcare in two ways. First, they are growing the boundaries between traditional healthcare and consumer product after their long development airport available, getting healthcare device and secondary. They acted as the best healthcare educators to consumers and increase people's healthcare awareness because they're taking an important role in the enhancement, health, literacy and healthcare democratization. And based on the story so far, I'd like to touch to business concept which can be applied to both Japan and the US and one expected change. It will be the emergence of data integration plot home while the telehealth. While the healthcare data data volume has increased 15 times for the last seven years and will continuously increase, we have a chance to improve the health care by harnessing the data. So meaning the new system, which unify the each patient data from multiple data sources and create 360 degrees longitudinal view each individual and then it sensitized the unified data to gain additional insights seen from structure data and unable to provide personal lives care. Finally, it's aggregate each individual data and reanalyzed to provide inside for population health. This is one specific model I envision. And, uh, health care will be provided slew online or offline and at the hospital or detail store. In order to amplify the impact of health care. The law off the mediator between health care between hospital and citizen will become more important. They can be a pharmacy toe health stand out about your care providers. They provide wide range of fundamental care and medication instruction and management. They also help individuals to manage their health care data. I will not explain the details today, but Japan has similar challenges in health care, such as increasing healthcare expenditure and lack of doctors and care givers. For example, they people in Japan have physical physician visit more than 20 times a year on average, while those in the U. S. On >>the do full times it sounds a joke, but people say because the artery are healthy, say visit hospitals to see friends. So we need to utilize thes mediators to reduce cost while they maintained social place for citizens in Japan, the government has promoted, uh, usual family, pharmacist and primary doctors and views the community based medical system as a policy. There was division of dispensing fees in Japan this year to ship the core load or pharmacist to the new role as a health management service providers. And so >>I believe we will see the change in those spaces not only in the U. S, but also in Japan, and we went through so unprecedented times. But I believe it's been resulting accelerating our healthcare transformation and creating a new business innovation. And this brings me to the end of my presentation. Thank you for your attention and hope you could find something somehow useful for your business. And if you have any questions >>or comments, please for you feel free to contact me.

>>Hi, everyone. Good afternoon. Thank you for joining this session. I feel honored to be invited to speak here today. And I also appreciate entity research Summit members for organ organizing and giving this great opportunity. Please let me give a quick introduction. First, I'm a Takashi from Marvin American population, and I'm leading technology scouting and global ation with digital health companies such as Business Alliance and Strategically Investment in North America. And since we started to focus on this space in 2016 our team is growing. And in order to bring more new technologies and services to Japan market Thesis year, we founded the new service theories for digital health business, especially, uh, in medical diagnosis space in Japan. And today I would like to talk how health care has been transformed for my micro perspective, and I hope you enjoy reasoning it. So what's happened since the US identify the first case in the middle of January, As everyone knows, unfortunately, is the damaged by this pandemic was unequal amongst the people in us. It had more determined tal impact on those who are socially and economically vulnerable because of the long, long lasting structural program off the U. S. Society and the Light Charity about daily case rating elevator country shows. Even in the community, the infection rate off the low income were 4.5 times higher than, uh, those of the high income and due to czar straight off the Corvette, about 14 million people are unemployed. The unique point off the U. S. Is that more than 60% of insurance is tied with employment, so losing a job can mean losing access to health care. And the point point here is that the Corvette did not create healthcare disparity but, uh nearly highlighted the underlying program and necessity off affordable care for all. And when the country had a need to increase the testing capacity and geographic out, treat the pharmacies and retails joined forces with existing stakeholders more than 90% off the U. S Corporation live within five miles off a community pharmacy such as CVS and Walgreen, so they can technically provide the test to everyone in all the community. And they also have a huge workforce memory pharmacist who are eligible to perform the testing scale, and this very made their potential in community based health care. Stand out and about your health has provided on alternative way for people to access to health care. At affordable applies under the unusual setting where social distancing, which required required mhm and people have a fear of infection. So they are afraid to take a public transportacion and visit >>the doctor the same thing supplied to doctor and the chart. Here is a number of total visit cranes by service type after stay at home order was issued across the U. S. By Ali April patient physical visits to doctor's offices or clinics declined by ALAN 70%. On the other hand, that share, or telehealth, accounted for 25% of the total total. Doctor's >>visit in April, while many states studied to re opening face to face visit is gradually recovering. And overall Tele Health Service did not offset the crime. Physician Physical doctor's visit and telehealth John never fully replace in person care. However, Telehealth has established a new way to provide affordable care, especially to vulnerable people, and I don't explain each player's today. But as an example, the chart shows the significant growth of >>the tell a dog who is one of the largest badger care and tell his provider, I believe there are three factors off paradox. Success under the pandemic. First, obviously tell Doc could reach >>the job between those patients and doctors. Majority of the patients who needed to see doctors who are those who have underlying health conditions and are high risk for Kelowna, Bilis and Secondary. They showed their business model is highly scalable. In the first quarter of this year, they moved quickly to expand their physical physicians network to increase their capacity and catch up growing demand. To some extent, they also contributed to create flexible job for the doctors who suffered from Lydia's appointment and surgery. They utilized. There are legalism to maximize the efficiency for doctors and doing so, uh, they have university maintained high quality care at affordable applies Yeah, and at the same time, the government recognize the body of about your care and de regulated traditional rules to sum up she m s temporary automated to pay a wide range of tell Her services, including hospital visit and HHS temporarily waived hip hop minorities for telehealth cases and they're changed allowed provider to use communication tools such as facetime and the messenger. During their appointment on August start, the government issued a new executive order to expand tell his services beyond the pandemic. So the government is also moving to support about your health care. So it was a quick review of the health care challenges and somewhat advancement in the pandemic. But as you understand, since those challenges are not caused by the pandemic, problems will stay remain and events off this year will continuously catalyze the transformation. So how was his cherished reshaped and where will we go? The topic from here can be also applied to Japan market. Okay, I believe democratization and decentralization healthcare more important than ever. So what does A. The traditional healthcare was defined in a framework over patient and a doctor. But in the new normal, the range of beneficiaries will be expanded from patient to all citizens, including the country uninsured people. Thanks to the technology evolution, as you can download health management off for free on iTunes stores while the range of the digital health services unable everyone to participate in new health system system. And in this slide, I put three essential element to fully realize democratization and decentralization off health care, health, literacy, data sharing and security, privacy and safety in addition, taken. In addition, technology is put at the bottom as a foundation off three point first. Health stimulus is obviously important because if people don't understand how the system works, what options are available to them or what are the pros and cons of each options? They can not navigate themselves and utilize the service. It can even cause a different disparity. Issue and secondary data must be technically flee to transfer. While it keeps interoperability ease. More options are becoming available to patient. But if data cannot be shared among stakeholders, including patient hospitals in strollers and budget your providers, patient data will be fragmented and people cannot yet continue to care which they benefited under current centralized care system. And this is most challenging part. But the last one is that the security aspect more players will involving decentralized health care outside of conventional healthcare system. So obviously, both the number of healthcare channels and our frequency of data sharing will increase more. It's create ah, higher data about no beauty, and so, under the new health care framework, we needed to ensure patient privacy and safety and also re examine a Scott write lines for sharing patient data and off course. Corbett Wasa Stone Catalyst off this you saved. But what folly. Our drivers in Macro and Micro Perspective from Mark Lowe. The challenges in healthcare system have been widely recognized for decades, and now he's a big pain. The pandemic reminded us all the key values. Misha, our current pain point as I left the church shores. Those are increasing the population, health sustainability for doctors and other social system and value based care for better and more affordable care. And all the elements are co dependent on each other. The light chart explained that providing preventive care and Alan Dimension is the best way threes to meet the key values here. Similarly, the direction of community based care and about your care is in line with thes three values, and they are acting to maximize the number of beneficiaries form. A micro uh, initiative by nonconventional players is a big driver, and both CBS and Walmart are being actively engaged in healthcare healthcare businesses for many years. And CBS has the largest walking clinic called MinuteClinic, Ottawa 1100 locations, and Walmart also has 20 primary clinics. I didn't talk to them. But the most interesting things off their recent innovation, I believe, is that they are adjusted and expanded their focus, from primary care to community health Center to out less to every every customer's needs. And CBS Front to provide affordable preventive health and chronic health monitoring services at 1500 CBS Health have, which they are now setting up and along a similar line would Mark is deploying Walmart Health Center, where, utilizing tech driven solutions, they provide affordable one stop service for core healthcare. They got less, uh, insurance status. For example, more than 40% of the people in U. S visit will not every big, so liberating the huge customer base and physical locations. Both companies being reading decentralization off health care and consumer device company such as Apple and Fitbit also have helped in transform forming healthcare in two ways. First, they are growing the boundaries between traditional healthcare and consumer product after their long development airport available, getting healthcare device and secondary. They acted as the best healthcare educators to consumers and increase people's healthcare awareness because they're taking an important role in the enhancement, health, literacy and healthcare democratization. And based on the story so far, I'd like to touch to business concept which can be applied to both Japan and the US and one expected change. It will be the emergence of data integration plot home while the telehealth. While the healthcare data data volume has increased 15 times for the last seven years and will continuously increase, we have a chance to improve the health care by harnessing the data. So meaning the new system, which unify the each patient data from multiple data sources and create 360 degrees longitudinal view each individual and then it sensitized the unified data to gain additional insights seen from structure data and unable to provide personal lives care. Finally, it's aggregate each individual data and reanalyzed to provide inside for population health. This is one specific model I envision. And, uh, health care will be provided slew online or offline and at the hospital or detail store. In order to amplify the impact of health care. The law off the mediator between health care between hospital and citizen will become more important. They can be a pharmacy toe health stand out about your care providers. They provide wide range of fundamental care and medication instruction and management. They also help individuals to manage their health care data. I will not explain the details today, but Japan has similar challenges in health care, such as increasing healthcare expenditure and lack of doctors and care givers. For example, they people in Japan have physical physician visit more than 20 times a year on average, while those in the U. S. On the do full times it sounds a joke, but people say because the artery are healthy, say visit hospitals to see friends. So we need to utilize thes mediators to reduce cost while they maintained social place for citizens in Japan, the government has promoted, uh, usual family, pharmacist and primary doctors and views the community based medical system as a policy. There was division of dispensing fees in Japan this year to ship the core load or pharmacist to the new role as a health management service providers. And so I believe we will see the change in those spaces not only in the U. S, but also in Japan, and we went through so unprecedented times. But I believe it's been resulting accelerating our healthcare transformation and creating a new business innovation. And this brings me to the end of my presentation. Thank you for your attention and hope you could find something somehow useful for your business. And if you have any questions >>or comments, please for you feel free to contact me. Thank you.

>> Narrator: From theCUBE Studios in Palo Alto in Boston, connecting with thought leaders all around the world, this is theCUBE conversation. >> Hi everybody, this is Dave Vellante and welcome to this week's CUBE insights powered by ETR. In this breaking analysis, we're going to bring in Sagar Kadakia who's the Director of Research at ETR. He's been away for the last couple of weeks, he's really digging into the latest data set, ETR of course it was in it's quiet period. And today, what we want to do is give you three of the macro takeaways from that last two-week analysis and drill into to some of the sectors. So Sagar, that's for coming on, great to see you again. Let's get right into it. >> Let's do it, thanks for having me. >> You've been crazy busy, we started the year at a plus 4%, consensus IT spend. We reported for several weeks and ended up at minus 4%. We're now at minus 5%, after you've gone through and done some additional analysis. So bring us up to date the IT spend projection. >> Yeah no problem, and that's our first macro takeaway, is we're seeing declines in IT budget, a decline of 5%. And remember, coming into the year as you mentioned, consensus assessments were right around that 4% number. And so we've seen this kind of 900 basis point shift downward so that's kind of where we are today, if we kind of look at that chart that we've been tracking for the last few weeks. And then for those that have seen this chart before, you've kind of seen where we've been kind of going the last two, three weeks. And for those that haven't seen the chart, I'll kind of go through it now. So, as many of you know, kind of launched its COVID-19 drill down survey to measure the impact that the virus was going to have on total spend this year and so we kind of launched that drill down on March 11th and so if you kind of look at that blue line there, what you're looking at, is we asked individuals, estimate what percentage impact you think the virus is going to have on your budget versus your original expectations. And since we launched this on March 11th, on that blue line that you're looking at, we got a lot of positivity in the beginning. And so if you look at the blue line all the way through, you follow that, you get about zero percent growth. Now the issue is, as I just mentioned is, we launched on the 11th, and there wasn't a tremendous amount of information available as to how severe the virus was, and so we kind of did this in Venn analysis and we talked about this last time, on the last breaking analysis, where it's probably more appropriate to look at a start date closer to 3/17 or 3/23 when the market really understood the severity of COVID-19. NYC became the epicenter. And if we look at just those customers who indicated a spend impact after that date, you can see it's coming out to about four or 5% decline. And so that's kind of one of our big macro takeaways, and the other thing on this chart, kind of focus on is, and even though we're not looking at, some of the vendors here, is when you think about declines, it's not across the full IT stack, and I think that's really important for the audience to understand. We're seeing focused declines among on-prem legacy pure plays. You're still seeing CIO spend on cloud and SaaS. In fact, they're doubling down there. And so when you kind of think about how things are going to shape up the next three, six, nine months, there's going to be a lot of bifurcation. And we think cloud and SaaS are going to be well positioned with a lot of legacy and on-prem. That's where you're going to see a majority of those declines that you're seeing here kind of play out. >> I've made the case, statement many times that cloud is good, or downturns have been to cloud. You saw this in 2008, 2009 with the shift from CapEx to OpEx. We came out of 2009 into the decade of cloud. And very clearly we're seeing some similar things here as people shift to that work-from-home. We had one CIO on the recent Venns that I want to just delete my data centers. Unfortunately, he's not going to be able to do that overnight, but I think, as Eric Bradley pointed out last week, a lot of customers who weren't even thinking about cloud, or really were sort of reticent to go all in, really have flipped and changed their tune. Let's talk about some of the industries that are impacted by this COVID-19 and the stay-at-home. This slide really kind of underscores that. Why don't you take us through it? >> Yeah, no problem. So on the last slide, you were looking at kind of our COVID-19 drill-down study. On this slide, what we're now going to focus on is a study that we did in tandem, which is called our Technology Spending Intentions Survey. And specifically we conducted this in April. What we did is we asked CIOs to update their 2020 spending intentions versus how they spent in '19. So this survey was originally posed in January and then we're essentially asking for a three-month update now. So we're trying to get an understanding of how much has changed in the last three months because of COVID-19. And when we asked these CIOs, we give them essentially a list of 400 vendors. And they're able to then indicate which ones they're flattening on, decreasing on, maybe accelerating on. And so what you're looking at here is we've aggregated that data by industry. And if you look at the X-axis here, you're going to look at spend intensity versus three months ago. And the Y-axis will be spend intensity versus a year ago. And so what you're seeing here is over the last three months, look at how much verticals, like retail/consumer, airlines, delivery services, financials/insurance, IT/TelCo, services/consulting. Those have really seen some of the largest pullbacks in spend versus three months ago. And those are also some of the industries that have indicated the largest pullback in demand from consumers and businesses. And so this is where we think a lot of the declines that we showed you earlier really kind of focus on some of these verticals. And that's how, when you kind of think about which organization are going to be hurt, which ones might see the most impact, three, six months from now, this is a really good chart to view. >> Yeah, a couple of points I would make on this data. Retail and consumer, again, even that's bifurcated. Obviously the physical stores getting crushed. You see Amazon now trading at all-time highs. Target announced today, I think they said a 200% increase in online shopping, which, of course, is fulfilled. 85% of Target's demand is fulfilled by their stores. So that's kind of mixed. You're going to see an accelerated move toward digital transformation there. Airlines, it's really unclear what's going to happen there. IT/TelCo, on one of the last Venns we talked about MPLS, people trying to get off of MPLS, really moving toward a SD-WAN. Healthcare, pharma, healthcare doesn't have time to do anything right now. No time to take a breather. Financials is interesting. I mean, they're down right now, but they still have a lot of cash. Liquidity is good. And then energy, I mean oil, I've just never seen anything like it. We're concerned obviously about credit risk there and oil companies being able to pay off their debts. So it's really not a pretty picture, is it? >> Yeah, and if focus on energy, even though you're not seeing a huge pullback versus three months ago in energy, it's really important to understand when we did this survey in January, energy was all the way on the left side of that chart. And so it already looked really bad coming into the year. So it got worse. But because of the severity versus last year, like they're just not seeing that much more of a negative impact now. This was before, this survey closed before everything happened the last few days with oil prices. So it is very possible that that data is going to get worse. And we'll know if it gets really-- >> We're not laughing a lot these days, but if you haven't filled up your car in a while, I mean it's, Anyway, let's go into the security piece. We talked about, you guys were really the first to report this work-from-home pivot. Others have sort of more recently coming to that conclusion. And it wasn't just Zoom and WebEx and video collaboration, Teams, et cetera. It really was all kinds of infrastructure, including security. So we can bring up the next chart, guys. Let's sort of get into this. We're going to talk about the sector and some of the vendors in here. Let's go. >> Yeah, no problem, so if we kind of step away from the macro and really start getting into the sectors and vendors in here. If we start with security, what we're really saying is that, look, a remote workforce is really kind of revealing best-in-breed. And we think it's going to lead to the permanent changes. So what you're looking at here is these are the net scores for each individual vendor currently versus three months ago as well as a year ago levels. The yellow bars will be what's currently. And the way to think about net score is just kind of spend intensity. And so the higher your net score, the more spend intensity, the more spend velocity you're seeing from enterprise customers. And what we're really seeing here, if you kind of look at the vendors on the left, you're seeing a lot of acceleration among secure web gateway end point, mobile security, cloud SaaS application security, identity, and these make sense. As we mentioned earlier, as you really accelerate your cloud and SaaS spend, you're going to want to use vendors that best protect those areas. And so if you look to the left here, Okta and Zscaler, Cloudflare, CrowdStrike, some of these really look best positioned moving forward. Palo Alto looks good longer term. Splunk at this point also looked good longer term. And then the other thing to kind of hit on here is the other side in terms of, we talked about the bifurcation that we expect. We're seeing significant declines in net scores among a lot of these legacy vendors. Check points come down quite a bit. Juniper, Trend Micro, Broadcom, Barracuda Networks, SonicWALL, and so you can see the disparity here. It's pretty clear on the image. But we think there's some pretty clear winners and losers here. And I think we may see permanent changes moving forward. >> Yeah, so Twistlock, of course, is now owned by Palo Alto. CrowdStrike, they're a hot company in the sector. Okta, I have the Chief Product Officer coming on shortly here for part of my CXO series. We've talked about Palo Alto and how they sort of fell behind a little bit in the cloud. But you talk to customers, they really see Palo Alto as in the mix. Zscaler came up in the Venn as, to your point, securing gateways and doing a really good job in that space. And so I think the fragmentation, the fragmentation probably continues, but there's also bifurcation, as you pointed out. Let's talk about cloud. As you've said and I said, downturns have been good to cloud. People are obviously looking more toward cloud, whether it's SaaS or cloud type of consumption. Let's bring up the next slide, which looks at the big three, Azure, AWS, and GCP. First of all, all three have very strong net scores. Up in the 60% plus range. But you have Azure pulling away. I'd love to hear your thoughts on that. >> Yeah, that's right, and we've kind of been using this analogy of kind of a horse race. Just kind of as context, coming into January you see really GCP accelerating. And so one of the things we said in January was it's becoming more of a three-horse race. Even though GCP doesn't have the same type of market share as the other two, you are seeing the spend intensity increase. And now what you're seeing is Azure pulling away a little bit because of, we think, COVID-19. When you look at Azure's data set, it really looks robust and healthy across all verticals, across most regions. And that is what you're seeing here where it's continuing to kind of accelerate. It looks good. AWS, GCP, it also looks good here, but you're not seeing the same uniform strength. There's a couple verticals for AWS where we're seeing a little bit of a pullback in spend, like retail and industrials. For GCP we're seeing a pullback in mid-size and small enterprises. So that's causing a couple of cracks here and there. Even though they look overall healthy, but we did want to kind of indicate here on cloud where, look one vendor looks like they're pulling away when it comes to spend velocity. >> It's going to be interesting to see. I mean, we reported on the sort of deltas between Azure and AWS and the cloud, the quality of the cloud. I think we're going to carefully watch the quarterly reports. You always have to kind of squint through the Azure numbers to see what's in there. But there's no question that Microsoft, across the board, is really very, very strong. All right, let's talk about collaboration, productivity, video conferencing. I mean, we've certainly seen upticks. But as shown on this slide, you guys, if you could bring the next slide up. You know, it's not all rosy. Talk about this a little bit. >> Yeah, I think, look, there's been a lot of coverage around which vendors look best. And so I kind of want to take the opposite view on this chart for the audience, and say hey look, which vendors are not benefiting? And this is kind of like a hodgepodge sector of productivity and collaboration, video conferencing. What we're saying is it's now of never, so to speak. And you're looking at replacement rates. So if you look at, if you see something on this chart that says 20% replacement, that means one out of five customers indicated for that vendor in our survey, indicated a replacement for them, which is not good. And so you're seeing vendors here like Dropbox, Box and Slack having elevated or accelerating replacement levels. And these vendors, pitch themselves as collaboration tools. And if they're not doing well now and they're seeing elevated replacements, especially as everyone is working from home, that doesn't bode well for the future. >> I think people who know me know I'm not a huge fan of Box and Slack. They drive me crazy. And so this is interesting to see. I mean, we're a Zoom shop, so obviously you Zoom, you like Zoom. I had my first experience very recently with Microsoft teams. I was quite impressed. I thought it was easy to use. Skype, hell was just terrible. And so, much, much improved. Very interesting cut on that one. So again, it's a bifurcated story. Let's drill into teams a little bit. Guys, have you bring up the next slide, Movements reporting. And you guys are really again, first on this, how strong Microsoft is across the board. But really going after it and collaboration. >> On that previous slide you saw that, Dropbox and Slack, we're all seeing replacements. So again, a lot of customers like where was all that spend going? Well, it's going to Microsoft Teams. It's going to One Drive. This is a Slack drilled out, or sorry, a Slack and teams drill down. That we did, earlier this year. And what we're trying to do is measure, how these products were going to do in the next 12 months. And so what you're looking at here is Fortune 500 organizations. What we did is we asked them how much of your organization, is using Microsoft Teams today. What percentage of your organization is going to be using Microsoft Teams 12 months from now? That's going to be in the yellow bars. And you can see the big upticks in 12 months. And we took some mid point averages. Look at how much Microsoft Teams is going to grow, within Fortune 500 accounts in the next 12 months. And if we look at Slack on the next slide, you're really now seeing the exact opposite. Same question, how many folks in your Fortune 500 organization are using Slack today? And what does that look like in 12 months? And the mid point average is actually coming down. And so, it's like Slack is a seat-based model. And so when you have less users that's going to generate less revenue. And so again, this is amongst the existing Fortune 500 customers. This doesn't include new Fortune 500, but this spells problems for Slack, when you kind of think about the next six to 12 months ahead. >> Well it's one thing if you're competing with Microsoft and your AWS. I've not really not worried about AWS, Microsoft, take a note AWS. If you're one of these collaboration platforms, Microsoft, we've seen over the years, first of all, they got great developer affinity. They know how to bundle different products together. Now they got the cloud working so they got their flywheel effect in the cloud. There's just not a ton of room. The thing is they have such a huge software estate, such a giant customer install base and it's just makes it easy for them. The products are good enough or in some cases really good. So that's going to be something to watch, because there's a lot of high valuations going on right now in their collaboration space. >> That's right. And I think, it really hits on the previous slide, or the previous slides on collaboration that we saw, was when you think again about the declines, a lot of that is impacting some of these pure plays. So in security you saw a lot of the legacy names getting in. On the collaboration side, you saw a lot of these pure plays your getting in. And so this is kind of, again when you think about where budgets are going and which vendors are being impacted, it's really concentrated into some specific areas. >> So now, one of the hardest hit areas, and you guys reported on this earlier, was the IT consulting and outsourcing IT. You guys have you bring up that the chart, it's pretty ugly. Maybe you can explain what you're seeing here and why you think that is. >> Yeah, no problem. So again, this is from our technology spending intention survey. We're measuring spend velocity here. Spend intensity, and you can see across, these are just a handful of IT consulting firms. If you look at the blue bars to the yellow bar. So the blue bar is, 2020 spending intent that we captured in January and now we're asking for updated 2020 spending intentions. You can see the deceleration in just the last three months. If you look at our COVID-19 drill down side that we conducted, one of the questions in there we asked was, are you freezing new IT projects or deployments? Almost, 1/4 percentage of customers said they are. And so, that is going to spell problems for this space. When you think about, look, if you're going into uncertain times an easy way to reduce your budget is by, spending less with consulting vendors since you know, you can just less than the number of deliverables, these individuals get paid based on. How many deliverables they can complete. So this is another area that when you kind of think about where the declines are coming from, this is certainly an area to look at. >> A lot of the customers we've talked to have said, we've basically shut down spending on some of the large projects. We're still focusing on some digital transformation, but that's maybe a longer term priority. And then the IBM piece of this chart, guys, if you could bring it back is interesting to me because look, they paid 34 billion for Red Hat. I've always said a key to the Red Hat acquisition was being able to point it at the large consulting base and modernize those applications. IBM actually had a pretty good quarter in services. Although they did mention that respect especially in software that in the month of the quarter software spending shutdown. I don't think we got visibility that this piece of the business, but this could be, somewhat of a concern going forward. I think that's going to be one of the areas that gets slow rolled coming back, Sagar. I don't think it's going to come back tomorrow. So please your thoughts. >> Just to kind of quickly wrap up IBM. So yeah, one of the things we kind of saw in the data was not only eroding spending intention data on a lot of their SaaS portfolio but also eroding market share. And we saw big down takes on Red Hat products and IT services. Even in cloud. And I know they indicated pretty healthy numbers on Red Hat and cloud. But again, we're asking about 2020, forward-looking spending intentions. And of course they pulled their guidance. So we don't know how that's going to look. But in our data, things are really coming down versus three months ago. And so I think just overall, that is a data set that we're quite negative one. >> I think IBM has that sense. Like I said, March was not good for software. That's when the big deals come through. You're right. Red Hat, I think route 20% in the quarter and is now accredited from a cashflow basis, which is one of their targets. I think they beat their target there. Still good cashflow. But I think there's just so much uncertainty, And IBM have to be prepared for that and I'm sure will. That we're at minus 5% now. We're seeing cloud SaaS, we're seeing a bifurcation. We talked about some of the areas that are in trouble. That's kind of part one. Next week we'll be talking about part two. What can we expect? >> Yeah, we'll start going through networking, CDN, ITSM, IT workflows, database, data warehousing, and we'll kind of go through that as well. But again, you're going to see a lot of what we talked about today. Just the bifurcation span where, vendors that are more next gen, more work-from-home friendly like all of the SaaS guys, they're doing really well. And on the on-prem and the legacy, you're just seeing elevated replacements, elevated decreased rates. This is the most bifurcated, I've seen this data set and I've been doing this at ETR for, almost seven, probably going on eight years now. So I think that kind of says something about the environment that we're in and what to kind of expect in the next three to six months. >> And it's kind of like the stock market is right now. You're actually seeing, some great momentum in certain stocks and terrible in others. Those were great balance sheets and maybe COVID is a tailwind for them. Others, tons of uncertainty, a lot of concern. I know in poking around the data set, like you said, some of the analytics, the data warehouses, you see Snowflake, UiPath, Automation Anywhere. A lot of the automation, RPA, momentum is there. Security, we talked about that. There's some real bright spots there but a lot of the on-prem stuff. We'll see product cycles affect that, in the second half of of 2020. We'll continue to report on this Sagar. Thank you so much for we're coming on and we'll definitely see you next week. >> Thanks for having me again, Dave. Looking forward. >> All right, and thank you for watching, this CUBE insights powered by ETR. We will see you next time. Don't forget, all these episodes are available as podcasts, wherever you listen. Go to etr.plus, checkout what's happening there. Siliconangle.com has all the news I publish in there weekly. I also publish on wikibond.com. Thanks for watching this breaking analysis. This is Dave Vellante and Sagar Kadakia, we'll see you next time. (upbeat music)

la from Las Vegas it's the cube covering AWS reinvent 2019 brought to you by Amazon Web Services and in care along with its ecosystem partners hey welcome back everyone cubes live coverage of eight of us reinvent 2019 this is the cube seventh year covering Amazon reinvent it's their eighth year of the conference and want to just shout out to Intel for their sponsorship for these two amazing sets without their support we would be able to bring our mission of great content to you I'm John Force to many men we're here with the chief of AWS the chief executive officer Andy chassis tech athlete and himself three our keynotes welcome to the cube again great to see you great to be here thanks for having me guys congratulations on a great show a lot of great buzz thank you a lot of good stuff your keynote was phenomenal you get right into you giddy up right into as you say three hours 30 announcements you guys do a lot but what I liked the new addition in the last year and this year is the band house man yeah they're pretty good they hit the Queen note so that keeps it balanced so we're going to work on getting a band for the cube awesome so if I have to ask you what's your walk-up song what would it be there's so many choices depends what kind of mood I'm in but maybe times like these by the Foo Fighters these are unusual times right now Foo Fighters playing at the Amazon intersect show they are Gandy well congratulations on the intersect you got a lot going on intersect is the music festival I'll get that in a second but I think the big news for me is two things obviously we had a one-on-one exclusive interview and you laid out essentially what looks like was gonna be your keynote it was transformation key for the practice I'm glad to practice use me anytime yeah and I like to appreciate the comments on Jedi on the record that was great but I think the transformation story is a very real one but the NFL news you guys just announced to me was so much fun and relevant you had the Commissioner of NFL on stage with you talking about a strategic partnership that is as top-down aggressive goals you could get yeah I have Roger Goodell fly to a tech conference to sit with you and then bring his team talk about the deal well you know we've been partners with the NFL for a while with the next-gen stats are they using all their telecasts and one of the things I really like about Roger is that he's very curious and very interested in technology in the first couple times I spoke with him he asked me so many questions about ways the NFL might be able to use the cloud and digital transformation to transform their various experiences and he's always said if you have a creative idea or something you think that could change the world for us just call me is it or text me or email me and I'll call you back within 24 hours and so we've spent the better part of the last year talking about a lot of really interesting strategic ways that they can evolve their experience both for fans as well as their players and the player health and safe safety initiative it's so important in sports and particularly important with the NFL given the nature of the sport and they've always had a focus on it but what you can do with computer vision and machine learning algorithms and then building a digital athlete which is really like a digital twin of each athlete so you understand what does it look like when they're healthy what and compare that when it looks like they may not be healthy and be able to simulate all kinds of different combinations of player hits and angles and different plays so that you can try to predict injuries and predict the right equipment you need before there's a problem can be really transformational so it was super excited about it did you guys come up with the idea it was the collaboration between there's really a collaboration I mean they look they are very focused on player's safety and health and it's it's a big deal for their you know they have two main constituents that the players and fans and they care deeply about the players and it's a it's a hard problem in a sport like football but you watch it yeah I gotta say it does point out the use cases of what you guys are promoting heavily at the show here of the stage maker studio which is a big part of your keynote where they have all this data right and they're dated hoarders they've the hoard data but they're the manual process of going through the data it was a killer problem this is consistent with a lot of the enterprises that are out there they have more data than they even know so this seems to be a big part of the strategy how do you get the customers to actually a wake up to the fact that they got data and how do you tie that together I think in almost every company they know they have a lot of data and there are always pockets of people who want to do something with it but when you're gonna make these really big leaps forward these transformations so things like Volkswagen is doing with they're reinventing their factories in their manufacturing process or the NFL where they're gonna radically transform how they do players health and safety it starts top-down and if they if the senior leader isn't convicted about wanting to take that leap forward and trying something different and organizing the data differently and organizing the team differently and using machine learning and getting help from us and building algorithms and building some muscle inside the company it just doesn't happen because it's not in the normal machinery of what most companies do and so it all wait almost always starts top-down sometimes it can be the commissioner or the CEO sometimes it can be the CIO but it has to be senior level conviction or it does get off the ground and the business model impact has to be real for NFL they know concussions hurting their youth pipelining this is a huge issue for them is their business model they they lose even more players to lower extremity injuries and so just the notion of trying to be able to predict injuries and you know the impact it can have on rules the impact it can have on the equipment they use it's a huge game changer when they look at the next 10 to 20 years all right love geeking out on the NFL but no more do you know off camera a 10 man is here defeated season so everybody's a Patriots fan now it's fascinating to watch you and your three-hour keynote Vernor in his you know architectural discussion really showed how AWS is really extending its reach you know it's not just a place for a few years people have been talking about you know cloud as an operation operational model it's not a destination or a location but I felt that really was laid out is you talked about breadth and depth and Verna really talked about you know architectural differentiation people talk about cloud but there are very there are a lot of differences between the vision for where things are going help us understand and why I mean Amazon's vision is still a bit different from what other people talk about where this whole cloud expansion journey but put over what tagger label you want on it but you know the control plane and the technology that you're building and where you see that going well I think that we've talked about this a couple times we we have two macro types of customers we have those that really want to get at the load level building blocks and stitch them together creatively and however they see fit to create whatever is in there in their heads and then we have this second segment of customers who say look I'm willing to give up some of that flexibility in exchange for getting 80% of the way they're much faster in an abstraction that's different from those low level building blocks in both segments of builders we want to serve and serve well and so we built very significant offerings in both areas I think when you look at micro services you know some of it has to do with the fact that we have this very strongly held belief born out of several years at Amazon where you know the first seven or eight years of Amazon's consumer business we basically jumbled together all of the parts of our technology and moving really quickly and when we wanted to move quickly where you had to impact multiple internal development teams it was so long because it was this big ball this big monolithic piece and we got religion about that and trying to move faster in the consumer business and having to tease those pieces apart and it really was a lot of the impetus behind conceiving AWS where it was these low-level very flexible building blocks that don't try and make all the decisions for customers they get to make them themselves and some of the micro services that you saw Verner talking about just you know for instance what we what we did with nitro or even what we do with firecracker those are very much about us relentlessly working to continue to to tease apart the different components and even things that look like low-level building blocks over time you build more and more features and all of a sudden you realize they have a lot of things that are they were combined together that you wished weren't that slowed you down and so nitro was a completely reimagining of our hypervisor and virtualization layer to allow us both to let customers have better performance but also to let us move faster and have a better security story for our customers I got to ask you the question around transformation because I think it all points to that all the data points you got all the references goldman-sachs on stage at the keynote Cerner and the healthcare just an amazing example because I mean this demonstrating real value there there's no excuse I talked to someone who wouldn't be named last night and then around the area said the CIA has a cost bar like this cost up on a budget like this but the demand for mission based apps is going up exponentially so there's need for the cloud and so seeing more and more of that what is your top-down aggressive goals to fill that solution base because you're also very transformational thinker what is your what is your aggressive top-down goals for your organization because you're serving a market with trillions of dollars of span that's shifting that's on the table a lot of competition now sees it too they're gonna go after it but at the end of the day you have customers that have that demand for things apps yeah and not a lot of budget increase at the same time this is a huge dynamic what's your goals you know I think that at a high level are top-down aggressive goals so that we want every single customer who uses our platform to have an outstanding customer experience and we want that outstanding customer experience in part is that their operational performance and their security are outstanding but also that it allows them to build and it build projects and initiatives that change their customer experience and allow them to be a sustainable successful business over a long period of time and then we also really want to be the technology infrastructure platform under all the applications that people build and they were realistic we know that that you know the market segments we address with infrastructure software hardware and data center services globally are trillions of dollars in the long term it won't only be us but we have that goal of wanting to serve every application and that requires not just the security operational performance but also a lot of functionality a lot of capability we have by far the most amount of capability out there and yet I would tell you we have three to five years of items on our roadmap that customers want us to add and that's just what we know today well and any underneath the covers you've been going through some transformation when we talked a couple years ago about how serverless is impacting things I've heard that that's actually in many ways glue behind the two pizza teams to work between organizations talk about how the internal transformations are happening how that impacts your discussions with customers that are going through that transformation well I mean there's a lot of a lot of the technology we build comes from things that we're doing ourselves you know and that we're learning ourselves it's kind of how we started thinking about microservices serverless - we saw the need we know we would have we would build all these functions that when some kind of object came into an object store we would spin up compute all those tasks would take like three or four hundred milliseconds then we spin it back down and yet we'd have to keep a cluster up in multiple availability zones because we needed that fault tolerance and it was we just said this is wasteful and that's part of how we came up with lambda and that you know when we were thinking about lambda people understandably said well if we build lambda and we build the serverless event-driven computing a lot of people who are keeping clusters of instances aren't going to use them anymore it's going to lead to less absolute revenue for us but we we have learned this lesson over the last 20 years at Amazon which is if it's something it's good for customers you're much better off cannibalizing yourself and doing the right thing for customers and being part of shaping something and I think if you look at the history of Technology you always build things and people say well that's gonna cannibalize this and people are gonna spend less money what really ends up happening is they spend spend less money per unit of compute but it allows them to do so much more that the ultimately long-term end up being you know more significant customers I mean you are like beating the drum all the time customers what they say we implement the roadmap I got that you guys have that playbook down that's been really successful for you yeah two years ago you told me machine learning was really important to you because your customers told what's the next tranche of importance for customers what's on top of mine now as you look at this reinvent kind of coming to a close replays tonight you had conversations your your tech a fleet you're running around doing speeches talking to customers what's that next hill from from my fist machine learning today there's so much I mean that's not it's not a soup question you know I think we're still in this in the very early days of machine learning it's not like most companies have mastered yet even though they're using it much more than they did in the past but you know I think machine learning for sure I think the edge for sure I think that we're optimistic about quantum computing even though I think it'll be a few years before it's really broadly useful we're very enthusiastic about robotics I think the amount of functions are going to be done by these robotic applications are much more expansive than people realize it doesn't mean humans won't have jobs they're just going to work on things that are more value-added I thought we're believers in augmented and virtual reality we're big believers and what's going to happen with voice and I'm also I think sometimes people get bored you know I think you're even bored with machine learning maybe already but yet people get bored with the things you've heard about but I think just what we've done with the chips you know in terms of giving people 40% better price performance in the latest generation of x86 processors it's pretty unbelievable and the difference in what people are going to be able to do or just look at big data I mean big date we haven't gotten through big data where people have totally solved it the amount of data that companies want to store process and analyze is exponentially larger than it was a few years ago and it will I think exponentially increase again in the next few years you need different tools the service I think we're not we're not for with machine learning we're excited to get started because we have all this data from the video and you guys got sage maker yeah we call it a stairway to machine learning heaven we start with the data move up what now guys are very sophisticated with what you do with technology and machine learning and there's so much I mean we're just kind of again in this early innings and I think that it was soaked before sage maker was so hard for everyday developers and data scientists to build models but the combination of sage maker and what's happened with thousands of companies standardizing on it the last two years Plus now sage maker studio giant leap forward we hope to use the data to transform our experience with our audience and we're on Amazon Cloud I really appreciate that and appreciate your support if we're with Amazon and Instant get that machine learning going a little faster for us a big that'll be better if you have requests so any I'm you talked about that you've got the customers that are builders and the customers that need simplification traditionally when you get into the you know the heart of the majority of adoption of something you really need to simplify that environment but when I think about the successful enterprise of the future they need to be builders yeah so has the model flipped if you know I normally would said enterprise want to pay for solutions because they don't have the skill set but if they're gonna succeed in this new economy they need to go through that transformation that yeah so I mean are we in just a total new era when we look back will this be different than some of these previous waves it's a it's a really good question Stu and I I don't think there's a simple answer to it I think that a lot of enterprises in some ways I think wish that they could just skip the low level building blocks and and only operate at that higher level abstraction it's why people were so excited by things like sage maker or code guru or Kendra or contact lens these are all services that allow them to just send us data and then run it on our models and get back the answers but I think one of the big trends that we see with enterprises is that they are taking more and more of their development in-house and they are wanting to operate more and more like startups I think that they admire what companies like Airbnb and Pinterest and slack and and you know Robin Hood and a whole bunch of those companies stripe have done and so when you know I think you go through these phases and errors where there are waves of success at different companies and then others want to follow that success and and replicate and so we see more and more enterprises saying we need to take back a lot of that development in-house and as they do that and as they add more developers those developers in most cases like to deal with the building blocks and they have a lot of ideas on how they can create us to creatively stitch them together on that point I want to just quickly ask you on Amazon versus other clouds because you made a comment to me in our interview about how hard it is to provide a service that to other people and it's hard to have a service that you're using yourself and turn that around and the most quoted line in my story was the compression algorithm there's no compression outliving for experience which to me is the diseconomies of scale for taking shortcuts yeah and so I think this is a really interesting point just add some color comments or I think this is a fundamental difference between AWS and others because you guys have a trajectory over the years of serving at scale customers wherever they are whatever they want to do now you got micro services it's even more complex that's hard yeah how about that I think there are a few elements to that notion of there's no compression algorithm I think the first thing to know about AWS which is different is we just come from a different heritage in a different background we sweep ran a business for a long time that was our sole business that was a consumer retail business that was very low margin and so we had to operate a very large scale given how many people were using us but also we had to run infrastructure services deep in the stack compute storage and database in reliable scalable data centers at very low costs and margins and so when you look at our our business it actually today I mean it's it's a higher margin business in our retail business the lower margin business and software companies but at real scale it's a it's a high-volume relatively low margin business and the way that you have to operate to be successful with those businesses and the things you have to think about and that DNA come from the type of operators that we have to be in our consumer retail business and there's nobody else in our space that does that you know the way that we think about cost the way we think about innovation and the data center and and I also think the way that we operate services and how long we've been operating services of the company it's a very different mindset than operating package software then you look at when you think about some of the issues and very large scale cloud you can't learn some of those lessons until you get two different elbows of the curve and scale and so what I was telling you is it's really different to run your own platform for your own users where you get to tell them exactly how it's going to be done but that's nothing really the way the real world works I mean we have millions of external customers who use us from every imaginable country and location whenever they want without any warning for lots of different use cases and they have lots of design patterns and we don't get to tell them what to do and so operating a cloud like that at a scale that's several times larger the next few providers combined is a very different endeavor and a very different operating rigor well you got to keep raising the bar you guys do a great job really impress again another tsunami of announcements in fact you had to spill the beans early with quantum the day before the event tight schedule I gotta ask you about the music festival because I think there's a really cool innovation it's the inaugural intersex conference yeah it's not part of replay which is the concert tonight right it's a whole new thing big music act you're a big music buff your daughter's an artist why did you do this what's the purpose what's your goal yeah it's an experiment I think that what's happened is that reinvent has gotten so big with 65,000 people here that to do the party which we do every year it's like a thirty five forty thousand person concert now which means you have to have a location that has multiple stages and you know we thought about it last year when we were watching it and we said we're kind of throwing like a four hour music festival right now there's multiple stages and it's quite expensive to set up that set for our partying we said well maybe we don't have to spend all that money for four hours in the rip it apart because actually the rent to keep those locations for another two days is much smaller than the cost of actually building multiple stages and so we we would try it this year we're very passionate about music as a business and I think we are I think our customers feel like we throw in a pretty good music party the last few years and we thought we were trying at a larger scale as an experiment and if you look at the economics the headliners real quick the Foo Fighters are headlining on Saturday night Anderson Park and the free Nashville free Nationals Brandi Carlile Shawn Mullins Willie Porter it's a good set Friday night it's back in Kacey Musgraves so it's it's a really great set of about 30 artists and we're hopeful that if we can build a great experience that people want to attend that we can do it it's scale and it might be something that you know both pays for itself and maybe helps pay for reinvent to overtime and you know I think that we're also thinking about it as not just a music concert and festival the reason we named it intersect is that we want an intersection of music genres and people and ethnicities and age groups and art and Technology all there together and this will be the first year we try it it's an experiment and we're really excited about I'm gone congratulations all your success and I want to thank you we've been seven years here at reinvent we've been documenting the history two sets now once-dead upstairs so appreciate a cube is part of reinvent you know you guys really are a part of the event and we really appreciate your coming here and I know people appreciate the content you create as well and we just launched cube 365 on Amazon Marketplace built on AWS so thanks for letting us cool build on the platform appreciate it thanks for having me guys Jesse the CEO of AWS here inside the cube it's our seventh year covering and documenting they're just the thunderous innovation that Amazon is doing they're really doing amazing work building out the new technologies here in the cloud computing world I'm John Force too many men be right back with more after this short break [Music]

>> Announcer: Live from San Juan, Puerto Rico. It's theCUBE, covering Block Chain Unbound, Brought to you by Blockchain Industries. >> Hello, everyone, welcome back to theCUBE's exclusive coverage in Puerto Rico for Block Chain Unbound. It's a global event, people from all around the world, from South Africa, Miami, Russia, San Francisco, New York, all around the world, talking about Blockchain cryptocurrency, the decentralized internet, and the future of Money, that's the killer app in Blockchain and cryptocurrency. I'm John Furrier, your host, my next guest is Scott Picken, who's the founder and CEO of Wealth Migrate Platform. Scott, thanks for coming on. >> Yeah, awesome John, thanks for having me. It's quite an exciting group of people here. >> We met last night, had a great conversation, I really liked some of the things that we were talking about, I wanted to bring you on because being in South Africa, where you're living and working, you have a unique perspective because you see the global landscape. So, I'm from Silicon Valley, we're here in Puerto Rico, America's got their view, the UK just announced a deal with Coinbase for essentially a license to convert funds into separate bank accounts through faster payment mechanisms, basically taking crypto and turning it into Fiat. Kind of a game changer. >> The one thing with the UK is they've been at the head of all of the different innovations over the last five to 10 years. They were right at the head in terms of crowdfunding and they're doing exactly the same in terms of now with the whole cryptospace. And it's actually quite interesting because when you take into account Brexit, they actually really need to do it because they want funds coming into the country, they want to be seen as the future of the banking market, et cetera, so it's actually really exciting. When you look around the world it's fascinating that I said this to you last night, that America really grew because Europe used to have all the controls. And so the capital basically left Europe and were in America and now it's happening 300 years later as America has all the controls and the capital's starting to go elsewhere. >> So America's turning into Europe. And so the potential is to bring, you don't have to say it, I'm an American and we're concerned about it. Americans are concerned that we don't want to be that old guard, like Europe was to America in the America days. So a new liberation's happening. UK's putting a stake in the ground, saying, "We want to get our mojo back," my words. >> Scott: sitting here in Puerto Rico. >> Yeah, they're in Puerto Rico. They're going to put a stake in the ground saying, "We're going to give you tax breaks 'til 2036." This is a money flow game right now. So you've been doing some pioneering work, what's your perspective, talk a little bit about some of the world dynamics that you see because, let's face it, this is the transfer of money, with crypto, it's happening at a massive scale, not just some underbelly boutique underground activities. This is front and center, mainstream, real money, real commerce. Your thoughts? >> I would take it a step back, actually. I think there's eight major macro trends that are all culminating at the same time. So the first one is in the education space, and the whole of education is changing, and it's really becoming gamification, and it's becoming learning while doing. So you don't learn and then go do something, you actually learn while you're doing it. The second one, for me, is the whole Blockchain. And what that's enabling people is getting democratization to wealth and access to assets, whether they're in their country or global assets, basically. The third thing that's really important is you've got the rise of the middle class. You know, a lot of people talk about the unbanked three billion, but what they don't realize is that 1.2 billion people joined the middle class. And they are primarily in the emerging world, they're in Africa, India, China. And what they want is, they want health, they want education, and they want access to wealth. Then you take into account what's happening in terms of collaborative investing. In the old days it was I do it on my own, you do it on your own, we sort of trust the financial industry. Now we're coming together, it's the power of the crowd. I could go on and on, that's just four of them, there's another four. They're all coming together and because this is happening is why we're seeing this metamorphosis and cryptocurrency is the catalyst on top of Blockchain that's allowing this to take place. >> Talk about some of the things that you've been advocating for, I know you were sharing a private story, maybe this may or may not be the right time to talk about it, but you put forth some pretty forthright concepts in memos and letters to folks, and no one will publish it. What are those views, because we've got the cameras rolling right now, share your vision. >> Again, I fundamentally believe that technology can solve grand challenges. And when you take our platform and what we're doing, we're effectively helping the 99% invest in commercial real estate like the top 1%. So what we were talking about last night was, I come from a country, South Africa, I was previously from Zimbabwe, and unfortunately for us is that in South Africa, they're talking now about taking away land without compensation. So land redistribution without compensation. Now, Einstein says that if you want to solve a problem, you can't solve it with the same reality that created the problem. And so I wrote a letter to the President, an open letter two weeks ago, and I said, listen. Why don't we do it differently? You're giving a person a piece of land in the middle of nowhere when they've never been a farmer will not help them get wealthy, I guarantee it. And if I'm wrong, let's go look at Zimbabwe. Which is a economic disaster. What about if we give them access to ownership of a good quality commercial asset that's earning a passive income? That is how you'll grow your wealth. And then add to that, Cape Town nearly became the first city, and it still could be the first city, that literally runs out of water. So why don't you go build a decent ionization plant in Cape Town with government money, allow people that you would give land to actually access to that asset and allow them to have the ownership? And that's sort of the concept, where you just think about it completely different. And you allow technology to actually give people what they want, which is wealth and prosperity for their family, and not just a farm in the middle of nowhere. >> And you're really addressing, I think, the incentive system combined with structural change. You talk about gamification earlier, this is kind of the dynamic. How important from an education standpoint, meaning educating stakeholders, old guard or existing governments, because you have this organic groundswell coming up of young people, people with vision that are older and more experienced like us, what's the formula, how do you get this ball rolling? >> So it's quite interesting, I get asked this question all the time and for us, in the first world, a lot of what we're talking about is it nice to have? It's sort of a bit of a game and if I can participate, but where I come from in the emerging world, it's a necessity. There are no other solutions. So if you live in South Africa or China or India and you want to get your money into a first world country like England, Australia, or America, it's very very difficult and virtually no one can do it. But it's a major problem, because you want world preservation, you want your Plan B, you want your children to be able to go to a first world university, et cetera, et cetera, et cetera. And so to answer your question, I think the way it will get solved is in communities where it's not a nice to have, it's a necessity. In terms of educating the old guard, I believe that what happens is you get groundswell, like literally when people really need a solution solved, they persuade governments and regulators to change and it's interesting, coming back to how we started the conversation, that's why smaller countries are often the ones to adopt the regulated new change and, more importantly, countries in emerging markets, whereas first world countries are trying to protect what they have and, unfortunately, the new world is about capital. And its capital flows. >> It's a choice between playing offense or defense, really in my mind it's a sports metaphor, whatever sport you like you know. We love the sports analogies. But this is what UK's doing, they're playing offense. And I think you're seeing other countries wanting to restructure themselves as digital nations because that's what the young people are expecting. So with that in mind, you have a global fabric here at this event, and it's just a microcosm of what we're seeing, which is outside the US, call it the little US bubble that we're living in, Silicon Valley, that's one case I'm wary of, but the growth outside the United States and even in Asia and south of the border, if you will, south of the equator, there's a ton of global action. What is, in your opinion, the few global things that are going on, that people should know about when it comes to how money's flowing and what they can do to take advantage of the trend rather than trying to hold it back. What do we do, is it get into the current? Ride the wave? What should people understand about the new global dynamic? >> So the first thing I would say is, I always laugh at this, but people don't understand how much innovation's going on in China. Like, go and understand WeChat to start off with. It is phenomenal, what is happening. The second thing for me is the global capital flows. When you consider how much capital is moving from the emerging world into the first world, primarily in real estate at the moment. And that's just the top 1% of the top 1%, you know, that's the people with 10, a hundred million dollars. But I've already said to you, there's 1.2 billion people coming into the emerging markets. In the middle class, they're going to want the same things. And so those capital flows are going to be going cross border. I also believe, with time, capital flows will be going from the first world into the emerging world in a safe way but wanting higher returns. >> So then the emerging world, the US has a shrinking middle class, but yet the emerging world has a growing middle class. That's going to attract new entrants. >> Exactly. >> Okay. >> Well, take into account China. Has China had a big impact on the global economy in the last 20 years? Yes or no? >> Yes. >> How many people are in the middle class in China? Plus or minus? >> Don't know. >> I've heard different reports from 200 million to 400 million, but whether it's 200 or 400-- >> It's more than it was 10 years ago. >> I know, but think about the impact that's had on the global economy. I'm not saying that this is 1.2 billion in the next 10 years, it's either a factor of five to eight, depending on which way you want to look at it. >> How much money, in your guesstimation, if you had to throw a dart at the board, order of magnitude, is flowing out of China with crypto into other assets? >> In the crypto space that's fascinating, because a lot of it is hard to tell, actually. In real estate last year alone, it was just short of 30 billion dollars went into commercial real estate from China. Now what's interesting is that a lot of that money is sort of gray, like no one actually knows where it's coming from, which is why China tightened it up so much. It's also why they tightened up the crypto side of things. Because a lot of people want to get their money out of the country and into first world economies, and that's why, in the emerging world, cryptocurrencies have been embraced more, actually, than in the first world. >> John: It's a faster way to move that money. >> Coming back to necessity. So in South Africa, in Zimbabwe, in China you pay more for Bitcoin than you do in America or Europe. I don't know if you know that. >> John: No, I don't know that. >> And by quite a lot. Like in Zimbabwe you pay nearly double. So a lot of people are making money by overcharging coins. They buy them in Europe, they sell them in South Africa, they sell them in Zimbabwe, they sell them in Nigeria. >> So the demand to move the money out of country is very high. >> Well, because they've got capital controls. So they have currency controls. So you're only allowed to move a certain amount of capital out of the country legally. So what happens now, you buy cryptocurrency and you can effectively invest in assets around the world. And you literally started off this conversation, right in the beginning, there's a democratization in terms of capital flows and what's happening, and people are going to put their capital where they want to. And governments, I believe, are not going to be able to control it by putting up controls, they're going to have to make their countries attractive so that the capital's flowing into the country, not out of the country. >> So what's your take on big multinational corporations that have capital structures, have equity positions, and it could be also growing venture-backed or private equity-based companies, they have capital structures, they have equity investors, in some case public, and privates, and unicorn valleys or whatnot, now moving to look at utility tokens as a way to get to a global gamification. So you have multiple securities, a utility, and in some cases a security token a real security. That seems to be a dynamic, are you seeing that on a global scale, are you seeing any activity there, we're seeing a little bit of movement around big companies trying to figure out how to play in crypto. >> From my experience, not a huge amount. I think that most people, they have a board, it's all around reputation, they got to meet the lawyers, the lawyers tell them, you're going to get crucified. And so from my experience, not a huge amount, it tends to be the small to medium enterprises that are prepared to go out and look at it. However, I will say from our personal business perspective, we built our entire company on a community. We've got shareholders all over the world and so for me, when it came to the crypto and the ICO market, that was just doing that more aggressively, effectively, and community-based companies are the future. So whether you're a Fortune 500 company or a start up, it's all about building the community, and I believe that whether it's utility token or security or a combination of the two, it provides an incredible vehicle to ultimately be the catalyst to a community. And if you're the catalyst to a community adding value, then you're going to build a company of value. >> And capture that value. So, Scott, I got to ask you about Wealth Migrate. Talk about your platform. First of all, thank you for sharing your perspective here on theCUBE. It's been fantastic to get that data out. What's your company about? Take a minute to explain what you guys are doing, your value proposition, state of the company, are you doing an ICO, have you had an ICO, what's the status of the company? >> So from Wealth Migrate's perspective, the platform went live in October, 2013, so we're a little over four years in now. We've effectively got members from 111 countries around the world and we've raised just short of 70 million dollars. All though the platform, all on Blockchain. We've facilitated real estate deals of over 485 million dollars and what I'm proudest of, actually, is that we've got a higher than 70% reinvestment rate. What we're doing is we're allowing the 99% to invest like the 1%, our minimum investment at the moment is $1,000, we're beta testing $100, and my dream is to get it to $1. You asked a little bit about the ICO. We built our platform on Blockchain not because of an ICO. Our number one challenge was trust. And ultimately Blockchain enabled us to solve the trust problem. The second thing for us is that my dream is to get it to $1 per person per investment. I want to solve the wealth gap. And I truly believe we can do it when we can allow anyone anywhere to invest in good quality assets. I can't do it with the current system, there's too many friction costs. With crypto and volume I can. >> Whether it's semantics, or education and/or hurdle rate on dollars, it's an interesting concept. You want to make the 99% invest like the 1%. Explain what that means, take a minute to explain that concept. I mean, some people are like, "Okay, I know what "the 1% is, there was a movement about that." So now you're talking about something pretty radical and interesting. What does that actually mean? I mean, empowering people to make more money? Unpack that concept. >> So let me ask you a question. Do you personally own a medical building? >> Do I own what? >> A medical building. >> No. >> Like a hospital, medical building. >> No. >> So it's 2009, I'm in Bondi Beach, Sydney and I meet two US dollar billionaires. I had helped about two and a half thousand people buy houses and apartments in England, Australia, America, and South Africa. And I sat with them and I said, "What are you investing in?" And they said, "Medical buildings." I said, "Why medical buildings?" And they said, "Well think about it. "No matter what happens in the global economy, "people need doctors." I was like, that makes sense. Secondly, they said, "Doctors never move." I was like, that makes sense. Thirdly, doctors are very good at being doctors, but they're not accountants. And so they sign long term, good, favorable leases. Now from a property perspective, real estate perspective, that's a no brainer. And I said to them, "How do I participate?" And they said it's really simple. It's for friends and family, there's eight people only, it's five million Australian dollars each. I was like, now there's the problem. That company today is over 700 million dollars, it's on the Australian Stock Exchange, and it's what I call financial exclusion. You and me don't own medical buildings. Since October 2013, we've enabled people to invest in medical buildings from $1,000. So the top 1% get wealthy by investing in better assets than the 99%. >> John: Because they have access. >> Because they've got access. >> John: And the cash. >> And the cash. But we've dropped the barriers to entry. Because you and I can participate now from $1,000 and I will get it to $1. >> So it's a combination of leveraging the asset based securitization with that opportunity by using a crowdsourcing kind of model, is that what you're thinking? >> So, effectively, and I'd suggest-- >> John: I'm oversimplifying it. >> No, no, 100%, I'd suggest everyone goes and looks up the term collaborative investing which is ultimately, it's a thing that's been going on for decades by very wealthy people on how to successfully invest. We've taken that but we've added a smart component. And why that's important is because in the past you needed 10, 50 million dollars to do collaborative investing, now you can do collaborative investing with $1,000. >> Yeah and what's beautiful is that you understand potentially whose reputation you're working with, you can move in herds, network effect kicks in, that's awesome. >> What gives me the greatest pleasure, I mean, children, my son is six years old, he's already investing. You know, most kids are playing Monopoly, he's playing real Monopoly, and so are adults. And what gives me the most pleasure and pride ever, and what I'm grateful for, is that we're changing people's lives. >> People talk about how to solve the welfare system, all kinds of things, you make people own something, or try to own something or trade, whether they make money or lose money, you learn from it, you're better for it. Here, you're providing a great service by opening the door, lowering the barriers to entry, to potentially wealth creation. >> Dude, I call it freedom. At the end of the day, if you're where you want to live, where you want to send your kids to school, how you want to retire, whether you want to donate to the church or whatever, I don't really care what you want, but I want you to have the freedom to be able to do it. And wealthy people get that freedom by investing in quality assets. And we're just allowing them to do that now. >> And the democratization is multiful, in this case you're creating a new economy model so the whole freedom, democracy aspect is in play. >> Well, I mean if you think about it, when you get into $1 per person, $1 will not change your life. But if you change your habits, you'll change your financial destiny. And so my philosophy is get it to $1, so that every single person can participate. And once you start to learn good habits around money and wealth, the rest just, it's a formula. >> It's a flywheel. Kickstand. Scott Picken, who's the founder and CEO of Wealth Migrate Platform from South Africa, formerly of Zimbabwe we learned today, great sharing the global perspective. Thanks for coming on theCUBE. Exclusive coverage from Puerto Rico, this is theCUBE, I'm John Furrier getting the signal here out of all the noise in the market, this is what we do, this is theCUBE's mission, to bring you the best content, best story from the best people, more coverage here in Puerto Rico. Day one of two days of coverage. After this short break, thanks for watching.

>> Announcer: Please welcome Vice President of Worldwide Marketing, Amazon Web Services, Ariel Kelman. (applause) (techno music) >> Good afternoon, everyone. Thank you for coming. I hope you guys are having a great day here. It is my pleasure to introduce to come up on stage here, the CEO of Amazon Web Services, Andy Jassy. (applause) (techno music) >> Okay. Let's get started. I have a bunch of questions here for you, Andy. >> Just like one of our meetings, Ariel. >> Just like one of our meetings. So, I thought I'd start with a little bit of a state of the state on AWS. Can you give us your quick take? >> Yeah, well, first of all, thank you, everyone, for being here. We really appreciate it. We know how busy you guys are. So, hope you're having a good day. You know, the business is growing really quickly. In the last financials, we released, in Q four of '16, AWS is a 14 billion dollar revenue run rate business, growing 47% year over year. We have millions of active customers, and we consider an active customer as a non-Amazon entity that's used the platform in the last 30 days. And it's really a very broad, diverse customer set, in every imaginable size of customer and every imaginable vertical business segment. And I won't repeat all the customers that I know Werner went through earlier in the keynote, but here are just some of the more recent ones that you've seen, you know NELL is moving their their digital and their connected devices, meters, real estate to AWS. McDonalds is re-inventing their digital platform on top of AWS. FINRA is moving all in to AWS, yeah. You see at Reinvent, Workday announced AWS was its preferred cloud provider, and to start building on top of AWS further. Today, in press releases, you saw both Dunkin Donuts and Here, the geo-spatial map company announced they'd chosen AWS as their provider. You know and then I think if you look at our business, we have a really large non-US or global customer base and business that continues to expand very dramatically. And we're also aggressively increasing the number of geographic regions in which we have infrastructure. So last year in 2016, on top of the broad footprint we had, we added Korea, India, and Canada, and the UK. We've announced that we have regions coming, another one in China, in Ningxia, as well as in France, as well as in Sweden. So we're not close to being done expanding geographically. And then of course, we continue to iterate and innovate really quickly on behalf of all of you, of our customers. I mean, just last year alone, we launched what we considered over 1,000 significant services and features. So on average, our customers wake up every day and have three new capabilities they can choose to use or not use, but at their disposal. You've seen it already this year, if you look at Chime, which is our new unified communication service. It makes meetings much easier to conduct, be productive with. You saw Connect, which is our new global call center routing service. If you look even today, you look at Redshift Spectrum, which makes it easy to query all your data, not just locally on disk in your data warehouse but across all of S3, or DAX, which puts a cash in front of DynamoDB, we use the same interface, or all the new features in our machine learning services. We're not close to being done delivering and iterating on your behalf. And I think if you look at that collection of things, it's part of why, as Gartner looks out at the infrastructure space, they estimate the AWS is several times the size business of the next 14 providers combined. It's a pretty significant market segment leadership position. >> You talked a lot about adopts in there, a lot of customers moving to AWS, migrating large numbers of workloads, some going all in on AWS. And with that as kind of backdrop, do you still see a role for hybrid as being something that's important for customers? >> Yeah, it's funny. The quick answer is yes. I think the, you know, if you think about a few years ago, a lot of the rage was this debate about private cloud versus what people call public cloud. And we don't really see that debate very often anymore. I think relatively few companies have had success with private clouds, and most are pretty substantially moving in the direction of building on top of clouds like AWS. But, while you increasingly see more and more companies every month announcing that they're going all in to the cloud, we will see most enterprises operate in some form of hybrid mode for the next number of years. And I think in the early days of AWS and the cloud, I think people got confused about this, where they thought that they had to make this binary decision to either be all in on the public cloud and AWS or not at all. And of course that's not the case. It's not a binary decision. And what we know many of our enterprise customers want is they want to be able to run the data centers that they're not ready to retire yet as seamlessly as they can alongside of AWS. And it's why we've built a lot of the capabilities we've built the last several years. These are things like PPC, which is our virtual private cloud, which allows you to cordon off a portion of our network, deploy resources into it and connect to it through VPN or Direct Connect, which is a private connection between your data centers and our regions or our storage gateway, which is a virtual storage appliance, or Identity Federation, or a whole bunch of capabilities like that. But what we've seen, even though the vast majority of the big hybrid implementations today are built on top of AWS, as more and more of the mainstream enterprises are now at the point where they're really building substantial cloud adoption plans, they've come back to us and they've said, well, you know, actually you guys have made us make kind of a binary decision. And that's because the vast majority of the world is virtualized on top of VMWare. And because VMWare and AWS, prior to a few months ago, had really done nothing to try and make it easy to use the VMWare tools that people have been using for many years seamlessly with AWS, customers were having to make a binary choice. Either they stick with the VMWare tools they've used for a while but have a really tough time integrating with AWS, or they move to AWS and they have to leave behind the VMWare tools they've been using. And it really was the impetus for VMWare and AWS to have a number of deep conversations about it, which led to the announcement we made late last fall of VMWare and AWS, which is going to allow customers who have been using the VMWare tools to manage their infrastructure for a long time to seamlessly be able to run those on top of AWS. And they get to do so as they move workloads back and forth and they evolve their hybrid implementation without having to buy any new hardware, which is a big deal for companies. Very few companies are looking to find ways to buy more hardware these days. And customers have been very excited about this prospect. We've announced that it's going to be ready in the middle of this year. You see companies like Amadeus and Merck and Western Digital and the state of Louisiana, a number of others, we've a very large, private beta and preview happening right now. And people are pretty excited about that prospect. So we will allow customers to run in the mode that they want to run, and I think you'll see a huge transition over the next five to 10 years. >> So in addition to hybrid, another question we get a lot from enterprises around the concept of lock-in and how they should think about their relationship with the vendor and how they should think about whether to spread the workloads across multiple infrastructure providers. How do you think about that? >> Well, it's a question we get a lot. And Oracle has sure made people care about that issue. You know, I think people are very sensitive about being locked in, given the experience that they've had over the last 10 to 15 years. And I think the reality is when you look at the cloud, it really is nothing like being locked into something like Oracle. The APIs look pretty similar between the various providers. We build an open standard, it's like Linux and MySQL and Postgres. All the migration tools that we build allow you to migrate in or out of AWS. It's up to customers based on how they want to run their workload. So it is much easier to move away from something like the cloud than it is from some of the old software services that has created some of this phobia. But I think when you look at most CIOs, enterprise CIOs particularly, as they think about moving to the cloud, many of them started off thinking that they, you know, very well might split their workloads across multiple cloud providers. And I think when push comes to shove, very few decide to do so. Most predominately pick an infrastructure provider to run their workloads. And the reason that they don't split it across, you know, pretty evenly across clouds is a few reasons. Number one, if you do so, you have to standardize in the lowest common denominator. And these platforms are in radically different stages at this point. And if you look at something like AWS, it has a lot more functionality than anybody else by a large margin. And we're also iterating more quickly than you'll find from the other providers. And most folks don't want to tie the hands of their developers behind their backs in the name of having the ability of splitting it across multiple clouds, cause they actually are, in most of their spaces, competitive, and they have a lot of ideas that they want to actually build and invent on behalf of their customers. So, you know, they don't want to actually limit their functionality. It turns out the second reason is that they don't want to force their development teams to have to learn multiple platforms. And most development teams, if any of you have managed multiple stacks across different technologies, and many of us have had that experience, it's a pain in the butt. And trying to make a shift from what you've been doing for the last 30 years on premises to the cloud is hard enough. But then forcing teams to have to get good at running across two or three platforms is something most teams don't relish, and it's wasteful of people's time, it's wasteful of natural resources. That's the second thing. And then the third reason is that you effectively diminish your buying power because all of these cloud providers have volume discounts, and then you're splitting what you buy across multiple providers, which gives you a lower amount you buy from everybody at a worse price. So when most CIOs and enterprises look at this carefully, they don't actually end up splitting it relatively evenly. They predominately pick a cloud provider. Some will just pick one. Others will pick one and then do a little bit with a second, just so they know they can run with a second provider, in case that relationship with the one they choose to predominately run with goes sideways in some fashion. But when you really look at it, CIOs are not making that decision to split it up relatively evenly because it makes their development teams much less capable and much less agile. >> Okay, let's shift gears a little bit, talk about a subject that's on the minds of not just enterprises but startups and government organizations and pretty much every organization we talk to. And that's AI and machine learning. Reinvent, we introduced our Amazon AI services and just this morning Werner announced the general availability of Amazon Lex. So where are we overall on machine learning? >> Well it's a hugely exciting opportunity for customers, and I think, we believe it's exciting for us as well. And it's still in the relatively early stages, if you look at how people are using it, but it's something that we passionately believe is going to make a huge difference in the world and a huge difference with customers, and that we're investing a pretty gigantic amount of resource and capability for our customers. And I think the way that we think about, at a high level, the machine learning and deep learning spaces are, you know, there's kind of three macro layers of the stack. I think at that bottom layer, it's generally for the expert machine learning practitioners, of which there are relatively few in the world. It's a scarce resource relative to what I think will be the case in five, 10 years from now. And these are folks who are comfortable working with deep learning engines, know how to build models, know how to tune those models, know how to do inference, know how to get that data from the models into production apps. And for that group of people, if you look at the vast majority of machine learning and deep learning that's being done in the cloud today, it's being done on top of AWS, are P2 instances, which are optimized for deep learning and our deep learning AMIs, that package, effectively the deep learning engines and libraries inside those AMIs. And you see companies like Netflix, Nvidia, and Pinterest and Stanford and a whole bunch of others that are doing significant amounts of machine learning on top of those optimized instances for machine learning and the deep learning AMIs. And I think that you can expect, over time, that we'll continue to build additional capabilities and tools for those expert practitioners. I think we will support and do support every single one of the deep learning engines on top of AWS, and we have a significant amount of those workloads with all those engines running on top of AWS today. We also are making, I would say, a disproportionate investment of our own resources and the MXNet community just because if you look at running deep learning models once you get beyond a few GPUs, it's pretty difficult to have those scale as you get into the hundreds of GPUs. And most of the deep learning engines don't scale very well horizontally. And so what we've found through a lot of extensive testing, cause remember, Amazon has thousands of deep learning experts inside the company that have built very sophisticated deep learning capabilities, like the ones you see in Alexa, we have found that MXNet scales the best and almost linearly, as we continue to add nodes, as we continue to horizontally scale. So we have a lot of investment at that bottom layer of the stack. Now, if you think about most companies with developers, it's still largely inaccessible to them to do the type of machine learning and deep learning that they'd really like to do. And that's because the tools, I think, are still too primitive. And there's a number of services out there, we built one ourselves in Amazon Machine Learning that we have a lot of customers use, and yet I would argue that all of those services, including our own, are still more difficult than they should be for everyday developers to be able to build machine learning and access machine learning and deep learning. And if you look at the history of what AWS has done, in every part of our business, and a lot of what's driven us, is trying to democratize technologies that were really only available and accessible before to a select, small number of companies. And so we're doing a lot of work at what I would call that middle layer of the stack to get rid of a lot of the muck associated with having to do, you know, building the models, tuning the models, doing the inference, figuring how to get the data into production apps, a lot of those capabilities at that middle layer that we think are really essential to allow deep learning and machine learning to reach its full potential. And then at the top layer of the stack, we think of those as solutions. And those are things like, pass me an image and I'll tell you what that image is, or show me this face, does it match faces in this group of faces, or pass me a string of text and I'll give you an mpg file, or give me some words and what your intent is and then I'll be able to return answers that allow people to build conversational apps like the Lex technology. And we have a whole bunch of other services coming in that area, atop of Lex and Polly and Recognition, and you can imagine some of those that we've had to use in Amazon over the years that we'll continue to make available for you, our customers. So very significant level of investment at all three layers of that stack. We think it's relatively early days in the space but have a lot of passion and excitement for that. >> Okay, now for ML and AI, we're seeing customers wanting to load in tons of data, both to train the models and to actually process data once they've built their models. And then outside of ML and AI, we're seeing just as much demand to move in data for analytics and traditional workloads. So as people are looking to move more and more data to the cloud, how are we thinking about making it easier to get data in? >> It's a great question. And I think it's actually an often overlooked question because a lot of what gets attention with customers is all the really interesting services that allow you to do everything from compute and storage and database and messaging and analytics and machine learning and AI. But at the end of the day, if you have a significant amount of data already somewhere else, you have to get it into the cloud to be able to take advantage of all these capabilities that you don't have on premises. And so we have spent a disproportionate amount of focus over the last few years trying to build capabilities for our customers to make this easier. And we have a set of capabilities that really is not close to matched anywhere else, in part because we have so many customers who are asking for help in this area that it's, you know, that's really what drives what we build. So of course, you could use the good old-fashioned wire to send data over the internet. Increasingly, we find customers that are trying to move large amounts of data into S3, is using our S3 transfer acceleration service, which basically uses our points of presence, or POPs, all over the world to expedite delivery into S3. You know, a few years ago, we were talking to a number of companies that were looking to make big shifts to the cloud, and they said, well, I need to move lots of data that just isn't viable for me to move it over the wire, given the connection we can assign to it. It's why we built Snowball. And so we launched Snowball a couple years ago, which is really, it's a 50 terabyte appliance that is encrypted, the data's encrypted three different ways, and you ingest the data from your data center into Snowball, it has a Kindle connected to it, it allows you to, you know, that makes sure that you send it to the right place, and you can also track the progress of your high-speed ingestion into our data centers. And when we first launched Snowball, we launched it at Reinvent a couple years ago, I could not believe that we were going to order as many Snowballs to start with as the team wanted to order. And in fact, I reproached the team and I said, this is way too much, why don't we first see if people actually use any of these Snowballs. And so the team thankfully didn't listen very carefully to that, and they really only pared back a little bit. And then it turned out that we, almost from the get-go, had ordered 10X too few. And so this has been something that people have used in a very broad, pervasive way all over the world. And last year, at the beginning of the year, as we were asking people what else they would like us to build in Snowball, customers told us a few things that were pretty interesting to us. First, one that wasn't that surprising was they said, well, it would be great if they were bigger, you know, if instead of 50 terabytes it was more data I could store on each device. Then they said, you know, one of the problems is when I load the data onto a Snowball and send it to you, I have to still keep my local copy on premises until it's ingested, cause I can't risk losing that data. So they said it would be great if you could find a way to provide clustering, so that I don't have to keep that copy on premises. That was pretty interesting. And then they said, you know, there's some of that data that I'd actually like to be loading synchronously to S3, and then, or some things back from S3 to that data that I may want to compare against. That was interesting, having that endpoint. And then they said, well, we'd really love it if there was some compute on those Snowballs so I can do analytics on some relatively short-term signals that I want to take action on right away. Those were really the pieces of feedback that informed Snowball Edge, which is the next version of Snowball that we launched, announced at Reinvent this past November. So it has, it's a hundred-terabyte appliance, still the same level of encryption, and it has clustering so that you don't have to keep that copy of the data local. It allows you to have an endpoint to S3 to synchronously load data back and forth, and then it has a compute inside of it. And so it allows customers to use these on premises. I'll give you a good example. GE is using these for their wind turbines. And they collect all kinds of data from those turbines, but there's certain short-term signals they want to do analytics on in as close to real time as they can, and take action on those. And so they use that compute to do the analytics and then when they fill up that Snowball Edge, they detach it and send it back to AWS to do broad-scale analytics in the cloud and then just start using an additional Snowball Edge to capture that short-term data and be able to do those analytics. So Snowball Edge is, you know, we just launched it a couple months ago, again, amazed at the type of response, how many customers are starting to deploy those all over the place. I think if you have exabytes of data that you need to move, it's not so easy. An exabyte of data, if you wanted to move from on premises to AWS, would require 10,000 Snowball Edges. Those customers don't want to really manage a fleet of 10,000 Snowball Edges if they don't have to. And so, we tried to figure out how to solve that problem, and it's why we launched Snowmobile back at Reinvent in November, which effectively, it's a hundred-petabyte container on a 45-foot trailer that we will take a truck and bring out to your facility. It comes with its own power and its own network fiber that we plug in to your data center. And if you want to move an exabyte of data over a 10 gigabit per second connection, it would take you 26 years. But using 10 Snowmobiles, it would take you six months. So really different level of scale. And you'd be surprised how many companies have exabytes of data at this point that they want to move to the cloud to get all those analytics and machine learning capabilities running on top of them. Then for streaming data, as we have more and more companies that are doing real-time analytics of streaming data, we have Kinesis, where we built something called the Kinesis Firehose that makes it really simple to stream all your real-time data. We have a storage gateway for companies that want to keep certain data hot, locally, and then asynchronously be loading the rest of their data to AWS to be able to use in different formats, should they need it as backup or should they choose to make a transition. So it's a very broad set of storage capabilities. And then of course, if you've moved a lot of data into the cloud or into anything, you realize that one of the hardest parts that people often leave to the end is ETL. And so we have announced an ETL service called Glue, which we announced at Reinvent, which is going to make it much easier to move your data, be able to find your data and map your data to different locations and do ETL, which of course is hugely important as you're moving large amounts. >> So we've talked a lot about moving things to the cloud, moving applications, moving data. But let's shift gears a little bit and talk about something not on the cloud, connected devices. >> Yeah. >> Where do they fit in and how do you think about edge? >> Well, you know, I've been working on AWS since the start of AWS, and we've been in the market for a little over 11 years at this point. And we have encountered, as I'm sure all of you have, many buzzwords. And of all the buzzwords that everybody has talked about, I think I can make a pretty strong argument that the one that has delivered fastest on its promise has been IOT and connected devices. Just amazing to me how much is happening at the edge today and how fast that's changing with device manufacturers. And I think that if you look out 10 years from now, when you talk about hybrid, I think most companies, majority on premise piece of hybrid will not be servers, it will be connected devices. There are going to be billions of devices all over the place, in your home, in your office, in factories, in oil fields, in agricultural fields, on ships, in cars, in planes, everywhere. You're going to have these assets that sit at the edge that companies are going to want to be able to collect data on, do analytics on, and then take action. And if you think about it, most of these devices, by their very nature, have relatively little CPU and have relatively little disk, which makes the cloud disproportionately important for them to supplement them. It's why you see most of the big, successful IOT applications today are using AWS to supplement them. Illumina has hooked up their genome sequencing to AWS to do analytics, or you can look at Major League Baseball Statcast is an IOT application built on top of AWS, or John Deer has over 200,000 telematically enabled tractors that are collecting real-time planting conditions and information that they're doing analytics on and sending it back to farmers so they can figure out where and how to optimally plant. Tata Motors manages their truck fleet this way. Phillips has their smart lighting project. I mean, there're innumerable amounts of these IOT applications built on top of AWS where the cloud is supplementing the device's capability. But when you think about these becoming more mission-critical applications for companies, there are going to be certain functions and certain conditions by which they're not going to want to connect back to the cloud. They're not going to want to take the time for that round trip. They're not going to have connectivity in some cases to be able to make a round trip to the cloud. And what they really want is customers really want the same capabilities they have on AWS, with AWS IOT, but on the devices themselves. And if you've ever tried to develop on these embedded devices, it's not for mere mortals. It's pretty delicate and it's pretty scary and there's a lot of archaic protocols associated with it, pretty tough to do it all and to do it without taking down your application. And so what we did was we built something called Greengrass, and we announced it at Reinvent. And Greengrass is really like a software module that you can effectively have inside your device. And it allows developers to write lambda functions, it's got lambda inside of it, and it allows customers to write lambda functions, some of which they want to run in the cloud, some of which they want to run on the device itself through Greengrass. So they have a common programming model to build those functions, to take the signals they see and take the actions they want to take against that, which is really going to help, I think, across all these IOT devices to be able to be much more flexible and allow the devices and the analytics and the actions you take to be much smarter, more intelligent. It's also why we built Snowball Edge. Snowball Edge, if you think about it, is really a purpose-built Greengrass device. We have Greengrass, it's inside of the Snowball Edge, and you know, the GE wind turbine example is a good example of that. And so it's to us, I think it's the future of what the on-premises piece of hybrid's going to be. I think there're going to be billions of devices all over the place and people are going to want to interact with them with a common programming model like they use in AWS and the cloud, and we're continuing to invest very significantly to make that easier and easier for companies. >> We've talked about several feature directions. We talked about AI, machine learning, the edge. What are some of the other areas of investment that this group should care about? >> Well there's a lot. (laughs) That's not a suit question, Ariel. But there's a lot. I think, I'll name a few. I think first of all, as I alluded to earlier, we are not close to being done expanding geographically. I think virtually every tier-one country will have an AWS region over time. I think many of the emerging countries will as well. I think the database space is an area that is radically changing. It's happening at a faster pace than I think people sometimes realize. And I think it's good news for all of you. I think the database space over the last few decades has been a lonely place for customers. I think that they have felt particularly locked into companies that are expensive and proprietary and have high degrees of lock-in and aren't so customer-friendly. And I think customers are sick of it. And we have a relational database service that we launched many years ago and has many flavors that you can run. You can run MySQL, you can run Postgres, you can run MariaDB, you can run SQLServer, you can run Oracle. And what a lot of our customers kept saying to us was, could you please figure out a way to have a database capability that has the performance characteristics of the commercial-grade databases but the customer-friendly and pricing model of the more open engines like the MySQL and Postgres and MariaDB. What you do on your own, we do a lot of it at Amazon, but it's hard, I mean, it takes a lot of work and a lot of tuning. And our customers really wanted us to solve that problem for them. And it's why we spent several years building Aurora, which is our own database engine that we built, but that's fully compatible with MySQL and with Postgres. It's at least as fault tolerant and durable and performant as the commercial-grade databases, but it's a tenth of the cost of those. And it's also nice because if it turns out that you use Aurora and you decide for whatever reason you don't want to use Aurora anymore, because it's fully compatible with MySQL and Postgres, you just dump it to the community versions of those, and off you are. So there's really hardly any transition there. So that is the fastest-growing service in the history of AWS. I'm amazed at how quickly it's grown. I think you may have heard earlier, we've had 23,000 database migrations just in the last year or so. There's a lot of pent-up demand to have database freedom. And we're here to help you have it. You know, I think on the analytic side, it's just never been easier and less expensive to collect, store, analyze, and share data than it is today. Part of that has to do with the economics of the cloud. But a lot of it has to do with the really broad analytics capability that we provide you. And it's a much broader capability than you'll find elsewhere. And you know, you can manage Hadoop and Spark and Presto and Hive and Pig and Yarn on top of AWS, or we have a managed elastic search service, and you know, of course we have a very high scale, very high performing data warehouse in Redshift, that just got even more performant with Spectrum, which now can query across all of your S3 data, and of course you have Athena, where you can query S3 directly. We have a service that allows you to do real-time analytics of streaming data in Kinesis. We have a business intelligence service in QuickSight. We have a number of machine learning capabilities I talked about earlier. It's a very broad array. And what we find is that it's a new day in analytics for companies. A lot of the data that companies felt like they had to throw away before, either because it was too expensive to hold or they didn't really have the tools accessible to them to get the learning from that data, it's a totally different day today. And so we have a pretty big investment in that space, I mentioned Glue earlier to do ETL on all that data. We have a lot more coming in that space. I think compute, super interesting, you know, I think you will find, I think we will find that companies will use full instances for many, many years and we have, you know, more than double the number of instances than you'll find elsewhere in every imaginable shape and size. But I would also say that the trend we see is that more and more companies are using smaller units of compute, and it's why you see containers becoming so popular. We have a really big business in ECS. And we will continue to build out the capability there. We have companies really running virtually every type of container and orchestration and management service on top of AWS at this point. And then of course, a couple years ago, we pioneered the event-driven serverless capability in compute that we call Lambda, which I'm just again, blown away by how many customers are using that for everything, in every way. So I think the basic unit of compute is continuing to get smaller. I think that's really good for customers. I think the ability to be serverless is a very exciting proposition that we're continuing to to fulfill that vision that we laid out a couple years ago. And then, probably, the last thing I'd point out right now is, I think it's really interesting to see how the basic procurement of software is changing. In significant part driven by what we've been doing with our Marketplace. If you think about it, in the old world, if you were a company that was buying software, you'd have to go find bunch of the companies that you should consider, you'd have to have a lot of conversations, you'd have to talk to a lot of salespeople. Those companies, by the way, have to have a big sales team, an expensive marketing budget to go find those companies and then go sell those companies and then both companies engage in this long tap-dance around doing an agreement and the legal terms and the legal teams and it's just, the process is very arduous. Then after you buy it, you have to figure out how you're going to actually package it, how you're deploy to infrastructure and get it done, and it's just, I think in general, both consumers of software and sellers of software really don't like the process that's existed over the last few decades. And then you look at AWS Marketplace, and we have 35 hundred product listings in there from 12 hundred technology providers. If you look at the number of hours, that software that's been running EC2 just in the last month alone, it's several hundred million hours, EC2 hours, of that software being run on top of our Marketplace. And it's just completely changing how software is bought and procured. I think that if you talk to a lot of the big sellers of software, like Splunk or Trend Micro, there's a whole number of them, they'll tell you it totally changes their ability to be able to sell. You know, one of the things that really helped AWS in the early days and still continues to help us, is that we have a self-service model where we don't actually have to have a lot of people talk to every customer to get started. I think if you're a seller of software, that's very appealing, to allow people to find your software and be able to buy it. And if you're a consumer, to be able to buy it quickly, again, without the hassle of all those conversations and the overhead associated with that, very appealing. And I think it's why the marketplace has just exploded and taken off like it has. It's also really good, by the way, for systems integrators, who are often packaging things on top of that software to their clients. This makes it much easier to build kind of smaller catalogs of software products for their customers. I think when you layer on top of that the capabilities that we've announced to make it easier for SASS providers to meter and to do billing and to do identity is just, it's a very different world. And so I think that also is very exciting, both for companies and customers as well as software providers. >> We certainly touched on a lot here. And we have a lot going on, and you know, while we have customers asking us a lot about how they can use all these new services and new features, we also tend to get a lot of questions from customers on how we innovate so quickly, and they can think about applying some of those lessons learned to their own businesses. >> So you're asking how we're able to innovate quickly? >> Mmm hmm. >> I think there's a few things that have helped us, and it's different for every company. But some of these might be helpful. I'll point to a few. I think the first thing is, I think we disproportionately index on hiring builders. And we think of builders as people who are inventors, people who look at different customer experiences really critically, are honest about what's flawed about them, and then seek to reinvent them. And then people who understand that launch is the starting line and not the finish line. There's very little that any of us ever built that's a home run right out of the gate. And so most things that succeed take a lot of listening to customers and a lot of experimentation and a lot of iterating before you get to an equation that really works. So the first thing is who we hire. I think the second thing is how we organize. And we have, at Amazon, long tried to organize into as small and separable and autonomous teams as we can, that have all the resources in those teams to own their own destiny. And so for instance, the technologists and the product managers are part of the same team. And a lot of that is because we don't want the finger pointing that goes back and forth between the teams, and if they're on the same team, they focus all their energy on owning it together and understanding what customers need from them, spending a disproportionate amount of time with customers, and then they get to own their own roadmaps. One of the reasons we don't publish a 12 to 18 month roadmap is we want those teams to have the freedom, in talking to customers and listening to what you tell us matters, to re-prioritize if there are certain things that we assumed mattered more than it turns out it does. So, you know I think that the way that we organize is the second piece. I think a third piece is all of our teams get to use the same AWS building blocks that all of you get to use, which allow you to move much more quickly. And I think one of the least told stories about Amazon over the last five years, in part because people have gotten interested in AWS, is people have missed how fast our consumer business at Amazon has iterated. Look at the amount of invention in Amazon's consumer business. And they'll tell you that a big piece of that is their ability to use the AWS building blocks like they do. I think a fourth thing is many big companies, as they get larger, what starts to happen is what people call the institutional no, which is that leaders walk into meetings on new ideas looking to find ways to say no, and not because they're ill intended but just because they get more conservative or they have a lot on their plate or things are really managed very centrally, so it's hard to imagine adding more to what you're already doing. At Amazon, it's really the opposite, and in part because of the way we're organized in such a decoupled, decentralized fashion, and in part because it's just part of our DNA. When the leaders walk into a meeting, they are looking for ways to say yes. And we don't say yes to everything, we have a lot of proposals. But we say yes to a lot more than I think virtually any other company on the planet. And when we're having conversations with builders who are proposing new ideas, we're in a mode where we're trying to problem-solve with them to get to yes, which I think is really different. And then I think the last thing is that we have mechanisms inside the company that allow us to make fast decisions. And if you want a little bit more detail, you should read our founder and CEO Jeff Bezos's shareholder letter, which just was released. He talks about the fast decision-making that happens inside the company. It's really true. We make fast decisions and we're willing to fail. And you know, we sometimes talk about how we're working on several of our next biggest failures, and we hope that most of the things we're doing aren't going to fail, but we know, if you're going to push the envelope and if you're going to experiment at the rate that we're trying to experiment, to find more pillars that allow us to do more for customers and allow us to be more relevant, you are going to fail sometimes. And you have to accept that, and you have to have a way of evaluating people that recognizes the inputs, meaning the things that they actually delivered as opposed to the outputs, cause on new ventures, you don't know what the outputs are going to be, you don't know consumers or customers are going to respond to the new thing you're trying to build. So you have to be able to reward employees on the inputs, you have to have a way for them to continue to progress and grow in their career even if they work on something didn't work. And you have to have a way of thinking about, when things don't work, how do I take the technology that I built as part of that, that really actually does work, but I didn't get it right in the form factor, and use it for other things. And I think that when you think about a culture like Amazon, that disproportionately hires builders, organizes into these separable, autonomous teams, and allows them to use building blocks to move fast, and has a leadership team that's looking to say yes to ideas and is willing to fail, you end up finding not only do you do more inventing but you get the people at every level of the organization spending their free cycles thinking about new ideas because it actually pays to think of new ideas cause you get a shot to try it. And so that has really helped us and I think most of our customers who have made significant shifts to AWS and the cloud would argue that that's one of the big transformational things they've seen in their companies as well. >> Okay. I want to go a little bit deeper on the subject of culture. What are some of the things that are most unique about the AWS culture that companies should know about when they're looking to partner with us? >> Well, I think if you're making a decision on a predominant infrastructure provider, it's really important that you decide that the culture of the company you're going to partner with is a fit for yours. And you know, it's a super important decision that you don't want to have to redo multiple times cause it's wasted effort. And I think that, look, I've been at Amazon for almost 20 years at this point, so I have obviously drank the Kool Aid. But there are a few things that I think are truly unique about Amazon's culture. I'll talk about three of them. The first is I think that we are unusually customer-oriented. And I think a lot of companies talk about being customer-oriented, but few actually are. I think most of the big technology companies truthfully are competitor-focused. They kind of look at what competitors are doing and then they try to one-up one another. You have one or two of them that I would say are product-focused, where they say, hey, it's great, you Mr. and Mrs. Customer have ideas on a product, but leave that to the experts, and you know, you'll like the products we're going to build. And those strategies can be good ones and successful ones, they're just not ours. We are driven by what customers tell us matters to them. We don't build technology for technology's sake, we don't become, you know, smitten by any one technology. We're trying to solve real problems for our customers. 90% of what we build is driven by what you tell us matters. And the other 10% is listening to you, and even if you can't articulate exactly what you want, trying to read between the lines and invent on your behalf. So that's the first thing. Second thing is that we are pioneers. We really like to invent, as I was talking about earlier. And I think most big technology companies at this point have either lost their will or their DNA to invent. Most of them acquire it or fast follow. And again, that can be a successful strategy. It's just not ours. I think in this day and age, where we're going through as big a shift as we are in the cloud, which is the biggest technology shift in our lifetime, as dynamic as it is, being able to partner with a company that has the most functionality, it's iterating the fastest, has the most customers, has the largest ecosystem of partners, has SIs and ISPs, that has had a vision for how all these pieces fit together from the start, instead of trying to patch them together in a following act, you have a big advantage. I think that the third thing is that we're unusually long-term oriented. And I think that you won't ever see us show up at your door the last day of a quarter, the last day of a year, trying to harass you into doing some kind of deal with us, not to be heard from again for a couple years when we either audit you or try to re-up you for a deal. That's just not the way that we will ever operate. We are trying to build a business, a set of relationships, that will outlast all of us here. And I think something that always ties it together well is this trusted advisor capability that we have inside our support function, which is, you know, we look at dozens of programmatic ways that our customers are using the platform and reach out to you if you're doing something we think's suboptimal. And one of the things we do is if you're not fully utilizing resources, or hardly, or not using them at all, we'll reach out and say, hey, you should stop paying for this. And over the last couple of years, we've sent out a couple million of these notifications that have led to actual annualized savings for customers of 350 million dollars. So I ask you, how many of your technology partners reach out to you and say stop spending money with us? To the tune of 350 million dollars lost revenue per year. Not too many. And I think when we first started doing it, people though it was gimmicky, but if you understand what I just talked about with regard to our culture, it makes perfect sense. We don't want to make money from customers unless you're getting value. We want to reinvent an experience that we think has been broken for the prior few decades. And then we're trying to build a relationship with you that outlasts all of us, and we think the best way to do that is to provide value and do right by customers over a long period of time. >> Okay, keeping going on the culture subject, what about some of the quirky things about Amazon's culture that people might find interesting or useful? >> Well there are a lot of quirky parts to our culture. And I think any, you know lots of companies who have strong culture will argue they have quirky pieces but I think there's a few I might point to. You know, I think the first would be the first several years I was with the company, I guess the first six years or so I was at the company, like most companies, all the information that was presented was via PowerPoint. And we would find that it was a very inefficient way to consume information. You know, you were often shaded by the charisma of the presenter, sometimes you would overweight what the presenters said based on whether they were a good presenter. And vice versa. You would very rarely have a deep conversation, cause you have no room on PowerPoint slides to have any depth. You would interrupt the presenter constantly with questions that they hadn't really thought through cause they didn't think they were going to have to present that level of depth. You constantly have the, you know, you'd ask the question, oh, I'm going to get to that in five slides, you want to do that now or you want to do that in five slides, you know, it was just maddening. And we would often find that most of the meetings required multiple meetings. And so we made a decision as a company to effectively ban PowerPoints as a communication vehicle inside the company. Really the only time I do PowerPoints is at Reinvent. And maybe that shows. And what we found is that it's a much more substantive and effective and time-efficient way to have conversations because there is no way to fake depth in a six-page narrative. So what we went to from PowerPoint was six-page narrative. You can write, have as much as you want in the appendix, but you have to assume nobody will read the appendices. Everything you have to communicate has to be done in six pages. You can't fake depth in a six-page narrative. And so what we do is we all get to the room, we spend 20 minutes or so reading the document so it's fresh in everybody's head. And then where we start the conversation is a radically different spot than when you're hearing a presentation one kind of shallow slide at a time. We all start the conversation with a fair bit of depth on the topic, and we can really hone in on the three or four issues that typically matter in each of these conversations. So we get to the heart of the matter and we can have one meeting on the topic instead of three or four. So that has been really, I mean it's unusual and it takes some time getting used to but it is a much more effective way to pay attention to the detail and have a substantive conversation. You know, I think a second thing, if you look at our working backwards process, we don't write a lot of code for any of our services until we write and refine and decide we have crisp press release and frequently asked question, or FAQ, for that product. And in the press release, what we're trying to do is make sure that we're building a product that has benefits that will really matter. How many times have we all gotten to the end of products and by the time we get there, we kind of think about what we're launching and think, this is not that interesting. Like, people are not going to find this that compelling. And it's because you just haven't thought through and argued and debated and made sure that you drew the line in the right spot on a set of benefits that will really matter to customers. So that's why we use the press release. The FAQ is to really have the arguments up front about how you're building the product. So what technology are you using? What's the architecture? What's the customer experience? What's the UI look like? What's the pricing dimensions? Are you going to charge for it or not? All of those decisions, what are people going to be most excited about, what are people going to be most disappointed by. All those conversations, if you have them up front, even if it takes you a few times to go through it, you can just let the teams build, and you don't have to check in with them except on the dates. And so we find that if we take the time up front we not only get the products right more often but the teams also deliver much more quickly and with much less churn. And then the third thing I'd say that's kind of quirky is it is an unusually truth-seeking culture at Amazon. I think we have a leadership principle that we say have backbone, disagree, and commit. And what it means is that we really expect people to speak up if they believe that we're headed down a path that's wrong for customers, no matter who is advancing it, what level in the company, everybody is empowered and expected to speak up. And then once we have the debate, then we all have to pull the same way, even if it's a different way than you were advocating. And I think, you always hear the old adage of where, two people look at a ceiling and one person says it's 14 feet and the other person says, it's 10 feet, and they say, okay let's compromise, it's 12 feet. And of course, it's not 12 feet, there is an answer. And not all things that we all consider has that black and white answer, but most things have an answer that really is more right if you actually assess it and debate it. And so we have an environment that really empowers people to challenge one another and I think it's part of why we end up getting to better answers, cause we have that level of openness and rigor. >> Okay, well Andy, we have time for one more question. >> Okay. >> So other than some of the things you've talked about, like customer focus, innovation, and long-term orientation, what is the single most important lesson that you've learned that is really relevant to this audience and this time we're living in? >> There's a lot. But I'll pick one. I would say I'll tell a short story that I think captures it. In the early days at Amazon, our sole business was what we called an owned inventory retail business, which meant we bought the inventory from distributors or publishers or manufacturers, stored it in our own fulfillment centers and shipped it to customers. And around the year 1999 or 2000, this third party seller model started becoming very popular. You know, these were companies like Half.com and eBay and folks like that. And we had a really animated debate inside the company about whether we should allow third party sellers to sell on the Amazon site. And the concerns internally were, first of all, we just had this fundamental belief that other sellers weren't going to care as much about the customer experience as we did cause it was such a central part of everything we did DNA-wise. And then also we had this entire business and all this machinery that was built around owned inventory business, with all these relationships with publishers and distributors and manufacturers, who we didn't think would necessarily like third party sellers selling right alongside us having bought their products. And so we really debated this, and we ultimately decided that we were going to allow third party sellers to sell in our marketplace. And we made that decision in part because it was better for customers, it allowed them to have lower prices, so more price variety and better selection. But also in significant part because we realized you can't fight gravity. If something is going to happen, whether you want it to happen or not, it is going to happen. And you are much better off cannibalizing yourself or being ahead of whatever direction the world is headed than you are at howling at the wind or wishing it away or trying to put up blockers and find a way to delay moving to the model that is really most successful and has the most amount of benefits for the customers in question. And that turned out to be a really important lesson for Amazon as a company and for me, personally, as well. You know, in the early days of doing Marketplace, we had all kinds of folks, even after we made the decision, that despite the have backbone, disagree and commit weren't really sure that they believed that it was going to be a successful decision. And it took several months, but thankfully we really were vigilant about it, and today in roughly half of the units we sell in our retail business are third party seller units. Been really good for our customers. And really good for our business as well. And I think the same thing is really applicable to the space we're talking about today, to the cloud, as you think about this gigantic shift that's going on right now, moving to the cloud, which is, you know, I think in the early days of the cloud, the first, I'll call it six, seven, eight years, I think collectively we consumed so much energy with all these arguments about are people going to move to the cloud, what are they going to move to the cloud, will they move mission-critical applications to the cloud, will the enterprise adopt it, will public sector adopt it, what about private cloud, you know, we just consumed a huge amount of energy and it was, you can see both in the results in what's happening in businesses like ours, it was a form of fighting gravity. And today we don't really have if conversations anymore with our customers. They're all when and how and what order conversations. And I would say that this going to be a much better world for all of us, because we will be able to build in a much more cost effective fashion, we will be able to build much more quickly, we'll be able to take our scarce resource of engineers and not spend their resource on the undifferentiated heavy lifting of infrastructure and instead on what truly differentiates your business. And you'll have a global presence, so that you have lower latency and a better end user customer experience being deployed with your applications and infrastructure all over the world. And you'll be able to meet the data sovereignty requirements of various locales. So I think it's a great world that we're entering right now, I think we're at a time where there's a lot less confusion about where the world is headed, and I think it's an unprecedented opportunity for you to reinvent your businesses, reinvent your applications, and build capabilities for your customers and for your business that weren't easily possible before. And I hope you take advantage of it, and we'll be right here every step of the way to help you. Thank you very much. I appreciate it. (applause) >> Thank you, Andy. And thank you, everyone. I appreciate your time today. >> Thank you. (applause) (upbeat music)