>>Okay, welcome back everyone. To the cubes coverage of ADB has re-invent 2021. I'm John fare with Dave Nicholson. My cohost we're here exploring all the future innovations. We've got a great guest we'll lead negam who's the EVP executive vice president chief research innovation officer cap, Gemini engineering will lead. Thanks for coming on the cube. Thank you. So I love the title, chief research, innovation engineering officer. >>I didn't make it up. They did. >>You got to love the cloud evolution right now because just more and more infrastructure as codes happening. You got this whole data abstraction layer developing where people are starting to see. Okay. I can have horizontally scalable governed data in a data lake. That's smart, someone intelligent and use machine learning. It seems to be the big trend here from AWS. More serverless, more goodness. So engineering kind of on the front lines here kind of making it happen. >>Yeah. So, uh, the question that our clients are asking us is how do these data center technologies moving over into cars, planes, trains, construction, equipment, industrial, right? And you know, maybe two decades ago it was called IOT. Uh, but we're not talking about just sensors, vertical lift aircraft, uh, software-defined cars, um, manufacturing facilities as a whole, you know, how are these data center technologies going to impact these companies? And it's not a architectural shift for say the Evie, the electric vehicle, many OEM, it's a financial transformation, right? Because if they can make their vehicle containerized, uh, if they can monitor the cars, behaviors, they can offer new types of experiences for their clients. So the questions we were asking ourselves is how do you get the cloud into the car? >>Yeah. And software driving, all that. So you've got software defined everything. Now you've got data-driven pun intended with the cars cloud everywhere. How does that look? What are the concerns, obviously, latency moving data around. They got outposts. Am I moving the cloud to the edge? How are you guys thinking? How are customers thinking through the architectural, I guess foundational playbook? Is there one? Yeah. >>I, you know, coming into this, I did ask my, my son, the question is hardware or software more important. And then he, you know, he's not, and he said, you know, we're coding our way out of hardware. It was very interesting insight software rules. That that is for sure. But when we're talking about physical products and these talking about trillions of dollars of investments going into green energy, uh, into autonomous driving into green aviation. So we're not, it's not just the matter of verse here. We're dealing real physical products. I think though the point for us as engineers or as an engineering businesses, how do you co-design hardware and software together? What are the questions you to ask about that machine learning model being moved over from AWS? For example, into the car, is the Silicon going to be able to support the inferencing rates that are required right. In real time and whatnot. So some of the things like that, >>Well, that's been a, it's been an age old battle between the idea that, uh, the flour that's nurtured in a walled garden is always going to be more beautiful than the one that grows out in the meadow. In other words, announcement, uh, at, in Adam's keynote, talking about advances in AWS Silicon. So what's your view on how important that is? You just sort of alluded to it as being important, the co-development of hardware and software together. >>Yeah. We're seeing product makers again, think, you know, anybody from a life sciences company building a digital therapeutics product, maybe a blood glucose monitor or, um, an automotive or even an aerospace, uh, going direct to Silicon asking questions around the performance of the Silicon and designing their experience around that. Right. So, uh, if they need a low latency, low power efficiency, green networks, they're taking those questions in-house or asking those questions in house. So, you know, AWS having a, sort of a portfolio of custom or bespoke Silicon now as part of the architectural discussion. Right? And so I look around here, I see a lot of developers who are going to have to get a little bit more versed in some of these questions around, you know, should I use an arm based chip? You know, do I use this Silicon partner? You know, what happens when I move it into the vehicle? And then I have over the air updates, how do I protect that code in an enclave in the car just to continue to use the so there's are a lot of architectural questions that I don't think software engineers typically ask when they're just dealing in the cloud. Uh, although at the end of the day over time, a lot of these will be abstracted from the developer to some degree, you know, that is just the nature of the game. >>It reminds me of the operating system theory of system software meeting hardware. And because you have software developers just want to code now, you're saying, well, now I'm responsible hardware. Well, not if it's programmer, was there a hard top two it's over, these are big questions and important ones I think is we're in a major inflection point, but it comes back down to, you mentioned aerospace space is the same problem. You can't send that break, fix engineer in space. Right. You've got software now. So you've got trust that security supply chain who's right. And who's doing the hardware now you've got the software supply chain. So a lot of interesting kind of, yeah. >>So you, you, you know, you check them off, back in into it, the supply chain problems with Silicon, and there are now alternatives to try and get around the bottlenecks using high-performance computers versus hundreds of ECS and a vehicle allows you kind of get away from the supply chain shortage. Uh there's you know, folks moving from one architecture to another, to avoid kind of getting locked in and then of course creating your own Silicon, or at least having more ownership over the Silicon. I think suffer defined systems, uh, are the way to go regardless of the industry. Uh, so you're going to make some decisions on performance, characteristics of the hardware, but ultimately you want a software defined system, so you can update it regularly. >>I was talking with doc some of the top hair executives. I talked to, um, the marketplace guys here, Deepak, uh, over at the, here at Amazon and containers comes up. You start to see a trend in containers where you see certified containers because containers are everywhere. You can put malware and containers. So, you know, think about like just hacking software. It's a surface area now. So you bring the software security model in there. So to see this kind of like certified containers, I can imagine certified infrastructure now because I mean, what's a processor, it's just a hardened top to a PC. Now you've got the cloud. If I have hardware, how do I know it's workable? How do I trust it? You know, how could it not be hacked? I don't want my car to be hacked and driven off the road. >>So, so, um, when you're dealing with a payment system or you're dealing with tick-tock different than when you're dealing with a car with life consequences. So we are very active in the software defined transformation of automotive. And it's easy to say, I'm just going to load it up with all this data center technology, but there's safety criticality issues that you have to take into considerations, but containers are well suited for that. Just requires some thought. I mean, my excitement, enthusiasm about this product engineering is if you just take any of these products and, and apply them into a product engineering context, there's so much invention and creativity can happen. Uh, but on the safety side, we're working through security enclaves using containers and hardware based roots of trust. So there's ways around, you know, malware and bad actors at the edge. Um, >>What's your, what's your take on explainable AI? Why got you might as well ask because this comes up a lot, explainable AI is hot in college right now, AI, that can be explained. It's kind of got some policy, uh, to it. What's your thoughts on this AI trend? Cause obviously it's everywhere. Um, I mean, what is explainable AI? Is that even real or how do you explain AI? Is that democratized? >>Yeah. Computer vision is a great example. I think to bring it to life I'm all of the audience probably knows this, but you could, you know, you can tell your kid that this is a cat once and they'll know every single cat out there is a cat, but if you, you, you need a thousands of images, uh, for a computer vision model to learn that this is a cat. And even, you know, you can probably give it an example, um, out of say a remote region of the world and it going to get confused. So to me, explainability is about adding some sort of certainty to the decision-making process. Um, and when there's a, some confusion, be able to understand why that happened. I think in, in automotive or any, even in quality assurance, being able to know that this product was definitively defective or this pedestrian definitively did cross the crosswalk or not. You know, it's very important because it could, you know, there are, there are consequences. So just being able to understand why the algorithm or the model said what it said, why did it make that judgment is super important, super important. >>So I've got to ask you now that we're here, re-invent from your engineering perspectives, you look at the landscape of AWS, the announcements. What, what, how do you think about it to other engineers out there trying to, uh, grok all the technology who really want to put innovation in place, whether it's creating new markets, new categories or innovating their existing business, how do you grab the class out and make it work for you? I mean, from an engineering standpoint, how do you look at AWS and say, how do I make this work better for me? >>Uh, so I mean, over the years, I, um, I think it's true. AWS has started to really look like a utility, you know, the days where it was called utility as a service. And, um, you know, I, I, I did attend a workshop on, I think it was called LightSail or something like that, but they are simplifying the way that you can consume this infrastructure to a degree that is somewhat phenomenal. Uh, and they're building any, yeah, they continue to expand the ecosystem. Um, so I mean, for me, it's, it's a utility. Uh, it's it's, it's, it's, it's, it's consumable. Uh, if you got an idea pick and roll your own. >>Okay. So back back to the, uh, the concept of AI and explainability, uh, one of my cars won't allow me to unlock certain functions because of the way that I drive. No one needs to explain to me why, because I know what I'm doing wrong, but I'm still frustrated by it. So that that's sort of leads to kind of the larger philosophical question to you about what you're seeing, where are we in this kind of leapfrog, constant pace of the technology exists, but people aren't culturally ready to accept it because it feels like right now to me that there isn't anything we can't do with cloud technology from a technical perspective, it can all be done. Swami's keynote today, talking about integrating all sorts of sources of data and actually leveraging them in the cloud. Um, technically possible yet 85% of it spend is still on prem. So, so what's your thought there? What are the, what are the inhibitors, what are the real inhibitors from a technology perspective versus the cultural ones? Uh, setting aside my lack of, uh, adherence to, uh, to driving lawful >>I industry by industry. I think in, um, you know, if you're trying to do a diagnostic on an MRI in an automated way, and there's going to be false positives, false negatives, and yes, we know that yeah, we know that there's going to be a physician participating in the final judgment call. Um, I think just getting a really good comfort level on the trustworthiness of these decision points, um, is really important. And so I don't blame folks for being reticent about, you know, trusting or, or asking some questions about, does this really work and are these autonomous systems as they become more and more precise, are they doing the right thing? Uh, I think there's research that has to be done on agency. You know, am I in patrol? What happened? Did I lose control? I think there's questions around handoffs, you know, and participation in decision-making. So I think just overall, just the broad area of trust and, uh, the relationship between the participants, the humans and the machines still. I think there's some work to do, to be honest with you. I think there's some work to do maybe in a manufacturing facility where everything's automated, you know, maybe it's a solved problem, but in an open road, when the vehicles driving, you know, in the middle afternoon, you know, you probably should ask some more questions. >>Well, I want to ask you what we got a couple of minutes left, real time data near real time, real time, always a big, hot topic. Seeing one more databases out there in the keynote today from Swami real-time are we there yet? How are we dealing with real-time data, software consuming the data? It comes to cars and things that are moving real time versus near real time. It could be life or death. I mean, this is big time. Where are we? >>So, um, I was trying to conduct a web conference. I won't tell the vendor because it has nothing to do with the vendor. Um, and I couldn't get a connection. I couldn't get a connection at reinvent. I just couldn't get it. I'm sorry guys. I can't get it. So I, you know, so we talk about real time talking about real-time operating systems and real time data collection at the edge. Yeah. We're there, we can collect the data and we can deploy a model in, you know, in the aircraft on the train to do predictive analytics. If we got to stream that data back home to the cloud, you know, we better figure out how to make sure we have a reliable and stable connection. 5g is a, you know, is, is, will be deployed, right? And it has ultra low latency, uh, and can achieve those types of, uh, requirements. But, uh, you know, it has to be in the right setting, right? That's to be the right setting and a facility, uh, very well controlled where you understand the density of the cell sites, small cells sound cells, and you really can deploy a, uh, a mobile robot, uh, wirelessly. Yes know, we can do that, but you know, kind of in, in, in other scenarios, we have a lot of ask that question about >>With the connections and making that false, huh? Well, he, thanks for coming on. Great insight, great conversation. Very deep, awesome work. Thanks for coming on and sharing your insights from cap Gemini. We're here in the cube, the worldwide leader in tech coverage live on the floor here at re-invent I'm John fare with Dave Nicholson. We write back.

>> Narrator: From theCUBE studios in Palo Alto in Boston, connecting with thought leaders all around the world, this is theCUBE conversation. >> Everyone, welcome to the Cube special coverage of the AWS Summit San Francisco, North America all over the world, and most of the parts Asia, Pacific Amazon Summit is the hashtag. This is part of theCUBE Virtual Program, where we're going to be covering Amazon Summits throughout the year. I'm John Furrier, host of theCUBE. And of course, we're not at the events. We're here in the Palo Alto Studios, with our COVID-19 quarantine crew. And we got a great guest here from AWS, Dave Brown, Vice President of EC2, leads the team on elastic compute, and its business where it's evolving and most importantly, what it means for the customers in the industry. Dave, thanks for spending the time to come on theCUBE virtual program. >> Hey John, it's really great to be here, thanks for having me. >> So we got the summit going down. It's new format because of the shelter in place. They're going virtual or digital, virtualization of events. And I want to have a session with you on EC2, and some of the new things they're going on. And I think the story is important, because certainly around the pandemic, and certainly on the large scale, SaaS business models, which are turning out to be quite the impact from a positive standpoint, with people sheltering in place, what is the role of data in all this, okay? And also, there's a lot of pressure financially. We've had the payroll loan programs from the government, and to companies really looking at their bottom lines. So two major highlights going on in the world that's directly impacted. And you have some products, and news around this, I want to do a deep dive on that. One is AppFlow, which is a new integration service by AWS, that really talks about taking the scale and value of AWS services, and integrating that with SaaS Applications. And the migration acceleration program for Windows, which has a storied history of database. For many, many years, you guys have been powering most of the Windows workloads, ironic that you guys are not Microsoft, but certainly had success there. Let's start with the AppFlow. Okay, this was recently announced on the 22nd of April. This is a new service. Can you take us through why this is important? What is the service? Why now, what was the main driver behind AppFlow? >> Yeah, absolutely. So with the launcher AppFlow, what we're really trying to do is make it easy for organizations and enterprises to really control the flow of their data, between the number of different applications that they use on premise, and AWS. And so the problem we started to see was, enterprises just had this data all over the place, and they wanted to do something useful with it. Right, we see many organizations running Data Lakes, large scale analytics, Big Machine Learning on AWS, but before you can do all of that, you have to have access to the data. And if that data is sitting in an application, either on-premise or elsewhere in AWS, it's very difficult to get out of that application, and into S3, or Redshift, or one of those services, before you can manipulate it, that was the challenge. And so the journey kind of started a few years ago, we actually launched a service on the EC2 network, inside Private Link. And it was really, it provided organizations with a very secure way to transfer network data, both between VPCs, and also between VPC, and on-prem networks. And what this highlighted to us, is organizations say that's great, but I actually don't have the technical ability, or the team, to actually do the work that's required to transform the data from, whether it's Salesforce, or SAP, and actually move it over Private Link to AWS. And so we realized, while private link was useful, we needed another layer of service that actually provided this, and one of the key requirements was an organization must be able to do this with no code at all. So basically, no developer required. And I want to be able to transfer data from Salesforce, my Salesforce database, and put that in Redshift together with some other data, and then perform some function on that. And so that's what AppFlow is all about. And so we came up with the idea about a little bit more than a year ago, that was the first time I sat down, and actually reviewed the content for what this was going to be. And the team's been hard at work, and launched on the 22nd of April. And we actually launched with 14 partners as well, that provide what we call connectors, which allow us to access these various services, and companies like Salesforce and ServiceNow, Slack, Snowflake, to name a few. >> Well, certainly you guys have a great ecosystem of SaaS partners, and that's you know well documented in the industry that you guys are not going to be competing directly with a lot of these big SaaS players, although you do have a few services for customers who want end to end, Jassy continues to pound that home on my Cube interviews. But I think this, >> Absolutely. is notable, and I want to get your thoughts on this, because this seems to be the key unlocking of the value of SaaS and Cloud, because data traversal, data transfer, there's costs involved, also moving traffic over the internet is unsecure, and unreliable. So a couple questions I wanted to just ask you directly. One is did the AppFlow come out of the AWS Private Link piece of it? And two, is it one directional or bi-directional? How is that working? Because I'm guessing that you had Private Link became successful, because no one wants to move on the internet. They wanted direct connects. Was there something inadequate about that service? Was there more headroom there? And is it bi-directional for the customer? >> So let me take the second one, it's absolutely bi-directional. So you can transfer that data between an on-premise application and AWS, or AWS and the on-premise application. Really, anything that has a connector can support the data flow in both directions. And with transformations, and so data in one data source, may need to be transformed, before it's actually useful in a second data source. And so AppFlow takes care of all that transformation as well, in both directions, And again, with no requirement for any code, on behalf of the customer. Which really unlocks it for a lot of the more business focused parts of an organization, who maybe don't have immediate access to developers. They can use it immediately, just literally with a few transformations via the console, and it's working for you. In terms of, you mentioned sort of the flow of data over the internet, and the need for security of data. It's critically important, and as we look at just what had happened as a company does. We have very, very strict requirements around the flow of data, and what services we can use internally. And where's any of our data going to be going? And I think it's a good example of how many enterprises are thinking about data today. They don't even want to trust even HTTPS, and encryption of data on the internet. I'd rather just be in a world where my data never ever traverses the internet, and I just never have to deal with that. And so, the journey all started with Private Link there, and probably was an interesting feature, 'cause it really was changing the way that we asked our customers to think about networking. Nothing like Private Link has ever existed, in the sort of standard networking that an enterprise would normally have. It's kind of only possible because of what VPC allows you to do, and what the software defined network on AWS gives you. And so we built Private Link, and as I said, customers started to adopt it. They loved the idea of being able to transfer data, either between VPCs, or between on-premise. Or between their own VPC, and maybe a third party provider, like Snowflake, has been a very big adopter of Private Link, and they have many customers using it to get access to Snowflake databases in a very secure way. And so that's where it all started, and in those discussions with customers, we started to see that they wanted us to up level a little bit. They said, "We can use Private Link, it's great, "but one of the problems we have is just the flow of data." And how do we move data in a very secure, in a highly available way, with no sort of bottlenecks in the system. And so we thought Private Link was a great sort of underlying technology, that empowered all of this, but we had to build the system on top of that, which is AppFlow. That says we're going to take care of all the complexity. And then we had to go to the ecosystem, and say to all these providers, "Can you guys build connectors?" 'Cause everybody realized it's super important that data can be shared, and so that organizations can really extract the value from that data. And so the 14 of them at launch, we have many, many more down the road, have come to the party with with connectors, and full support of what AppFlow provides. >> Yeah us DevOps purists always are pounding the fist on the table, now virtual table, API's and connectors. This is the model, so people are integrating. And I want to get your thoughts on this. I think you said low code, or no code on the developer simplicity side. Is it no code, or low code? Can you just explain quickly and clarify that point? >> It's no code for getting started literally, for the kind of, it's basic to medium complexity use case. It's not code, and a lot of customers we spoke to, that was a bottleneck. Right, they needed something from data. It might have been the finance organization, or it could have been human resources, somebody else in organization needed that. They don't have a developer that helps them typically. And so we find that they would wait many, many months, or maybe even never get the project done, just because they never ever had access to that data, or to the developer to actually do the work that was required for the transformation. And so it's no code for almost all use cases. Where it literally is, select your data source, select the connector, and then select the transformations. And some basic transformations, renaming of fields, transformation of data in simple ways. That's more than sufficient for the vast majority of use cases. And then obviously through to the destination, with the connector on the other side, to do the final transformation, to the final data source that you want to migrate the data to. >> You know, you have an interesting background, was looking at your history, and you've essentially been a web services kind of guy all your life. From a code standpoint software environment, and now I'll say EC2 is the crown jewel of AWS, and doing more and more with S3. But what's interesting, as you build more of these layers services in there, there's more flexibility. So right now, in most of the customer environments, is a debate around, do I build something monolithic, and or decoupled, okay? And I think there's a world where there's a mutually, not mutually exclusive, I mean, you have a mainframe, you have a big monolithic thing, if it does something. But generally people would agree that a decoupled environment is more flexible, and more agile. So I want to kind of get to the customer use case, 'cause I can really see this being really powerful, AppFlow with Private Link, where you mentioned Snowflake. I mean, Snowflake is built on AWS, they're doing extremely, extremely well, like any other company that builds on AWS. Whether it's theCUBE Cloud, or it's Snowflake. As we tap those services, customers, we might have people who want to build on our platform on top of AWS. So I know a bunch of startups that are building within the Snowflake ecosystem, a customer of yours. >> Yeah. >> So they're technically a customer of Amazon, but they're also in the ecosystem of say, Snowflake. >> Yes. >> So this brings up an interesting kind of computer science problem, which is architecturally, how do I think about that? Is this something where AppFlow could help me? Because I certainly want to enable people to build on a platform, that I build if I'm doing that, if I'm not going to be a pure SaaS turnkey application. But if I'm going to bring partners in, and do integration, use the benefits of the goodness of an API or Connector driven architecture, I need that. So explain to me how this helps me, or doesn't help me. Is this something that makes sense to you? Does this question make sense? How do you react to that? >> I think so, I think the question is pretty broad. But I think there's an element in which I can help. So firstly, you talk about sort of decoupled applications, right? And I think that is certainly the way that we've gone at Amazon, and been very, very successful for us. I think we started that journey back in 2003, when we decoupled the monolithic application that was amazon.com. And that's when our service journey started. And a lot of that sort of inspired AWS, and how we built what we built today. And we see a lot of our customers doing that, moving to smaller applications. It just works better, it's easier to debug, there's ownership at a very controlled level. So you can get all your engineering teams to have very clear and crisp ownership. And it just drives innovation, right? 'Cause each little component can innovate without the burden of the rest of the ecosystem. And so that's what we really enjoy. I think the other thing that's important when you think about design, is to see how much of the ecosystem you can leverage. And so whether you're building on Snowflake, or you're building directly on top of AWS, or you're building on top of one of our other customers and partners. If you can use something that solves the problem for you, versus building it yourself. Well that just leaves you with more time to actually go and focus on the stuff that you need to be solving, right? The product you need to be building. And so in the case of AppFlow, I think if there's a need for transfer of data, between, for example, Snowflake and some data warehouse, that you as an organisation are trying to build on a Snowflake infrastructure. AppFlow is something you could potentially look at. It's certainly not something that you could just use for, it's very specific and focused to the flow of data between services from a data analytics point of view. It's not really something you could use from an API point of view, or messaging between services. It's more really just facilitating that flow of data, and the transformation of data, to get it into a place that you can do something useful with it. >> And you said-- >> But like any of our services-- (speakers talk over each other) Couldn't be using any layer in the stack. >> Yes, it's a level of integration, right? There's no code to code, depending on how you look at it, cool. Customer use cases, you mentioned, large scale analytics, I thought I heard you say, machine learning, Data Lakes. I mean, basically, anyone who's using data is going to want to tap some sort of data repository, and figure out how to scale data when appropriate. There's also contextual, relevant data that might be specific to say, an industry vertical, or a database. And obviously, AI becomes the application for all this. >> Exactly. >> If I'm a customer, how does AppFlow relate to that? How does that help me, and what's the bottom line? >> So I think there's two parts to that journey. And depending on where customers are, and so there's, we do have millions of customers today that are running applications on AWS. Over the last few years, we've seen the emergence of Data Lakes, really just the storage of a large amount of data, typically in S3. But then companies want to extract value out of, and use in certain ways. Obviously, we have many, many tools today, from Redshift, Athena, that allow you to utilize these Data Lakes, and be able to run queries against this information. Things like EMR, and one of our oldest services in the space. And so doing some sort of large scale analytics, and more recently, services like SageMaker, are allowing us to do machine learning. And so being able to run machine learning across an enormous amount of data that we have stored in AWS. And there's some stuff in the IoT, workload use space as well, that's emerging. And many customers are using it. There's obviously many customers today that aren't using it on AWS, potential customers for us, that are looking to do something useful with data. And so the one part of the journey is taking up all of that infrastructure, and we have a lot of services that make it really easy to do machine learning, and do analytics, and that sort of thing. And then the other problem, the other side of the problem, which is what AppFlow is addressing is, how do I get that data to S3, or to Redshift, to actually go and run that machine learning workload? And that's what it's really unlocking for customers. And it's not just the one time transfer of data, the other thing that AppFlow actually supports, is the continuous updating of data. And so if you decide that you want to have that view of your data in S3, for example, and Data Lake, that's kept up to date, within a few minutes, within an hour, you can actually configure AppFlow to do that. And so the data source could be Salesforce, it could be Slack, it could be whatever data source you want to blend. And you continuously have that flow of data between those systems. And so when you go to run your machine learning workload, or your analytics, it's all continuously up to date. And you don't have this problem of, let me get the data, right? And when I think about some of the data jobs that I've run, in my time, back in the day as an engineer, on early EC2, a small part of it was actually running the job on the data. A large part of it was how do I actually get that data, and is it up to date? >> Up to date data is critical, I think that's the big feature there is that, this idea of having the data connectors, really makes the data fresh, because we go through the modeling, and you realize why I missed a big patch of data, the machine learnings not effective. >> Exactly. >> I mean, it's only-- >> Exactly, and the other thing is, it's very easy to bring in new data sources, right? You think about how many companies today have an enormous amount of data just stored in silos, and they haven't done anything with it. Often it'll be a conversation somewhere, right? Around the coffee machine, "Hey, we could do this, and we can do this." But they haven't had the developers to help them, and haven't had access to the data, and haven't been able to move the data, and to put it in a useful place. And so, I think what we're seeing here, with AppFlow, really unlocking of that. Because going from that initial conversation, to actually having something running, literally requires no code. Log into the AWS console, configure a few connectors, and it's up and running, and you're ready to go. And you can do the same thing with SageMaker, or any of the other services we have on the other side that make it really simple to run some of these ideas, that just historically have been just too complicated. >> Alright, so take me through that console piece. Just walk me through, I'm in, you sold me on this. I just came out of meeting with my company, and I said, "Hey, you know what? "We're blowing up this siloed approach. "We want to kind of create this horizontal data model, "where we can mix "and match connectors based upon our needs." >> Yeah. >> So what do I do? I'm using SageMaker, using some data, I got S3, I got an application. What do I do? I'm connecting what, S3? >> Yeah, well-- >> To the app? >> So the simplest thing is, and the simplest place to find this actually, is on Jeff Bezos blog, that he did for the release, right? Jeff always does a great job in demonstrating how to use our various products. But it literally is going into the standard AWS console, which is the console that we use for all of our services. I think we have 200 of them, so it is getting kind of challenging to find the ball in that console, as we continue to grow. And find AppFlow. AppFlow is a top level service, and so you'll see it in the console. And the first thing you got to do, is you got to configure your Source-Connect. And so it's a connector that, where's the data coming from? And as I said, we had 14 partners, you'll be able to see those connectors there, and see what's supported. And obviously, there's the connectivity. Do you have access to that data, or where is the data running? AppFlow runs within AWS, and so you need to have either VPN, or direct connect back to the organization, if the data source is on-premise. If the data source happens to be in AWS, and obviously be in a VPC, and you just need to configure some of that connectivity functionality. >> So no code if the connectors are there, but what if I want to build my own connector? >> So building your own connector, that is something that we working with third parties with right now. I could be corrected, but not 100% sure whether that's available. It's certainly something I think we would allow customers to do, is to extend sort of either the existing connectors, or to add additional transformations as well. And so you'd be able to do that. But the transformations that the vast majority of our customers are using are literally just in the console, with the basic transformations. >> It comes bigger apps that people have, and just building those connectors. How does a partner get involved? You got 14 partners now, how do you extend the partner base contact in Amazon Partner Manager, or you send an email to someone? How does someone get involved? What are you recommending? >> So there are a couple of ways, right? We have an extensive partner ecosystem that the vast majority of these ISVs are already integrated with. And so, we have the 14 we launched with, we also pre announced SAP, which is going to be a very critical one for the vast majority of our customers. Having deep integration with SAP data, and being able to bring that seamlessly into AWS. That'll be launching soon. And then there's a long list of other ones, that we're currently working on. And they're currently working on them themselves. And then the other one is going to be, like with most things that Amazon, feedback from customers. And so what we hear from customers, and very often you'll hear from third party partners as well, who'll come and say, "Hey, my customers are asking me "to integrate with the AppFlow, what do I need to do?" And so, you know, just reaching out to AWS, and letting them know that you'd be interested in integrating, that you're not part of the partner program. The team would be happy to engage, and bring you on board, so-- >> (mumbles) on playbook, get the top use cases nailed down, listen to customers, and figure it out. >> Exactly. >> Great stuff Dave, we really appreciate it. I'm looking forward to digging in AppFlow, and I'll check on Jeff Bezos blog. Sure, it's April 22, was the launch day, probably had up there. One of the things that want to just jump into, now moving into the next topic, is the cost structure. A lot of pressure on costs. This is where I think this Migration Acceleration Program for Windows is interesting. Andy Jassy always likes to boast on stage at Reinvent, about the number of workloads of Windows running on Amazon Web Services. This has been a big part of the customers, I think, for over 10 years, that I can think of him talking about this. What is this about? Are you still seeing uptake on Windows workloads, or, I mean,-- >> Absolutely. >> Azure has got some market share, >> Absolutely. >> but now you, doesn't really kind of square in my mind, what's going on here. Tell us about this migration service. >> Yeah, absolutely, on the migration side. So Windows is absolutely, we still believe AWS is the best place to run a Windows workload. And we have many, many happy Windows customers today. And it's a very big, very large, growing point of our business today, it used to be. I was part of the original team back in 2008, that launched, I think it was Windows 2008, back then on EC2. And I remember sort of working out all the details, of how to do all the virtualization with Windows, obviously back then we'd done Linux. And getting Windows up and running, and working through some of the challenges that Windows had as an operating system in the early days. And it was October 2008 that we actually launched Windows as an operating system. And it's just been, we've had many, many happy Windows customers since then. >> Why is Amazon so peak to run workloads from Windows so effectively? >> Well, I think, sorry what did you say peaked? >> Why is Amazon so in well positioned to run the Windows workloads? >> Well, firstly, I mean, I think Windows is really just the operating system, right? And so if you think about that as the very last little bit of your sort of virtualization stack, and then being able to support your applications. What you really have to think about is, everything below that, both in terms of the compute, so performance you're going to get, the price performance you're going to get. With our Nitro Hypervisor, and the Nitro System that we developed back in 2018, or launched in 2018. We really are able to provide you with the best price performance, and have the very least overhead from a hypervisor point of view. And then what that means is you're getting more out of your machine, for the price that you pay. And then you think about the rest of the ecosystem, right? Think about all the other services, and all the features, and just the breadth, and the extensiveness of AWS. And that's critically important for all of our Windows customers as well. And so you're going to have things like Active Directory, and these sort of things that are very Windows specific, and we can absolutely support all of those, natively. And in the Windows operating system as well. We have things like various agents that you can run inside the Windows box to do more maintenance and management. And so I think we've done a really good job in bringing Windows into the larger, and broader ecosystem of AWS. And it really is just a case of making sure that Windows runs smoothly. And that's just the last little bit on top of that, and so many customers enterprises run Windows today. When I started out my career, I was developing software in the banking industry, and it was a very much a Windows environment. They were running critical applications. And so we see it's critically important for customers who run Windows today, to be able to bring those Windows workloads to AWS. >> Yeah, and that's certainly-- >> We are seeing a trend. Yeah, sorry, go ahead. >> Well, they're certainly out there from a market share standpoint, but this is a cost driver, you guys are saying, and I want you to just give an example, or just illustrate why it costs less. How is it a cost savings? Is it just services, cycle times on EC2? I mean what's the cost savings? I'm a customer like, "Okay, so I'm going to go to Amazon with my workloads." Why is it a cost saving? >> I think there are a few things. The one I was referring to in my previous comment was the price performance, right? And so if I'm running on a system, where the hypervisor is using a significant portion of the physical CPU that I want to use as well. Well there's an overhead to that. And so from a price performance point of view, I look at, if I go and benchmark a CPU, and I look at how much I pay for that per unit of that benchmark, it's better on AWS. Because with our natural system, we're able to give you 100% of the floor. And so you get a performance then. So that's the first thing is price performance, which is different from this price. But there's a saving there as well. The other one is a large part, and getting into the migration program as well. A large part of what we do with our customers, when they come to AWS, is supposed to be, we take a long look at their license strategy. What licenses do they have? And a key part of bringing in Windows workloads AWS, is license optimization. What can we do to help you optimize the licenses that you're using today for Windows, for SQL Server, and really try and find efficiencies in that. And so we're able to secure significant savings for many of our customers by doing that. And we have a number of tools that they use as part of the migration program to do that. And so that helps save there. And then finally, we have a lot of customers doing what we call modernization of their applications. And so it really embraced Cloud, and some of the benefits that you get from Cloud. Especially elasticities, so being able to scale for demand. It's very difficult to do that when you bound by license for your operating system, because every box you run, you have to have a license for it. And so tuning auto scaling on, you've got to make sure you have enough licenses for all these Windows boxes you've seen. And so the push the Cloud's bringing, we've seen a lot of customers move Windows applications from Windows to Linux, or even move SQL Server, from SQL server to SQL Server on Linux, or another database platform. And do a modernization there, that already allows them to benefit from the elasticity that Cloud provides, without having to constantly worry about licenses. >> So final question on this point, migration service implies migration from somewhere else. How do they get involved? What's the onboarding process? Can you give a quick detail on that? >> Absolutely, so we've been helping customers with migrations for years. We've launched a migration program, or Migration Acceleration Program, MAP. We launched it, I think about 2016, 2017 was the first part of that. It was really just a bringing together of the various, the things we'd learned, the tools we built, the best strategies to do a migration. And we said, "How do we help customers looking "to migrate to the Cloud." And so that's what MAP's all about, is just a three phase, we'll help you assess the migration, we'll help you do a lot of planning. And then ultimately, we help you actually do the migration. We partner with a number of external partners, and ISVs, and GSIs, who also worked very closely with us to help customers do migrations. And so what we launched in April of this year, with the Windows migration program, is really just more support for Windows workload, as part of the broader Migration Acceleration Program. And there's benefits to customers, it's a smoother migration, it's a faster migration in almost all cases, we're doing license assessments, and so there's cost reduction in that as well. And ultimately, there's there's other benefits as well that we offer them, if they partner with us in bringing the workload to AWS. And so getting involved is really just reaching out to one of our AWS sales folks, or one of your account managers, if you have an account manager, and talk to them about workloads that you'd like to bring in. And we even go as far as helping you identify which applications are easiest to migrate. And so that you can kind of get going with some of the easier ones, while we help you with some of the more difficult ones. And strategies' about removing those roadblocks to bring your services to AWS. >> Takes the blockers away, Dave Brown, Vice President of EC2, the crown jewel of AWS, breaking down AppFlow, and the migration to Windows services. Great insights, appreciate the time. >> Thanks. >> We're here with Dave Brown, VP of EC2, as part of the virtual Cube coverage. Dave, I want to get your thoughts on an industry topic. Given what you've done with EC2, and the success, and with COVID-19, you're seeing that scale problem play out on the world stage for the entire population of the global world. This is now turning non-believers into believers of DevOps, web services, real time. I mean, this is now a moment in history, with the challenges that we have, even when we come out of this, whether it's six months or 12 months, the world won't be the same. And I believe that there's going to be a Cambrian explosion of applications. And an architecture that's going to look a lot like Cloud, Cloud-native. You've been doing this for many, many years, key architect of EC2 with your team. How do you see this playing out? Because a lot of people are going to be squirreling in rooms, when this comes back. They're going to be video conferencing now, but when they have meetings, they're going to look at the window of the future, and they're going to be exposed to what's failed. And saying, "We need to double down on that, "we have to fix this." So there's going to be winners and losers coming out of this pandemic, really quickly. And I think this is going to be a major opportunity for everyone to rally around this moment, to reset. And I think it's going to look a lot like this decoupled, this distributed computing environment, leveraging all the things that we've talked about in the past. So what's your advice, and how do you see this evolving? >> Yeah, I completely agree. I mean, I think, just the speed at which it happened as well. And the way in which organizations, both internally and externally, had to reinvent themselves very, very quickly, right? We've been very fortunate within Amazon, moving to working from home was relatively simple for the vast majority of us. Obviously, we have a number of our employees that work in data centers, and performance centers that have been on the front lines, and be doing a great job. But for the rest of us, it's been virtual video conferencing, right? All about meetings, and being able to use all of our networking tools securely, either over the VPN, or the no VPN infrastructure that we have. And many organizations had to do that. And so I think there are a number of different things that have impacted us right now. Obviously, virtual desktops has been a significant sort of growth point, right? Folks don't have access to the physical machine anymore, they're now all having to work remote, and so service like Workspaces, which runs on EC2, as well, has being a critical service data to support many of our largest customers. Our client VPN service, so we have within EC2 on the networking side, has also been critical for many large organizations, as they see more of their staff working everyday remotely. It has also seen, been able to support a lot of customers there. Just more broadly, what we've seen with COVID-19, is we've seen some industries really struggle, obviously travel industry, people just aren't traveling anymore. And so there's been immediate impact to some of those industries. They've been other industries that support functions like the video conferencing, or entertainment side of the house, has seen a bit of growth, over the last couple of months. And education has been an interesting one for us as well, where schools have been moving online. And behind the scenes in AWS, and on EC2, we've been working really hard to make sure that our supply chains are not interrupted in any way. The last thing we want to do is have any of our customers not be able to get EC2 capacity, when they desperately need it. And so we've made sure that capacity is fully available, even all the way through the pandemic. And we've even been able to support customers with, I remember one customer who told me the next day, they're going to have more than hundred thousand students coming online. And they suddenly had to grow their business, by some crazy number. And we were able to support them, and give them the capacity, which is way outside of any sort of demand--. >> I think this is the Cambrain explosion that I was referring to, because a whole new set of new things have emerged. New gaps in businesses have been exposed, new opportunities are emerging. This is about agility. It's real time now. It's actually happening for everybody, not just the folks on the inside of the industry. This is going to create a reinvention. So it's ironic, I've heard the word reinvent mentioned more times now, over the past three months, than I've heard it representing to Amazon. 'Cause that's your annual conference, Reinvent, but people are resetting and reinventing. It's actually a tactic, this is going on. So they're going to need some Clouds. So what do you say to that? >> So, I mean, the first thing is making sure that we can continue to be highly available, continue to have the capacity. The worst scenario is not being able to have the capacity for our customers, right? We did see that with some providers, and that honesty on outside is just years and years of experience of being able to manage supply chain. And the second thing is obviously, making sure that we remain available, that we don't have issues. And so, you know, with all of our stuff going remote and working from home, all my teams are working from home. Being able to support AWS in this environment, we haven't missed a beat there, which has been really good. We were well set up to be able to absorb this. And then obviously, remaining secure, which was our highest priority. And then innovating with our customers, and being able to, and that's both products that we're going to launch over time. But in many cases, like that education scenario I was talking about, that's been able to find that capacity, in multiple regions around the world, literally on a Sunday night, because they found out literally that afternoon, that Monday morning, all schools were virtual, and they were going to use their platform. And so they've been able to respond to that demand. We've seen a lot more machine learning workloads, we've seen an increase there as well as organizations are running more models, both within the health sciences area, but also in the financial areas. And also in just general business, (mumbles), yes, wherever it might be. Everybody's trying to respond to, what is the impact of this? And better understand it. And so machine learning is helping there, and so we've been able to support all those workloads. And so there's been an explosion. >> I was joking with my son, I said, "This world is interesting." Amazon really wins, that stuff's getting delivered to my house, and I want to play video games and Twitch, and I want to build applications, and write software. Now I could do that all in my home. So you went all around. But all kidding aside, this is an opportunity to define agility, so I want to get your thoughts, because I'm a bit a big fan of Amazon. As everyone knows, I'm kind of a pro Amazon person, and as other Clouds kind of try to level up, they're moving in the same direction, which is good for everybody, good competition and all. But S3 and EC2 have been the crown jewels. And building more services around those, and creating these abstraction layers, and new sets of service to make it easier, I know has been a top priority for AWS. So can you share your vision on how you're going to make EC2, and all these services easier for me? So if I'm a coder, I want literally no code, low code, infrastructure as code. I need to make Amazon more programmable and easier. Can you just share your vision on, as we talk about the virtual summits, as we cover the show, what's your take on making Amazon easier to consume and use? >> It's been something we thought a lot over the years, right? When we started out, we were very simple. The early days of EC2, it wasn't that rich feature set. And it's been an interesting journey for us. We've obviously become a lot more, we've written, launched local features, which narrative brings some more complexity to the platform. We have launched things like Lightsail over the years. Lightsail is a hosting environment that gives you that EC2 like experience, but it's a lot simpler. And it's also integrated with a number of other services like RDS and ELB as well, basic load balancing functionality. And we've seen some really good growth there. But what we've also learned is customers enjoy the richness of what ECU provides, and what the full ecosystem provides, and being able to use the pieces that they really need to build their application. From an S3 point of view, from a board ecosystem point of view. It's providing customers with the features and functionality that they really need to be successful. From the compute side of the house, we've done some things. Obviously, Containers have really taken off. And there's a lot of frameworks, whether it's EKS, or community service, or a Docker-based ECS, has made that a lot simpler for developers. And then obviously, in the serverless space, Landers, a great way of consuming EC2, right? I know it's serverless, but there's still an EC2 instance under the hood. And being able to bring a basic function and run those functions in serverless is, a lot of customers are enjoying that. The other complexity we're going after is on the networking side of the house, I find that a lot of developers out there, they're more than happy to write the code, they're more than happy to bring their reputation to AWS. But they struggle a little bit more on the networking side, they really do not want to have to worry about whether they have a route to an internet gateway, and if their subnets defined correctly to actually make the application work. And so, we have services like App Mesh, and the whole mesh server space is developing a lot. To really make that a lot simpler, where you can just bring your application, and call it on an application that just uses service discovery. And so those higher level services are definitely helping. In terms of no code, I think that App Mesh, sorry not App Mesh, AppFlow is one of the examples for already given organizations something at that level, that says I can do something with no code. I'm sure there's a lot of work happening in other areas. It's not something I'm actively thinking on right now , in my role in leading EC2, but I'm sure as the use cases come from customers, I'm sure you'll see more from us in those areas. They'll likely be more specific, though. 'Cause as soon as you take code out of the picture, you're going to have to get pretty specific in the use case. You already get the depth, the functionality the customers will need. >> Well, it's been super awesome to have your valuable time here on the virtual Cube for covering Amazon Summit, Virtual Digital Event that's going on. And we'll be going on throughout the year. Really appreciate the insight. And I think, it's right on the money. I think the world is going to have in six to 12 months, surge in reset, reinventing, and growing. So I think a lot of companies who are smart, are going to reset, reinvent, and set a new growth trajectory. Because it's a Cloud-native world, it's Cloud-computing, this is now a reality, and I think there's proof points now. So the whole world's experiencing it, not just the insiders, and the industry, and it's going to be an interesting time. So really appreciate that, they appreciate it. >> Great, >> Them coming on. >> Thank you very much for having me. It's been good. >> I'm John Furrier, here inside theCUBE Virtual, our virtual Cube coverage of AWS Summit 2020. We're going to have ongoing Amazon Summit Virtual Cube. We can't be on the show floor, so we'll be on the virtual show floor, covering and talking to the people behind the stories, and of course, the most important stories in silicon angle, and thecube.net. Thanks for watching. (upbeat music)

>>Like for Las Vegas, Nevada, that's the cue governor AWS reinvent 2016, brought to you by AWS and its ecosystem partners. Now, here are your hosts, John furrier and Stu minimum. >>We are here, live in Las Vegas with the cube all week. I'm John minimum. We are breaking down all the re-invent coverage. The cube is going on for three days. Um, Stu and I are going to break down here and studio B the analysis of Andy Jassy, his keynote. This is really day one of the event yesterday was kind of a preview at James Hamilton. Uh, Tuesday evening, I had a great band up there. Uh, and then he came on and delivered a really an Epic performance laying out as a, he's not a showman in the sense of, uh, uh, Steve jobs like, but he has a Steve jobs like cred, uh, James Hamilton, when it comes to the gigs in the community, he delivered the, what I call the secret sauce with AWS as data centers. And then Andy Jassy today with his keynote again is so high pack. >>They start at 8:00 AM, which is kind of not usual for events with so much to up their pack. Councilor came on stage AI Stu. First, I want to get your take on today's keynote with Andy Jassy. You were in the front row. What was going on inside the room? Tip, tell us your perspective, give us the vibe. What was the energy level and what was, what was it like? Yeah. John, as you said, starting at 8:00 AM, it's like a up, we must be talking to the tech audience because developers usually like to start a little bit later than that. Um, it was an embarrassment of riches. Uh, Andy gets on stage, as he told you, when you met with him up at his home in Seattle, uh, they've got, they're going to have about a thousand, you know, major new features updates. Uh, and you know, I think Andy went through a couple of hundred of them up on stage. >>Uh, you know, this is a group of true believers pack. Keynote people started streaming in over an hour ahead of time because only 10,000 could fit in the main tent. They had other remote locations where you could go get, you know, mimosas, bloody Marys or coffee. Uh, if you wanted to watch us, all over that. But it, it, it just to tell you, my fourth year here at the show and it's like, Oh yeah, another tech show. You're going to get keynotes. They're going to make some announcements yawn, no Amazon impresses every year. And they delivered this year. Andy might not be a showman, but you know, he was punching at a, you know, Larry Ellison and Oracle quite a bit. He got huge ovations. Like every time they announced a new compute instance, uh, in lots of these things, uh, and a little bit of show flare, uh, at the end, uh, certainly the going into the database market. >>Uh, but also they're making some really good infrastructure enhancements with the new services. What was your highlight if you're going to look at what the most significant, most important story this morning, what, what was squinting through all the great announcements? What ones you liked best? Oh boy. John, I have to pick one. I mean, here, here's a few number one is, you know, there's, there's some pushback from people in the community that, Oh, you know, they announced another ton of news, you know, compute instances, there's all these different storage configurations. Uh aren't we supposed to be making things simple. Uh, and that's when they had a one Amazon LightSail, which is the virtual private servers in seconds really goes after, you know, kind of a, you know, simple, low cost model, uh, really digital ocean's the leader in that space starting at like $5 a month, John, uh, you know, very exciting. A lot of people, uh, you know, really getting, uh, you know, as to where this could go every year, Amazon has a number of competitors that they're just like up, we see this opportunity. We can go after this. And John, this is not a high margin business. I mean, usually it's like, Oh, okay, database. I understand there's huge margin there. The storage market, of course, LightSail $5 a month. I mean, you know, they make it up in volume, but it's super fast. >>It was on a playbook. It drive the price down as low as possible, and then shift the value with the analytics. Um, and, uh, Aurora PA um, um, uh, pack housing or any chassis said fastest growing service in the history of Amazon last year, he said red shift was that this surpass red shift, uh, the announced Postgres equal on a roar, another big significant customer request. Um, just on and on the database seems to be the lock-in spec that they're trying to undo from Oracle. Um, they're not stopping. I mean, the rhetoric was all time high, John, the picture Larry Ellison popped out, popped in the Oracle. Oh, in the, in, in the O >>We know the long pole in the tent for enterprises is the applications you have making any changes in that, uh, doing any refactoring, you know, tinkering, you know, those are hard things to do. Um, but you know, we've heard a lot from Amazon this week as to how they're helping with migration, how they're giving options, how they're giving bridges, uh, things like VMware on AWS to bridge over from where you are, you know, you can lift and shift it. You can move it, you can rewrite it, lots of options there. Uh, and Amazon just has so many services and so many customers, thousands of systems integrators, uh, you know, thousands of ASVs, uh, and really big enterprises, you know, making statements up on stage. When you get Workday up on stage, John, you get McDonald's up on stage. Uh, you know, it's impressive. >>Some big name accounts, no doubt about it. That's do I want to get your thoughts on James Hamilton? Again, Amazon's got some of the announcements. I mean, some companies will launch entire conference keynote around maybe one or two of what they've done out of the many that they've had here also to note, there's been over 150 partner announcements. So the ecosystems do before we get to Hamilton, I want to talk about the ecosystem. This feels a lot like 2011, VMware. I was kind of joking with Sanjay Poonen the CEO of VMware was just on the cube with us and saying, what do you think about VMworld this year? I mean, re-invent, I was kind of tongue in cheek. I wanted to zinc them a little bit, but stew, this feels like, >>So John, I'm an infrastructure guy, and I want to talk about James Hamilton. One thing we got to cover first green grass. I, you know, green grass is how Amazon is taking their serverless architecture, really Lambda and taking it beyond the cloud. So how do I get, you know, that, that kind of hybrid edge, we talked about it a little bit with Sanjay, but number one, I can start pulling VMware into AWS. Number two, I can now get, you know, my Lambda services, uh, out on the edge, they talked about some IOT plays on, they talked about the snowball edge, uh, which is going to allow me to have kind of compute and storage, uh, down at that edge. Uh, I've seen huge excitement at this show, uh, on the serverless piece developers, it's really quick to work with, uh, twenty-five thousand Amazon echo dots were handed out and I've already talked to people that are already, you know, writing functions for that and figuring out how to can play with it. And God, we haven't even talked about the AI, John with voice and images. How many hours do we have John? >>I we'll get there. Let's stay on green grass for a minute, because if you think about what that's about, I want to get your thoughts on your thoughts on the impact of green grass. I mean, obviously the lamb done, that's got a little edge piece of snowball tied to it. Uh, you know, green grass and high ties forever. The old song by, you know, Southern rock band Outlaws back in the day, this is a significant announcement. What is the impact of that? >>Yeah, well, John, I mean the grass is greener in the cloud, right? So now we're going to bring the green grass, >>No ball when it snowball, my melts extends in the green grass. >>So we're going to be riffing all day on this stuff. So David foyer, uh, our CTO at Wiki bond has been talking for awhile, uh, that, you know, while cloud is great for data, the problem we have is that IOT is going to have most of the, you know, most of the data out on the edge. And we know the physics of moving large amounts of data is really tough. And especially if it's spread out things like sensors, things like wind farms, getting the networking to that last mile can be difficult. That's where things like green grass are going to be able to play in. How can I take really that cloud type of compute and put it on the edge. It really has potential to be a real game changer. I think John, we talked about what hybrid means, uh, and you know, we'll, we'll see a lot, a lot of buzz in the industry about what Microsoft's doing with Azure stack, uh, and you know, lots of pieces, but you know, grass, you know, it gives this new model of programming. It gives the developers, uh, it gives me, you know, I can use the arm processors, uh, out on the edge and, you know, we could try and talk about how that fits with James Hamilton too. >>We are inside the hall next to the cube studio, being so much content. We have to actually set up a separate set. Stu I want to get your thoughts on, I mean, obviously we can go on forever, but the significant innovation on multiple fronts for Amazon, you mentioned Greengrass, snowball, multiple instances. Um, and certainly they got all the analytics on Bubba, the top of the stack with Redshift and other stuff. And he says, streaming goes on and on the list goes on and on, but you look at what they're doing with Greengrass and snowball. And then you go look at what James Hamilton talked about yesterday. Now they're going down an innovating down to the actual physical chip level. They're doing stuff with the network routes, the control in the packet there, no one's touching the packets. They are significantly building the next global infrastructure backbone for themselves to power the world. This is, to me, I thought a subtle talk that James gave. There's a ton of nuance in there. Your thoughts on last, night's a really Epic presentation. I know we're gonna have a sit down exclusive interview with James Hamilton with Rob Hoff, our new editor in chief Silicon angle, but still give us a preview. What blew you away? What got you excited? I mean, it was certainly a geek dream. >>Yeah. I mean, John, you know, James Hamilton is just one of those. You talk about tech athletes, you know, just the, the real heroes in this space, uh, that so many of us look up to, uh, it's been one of the real pleasures of my career working, uh, with the cube that I've gotten to speak to James a few times. Uh, and the first article I wrote three years ago, uh, about what James Hamilton has done is it's hyper optimization. The misconception that people had about cloud is, Oh, it's just a white box. They're taking standard stuff, Amazon. And what James always talks about is how to, you know, really grow and innovate at scale. And that means they build for their environments and they really get down to every piece of the environment, all the software, all the hardware, they either customize it or make their own. So, you know, the big monitor >>And Stu to your point for their own use cases, the home, a prime Fridays and those spike days, he was talking about how they would have to provision months and months in advance to add, to understand some estimated peak that they were spinning up, literally thousands of servers. >>Yeah. So John, you know, Amazon doesn't make a lot of acquisitions, but one that they made is Annapurna labs. So they've got their own custom Silicon that they're making. Uh, so this will really allows them to control, uh, how they're doing their build-out. They can focus on things like performance. Uh, James talked about, uh, you know, how they're, they're really innovating on the network side. He was very early with 25 gigabit ethernet, uh, which really drove down. Some of the costs, gave them huge bandwidth advantages, uh, and kind of leading the way in the industry. Uh, the, the, the thing we've been poking out a bit is while Amazon leverages a lot of open source, they don't tend to give back as much. Uh, they've got the big MX net announcement as to how they're going to be involved in, in the machine learning. And that's good to see they hired Adrian Cockcroft, uh, you know, who lots of us knew from his Netflix days. Uh, and when he was a venture capitalist, he's going to be driving a lot of the open source activity. But James, you know, kind of went through everything from, >>By the way, on your point about source, I set it on the cube and I'll say it again. And you Mark my words. If Amazon does not start thinking about the open source equation, they could see a revolt that no one's ever seen before in the tech industry. And that is the open source community. Now as a tier one, it has been for a long time tier one contributor to innovation, and as a difference between using open source for an application like Facebook and a specific point application or Google for search, if you are building open source to build a company, to take territory from others, there will be a revolts. Do you, John, do you agree? Am I off, >>Uh, revolt might be a little strong, but absolutely. We already see some pushback there. And anytime a company gets large power in the marketplace, you see pushback. We saw it with Oracle, with salt, with Microsoft, we see it with VMware. Uh, so you know, and I think Amazon, here's this point, uh, Andy Jassy talks about how they're making meaningful contributions. I expect Adrian, uh, to make that much more visible. Um, we'll have to get into some of the James Hamilton stuff at a later date, but >>Down with him with Rob posts more on that later, you and I will hit James Hamilton analysis on the key later final thoughts you were giving me some help before we came on to talk here about me saying, I'm bullish on VMware's relationship with AWS. And you said, really? And I said, I am because I am a big fan of VMware, um, also AWS, but for their customers, for AI, for VMware customers, this is a good thing. Now you might have some thoughts on execution. Maybe what's your, why? Why did you roll your eyes when I said that? >>So, John, I mean, you know, I've lots of love for the VMware community. Uh, you know, spent lots of time in that space. Uh, and it, it's good to see, uh, VMware working with the public clouds. However, uh, I think the balance of power Shilton shifts in the side of Amazon being in control here. Uh, and you know, there's a lot of nuance. Where are the services where the value is what's going to be good for customer. Amazon's really good at listening. Uh, and you know, this embarrassment of riches that they do, right? >>A real summary, what bottom line, what happened this morning and your mind abstracted all the way in one soundbite, wait, >>They rolled a truck out, out stage, John, this snowmobile a hundred terabytes, a hundred petabytes of storage and a terabyte of information. Something that, you know, we were like, this is amazing. It's it's the, the maturation of the hybrid message is different from what people have been talking about hybrid, uh, you know, where SAS lives, all the ISV is. Where's the data, where's the application. Amazon's in a really good position. John, there's a big and growing ecosystem here. Uh, but there's a huge battles that I know we're going to get into, uh, out in the marketplace. You know, who's going to win voice, uh, you know, everybody's their apples, their Microsoft, >>Because everyone's jocking for position. Got Google, you got Oracle, you've got IBM. You've got Microsoft all looking at AWS and saying, how do we change the game on them? And we'll be covering this. The cute we are here in Las Vegas studio B cube three days of wall-to-wall Cubs, I'm Jeffers do minimum, breaking it down on day one, keynotes and analysis. Thanks for watching. We'll be right back. Stay tuned to the cube cube siliconangle.tv. You go to siliconangle.com for all the special exclusive stories from re-invent specifically to, with Andy Jassy, James Hamilton, and more thanks for watching.