okay so we have implemented HTTPS protocol in our cluster basically when we have set up the Elasticsearch cluster okay we need an endpoint to be set up for the data ingestion and the data retrieval because Elasticsearch is in a database or you can say the search engine or the data store okay so we store around 200 TB of data in single cluster and there are like multiple clusters that shows the old storage as a so there would be around five like a let's say five petabytes of data or more than that so but hot cluster we use is the around 2 TB of data to access this cluster we need some kind of a endpoint to push the data to create the data to post the data to retrieve the data and all those stuff so how we have implemented in our Kubernetes cluster we have created a service that connects to this all nodes all nodes in this is Elasticsearch nodes from that from that service we have to give some protocols like which kind of a security protocol we will be using all this stuff we have to give which kind of a port we will be using so we are using HTTPS and 9092 port for the Elasticsearch okay so 9092 port is defaulted by Elasticsearch okay from that service we have created an ingress, ingress is act as an internal load balancer for the Kubernetes that will that will circulate your request to a different different node based on the coming request and the node of the particular system and that ingress will be connected to the AWS load balancer so from and if we need to access and that load balancer will have route 53 and DNS entries as well so in the DNS entries we have to give that entry like you can see the URL entry or the host that will be connected to the route 53 route 53 will also have the certificates for HTTPS and all those things so we can easily get an implemented HTTPS protocol for our Elasticsearch in this way okay apart from that we have implemented HTTPS protocol for our API services okay so for that we have used this route 53 you know route 53 API gateway and lambda that will connect to our basically API gateway directly there is no need of load balancer over here but it will be needed to connect to a route 53 so that's how we have maintained HTTPS gate for our API services so yeah
