Q:

SonarQube, Fargate & AWS ElasticSearch

I’m running SonarQube 7.9 LTS Community. I am hosting it on AWS using Fargate, RDS and it’s working. I’d like to however switch from using the inbuilt SonarQube ElasticSearch to the AWS ElasticSearch.
Is this possible when using the Community Edition? I ask because essentially what I am trying to setup is pretty much the DataCenter edition as described here https://docs.sonarqube.org/latest/setup/install-cluster/. It states " Running SonarQube as a Cluster is only possible with a Data Center Edition ."
I am not really looking for high availability. It just isn’t good practice to run ElasticSearch within a Fargate container as the Elasticsearch indexes will be deleted whenever the container is replaced.
In addition to the above the SonarQube doco states:
" By default, Elasticsearch data is stored in $SONARQUBE-HOME/data , but this is not recommended for production instances. Instead, you should store this data elsewhere, ideally in a dedicated volume with fast I/O. Beyond maintaining acceptable performance, doing so will also ease the upgrade of SonarQube." (https://docs.sonarqube.org/latest/setup/install-server/)
So yeah, I’d like to be able to use the AWS Elasticsearch, not the SonarQube integrated one. Is this possible?

A:

It appears (see link below) you must use the ElasticSearch embedded within the SonarQube. You cannot use any third party ElasticSearch services etc. 
https://community.sonarsource.com/t/sonarqube-fargate-aws-elasticsearch/11576/5

