Amazon Elasticsearch can improve the bullion in the near search and the ease of integration with Kibana. Additionally, there could be more flexibility in the configuration and documentation.

Not for all the projects I saw, but most of the projects were using Elasticsearch, which is very common. In my case, I have faced two scenarios with the solution. Other than that, generic solutions like SNS, SQS, and Lambda are some of the very generic tools we are using.

Regarding what I would like to see improved in the solution, I would say that, basically, the configuration part is an area with a shortcoming. We have a DevOps person, so all these things are configured in the Terraform through the Terraform script we use. The DevOps team used to take care of it. To run the process or run the services and how to use the services are the parts for which we are using the solution. Some upgradation is required on the configuration side so that we can get to use it. In that case, I have to check on that area with the DevOps.

I want to see a new feature in Amazon Elasticsearch Service that allows users to create default filters for filtered levels. 

This would make it easier for users to filter the data and find the information more quickly.

One glaring issue was with our mapping configuration as the system accepted the data we posted, but after a few months, when we attempted complex queries, we realized the date formatting had become problematic. Modifying the mapping at that point proved to be a costly and time-consuming task.

The configuration should be more straightforward because we had to select a lot of things. This included the CPU and the configuration required for the alternative instance. We would prefer that whatever we have configured for EC2 is just copied, and alternate operations required at the user's end can be done with just a simple click. You should not have to enter the details again, such as what memory is required or what CPUs are needed.

There is the problem with the database. If we want to use the database of the MySQL on body and other things, Amazon only provides the host to run to our applications bias, but there is no option to manage the database within the Elasticsearch product.