(upbeat music) >> Hello, CUBE friends and welcome back to Vegas. Lisa Martin here with John Furrier. This is our third day of coverage of AWS re:Invent. There are somewhere between 50,000 and 60, 70,000 people here. The excitement is palpable. The energy in the room has been on fire since Monday night. John, we love talking, we love re:Invent. We love talking about AWS and it's incredible ecosystem of partners and we're going to be doing that next. >> Yeah, I mean 10 years of theCUBE, we've been here since 2013. Watching it grow as the cloud computing invention. And then the ecosystem has just been growing, growing, growing at the same time innovation. And that's this next segment with the company that we both have covered deeply. Boomi is going to be a great segment. Looking forward to it. >> We have, we have. And speaking of innovation and Boomi, we have a four-time cube guests back with us. Ed Macosky joined us, Chief Innovation Officer at Boomi. And it's great to see you in person. >> Yeah, great to be here. Thanks for having me. >> What's going on at Boomi? I mean, I know up and to the right, continues we'll go this way. What's going on? >> Yeah, we continue to grow. We're really focused with AWS on the cloud and app modernization. Most of our projects and many of our customers are in this modernization journey from an enterprise perspective, moving from on-premises, trying to implement multicloud, hybrid cloud, that sort of thing. But what we're really seeing is this modernization choke point that a lot of our customers are facing in that journey where they just can't get over the hump. And a lot of their, they come to us with failing projects where they're saying, "Hey, I've got maybe this anchor of a legacy data source or applications that I need to bring in temporarily or I need to keep filling that." So we help with integrating these workflows, integrating these applications and help that lift and shift and help our customers projects from failing and quickly bringing themselves to the cloud. >> You know, Ed, we've been talking with you guys for many many years with theCUBE and look at the transition, how the market's evolved. If you look at the innovation going on now, I won't say it's an innovator's dilemma because there's a lot of innovation happening. It's becoming an integrator's dilemma. And I was talking with some of your staff. Booth traffic's up, great leads coming in. You mentioned on the keynote in a slide. I mean, the world spun in the direction of Boomi with all your capabilities around integration, understanding how data works. All the themes here at re:Invent kind of like are in that conversation top track that we've been mentioning and Boomi, you guys have been building around. Explain why that's happening. Am I right? Am I getting that right, or can you share your thoughts? >> Yeah, absolutely. We're in a great spot. I mean, given the way the economy's going today, people are, again, trying to do more with less. But there is this modernization journey that I talked about and there's an explosion of SaaS applications, cloud technologies, data sources, et cetera. And not only is it about integrating data sources and automating workflows, but implementing things at scale, making sure you have high data quality, high data governance, security, et cetera. And Boomi sits right in the middle of providing solutions of all of that to make a business more efficient. Not only that, but you can implement things very very quickly 'cause we're a low-code platform. It's not just about this hardcore technology that's really hard to implement. You can do it really quickly with our platform. >> Speaking of transformation, one of the things John does every year ahead of re:Invent is he gets to sit down with the CEO of re:Invent and really does a great, if you haven't seen it, check it out on siliconangle.com. Really kind of a preview of what we're going to expect at the show. And one of the things Adam said to you was CIOs, CEOs are coming to me not wanting to talk about technology. They want to talk about transformation, business transformation. It's no more, not so much about digital transformation anymore, it's about transforming businesses. Are you hearing customers come to you with the same help us transform our business so we can be competitive, so we can meet customer demand? >> Oh, absolutely. It's no longer about tools and technology and providing people with paint to paint on a canvas. We're offering solutions on the AWS marketplace. We have five solutions that we launched this year to get people up and running very quickly based on business problems from disbursement to lead to cash with Salesforce and NetSuite to business-to-business integrations and EDI dashboarding and that sort of thing. We also have our own marketplace that provide these solutions and give our customers the ability to visualize what they can do with our platform to actually solve business problems. Again, not just about tooling and technology and how to connect things. >> How's the marketplace relationship going for you? Are you guys seeing success there? >> Yeah, we're seeing a lot of success. I mean, in fact, we're going to be doubling down in the next year. We're going to be, we haven't announced it yet, but we're going to be announcing some new solutions. >> John: I guess we're announcing it now. >> No, I'm not going to get to specifics. But we're going to be putting more and more solutions on the marketplace and we're going to be offering more ways to consume and purchase our platform on the marketplace in the next couple of months. >> Ed, talk about what's new with Boomi real quick. I know you guys have new connectors Early Access. What's been announced? What have you guys announced? What's coming? What's the new things folks should pay attention from a product standpoint? >> Yeah, so you mentioned the connectors. We have 32 new connectors. And by the way in our ecosystem, our customers have connected 199,970 unique things. Amazon SQS is one of those in that number. So that's the kind of scale. >> What's the number again? >> 199,970. At least that's the last I checked earlier. >> That's a good recall right there. Exact number. >> It's an exciting number 'cause we're scaling very, very rapidly. But the other things that are exciting are we announced our event streaming service that we want to bring to our cloud. We've relied on partners in the past to do that for us, but it's been a very critical need that our customers have asked for. So we're integrating that into our platform. We're also going to be focusing more and more on our data management capabilities because I mentioned it a little earlier, connecting things, if bad data's going in and bad data's going out, bad data's going everywhere. So we have the tools and capability to govern data, manage data, high quality solutions. So we're going to invest more and more in that 'cause that's what our customers are asking us for. >> Data governance is a challenge for any business in any industry. Too much access is a huge risk, not enough access to the right people means you can't really extract the insights from data to be able to make data-driven decisions. How do you help customers really on that fine line of data governance? >> Very specifically, we have as part of our iPaaS platform, we have a data catalog and data prep capability within the platform itself that gives citizens in the organization the ability to catalog data in a secure way based on what they have capabilities to. But not only that, the integrator can use data catalog to actually catalog the data and understand what needs to be integrated and how they can make their business more efficient by automating the movement of data and sharing the data across the organization. >> On the innovation side, I want to get back to that again because I think this integration innovation angle is something that we talked about with Adams Selipsky in our stories hitting SiliconANGLE right now are all about the partner ecosystems. We've been highlighting some of the bigger players emerging. You guys are out there. You got Databricks, Snowflake, MongoDB where they're partnering with Amazon, but they're not just an ISV, they're platforms. You guys have your own ISVs. You have your own customers. You're doing low-code before no-code is popular. So where are you guys at on that wave? You got a good customer base, share some names. What's going on with the customers? Are they becoming more developer oriented? 'Cause let's face it, your customers that working on Boomi, they're developers. >> Yes. >> And so they got tools. You're enablers, so you're a platform on Amazon. >> We are a platform on Amazon. >> We call that supercloud, but that's where this new shift is happening. What's your reaction to that? >> Yes, so I guess we are a supercloud on Amazon and our customers and our partners are developers of our platforms themselves. So most of our partners are also customers of ours and they will be implementing their own integrations in the backend of their platforms into their backend systems to do things like billing and monitoring of their own usage of their platforms. But with our customers, they're also Amazon customers who are trying to connect in a multicloud way or many times just within the Amazon ecosystem. Or even customers like Kenco and Tim Heger who did a presentation from HealthBridge. They're also doing B2B connectivity to bring information from their partners into their ecosystem within their platform. So we handle all of the above. So now we are an independent company and it's nice to be a central part of all of these different ecosystems. And where I find myself in my role a lot of times is literally connecting different platforms and applications and SI partners to solve these problems 'cause nobody can really see it themselves. I had a conversation earlier today where someone would say, "Hey, you're going to talk with that SI partner later today. They're a big SI partner of ours. Why don't they develop solutions that we can go to market together to solve problems for our customers?" >> Lisa, this is something that we've been talking about a lot where it's an and conversation. My big takeaway from Adam's one-on-one and re:Invent so far is they're not mutually exclusive. There's an and. You can be an ISV and this platforms in the ecosystem because you're enabling software developers, ISV as they call it. I think that term is old school, but still independent software vendors. That's not a platform. They can coexist and they are, but they're becoming on your platform. So you're one of the most advanced Amazon partners. So as cloud grows and we mature and what, 13 years old Amazon is now, so okay, you're becoming bigger as a platform. That's the next wave. What happens in that next five years from there? What happens next? Because if your platform continues to grow, what happens next? >> So for us, where we're going is connecting platform providers, cloud providers are getting bigger. A lot of these cloud providers are embracing partnerships with other vendors and things and we're helping connect those. So when I talk about business-to-business and sharing data between those, there are still some folks that have legacy applications that need to connect and bring things in and they're just going to ride them until they go away. That is a requirement, but at some point that's all going to fall by the wayside. But where the industry is really going for us is it is about automation and quickly automating things and again, doing more with less. I think Tim Heger had a quote where he said, "I don't need to use Michelangelo to come paint my living room." And that's the way he thinks about low-code. It's not about, you don't want to just sit there and code things and make an art out of coding. You want to get things done quickly and you want to keep automating your business to keep pushing things forward. So a lot of the things we're looking at is not just about connecting and automating data transformation and that's all valuable, but how do I get someone more productive? How do I automate the business in an intelligent way more and more to push them forward. >> Out of the box solutions versus platforms. You can do both. You can build a platform. >> Yes. >> Or you can just buy out of the box. >> Well, that's what's great about us too is because we don't just provide solutions. We provide solutions many times as a starting point or the way I look at it, it's art of the possible a lot of what we give 'cause then our customers can take our low-code tooling and say, wow, I like this solution, but I can really take it to the next step, almost in like an open source model and just quickly iterate and drive innovation that way. And I just love seeing our, a lot of it for me is just our ecosystem and our partners driving the innovation for us. >> And driving that speed for customers. When I had the chance to interview Tim Heger myself last month and he was talking about Boomi integration and Flow are enabling him to do integration 10x faster than before and HealthBridge built their business on Boomi. They didn't replace the legacy solution, but he had experience with some of your big competitors and chose Boomi and said, "It is 10x faster." So he's able to deliver to those and it's a great business helping people pay for health issues if they don't have the funds to do that. So much faster than they could have if had they chosen a different technology. >> Yeah, and also what I like about the HealthBridge story is you said they started with Boomi's technology. So I like to think we scale up and scale down. So many times when I talk to prospects or new customers, they think that our technology is too advanced or too expensive or too big for them to go after and they don't think they can solve these problems like we do with enterprises. We can start with you as a startup going with SaaS applications, trying to be innovative in your organization to automate things and scale. As you scale the company will be right there along with you to scale into very very advanced solutions all in a low-code way. >> And also helping folks to scale up and down during what we're facing these macroeconomic headwinds. That's really important for businesses to be able to do for cost optimization. But at the end of the day, that company has to be a data company. They have to be able to make sure that the data matches. It's there. They know what they have. They can actually facilitate communications, conversations and deliver the end user customer is demanding whether it's a retailer, a healthcare organization, a bank, you name it. >> Exactly. And another thing with today's economy, a lot of people forget with integration or automation tooling, once you get things implemented, in many traditional forms you got to manage that long term. You have to have a team to do that. Our technology runs autonomously. I hear from our customers over and over again. I just said it, sometimes I'll walk away for a month and come back and wow, Boomi's still running. I didn't realize it. 'Cause we have technology that continues to patch itself, heal itself, continue running autonomously. That also saves in a time like now where you don't have to worry about sending teams out to patch and upgrade things on a continuous basis. We take care of that for our customers. >> I think you guys can see a lot of growth with this recession and looming. You guys fit well in the marketplace. As people figure out how to right size, you guys fit right nicely into that equation. I got to ask you, what's ahead for 2023 for Boomi? What can we expect to see? >> Yeah, what's ahead? I briefly mentioned it earlier, but the new service we're really excited about that 'cause it's going to help our customers to scale even further and bring more workloads into AWS and more workloads that we can solve challenges for our customers. We've also got additional solutions. We're looking at launching on AWS marketplace. We're going to continue working with SIs and GSIs and our ISV ecosystem to identify more and more enterprise great solutions and verticals and industry-based solutions that we can take out of the box and give to our customers. So we're just going to keep growing. >> What are some of those key verticals? Just curious. >> So we're focusing on manufacturing, the financial services industry. I don't know, maybe it's vertical, but higher ed's another big one for us. So we have over a hundred universities that use our technology in order to automate, grant submissions, student management of different aspects, that sort of thing. Boise State is one of them that's modernized on AWS with Boomi technology. So we're going to continue rolling in that front as well. >> Okay. Is it time for the challenge? >> It's time for the challenge. Are you ready for the challenge, Ed? We're springing this on you, but we know you so we know you can nail this. >> Oh no. >> If you were going to create your own sizzle reel and we're creating sizzle reel that's going to go on Instagram reels and you're going to be a star of it, what would that sizzle reel say? Like if you had a billboard or a bumper sticker, what's that about Boomi boom powerful story? >> Well, we joked about this earlier, but I'd have to say, Go Boomi it. This isn't real. >> Go Boomi it, why? >> Go Boomi it because it's such a succinct way of saying our customer, that terminology came to us from our customers because Boomi becomes a verb within an organization. They'll typically start with us and they'll solve an integration challenge or something like that. And then we become viral in a good way with an organization where our customers, Lisa, you mentioned it earlier before the show, you love talking to our customers 'cause they're so excited and happy and love our technology. They just keep finding more ways to solve challenges and push their business forward. And when a problem comes up, an employee will typically say to another, go Boomi it. >> When you're a verb, that's a good thing. >> Ed: Yes it is. >> Splunk, go Splunk it. That was a verb for log files. Kleenex, tissue. >> Go Boomi it. Ed, thank you so much for coming back on your fourth time. So next time we see you will be fifth time. We'll get you that five-timers club jacket like they have on SNL next time. >> Perfect, can't wait. >> We appreciate your insight, your time. It's great to hear what's going on at Boomi. We appreciate it. >> Ed: Cool. Thank you. >> For Ed Macosky and John Furrier, I'm Lisa Martin. You're watching theCUBE, the leader in live enterprise and emerging tech coverage. (upbeat music)

(upbeat music) >> Hello, friends. Welcome back to The Cube's live coverage of AWS re:Invent 2022. We're in Vegas. Lovely Las Vegas. Beautiful outside, although I have only seen outside today once, but very excited to be at re:Invent. We're hearing between 50,000 and 70,000 attendees and it's insane, but people are ready to be back. This morning's keynote by CEO Adam Selipsky was full of great messages, big focus on data, customers, partners, the ecosystem. So excited. And I'm very pleased to welcome back one of our alumni to the program, David Shacochis, VP Enterprise Portfolio Strategy Product Management at Lumen. David, welcome back. >> Lisa, good to be here. The Five Timers Club. >> You are in the Five Timers Club. This is David's fifth appearance on the show. And we were talking before we went live- >> Do we do the jacket now and do we do the jacket later? >> Yeah, the jacket will come later. >> Okay. >> The Five Timers Club, like on SNL. We're going to have that for The Cube. We'll get you measured up and get that all fitted for you. >> That'd be better. >> So talk a little bit about Lumen. 'Cause last time you hear it wasn't Lumen. >> We weren't Lumen last time. So this is the first time... last time we were here on The Cube at re:Invent. This was probably 2019 or so. We were a different company. The company was called CenturyLink back then. We rebranded in 2020 to really represent our identity as a delivery of...as a solutions provider over our fiber network. So Lumen is the corporate brand, the company name. It represents basically a lot of the fiber that's been laid throughout the world and in North America and in enterprise metropolitan areas over the past 10 to 15 years. You know, companies like CenturyLink and Quest and Level 3, all those companies have really rolled up into building that core asset of the network. So Lumen is really the brand for the 21st century for the company, really focused on delivering services for the enterprise and then delivering a lot of value added services around that core network asset. >> So rebranding during the pandemic, what's been the customer feedback and sentiment? >> Yeah, I think customers have really actually appreciated it as certainly a more technology oriented brand, right? Sort of shifting away a little bit from some of the communications and telecom background of the company and the heritage. And while those assets that were built up during that period of time have been substantial, and we still build off of those assets going forward, really what a lot of the customer feedback has been is that it puts us in a posture to be a little bit more of a business solutions provider for customers, right? So there's a lot of things that we can do with that core network asset, the fiber networking a lot of the services that we launch on that in terms of public IP, you know, public internet capacity, private networking, private VPNs, VoIP and voice services. These are services that you'd expect from a company like that. But there's a lot of services inside the Lumen brand that you might surprise you, right? There's an edge computing capability that can deliver five milliseconds of latency within 95% of North American enterprise. >> Wow. >> There's a threat detection lab that goes and takes all of the traffic flowing over the public side of our network and analyzes it in a data lake and turns it into threat intelligence that we then offer off to our customers on a subscription basis. There's a production house that goes and, you know, does production networking for major sports arenas and sports events. There's a wide range of services inside of Lumen that really what the Lumen brand allows us to do is start talking about what those services can do and what networking can do for our customers in the enterprise in a more comprehensive way. >> So good changes, big brand changes for Lumen in the last couple of years. Also, I mean, during a time of such turmoil in the world, we've seen work change dramatically. You know, everybody...companies had to pivot massively quickly a couple years ago. >> Yep. >> Almost approaching three years ago, which is crazy amazing to be digital because they had to be able to survive. >> They did >> Now they're looking at being able to thrive, but now we're also in this hybrid work environment. The future of work has changed. >> Totally. >> Almost permanently. >> Yep. >> How is Lumen positioned to address some of the permanent changes to the work environments? Like the last time we were at re:Invented- >> Yeah. >> In person. This didn't exist. >> That's right. So really, it's one of the things we talk to our customers almost the most about is this idea of the future of work. And, you know, we really think about the future of work as about, you know, workers and workloads and the networks that connect them. You think about how much all of those demands are shifting and changing, right? What we were talking about, and it's very easy for all of us to conceptualize what the changing face of the worker looks like, whether those are knowledge workers or frontline workers the venues in which people are working the environments and that connectivity, predictability of those work desk environments changes so significantly. But workloads are changing and, you know we're sitting here at a trade show that does nothing but celebrate the transformation of workloads. Workloads running in ways in business logic and capturing of data and analysis of data. The changing methodologies and the changing formats of workloads, and then the changing venues for workloads. So workloads are running in places that never used to be data centers before. Workloads are running in interesting places and in different and challenging locations for what didn't used to be the data center. And so, you know, the workloads and the workloads are in a very dynamic situation. And the networks that connect them have to be dynamic, and they have to be flexible. And that's really why a lot of what Lumen invests in is working on the networks that connect workers and workloads both from a visibility and a managed services perspective to make sure that we're removing blind spots and then removing potential choke points and capacity issues, but then also being adaptable and dynamic enough to be able to go and reconfigure that network to reach all of the different places that, you know, workers and workloads are going to evolve into. What you'll find in a lot of cases, you know, the workers...a common scenario in the enterprise. A 500 person company with, you know, five offices and maybe one major facility. You know, that's now a 505 office company. >> Right. >> Right? The challenge of the network and the challenge of connecting workers and workloads is really one of the main conversations we have with our customers heading into this 21st century. >> What are some of the things that they're looking forward to in terms of embracing the future of work knowing this is probably how it's going to remain? >> Yeah, I think companies are really starting to experiment carefully and start to think about what they can do and certainly think about what they can do in the cloud with things like what the AWS platform allows them to do with some of the AWS abstractions and the AWS services allow them to start writing software for, and they're starting to really carefully, but very creatively and reach out into their you know, their base of enterprise data, their base of enterprise value to start running some experiments. We actually had a really interesting example of that in a session that Lumen shared here at re:Invent yesterday. You know, for the few hundred people that were there. You know, I think we got a lot of great feedback. It was really interesting session about the...really gets at this issue of the future of work and the changing ways that people are working. It actually was a really cool use case we worked on with Major League Baseball, Fox Sports, and AWS with the... using the Lumen network to essentially virtualize the production truck. Right? So you've all heard that, you know, the sports metaphor of, you know, the folks in the booth were sitting there started looking down and they're saying, oh great job by the guys or the gals in the truck. >> Yep. >> Right? That are, you know, that bring in that replay or great camera angle. They're always talking about the team and their production truck. Well, that production truck is literally a truck sitting outside the stadium. >> Yep. >> Full of electronics and software and gear. We were able to go and for a Major League Baseball game in...back in August, we were able to go and work with AWS, using the Lumen network, working with our partners and our customers at Fox Sports and virtualize all of that gear inside the truck. >> Wow. That's outstanding. >> Yep. So it was a live game. You know, they simulcast it, right? So, you know, we did our part of the broadcast and many hundreds of people, you know, saw that live broadcast was the first time they tried doing it. But, you know, to your point, what are enterprises doing? They're really starting to experiment, sort to push the envelope, right? They're kind of running things in new ways, you know, obviously hedging their bets, right? And sort of moving their way and sort of blue-green testing their way into the future by trying things out. But, you know, this is a massive revenue opportunity for a Major League Baseball game. You know, a premier, you know, Sunday night baseball contest between the Yankees and the Cardinals. We were able to go and take the entire truck, virtualize it down to a small rack of connectivity gear. Basically have that production network run over redundant fiber paths on the Lumen network up into AWS. And AWS is where all that software worked. The technical director of the show sitting in his office in North Carolina. >> Wow. >> The sound engineer is sitting in, you know, on his porch in Connecticut. Right? They were able to go and do the work of production anywhere while connected to AWS and then using the Lumen network, right? You know, the high powered capabilities of Lumens network underlay to be able to, you know, go and design a network topology and a worked topology that really wasn't possible before. >> Right. It's nice to hear, to your point, that customers are really embracing experimentation. >> Right. >> That's challenging to, obviously there was a big massive forcing function a couple of years ago where they didn't have a choice if they wanted to survive and eventually succeed and grow. >> Yeah. >> But the mindset of experimentation requires cultural change and that's a hard thing to do especially for I would think legacy organizations like Major League Baseball, but it sounds like they have the appetite. >> Yeah. They have the interest. >> They've been a fairly innovative organization for some time. But, you know, you're right. That idea of experimenting and that idea of trying out new things. Many people have observed, right? It's that forcing function of the pandemic that really drove a lot of organizations to go and make a lot of moves really quickly. And then they realized, oh, wait a minute. You know... I guess there's some sort of storytelling metaphor in there at some point of people realizing, oh wait, I can swim in these waters, right? I can do this. And so now they're starting to experiment and push the envelope even more using platforms like AWS, but then using a lot of the folks in the AWS partner network like Lumen, who are designing and sort of similarly inspired to deliver, you know, on demand and virtualized and dynamic capabilities within the core of our network and then within the services that our network can and the ways that our network connects to AWS. All of that experimentation now is possible because a lot of the things you need to do to try out the experiment are things you can get on demand and you can kind of pat, you can move back, you can learn. You can try new things and you can evolve. >> Right. >> Yep. >> Right. Absolutely. What are some of the things that you're excited about as, you know, here was this forcing function a couple years ago, we're coming out of that now, but the world has changed. The future of work as you are so brilliantly articulated has changed permanently. What are you excited about in terms of Lumen and AWS going forward? As we saw a lot of announcements this morning, big focus on data, vision of AWS is really that flywheel with Adams Selipsky is really, really going. What are you excited about going forward into 2023? >> Yeah, I mean we've been working with AWS for so long and have been critical partners for so long that, you know, I think a lot of it is continuation of a lot of the great work we've been doing. We've been investing in our own capabilities around the AWS partner network. You know, we're actually in a fairly unique position, you know, and we like to think that we're that unique position around the future of work where between workers, workloads and the networks that connect them. Our fingers are on a lot of those pulse points, right? Our fingers are on at really at the nexus of a lot of those dynamics. And our investment with AWS even puts us even more so in a position to go where a lot of the workloads are being transformed, right? So that's why, you know, we've invested in being one of the few network operators that is in the AWS partner network at the advanced tier that have the managed services competency, that have the migration competency and the network competency. You can count on one hand the number of network operators that have actually invested at that level with AWS. And there's an even smaller number that is, you know, based here in the United States. So, you know, I think that investment with AWS, investment in their partner programs and then investment co-innovation with AWS on things like that MLB use case really puts us in a position to keep on doing these kinds of things within the AWS partner network. And that's one of the biggest things we could possibly be excited about. >> So what does the go to market look like? Is it Lumen goes in, brings in AWS, vice versa? Both? >> Yeah, so a lot of being a member of the AWS partner network you have a lot of flexibility. You know, we have a lot of customers that are, you know, directly working with AWS. We have a lot of customers that would basically look to us to deliver the solution and, you know, and buy it all as a complete turnkey capability. So we have customers that do both. We have customers that, you know, just look to Lumen for the Lumen adjacent services and then pay, you know, pay a separate bill with AWS. So there's a lot of flexibility in the partner network in terms of what Lumen can deliver as a service, Lumen can deliver as a complete solution and then what parts of its with AWS and their platform factors into on an on-demand usage basis. >> And that would all be determined I imagine by what the customer really needs in their environment? >> Yeah, and sort of their own cloud strategy. There's a lot of customers who are all in on AWS and are really trying to driving and innovating and using some of the higher level services inside the AWS platform. And then there are customers who kind of looked at AWS as one of a few cloud platforms that they want to work with. The Lumen network is compatible and connected to all of them and our services teams are, you know, have the ability to go and let customers sort of take on whatever cloud posture they need. But if they are all in on AWS, there's, you know. Not many networks better to be on than Lumen in order to enable that. >> With that said, last question for you is if you had a bumper sticker or a billboard. Lumen's rebranded since we last saw you. What would that tagline or that phrase of impact be on that bumper sticker? >> Yeah, I'd get in a lot of trouble with our marketing team if I didn't give the actual bumper sticker for the company. But we really think of ourselves as the platform for amazing things. The fourth industrial revolution, everything going on in terms of the future of work, in terms of the future of industrial innovation, in terms of all the data that's being gathered. You know, Adam in the keynote this morning really went into a lot of detail on, you know, the depth of data and the mystery of data and how to harness it all and wrangle it all. It requires a lot of networking and a lot of connectivity. You know, for us to acquire, analyze and act on all that data and Lumen's platform for amazing things really helps forge that path forward to that fourth industrial revolution along with great partners like AWS. >> Outstanding. David, it's been such a pleasure having you back on The Cube. We'll get you fitted for that five timers club jacket. >> It sounds good. (Lisa laughs) >> I'll be back. >> Thanks so much for your insights and your time and well done with what you guys are doing at Lumen and AWS. >> Thanks Lisa. >> For David Shacochis, I'm Lisa Martin. You've been watching The Cube hopefully all day. This is our first full day of coverage at AWS re:Invent '22. Stick around. We'll be back tomorrow, and we know we're going to see you then. Have a great night. (upbeat music)

(upbeat music) >> Hello, everyone and welcome back to fabulous Las Vegas, Nevada, where we are here on the show floor at AWS re:Invent. We are theCUBE. I am Savannah Peterson, joined with John Furrier. John, afternoon, day two, we are in full swing. >> Yes. >> What's got you most excited? >> Just got lunch, got the food kicking in. No, we don't get coffee. (Savannah laughing) >> Way to bring the hype there, John. >> No, there's so many people here just in Amazon. We're back to 2019 levels of crowd. The interest levels are high. Next gen, cloud security, big part of the keynote. This next segment, I am super excited about. CUBE Alumni, going back to 2013, 10 years ago he was on theCUBE. Now, 10 years later we're at re:Invent, looking forward to this guest and it's about security, great topic. >> I don't want to delay us anymore, please welcome Mark. Mark, thank you so much for being here with us. Massive day for you and the team. I know you oversee three different units at Amazon, Inspector, Detective, and the most recently announced, Security Lake. Tell us about Amazon Security Lake. >> Well, thanks Savannah. Thanks John for having me. Well, Security Lake has been in the works for a little bit of time and it got announced today at the keynote as you heard from Adam. We're super excited because there's a couple components that are really unique and valuable to our customers within Security Lake. First and foremost, the foundation of Security Lake is an open source project we call OCFS, Open Cybersecurity Framework Schema. And what that allows is us to work with the vendor community at large in the security space and develop a language where we can all communicate around security data. And that's the language that we put into Security Data Lake. We have 60 vendors participating in developing that language and partnering within Security Lake. But it's a communal lake where customers can bring all of their security data in one place, whether it's generated in AWS, they're on-prem, or SaaS offerings or other clouds, all in one location in a language that allows analytics to take advantage of that analytics and give better outcomes for our customers. >> So Adams Selipsky big keynote, he spent all the bulk of his time on data and security. Obviously they go well together, we've talked about this in the past on theCUBE. Data is part of security, but this security's a little bit different in the sense that the global footprint of AWS makes it uniquely positioned to manage some security threats, EKS protection, a very interesting announcement, runtime layer, but looking inside and outside the containers, probably gives extra telemetry on some of those supply chains vulnerabilities. This is actually a very nuanced point. You got Guard Duty kind of taking its role. What does it mean for customers 'cause there's a lot of things in this announcement that he didn't have time to go into detail. Unpack all the specifics around what the security announcement means for customers. >> Yeah, so we announced four items in Adam's keynote today within my team. So I'll start with Guard Duty for EKS runtime. It's complimenting our existing capabilities for EKS support. So today Inspector does vulnerability assessment on EKS or container images in general. Guard Duty does detections of EKS workloads based on log data. Detective does investigation and analysis based on that log data as well. With the announcement today, we go inside the container workloads. We have more telemetry, more fine grain telemetry and ultimately we can provide better detections for our customers to analyze risks within their container workload. So we're super excited about that one. Additionally, we announced Inspector for Lambda. So Inspector, we released last year at re:Invent and we focused mostly on EKS container workloads and EC2 workloads. Single click automatically assess your environment, start generating assessments around vulnerabilities. We've added Lambda to that capability for our customers. The third announcement we made was Macy sampling. So Macy has been around for a while in delivering a lot of value for customers providing information around their sensitive data within S3 buckets. What we found is many customers want to go and characterize all of the data in their buckets, but some just want to know is there any sensitive data in my bucket? And the sampling feature allows the customer to find out their sensitive data in the bucket, but we don't have to go through and do all of the analysis to tell you exactly what's in there. >> Unstructured and structured data. Any data? >> Correct, yeah. >> And the fourth? >> The fourth, Security Data Lake? (John and Savannah laughing) Yes. >> Okay, ocean theme. data lake. >> Very complimentary to all of our services, but the unique value in the data lake is that we put the information in the customer's control. It's in their S3 bucket, they get to decide who gets access to it. We've heard from customers over the years that really have two options around gathering large scale data for security analysis. One is we roll our own and we're security engineers, we're not data engineers. It's really hard for them to build these distributed systems at scale. The second one is we can pick a vendor or a partner, but we're locked in and it's in their schemer and their format and we're there for a long period of time. With Security Data Lake, they get the best of both worlds. We run the infrastructure at scale for them, put the data in their control and they get to decide what use case, what partner, what tool gives them the most value on top of their data. >> Is that always a good thing to give the customers too much control? 'Cause you know the old expression, you give 'em a knife they play with and they they can cut themselves, I mean. But no, seriously, 'cause what's the provisions around that? Because control was big part of the governance, how do you manage the security? How does the customer worry about, if I have too much control, someone makes a mistake? >> Well, what we finding out today is that many customers have realized that some of their data has been replicated seven times, 10 times, not necessarily maliciously, but because they have multiple vendors that utilize that data to give them different use cases and outcomes. It becomes costly and unwieldy to figure out where all that data is. So by centralizing it, the control is really around who has access to the data. Now, ultimately customers want to make those decisions and we've made it simple to aggregate this data in a single place. They can develop a home region if they want, where all the data flows into one region, they can distribute it globally. >> They're in charge. >> They're in charge. But the controls are mostly in the hands of the data governance person in the company, not the security analyst. >> So I'm really curious, you mentioned there's 60 AWS partner companies that have collaborated on the Security lake. Can you tell us a little bit about the process? How long does it take? Are people self-selecting to contribute to these projects? Are you cherry picking? What does that look like? >> It's a great question. There's three levels of collaboration. One is around the open source project that we announced at Black Hat early in this year called OCSF. And that collaboration is we've asked the vendor community to work with us to build a schema that is universally acceptable to security practitioners, not vendor specific and we've asked. >> Savannah: I'm sorry to interrupt you, but is this a first of its kind? >> There's multiple schemes out there developed by multiple parties. They've been around for multiple years, but they've been built by a single vendor. >> Yeah, that's what I'm drill in on a little bit. It sounds like the first we had this level of collaboration. >> There's been collaborations around them, but in a handful of companies. We've really gone to a broad set of collaborators to really get it right. And they're focused around areas of expertise that they have knowledge in. So the EDR vendors, they're focused around the scheme around EDR. The firewall vendors are focused around that area. Certainly the cloud vendors are in their scope. So that's level one of collaboration and that gets us the level playing field and the language in which we'll communicate. >> Savannah: Which is so important. >> Super foundational. Then the second area is around producers and subscribers. So many companies generate valuable security data from the tools that they run. And we call those producers the publishers and they publish the data into Security Lake within that OCSF format. Some of them are in the form of findings, many of them in the form of raw telemetry. Then the second one is in the subscriber side and those are usually analytic vendors, SIM vendors, XDR vendors that take advantage of the logs in one place and generate analytic driven outcomes on top of that, use cases, if you will, that highlight security risks or issues for customers. >> Savannah: Yeah, cool. >> What's the big customer focus when you start looking at Security Lakes? How do you see that planning out? You said there's a collaboration, love the open source vibe on that piece, what data goes in there? What's sharing? 'Cause a big part of the keynote I heard today was, I heard clean rooms, I've cut my antenna up. I'd love to hear that. That means there's an implied sharing aspect. The security industry's been sharing data for a while. What kind of data's in that lake? Give us an example, take us through. >> Well, this a number of sources within AWS, as customers run their workloads in AWS. We've identified somewhere around 25 sources that will be natively single click into Amazon Security Lake. We were announcing nine of them. They're traditional network logs, BBC flow, cloud trail logs, firewall logs, findings that are generated across AWS, EKS audit logs, RDS data logs. So anything that customers run workloads on will be available in data lake. But that's not limited to AWS. Customers run their environments hybridly, they have SaaS applications, they use other clouds in some instances. So it's open to bring all that data in. Customers can vector it all into this one single location if they decide, we make it pretty simple for them to do that. Again, in the same format where outcomes can be generated quickly and easily. >> Can you use the data lake off on premise or it has to be in an S3 in Amazon Cloud? >> Today it's in S3 in Amazon. If we hear customers looking to do something different, as you guys know, we tend to focus on our customers and what they want us to do, but they've been pretty happy about what we've decided to do in this first iteration. >> So we got a story about Silicon Angle. Obviously the ingestion is a big part of it. The reporters are jumping in, but the 53rd party sources is a pretty big number. Is that coming from the OCSF or is that just in general? Who's involved? >> Yeah, OCSF is the big part of that and we have a list of probably 50 more that want to join in part of this. >> The other big names are there, Cisco, CrowdStrike, Peloton Networks, all the big dogs are in there. >> All big partners of AWS, anyway, so it was an easy conversation and in most cases when we started having the conversation, they were like, "Wow, this has really been needed for a long time." And given our breadth of partners and where we sit from our customers perspective in the center of their cloud journey that they've looked at us and said, "You guys, we applaud you for driving this." >> So Mark, take us through the conversations you're having with the customers at re:Inforce. We saw a lot of meetings happening. It was great to be back face to face. You guys have been doing a lot of customer conversation, security Data Lake came out of that. What was the driving force behind it? What were some of the key concerns? What were the challenges and what's now the opportunity that's different? >> We heard from our customers in general. One, it's too hard for us to get all the data we need in a single place, whether through AWS, the industry in general, it's just too hard. We don't have those resources to data wrangle that data. We don't know how to pick schema. There's multiple ones out there. Tell us how we would do that. So these three challenges came out front and center for every customer. And mostly what they said is our resources are limited and we want to focus those resources on security outcomes and we have security engines. We don't want to focus them on data wrangling and large scale distributed systems. Can you help us solve that problem? And it came out loud and clear from almost every customer conversation we had. And that's where we took the challenge. We said, "Okay, let's build this data layer." And then on top of that we have services like Detective and Guard Duty, we'll take advantage of it as well. But we also have a myriad of ISV third parties that will also sit on top of that data and render out. >> What's interesting, I want to get your reaction. I know we don't have much time left, but I want to get your thoughts. When I see Security Data Lake, which is awesome by the way, love the focus, love how you guys put that together. It makes me realize the big thing in re:Invent this year is this idea of specialized solutions. You got instances for this and that, use cases that require certain kind of performance. You got the data pillars that Adam laid out. Are we going to start seeing more specialized data lakes? I mean, we have a video data lake. Is there going to be a FinTech data lake? Is there going to be, I mean, you got the Great Lakes kind of going on here, what is going on with these lakes? I mean, is that a trend that Amazon sees or customers are aligning to? >> Yeah, we have a couple lakes already. We have a healthcare lake and a financial lake and now we have a security lake. Foundationally we have Lake Formation, which is the tool that anyone can build a lake. And most of our lakes run on top of Lake Foundation, but specialize. And the specialization is in the data aggregation, normalization, enridgement, that is unique for those use cases. And I think you'll see more and more. >> John: So that's a feature, not a bug. >> It's a feature, it's a big feature. The customers have ask for it. >> So they want roll their own specialized, purpose-built data thing, lake? They can do it. >> And customer don't want to combine healthcare information with security information. They have different use cases and segmentation of the information that they care about. So I think you'll see more. Now, I also think that you'll see where there are adjacencies that those lakes will expand into other use cases in some cases too. >> And that's where the right tools comes in, as he was talking about this ETL zero, ETL feature. >> It be like an 80, 20 rule. So if 80% of the data is shared for different use cases, you can see how those lakes would expand to fulfill multiple use cases. >> All right, you think he's ready for the challenge? Look, we were on the same page. >> Okay, we have a new challenge, go ahead. >> So think of it as an Instagram Reel, sort of your hot take, your thought leadership moment, the clip we're going to come back to and reference your brilliance 10 years down the road. I mean, you've been a CUBE veteran, now CUBE alumni for almost 10 years, in just a few weeks it'll be that. What do you think is, and I suspect, I think I might know your answer to this, so feel free to be robust in this. But what do you think is the biggest story, key takeaway from the show this year? >> We're democratizing security data within Security Data Lake for sure. >> Well said, you are our shortest answer so far on theCUBE and I absolutely love and respect that. Mark, it has been a pleasure chatting with you and congratulations, again, on the huge announcement. This is such an exciting day for you all. >> Thank you Savannah, thank you John, pleasure to be here. >> John: Thank you, great to have you. >> We look forward to 10 more years of having you. >> Well, maybe we don't have to wait 10 years. (laughs) >> Well, more years, in another time. >> I have a feeling it'll be a lot of security content this year. >> Yeah, pretty hot theme >> Very hot theme. >> Pretty odd theme for us. >> Of course, re:Inforce will be there this year again, coming up 2023. >> All the res. >> Yep, all the res. >> Love that. >> We look forward to see you there. >> All right, thanks, Mark. >> Speaking of res, you're the reason we are here. Thank you all for tuning in to today's live coverage from AWS re:Invent. We are in Las Vegas, Nevada with John Furrier. My name is Savannah Peterson. We are theCUBE and we are the leading source for high tech coverage. (upbeat music)