Script Allowed Types
All script types, including inline and stored scripts, are allowed on the cluster. Broad allowance increases the chance of expensive or unsafe scripts during queries and updates.
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.
The allowed scripts are: 12
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Restrict script types
Condition: Always shown for this insight.
Set script.allowed_types: none in elasticsearch.yml, then restart the node.
Impact: Running scripts with all types allowed can lead to costly scripts being allowed to run, which in turn might cause performance issues in the cluster. Query scripts can place a heavy load on your cluster, particularly if the scripts are not written carefully with thought for the resources they might require. For this reason it is a best practice to limit both the type of scripts that can run on a cluster, and also the contexts in which scripts can run. You can set script.allowed_types to inline, stored, both or none. these values are perfectly valid, since many applications require scripts to enable them to run correctly. To set this value, you need to know whether your application requires the use of scripts or not, and how those scripts are implemented.