Closed manuasir closed 4 years ago
├── demo
│ ├── deploy.sh
│ ├── elastic
│ ├── images
│ ├── README.md
│ ├── splunk
│ ├── wazuh
│ └── wazuh_template.yml
├── production
│ ├── deploy.sh
│ ├── elastic
│ ├── parameters.json
│ ├── README.md
│ ├── splunk
│ ├── wazuh
│ └── wazuh_template.yml
└── README.md
parameters.json
) with placeholders to ease the environment set up.JavaScript heap out of memory
errors during the Kibana plugin optimization on the provision stage. The development branch has been updated: feature-51-prod-ready-cluster
demo
and production
environments have been bumped to v3.12.2demo
and production
environments. a643438b9af7e2275243d341344850066b3d4ab0, 5ce64443cdca7ef80630fc7967d1462d81f9259eWorking on the route53 records for the template.
EnableDNSRecord
parameter.Subdomain
parameter sets the subdomain name for the loadbalancer.HostedZoneName
sets the parent domain for the loadbalancer and the instances.The following template contains an example list of parameters and value placeholders:
[{
"ParameterKey": "ElasticWazuhVersion",
"ParameterValue": "<ElasticWazuhVersion>"
},
{
"ParameterKey": "WazuhInstanceType",
"ParameterValue": "t2.medium"
},
{
"ParameterKey": "InstallType",
"ParameterValue": "<InstallType>"
},
{
"ParameterKey": "ElasticInstanceType",
"ParameterValue": "t2.large"
},
{
"ParameterKey": "KibanaInstanceType",
"ParameterValue": "t2.large"
},
{
"ParameterKey": "SshUsername",
"ParameterValue": "<SshUsername>"
},
{
"ParameterKey": "SshPassword",
"ParameterValue": "<SshPassword>"
},
{
"ParameterKey": "WazuhServerPort",
"ParameterValue": "1514"
},
{
"ParameterKey": "WazuhRegistrationPort",
"ParameterValue": "1515"
},
{
"ParameterKey": "WazuhRegistrationPassword",
"ParameterValue": "<WazuhRegistrationPassword>"
},
{
"ParameterKey": "WazuhApiPort",
"ParameterValue": "55000"
},
{
"ParameterKey": "WazuhApiAdminUsername",
"ParameterValue": "<WazuhApiAdminUsername>"
},
{
"ParameterKey": "WazuhApiAdminPassword",
"ParameterValue": "<WazuhApiAdminPassword>"
},
{
"ParameterKey": "KeyPairName",
"ParameterValue": "<KeyPairName>"
},
{
"ParameterKey": "AvailabilityZone",
"ParameterValue": "<AvailabilityZone>"
},
{
"ParameterKey": "SSLCertificateARN",
"ParameterValue": "<SSLCertificateARN>"
},
{
"ParameterKey": "EnableDNSRecord",
"ParameterValue": "disabled"
},
{
"ParameterKey": "Subdomain",
"ParameterValue": "<Subdomain>"
},
{
"ParameterKey": "HostedZoneName",
"ParameterValue": "<HostedZoneName>"
}
]
Hi team,
Currently, we provide a way to deploy a specific environment with several customized use cases installed on different agents. The main goal of this task is to implement the ability to deploy a production-ready cluster that includes:
The template should support as many parameters as possible in order to gain flexibility. Also, this environment should be started with the default configuration.
Regards