 I'm going to talk a little bit about OpenSearch today. My name is Kyle. I'm Senior Developer Advocate for OpenSearch at AWS. And I'm exclusively dedicated to OpenSearch. So what I'd like to do today is just first bring in the definition of what OpenSearch is. OpenSearch is a community-driven, we take our marching orders from the community. OpenSearch, search and analytics suite, derived from the Apache 2 licensed Elasticsearch 7.10.2 and Kibana 7.10.2. It consists of a search engine daemon, OpenSearch, which is analogous to Elasticsearch, a visualization and user interface, OpenSearch dashboards, which is analogous to Kibana, as well as functionality, adding tools and plugins. Now, I've said a lot in this slide. Let's go and talk a little bit about the history and why this has come about and why you may have heard of it and what's happening. So Elasticsearch and Kibana existed for a long time. And they were open-source licensed. They had a lot of use cases and our customers at Amazon and AWS, internal users as well, kind of found a number of different things that they wanted to add to this open-source core. And that came in the way of plugins and tools. These were all open-source and we released them together with the open-source core of Elasticsearch and Kibana to create OpenDistro for Elasticsearch. So let's fast forward a little bit that happened in 2019. Let's go to January of 2020, where there was a license change. The creators, Elasticsearch and Kibana, decided to take what was Apache 2 licensed and convert it to SSPL and Elastic License, which those are not open-source licenses. So the decision was made to fork Elasticsearch and Kibana. So what happens then with OpenDistro for Elasticsearch? So at that point, that project was put into maintenance mode and then those plugins and tools were forked to work with this new project. And together that formed OpenSearch. Now I say this because OpenSearch is more than one thing. The collection of things, it's a whole project that has a number of different aspects to it. Now, what's important to that is that all of these pieces are licensed as Apache V2. This allows you to use Modify, Extend, and then monetize, resell, make part of your own product service. And we have that consistently across OpenSearch and OpenSearch dashboards, all plugins and all tools. So what do you do with OpenSearch? So one of the first things you might think of is TextSearch and it's great at that. So it allows you to query your data in a more natural way, sort that data and how it's relevant to you and you're able to have control over it. And then as well, when you start thinking about how you bring data into it, you are able to stream data into OpenSearch. It works great with high volumes and you can be able to query that in near real time. Of course it's distributed so it can work across many different nodes and then have a scale out architecture. And then you're able to analyze that data that you brought in. So you can look at it in visualization, statistics, and there's lots of tools that allow you to do further analysis. Today though, I wanna talk specifically about a use case where you're taking OpenSearch and you are using it to analyze the outputs of testing and build processes. So in a complex piece of software, you have a number of different repos and dependencies that you're building and testing oftentimes many times a day. Now, if you're trying to understand what's going on with that, you have a big challenge ahead of you because you have to take in all that data and then understand what's happening there. If you're to go to every single process and look at those different processes and try to understand what would happen to take you forever. So you can take all that information that the output of these processes and put them into OpenSearch. From there, you can start looking at how you can search through that data just looking for specific keywords as an example or you can aggregate that data and get a higher level view without having to view each individual document. You can then of course take that data and visualize it in a way that will help you understand things without having to page through even the aggregations and present it in a human understandable chart. It's colorful and can be presented to people without a lot of context. And we can even do further things. So one of the things OpenSearch has is built-in anomaly detection. So when you are bringing data in, it can actually look for data that looks out of the ordinary. So for example, if you typically get 50 warnings in a given session, a build and suddenly you're getting 65, 70, 80, you don't have to manually set a threshold that will then look for that area. But what you can also do is set up an alert. So let's say that you set a threshold or an example where you're using your checker you get knowledge data, you can have it make an alert and then send off say a Slack message or an email. So it really is useful in understanding this high volume data and that's where OpenSearch really shines. So if you're interested in this and you want to get involved, go ahead, go over to opensarch.org where you can download or get more information. And if you want to contribute we're on GitHub, we love contributions. So you can visit us on github.com slash opensarch dash project and you can see all the different every post.