Benchmark: Elasticsearch
Description
This section contains recommendations for configuring Elasticsearch resources.
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.all_controls_esSnapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.all_controls_es --shareControls
- Elasticsearch domains should have audit logging enabled
- Elasticsearch domains should have cognito authentication enabled
- Elasticsearch domains should have at least three data nodes
- Elasticsearch domains should be configured with at least three dedicated master nodes
- Connections to Elasticsearch domains should be encrypted using TLS 1.2
- ES domain encryption at rest should be enabled
- Elasticsearch domain error logging to CloudWatch Logs should be enabled
- ES domains should be in a VPC
- Elasticsearch domains should have internal user database enabled
- Elasticsearch domain should send logs to CloudWatch
- Elasticsearch domain node-to-node encryption should be enabled