Elasticsearch не образующий кластер в AWS EC2 VPC

Question

Я создал три узла эластичного поиска в экземплярах EC2 с VPC.Это не формирование кластера вместе.PFB для конфигурации в узлах.

Installed discovery-ec2 plugin

Elasticsearch version: 7.3

Я могу свернуть и пропинговать другие экземпляры, используя ip и 9200

Узел-1

cluster.name: sba
node.name: master-2
cluster.initial_master_nodes: ["master-1","master-2","master-3"]
bootstrap.memory_lock: true
discovery.seed_providers: ec2
network.publish_host: _ec2:privateIp_
network.host: _ec2:privateIp_
transport.publish_host: _ec2:privateIp_
discovery.seed_hosts: ["172.16.1.243","172.16.1.62","172.16.1.132"] 

Узел -2

  cluster.name: sba
    node.name: master-1
    cluster.initial_master_nodes: ["master-1","master-2","master-3"]
    bootstrap.memory_lock: true
    discovery.seed_providers: ec2
    network.publish_host: _ec2:privateIp_
    network.host: _ec2:privateIp_
    transport.publish_host: _ec2:privateIp_
    discovery.seed_hosts: ["172.16.1.243","172.16.1.62","172.16.1.132"]

Журнал запуска Elasticsearch:

[2019-09-19T06:11:43,057][INFO ][o.e.x.s.a.s.FileRolesStore] [master-1] parsed [0] roles from file [/etc/elasticsearch/roles.yml]
[2019-09-19T06:11:43,859][INFO ][o.e.x.m.p.l.CppLogMessageHandler] [master-1] [controller/29816] [Main.cc@110] controller (64 bit): Version 7.3.2 (Build 265429af874fbe) Copyright (c) 2019 Elasticsearch BV
[2019-09-19T06:11:44,655][DEBUG][o.e.a.ActionModule       ] [master-1] Using REST wrapper from plugin org.elasticsearch.xpack.security.Security
[2019-09-19T06:11:45,165][INFO ][o.e.d.DiscoveryModule    ] [master-1] using discovery type [zen] and seed hosts providers [settings, ec2]
[2019-09-19T06:11:45,975][INFO ][o.e.n.Node               ] [master-1] initialized
[2019-09-19T06:11:45,975][INFO ][o.e.n.Node               ] [master-1] starting ...
[2019-09-19T06:11:46,110][INFO ][o.e.t.TransportService   ] [master-1] publish_address {172.16.1.243:9300}, bound_addresses {172.16.1.243:9300}
[2019-09-19T06:11:46,118][INFO ][o.e.b.BootstrapChecks    ] [master-1] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2019-09-19T06:11:46,165][INFO ][o.e.c.c.Coordinator      ] [master-1] cluster UUID [ibbVibMVRuie2Ee6C-Qckw]
[2019-09-19T06:11:46,379][INFO ][o.e.c.s.MasterService    ] [master-1] elected-as-master ([1] nodes joined)[{master-1}{zPKB7YQDQ_mVe8rxflDjug}{hQsUGcEES7G1mI8Jaa-v6A}{172.16.1.243}{172.16.1.243:9300}{dim}{ml.
machine_memory=3887251456, xpack.installed=true, ml.max_open_jobs=20} elect leader, _BECOME_MASTER_TASK_, _FINISH_ELECTION_], term: 13, version: 51, reason: master node changed {previous [], current [{master-
1}{zPKB7YQDQ_mVe8rxflDjug}{hQsUGcEES7G1mI8Jaa-v6A}{172.16.1.243}{172.16.1.243:9300}{dim}{ml.machine_memory=3887251456, xpack.installed=true, ml.max_open_jobs=20}]}
[2019-09-19T06:11:46,497][INFO ][o.e.c.s.ClusterApplierService] [master-1] master node changed {previous [], current [{master-1}{zPKB7YQDQ_mVe8rxflDjug}{hQsUGcEES7G1mI8Jaa-v6A}{172.16.1.243}{172.16.1.243:9300
}{dim}{ml.machine_memory=3887251456, xpack.installed=true, ml.max_open_jobs=20}]}, term: 13, version: 51, reason: Publication{term=13, version=51}
[2019-09-19T06:11:46,604][INFO ][o.e.h.AbstractHttpServerTransport] [master-1] publish_address {172.16.1.243:9200}, bound_addresses {172.16.1.243:9200}
[2019-09-19T06:11:46,605][INFO ][o.e.n.Node               ] [master-1] started
[2019-09-19T06:11:46,951][INFO ][o.e.l.LicenseService     ] [master-1] license [07d759bf-d7ac-4800-b30e-821497ed6190] mode [basic] - valid
[2019-09-19T06:11:46,952][INFO ][o.e.x.s.s.SecurityStatusChangeListener] [master-1] Active license is now [BASIC]; Security is disabled
[2019-09-19T06:11:46,962][INFO ][o.e.g.GatewayService     ] [master-1] recovered [0] indices into cluster_state

Я что-то упустил?Пожалуйста, помогите!