Check ID:
Provider: AWS
Service:
Severity: LOW
Categories:
Resource type:
opensearch_service_domains_cloudwatch_logging_enabledProvider: AWS
Service:
opensearchSeverity: LOW
Categories:
loggingResource type:
AwsOpenSearchServiceDomainWhat this check verifies
Amazon OpenSearch Service domains have slow log publishing enabled for both search and indexing operations to CloudWatch Logs (SEARCH_SLOW_LOGS and INDEX_SLOW_LOGS).
Risk
Without these logs, visibility into expensive searches and slow indexing is lost, masking hotspots and abuse.- Availability: timeouts, throttling, node pressure
- Integrity: missed or delayed indexing
- Operations: slower incident response and capacity planning
Recommendation
Enable bothSEARCH_SLOW_LOGS and INDEX_SLOW_LOGS for all domains and publish to CloudWatch. Set meaningful thresholds and retention, separate log groups, and alert on anomalies. Apply least privilege to log access and use defense in depth with complementary error and audit logs.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-createdomain-configure-slow-logs.html
- https://support.icompaas.com/support/solutions/articles/62000129471-ensure-amazon-elasticsearch-service-es-domains-have-logging-enabled
- https://bigdataboutique.com/blog/inspecting-search-slow-logs-on-elasticsearch-and-opensearch-b05d87
- https://repost.aws/knowledge-center/opensearch-troubleshoot-slow-logs
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/Elasticsearch/slow-logs.html
- https://medium.com/heyjobs-tech/how-to-create-an-opensearch-cluster-using-terraform-926b4a62b489
- https://docs.aws.amazon.com/opensearch-service/latest/developerguide/createdomain-configure-slow-logs.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = opensearch_service_domains_cloudwatch_logging_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks