>> Narrator: From Sand Hill Road, in the heart of Silicon Valley, it's the CUBE. Presenting, The People First Network, insights from entrepreneurs and tech leaders. >> Hello everyone welcome to this special CUBE conversation, I'm John Furrier, host of theCUBE. We're here at Mayfield Fund, on Sand Hill Road and Menlo Park. As part of Mayfield's People First Network, co-creation with SiliconANGLE and theCUBE and Mayfield. Next guest, Beth Devin, Managing Director of Innovation Network and Emerging Technologies at Citi Ventures. Thanks for coming on. >> Thanks for having me. >> Hey, thanks for coming in. We're here for the Mayfield fiftieth anniversary, where they're featuring luminaries like yourself, and we're talking about conversations around how the world's changing and the opportunities and the challenges can be met, and how you can share some of your best practices. Talk about what your role is at Citi Ventures and what your focus is. >> Sure, sure, and boy howdy, has it been changing. It's hard to keep up with. I've been at Citi Ventures about two years and one of the reasons I joined was to stand up an Emerging Technology practice. Citi Ventures does a lot of work in corporate venture investing. We tend to be strategic investors, for start up companies that are aligned with the strategy of Citi, as well as our client. We serve probably, eighty percent of the Fortune Five Hundred companies in the world. But we also are a really important part of the innovation ecosystem at Citi. Which is looking at how to drive culture change, broaden mindset, and really, enlist our employees to be part of the innovation process. So, we have an internal incubator, we have a Shark Tank-like process we call Discover Ten X. And what I really bring to the table with my team is monitoring, and learning about, and digesting technology that's not quite ready for commercialization but we think it might be disruptive in a good or challenging way for the bank or our clients. We try to educate and provide content that's helpful to our executives, and just the employee body at large. >> I want to get into a LinkedIn post you wrote, called the Tech Whisperer, which I love. >> Thank you. >> You're there to identify new things to help people understand what that is. But that's not what you've done. You've actually implemented technology. So, on the other side of the coin, in your career. Tell us about some of the things you've done in your career, because you've been a practitioner. >> Beth: Yeah. >> and now you're identifying trends and technologies, before you were on the other side of the table. >> That's right, and sometimes I'll tell you, I have that itch. I miss the operator role, sometimes. Yeah, you know, I feel so fortunate I sort of stumbled on computer science early when I was going to school. And, the first, I'd say twenty years of my career, were working in enterprise I.T, which at that time I couldn't even have made that distinction, like why do you have to say enterprise I.T. I was a software developer, and I was then a DBA, and I even did assembler language programing. So way back when, I think I was so fortunate to fall in to software engineering. It's like problem solving, or puzzle making, and you with your own brain and sort of typing can figure out these problems. Then over the years I became more of a manager and a leader, and sort of about a reputation for being somebody you could put on any hard problem and I'd figure a way out. You know tell me where we're trying to go it looks knotty, like not a fun project, and I would tackle that. And then I'd say, I had some experience working in lots of different industries. Which really gave me an appreciation, for you know, at the end of the day, we can all debate the role that technology plays in companies. But industries, whether it's health care or media, or financial services. There's a lot of the same challenges that we have. So I worked at Turner Broadcasting before it was acquired, you know by Time Warner and AOL. And I learned about media. And then I had a fantastic time working at Charles Schwab. That was my first big Financial Services role when it came back to the bay area. I worked at Art.Com, it was a need converse company, the first company I worked at where I was in charge of all the technology. We had no brick and mortar, and if the technology wasn't working, we weren't earning revenue, in fact, not only that, we were really making customers angry. I also had a role at a start up, where I was the third person to join the company, and we had a great CEO who had a vision, but it was on paper. And we hadn't really figured out how to build this. I was very proud to assemble a team, get an office, and have a product launch in a year. >> So you're a builder, you're a doer, an assembler, key coding, hexadecimal cord dumps back in the day. >> Way back when. We didn't even have monitors. I'll tell ya, it was a long time ago. >> Glory days, huh? Back when we didn't have shoes on. You know, technology. But what a change. >> Huge change. >> The variety of backgrounds you have, The LinkedIn, the Charles Schwab, I think was during the growth years. >> And the downturn, so we got both sides. >> Both sides of that coin, but again, the technologies were evolving. >> Yes. >> To serve that kind of high frequency customer base. >> Beth: That's right. >> With databases changing, internet getting faster. >> It has. >> Jeff: More people getting online. >> We were early adopters, I'll tell you. I still will tell people, Charles Schwab is one of the best experiences I have, even though at the end I was part of the layoff process. I was there almost seven years, and I watched, we had crazy times in the internet boom. Going in 98, 99, 2000, I can't even tell you some of the experiences we had. And we weren't a digital native. But we were one of the first companies to put trading online, and to build APIs so our customers could self service, and they could do that all online. We did mobile trading. I remember we had to test our software on like twenty different phone sets. Today, it's actually, so much easier. >> It's only three. Or two. Or one. Depending on how you look at it. >> That's right. We couldn't even test on all the phone sets that were out then. But that was such a great experience, and I still, that Schwab network, is still people I'm in touch with today. And we all sort of sprinkled out to different places. I think, I dunno, there's just something special about that company in terms of what we learned, and what we were able to accomplish. >> You have a fantastic background. Again the waves of innovation you have lived through, been apart of, tackling hard problems, taking it head on. Great ethos, great management discipline. Now more than ever, it seems to be needed, because we're living in an age of massive change. Cause you have the databases are changing, the networks changing, the coding paradigms changing. Dev ops, you've got the role of data. Obviously, mobile clearly is proliferated. And now the business models are evolving. Now you got business model action, technical changes, cultural people changes. All of those theaters are exploding with opportunity, but also challenges. What's your take on that as you look at that world? >> You know, I'm a change junkie, I think. I love when things are changing, when organizations are changing, when companies are coming apart and coming together. So for me, I feel like, I've been again, so fortunate I'm in the perfect place. But, one of the things that I really prided myself on early in my career, is being what I call the bridge, or the, the translator between the different lines of business folks that I work with. Whether it was head of marketing, or somebody in a sales or customer relationship, or service organization, and the technology teams I built and led. And I think I've had a natural curiosity about what makes a business tick, and not so much over indexing on the technology itself. So technology is going to come and go, there's going to be different flavors. But actually, how to really take advantage of that technology, to better engage your customers, which as you said, their needs and their demands are changing, their expectations are so high. They really set the pace now. Who would have though that ten years ago we'd live in an environment where industries and businesses are changing because consumers have sort of set the bar on the way we all want to interact, engage, communicate, buy, pay. So there's this huge impact on organizations, and you know, I have a lot of empathy for large established enterprises that are challenged to make it through this transformation, this change, that somehow, they have to make. And I always try to pay attention on which companies have done it. And I call out Microsoft as an example. I can still remember several years ago, being at a conference. I think it was Jeffrey Moore who was speaking, and he had on one slide... Here's all the companies in technology that have had really large success. Leading up to the internet boom days, there would be a recipe for the four companies that would come together. I think it was Sun, Oracle, and Microsoft. And then he said, and now here's the companies of today. And most young people coming out of college, or getting computer science degrees won't use any of these old technology companies. But Microsoft proved us all wrong, but they did it, focused on people, culture, being willing to say where they screwed up, and where they're not going to focus anymore, and part ways with those parts of their business. And really focus on who are their customers, what are their customer needs. I think there's something to be learned from those changes they made. And I think back to the Tech Whisperer, there's no excuse for an executive today, not to at least understand the fundamentals of technology. So many decisions have to be made around investment, capital, hiring, investment in your people. That without that understanding, you're sort of operating blind. >> And this is the thing that I think I love, and was impressed by that Tech Whisperer article. You know, a play on the Horse Whisperer, the movie. You're kind of whispering in the ears of leaders who won't admit that they're scared. But they're all scared! They're all scared. And so they need to get, maybe it's cognitive dissonance around decision making, or they might not trust their lead. Or they don't know what they're talking about So this certainly is there, I would agree with that. But there's dynamics at play, and I want to get your thoughts on this. I think this plays into the Tech Whisperer. The trend we're seeing is the old days was the engineers are out coding away, hey they're out there coding away, look at them coding away. Now with Cloud they're in the front lines. They're getting closer to the customer, the apps are in charge. They're dictating to the infrastructure what can be done. With data almost every solution can be customized. There's no more general purpose. These are the things we talk about, but this changes the personnel equation. Now you got engineering and product people talking to sales and marketing people, business people. >> And customers. >> They tend not to, they traditionally weren't going well. Now they have to work well, engineers want to work with the customers. This is kind of a new business practice, and now I'm a scared executive. Beth, what do I do? What's your thoughts on that dynamic? >> You know, I'm not sure I would have had insight in that if I hadn't had the oppurtunity to work at this little start up, which we were a digital native. And it was the first time I worked in an environment where we did true extreme programming, pair programming, we had really strong product leads, and engineers. So we didn't have project managers, business analysts, a lot of things that I think enterprise I.T tends to have. Because the folks, historically, at an enterprise, the folks that are specifying the need, the business need, are folks in the lines of business. And they're not product managers, and even product managers, I say in banking for example, they aren't software product managers. And so that change, if you really do want to embrace these new methods and dev ops, and a lot of the automation that's available to engineering and software development organizations today, you really do have to make that change. Otherwise it's just going to be a clumsy version of what you use to do, with a new name on it. The other thing though that I would say, is I don't want to discount for large enterprises is partnerships with start up companies or other tech partners. You don't need to build everything. There's so much great technology out there. You brought up the Cloud. Look at how rich these Cloud stacks are getting. You know, it's not just now, can you provision me some compute, and some storage, and help me connect to the internet. There's some pretty sophisticated capabilities in there around A.I and machine learning, and data management, and analysis. So, I think overtime, we'll see richer and richer Cloud stacks, that enables you know, every company to benefit from the technology and innovation that's going on right now. >> Andy Jassy, the CEO of Amazon Web Search, has always said whenever I've interviewed him, he always talks publicly now about it is, two pizza teams, and automate the undifferentiated heavy lifting. In tech we all know what that is, the boring, mundane, patching, provisioning, ugh. And deploying more creative research. Okay so, I believe that. I'm a big believer of that philosophy. But it opens up the role, the question of the roles of the people. That lonely DBA, that you once were, I did some DBA work myself. System admins, storage administrator, these were roles, network administrator, the sacred God of the network, they ran everything. They're evolving to be much more coding oriented, software driven changes. >> It's a huge change. And you know, one thing that I think is sad, is I run into folks often that are, I'll just say, technology professionals, just say, you know, we're at large. Who are out of work. You know, who sort of hang their head, they're not valued, or maybe there's some ageism involved, or they get marked as, oh that's old school, they're not going to change. So, I really do believe we're at a point, where there's not enough resources out there. And so how we invest in talent that's available today, and help people through this change, not everybody is going to make it. It starts with you, knowing yourself, and how open-minded you are. Are you willing to learn, are you willing to put some effort forth, and sort of figuring out some of these new operating models. Because that's just essential if you want to be part of the future. And I'll tell you, it's hard, and it's exhausting. So I don't say this lightly, I just think. You know about my career, how many changes and twists and turns their have been. Sometimes you're just like, okay I'm ready, I'm ready to just go hiking. (Beth laughs) >> It can be, there's a lot of institutional baggage, associated with the role you had, I've heard that before. Old guard, old school, we don't do that, you're way too old for that, we need more women so lets get women in. So there's like a big dynamic around that. And I want to get your thoughts on it because you mentioned ageism, and also women in tech has also grown. There's a need for that. So there's more opportunities now than ever. I mean you go to the cyber security job boards, there are more jobs for cyber security experts than any. >> Oh, I'll tell you, yesterday, we held an event at our office, in partnership with some different start ups. Because that's one of the things you do when you're in a corporate venture group, and it was all on the future of authentication. So it was really targeted at an audience of information security professionals and chief information security officers. And it was twenty men and one woman. And I thought, wow, you know I'm use to that from having been a CIO that a lot of the infrastructure roles in particular, like as you were saying, the rack and stack, the storage management, the network folks, just tend to be more male dominant, than I think the product managers, designers, even software engineers to some extent. But here you know, how many times can you go online and see how many openings there are for that type of role. So I personally, am not pursuing that type of role, so I don't know what all the steps would need to be, to get educated, to get certified, but boy is there a need. And that needs not going to go away. As more, if everything is digitized and everything is online. Then security is going to be a constant concern and sort of dynamic space. >> Well, we interview a lot of women in tech, great to have you on, you're a great leader. We also interview a lot of people that are older. I totally believe that there's an ageism issue out there. I've seen it first hand, maybe because I'm over fifty. And also women in tech, there's more coming but not enough. The numbers speak for themselves. There's also an opportunity, if you look at the leveling up. I talked to a person who was a network engineer, kind of the same thing as him, hanging his head down. And I said, do you realize that networking paradigm is very similar to how cyber works. So a lot of the old is coming back. So if you look at what was in the computer science programs in the eighties. It was a systems thinking. The systems thinking is coming back. So I see that as a great opportunity. But also the aperture of the field of computer science is changing. So it's not, there are some areas that frankly, women are better than men at in my opinion. In my opinion, might get some crap for that. But the point, I do believe that. And there are different roles. So I think it's not just, there's so much more here. >> Oh, that's what I try to tell people. It's not just coding, right. There's so many different types of roles. And unfortunately I think we don't market ourselves well. So I encourage everyone out there that knows somebody. (Beth laughs) Who's looking-- >> If someone was provisioned Sun micro-systems, or mini computers, or workstations, probably has a systems background that could be a Cloud administrator or a Cloud architect. Same concepts. So I want to get your thoughts on women in tech since you're here. What's your thoughts on the industry, how's it going, things you advise, other folks, men and women, that they could do differently. Any good signs? What's your thoughts in general? >> Yeah so, first of all, I'm just a big advocate for women in general. Young girls, and, young women, just getting into the work force, and always have been. Have to say again, very fortunate early in my career working for companies like a phone company, and Schwab, we had so many amazing female leaders. And I don't even think we had a program, it was just sort of part of the DNA of the company. And it's really only in the last couple of years I really seen we have a big problem. Whether it's reading about some of the cultures of some of the big tech companies, or even spending more time in the valley. I think there's no one answer, it's multifaceted. It's education, it's families, it's you know, each one of us could make a difference in how we hire, sort of checking in what our unintended biases are, I know at Citi right now, there's a huge program around diversity and inclusion. Gender, and otherwise. And one of the ways I think it's going to be impactful. They've set targets that I know are controversial, but it holds people accountable, to make decisions and invest in developing people, and making sure there's a pipeline of talent that can step up into even bigger roles with a more diverse leadership team. It will take time though, it will take time. >> But mind shares are critical. >> It absolutely is. Self-awareness, community awareness, very much so. >> What can men do differently, it's always about women in tech, but what can we, what can men do? >> I think it's a great question. I would say, women can do this too. I hate when I see a group together, and it's all women working on the women issue. Shame on us, for not inviting men into the organization. And then I think it's similar to the Tech Whisperer. Don't be nervous, don't be worried, just step in. Because, you know, men are fathers, men are leaders, men are colleagues. They're brothers, they're uncles. We have to work on this together. >> I had a great guest, and friend, I was interviewing. And she was amazing, and she said, John, it's not diversity and inclusion, it's inclusion and diversity. It's I-N-D not D-I. First of all, I've never heard of it, what's D-N-I? My point exactly. Inclusion is not just the diversity piece, inclusion first is inclusive in general, diversity is different. So people tend to blend them. >> Yes they do. >> Or even forget the inclusion part. >> Final question, since you're a change junkie, which I love that phrase, I'm kind of one myself. Change junkies are always chasing that next wave, and you love waves. Pat Gelsinger at VMWare, wave junkie, always love talking with him. And he's a great wave spotter, he sees them early. There's a big set of waves coming in now, pretty clear. Cloud has done it's thing. It's only going to change and get bigger, hybrid, private, multi Cloud. Data, AI, twenty year cycle coming. What waves are you most excited about? What's out there? What waves are obvious, what waves aren't, that you see? >> Yeah, oh, that's a tough one. Cause we try to track what those waves are. I think one of the things that I'm seeing is that as we all get, and I don't just mean people, I mean things. Everything is connected, and everything has some kind of smarts, some kind of small CPU senser. There's no way that our existing, sort of network, infrastructure and the way we connect and talk can support all of that. So I think we're going to see some kind of discontinuous change, where new models are going to, are going to absolutely be required cause we'll sort of hit the limit of how much traffic can go over the internet, and how many devices can we manage. How much automation can the people and an enterprise sort of oversee and monitor, and secure and protect. That's the thing that I feel like it's a tsunami about to hit us. And it's going to be one of these perfect storms. And luckily, I think there is innovation going on around 5G and edge computing, and different ways to think about securing the enterprise. That will help. But it couldn't come soon enough. >> And model also meaning not just technical business. >> Absolutely. Machine the machine. Like who's identity is on there that's taken an action on your behalf, or the companies behalf. You know, we see that already with RPA, these software robots. Who's making sure that they're doing what they're suppose to do. And they're so easy to create, now you have thousands of them. In my mind, it's just more software to manage. >> And a great contrary to Carl Eschenbach, former VMware CEO now at Sequoia, he's on the board of UIPath, they're on the front page of Forbes today, talking about bots. >> Yes, yes, yes, I've heard them speak. >> This is an issue, like is there a verification. Is there a fake bots coming. If there's fake news, fake bots are probably going to come too. >> Absolutely they will. >> This is a reality. >> And we're putting them in the hands of non-engineers to build these bots. Which there's good and bad, right. >> Regulation and policy are two different things, and they could work together. This is going to be a seminal issue for our industry. Is understanding the societal impact, tech for good. Shaping the technologies. This is what a Tech Whisperer has to do. You have a tough job ahead of you. >> But I love it. >> Jeff: Beth thank you for coming on. >> Thank you for having me. >> I'm Jeff Furrier for the People First Network here at Sand Hill Road at Mayfield as part of theCUBE and SiliconANGLE's co-creation with Mayfield Fund, thans for watching.

>> Announcer: Live from New York. It's the Cube. Covering AWS Global Summit 2019. Brought to you by Amazon Web Services. >> Welcome back rush hour's started a little bit early here in New York City with over 10,000 people in attendance for AWS summit in New York City. I'm Stu Miniman, my co host for today is Corey Quinn. Happy to welcome to the program two first time guests from our host, Amazon Web Services. To my right here is Deepak Singh, who's the Director of Compute Services. Sitting to his right is Aaron Kao, who's the Senior Manager of Product Marketing. Gentlemen, thanks so much for joining us. >> Thank you for having us. >> Thank you for having us. >> Alright, 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 read Corey's newsletter here. But in your group in compute, we know there's a lot going on and quite a few announcements. So Aaron, why don't you kick us off with some of the hard news that went through this morning? >> Yeah, we just launched Amazon EventBridge. It's a serverless event boss that allows you to connect your applications with data from sources like SaaS applications, AWS resources and your own applications. >> All right, so Deepak, I would love to dig into that a little bit. Like you said you that Amazon, you've learned a lot from CloudWatch and building this tool. Everybody looking at kind of, you know, Lambda in the serverless space is like, Okay, how are all these pieces going to come together? Is it all Amazon services all the time? And of course, Amazon has a huge ecosystem, but help us understand or layer down you know how this works? >> Yeah so as you know, AWS services send events to CloudWatch events. They consume events from CloudWatch events. One of the best ways to do it is through Lambda. One of Lambda's biggest strengths is the number of integrations we have with event sources, both taking in events and triggering events. But to your point, there are always events inside database ecosystem. And I think one of the things as a service owner that really excites me about EventBridge is how now customers have access not just to event triggers inside AWS, but also to our partners like Zendesk and the applications you can build will be really exciting. >> Alright, quite a few other announcements, maybe walk us through some of them. >> Yeah, CDK is another announcement where it's an open source software development framework that allows you to model your applications using programming language like TypeScript, Java, Python and .net. You know, the whole thing with building in the cloud, it's slightly different. You used to take your code, put it on a server and run it. Now people are building things a little more distributed, using a lot of different resources for their applications. So it's getting, provisioning your infrastructure is a little bit harder, right? You either have to do a lot of things manually or maybe you're writing a lot of scripts or using a domain specific language. But with CDK, you're now able to use the programming languages that you're programming your applications with, to model and provision your infrastructure. So it's super helpful. Really think it's going to 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 with a few lines of code, they're able to do a lot more. >> All right. >> I wound up playing with it a little bit when it was in preview and one of the things that I found that it was extremely helpful was, it was a lot easier for me to write something in using CDK, 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 write, which is admittedly awful, but I almost 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 and key ways. Under the hood, how much are these products that you're coming out with starting to shape the direction of cloud formation itself, or is that mostly baked and done? >> There's a lot of products that we're building that you know, are complementing cloud formation. You know, cloud formation is the templating modeling language to provision AWS resources. But on top of that, we have things like Sam right, that provides a declarative a more high level abstract declarative way to build on top of cloud formation, you know, we have Amplified that also uses cloud formation to help you build mobile applications and front end development. And then finally, you have CDK for just general use. So, these things are all complementing and, you know, things customers are asking for and helping us shape the ecosystem there. >> Yeah, Deepak the container space, of course, has been you know, one of these tidal waves that we've been watching and it's fundamentally changing the way people architect their applications and has huge impact on your product line. Give us the update. If you could just start with some of the high level, I remember first when I talked to you a couple of years ago it was when the whole Kubernetes piece was sorting out. So you know, ECS, EKS, used to have a much longer name that Cory would constantly >> Only for Cory >> Finally you've fixed the compensation problem where someone was getting compensated based upon number of syllables and a service name so good on you on that one. >> Right and you know the acronym A-M-I maybe you can you know settle once and for all you know how how we pronounce that. >> I'm old school it'll always be AMI. (laughs loudly) >> Walk us through kind of, you know your container services. >> I think the great thing about containers is as you said the adoption is everywhere. And what we find is there's a growth of ECS, the growth of EKS whether you're running it on EC2 or Fargate everything is growing like crazy, because people find new interesting ways to run applications based on what they know and what they're comfortable with. We have customers, customers like SNAP that know Kubernetes well and they are building on there're building a big chunk of their new infrastructure on EKS on AWS and it basically helps the developer velocity. On the flip side, you have customers like Turner Broadcasting that run a lot of their web services or the Comedy Central content properties like that on Fargate because they can just stamp them out. They all you know, it's a website, it's a service that they can just keep expanding. So it boils down to what are the key things that you're comfortable with? What are the reasons you've picked something. So if you're running like SNAP across, you know, in many different places, you are likely to choose Kubernetes and standardize on that. So that's the best part for me is, people have choices and then they pick based on what they need at that point in time, which 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 observe ability and developer experience. Those are areas that our customers have been asking for. CDK plays into that you saw in the demo this morning and with observe ability with container insights and with the fluid plugins that we announced. I think those are areas that you'll see us do a lot more going forward. >> So right, that was one of news today, CloudWatch container insights just to explain what that one is. >> So historically, when you do CloudWatch look, it's very BM-centric, you're looking at CPU memory, you assuming an application, instances run for a particular period of time. In the container world, you have services where the underlying tasks come and go, all you know, at a very different rate. CloudWatch container insights is meant to be a world that's aware of the fact that your containerized applications are tasks and services and pods, so you're able to get more fine grained metrics on the things that container customers care about and you're not trying to use BM-centric language to look at a containerized infrastructure. So that's the biggest reason for doing that. And then on the Fluent Bit side was, our customers want log routing to whatever they want to do it on. Whether they want it to send to S3 or the Elasticsearch We do that with Kinesis Data Firehose. So we basically wrote a bunch of open source plugins for Fluent Bit that just send your logs where you want them to go. So that's kind of where we are focused. >> Yeah, I view it as more of a log router than I do almost anything else. >> It is that. >> Yeah. A question of: Where does it come from? Where does it go? How do you keep it straight? >> Yeah. >> It's at this point, what does it output to you these days? Are there are various destination options, third party vendors, CloudWatch, history? >> So we wrote two plugins one was for well three, I don't know. One for S3 because so many people don't understand the data to S3. The other one was a Kinesis Data Firehose. So from there, you can send it to Redshift, you can send it to you can send it to Elasticsearch. So based on what you however you want another analyze it, you can send it to a custom resource that's Kinesis. So, you're using some third party provider, you can just send your logs over to those. >> Yeah, Corey, you know, you're dealing with a lot of customers, you know, there's now so many, you know, different instance types and some of the pieces, you know, what's the feedback you're giving to, you know, Amazon these days? >> Entirely depends upon the service teams and it ranges from this is amazing, excellent job to okay, it's a good start. And it's always a question though, it's when you have what 200 service options or darn near it at this point, 170. It's impossible to wind up with something that is evenly consistent and you have services that are sub components of other services and built on top. I mean, I think the, 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 to storytelling, more or less of meeting people at various points along their journey and then 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 stack as far as leverage services. It's not just we took the VMs and now we run them somewhere else. Now it's about building a high, extremely volume intensive applications on top of a whole bunch of managed services and these are serious companies. These are regulators it's not just Twitter for pets anymore. >> Nothing wrong with that. >> No. >> So, you know, we were discussing, like FINRA was a great case study this morning and they talked about in the four years that they've been on, they've re-architected three times. You know, how do you balance all of these new instances coming out with, you know, and how do I 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. >> So actually, we think about that quite a bit. One of the reasons we built app match the way we did, as something that sits outside the container orchestrator, was it doesn't lock you into choosing one or the other or even choosing an architecture. You can start off with a monolith, start putting side cards on it, getting visibility into all your traffic, then portions of your applications you can start breaking out, you can put them on Fargate, you can put them on ECS, you can put them on the EC2. 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 stack using managed databases, using Lambda, but it's not decision they need to make all up front. They can do it piecemeal, and we see our customers find another good example, they've done that. >> One of the philosophies of it, like AWS is giving customers building blocks to build things 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 190 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's a microcosm of the larger service problem. I want to build a web app that does a thing, which services 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 there. >> All right, and this is where things like Amplify, Fargate, AWS Batch where you don't need to select an instance. Where you just tell us what your requirements are and Batch makes that selection for you. The core building blocks are important because you can't really figure out what to do. But then you'll see us do much more about the stack to help people get there. It's an ongoing thing that will keep trying to tackle but you'll 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. >> Yeah, but if you want more knobs, you can use Fargate. So I think that, that's the beauty of it that you do have that choice. >> Yeah, one of the lines Aaron, I really liked in Werner's keynote is he said, "we've really, you know, my words commoditized IT. "We all have access to all of the tools now." You know, that was, you know what big data originally and cloud also was, you know, you used to have to be a nation state or fortune 100 to be able to do some of these things so, you know, what do you hear from customers? You know, how do they make sure, you know, they're staying competitive and ahead, and therefore, in that relationship between the business and IT, what do you hear from your customers these days? >> In terms of that? Well, I think for, you know, for customers, like I think EventBridge is a, a pretty good example of that, in terms of customers asking us for ability to, you know, integrate their SaaS providers, integrate a lot of different things and not have to, you know, not have to do a lot of undifferentiated heavy lifting and things like that and, you know, customers are increasingly moving towards like event driven architectures and they asked us, hey, we really like CloudWatch events and how you do things with IT automation and then bringing SaaS providers in and, we want to, you know, we don't want to build pulling infrastructure in order to access API's and do all all those heavy liftings. What we did was we built out, we took CloudWatch events and added new features for SaaS applications and built that into a separate service for people to use. So that's like, you know, a lot of the relationships we have with our customers, listening to what they need and giving them what they want. >> And I think that, that's a very valuable thing. You know, we used to say, you know, five years ago, you would talk about, you know, let's get rid of undifferentiated heavy lifting. >> Yeah. >> Well, now it's like, no, no, let's enable, you know, something 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, as Corey said, this is still a little bit daunting and you know, well you've got a lot of ecosystem and service providers and services to help us, you know, take care of, you know, because it's the Paradox of Choice with all the options that you have. >> And I think that's the beauty of what, I mean our customers are smart, they manage to find it interesting ways to keep challenging us and they keep us busy. But I also think that really, really many of them, the ones who have been able to be successful, have figured out what it means to take all the tools we give them, which are the ones where they want to completely hand it over to AWS and give us the responsibility and then which ones do they really feel they care about and the ones who can find their balance are the ones that we see moving the fastest. I think that's what we're trying to do. >> All right, now and one thing that does absolutely permeates virtually every service team I've worked with at AWS, I mean, you I've had this experience with you, where I talked 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 from the baseline assumption that my use case is ridiculous, which let's face it, it probably is. But being able to address a customer need and understand that even if it doesn't dictate roadmap, is incredibly valuable and I don't find that 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. >> We try, I mean, I think you heard Andy say there's so much like a big chunk 85, 90% of our roadmap is customer requests, I would say that even the remaining 10% is maybe not things that they've directly asked for but things that we've observed they've run into or that we've run into working with, you know, the one or two customers who are ahead of the pack. And Okay, they have this problem, how do you generalize that? And we try and understand what it means. One of the reasons we made the container roadmap 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, this gives us an avenue for them to come to us and just tell us, GitHub issues. >> Yeah, so right. Final question I have for both of you. Directionally looking forward, you know, the roadmap, we love when there is publicly facing material not under the NDAs 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 to watch AWS kind of further, as we head towards re:Invent later this year. >> I think customers are asking us for different things for developer experience, especially event driven architectures. I think there's going to be a lot of interesting things happening in the Lambda space and that entire space. >> Yeah and to add to that, I think, to your point earlier, helping them simplify choices is going to be a big part of it. Meeting them where they are, in their IDEs with a tooling is a big part of what you'll see us do. So, you know, I think you saw examples today and we'll keep building on top of those. >> 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. Thanks so much and welcome to being Cube alumni. >> Thank you for have us. >> Thank you for having us on. >> Appreciate it. >> Aaron, Deepak you know, from AWS. He's Corey Quinn, I'm Stu Miniman. Back with lots more coverage from AWS summit, here in New York City, thanks for watching the Cube.

>> 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