>>from around the globe. It's the Cube with digital coverage of AWS reinvent 2020 sponsored by Intel and AWS. Yeah, welcome back to the Cubes. Live coverage of AWS reinvent 2020. It's virtual this year over three weeks. Next three weeks we're here on the ground, covering all the live action. Hundreds of videos Walter Wall coverage were virtual not in person this year. So we're bringing all the interviews remote. We have Deepak Singh, vice president of Compute Services. A range of things within Amazon's world. He's the container guy. He knows all what's going on with open source. Deepak, great to see you again. Sorry, we can't be in person, but that's the best we could do. Thanks for coming on. And big keynote news all year all over the keynote. Your DNA is everywhere in the keynote. Thanks for coming on. >>Yeah. Now, no thanks for having me again. It's always great to be on the Cube. Unfortunately, not sitting in the middle of the floral arrangement, which I kind of miss. I know, but it waas great morning for us. We had a number of announcements in the container space and sort of adjacent to that in the developer and operator experience space about making it easy for people to adopt things like containers and serverless. So we're pretty excited about. And his keynote today and the rest agreement. >>It's interesting, You know, I've been following Amazon. Now start a three invent. I've been using Amazon since easy to started telling that garment that story. But you look like the mainstream market right now. This is a wake up call for Cloud. Um, mainly because the pandemic has been forced upon everybody. I talked to Andy about that he brought up in the keynote, but you start to get into the meat on the bone here. When you're saying OK, what does it really mean? The containers, the server Lis, Uh, the machine learning all kind of tied together with computers getting faster. So you see an absolute focus of infrastructures of service, which has been the bread and butter for Amazon web services. But now that kinda you know, connective tissue between where the machine learning kicks in. This is where I see containers and lambda and serve Earless really kicking ass and and really fill in the hole there because that's really been the innovation story and containers air all through that and the eks anywhere was to me the big announcement because it shows Amazon's wow vision of taking Amazon to the edge to the data center. This is a big important announcement. Could you explain E. K s anywhere? Because I think this is at the heart of where customers are looking to go to its where the puck is going. You're skating to where the puck is. Explain the importance of eks anywhere. >>Yeah, I'll actually step back. And I talked about a couple of things here on I think some of the other announcements you heard today like the smaller outposts, uh, you know, the one you and do you outpost skills are also part of that story. So I mean, if you look at it, AWS started thinking about what will it take for us to be successful in customers data centers a few years ago? Because customers still have data centers, they're still running there On our first step towards that Waas AWS in many ways benefits a lot from the way we build hardware. How what we do with nitro all the way to see C two instance types that we have. What we have a GPS on our post waas. Can we bring some of the core fundamental properties that AWS has into a customer data center, which then allowed PCs any KS and other AWS services to be run on output? Because that's how we run today. But what we started hearing from customers waas That was not enough for two reasons. One, not all of them have big data centers. They may want to run things on, you know, in a much smaller location. I like to think about things like oil rates of point of sale places, for they may have existing hardware that they still plan to use and intend to use for a very long time with the foundational building blocks easy to EBS. Those get difficult when we go on to hardware. That is not a W s hardware because be very much depend on that. But it containers we know it's possible. So we started thinking about what will it take for us to bring the best of AWS toe help customers run containers in their own data center, so I'll start with kubernetes, so with que binaries. People very often pick Kubernetes because they start continue rising inside their own data centers. And the best solution for them is Cuban Aires. So they learn it very well. They understand it, their organizations are built around it. But then they come to AWS and run any chaos. And while communities is communities, if you're running upstream, something that runs on Prem will run on AWS. They end up in two places in sort of two situations. One, they want to work with AWS. They want to get our support. They want to get our expertise second, most of them once they start running. Eks realized that we have a really nice operational posture of a D. K s. It's very reliable. It scales. They want to bring that same operational posture on Prem. So with the ts anywhere what we decided to do Waas start with the bits underlying eks. The eks destroyed that we announced today it's an open source communities distribution with some additional pieces that that we had some of the items that we use that can be run anywhere. They're not dependent on AWS. You don't even have be connected to a W s to use eks destro, but we will Patrick. We will updated. It's an open source project on get help. So that's a starting point that's available today. No, Over the next several months, what will add is all of the operational to link that we have from chaos, we will make available on premises so that people can operate the Cuban and these clusters on Prem just the way they do on AWS. And then we also announced the U. K s dashboard today which gives you visibility into our communities clusters on AWS, and we'll extend that so that any communities clusters you're running will end up on the dashboard to get a single view into what's going on. And that's the vision for eks anywhere, which is if you're running communities. We have our operational approach to running it. We have a set of tools that we're gonna that we have built. We want everybody to have access to the same tools and then moving from wherever you are to aws becomes super easy cause using the same tooling. We did something similar with the C s as well the DCs anywhere. But we did it a little bit differently. Where in the CSU was centralized control plane and all we want for you is to bring a CPU and memory. The demo for that actually runs in a bunch of raspberry PiS. So as long as you can install the C s agent and connect to an AWS region, you're good to go. So same problem. Different, slightly different solutions. But then we are customers fall into both buckets. So that's that's the general idea is when we say anywhere it means anywhere and we'll meet you there >>and then data centers running the case in the data center and cloud all good stuff. The other thing that came out I want you to explain is the importance of what Andy was getting to around this notion of the monolith versus Micro Services at one slightly put up. And that's where he was talking about Lambda and Containers for smaller compute loads. What does it mean? What was he talking about there? Explain what he means by that >>that Z kind of subtle and quite honestly, it's not unique to London containers. That's the way the world was going, except that with containers and with several functions with panda. You got this new small building blocks that allow you to do it that much better. So you know you can break your application off. In the smaller and smaller pieces, you can have teams that own each of those individual pieces each other pieces. Each of these services can be built using architecture that you secret, some of them makes sense. Purely service, land and media gateway. Other things you may want to run on the C s and target. Ah, third component. You may have be depending on open source ecosystem of applications. And there you may want to run in communities. So what you're doing is taking up what used to be one giant down, breaking up into a number of constituent pieces, each of which is built somewhat independently or at least can be. The problem now is how do you build the infrastructure where the platform teams of visibility in tow, what all the services are they being run properly? And also, how do you scale this within an organization, you can't train an entire organ. Communities overnight takes time similar with similarly with server list eso. That's kind of what I was talking about. That's where the world is going. And then to address that specific problem we announced AWS proton, uh, AWS program is essentially a service that allows you to bring all of these best practices together, allows the centralized team, for example, to decide what are the architectures they want to support. What are the tools that they want to support infrastructure escort, continuous delivery, observe ability. You know all the buzzwords, but that's where the world's going and then give them a single framework where they can deploy these and then the developers can come into self service. It's like I want to build a service using Lambda. I don't even learn how toe put it all together. I'm just gonna put my coat and pointed at this stock that might centralized team has built for me. All I need to do is put a couple of parameters, um, and I'm off to the races and not scale it to end, and it gives you the ability to manage also, So >>it's really kind of the building blocks pushing that out to the customer. I gotta ask you real quick on the proton. That's a fully managed service created best. Could you explain what that means for the developer customer? What's the bottom line? What's the benefit to >>them? So the biggest benefit of developers if they don't need to become an expert at every single technology out there, they can focus on writing application court, not have to learn how to crawl into structure and how pipelines are built and what are the best practices they could choose to do. So the developers, you know, modern and companies Sometimes developers wear two hats and the building off, the sort of underlying scaffolding and the and the build applications for application development. Now all you have to do is in writing an application code and then just go into a proton and say, This is architecture, that I'm going to choose your self, service it and then you're off to the races. If there's any underlying component that's changing, or any updates are coming on, put on it automatically take care off updates for you or give you a signal that says, Hey, the stock has to be updated first time to redeploy accord so you can do all of that in a very automated fashion. That's why everything is done. Infrastructures Gold. It's like a key, uh, infrastructure and told us, and continuous delivery of sort of key foundational principles off put on. And what they basically do is doing something that every company that we talked oh wants to do. But only a handful have the teams and the skill set to do that. It takes a lot of work and it takes ah lot of retraining. And now most companies don't need to do that. Or at least not in that here. So I think this is where the automation and manageability that brings makes life a lot easier. >>Yeah, a lot of drugs. No docker containers. They're very familiar with it. They want to use that. Whatever. Workflow. Quickly explain again to me so I can understand fully the benefit of the lamb container dynamic. Because what was the use case there? What's the problem that you solve? And what does it mean for the developer? What specifically is going on there? What's the What's the benefit? Why would I care? >>Yeah, eso I'll actually talked about one of the services that my team runs called it of your stature. AWS batch has a front time that's completely serverless. It's Lambda and FBI did play its back in the PCs running on the city right? That's the better the back end services run on their customers. Jobs in the running. Our customers are just like that. You know, we have many customers out there that are building services that are either completely service, but they fit that pattern. They are triggered by events. They're taking an event from something and then triggering a bunch of services or their triggering an action which is doing some data processing. And then they have these long running services, which almost universally in our running on containment. How do you bring all of this together into a single framework, as opposed to some people being experts on Lambda and some people being experts and containers? That's not how the real world works. So trying to put all of this because these teams do work together into a single framework was our goal, because that's what we see our customers doing, and I think they'll they'll do it. More related to that is the fact that Lambda now supports Dr Images containing images as a packaging format because a lot of companies have invested in tooling, toe build container images and our land. I can benefit from that as well. While customers get all the, you know, magic, The Lambda brings you >>a couple of years ago on this on the Cube. I shared this tweet out earlier in the week. Andy, we pressed and even services launches like, would you launch build Amazon on Lamb? Day says we probably would. And then he announced to me And he also I think you mentioned the keynote that half of Amazon's new APS are built on lambda. >>Yeah, that's good. This >>is a new generation of developers. >>Oh, absolutely. I mean, you should talk to the Lambda today also, but even like even in the container side, almost half of the new container customers that we have on AWS in 2020 have chosen target, which is serverless containers. They're not picking E c s or E. T. S and running at least two. They're running it on target the vast majority of those two PCs, but we see that trend on the container side as well, and actually it's accelerating. More and more and more new customers will pick target, then running containers on the city. >>Deepak, great to chat with you. I know you gotta go. Thanks for coming on our program. Breaking down the keynote analysis. You've got a great, um, focus area is only going to get hotter and grow faster and a lot more controversy and goodness coming at the same time. So congratulations. >>Thank you. And always good to be here. >>Thanks for coming on. This is the Cube Virtual. We are the Cube. Virtual. I'm John for your host. Thanks for watching.

>> live from London, England. It's the queue covering a ws summat. London twenty nineteen Brought to you by Amazon Web services >> Hello and welcome to the Age Ws Summit live from London's Excel Center. I'm Susanna Street, and this is my co host on the Cube Day Volonte on. There are lots of breakout sessions taking place right across this venue. One of them all about Bring Thio life, the eight of us marketplace and really helping people, companies and stand cow to make that journey to the cloud. And my two guests here right now have been at that session trying to communicate that toe many delegates who were there here Mobile, who's from Computer Center. He is the public cloud lead for the UK and Ireland, and Garforth, who's a director off a ws marketplace. Thank you very much for joining us >> to be here >> Now there are riel complexities are their way. Just helping people navigate their way through. Tell me that a bit more about how marketplace has evolved because it's being rapid. Hasn't >> it? Has been rapid. We launched a CZ initial service in two thousand twelve, so we just had our seventh birthday last year. We started with pretty modest aspirations, and it was all about helping developers take advantage of the sea to and be able to take advantage of. A bus. Service is available at the time. So it was a cattle about two hundred fifty mostly open source applications that developers could sort of find, explore, discover and provisions straight from the council where they were doing their work. Overtime. We've added support for a lot of new product type, so we support SAS applications. All right, reinvent Last year, we announce support for Dr in being able to take Dr Images and deploy those into stage maker. We're talking about that earlier. Also support for containers. And so his customers are moving to more of a survivalist type architecture. We have already made set of container images that they could deploy directly into the S E. K s or far gate. I'd say one of more interesting sort of inflection point in our evolution was when people started buying real stuff for real money because I think when we got started serving the developers, I kind of think of that is kind of a Lamborghini kind of crowd. That's a customer, by the way, but, uh, Lamborghini guys just, you know, developers want to go as fast as they possibly can. They don't really care for speed limits, you know, they just want to get the job done as quick as they can. Um, we had an example, for example, our first million dollar transaction. Wait, We're surprised to see it. We woke up on Monday and we saw a million dollar transaction. So I told my finance team not to get too excited. I went to the customer and I said, Was this a mistake or did you intend >> to do >> that? And the developer team said No, that was the best software sale ever because I didn't have to talk to anybody. >> I couldn't make money while you sleep isn't absolutely, but they were >> able to. Basically, they didn't have to go through a lengthy process of procurement and legal reviews and everything else. They literally were able to subscribe to the product and get it deployed within seconds, and the estimated that it took about three months off of their engineering cycle was being able to go that fast. But >> the interesting thing on >> million dollar transactions is, there's a lot of other people that care about that. So I got a letter about eight weeks later from their corporate headquarters in New York. It said that Development team was not >> really authorized to spend that much money on that product, >> and so that is what I call the Volvo crowd. And there are big parts of our customer that are very, very interested in safety and airbags and collision avoidance and all that other fun stuff. And so what Marketplace has been really innovating on in the last couple of years is finding a way to modernize how companies buy and deploy softer in the cloud. Do that at speed. But do it in a way that's compliant with whatever regulations governing the things. >> So do it speed but variable speed, >> variable speed and just, you know, a lot of our customers in the public sector or in health care financial services. They're heavily regulated on on their own, and they have a certain way they need to do things. And so we've been building features like the private marketplace which we just launched actually allows the customer to go in and reason over our catalog We've got forty eight hundred listings in our catalog, fourteen hundred different vendors and they can decide on their own. Which one of those air fruit for use or not, >> because it's very hard to meet the procurement demands of various of public sector organization because they're so >> they are very diverse. But that's also one of the reasons, like I'm excited too heavy in here. We've been working for the last couple of years to figure out how we can more effectively work with partners to sort of serve our joint customers. So he and what's your story? How >> do you fit what? It's a good question. So I think Computer Center entered into the fray with eight of us, sort of circa reinvent twenty seventeen. So just a time where Marketplace was launching two partners, I guess in the mainstream on on, we looked at what the offering in partnership with these guys and what it would mean to our customers, and that was kind of very customer letters and organization if you know anything about us. Customers were asking for different ways to potentially by traditional software packages as they moved into the Ws Cloud, and they were moving at scale and that velocity that we talk about and it was about well, is this a product or a mechanism that can help them streamline? Can they simplify on the way? Can they cut some of that complexity on that journey? We see that very much as a Roald. Help them achieve that. This seems like a really good mechanism, so we fast forward through twenty eighteen. We do some great deals together, those sort of way talk about on way. See that this is becoming more mainstream for customers. Is their landing in a ws in the cloud and thinking about different ways? Different software titles challenging Do We Need to Do Things is normal, or should we do things a different way? What about this dynamic that we were just talking about? That garden was just saying about the procurement folk, the >> Volvo crowd versus the Lamborghini Cross You what do you have developed a workflow approval process that it worked? Yeah, well, unpack it a little bit, the the private marketplace allows, and every customer is a little bit different. Sometimes it's the chief security officer who kind of makes the final decision. Sometimes it's procurement. Sometimes the legal team has specific move constraints on what they what. They want to prove that not I really haven't found two customers that are identical in terms of how they're worked over an l O B manager. Correct CFO. I mean, you're right, lots of different roles. So we effectively, we did some surgery on the underlying service to create a new I am role. And so if Ian is the administrator for his organization, regardless of role, he's given permission to go approve and disapprove products. And some customers are kind of in a white list load, which is basically you can use, uh, only the things that I wait listed. So everything's forbidden until I've explicitly approved it. Other companies, like a lot of smaller companies that may not have that much process. We're more of a blacklist mode. We're sort of like everything in the marketplace is fair game, except the ones I've specifically said not to use on DH. So we just created this really flexible infrastructure that lets customers customize the marketplace to their needs. So you give superpowers to some admin and then the white list black blacklist, depending on what it is. And then it becomes frictionless. It becomes frictionless, and then the user experience the customer can actually have their own logo. They can put their own language around, kind of how they wantto sort of represent that to the developers. And then every developer in their organization then sees that experience and they can see what's been approved in what hasn't. OK, so you get a private label through the channel. Yeah, so that I, as a consumer see whatever brand that your customer yet need to see exactly. And then we've also got a facility because, you know, with over forty eight hundred listings in the marketplace, fourteen hundred different vendors, you know, nobody's got time to go reason over every single item, and we're adding hundreds every year, so that keeps growing. And so we've got a facility. If the developer has a specific technology that they really require, we've got a little simple work flow so developed could say, I need this widget to build this thing, and then we kick it off to the admin who could approve it. And as we were talking about for our video closet, you gonna have precise understanding of the pricing. You know this one hundred percent clarity. And then once you have that on you, Khun, split the pie hole, then you can split up and we did. But like one of the foundational technologies that we launched, twenty seventeen was this notion of a private offer. And so if I want to make a private offer to Ian at a price that he and I have negotiated on legal terms that he and I have agreed to, I can do that through marketplace. And then what with the way that would work in a large organization is once somebody's subscribes Once to that price, everybody in the organization that used that product is using it at the agreed price. OK, right. And then we extended that to enable Channel partners now. So for the ice fees that included center works with now, he's now able to go create private offers for his custom. So what, you're essentially created a two sided >> marketplace that effect? Yeah, I think the interface between the two organizations is really important. It becomes that sort of tripartite with the ice V, putting the customer right in the center. I think that's the signage is that we seem to organizations. >> Do you really see what your input has bean there items that are listed as well. Did you get that >> for, like, selection? >> Yeah, yeah, that that like, you know, >> saying it's pretty customer focused, you know, we work with customers we have. We have a set of people around the world that do what we call category management, and they theirjob is to work with customers and make sure that we're stocking the right inventory on the shelves, so to speak. So we get that input like every day, >> and then that helps you develop you new products, >> New continent, new products. And that's >> ahead of the competition. >> Wei. Try to think more about like, let's focus on our customers. Wei don't spend a lot of time chasing tail lights, but very customer obsessed. What things always >> interested me about the marketplaces. It's so complex in terms of region's >> tax laws, pricing considerations on and on and on so many permutations. You talk a little bit about how you've >> succeeded in just essentially making that all transparent and what what's behind that? >> Um well, I think you know Amazon >> and eight of us like we operate within the legal frameworks and all the countries where we operate in. So we have our own requirements in terms of how we remit and collect tax in countries compliant with local laws. Right. So we had to do that just to operate a to B S right way were able to leverage a lot of the same plumbing we had to build for ourselves and effectively make that available to our lives. So we have, like, there's a small eyes. We actually they've grown to be quite big. But here in the UK is a company called Matile Ian, who uses us exclusively a cz, their cloud channel. Um and we take him the HBS available eighteen regions marketplace on, and then everywhere we need to we will remit and collect tax on his behalf and then give him reports that he could share with his auditor to ensure compliance with local laws. And so we do a lot of that stuff. He's a small firm, you know, and for us to be able to sort of, like, extract and abstract all that complexity from him and just give him a nice monthly report that shows him all the taxes we can on his behalf. That's a big service right >> now. How's it transform your business? >> So I say transforming rather than transformed because it's a continuum thing all the time. I think it's absolutely that a different way of procurement is, firstly, the thing that customers are asking for. So it's just one cog in the wheel for a ws that customs picking up on. I think the point that golf is very well glossing over is that between us, we're doing the heavy lifting on behalf of the customer. I think that's today's point thing. That's that's the whole point here, where that we've all got a part to play in the ecosystem and it's it's all about customer experience. That's most important. I think what we're seeing is repeat customers come back. Actually, that's the biggest from if I look up from the start of twenty eighteen to the end, it was the repeat visits, so you get you know, the one million pound or dollar deal customer coming back twice or three times in the year to do the same thing again, >> but have any being put off by this new >> approach, but I haven't seen that so genuine. It hasn't appeared so far, so there's some education. Of course, that has to happen because it's different. It's not the norm. If you think about enterprise customers, they've been buying up a particular mode for twenty or thirty years or longer, a CZ we joke about. So this is just an education process that let them know what on how on then, what's there on the bandwagon? It kind of becomes that streamline process. >> Yeah, ad I'd build on top again. Sport like you kind of think about the way way >> customers thought about procuring infrastructure before eight of us existed, like back in way. But in the way big back of two thousand five, like buying hardware in storage and networking gear was crazy, hard and very difficult and long and laborious. And your racket and stacking everything else. And then a dubious comes along with services like Three and Easy to know what it makes provisioning access, the hard work. It's seconds, you know, not months of procurement, and in a way, we're kind of software is now catching up, and in a way, what marketplace is trying to do is to revolutionize the way people acquire software for the cloud in the same way that eight of us to infrastructure well, and you're creating a to be a consumer dynamic, not unlike my Amazon retail, where there's trust, simplicity, comfort levels on DH. You know, you even don't tell Jeff. I'Ll pay a little bit more from, you know, Amazon website cause I trust it. Yeah, you know, not too much, right? And you guys have to stay price competitive. Absolutely so. But that to me, is that it's that consumer like experience that you're obviously it is more complex but somewhat creating that way looked, we look to retail for all sorts of cool inspiration. You know, on the retail side, they have a retail marketplace, which is huge and thriving business with millions of merchants. And so we're constantly comparing notes and saying, like one of the things that you're doing for your merchants and are the things that can inspire us on our side kind of follow suit. I will note that you know, I when I get in front of customers I like to do, I'd like to show our user experience we have a pretty website and all that other good stuff. The vast majority of customers actually interfaced with us through command line and automation tools and all that other stuff. So retail analogy gets me so developers, >> thank >> you very much for it's really great to have you here, Director A ws marketplace and here mobile. As you say, >> we're in the midst of this transformation. It's really great to hear your story. So thank you very much for two years here >> on the Cube, on the aid everywhere summits in London That's all from us for now.