Okay, for HTTP protocol, we are using in terms of where we need to communicate to any certain endpoints So let's say HTTPS we are using basically the secure protocol. Okay, so when when I say that we are using the Elasticsearch clusters, okay, that needs an endpoint to be connected with okay And that in point is hosted as a secure way and we are connecting to it with the help of username and password Okay, so basically when When we have set up that Elasticsearch cluster, we have set up that into the Kubernetes So each node or each part of Elasticsearch is acting as a single node in the machine So all of this cluster needs to be connected to the service or that will be on the load balancer on the AWS side basically that needs to be Hosted somewhere in the route 53 so that you will be able to get access to it Okay, so what we do is like we created and we created a service that connects to all these nodes Okay, that reads data that puts data whatever the operations are there that service helps us In this service, we have to connect an ingress. Ingress will act as an internal load balancer for all of our for all of our nodes and all of our clusters. So in this cluster we will access the internal load balancer application in the AWS. Internal load balancer will be connected to the certificate HTTP means secure protocol certificate and also it will be connected to the Route 53 and DNS entries that we have to make. So that's how we are using HTTP or HTTPS protocol for our data communication with Elasticsearch. Also, we are using this HTTPS protocols to our API that is explicitly Made for the different clients that we are hosted on the Lambda Okay, so that Lambda is being connected to the API gateway. API gateway is act as a Act as an intermediary between Lambda and the client. So whatever the request comes to API gateway It will be given to the Lambda that will process the request and revert back to the client with the appropriate response So this in this way API gateway also act as an HTTP creates an HTTP protocols Protocols to connect to your client to your database So basically that's where we are using HTTP as HTTP protocols for our data use cases Okay, again, how do we make sure? The data integrity with it is because we are sure we keep the logs. Basically it checks every Parameter that needs to come here that needs to be common that needs to go from our system We have that kind of a mechanism that validates the data. Is it correct or not? So based on that we make sure the data integrity that we are giving out of this Protocol is correct and it has a secure HTTPS site is a certificate We are reliable on it
