Security posture waste check
OpenSearch No Encryption at Rest
opensearch_no_encryption_at_rest
What it finds
OpenSearch No Encryption at Rest: one of the Security posture checks in the security & compliance group. Checks in this group look for: configuration gaps on resources you pay for: missing encryption, missing deletion protection, public exposure, uncovered backups.
Why it costs money
These are posture findings first. Some also carry a cost, such as a resource nobody backs up or protects properly, and the report labels which is which.
How it is detected
OpenSearch domain without encryption at rest
Detection confidence: HIGH. This is the criterion from our public docs. It runs in a local scan with your own read-only credentials.
AWS's own tools
AWS flags this too, under "Opensearch.1 OpenSearch domains should have encryption at rest enabled".
Checked against the AWS documentation.
Run it yourself
Nothing leaves your machine. The local scan has no telemetry.