Automate should not lose connectivity with AWS ES service

[kalroy]

Describe the bug

Automate has the ability to connect to AWS ElasticSearch Service.
This was part of the release versioned 20201230192246.

We found that Automate looses connectivity with AWS ES service cluster when:

1. the ES cluster is setup without master node
2. the number of data nodes are changed

4645

To Reproduce

Steps to reproduce the behaviour:

• Setup Automate in EC2
• Setup AWS ES service cluster without any master node
• Change the number of data nodes
• Open up Automate UI and click on Compliance/Infrastructure
• Automate would warn that it is not able to fetch the data and data won't be loaded

Expected behaviour

On changing the number of data nodes Automate should be still connected.
The UI should be still working.

Screenshots

Versions (please complete the following information):

• Automate Build Number 20210129162733

Additional context

Aha! Link: https://chef.aha.io/epics/SH-E-463