Benchmark: Opensearch
Overview
This section contains recommendations for configuring OpenSearch 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 Opensearch.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.foundational_security_opensearchSnapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.foundational_security_opensearch --shareControls
- 1 OpenSearch domains should have encryption at rest enabled
- 2 OpenSearch domains should not be publicly accessible
- 3 OpenSearch domains should encrypt data sent between nodes
- 4 OpenSearch domain error logging to CloudWatch Logs should be enabled
- 5 OpenSearch domains should have audit logging enabled
- 6 OpenSearch domains should have at least three data nodes
- 7 OpenSearch domains should have fine-grained access control enabled
- 8 Connections to OpenSearch domains should be encrypted using TLS 1.2
- 10 OpenSearch domains should have the latest software update installed