Benchmark: Elasticsearch
Overview
This section contains recommendations for configuring Elasticsearch resources and options.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-complianceStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select Elasticsearch.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.foundational_security_esSnapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.foundational_security_es --shareControls
- 1 Elasticsearch domains should have encryption at-rest enabled
- 2 Elasticsearch domains should not be publicly accessible
- 3 Amazon Elasticsearch Service domains should encrypt data sent between nodes
- 4 Elasticsearch domain error logging to CloudWatch Logs should be enabled
- 5 Elasticsearch domains should have audit logging enabled
- 6 Elasticsearch domains should have at least three data nodes
- 7 Elasticsearch domains should be configured with at least three dedicated master nodes
- 8 Connections to Elasticsearch domains should be encrypted using TLS 1.2