OpenSearch domain accepts plain HTTP
- Severity
- Medium
- Service
- OpenSearch
- Check ID
- ES_HTTPS_NOT_ENFORCED
What this check finds
The domain endpoint does not require HTTPS, so requests and their credentials or data can be sent unencrypted.
Passing looks like: OpenSearch domains require HTTPS.
How to fix it
Require HTTPS for all traffic to the domain.
AWS CLI
aws opensearch update-domain-config --domain-name DOMAIN --domain-endpoint-options EnforceHTTPS=true,TLSSecurityPolicy=Policy-Min-TLS-1-2-2019-07
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
Amazon OpenSearch Service → Domains → select domain → Actions → Edit security configuration → Require HTTPS.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| PCI-DSS v4.0.1 |
|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs