WEBVTT - Nasdaq and AWS Partner to Transform Markets

0:00:00.080 --> 0:00:03.640
<v Speaker 1>You're listening to Bloomberg Business Week with Carol Messer and

0:00:03.720 --> 0:00:08.119
<v Speaker 1>Bloomberg Quick Takes. Tim Stinovic on Bloomberg Radio. We've got

0:00:08.119 --> 0:00:12.240
<v Speaker 1>the details on a partnership between NASDAC and Amazon Web Services.

0:00:12.280 --> 0:00:15.000
<v Speaker 1>It's all about building out the next gen cloud enabled

0:00:15.040 --> 0:00:19.079
<v Speaker 1>infrastructure for the world's capital markets. Cloud is everywhere, It

0:00:19.200 --> 0:00:22.560
<v Speaker 1>certainly is. Ruba Borno is Global Channel chief for a WS,

0:00:22.560 --> 0:00:25.119
<v Speaker 1>also known as Amazon Web Services. Ruba joins us on

0:00:25.160 --> 0:00:27.920
<v Speaker 1>the phone from North Carolina. Lauren Dillard is Executive vice

0:00:27.920 --> 0:00:31.640
<v Speaker 1>president of Investment Intelligence at NASDAC. Lauren joins us on

0:00:31.640 --> 0:00:34.040
<v Speaker 1>the phone from Austin, Texas. Great to have you both

0:00:34.120 --> 0:00:36.400
<v Speaker 1>with us, Lauren, I want to start with you, uh

0:00:36.400 --> 0:00:39.839
<v Speaker 1>and just understand why the partnership is is why this

0:00:39.880 --> 0:00:44.239
<v Speaker 1>is the right partnership for NASDAC, NASDAC and AWS UM. Well,

0:00:44.280 --> 0:00:47.040
<v Speaker 1>thank you Tim for having for having us both and

0:00:47.120 --> 0:00:50.760
<v Speaker 1>we're excited to talk about this. Look at NAZAC, we've

0:00:50.800 --> 0:00:54.040
<v Speaker 1>had a long cloud journey. Actually, our vision is that

0:00:54.520 --> 0:00:57.400
<v Speaker 1>the global capital markets and where we sit UM will

0:00:57.440 --> 0:01:00.800
<v Speaker 1>be enabled and belong in the cloud. I think everything

0:01:00.840 --> 0:01:03.800
<v Speaker 1>you're seeing in the markets today UM just reinforce that

0:01:05.080 --> 0:01:06.960
<v Speaker 1>that they have to be dynamic, they have to be

0:01:07.040 --> 0:01:10.200
<v Speaker 1>future focused, they have to be innovative. New retail brokers

0:01:10.200 --> 0:01:13.160
<v Speaker 1>have to be able to set up shop quickly and frankly,

0:01:13.800 --> 0:01:17.880
<v Speaker 1>you know, as the technology provider, we have long had many,

0:01:17.959 --> 0:01:21.640
<v Speaker 1>many kind of cloud native products on the back of Amazon,

0:01:22.200 --> 0:01:27.200
<v Speaker 1>and this partnership just really solidifies taking the markets themselves

0:01:27.200 --> 0:01:29.680
<v Speaker 1>into the future. We can talk about the details that

0:01:29.760 --> 0:01:31.920
<v Speaker 1>we have. We have actually a lot of the surrounding

0:01:31.959 --> 0:01:33.680
<v Speaker 1>systems already in the cloud because we've been on this

0:01:33.760 --> 0:01:36.560
<v Speaker 1>journey with with Amazon for for over a decade now,

0:01:36.920 --> 0:01:40.160
<v Speaker 1>but truly moving the matching engine, the actual matching engine

0:01:40.200 --> 0:01:42.520
<v Speaker 1>in the markets. The cloud is is what we're endeavoring

0:01:42.560 --> 0:01:45.039
<v Speaker 1>to do across the markets and APEX run and we're

0:01:45.080 --> 0:01:47.120
<v Speaker 1>we're delighted with the partnership. We have a come on

0:01:47.160 --> 0:01:49.360
<v Speaker 1>in on the conversation. So you know, you guys work

0:01:49.400 --> 0:01:51.360
<v Speaker 1>with a lot of companies that depend on you for

0:01:51.640 --> 0:01:56.800
<v Speaker 1>various cloud services. We know that aws IS is massive. Um,

0:01:56.960 --> 0:01:58.880
<v Speaker 1>when you approach a project like this, how do you

0:01:58.920 --> 0:02:01.720
<v Speaker 1>think about it? Uh, and and listen to the client

0:02:01.760 --> 0:02:03.680
<v Speaker 1>in terms of what they're needing, especially when it comes

0:02:03.720 --> 0:02:06.520
<v Speaker 1>to financial markets. Right, this is our bread and butter

0:02:06.960 --> 0:02:09.240
<v Speaker 1>and you've got to make sure that they're running smoothly.

0:02:10.880 --> 0:02:13.320
<v Speaker 1>Thank you so much, Carol, Tim for having me and

0:02:13.400 --> 0:02:16.400
<v Speaker 1>Lauren here. And we're really excited about the partnerships. And

0:02:16.440 --> 0:02:18.919
<v Speaker 1>one of the greatest things about AWS is that we

0:02:19.000 --> 0:02:22.960
<v Speaker 1>do everything with a foundation built on leadership principles. And

0:02:23.000 --> 0:02:26.519
<v Speaker 1>one of our our top leadership principles actually customer obsession

0:02:26.720 --> 0:02:29.440
<v Speaker 1>and what that means is actually working backwards from the customer.

0:02:29.880 --> 0:02:33.000
<v Speaker 1>Now with NASDAC, they are both a customer and a partner.

0:02:33.480 --> 0:02:36.799
<v Speaker 1>And as Lauren mentioned, this has been a ten year relationship,

0:02:36.880 --> 0:02:40.040
<v Speaker 1>so nearly a decade going back, um, we had our NAZAC.

0:02:40.240 --> 0:02:42.840
<v Speaker 1>We had NAZAC CEO Adina Freedman on stage at our

0:02:42.840 --> 0:02:46.799
<v Speaker 1>annual conference Reinvent this past November to talk about this, uh,

0:02:46.840 --> 0:02:49.520
<v Speaker 1>this multi year partnership. But if I go back to

0:02:49.800 --> 0:02:54.519
<v Speaker 1>even when Nezac first moved from an on premises data

0:02:54.560 --> 0:02:57.200
<v Speaker 1>warehouse to an a w S data warehouse to increased

0:02:57.240 --> 0:03:01.359
<v Speaker 1>scale and performance and lower operational costs, that was really

0:03:01.400 --> 0:03:03.720
<v Speaker 1>the start of it. And then that cluster continued to

0:03:03.760 --> 0:03:07.200
<v Speaker 1>grow as NAZBAT grew and they continued to consume more

0:03:07.240 --> 0:03:10.000
<v Speaker 1>and more of a WS services, so as we think

0:03:10.040 --> 0:03:13.320
<v Speaker 1>about the next phase of the partnership when NAZBAC will

0:03:13.360 --> 0:03:16.000
<v Speaker 1>move all of its operations to a WUS, and Lauren

0:03:16.040 --> 0:03:18.640
<v Speaker 1>mentioned moving the matching engine, which is the technology that

0:03:18.720 --> 0:03:22.399
<v Speaker 1>powers then stac stocket change. It's really incredible because we're

0:03:22.400 --> 0:03:25.000
<v Speaker 1>looking at not just what it gives them, but also

0:03:25.120 --> 0:03:28.200
<v Speaker 1>gives their end customers as well. So it gives them

0:03:28.200 --> 0:03:32.440
<v Speaker 1>and other market infrastructure operators and market participants the ability

0:03:32.639 --> 0:03:35.800
<v Speaker 1>to confidantly move their trading systems to the cloud. It's

0:03:35.800 --> 0:03:38.520
<v Speaker 1>really the first of its kind of collaboration that we've

0:03:38.520 --> 0:03:42.360
<v Speaker 1>had designed to meet the latency, fairness, and regulatory requirements

0:03:42.360 --> 0:03:45.360
<v Speaker 1>of the world's most critical markets. And what we're excited

0:03:45.360 --> 0:03:48.360
<v Speaker 1>about is that it helps deepen the capabilities that Nasdaq

0:03:48.440 --> 0:03:52.800
<v Speaker 1>has and anti financial crime data and analytics and market

0:03:52.800 --> 0:03:56.240
<v Speaker 1>infrastructure software solutions for their clients helps them deliver it

0:03:56.280 --> 0:03:59.480
<v Speaker 1>at Lauren, I gotta bring you back because the last

0:03:59.560 --> 0:04:01.720
<v Speaker 1>year and a half or so, certainly during the pandemic,

0:04:01.840 --> 0:04:04.880
<v Speaker 1>right we were all watching the rise of the retail

0:04:04.920 --> 0:04:09.480
<v Speaker 1>investor and meme stocks and alternate trading platforms. How do

0:04:09.560 --> 0:04:13.200
<v Speaker 1>you guys think about what your platform needs to be,

0:04:13.520 --> 0:04:16.839
<v Speaker 1>especially as how we trade and the financial markets in

0:04:16.839 --> 0:04:19.760
<v Speaker 1>a big way continue to evolve and and kind of

0:04:20.120 --> 0:04:23.680
<v Speaker 1>test if you will, UM, the establishment, which you guys

0:04:23.680 --> 0:04:26.280
<v Speaker 1>are a part of. Even though you're certainly younger than

0:04:26.320 --> 0:04:28.840
<v Speaker 1>the New York Stock Exchange, Um, you're considered part of

0:04:28.839 --> 0:04:31.800
<v Speaker 1>the establishment. And people are, especially a younger generation, a

0:04:31.839 --> 0:04:34.800
<v Speaker 1>younger retail investor, are looking for different ways to be

0:04:34.839 --> 0:04:38.600
<v Speaker 1>involved in the market. Well, let me start with just

0:04:39.040 --> 0:04:43.000
<v Speaker 1>fundamentally the markets. The security of the markets, the resiliency,

0:04:43.080 --> 0:04:47.160
<v Speaker 1>the reliability, I mean, those are all core too, frankly

0:04:48.120 --> 0:04:52.279
<v Speaker 1>allowing market participants and and as Ruba said, um we

0:04:52.400 --> 0:04:57.560
<v Speaker 1>at NAZAC our purpose is fundamentally inclusive capital, driving inclusive capital.

0:04:57.640 --> 0:04:59.920
<v Speaker 1>So we want more market participants. That's that's fund and

0:05:00.000 --> 0:05:01.840
<v Speaker 1>the lead the way we think about it. So if

0:05:01.839 --> 0:05:04.000
<v Speaker 1>you kind of tie this back to our cloud discussion,

0:05:04.240 --> 0:05:09.719
<v Speaker 1>that resiliency, that security, that innovation, that scalability. UM is

0:05:09.720 --> 0:05:12.520
<v Speaker 1>a big reason why this partnership is very important to

0:05:12.600 --> 0:05:14.520
<v Speaker 1>us as we look forward in scale. And you are

0:05:14.560 --> 0:05:19.200
<v Speaker 1>exactly right if you think about the market itself from

0:05:19.279 --> 0:05:23.720
<v Speaker 1>pre pandemic to now, this is a good fact. Prior

0:05:23.800 --> 0:05:28.120
<v Speaker 1>to two thousand nineteen, the average message count for options

0:05:28.200 --> 0:05:32.040
<v Speaker 1>was about fifteen billion messages and now the new normal

0:05:32.240 --> 0:05:36.120
<v Speaker 1>for options fifty five billion messages. So there is an

0:05:36.320 --> 0:05:39.240
<v Speaker 1>enormous amount of activity on the markets and that market

0:05:39.279 --> 0:05:43.120
<v Speaker 1>resiliency is so critical to us, and we and NAZAC

0:05:43.200 --> 0:05:46.080
<v Speaker 1>take great pride in that. And I should mention in Ruba.

0:05:46.400 --> 0:05:48.440
<v Speaker 1>Ruba touched on this as as you did as well.

0:05:48.920 --> 0:05:52.799
<v Speaker 1>We run our NAZAC market, but we actually also power

0:05:53.120 --> 0:05:57.719
<v Speaker 1>over a hundred and thirty other market infrastructure clients. So

0:05:57.720 --> 0:06:00.960
<v Speaker 1>when you think about how important this this cloud journey

0:06:01.040 --> 0:06:03.320
<v Speaker 1>is for us, it's not just for our own markets,

0:06:03.320 --> 0:06:06.080
<v Speaker 1>which is obviously critical and those those numbers that I

0:06:06.120 --> 0:06:08.880
<v Speaker 1>just said are staggering, but it's also spanning all of

0:06:08.920 --> 0:06:12.559
<v Speaker 1>the exchanges and banks and clearing houses and and other

0:06:13.080 --> 0:06:16.320
<v Speaker 1>other technology platforms that we provide um and that rely

0:06:16.400 --> 0:06:19.480
<v Speaker 1>on us frankly for clearing and trading and settlement and surveillance.

0:06:19.480 --> 0:06:22.120
<v Speaker 1>So we are a technology provider for and so this

0:06:22.160 --> 0:06:25.680
<v Speaker 1>cloud journey really shows the other markets that we can

0:06:25.800 --> 0:06:27.680
<v Speaker 1>endeavor on this journey as well. Okay, Reybody, I want

0:06:27.680 --> 0:06:29.440
<v Speaker 1>to get a little nitty gritty here with what exactly

0:06:29.480 --> 0:06:33.040
<v Speaker 1>AWS is doing for for NASDAC. Here are we talking

0:06:33.160 --> 0:06:36.359
<v Speaker 1>fully cloud like all off premise or is there stuff

0:06:36.400 --> 0:06:38.520
<v Speaker 1>on the edge that helps make that transition to the

0:06:38.520 --> 0:06:44.960
<v Speaker 1>cloud thanks to him. It's actually both. So what we're

0:06:45.000 --> 0:06:48.040
<v Speaker 1>really excited about here is that cord to NASDAK move

0:06:48.120 --> 0:06:51.640
<v Speaker 1>to a WS will be something we call a WS outposts,

0:06:51.680 --> 0:06:55.520
<v Speaker 1>which extends the AWS Infrastructure Services, APIs and tools to

0:06:55.600 --> 0:06:59.680
<v Speaker 1>virtually any data center, co location space or on premises facility.

0:07:00.080 --> 0:07:02.839
<v Speaker 1>So we're really excited about that, and it does provide

0:07:03.200 --> 0:07:05.479
<v Speaker 1>all of those services um and we're starting in a

0:07:05.480 --> 0:07:08.320
<v Speaker 1>phased approach. So actually we began with one of the

0:07:08.360 --> 0:07:10.800
<v Speaker 1>markets in January of this year, and so we'll be

0:07:10.880 --> 0:07:14.680
<v Speaker 1>following a phased approach to to continue that expansion. All right,

0:07:14.720 --> 0:07:17.360
<v Speaker 1>we're gonna come back and continue the conversation with ruber Borno,

0:07:17.480 --> 0:07:20.320
<v Speaker 1>she's Global Channel chief at Amazon Web Services on the

0:07:20.320 --> 0:07:23.760
<v Speaker 1>phone in North Carolina. And Lauren Dillard, Executive vice president

0:07:23.760 --> 0:07:27.160
<v Speaker 1>of Investment Intelligence at NASDAK, on the phone from Austin, Texas.

0:07:27.400 --> 0:07:30.200
<v Speaker 1>Our guest with us ruble Borno, she is Global channel

0:07:30.240 --> 0:07:32.560
<v Speaker 1>chief over at Amazon Web Services. She's with us on

0:07:32.600 --> 0:07:35.480
<v Speaker 1>the phone from North Carolina. Also with us, Lauren Dillard,

0:07:35.560 --> 0:07:39.280
<v Speaker 1>Executive VP of Investment Intelligence on at NASDAK on the

0:07:39.280 --> 0:07:41.880
<v Speaker 1>phone from Austin, Texas. They've been talking about their partnership

0:07:42.400 --> 0:07:45.320
<v Speaker 1>between the two building out the next gen cloud enabled

0:07:45.360 --> 0:07:50.440
<v Speaker 1>infrastructure for capital markets, the global capital markets. Hey, guys,

0:07:50.480 --> 0:07:53.800
<v Speaker 1>I wanted to ask you, UM hard to ignore with

0:07:53.920 --> 0:07:57.240
<v Speaker 1>every leader that we have here on at Bloomberg to

0:07:57.280 --> 0:08:00.800
<v Speaker 1>talk about some of the headlines the in Ukraine because

0:08:00.800 --> 0:08:04.280
<v Speaker 1>of the Russian invasion, volatility in the financial markets. UM,

0:08:04.320 --> 0:08:07.920
<v Speaker 1>there's so many questions about the global economic and market

0:08:07.960 --> 0:08:10.600
<v Speaker 1>outlook and whether it's really time to rethink the second

0:08:10.640 --> 0:08:12.720
<v Speaker 1>half of the year. And I'm curious how you each

0:08:12.800 --> 0:08:14.960
<v Speaker 1>see it. And Lauren, let me start with you. Because

0:08:14.960 --> 0:08:18.440
<v Speaker 1>there's been so much volatility in the markets. What are

0:08:18.480 --> 0:08:20.960
<v Speaker 1>some of the conversations that you guys are having at

0:08:21.080 --> 0:08:28.600
<v Speaker 1>NASDAC about maybe what what what's to come here? In Well?

0:08:28.640 --> 0:08:31.640
<v Speaker 1>I mean, it is our role and responsibility to have

0:08:31.760 --> 0:08:34.880
<v Speaker 1>resilient markets UM, to frankly make sure that they can

0:08:34.960 --> 0:08:38.280
<v Speaker 1>handle the peaks of of traffic and latency, which we

0:08:38.320 --> 0:08:41.360
<v Speaker 1>talked about UM, and and we don't see any of

0:08:41.400 --> 0:08:46.080
<v Speaker 1>that changing. UM. We continue to have records of message traffic.

0:08:46.640 --> 0:08:49.360
<v Speaker 1>So I would say from a just market resiliency perspective.

0:08:49.679 --> 0:08:53.120
<v Speaker 1>We're very proud of being able to support the levels frankly,

0:08:53.120 --> 0:08:56.240
<v Speaker 1>that we've seen to date around you know, the rest

0:08:56.240 --> 0:08:58.520
<v Speaker 1>of the capital markets. You know, we sit in a

0:08:58.559 --> 0:09:00.880
<v Speaker 1>really unique place in the eCos of them, so we

0:09:00.920 --> 0:09:05.080
<v Speaker 1>set in between asset managers and investors and corporates, and frankly,

0:09:05.120 --> 0:09:07.800
<v Speaker 1>a lot of the needs around the clients we serve

0:09:08.640 --> 0:09:12.960
<v Speaker 1>are unchanged there. They of course are changed from pressure,

0:09:13.280 --> 0:09:15.880
<v Speaker 1>but you know, they still need to do business, they

0:09:15.920 --> 0:09:18.680
<v Speaker 1>still need to make investments, they still need to do

0:09:18.840 --> 0:09:22.480
<v Speaker 1>manager research, which is something that we provide on our technology,

0:09:22.520 --> 0:09:26.400
<v Speaker 1>our corporate listed clients. They'll need to understand their investors,

0:09:26.559 --> 0:09:29.640
<v Speaker 1>and there's obviously a a push for more E s

0:09:29.720 --> 0:09:33.400
<v Speaker 1>D disclosures, So all of kind of those business matters continue.

0:09:33.760 --> 0:09:36.360
<v Speaker 1>We have a healthy pipeline of I P O s

0:09:36.920 --> 0:09:40.559
<v Speaker 1>UM and it remains strong. But because of the market volatility,

0:09:40.640 --> 0:09:43.120
<v Speaker 1>we could see some of those getting pushed out UM,

0:09:43.520 --> 0:09:45.240
<v Speaker 1>so that we see a little bit of what I

0:09:45.280 --> 0:09:48.000
<v Speaker 1>would call an adjustment. But the pipeline has been extraordinarily

0:09:48.000 --> 0:09:50.040
<v Speaker 1>strong to start and you don't see any of that

0:09:50.200 --> 0:09:53.280
<v Speaker 1>at this point. The pipeline backing off at this point, Lauren,

0:09:54.280 --> 0:09:57.040
<v Speaker 1>I mean you've seen some quality deals take place despite

0:09:57.120 --> 0:09:59.559
<v Speaker 1>what you've seen with some of the pullback. But um,

0:09:59.559 --> 0:10:02.440
<v Speaker 1>and there's still a lot of optimism and frankly, you

0:10:02.440 --> 0:10:05.199
<v Speaker 1>know accessing the public markets, UM. But you know windows

0:10:05.280 --> 0:10:09.000
<v Speaker 1>open and closed, and so the team that focuses on that,

0:10:09.040 --> 0:10:11.679
<v Speaker 1>you know, stays with that pipeline. So RU, But let

0:10:11.679 --> 0:10:13.560
<v Speaker 1>me bring you in this kind of same thing. I mean,

0:10:14.760 --> 0:10:16.480
<v Speaker 1>like we said, we asked all of our leaders who

0:10:16.520 --> 0:10:20.040
<v Speaker 1>are coming on UM about the headlines. You know, one

0:10:20.080 --> 0:10:22.439
<v Speaker 1>of the things that we are realizing or that we've

0:10:22.480 --> 0:10:25.480
<v Speaker 1>seen certainly, is that in this war, it's certainly a

0:10:25.520 --> 0:10:28.040
<v Speaker 1>ground war and military war, but it's also a cyber war.

0:10:28.440 --> 0:10:31.959
<v Speaker 1>And we have talked so much about cybersecurity. How are

0:10:32.000 --> 0:10:34.960
<v Speaker 1>you guys at Amazon Web Services? Are you seeing any

0:10:35.040 --> 0:10:38.720
<v Speaker 1>kind of breaches or increased act activity because of our

0:10:38.760 --> 0:10:43.600
<v Speaker 1>following this war in Ukraine. It's such a good question. Um.

0:10:43.640 --> 0:10:47.200
<v Speaker 1>While we're seeing an increasing activity of malicious state actors,

0:10:47.200 --> 0:10:51.480
<v Speaker 1>were also just being higher operational tempo by other malicious actors.

0:10:51.559 --> 0:10:56.199
<v Speaker 1>And we've seen several situations where malware has specifically targeted charities,

0:10:56.520 --> 0:11:00.240
<v Speaker 1>NGOs and other aid organizations just to spread confuse, Usian

0:11:00.280 --> 0:11:03.680
<v Speaker 1>and cause disruption. UM. So this is an area where

0:11:03.679 --> 0:11:06.520
<v Speaker 1>we are focused. We're continuing to work hard to protect

0:11:06.920 --> 0:11:09.200
<v Speaker 1>UH these customers and we're going to continue to work

0:11:09.240 --> 0:11:11.600
<v Speaker 1>closely with them UM as they carry out their much

0:11:11.600 --> 0:11:14.120
<v Speaker 1>needed work to help those that are impacted by this

0:11:14.240 --> 0:11:17.160
<v Speaker 1>terrible conflict. But that's absolutely a huge focus of ours

0:11:17.280 --> 0:11:20.760
<v Speaker 1>is UH cybersecurity and supporting our customers. There have to

0:11:20.800 --> 0:11:23.640
<v Speaker 1>follow up. Do you know any indication of where kind

0:11:23.640 --> 0:11:27.559
<v Speaker 1>of the bad actors are coming from? At this day,

0:11:27.640 --> 0:11:31.160
<v Speaker 1>we haven't shared anything publicly on that, but it's this

0:11:31.200 --> 0:11:33.679
<v Speaker 1>is something that's just activities increasing. It could be coming

0:11:33.720 --> 0:11:36.520
<v Speaker 1>from anywhere. So Ruba, what would you say to people

0:11:36.559 --> 0:11:39.160
<v Speaker 1>listening right now who need to keep their own networks

0:11:39.160 --> 0:11:40.680
<v Speaker 1>safe and what's the right way to do this in

0:11:40.720 --> 0:11:45.640
<v Speaker 1>this environment? That's thank you, sim So. Our teams are

0:11:45.640 --> 0:11:48.520
<v Speaker 1>continually learning from the intelligence that we collect, and I

0:11:48.559 --> 0:11:51.040
<v Speaker 1>think that what we're working on with our customers is

0:11:51.840 --> 0:11:55.200
<v Speaker 1>work with your account manager, security specialist, solution architects, and

0:11:55.200 --> 0:11:59.720
<v Speaker 1>other technical professionals to constantly assess the threat landscape that

0:11:59.760 --> 0:12:02.120
<v Speaker 1>you have, the threat perimeter that you have, and ensure

0:12:02.200 --> 0:12:04.559
<v Speaker 1>that you are secure. But we are ready to support

0:12:04.600 --> 0:12:07.280
<v Speaker 1>our customers there, but it's it's really a constant game.

0:12:07.480 --> 0:12:10.520
<v Speaker 1>The threat landscape is constantly increasing, UM, and the number

0:12:10.520 --> 0:12:13.440
<v Speaker 1>of threat actors is constantly increasing as well. So it

0:12:13.559 --> 0:12:16.440
<v Speaker 1>is diligence that isn't a destination. You will never have

0:12:16.520 --> 0:12:19.360
<v Speaker 1>it solved at the end, but it is constant work UM.

0:12:19.400 --> 0:12:21.480
<v Speaker 1>And so I would say, just reach out and we're

0:12:21.480 --> 0:12:24.080
<v Speaker 1>ready to help. I also am curious for both of

0:12:24.120 --> 0:12:27.480
<v Speaker 1>you in terms of employees you might have overseas, whether

0:12:27.480 --> 0:12:29.680
<v Speaker 1>it's Russia or Ukraine. I mean, one of the things

0:12:29.679 --> 0:12:32.719
<v Speaker 1>that has come out about this and unfortunately, UM it's

0:12:32.760 --> 0:12:36.160
<v Speaker 1>come out because it took a war for us to understand.

0:12:36.320 --> 0:12:39.559
<v Speaker 1>You know, how much companies reply rely on I t

0:12:39.960 --> 0:12:43.959
<v Speaker 1>out of Ukraine, UM, and how important it is um, Lauren,

0:12:44.000 --> 0:12:48.520
<v Speaker 1>any thoughts on that, I would just I would just

0:12:48.559 --> 0:12:52.560
<v Speaker 1>say that we we obviously run markets in in across Europe,

0:12:52.600 --> 0:12:56.320
<v Speaker 1>specifically the Nordics and the Baltics, so UM, we we

0:12:56.520 --> 0:12:59.920
<v Speaker 1>are very focused, as as our other companies on you know,

0:13:00.120 --> 0:13:03.679
<v Speaker 1>the safety of our employees obviously, the resiliency of our

0:13:03.720 --> 0:13:06.800
<v Speaker 1>markets UM and and of course the outpouring of our

0:13:06.840 --> 0:13:10.280
<v Speaker 1>our employees families. UM. And we are focused of course

0:13:10.320 --> 0:13:14.200
<v Speaker 1>on the humanitarian release and efforts. UM. So you know,

0:13:14.240 --> 0:13:17.199
<v Speaker 1>I think we like every company that have anyone nearby

0:13:17.280 --> 0:13:19.959
<v Speaker 1>or focused on our employees there and and of course

0:13:20.120 --> 0:13:22.320
<v Speaker 1>again since we run the markets in the Baltics and

0:13:22.400 --> 0:13:25.920
<v Speaker 1>then Ordics, extremely focused on resiliency. Yeah, but what about

0:13:25.920 --> 0:13:27.800
<v Speaker 1>you when it comes to Amazon Web Services. We've done

0:13:27.800 --> 0:13:30.240
<v Speaker 1>a lot of reporting on tech companies that have had

0:13:30.280 --> 0:13:32.679
<v Speaker 1>to get employees out of Ukraine. But um, what's the

0:13:32.720 --> 0:13:36.319
<v Speaker 1>presence right now in Russia, Ukraine, UH, in Belarus and

0:13:36.520 --> 0:13:38.480
<v Speaker 1>and what are you doing in those areas right now?

0:13:39.800 --> 0:13:42.280
<v Speaker 1>So we don't have a local presence right now, So

0:13:42.280 --> 0:13:45.319
<v Speaker 1>it's just about for us to without a local presence

0:13:45.360 --> 0:13:47.720
<v Speaker 1>to provide direct support and award zone. But we are

0:13:47.760 --> 0:13:51.160
<v Speaker 1>focused on the humanitarian aspects of this. So it's donations.

0:13:51.200 --> 0:13:54.920
<v Speaker 1>Are employees want to donate, so we're also matching their donations. UM,

0:13:54.960 --> 0:13:57.920
<v Speaker 1>we're helping our customers as well with donation buttons on

0:13:58.400 --> 0:14:01.600
<v Speaker 1>charitable organizations in the whole pages of our websites. And

0:14:01.640 --> 0:14:04.960
<v Speaker 1>then in addition to that, UM, focusing on our people.

0:14:05.440 --> 0:14:09.480
<v Speaker 1>So not only are we supporting our team members, UH.

0:14:09.600 --> 0:14:12.160
<v Speaker 1>For example, team members in adjacent countries like Poland, we've

0:14:12.200 --> 0:14:14.600
<v Speaker 1>given them additional time off to take care of themselves

0:14:14.600 --> 0:14:17.000
<v Speaker 1>and their families. But this is something where we're going

0:14:17.040 --> 0:14:19.440
<v Speaker 1>to have to respond to the moment and meet our

0:14:19.480 --> 0:14:22.040
<v Speaker 1>employees where they are, so as we hear feedback on

0:14:22.120 --> 0:14:24.480
<v Speaker 1>what they need, we will meet them in that moment. Well,

0:14:24.600 --> 0:14:26.440
<v Speaker 1>our thanks to both of you, and good luck with

0:14:26.560 --> 0:14:30.720
<v Speaker 1>the ongoing partnership that you've got. Ruba Borno, Global Channel

0:14:30.760 --> 0:14:33.880
<v Speaker 1>chief at Amazon Web Services, on the phone from North Carolina.

0:14:33.960 --> 0:14:37.240
<v Speaker 1>Lauren Dillard, Executive EP of Investment Intelligence over at NASDAC,

0:14:37.320 --> 0:14:39.440
<v Speaker 1>on the phone from Austin, Texas. But we really appreciate

0:14:39.480 --> 0:14:42.520
<v Speaker 1>them also, uh their frankness about what's going on in

0:14:42.720 --> 0:14:44.080
<v Speaker 1>terms of the war in Ukraine.