AWS ElasticSearch | Concept & Configuration | Integration of CloudWatch Log with ElasticSearch

AWS ElasticSearch | Concept & Configuration | Integration of CloudWatch Log with ElasticSearch



Video will help us to understand the concept of AWS ElasticSearch Domain along with how to configure AWS ES domain and access it from ES head Plugin and Kibana Dashboard. Also i have covered the configuration concept of how to ingest log data from CloudWatch logs to AWS ES.

Below points covered:-

– Concept of AWS ElasticSearch Domain
– Benefits
– Demo:-
1- ES domain Configuration
2- How to Access ES domain link
3- How to ingest log data from CloudWatch to ES engine and analyse the pattern.
4- How to use Kibana Dashboard to check data.

AWS ES Domain Pricing:-

AWS ES Overview:-

Chrome Plugin:- ElasticSearch Head

If you like the video please like , comment , share and subscribe the channel to get more updates on technical videos.

Channel Link:-

Happy Learning !!!

9 thoughts on “AWS ElasticSearch | Concept & Configuration | Integration of CloudWatch Log with ElasticSearch

  1. Hi,

    i have to do the like below tasks in my institute, can i process the same what you said, is it correct for below questions? please respond me ASAP.
    a) Installs ElasticSearch configured in a way that requires credentials and provides encrypted

    communication

    b) Demonstrates that it is functioning
    c) ElasticSearch access and communication must be secure.

  2. Hi, I did the same thing as you did. Basically I have a log groups in CloudWatch that has already some logs. Then I click action to Start stream it to ElasticSearch.

    After I follow through everything, the Elastic Search is still not receiving the data.Could it be because the IAM role execution in the Lambda that sends the logs to ElasticSearch? This is the IAM role that I have set to the Lambda.

    https://drive.google.com/file/d/1qBEtY28tReb8L_aAYSSjZbtFDQWF_Bsp/view?usp=sharing

    I would appreciate your help. Thanks.

Leave a Reply

Your email address will not be published. Required fields are marked *