Skip to main content
Warning This document has not been updated for a while now. It may be out of date.
Last updated: 9 Jun 2020

govuk-aws: 22. Remove the Elasticsearch proxy

Date: 2017-08-16




We currently have a local nginx based proxy for Elasticsearch connections on a number of our machines. The original reason for this was:

Load balance connections to Elasticsearch by creating a loopback-only
vhost in Nginx which will forward to a set of Elasticsearch servers.

This is for the benefit of applications with client libraries that don't
support native cluster awareness or load balancing.

In the AWS environments these services are behind an ELB so this layer may no longer be required.


We've tested the instances in AWS without the local proxies and we have not discovered any degradation of service when using the ELBs. In light of this we will remove the configuration and exclude this puppet code from running in AWS and accept the ELBs as its replacement.


There will be a slight difference, considered by the team to be an improvement, between the current environments and the new, AWS ones. This means we won't be testing the exact same thing but will simplify the networking and application data flow paths.