7.2.0
Elasticsearch, Kibana and Logstash 7.2.0
This release adds support for deploying Elasticsearch Kibana and Logstash 7.2.0 to Azure!
Features
#289 Add Elastic Stack 7.2.0 🥇
This release adds Elastic Stack 7.2.0 to the template, with 7.2.0 now the default version.
There are many new features in 7.2.0 that make it for more like a major version release than a minor, such as the beta release of Elastic SIEM:
Be sure to check out the release blog post for more details.
#293 Deploy multiple Logstash instances
Multiple instances of Logstash can now be deployed, using the vmLogstashCount
parameter to control the number of instances to deploy. Logstash VMs are deployed into their own Availability Set.
#292 Allow load balancer SKU to be selected
It is now possible to choose between Basic and Standard SKU load balancers for both the internal and external load balancer. Please consult the Azure load balancer documentation to understand the differences.
When choosing Standard SKU for the external load balancer, the public IP address assigned to the load balancer will also be Standard SKU, and have an IP addess statically allocated.
Breaking Changes
#295 Replace artifactsBaseUrl
with _artifactsLocation
and _artifactsLocationSasToken
The artifactsBaseUrl
input parameter has been replaced with _artifactsLocation
. A new _artifactsLocationSasToken
parameter has been added. Both parameters are in line with Microsoft's updated best practices for Azure ARM templates.
_artifactsLocation
works the same as artifactsBaseUrl
, with the additional requirement that it must end in a trailing /
. Please see the updated documentation for examples
Bug fixes
- #291 Add native realm when configuring SAML realm
A native realm is explicitly added to elasticsearch.yml configuration, to allow both the native realm and SAML realm to be used for authentication.
Miscellaneous
- #296 Set kibana logging to quiet by default
Kibana logging has been set to silent from the outset, which suppresses all log output. With this change, errors will now be logged. Care should be taken to monitor the size of the Kibana log file, as it will continue to grow over time.