Script contexts unrestricted
All script contexts can run: script.allowed_contexts is unset. Scripts might run in search, ingest, update, aggregations, and other contexts.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Cluster |
| Domains | performance, security-safety |
The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.
script.allowed_contexts is unset, so scripts can run in every context. Current value: inline, stored.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Restrict allowed script contexts
Condition: Always shown for this insight.
Set script.allowed_contexts to the contexts your applications need (for example search, ingest, or update). Do not set none if Kibana, ingest, or search scripts must run. Add the setting in elasticsearch.yml, then restart the node.
Unset means all contexts. none blocks every context.
script.allowed_contexts controls where scripts might run. When the setting is unset, Elasticsearch allows all contexts.
A broad context list increases load risk and the chance that scripts run in paths you did not intend. Set an allowlist of the contexts you actually use.
none blocks all script contexts. Do not use it if Kibana, ingest, or search scripts must run.