Closed arkheliel closed 3 years ago
Hello @arkheliel ,
Sorry for the inconvenience, let us investigate this problem and we'll get back to you ASAP.
Regards
Hi @manuasir, any idea?
Hello @arkheliel,
I've made a full deployment and was successful. Please, if you could attach some Kibana logs that could help to debug the problem. Maybe the instance type you're currently using for that is not enough? I recommend using t2.large
as a minimum for Kibana.
Hi, @manuasir I tried again but i check and the Kibana wont install.
Deploylog stop here:
Starting process. Checking root. Running as root. Created SSH user. Started SSH service. Added Elasticsearch repo. Installing Elasticsearch. Installed Elasticsearch.
Thanks.
Hello @arkheliel ,
Sorry for the late response. Were you able to resolve this? I couldn't reproduce in my environment. Can you please try with our latest release?
I had the same issue. I set the SSHAccessCidr to my own IP, and then the scripts configure that as the only IP allowed for ssh. Since some of the scripts scp from the other machines being created in the 10.0.x.x network, they die because they cannot copy anything. How should SSHAccessCidr be set to allow the new machines to talk to each other and our own IP to connect?
Oh, also I found the wazuh user was hard coded into some scripts, so if SshUsername is not wazuh, there will be issues there too.
I updated to the latest version v3.13.2_7.9.2
, please check using the latest template.
On the other hand, I've just merged #73 and #74 to fix the issues reported by @synacktic. Much appreciated.
Please, open a new ticket if you still face issues.
I used the YML template directly on AWS CloudFormation. Deployment was successful, but Kibana was not installed.
Branch 3.13.1 used.
Is there another way, or correct way to install the production environment?