# Neo4j Causal Cluster on AWS EC2 Instance **URL:** \ **Category:** Cluster\ **Created:** [December 17, 2020, 3:58pm UTC](https://community.neo4j.com/t/neo4j-causal-cluster-on-aws-ec2-instance/30550 "2020-12-17T15:58:10Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![abhijithwarrier](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/abhijithwarrier/32/4175_2.png) [@abhijithwarrier](https://community.neo4j.com/u/abhijithwarrier)\ **Post date:** [December 17, 2020, 3:58pm UTC](https://community.neo4j.com/t/neo4j-causal-cluster-on-aws-ec2-instance/30550/1 "2020-12-17T15:58:11Z")
In our AWS Account we have created 3 EC2 instances each with Neo4j Enterprise Causal Cluster AMIs.. We made necessary configurations in the neo4j.template of each Neo4j EC2 Instance to enable Causal Clustering. After making the necessary changes, the system was restarted using the command ./etc/init.d/neo4j start. When checked the status using systemctl status neo4j, it is still neo4j\_mode as SINGLE though it was set to CORE. Also the Neo4j UI is not accessible from the browser window. How can we enable Neo4j Causal Clustering using 3 EC2 Instances with Neo4j AMIs. Is there any specific AMI that we should use with EC2 to enable Causal Clustering. Is there any documentation for the same (EC2 Neo4j Causal Clustering)? ---
**Author:** ![david\_allen](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/david_allen/32/13090_2.png) [@david\_allen](https://community.neo4j.com/u/david_allen)\ **Post date:** [December 17, 2020, 6:12pm UTC](https://community.neo4j.com/t/neo4j-causal-cluster-on-aws-ec2-instance/30550/2 "2020-12-17T18:12:13Z")
Make sure to read the neo4j configuration section of this page: > **[Neo4j Cloud Virtual Machines - Developer Guides](https://neo4j.com/developer/neo4j-cloud-vms/)** > > This guide describes how Neo4j deployed in cloud virtual machines operate, and how they differ from other installation platforms for Neo4j. Can you please paste a snippet of your neo4j.template file, and your neo4j.conf file, after you start the service? ---
**Author:** ![abhijithwarrier](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/abhijithwarrier/32/4175_2.png) [@abhijithwarrier](https://community.neo4j.com/u/abhijithwarrier)\ **Post date:** [December 17, 2020, 6:27pm UTC](https://community.neo4j.com/t/neo4j-causal-cluster-on-aws-ec2-instance/30550/3 "2020-12-17T18:27:14Z")
Below are the configuration changes that we made in the neo4j.template file of one of the EC2 instances.Similar changes were made in the other EC2 instances neo4j.template files. The parameters where Private IPs are used, there we also tried using Public IPs instead of Private IPs. dbms.security.procedures.unrestricted=apoc._,gds._ # Paths of directories in the installation. dbms.directories.data=/var/lib/neo4j/data dbms.directories.plugins=/var/lib/neo4j/plugins dbms.directories.logs=/var/log/neo4j dbms.directories.lib=/usr/share/neo4j/lib dbms.directories.run=/var/run/neo4j #dbms.directories.metrics=/var/lib/neo4j/metrics #dbms.directories.dumps.root=data/dumps dbms.directories.import=/var/lib/neo4j/import dbms.security.auth\_enabled=true #dbms.allow\_upgrade=true #dbms.memory.heap.initial\_size=512m #dbms.memory.heap.max\_size=512m #dbms.memory.pagecache.size=10g dbms.tx\_state.memory\_allocation=ON\_HEAP dbms.backup.enabled=$dbms\_backup\_enabled dbms.ssl.policy.backup.trust\_all=$dbms\_ssl\_policy\_backup\_trust\_all dbms.backup.listen\_address=0.0.0.0:6364 #\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* # Network connector configuration #\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* dbms.default\_listen\_address=0.0.0.0 dbms.default\_advertised\_address=(PRIVATE IP OF EC2) # Bolt connector dbms.connector.bolt.enabled=$dbms\_connector\_bolt\_enabled dbms.connector.bolt.tls\_level=$dbms\_connector\_bolt\_tls\_level dbms.connector.bolt.advertised\_address=$dbms\_connector\_bolt\_advertised\_address dbms.connector.bolt.listen\_address=:7689 # HTTP Connector. There must be exactly one HTTP connector. dbms.connector.http.enabled=$dbms\_connector\_http\_enabled dbms.connector.http.advertised\_address=$dbms\_connector\_http\_advertised\_address dbms.connector.http.listen\_address=:7476 # HTTPS Connector. There can be zero or one HTTPS connectors. dbms.connector.https.enabled=$dbms\_connector\_https\_enabled dbms.connector.https.advertised\_address=$dbms\_connector\_https\_advertised\_address dbms.connector.https.listen\_address=:6476 dbms.ssl.policy.https.base\_directory=$dbms\_ssl\_policy\_https\_base\_directory dbms.ssl.policy.https.client\_auth=$dbms\_ssl\_policy\_https\_client\_auth dbms.ssl.policy.https.trust\_all=$dbms\_ssl\_policy\_https\_trust\_all #\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* # Causal Clustering Configuration #\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* causal\_clustering.minimum\_core\_cluster\_size\_at\_formation=3 causal\_clustering.minimum\_core\_cluster\_size\_at\_runtime=3 causal\_clustering.initial\_discovery\_members=(PRIVATE IP OF EC2 SERVER-1):5000,(PRIVATE IP OF EC2 SERVER-2):5001,(PRIVATE IP OF EC2 SERVER-3):5002 causal\_clustering.discovery\_advertised\_address=$causal\_clustering\_discovery\_advertised\_address causal\_clustering.discovery\_listen\_address=:5002 causal\_clustering.transaction\_listen\_address=:6002 causal\_clustering.discovery\_type=LIST causal\_clustering.raft\_listen\_address=:7002