SUSE & AWS Leaders on Managing Cloud Complexity and AI-Driven Automation | AWS re:Invent 2025

Hey everyone. Welcome back to our Tech Drug TV coverage of AWS Reinvent 2025, sponsored by our good friends at suse. You know, we've been doing a couple of panels.

I love doing the panels 'cause we get a lot of points of view, and we've got some really, really smart people that I, I enjoy learning from. Let me introduce you to our smart panel for today. I'm gonna start on the far right with Rick and I'm gonna let each of them introduce themselves because I'm not smart enough to remember all their names and titles.

But Rick, why don't you go first. Sure. My name's Rick.

I'm the general manager of the Linux team at suse. Wonderful, Excellent. Uh, Manuk, I lead all of our business and Linux application partnerships at AWS And Margaret Dawson.

I also love Linux, but it's not in my job title and I'm the Chief Marketing Officer at suse. Excellent. Thank you all.

Rick. The other two folks gave their last name. I'm going to call you out.

Sure. My name is Rick Spencer. That's what we want to hear Rick.

'cause there's someone at home who says, that's my dad, my husband, my someone. I think I Kids', mom. My kids probably know my name, but name if you wanna find me online, I'm Rick Spencer.

Three, all one word on all my social media. There we go. Who's Rick Spencer?

One and Two. My grandfather and my father. Oh, that's Cool.

Okay. Really? Yeah.

Very cool. Well be that as it made though. We're here to talk about something really important today.

You know, I wanted to start this conversation off with, I, I've been been a user and a a my name is Alan. I am an AWS user, um, for a long time. And you know, it's funny, when you start, you first start, I don't know how many of you have been mine, I assume you have, have done on your own AWS journey, but you whip out your credit card, you open your first instance, it's easy peasy.

Mm-hmm. Right? Pick.

I'll go with the default Linux and I click that. I'll click one of these, gimme two of those. And, and it's very simple.

But these things have a way of, of like being like rabbits where they breed and they, and, and, and at each level it becomes more complex and more complex. And then your, your cohort at work, he's on his own journey and she's on her own journey. And then someone says, how many instances of AWS are we running on this table?

Everyone gives the face. I don't know. It becomes a complex kind of thing because maybe you didn't pick the same Linux I'm running.

Maybe you didn't pick the same configuration manager mm-hmm. Program Man. I'm sure at AWS you guys know this journey well where one day you wake up, you know, and then give, gave rice an whole finops movement as well.

Right. That was part of it. Yeah.

Right. What do I, my goodness, what am I managing here? What do we got?

How do I know what we have? How do we, how do we bring order to this chaos? Right.

And it, it's a problem. It's a real problem. Right?

For, for most organizations, especially at the enterprise level. Rick, I don't know, do you see this problem on-prem as much at suse? Like, 'cause SUSE has a lot of on-prem enterprises as well?

Or is this kind of a, a cloud specific? Um, I would say it's not cloud specific. So what we see is that in a typical enterprise, they're abs absolutely managing a multi Linux estate as we, as we put it.

And, um, there's different reasons that lead to that. As, as you mentioned, like the ease on a cloud provider for like, you know, picking a workload, launching it without, you know, giving thought to what you know, what you're gonna do in two days when there's time to apply updates and et cetera. Um, also, um, you know, different, uh, different ways of running workloads.

One company might acquire another company and that company had standardized in a different way. Uh, so this is one of the reasons that our multi Linux manager tool is so popular. 'cause that allows you to manage any Linux anywhere at any scale.

That's very useful in AWS environments. 'cause you know, EC2 customers may be managing, you know, workloads from, with all different, um, oss, not just suse, of course, Amazon Linux, you know, other, other, other linuxes. And so that's, uh, a really good option for if you're an EC2 customer, you want to get like a pane of glass that'll help you make sure things are being up to date.

Multi Linux manager will help you apply, uh, policies. It'll help you mirror repositories so that you can, um, you know, operate with the utmost safety, et cetera. I think This goes to some things we've talked about a lot this week already, where an AWS and SUSE are very aligned in providing that choice.

I mean, people may not realize that when they spin up an instance in AWS you can choose from a multitude of different linuxes or, or Kubernetes. I know we're gonna move to that in a minute. But, um, I think the importance is that we're now very, very focused on how do you help people understand those different environments?

How do you help people manage those different environments? Have more of a, you know, single control plane. I don't actually believe in a single pane of glass.

I don't think we can even do that. But like, we can help you have better visibility. How do we understand the cost better?

How do you integrate finops different things? So that's really where we are today. And then, you know, part of that is then how we integrate ai because that's helping you automate, helping you do things more easily.

So I think the original demand and ease of use that came out of AWS you know, initially that allowed developers to spin all that up and have that choice. Now people want a little bit more control, a little bit more management, a little bit more visibility while still giving developers, while still having choice. Correct.

While still having choice. They're not giving choice up. That's correct.

And still, and ease of use. Developers wanna build an app, they wanna build cool things. So how do we not take away any of the ease of use?

We don't wanna add friction, but for the ops people, for the management, for all the other people that are leveraging, um, that incredible cloud infrastructure, how do we give them more visibility and more management, more control? I think a part, uh, a part of coming here at Reinvent with all the 60,000 developers and, you know, people who are part of the A Ws ecosystem, I think it's also to put a flag not, uh, right now, but like what's gonna happen over the next 12 months. And I think a part of this conversation of managing complexity is also, you know, some of the stuff that, um, Matt shared yesterday in the keynote around the work that we are doing with our frontier models.

Yeah. And I think that, uh, the, the whole idea is that we are trying to abstract the complexity away. Mm-hmm.

So there is a level of, you know, abstraction on the complexity that is happening, what Rick mentioned, uh, at the, uh, the Linux manager level. Mm-hmm. But as we progress over the next 12 months, I think we need to talk about how we are bringing the MCP servers as part of this conversation.

How do we bring the, you know, the, the big announcement yesterday was around Quick Suite. Yes. So I think the, the thinking here is that yes, we are having this, uh, SUSE Linux manager that is going to manage a lot of the, what is your security posture?

What's your packages, what is your profile? That stuff is, you know, that's beautiful. Now from a developer who's just getting started, we know the people who are doing one servers or two servers, they're not really super sophisticated into the nuts and bolts of the Linux.

Or as well for the AWS for that matter. I think we are moving to this natural language processing interface, like a chat bot. You know, you talk to the machine and the response back.

So I think that's where it is very exciting over the next 12 months. I think where we see is mm-hmm. Integration of the SUSE manager with Quick Suite.

So customers can actually just speak or, you know, in natural language discuss, Hey, what is, you know, how is my overall Linux distribution? What is my cost? How do I manage it?

What is my security posture? And I think that really makes it much more accessible and democratizes and then also gives you more control and give you more control, more choice as well. Right?

Yeah. And it also brings in like the agent capabilities. And so in some ways I look at the Quick Suite as like sort of almost an, an agentic orchestrator.

And so you need the primitives there, which are those MPC servers. For instance, the, you know, right now you can go get multi Linux manager, you can install the MCP server, try it out. Right now you can go spin up SLED 16.

Our, our latest release we released a few weeks ago, install the MCP server, of course rancher, um, install rancher, get your Kubernetes clusters in control, install your MCP server, which is great. But Quick Suite really can like help you take it to the next level by allowing you to, you know, run Agentic jobs, which may be, you know, if it detects an issue, the LLM can like make some decisions about maybe I need to log a ticket, maybe I need to use, you know, the other services that are available as part of Quick Suite. Maybe enhance the information with some other things that Quick Suite would know, like, you know, who owns that server in your organization.

Mm-hmm. Is it mission critical or is this something that can go down? And those kinds of things.

So I think the combination of like the SUSE infrastructure, uh, using EC2 and EKS and Quick Suite is going to, it'll just be totally different in 12 months how people are managing their infrastructure at scale. And there'll be like more uptime, more efficiency. Um, I'm, I'm really excited to see what, uh, happens over the next 12 months.

You know, scale's a funny word, right? Your scale may be different than my scale. Yes.

Right? And, and so it's relative, but you know, they don't call a WSA hyperscaler for nothing. Right.

Some of this, the scale of, of the, of the install base right. Of, of, of enterprises on AWS is truly massive, massive scale. Mm-hmm.

And to me, it seems like this is a perfect use case for a AI and agent AI and MPC servers, right? Because how else are we going to get our hands around this? I mean, and, and when you think about why do we really want to use ai, right?

It's, it's to do things that, the mundane things, yes. But it's to do things that we, we can't, it not easily get our hands around. Mm-hmm.

And, and so I, I think it's important. Now, we spoke in the last panel about the strategic nature of the relationship now mm-hmm. Between Linux, uh, between, excuse me, between s and a and AWS.

They're around Linux, around rancher and around Kubernetes and all of this. But I don't think you can mention those three or four things without now mentioning AI as well, because this is an AI assisted model. Mm-hmm.

We've seen a lot. As you mentioned, man, there was a lot of, uh, announcements around AgTech and AgTech, AI and AI in general yesterday. Rick, I'm gonna throw it to you and then we bounce it around the panel here.

How, you know, 'cause this is a 12 month roadmap, let's say, but who knows? This goes real quick. How quickly do you see suse, you know, taking what was announced this week, internalizing it, if you will, and, and reflecting it on what's available in the marketplace?

Well, I, I would argue it's happening right now. And that SUSE is uniquely positioned for this. I think only SUSE has a multi Linux management tool.

Only SUSE has a multi Kubernetes management tool. Um, only SSA also has a, a Linux distribution that's made to work with that. Um, now, um, if I may, I, I would caution people to think about, like, if you're just grabbing an MCP server, hooking it up to your LLM and letting it, like do what it wants to do, that's probably not a good idea.

Because if, you know, if you just take the approach of just exposing the API to an LLM, we've all read the tragedies of like, LLMs deleting production databases and stuff like that. So the thing I would say is that, you know, if you look at SUSE's history over the last, what, 25 years, you know, we've been really focused on like security, safety, compliance. So we're very carefully building those agentic capabilities so that they fit into a real, real world workflow.

You know? And, um, and I, I think we're probably the most trustworthy company to actually like, bring all of the, uh, power of the Quick suite and all that ag agentic orchestration that people are doing, like, into the operation space. I think just wanna call.

Thanks Rick. I think I wanna call back to your point about scale. Like a, a company scale is different from B'S company.

I wanna highlight, uh, that Suzy and AWS have been partnering for two decades now. Mm-hmm. And so we have thousands of customers that are running mission critical workloads, both on the SUSE rancher offering as well as stress.

And these are, you know, company, you know, workloads like High Performance Computing, SAP. So, so customers are really, they love the fact that the two companies have been working together. There's a level of trust and we are supporting mission critical workloads for a long time.

So I think agent is just the next chapter in this partnership. I think we spoke already about, uh, managing the complexity of Linux, which is distributed across AWS and across your multiple, uh, multi-cloud environments as well as on premises. How do we bring this back into, um, you know, a quick, uh, suite view, and then we can actually do real time analytics on that?

We spoke about that. I think that then this entire narrative of abstracting complexity mm-hmm. Then extends to container workflow.

So with, you know, the, the rancher manager, the SaaS application that underlie underneath uses, um, uh, bedrock. So then, again, similar to what we discussed in Linux, in a natural language interface, customers can say, Hey, what's the status of my clusters? Uh, what is the cost associated with it as we discussed?

That's a big, uh, that's a big concern as well. And then, uh, how do I manage it? And so I think, again, it's all about democratizing, making it easy, uh, for our customer.

And, you know, we have a track record of doing it for two decades. And, uh, we just going, this is the next evolution of, I think there's one other piece of this strategic relationship is that we're doing this, you know, we talked about choice across very heterogeneous environments in terms of multi Kubernetes, multi Linux. Like, we're kind of embracing that together.

What the AI does is take all of those, you know, very, um, disparate sources almost of data and is does such a great job of bringing that together, just like we make it easier to manage all those disparate, you know, flavors of Kubernetes and Linux. So it, you know, there's these kind of thematic ideas that both companies are embracing, and it is about lack of complexity, but it's also about ease of use, ease of management. Um, and then I think the other piece that SUSE brings is that open source heritage into AWS that came with the supplemental packages on Amazon Linux.

So it comes back to whether you're using SUSE Linux or Amazon Linux, how does SUSE support that and make it even better, bring you the technologies and tools you want as you're using Amazon. You know, how does Amazon allow you to have a choice around that? And I think that is a very unique and differentiating, um, partnership.

Yeah. Right? Because we're bringing you the stability, the security, the scale.

Nobody scales like Amazon, right? Nobody brings open source technologies in a secure, more stable way. And then we're also giving that choice and control of heterogeneous, heterogeneous environment.

So I, I think that combination of all those things is really powerful for the customer. Absolutely. I, I, I couldn't have said it better, Margaret.

We spoke MPC service. Yeah. Everybody has an MPC server today, it seems.

Right? How many MPC servers do M-C-P-M-C-P, excuse me. Mm-hmm.

I forgot what MPC thinks. I Don't know. We should make something That multiplayer gaming.

It is. It's a multiplayer console. Console.

That's what it's, that's what, well, that's where my head's at. But bring out the Xbox. Yep.

Okay. But you know, the, the problem I like, in my mind, I'd like to see Amazon come out with an open source version of the server that everyone could standardize on. And then suse, you could build your special sauce on top of this.

In other words, how many different, like right now, how many MCP, right? Yeah. Mm-hmm.

Now you have me questioning myself. Um, how many MCP services? So I think one of the things we discussed, um, so first all, I think the standard spec for M CCP is, is open source.

Yes. Similar With A two A in terms of how the agents thing open source, um, more than, uh, you know, we launched this CP server slash agent tech slash AI marketplace back at the New York Summit in July. Yes.

So we have thousands of ISVs as well as products that are listed. So I think now at this point of time, um, the customers are really transitioning from piloting over the last year. I think that's our, our thesis is over 2025.

A lot of the piloting, a lot of testing, and 2026 customers are really going into production around that. So I think, uh, so everything that Rick and we discussed in terms of exposing the capability of, for example, the thing we discussed about either rancher, uh, um, you know, manager, or whether the SUSE Linux manager, the MCP is just like, you know, uh, it is just an interface into managing that. Uh, you know, and how does it talk to an LLM.

Mm-hmm. And then we bring that all of that, integrate that into Quick Suite. So that's where the customer is, customers actually doing a natural language conversation with quick suite.

Either it is text or it is voice. And then, uh, we abstract the complexity way or through the MCP server and the MCP client in the background, all of that insights, whether it is the state of your Linux operating system, whether it is how your Kubernetes cluster is doing, what is the security, what is the posture, the cost, all of that comes and says, Hey, I can you give me, and for example, a question would be, can you tell me how many Linux distributions that I'm using across my state here? Mm-hmm.

What is the status of my Kubernetes? Just gimme an overall view. How is the cost trending over the last three months, six months, nine months?

Just gimme a and what can I do to optimize? Those are really powerful things right now would take, you know, days and weeks for somebody to pull that entire view together. I think we are in the next 12 months where we are heading is to consolidate that view to one.

I I would like to, um, well, first of all, if I may, if there's any viewers who are like, what is exactly MCP and how it's working, so think of it as basically like a shim between like any tool and an LLM. Mm-hmm. And there's two main parts to think about.

And the first part is like context, right? You tell the MCP server tells the LLM how to ask for context, right? So how do you query for logs and that kind of thing.

And then the other part is tools or tasks that the MCP ser that the LLM can actually take, right? You, you tell it, you tell the LLM, you can actually go do these things through the MCP server. Mm-hmm.

And, um, so it's actually relatively trivial to stand up an MCP server in the same way it's tri trivial to stand up a, a website. Mm-hmm. Right?

However, designing one that is usable in production in the way that we're talking about is non-trivial. And so, um, that's why we're like really excited to be working with Amazon to expose like our very careful painstaking work to like, you know, bring those natural language queries and those automated actions like into the operations and administration space. And then exposing that back up to, to the, the quick sweet where it can bring in other contexts that, you know, were are not being provided by our tools and other actions that, you know, are, are exposed to other tools.

Like think of something as simple as like logging a ticket in your Atlassian or whatever mm-hmm. Your GitHub or et cetera, right? So it can like, ask our tools for, you know, is everything looking okay?

And it might say it's looking okay, but a little shaky. Let me log a ticket so that when your admin wakes up in the morning or it's looking really bad, let me use your PagerDuty and wake something, somebody up. You know, these are the kinds of like very trivial examples of the kind of workflows that people are gonna be able to build in their, um, you know, using the, the, uh, quick suite along with our MCP servers for our management tools.

So mm-hmm. Mm-hmm. I wanna return to money.

So it's, it's always on top of everyone's mind. Ronnie, you mentioned a little bit, we, we can actually through quick Suite ask the ai what can we do to optimize, you know, you wanna call it thin ops or whatever you wanna call it, but optimize spend cost. Um, how, I mean, it's one thing to ask and get some suggestions.

It's another thing to say, okay, you gotta close this, move that, do this, do that. How close are we to automating that? Like, so for instance, when I write something with ai, right?

It says, do you, would you like me to do this? Yes. Mm-hmm.

And it does it, right? That's, to me, that's the money shot. Right?

Can we do that now with, with the Linux, with this relationship and, and with what we have there? I mean Sure. Like, Do you want to though, Is your question?

Yeah. So the way that we actually have implemented like our logic is like, you wouldn't let an LLM do something, right? That you wouldn't let a team member do, right?

Like no sane SRE team let somebody just like log in and make a massive change without a code review, right? So if you look at some of our demos and, you know, come to our booth, we can show you, you know, for it can, you know, write the recipes and scripts, check it in for you, start the code review process, you know, which is what you would expect a human to do. The only thing is it can be done a lot faster with a lot more context.

You know, the LLM handles complexity in a different way than a human does. But, um, that's to go back to what I was saying before, like that's really why I think you wanna partner with a company like suse. 'cause we take that very, very seriously.

Like, you know, making sure that you're, uh, infrastructure is protected and compliant and following all your compliance guidelines while also giving you all the efficiency gains that, you know, admin teams are so hungry. I think in like absolutely, I think in the enterprise setting, this is still, uh, it's still a, uh, a problem that everybody's working on. Mm-hmm.

I think if you saw, again, Matt, a keynote yesterday, he talked about everything that we are doing around guardrails and policies. Mm-hmm. So I think there is a lot of active work that we are doing both at the level as well as through quick suite in terms of how do we manage and police, uh, you know, the, the actions that the LL m's taking on behalf of the customer.

I think have we, are we there fully? I think to Rick's point, um, you know, we can create guard rails, we can train data. There's is already like LLM looking at the LLM to make sure that, uh, you know, we are in the state and narrow here.

Uh, and I think that's where we, we discussed like 2025 was a lot about experimenting. If we have to get to the scale in 2026, get into production, this is probably the most critical, uh, thing that we have to, you know, cross the chasm as they say, uh, to get, to make, uh, enterprises comfortable with, you know, taking that leap. Yeah.

And I think the question is when do you want the LLM to take that action versus you still want a human in the loop, right? And I don't think we're done with that conversation, right? There's still gonna be times where you want a human to push the button, so to speak.

Um, you're not gonna give the LLM access to your source code necessarily, right. Um, even if you want it to help you develop in your way. So I, I think there's still some, um, ongoing discussion and of where the human in the loop is, um, even with all the guardrails and all the, the, the governance that happens.

But I think the more you can automate all of those things and bring us intelligence faster, better, cheaper, right, then we can make better Decisions. Yeah. I mean the, I mean, we all agree though.

There's a massive push to get into that direction. I think the, the value and the opportunity is, is tremendous. Mm-hmm.

Yeah. And so that's why everybody's just, uh, you know, kind of run, you know, running for, Well, I, you know, so you ask yourself why, why, why, why must there be a human in the loop? Well, there's two reasons.

Number one, is the underlying technology good enough where I could I, because it comes down to a matter of trust, right? Mm-hmm. Can I trust it by itself?

You know, I, I was driving my car on the highway a couple weeks ago going to the airport and it said, Hey, why don't try our, it's A-B-M-W-B-M-W assisted driving. I said, oh, let me try it. I'm by myself.

No one will yell at me. I, I, I hit the button and it started driving it, it take your hands off the wheel, take your feet off the pedal, just sit back and watch. And I, I, I found myself like this.

Yeah. Right. Sitting wait, ready to pounce on that wheel.

And you know what? I never had to, it, it took the turns. It, if I put on my signal to switch, if there's a car there, it tells me no, if there's no car, it speeds up in switches.

It's a very similar experience to trusting the, the LLM, the, the AI to do these things. It, it's gonna take time until you take your hands away from the steering wheel and put 'em on your lap. And we, we'll get there one day, I think.

Mm-hmm. I don't know if I'll be here, but we'll get there. And, um, it's, it's, it's coming for sure.

Like, there's no doubt in my mind this is the way of where we're headed. I mean, I think it depends on how you look at it, right? Because if you think of like the driving analogy being that, um, the LLM is changing your infrastructure like directly, like that makes sense.

But if you think about the way people actually manage their infrastructure through like Ansible and Salt and other tools, like we're there right now mm-hmm. Like the absolutely can generate like perfectly serviceable Ansible scripts that can go into your, into your whole GI ops workflow. And people can, can, you know, your other GI ops team members can look it over, other LLMs can look it over and make sure, like, does this meet our security compliance and et cetera.

So, um, I, um, I think the technology is there as they want said on a TV show. We have the technology. Yeah.

But do we have the Trust? I think like a lot to explain a lot of that is deterministic in the sense we know there's like A to B2C, everything is for retract. I think the LLMs is non-deterministic, some part of it.

Uh, so I think like once the technology is there, there's already a pattern here that, you know, the customers trust and you know, yes. This, they're already deploying mission critical workloads through, you know, solid scripts and such. I think the, I think the, the LLM in itself has to, has to evolve to get there, right?

And I think right to Margaret's point, we are still, I think for 2026, we still foresee the human in the loop. It's gonna play a very critical, uh, thing. Yeah, yeah.

Critical role. Yeah. Agree.

I mean, there are, there are patterns in like in for instance, Kubernetes, you can set it to like auto scale and different things. Mm-hmm. So like I think, um, a lot of it is like what RAC, what role-based access controls do you give the LLM?

And this is already a very common pattern, right? Like a lot of platform teams will say like, Hey, our ops team is allowed to scale out, but they can't scale down. Or similar things like that.

And so I think we'll see over the course of just literally the next 12 months, like patterns like that being brought into like this is a tool that we can give the LLM to just go ahead and do it. 'cause they can't do much damage. Like they could create a new table, but they can't delete a table.

I think the question is like, do you use the ZLM put out patches to all the unpatched systems? And you're like, do you trust it enough to do that or not? Do you let it roll back a feature update or not?

Right? So I think there's like a level of specificity, Certain kinds of patches, right, exactly. Do Yeah, exactly.

Or not. Right. And I think it just one last point in the race to get to that determination, like, you know, the best state here where we can start trusting the LLM apart, a lot of it is actually training and what data that we are training the LLM on.

And in fact, and in fact that, you know, just SUSE has decades of, uh, data in terms of how customers are using both their Linux and the Kubernetes distributions for AWS you know, what Matt discussed yesterday are the frontier models around developing code on deploying code and running security. So we are running as, you know, as said, hyper scaled, right? So we have like tons of, you know, supporting millions of customers, uh, over couple of decades now.

So that data and then what is the learning that we have done as a function on that, that informing some of the, the new AI or the new elements we are developing, specifically what that specific workload, I think that is probably the path to getting our customers more comfortable into deploying it and production use cases. I think that seems like the, the road to get there. Mm-hmm.

So there's been a great discussion, but you, you know what I'm worried about people looking at home. If they're watching this, they're probably not here. How can we get them started?

How do we, these are all great things that we spoke about, right? Really kind of job changing. If you're a, a Linux administrator or an AWS administrator, Rick, I'm gonna start with you.

Sure. Where do people go? How do they get started?

Where's the on-ramp here? Sure. So, um, I would say for a call to action, if you want to get involved, go to the marketplace.

You can get multi Linux manager there. You can get SLES 16 there. Go ahead and install the tech previews for the MCP servers, start giving us feedback, you know, what's working for you, what's not working for you.

That's exactly why we put it out in, uh, in as a tech preview so that we can iterate quickly with the user base. Mm-hmm. And same is true for rancher.

Yeah. And, uh, my call to action is do everything what Rick is. That's an easy one.

Plus, uh, uh, you know, try out the new kiro, uh, software developer platform, uh, that is becoming now generally available. Also, go look at, uh, you know, some of the new stuff that we are doing here with, uh, the frontier models, both on the DevOps side as well, security side. I think that is really gonna start, uh, pulling the story together in terms of what, you know, Rick is talking and then Yeah.

And no coincidence. Those are the three A agents that were announced yesterday, right? Yes.

The kiro agent and security agent And the DevOps agent. And the DevOps agent. Yeah.

So you can get all of those. Margaret, I wanted to give you the last word. Wow, I don't see this.

Now you've got me speechless. No, I think I'm just really not lost. No, no, no.

I work That down. I was just gonna say that, that last two days, which feels a lot longer than two days, but there is just so much energy in this show. There's so much energy around Amazon, around ai, around just h how to collaborate.

And, and again, I'm gonna go back to, I know this is becoming a repetitive theme, but, you know, continuing to look at the ecosystem around AWS and I would say it's our ecosystem and a W s's ecosystem and the power of how all these companies and all these technologies are coming together to help people, you know, build applications that are better, faster, smarter, more secure, um, and, and deploy them, you know, what works best for them. So I, it's just exciting. Like there's just a lot of enthusiasm that's great Tech at, at at great scale too.

At great scale and great technology. Rick, Manu, Margaret, thank you so much for joining us on our Textron TV coverage. We're gonna take a break here on Textron tv.

We've got lots more coming at you today and tomorrow, so stay tuned, but we'll be right back.