>> live from New York. It's the Q covering AWS Global Summit 2019 brought to you by Amazon Web service, is >> Welcome back. Rush hours started a little bit early here in New York City, with over 10,000 people in attendance for any of US Summit in New York City. I'm stupid, and my co host for today is Corey Quinn. Having a welcome to the program to first time guests from our host Amazon Web service is to my right. Here is Deepak Singh, who is the director of Compute Service's. To his right is Aaron Cow, Who's the senior manager product marketing Gentlemen, thanks so much for joining us. Thank >> you for having us >> for having us, all right, so we know that every day we wake up and there's new announcements coming from Amazon, and the only way most of us keep up with it is trying to re Cory's newsletter here. But in your group and computer, we know there's a lot going on and quite a few announcements. So, Aaron, what do you kick us off with? Some of the hard news that went >> through this morning? Yeah, we just launched Amazon event. Bridgette's Ah, serverless event boss that allows youto connect your applications with data from sources like sass applications. A devious resource is in your own applications. >> All right, So Deepak would look to dig into that a little bit. I like you said, you that Amazon. You learned a lot from cloudwatch in building this tool. Everybody looking at kind of lambda and the service faces, Like Okay, how all these pieces together is that all? Amazon service is all the time. And, of course, Amazon has a huge ecosystem. But help help us understand a layer down. You know how this works. >> Yeah. So, you know, a dress service send events watchman consumer event from one of the best ways to do it is through Lando. Lando. One of London's biggest trends is the number off integration we have with events both taking in events and triggering event. But to your point there already events inside database system. I think one of the things as a service owner, that really excites me about event. How now? Customers of access, not just two ventricles inside eight of us were awesome apartments extended so that the application you can build will be really exciting. >> Quite a few other announcements maybe August or someone CK >> is another announcement where it's open. Source. Software development framework allows you to model your applications using programming language like typescript Job a python and got that. You know the whole thing with building in the cloud. It's slightly different. You usedto take your coat. Put it on a servant. Run it. Now people are building things a little more distributed. Using a lot of different resource is for their applications, so it's getting provisioning. Your infrastructure is a little bit harder, right? Either Have to do a lot of things manually. Are maybe you're writing. A lot of scripts are using a domain specific language, But with CD Kay, you're now able to use the programming languages that you're hurting your applications with two model and provisions your infrastructure. So it's super helpful. Really think it's gonna help developers increase their development velocity? They're able to use things like loops, conditions, object oriented programming. They don't have to do context switching and just a few lines of code. They're able to do a lot more. All right, >> I want I want a playing with it a little bit when it was in review, and one of things that I found that it was extremely helpful was it was a lot easier for me to write something in using CD kay and then see what that rendered down to in terms of cloud formation. And then, oh, I guess that's how I do it in cloud formation, which was great. The counterpoint, though, is it also felt, at times like it was super wordy. So if I read that what it generates compared to what I normally right, which is admittedly awful. But it's all right, we'll start to feel like I'm doing it wrong with that. And then with amplify and with Sam and the rest. There's a lot of higher level abstractions that build cloud formation for you. But then it renders down in a few different key ways under the hood. How much are these products that you're coming out with starting to shape the direction of confirmation itself? Or is that mostly baked and done? >> There's a lot of products that we're building that you know are complimenting information. Information is the template ing modeling language to provisional abusive resource is put on top of that. We have things like Sam, right? That provides a declared of ATM or high level abstracted declared way to build on topical information. You know, we have amplified also use this information to help you build mobile applications in front development and then finally have see decay for general use other things. They're all complimenting and you know are things customers are asking for helping us >> get the ecosystem. Deepak. The container space, of course, has been You know what one of these tidal waves that we've been watching on It's fundamentally changing the way people architect their applications. That huge impact on your product line Give us the update. If you could just start with some of the high level. Remember first when I talk to you. A couple of years ago, the whole kubernetes piece was sorting out. So you know, e c s E. K s usedto have a much longer name that Cory >> Cory. Finally, you fix the compensation problem where someone was getting compensated based upon number of syllables in a service name. So good on you on that one. >> Right on. Uh, you know, acronym, am I? Maybe you can you know, settle once and for all. You know how how we pronounce that >> I'm old school in love with the Army. >> But what what walk us through? Kind of. You know, your container service is, >> I think, the great thing about container, I said, adoption is everywhere on what we find. It brought a VCs the growth of cares where they're running it on to our fargate. Everything is growing like crazy because people find new interesting ways to run applications based on what they know. One what they're comfortable with their customers. Customers like Snap. There's no community well, and they're building on their building a big chunk of their new infrastructure on kneecaps or need to be with, and it basically helped develop a velocity. On the flip side, your customers like Turner Broadcasting that run a lot of their Web service is the comedy central content properties like that on Fargate because they can just stamp them out. They all you know, it's about time. It's a service that you can just keep expanding. So it boils down to one of the key things that you're comfortable with. One of the reasons you fix something if you are running like snap across. You know, in many different looks places you are likely to choose community and standardize on that. So that's the best part for me is people have choices and then the pic based on what they need. At that point in time, it can be two different teams at the same place. Picking a different solution. I will add that one of the areas that we are focused on now is a dub ability and develop experience, though the areas that our customers have been asking for CD Kay played into that record in the demo this morning. And with the probability with container inside on with the fluid that be announced, I think though that area, they do a lot more >> going forward, right? That was one of those cloudwatch container insights. Just explain what that one is >> so historically, when you do cloudwatch look very bm centric, you're looking at CPU memory. You're zooming application. We are instances run for a particular period of time. At the container world you have service is with the underlying tasks. Come and go all you know, a very different rate container inside. It's meant to be a world aware of the fact that you're containerized application that fast service is and part, they're able to get more fine grained metrics on the things that container customers care about. And you're not trying to use the BM centric language to look at the content. That's the biggest reason for doing that. And then on the floor in bedside Boy, our customers want loud rounding to whatever they want to do it on where they understand three or elasticsearch. We do that with data borrows. So we basically wrote a bunch of open source plug in for fluent, but they just end your log where you want them to go. That's kind of maybe a >> Yeah, I view it as more of a log router than I do. Almost anything else? Yeah, a question of where did it come from? Where does it go? How do you do? Keep straight. It's at this point. What is it out? What is it output to these days of their various destination options? Third party vendors cloudwatch history >> to plug in 14315413 because so many people in the center there with three the other one was like Anita. There. Apart from there, you can send it to read, Chef, you can send it todo you can send it to elasticsearch. So based on what however you want and I'll analyze it, you can send it to a custom resource. So you want you're using some third party provider. You can just send your logs over to those. >> Corey, you know, you're dealing with a lot of customers. You know, there's so many, you know, different instance types and some of some of the pieces. You know, what's the feedback you're giving? You know, Amazon these days >> entire depends upon the service teams, and it ranges from This is amazing. Excellent job, too. Okay, it's a good start, and it's always a question, though. It's when you have what 200 service options are darn near. It at this point aren't 70. It's impossible to wind up with something that is evenly consistent, and you have service is that air sub components of other service is built on top. I mean, I think the uh, I guess the feedback I've been giving almost universally across the board is assume that I am about 20% as smart as you right now seem to think I am and then explain it to me, and then I'll probably understand it a lot better. It comes down to service the storytelling more or less of meeting people of various points along their journey, and that I was mentioning in our editorial session just before this segment that that's something that AWS has markedly improved on the last two or three years, where you have customer stories that are rapidly moving up the up the stack as Faras Leverage Service's It's not just we took the EMS, and now we run them somewhere else. Now it's about building of extremely volume intensive applications on top of a whole bunch of managed service is and these air serious cos these air regulators. It's not just Twitter for pets anymore. >> Nothing wrong with that. No, >> So way were discussing like Enron was a great case this morning, and they talked about in the four years that they've been on, they re architected three times, you know, how do you balance all of these new wins is coming out with, you know, how do we make sure that I deploy something today that I've got the flexibility to change. But, you know, I want to be able to lock in my pricing and make it easier. >> Actually, we think about that quite a bit. One of the reasons we met, the way we did something that sits outside a container orchestrator. What? It doesn't lock you into choosing one or the other or even using an architecture. You can start over the monolith, start putting sidecars on it. It's getting with the ability to all your traffic portions of applications. You can start breaking out. You can put them on target. You can put them on PCs. You can put them on it, too. I think that is something we did very consciously because so many of our customers are in that position. And I think more and more are going to go higher up the stock using managed databases. You think lambda. But it's not decision they need to make all up front. They can do it piecemeal, and we see a custom fender. The good example there done that. >> I think one of the >> philosophies of like eight of us is giving customers building blocks the buildings on, so the whole thing is here's a new primitive that you can use. Then you can take it out, replace something with something else, depending on your needs. So we give customers flexibility and choice. >> And part of the problem is that that very much becomes a double edged sword. I mean, most recently you've had effectively declared war on alphabet. I don't mean the large cloud provider that turns things off for a living. I'm talking about the English alphabet where you take a look at all the different ec2 instance types. I think in US East one. Now there's over. What is it? 100 90 different instances you can pick from. It leads to analysis paralysis. Which one do I pick? What's the right answer? What am I committing to? What am I not? And you see that? That's a microcosm. The larger service problem. I want to build a Web app that does a thing. Which service is do I use? You open up the service listing and you just get this sort of sinking sensation. I get that. I can't imagine what someone new to the space is getting to >> you, and this is where things like amplify fargate aws patch. You don't need to select an instance where you just tell us for your requirements are on Batch makes that collection for you the core building. What's important because you can't really figure out what to do. But then you see us too much more about the attack to help people get there. It's an ongoing thing that will keep trying to tackle, but you see a lot more of that. >> It's controversial. One of my favorite things about Lambda, for example, is there's one knob ram, and as you turn that up, other performance characteristics increase and people complain about it. But I love the simplicity because I don't have to sit and think and make all these different decisions. It's one access, >> but if you want more knob, you can you fuck it. So I think that that's the beauty ofit that you do have that choice. >> Yeah, one lines there, and I really liked it. Borders keynote. Is he said way? Really? You know my words, commoditized. I t We all have access to all of the tools now, you know that was you know what big date originally file. It also was used to have to be a nation state 4100 to be able to do some of these things. So, you know, what do you hear from customers? How do they make sure you know, they're staying competitive and ahead on their four in that relationship between the business and I T. What do you hear from your customers these days? >> In terms of that? Well, I think, um, for you know, for customers like I think of Emperor age is a, uh, a pretty good example off that in terms of customers asking us for ability to, you know, integrate their SAS providers and a great a lot of different things and not have thio you No, no, no. >> I have >> to do a lot of undifferentiated heavy lifting and things like that. And customers are increasingly moving towards, like avenger oven architectures. And they asked us, Hey, we really like cloudwatch events and how you do things with a iittie automation and then bringing SAS providers and on way wantto you know, we don't want to build a polling infrastructure and orderto access athe eyes and do all all the heavy lifting. What we did was we built out way took cloudwatch events and added new features for SAS applications and build that into a separate service for people to use. That's like, you know, a lot of the relationships we have our customers listening to what they need and giving them what they want. >> I think that that's a very valuable thing. We used to say, You know, five years ago you would talk about, you know, let's get rid of indifferent, heavy lifting Well, now it's like, No, no, let's enable you know some thing that you would have thought was heavy lifting and we're daunted to be able to do it. But now hopefully it's easier because a lot of this stuff, you know, he said, This is still a little bit daunting, and you know, you've got a lot of ecosystem and service providers, and service is help us. You take care of, you know, because it's the paradox of choice. With all the options that you >> have on. I think that's the beauty of what I'm in a customer that smart. They managed to find interesting ways to keep challenging us and keep us busy. But I also think that really, really many of them the ones who've been able to be successful. I figured out what it needs to be. Take all the tools to give them which other ones where they want to completely hand it over to AWS and give us the responsibility. And then which ones today really feeling, get they care about and the ones who can find their balance of the ones that we see moving faster. I think that's what we're trying to >> write that one thing that does absolutely permeates virtually every service team I've worked with that AWS. I mean, I've had this experience with you where I talk about how my use case isn't a terrific fit for your product, and your response is always well, what is your use case? It's not. Is starting off on the baseline assumption that my use cases ridiculous, which, let's face it, it probably is. But being able to address a customer need to understand that even if it doesn't dictate, road map is incredibly valuable, and I don't find there are too many players in any space, let alone this one that are willing to have the patience to listen to. Frankly, some loud person wearing a suit. >> Way try. I mean, I think you heard me say this so much like a big junk. 85 90% of a road map. Customer request. I would say that even though remember remaining 10% maybe not think that they're directly asked for but think that you observed their running to or that we run into working with, you know, the one of the customers go ahead of the pack. Okay. They have this problem, Baker. How do you generalize that? And we try and understand what it means. One of the reasons to be made the container road map public was This space is moving so quickly. It's almost impossible for us to talk to enough customers to figure that out. So, like, okay, that gives us an avenue for them to come to us and just tell us and get have >> issues. Yeah, s o right. Final question for both of you directions. Looking forward, you know, the road map we love when there is publicly facing material, not under the NBA's that we normally have to be able to hear. So what are you hearing from your customers? What direction are they pulling you towards and that we should expect tow watch aws kind of a cz we head towards reinvent later this year. Yeah, >> like customers are asking us for different things for developer experience, especially event driven architectures. I think there's gonna be a lot of interesting things happening in the land of space and that entire space >> on to add to that. I think your point earlier helping the simplified choices is going to be a big part of it. Meeting them where they are in their ideas with the cooling is a big part of what you'll see us do. So you know, I think you saw examples today. We'll keep building on top of >> All right. Well, send our congratulations to the two pizza teams that worked on all of the projects that were announced today. Look forward to seeing you. You know, down the road in tracking down. Thanks so much. And welcome to be in Cuba one night having us Deepak, you know, from AWS. He's Cory Quinn on student back with lots more coverage from 80 West Summit here in New York City. Thanks for watching