Get Deployment Elasticsearch Resource Info
Get info about an Elasticsearch Resource belonging to a given Deployment.
Path parameters
-
Identifier for the Deployment
-
User-specified RefId for the Resource (or '_main' if there is only one).
Query parameters
-
Whether to include the Elasticsearch 2.x security information in the response - can be large per cluster and also include credentials.
Default value is
false
. -
Whether to include the full cluster metadata in the response - can be large per cluster and also include credentials.
Default value is
false
. -
Whether to include the full current and pending plan information in the response - can be large per cluster.
Default value is
true
. -
Whether to include with the current and pending plan information the attempt log - can be very large per cluster.
Default value is
false
. -
Whether to include with the current and pending plan information the plan history- can be very large per cluster.
Default value is
false
. -
If showing plans, whether to show values that are left at their default value (less readable but more informative).
Default value is
false
. -
If showing plans, whether to leave pre-2.0.0 plans in their legacy format (the default), or whether to update them to 2.0.x+ format (if 'true').
Default value is
false
. -
Number of system alerts (such as forced restarts due to memory limits) to be included in the response - can be large per cluster. Negative numbers or 0 will not return field.
Default value is
0
. -
Whether to show cluster settings in the response.
Default value is
false
. -
If showing plans, whether to enrich the plan by including the missing elements from the deployment template it is based on.
Default value is
true
. -
If set (defaults to false) then removes the transient section from all child resources, making it safe to reapply via an update
Default value is
false
.
Responses
-
Standard response.
Hide response attributes Show response attributes object
-
The locally-unique user-specified id of a Resource
-
The randomly-generated id of a Resource
-
The region where this resource exists
-
Info for the resource.
Hide info attributes Show info attributes object
-
The id of the cluster
-
The name of the cluster
-
The id of the deployment that this Elasticsearch belongs to.
-
Whether the cluster is healthy or not (one or more of the info subsections will have healthy: false)
-
Cluster status
Values are
initializing
,stopping
,stopped
,rebooting
,restarting
,reconfiguring
, orstarted
. -
Information about the current, pending, and past Elasticsearch cluster plans.
Hide plan_info attributes Show plan_info attributes object
-
Whether the plan situation is healthy (if unhealthy, means the last plan attempt failed)
-
Information about the Elasticsearch cluster plan.
Hide current attributes Show current attributes object
-
A UUID for each plan attempt
-
A human readable name for each plan attempt, only populated when retrieving plan histories
-
Either the plan ended successfully, or is not yet completed (and no errors have occurred)
-
When this plan attempt (ie to apply the plan to the cluster) started (ISO format in UTC)
-
If this plan completed or failed (ie is not pending), when the attempt ended (ISO format in UTC)
-
If this plan is not current or pending, when the plan was no longer active (ISO format in UTC)
-
The plan for building this Elasticsearch cluster
Hide plan attributes Show plan attributes object
-
The topology of the Elasticsearch nodes, including the number, capacity, and type of nodes, and where they can be allocated.
Hide cluster_topology attributes Show cluster_topology attributes object
-
Unique identifier of this topology element
-
Controls the combinations of Elasticsearch node types. TIP: By default, the Elasticsearch node is master eligible, can hold data, and run ingest pipelines. WARNING: Do not set for tiebreaker topologies.
Hide node_type attributes Show node_type attributes object
-
Defines whether this node can be elected master (default: false)
-
Defines whether this node can hold data (default: false)
-
Defines whether this node can run an ingest pipeline (default: false)
-
Defines whether this node can run ml jobs, valid only for versions 5.4.0 or greater (default: false)
-
-
The list of node roles for this topology element (ES version >= 7.10). Allowable values are: master, ingest, ml, data_hot, data_content, data_warm, data_cold, data_frozen, remote_cluster_client, transform
Values are
master
,ingest
,ml
,data_hot
,data_content
,data_warm
,data_cold
,data_frozen
,remote_cluster_client
, ortransform
. -
The default number of zones in which data nodes will be placed
-
The Elasticsearch cluster settings. When specified at the top level, provides a field-by-field default. When specified at the topology level, provides the override settings.
Hide elasticsearch attributes Show elasticsearch attributes object
-
The version of the Elasticsearch cluster (must be one of the ECE supported versions). Currently cannot be different across the topology (and is generally specified in the globals). Defaults to the latest version if not specified.
-
A docker URI that allows overriding of the default docker image specified for this version
-
A subset of Elasticsearch settings. TIP: To define the complete set of Elasticsearch settings, use
ElasticsearchSystemSettings
withuser_settings_override*
anduser_settings*
.Hide system_settings attributes Show system_settings attributes object
-
Controls the languages supported by the Elasticsearch cluster, such as Painless, Mustache, and Expressions. Controls how the languages are used, such as file, index, and inline. TIP: For complex configurations, leave these blank and configure these settings in the user YAML or JSON.
Hide scripting attributes Show scripting attributes object
-
(5.x+ only) If enabled (the default) then the painless scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.painless.[file|stored|inline]')
-
(5.x+ only) If enabled (the default) then the mustache scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.mustache.[file|stored|inline]')
-
(5.x+ only) If enabled (the default) then the expressions scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.expression.[file|stored|inline]')
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide stored attributes Show stored attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide file attributes Show file attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide inline attributes Show inline attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
-
Limits remote Elasticsearch clusters that can be used as the source for '_reindex' API commands
-
If true (the default), then any write operation on an index that does not currently exist will create it. NOTES: (Corresponds to the parameter 'action.auto_create_index')
-
Defaults to false on versions <= 7.2.0, true otherwise. If false, then the API commands to close indices are disabled. This is important because Elasticsearch does not snapshot or migrate close indices on versions under 7.2.0, therefore standard Elastic Cloud configuration operations will cause irretrievable loss of indices' data. NOTES: (Corresponds to the parameter 'cluster.indices.close.enable')
-
If true (default is false) then the index deletion API will not support wildcards or '_all'. NOTES: (Corresponds to the parameter 'action.destructive_requires_name')
-
The trigger engine for Watcher, defaults to 'scheduler' - see the xpack documentation for more information. NOTES: (Corresponds to the parameter '(xpack.)watcher.trigger.schedule.engine', depending on version. Ignored from 6.x onwards.)
-
(2.x only - to get the same result in 5.x template mappings must be used) Sets the default number of shards per index, defaulting to 1 if not specified. (Corresponds to the parameter 'index.number_of_shards' in 2.x, not supported in 5.x)
-
The default interval at which monitoring information from the cluster if collected, if monitoring is enabled. NOTES: (Corresponds to the parameter 'marvel.agent.interval' in 2.x and 'xpack.monitoring.collection.interval' in 5.x)
-
The duration for which monitoring history is stored (format '(NUMBER)d' eg '3d' for 3 days). NOTES: ('Corresponds to the parameter xpack.monitoring.history.duration' in 5.x, defaults to '7d')
-
-
An arbitrary JSON object allowing cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters arey are on the allowlist and not on the denylist. NOTES: (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Elasticsearch settings)
-
An arbitrary YAML object allowing cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters arey are on the allowlist and not on the denylist. NOTES: (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Elasticsearch settings)
-
An arbitrary JSON object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), ie in addition to the documented 'system_settings'. NOTES: (This field together with 'system_settings' and 'user_settings*' defines the total set of Elasticsearch settings)
-
An arbitrary YAML object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), ie in addition to the documented 'system_settings'. NOTES: (This field together with 'system_settings' and 'user_settings*' defines the total set of Elasticsearch settings)
-
A list of plugin names from the Elastic-supported subset that are bundled with the version images. NOTES: (Users should consult the Elastic stack objects to see what plugins are available, this is currently only available from the UI)
-
A list of admin-uploaded plugin objects that are available for this user.
A list of admin-uploaded plugin objects.
Hide user_plugins attributes Show user_plugins attributes object
-
A list of admin-uploaded bundle objects (eg scripts, synonym files) that are available for this user.
A list of admin-uploaded bundle objects, such as scripts and synonym files.
Hide user_bundles attributes Show user_bundles attributes object
-
The name of the bundle
-
The URL of the bundle, which must be accessible from the ECE infrastructure. This URL could be cached by platform, make sure to change it when updating the bundle
-
The supported Elasticsearch version (must match the version in the plan)
-
-
Defines the index curation routing for the cluster
-
Defines the Elasticsearch node attributes for the instances in the topology
-
-
Controls the allocation of this topology element as well as allowed sizes and node_types. It needs to match the id of an existing instance configuration.
-
The version of the Instance Configuration Id. If it is unset, the meaning depends on read vs writes. For deployment reads, it is equivalent to version 0 (or the IC is unversioned); for deployment creates and deployment template use, it is equivalent to 'the latest version'; and for deployment updates, it is equivalent to 'retain the current version'.
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
An arbitrary JSON object overriding the default autoscaling policy. Don't set unless you really know what you are doing.
-
Controls for the topology element. Only used as part of the deployment template. Ignored if included as part of a deployment.
Hide topology_element_control attribute Show topology_element_control attribute object
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
-
Set to true to enable autoscaling for this topology element, even if the cluster-level 'autoscaling_enabled' field is false. Note that 'autoscaling_tier_override' cannot be set to false if cluster-level 'autoscaling_enabled' is true. Currently only supported for the 'ml' tier
-
-
The Elasticsearch cluster settings. When specified at the top level, provides a field-by-field default. When specified at the topology level, provides the override settings.
Hide elasticsearch attributes Show elasticsearch attributes object
-
The version of the Elasticsearch cluster (must be one of the ECE supported versions). Currently cannot be different across the topology (and is generally specified in the globals). Defaults to the latest version if not specified.
-
A docker URI that allows overriding of the default docker image specified for this version
-
A subset of Elasticsearch settings. TIP: To define the complete set of Elasticsearch settings, use
ElasticsearchSystemSettings
withuser_settings_override*
anduser_settings*
.Hide system_settings attributes Show system_settings attributes object
-
Controls the languages supported by the Elasticsearch cluster, such as Painless, Mustache, and Expressions. Controls how the languages are used, such as file, index, and inline. TIP: For complex configurations, leave these blank and configure these settings in the user YAML or JSON.
Hide scripting attributes Show scripting attributes object
-
(5.x+ only) If enabled (the default) then the painless scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.painless.[file|stored|inline]')
-
(5.x+ only) If enabled (the default) then the mustache scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.mustache.[file|stored|inline]')
-
(5.x+ only) If enabled (the default) then the expressions scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.expression.[file|stored|inline]')
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide stored attributes Show stored attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide file attributes Show file attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide inline attributes Show inline attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
-
Limits remote Elasticsearch clusters that can be used as the source for '_reindex' API commands
-
If true (the default), then any write operation on an index that does not currently exist will create it. NOTES: (Corresponds to the parameter 'action.auto_create_index')
-
Defaults to false on versions <= 7.2.0, true otherwise. If false, then the API commands to close indices are disabled. This is important because Elasticsearch does not snapshot or migrate close indices on versions under 7.2.0, therefore standard Elastic Cloud configuration operations will cause irretrievable loss of indices' data. NOTES: (Corresponds to the parameter 'cluster.indices.close.enable')
-
If true (default is false) then the index deletion API will not support wildcards or '_all'. NOTES: (Corresponds to the parameter 'action.destructive_requires_name')
-
The trigger engine for Watcher, defaults to 'scheduler' - see the xpack documentation for more information. NOTES: (Corresponds to the parameter '(xpack.)watcher.trigger.schedule.engine', depending on version. Ignored from 6.x onwards.)
-
(2.x only - to get the same result in 5.x template mappings must be used) Sets the default number of shards per index, defaulting to 1 if not specified. (Corresponds to the parameter 'index.number_of_shards' in 2.x, not supported in 5.x)
-
The default interval at which monitoring information from the cluster if collected, if monitoring is enabled. NOTES: (Corresponds to the parameter 'marvel.agent.interval' in 2.x and 'xpack.monitoring.collection.interval' in 5.x)
-
The duration for which monitoring history is stored (format '(NUMBER)d' eg '3d' for 3 days). NOTES: ('Corresponds to the parameter xpack.monitoring.history.duration' in 5.x, defaults to '7d')
-
-
An arbitrary JSON object allowing cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters arey are on the allowlist and not on the denylist. NOTES: (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Elasticsearch settings)
-
An arbitrary YAML object allowing cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters arey are on the allowlist and not on the denylist. NOTES: (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Elasticsearch settings)
-
An arbitrary JSON object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), ie in addition to the documented 'system_settings'. NOTES: (This field together with 'system_settings' and 'user_settings*' defines the total set of Elasticsearch settings)
-
An arbitrary YAML object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), ie in addition to the documented 'system_settings'. NOTES: (This field together with 'system_settings' and 'user_settings*' defines the total set of Elasticsearch settings)
-
A list of plugin names from the Elastic-supported subset that are bundled with the version images. NOTES: (Users should consult the Elastic stack objects to see what plugins are available, this is currently only available from the UI)
-
A list of admin-uploaded plugin objects that are available for this user.
A list of admin-uploaded plugin objects.
Hide user_plugins attributes Show user_plugins attributes object
-
A list of admin-uploaded bundle objects (eg scripts, synonym files) that are available for this user.
A list of admin-uploaded bundle objects, such as scripts and synonym files.
Hide user_bundles attributes Show user_bundles attributes object
-
The name of the bundle
-
The URL of the bundle, which must be accessible from the ECE infrastructure. This URL could be cached by platform, make sure to change it when updating the bundle
-
The supported Elasticsearch version (must match the version in the plan)
-
-
Defines the index curation routing for the cluster
-
Defines the Elasticsearch node attributes for the instances in the topology
-
-
Documents which deployment template was used in the creation of this plan
-
Defines the configuration parameters that control how the plan is applied. For example, the Elasticsearch cluster topology and Elasticsearch settings.
Hide transient attributes Show transient attributes object
-
The options for performing a plan change. Specify only one property each time. The default is
grow_and_shrink
.Hide strategy attributes Show strategy attributes object
-
Performs inline, rolling configuration changes that mutate existing containers. TIP: This is the fastest way to update a plan, but can fail for complex plan changes, such as topology changes. Also, this is less safe for configuration changes that leave a cluster in a non running state. NOTE: When you perform a major version upgrade, and 'group_by' is set to 'pass:macros[all]';, rolling is required.
Hide rolling attributes Show rolling attributes object
-
Specifies the grouping attribute to use when rolling several instances. Instances that share the same value for the provided attribute key are rolled together as a unit. Examples that make sense to use are '__all__' (roll all instances as a single unit), 'logical_zone_name' (roll instances by zone), '__name__' (roll one instance at a time, the default if not specified). Note that '__all__' is required when performing a major version upgrade
-
Whether we allow changing the capacity of instances (default false). This is currently implemented by stopping, re-creating then starting the affected instance on its associated allocator when performing the changes. NOTES: This requires a round-trip through the allocation infrastructure of the active constructor, as it has to reserve the target capacity without over-committing
-
Whether to skip attempting to do a synced flush on the filesystem of the container (default: false), which is less safe but may be required if the container is unhealthy
-
The time, in seconds, to wait for shards that show no progress of initializing before rolling the next group (default: 10 minutes)
-
-
A strategy that creates instances with the new plan, migrates data from the old instances, then shuts down the old instances.
GrowShrinkStrategyConfig
is safer than 'rolling' and ensures single node availability during a plan change, but can be a lot slower on larger clusters. -
A strategy that creates new Elasticsearch instances, Kibana instances, and APM Servers with the new plan, then migrates the node data to minimize the amount of spare capacity.
-
A strategy that lets constructor choose the most optimal way to execute the plan.
-
-
The configuration settings for the timeout and fallback parameters.
Hide plan_configuration attributes Show plan_configuration attributes object
-
The total timeout in seconds after which the plan is cancelled even if it is not complete. Defaults to 4x the max memory capacity per node (in MB). NOTES: A 3 zone cluster with 2 nodes of 2048 each would have a timeout of 4*2048=8192 seconds. Timeout does not include time required to run rollback actions.
-
This timeout determines how long to give a cluster after it responds to API calls before performing actual operations on it. It defaults to 5s
-
If true (default: false), does not take (or require) a successful snapshot to be taken before performing any potentially destructive changes to this cluster
-
If taking a snapshot (ie unless 'skip_snapshots': true) then will retry on failure at most this number of times (default: 5)
-
When you take a snapshot and 'skip_snapshots' is false, specifies the maximum age in seconds of the most recent snapshot before a new snapshot is created. Default is 300
-
If true (default false), does not clear the maintenance flag (which prevents its API from being accessed except by the constructor) on new instances added until after a snapshot has been restored, otherwise, the maintenance flag is cleared once the new instances successfully join the new cluster
-
Set to 'forced' to force a reboot as part of the upgrade plan. NOTES: (ie taking an existing plan and leaving it alone except for setting 'transient.plan_configuration.cluster_reboot': 'forced' will reboot the cluster)
Value is
forced
.
-
-
Restores a snapshot from a local or remote repository.
Hide restore_snapshot attributes Show restore_snapshot attributes object
-
If specified, contains the name of the snapshot repository - else will default to the Elastic Cloud system repo ('found-snapshots')
-
The name of the snapshot to restore. Use '__latest_success__' to get the most recent snapshot from the specified repository
-
Raw remote snapshot restore settings. Do not send this if you are sending source_cluster_id
-
The configuration for the restore command, such as which indices you want to restore.
Hide restore_payload attributes Show restore_payload attributes object
-
The list of indices to restore (supports +ve and -ve selection and wildcarding - see the default Elasticsearch index format documentation)
-
This JSON object (merged with the 'indices' field (if present) is passed untouched into the restore command - see the Elasticsearch '_snapshot' documentation for more details on supported formats
-
-
The restore strategy to use. Defaults to a full restore. Partial restore will attempt to restore unavailable indices only
Values are
partial
,full
, orrecovery
. -
If specified, contains the name of the source cluster id. Do not send this if you are sending repository_config
-
-
The list of resources that will be configured as remote clusters
Hide remote_clusters attribute Show remote_clusters attribute object
-
The remote resources
The Elasticsearch resource used as a Remote Cluster.
Hide resources attributes Show resources attributes object
-
The id of the deployment
-
The locally-unique user-specified id of an Elasticsearch Resource
-
The alias for this remote cluster. Aliases must only contain letters, digits, dashes and underscores
-
If true, skip this cluster during search if it is disconnected. Default: false
-
Information about a Remote Cluster.
Hide info attributes Show info attributes object
-
Whether or not the remote cluster is healthy
-
Whether or not there is at least one connection to the remote cluster.
-
Whether or not the remote cluster version is compatible with this cluster version.
-
Whether or not the remote cluster is trusted by this cluster.
-
Whether or not the remote cluster trusts this cluster back.
-
-
-
-
If specified, contains transient settings to be applied to an Elasticsearch cluster during changes,default values shown below applied. These can be overridden by specifying them in the map (or null to unset). Additional settings can also be set. Settings will be cleared after the plan has finished. If not specified, no settings will be applied. NOTE: These settings are only explicitly cleared for 5.x+ clusters, they must be hand-reset to their defaults in 2.x- (or a cluster reboot will clear them).
- indices.store.throttle.max_bytes_per_sec: 120Mb
- indices.recovery.max_bytes_per_sec: 120Mb
- cluster.routing.allocation.cluster_concurrent_rebalance: 5
- cluster.routing.allocation.node_initial_primaries_recoveries: 5
- cluster.routing.allocation.node_concurrent_incoming_recoveries: 5 For version 8.1 and later no defaults are provided through this mechanism, but instead hardware dependent settings are provided to each instance.
-
-
Enable autoscaling for this Elasticsearch cluster.
-
-
Information about a step in a plan.
Hide plan_attempt_log attributes Show plan_attempt_log attributes object
-
ID of current step
-
When the step started (ISO format in UTC)
-
When the step completed (ISO format in UTC)
-
The duration of the step in MS
-
The status of the step (success, warning, error - warning means something didn't go as expected but it was not serious enough to abort the plan)
Values are
success
,warning
,error
, orpending
. -
Current stage that the step is in
Values are
starting
,completed
, orin_progress
. -
Human readable summaries of the step, including messages for each stage of the step
The log message from a specified stage of an executed step in a plan.
Hide info_log attributes Show info_log attributes object
-
Timestamp marking on info log of step
-
Time in milliseconds since previous log message
-
Stage that info log message takes place in
Values are
starting
,completed
, orin_progress
. -
Human readable log message
-
A map with details for the log about what happened during the step execution. Keys and values for are always both strings, representing the name of the detail and its value, respectively.
-
The failure type, in case the step failed
-
-
-
Information describing the source that facilitated the plans current state
Hide source attributes Show source attributes object
-
The service where the change originated from
-
The type of plan change that was initiated
-
The time the change was initiated
-
The user that requested the change
-
The admin user that requested the change
-
The host addresses of the user that originated the change
-
-
Information about a warning from a plan.
-
Information about an error during a plan attempt.
Hide error attributes Show error attributes object
-
Timestamp marking on info log of step
-
Human readable error message
-
A map with details regarding the error. Both the keys and values are always strings, representing the name of the detail and its value, respectively.
-
The failure type
-
-
-
Information about the Elasticsearch cluster plan.
Hide pending attributes Show pending attributes object
-
A UUID for each plan attempt
-
A human readable name for each plan attempt, only populated when retrieving plan histories
-
Either the plan ended successfully, or is not yet completed (and no errors have occurred)
-
When this plan attempt (ie to apply the plan to the cluster) started (ISO format in UTC)
-
If this plan completed or failed (ie is not pending), when the attempt ended (ISO format in UTC)
-
If this plan is not current or pending, when the plan was no longer active (ISO format in UTC)
-
The plan for building this Elasticsearch cluster
Hide plan attributes Show plan attributes object
-
The topology of the Elasticsearch nodes, including the number, capacity, and type of nodes, and where they can be allocated.
Hide cluster_topology attributes Show cluster_topology attributes object
-
Unique identifier of this topology element
-
Controls the combinations of Elasticsearch node types. TIP: By default, the Elasticsearch node is master eligible, can hold data, and run ingest pipelines. WARNING: Do not set for tiebreaker topologies.
Hide node_type attributes Show node_type attributes object
-
Defines whether this node can be elected master (default: false)
-
Defines whether this node can hold data (default: false)
-
Defines whether this node can run an ingest pipeline (default: false)
-
Defines whether this node can run ml jobs, valid only for versions 5.4.0 or greater (default: false)
-
-
The list of node roles for this topology element (ES version >= 7.10). Allowable values are: master, ingest, ml, data_hot, data_content, data_warm, data_cold, data_frozen, remote_cluster_client, transform
Values are
master
,ingest
,ml
,data_hot
,data_content
,data_warm
,data_cold
,data_frozen
,remote_cluster_client
, ortransform
. -
The default number of zones in which data nodes will be placed
-
The Elasticsearch cluster settings. When specified at the top level, provides a field-by-field default. When specified at the topology level, provides the override settings.
Hide elasticsearch attributes Show elasticsearch attributes object
-
The version of the Elasticsearch cluster (must be one of the ECE supported versions). Currently cannot be different across the topology (and is generally specified in the globals). Defaults to the latest version if not specified.
-
A docker URI that allows overriding of the default docker image specified for this version
-
A subset of Elasticsearch settings. TIP: To define the complete set of Elasticsearch settings, use
ElasticsearchSystemSettings
withuser_settings_override*
anduser_settings*
.Hide system_settings attributes Show system_settings attributes object
-
Controls the languages supported by the Elasticsearch cluster, such as Painless, Mustache, and Expressions. Controls how the languages are used, such as file, index, and inline. TIP: For complex configurations, leave these blank and configure these settings in the user YAML or JSON.
Hide scripting attributes Show scripting attributes object
-
(5.x+ only) If enabled (the default) then the painless scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.painless.[file|stored|inline]')
-
(5.x+ only) If enabled (the default) then the mustache scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.mustache.[file|stored|inline]')
-
(5.x+ only) If enabled (the default) then the expressions scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.expression.[file|stored|inline]')
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide stored attributes Show stored attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide file attributes Show file attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide inline attributes Show inline attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
-
Limits remote Elasticsearch clusters that can be used as the source for '_reindex' API commands
-
If true (the default), then any write operation on an index that does not currently exist will create it. NOTES: (Corresponds to the parameter 'action.auto_create_index')
-
Defaults to false on versions <= 7.2.0, true otherwise. If false, then the API commands to close indices are disabled. This is important because Elasticsearch does not snapshot or migrate close indices on versions under 7.2.0, therefore standard Elastic Cloud configuration operations will cause irretrievable loss of indices' data. NOTES: (Corresponds to the parameter 'cluster.indices.close.enable')
-
If true (default is false) then the index deletion API will not support wildcards or '_all'. NOTES: (Corresponds to the parameter 'action.destructive_requires_name')
-
The trigger engine for Watcher, defaults to 'scheduler' - see the xpack documentation for more information. NOTES: (Corresponds to the parameter '(xpack.)watcher.trigger.schedule.engine', depending on version. Ignored from 6.x onwards.)
-
(2.x only - to get the same result in 5.x template mappings must be used) Sets the default number of shards per index, defaulting to 1 if not specified. (Corresponds to the parameter 'index.number_of_shards' in 2.x, not supported in 5.x)
-
The default interval at which monitoring information from the cluster if collected, if monitoring is enabled. NOTES: (Corresponds to the parameter 'marvel.agent.interval' in 2.x and 'xpack.monitoring.collection.interval' in 5.x)
-
The duration for which monitoring history is stored (format '(NUMBER)d' eg '3d' for 3 days). NOTES: ('Corresponds to the parameter xpack.monitoring.history.duration' in 5.x, defaults to '7d')
-
-
An arbitrary JSON object allowing cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters arey are on the allowlist and not on the denylist. NOTES: (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Elasticsearch settings)
-
An arbitrary YAML object allowing cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters arey are on the allowlist and not on the denylist. NOTES: (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Elasticsearch settings)
-
An arbitrary JSON object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), ie in addition to the documented 'system_settings'. NOTES: (This field together with 'system_settings' and 'user_settings*' defines the total set of Elasticsearch settings)
-
An arbitrary YAML object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), ie in addition to the documented 'system_settings'. NOTES: (This field together with 'system_settings' and 'user_settings*' defines the total set of Elasticsearch settings)
-
A list of plugin names from the Elastic-supported subset that are bundled with the version images. NOTES: (Users should consult the Elastic stack objects to see what plugins are available, this is currently only available from the UI)
-
A list of admin-uploaded plugin objects that are available for this user.
A list of admin-uploaded plugin objects.
Hide user_plugins attributes Show user_plugins attributes object
-
A list of admin-uploaded bundle objects (eg scripts, synonym files) that are available for this user.
A list of admin-uploaded bundle objects, such as scripts and synonym files.
Hide user_bundles attributes Show user_bundles attributes object
-
The name of the bundle
-
The URL of the bundle, which must be accessible from the ECE infrastructure. This URL could be cached by platform, make sure to change it when updating the bundle
-
The supported Elasticsearch version (must match the version in the plan)
-
-
Defines the index curation routing for the cluster
-
Defines the Elasticsearch node attributes for the instances in the topology
-
-
Controls the allocation of this topology element as well as allowed sizes and node_types. It needs to match the id of an existing instance configuration.
-
The version of the Instance Configuration Id. If it is unset, the meaning depends on read vs writes. For deployment reads, it is equivalent to version 0 (or the IC is unversioned); for deployment creates and deployment template use, it is equivalent to 'the latest version'; and for deployment updates, it is equivalent to 'retain the current version'.
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
An arbitrary JSON object overriding the default autoscaling policy. Don't set unless you really know what you are doing.
-
Controls for the topology element. Only used as part of the deployment template. Ignored if included as part of a deployment.
Hide topology_element_control attribute Show topology_element_control attribute object
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
-
Set to true to enable autoscaling for this topology element, even if the cluster-level 'autoscaling_enabled' field is false. Note that 'autoscaling_tier_override' cannot be set to false if cluster-level 'autoscaling_enabled' is true. Currently only supported for the 'ml' tier
-
-
The Elasticsearch cluster settings. When specified at the top level, provides a field-by-field default. When specified at the topology level, provides the override settings.
Hide elasticsearch attributes Show elasticsearch attributes object
-
The version of the Elasticsearch cluster (must be one of the ECE supported versions). Currently cannot be different across the topology (and is generally specified in the globals). Defaults to the latest version if not specified.
-
A docker URI that allows overriding of the default docker image specified for this version
-
A subset of Elasticsearch settings. TIP: To define the complete set of Elasticsearch settings, use
ElasticsearchSystemSettings
withuser_settings_override*
anduser_settings*
.Hide system_settings attributes Show system_settings attributes object
-
Controls the languages supported by the Elasticsearch cluster, such as Painless, Mustache, and Expressions. Controls how the languages are used, such as file, index, and inline. TIP: For complex configurations, leave these blank and configure these settings in the user YAML or JSON.
Hide scripting attributes Show scripting attributes object
-
(5.x+ only) If enabled (the default) then the painless scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.painless.[file|stored|inline]')
-
(5.x+ only) If enabled (the default) then the mustache scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.mustache.[file|stored|inline]')
-
(5.x+ only) If enabled (the default) then the expressions scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.expression.[file|stored|inline]')
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide stored attributes Show stored attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide file attributes Show file attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide inline attributes Show inline attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
-
Limits remote Elasticsearch clusters that can be used as the source for '_reindex' API commands
-
If true (the default), then any write operation on an index that does not currently exist will create it. NOTES: (Corresponds to the parameter 'action.auto_create_index')
-
Defaults to false on versions <= 7.2.0, true otherwise. If false, then the API commands to close indices are disabled. This is important because Elasticsearch does not snapshot or migrate close indices on versions under 7.2.0, therefore standard Elastic Cloud configuration operations will cause irretrievable loss of indices' data. NOTES: (Corresponds to the parameter 'cluster.indices.close.enable')
-
If true (default is false) then the index deletion API will not support wildcards or '_all'. NOTES: (Corresponds to the parameter 'action.destructive_requires_name')
-
The trigger engine for Watcher, defaults to 'scheduler' - see the xpack documentation for more information. NOTES: (Corresponds to the parameter '(xpack.)watcher.trigger.schedule.engine', depending on version. Ignored from 6.x onwards.)
-
(2.x only - to get the same result in 5.x template mappings must be used) Sets the default number of shards per index, defaulting to 1 if not specified. (Corresponds to the parameter 'index.number_of_shards' in 2.x, not supported in 5.x)
-
The default interval at which monitoring information from the cluster if collected, if monitoring is enabled. NOTES: (Corresponds to the parameter 'marvel.agent.interval' in 2.x and 'xpack.monitoring.collection.interval' in 5.x)
-
The duration for which monitoring history is stored (format '(NUMBER)d' eg '3d' for 3 days). NOTES: ('Corresponds to the parameter xpack.monitoring.history.duration' in 5.x, defaults to '7d')
-
-
An arbitrary JSON object allowing cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters arey are on the allowlist and not on the denylist. NOTES: (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Elasticsearch settings)
-
An arbitrary YAML object allowing cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters arey are on the allowlist and not on the denylist. NOTES: (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Elasticsearch settings)
-
An arbitrary JSON object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), ie in addition to the documented 'system_settings'. NOTES: (This field together with 'system_settings' and 'user_settings*' defines the total set of Elasticsearch settings)
-
An arbitrary YAML object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), ie in addition to the documented 'system_settings'. NOTES: (This field together with 'system_settings' and 'user_settings*' defines the total set of Elasticsearch settings)
-
A list of plugin names from the Elastic-supported subset that are bundled with the version images. NOTES: (Users should consult the Elastic stack objects to see what plugins are available, this is currently only available from the UI)
-
A list of admin-uploaded plugin objects that are available for this user.
A list of admin-uploaded plugin objects.
Hide user_plugins attributes Show user_plugins attributes object
-
A list of admin-uploaded bundle objects (eg scripts, synonym files) that are available for this user.
A list of admin-uploaded bundle objects, such as scripts and synonym files.
Hide user_bundles attributes Show user_bundles attributes object
-
The name of the bundle
-
The URL of the bundle, which must be accessible from the ECE infrastructure. This URL could be cached by platform, make sure to change it when updating the bundle
-
The supported Elasticsearch version (must match the version in the plan)
-
-
Defines the index curation routing for the cluster
-
Defines the Elasticsearch node attributes for the instances in the topology
-
-
Documents which deployment template was used in the creation of this plan
-
Defines the configuration parameters that control how the plan is applied. For example, the Elasticsearch cluster topology and Elasticsearch settings.
Hide transient attributes Show transient attributes object
-
The options for performing a plan change. Specify only one property each time. The default is
grow_and_shrink
.Hide strategy attributes Show strategy attributes object
-
Performs inline, rolling configuration changes that mutate existing containers. TIP: This is the fastest way to update a plan, but can fail for complex plan changes, such as topology changes. Also, this is less safe for configuration changes that leave a cluster in a non running state. NOTE: When you perform a major version upgrade, and 'group_by' is set to 'pass:macros[all]';, rolling is required.
Hide rolling attributes Show rolling attributes object
-
Specifies the grouping attribute to use when rolling several instances. Instances that share the same value for the provided attribute key are rolled together as a unit. Examples that make sense to use are '__all__' (roll all instances as a single unit), 'logical_zone_name' (roll instances by zone), '__name__' (roll one instance at a time, the default if not specified). Note that '__all__' is required when performing a major version upgrade
-
Whether we allow changing the capacity of instances (default false). This is currently implemented by stopping, re-creating then starting the affected instance on its associated allocator when performing the changes. NOTES: This requires a round-trip through the allocation infrastructure of the active constructor, as it has to reserve the target capacity without over-committing
-
Whether to skip attempting to do a synced flush on the filesystem of the container (default: false), which is less safe but may be required if the container is unhealthy
-
The time, in seconds, to wait for shards that show no progress of initializing before rolling the next group (default: 10 minutes)
-
-
A strategy that creates instances with the new plan, migrates data from the old instances, then shuts down the old instances.
GrowShrinkStrategyConfig
is safer than 'rolling' and ensures single node availability during a plan change, but can be a lot slower on larger clusters. -
A strategy that creates new Elasticsearch instances, Kibana instances, and APM Servers with the new plan, then migrates the node data to minimize the amount of spare capacity.
-
A strategy that lets constructor choose the most optimal way to execute the plan.
-
-
The configuration settings for the timeout and fallback parameters.
Hide plan_configuration attributes Show plan_configuration attributes object
-
The total timeout in seconds after which the plan is cancelled even if it is not complete. Defaults to 4x the max memory capacity per node (in MB). NOTES: A 3 zone cluster with 2 nodes of 2048 each would have a timeout of 4*2048=8192 seconds. Timeout does not include time required to run rollback actions.
-
This timeout determines how long to give a cluster after it responds to API calls before performing actual operations on it. It defaults to 5s
-
If true (default: false), does not take (or require) a successful snapshot to be taken before performing any potentially destructive changes to this cluster
-
If taking a snapshot (ie unless 'skip_snapshots': true) then will retry on failure at most this number of times (default: 5)
-
When you take a snapshot and 'skip_snapshots' is false, specifies the maximum age in seconds of the most recent snapshot before a new snapshot is created. Default is 300
-
If true (default false), does not clear the maintenance flag (which prevents its API from being accessed except by the constructor) on new instances added until after a snapshot has been restored, otherwise, the maintenance flag is cleared once the new instances successfully join the new cluster
-
Set to 'forced' to force a reboot as part of the upgrade plan. NOTES: (ie taking an existing plan and leaving it alone except for setting 'transient.plan_configuration.cluster_reboot': 'forced' will reboot the cluster)
Value is
forced
.
-
-
Restores a snapshot from a local or remote repository.
Hide restore_snapshot attributes Show restore_snapshot attributes object
-
If specified, contains the name of the snapshot repository - else will default to the Elastic Cloud system repo ('found-snapshots')
-
The name of the snapshot to restore. Use '__latest_success__' to get the most recent snapshot from the specified repository
-
Raw remote snapshot restore settings. Do not send this if you are sending source_cluster_id
-
The configuration for the restore command, such as which indices you want to restore.
Hide restore_payload attributes Show restore_payload attributes object
-
The list of indices to restore (supports +ve and -ve selection and wildcarding - see the default Elasticsearch index format documentation)
-
This JSON object (merged with the 'indices' field (if present) is passed untouched into the restore command - see the Elasticsearch '_snapshot' documentation for more details on supported formats
-
-
The restore strategy to use. Defaults to a full restore. Partial restore will attempt to restore unavailable indices only
Values are
partial
,full
, orrecovery
. -
If specified, contains the name of the source cluster id. Do not send this if you are sending repository_config
-
-
The list of resources that will be configured as remote clusters
Hide remote_clusters attribute Show remote_clusters attribute object
-
The remote resources
The Elasticsearch resource used as a Remote Cluster.
Hide resources attributes Show resources attributes object
-
The id of the deployment
-
The locally-unique user-specified id of an Elasticsearch Resource
-
The alias for this remote cluster. Aliases must only contain letters, digits, dashes and underscores
-
If true, skip this cluster during search if it is disconnected. Default: false
-
Information about a Remote Cluster.
Hide info attributes Show info attributes object
-
Whether or not the remote cluster is healthy
-
Whether or not there is at least one connection to the remote cluster.
-
Whether or not the remote cluster version is compatible with this cluster version.
-
Whether or not the remote cluster is trusted by this cluster.
-
Whether or not the remote cluster trusts this cluster back.
-
-
-
-
If specified, contains transient settings to be applied to an Elasticsearch cluster during changes,default values shown below applied. These can be overridden by specifying them in the map (or null to unset). Additional settings can also be set. Settings will be cleared after the plan has finished. If not specified, no settings will be applied. NOTE: These settings are only explicitly cleared for 5.x+ clusters, they must be hand-reset to their defaults in 2.x- (or a cluster reboot will clear them).
- indices.store.throttle.max_bytes_per_sec: 120Mb
- indices.recovery.max_bytes_per_sec: 120Mb
- cluster.routing.allocation.cluster_concurrent_rebalance: 5
- cluster.routing.allocation.node_initial_primaries_recoveries: 5
- cluster.routing.allocation.node_concurrent_incoming_recoveries: 5 For version 8.1 and later no defaults are provided through this mechanism, but instead hardware dependent settings are provided to each instance.
-
-
Enable autoscaling for this Elasticsearch cluster.
-
-
Information about a step in a plan.
Hide plan_attempt_log attributes Show plan_attempt_log attributes object
-
ID of current step
-
When the step started (ISO format in UTC)
-
When the step completed (ISO format in UTC)
-
The duration of the step in MS
-
The status of the step (success, warning, error - warning means something didn't go as expected but it was not serious enough to abort the plan)
Values are
success
,warning
,error
, orpending
. -
Current stage that the step is in
Values are
starting
,completed
, orin_progress
. -
Human readable summaries of the step, including messages for each stage of the step
The log message from a specified stage of an executed step in a plan.
Hide info_log attributes Show info_log attributes object
-
Timestamp marking on info log of step
-
Time in milliseconds since previous log message
-
Stage that info log message takes place in
Values are
starting
,completed
, orin_progress
. -
Human readable log message
-
A map with details for the log about what happened during the step execution. Keys and values for are always both strings, representing the name of the detail and its value, respectively.
-
The failure type, in case the step failed
-
-
-
Information describing the source that facilitated the plans current state
Hide source attributes Show source attributes object
-
The service where the change originated from
-
The type of plan change that was initiated
-
The time the change was initiated
-
The user that requested the change
-
The admin user that requested the change
-
The host addresses of the user that originated the change
-
-
Information about a warning from a plan.
-
Information about an error during a plan attempt.
Hide error attributes Show error attributes object
-
Timestamp marking on info log of step
-
Human readable error message
-
A map with details regarding the error. Both the keys and values are always strings, representing the name of the detail and its value, respectively.
-
The failure type
-
-
-
Information about the Elasticsearch cluster plan.
Hide history attributes Show history attributes object
-
A UUID for each plan attempt
-
A human readable name for each plan attempt, only populated when retrieving plan histories
-
Either the plan ended successfully, or is not yet completed (and no errors have occurred)
-
When this plan attempt (ie to apply the plan to the cluster) started (ISO format in UTC)
-
If this plan completed or failed (ie is not pending), when the attempt ended (ISO format in UTC)
-
If this plan is not current or pending, when the plan was no longer active (ISO format in UTC)
-
The plan for building this Elasticsearch cluster
Hide plan attributes Show plan attributes object
-
The topology of the Elasticsearch nodes, including the number, capacity, and type of nodes, and where they can be allocated.
Hide cluster_topology attributes Show cluster_topology attributes object
-
Unique identifier of this topology element
-
Controls the combinations of Elasticsearch node types. TIP: By default, the Elasticsearch node is master eligible, can hold data, and run ingest pipelines. WARNING: Do not set for tiebreaker topologies.
Hide node_type attributes Show node_type attributes object
-
Defines whether this node can be elected master (default: false)
-
Defines whether this node can hold data (default: false)
-
Defines whether this node can run an ingest pipeline (default: false)
-
Defines whether this node can run ml jobs, valid only for versions 5.4.0 or greater (default: false)
-
-
The list of node roles for this topology element (ES version >= 7.10). Allowable values are: master, ingest, ml, data_hot, data_content, data_warm, data_cold, data_frozen, remote_cluster_client, transform
Values are
master
,ingest
,ml
,data_hot
,data_content
,data_warm
,data_cold
,data_frozen
,remote_cluster_client
, ortransform
. -
The default number of zones in which data nodes will be placed
-
The Elasticsearch cluster settings. When specified at the top level, provides a field-by-field default. When specified at the topology level, provides the override settings.
Hide elasticsearch attributes Show elasticsearch attributes object
-
The version of the Elasticsearch cluster (must be one of the ECE supported versions). Currently cannot be different across the topology (and is generally specified in the globals). Defaults to the latest version if not specified.
-
A docker URI that allows overriding of the default docker image specified for this version
-
A subset of Elasticsearch settings. TIP: To define the complete set of Elasticsearch settings, use
ElasticsearchSystemSettings
withuser_settings_override*
anduser_settings*
.Hide system_settings attributes Show system_settings attributes object
-
Controls the languages supported by the Elasticsearch cluster, such as Painless, Mustache, and Expressions. Controls how the languages are used, such as file, index, and inline. TIP: For complex configurations, leave these blank and configure these settings in the user YAML or JSON.
Hide scripting attributes Show scripting attributes object
-
(5.x+ only) If enabled (the default) then the painless scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.painless.[file|stored|inline]')
-
(5.x+ only) If enabled (the default) then the mustache scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.mustache.[file|stored|inline]')
-
(5.x+ only) If enabled (the default) then the expressions scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.expression.[file|stored|inline]')
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide stored attributes Show stored attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide file attributes Show file attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide inline attributes Show inline attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
-
Limits remote Elasticsearch clusters that can be used as the source for '_reindex' API commands
-
If true (the default), then any write operation on an index that does not currently exist will create it. NOTES: (Corresponds to the parameter 'action.auto_create_index')
-
Defaults to false on versions <= 7.2.0, true otherwise. If false, then the API commands to close indices are disabled. This is important because Elasticsearch does not snapshot or migrate close indices on versions under 7.2.0, therefore standard Elastic Cloud configuration operations will cause irretrievable loss of indices' data. NOTES: (Corresponds to the parameter 'cluster.indices.close.enable')
-
If true (default is false) then the index deletion API will not support wildcards or '_all'. NOTES: (Corresponds to the parameter 'action.destructive_requires_name')
-
The trigger engine for Watcher, defaults to 'scheduler' - see the xpack documentation for more information. NOTES: (Corresponds to the parameter '(xpack.)watcher.trigger.schedule.engine', depending on version. Ignored from 6.x onwards.)
-
(2.x only - to get the same result in 5.x template mappings must be used) Sets the default number of shards per index, defaulting to 1 if not specified. (Corresponds to the parameter 'index.number_of_shards' in 2.x, not supported in 5.x)
-
The default interval at which monitoring information from the cluster if collected, if monitoring is enabled. NOTES: (Corresponds to the parameter 'marvel.agent.interval' in 2.x and 'xpack.monitoring.collection.interval' in 5.x)
-
The duration for which monitoring history is stored (format '(NUMBER)d' eg '3d' for 3 days). NOTES: ('Corresponds to the parameter xpack.monitoring.history.duration' in 5.x, defaults to '7d')
-
-
An arbitrary JSON object allowing cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters arey are on the allowlist and not on the denylist. NOTES: (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Elasticsearch settings)
-
An arbitrary YAML object allowing cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters arey are on the allowlist and not on the denylist. NOTES: (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Elasticsearch settings)
-
An arbitrary JSON object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), ie in addition to the documented 'system_settings'. NOTES: (This field together with 'system_settings' and 'user_settings*' defines the total set of Elasticsearch settings)
-
An arbitrary YAML object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), ie in addition to the documented 'system_settings'. NOTES: (This field together with 'system_settings' and 'user_settings*' defines the total set of Elasticsearch settings)
-
A list of plugin names from the Elastic-supported subset that are bundled with the version images. NOTES: (Users should consult the Elastic stack objects to see what plugins are available, this is currently only available from the UI)
-
A list of admin-uploaded plugin objects that are available for this user.
A list of admin-uploaded plugin objects.
Hide user_plugins attributes Show user_plugins attributes object
-
A list of admin-uploaded bundle objects (eg scripts, synonym files) that are available for this user.
A list of admin-uploaded bundle objects, such as scripts and synonym files.
Hide user_bundles attributes Show user_bundles attributes object
-
The name of the bundle
-
The URL of the bundle, which must be accessible from the ECE infrastructure. This URL could be cached by platform, make sure to change it when updating the bundle
-
The supported Elasticsearch version (must match the version in the plan)
-
-
Defines the index curation routing for the cluster
-
Defines the Elasticsearch node attributes for the instances in the topology
-
-
Controls the allocation of this topology element as well as allowed sizes and node_types. It needs to match the id of an existing instance configuration.
-
The version of the Instance Configuration Id. If it is unset, the meaning depends on read vs writes. For deployment reads, it is equivalent to version 0 (or the IC is unversioned); for deployment creates and deployment template use, it is equivalent to 'the latest version'; and for deployment updates, it is equivalent to 'retain the current version'.
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
An arbitrary JSON object overriding the default autoscaling policy. Don't set unless you really know what you are doing.
-
Controls for the topology element. Only used as part of the deployment template. Ignored if included as part of a deployment.
Hide topology_element_control attribute Show topology_element_control attribute object
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
-
Set to true to enable autoscaling for this topology element, even if the cluster-level 'autoscaling_enabled' field is false. Note that 'autoscaling_tier_override' cannot be set to false if cluster-level 'autoscaling_enabled' is true. Currently only supported for the 'ml' tier
-
-
The Elasticsearch cluster settings. When specified at the top level, provides a field-by-field default. When specified at the topology level, provides the override settings.
Hide elasticsearch attributes Show elasticsearch attributes object
-
The version of the Elasticsearch cluster (must be one of the ECE supported versions). Currently cannot be different across the topology (and is generally specified in the globals). Defaults to the latest version if not specified.
-
A docker URI that allows overriding of the default docker image specified for this version
-
A subset of Elasticsearch settings. TIP: To define the complete set of Elasticsearch settings, use
ElasticsearchSystemSettings
withuser_settings_override*
anduser_settings*
.Hide system_settings attributes Show system_settings attributes object
-
Controls the languages supported by the Elasticsearch cluster, such as Painless, Mustache, and Expressions. Controls how the languages are used, such as file, index, and inline. TIP: For complex configurations, leave these blank and configure these settings in the user YAML or JSON.
Hide scripting attributes Show scripting attributes object
-
(5.x+ only) If enabled (the default) then the painless scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.painless.[file|stored|inline]')
-
(5.x+ only) If enabled (the default) then the mustache scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.mustache.[file|stored|inline]')
-
(5.x+ only) If enabled (the default) then the expressions scripting engine is allowed as a sandboxed language. Sandboxed languages are the only ones allowed if 'sandbox_mode' is set to true. NOTES: (Corresponds to the parameters 'script.engine.expression.[file|stored|inline]')
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide stored attributes Show stored attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide file attributes Show file attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
Enables scripting for the specified type and controls other parameters. Store scripts in indexes (
stored
), upload in file bundles (file
), or use in API requests (inline
).Hide inline attributes Show inline attributes object
-
If enabled (default: true) then scripts are enabled, either for sandboxing languages (by default), or for all installed languages if 'sandbox_mode' is disabled (or for 6.x). NOTES: (Corresponds to the parameter 'script.file|stored/indexed|inline')
-
If enabled (default: true) and this script type is enabled, then only the sandbox languages are allowed. By default the sandbox languages are painless, expressions and mustache, but this can be restricted via the 'painless_enabled', 'mustache_enabled' 'expression_enabled' settings.NOTES: Not supported in 6.x. (Corresponds to the parameters 'script.engine.[painless|mustache|expressions].[file|stored|inline]')
-
-
-
Limits remote Elasticsearch clusters that can be used as the source for '_reindex' API commands
-
If true (the default), then any write operation on an index that does not currently exist will create it. NOTES: (Corresponds to the parameter 'action.auto_create_index')
-
Defaults to false on versions <= 7.2.0, true otherwise. If false, then the API commands to close indices are disabled. This is important because Elasticsearch does not snapshot or migrate close indices on versions under 7.2.0, therefore standard Elastic Cloud configuration operations will cause irretrievable loss of indices' data. NOTES: (Corresponds to the parameter 'cluster.indices.close.enable')
-
If true (default is false) then the index deletion API will not support wildcards or '_all'. NOTES: (Corresponds to the parameter 'action.destructive_requires_name')
-
The trigger engine for Watcher, defaults to 'scheduler' - see the xpack documentation for more information. NOTES: (Corresponds to the parameter '(xpack.)watcher.trigger.schedule.engine', depending on version. Ignored from 6.x onwards.)
-
(2.x only - to get the same result in 5.x template mappings must be used) Sets the default number of shards per index, defaulting to 1 if not specified. (Corresponds to the parameter 'index.number_of_shards' in 2.x, not supported in 5.x)
-
The default interval at which monitoring information from the cluster if collected, if monitoring is enabled. NOTES: (Corresponds to the parameter 'marvel.agent.interval' in 2.x and 'xpack.monitoring.collection.interval' in 5.x)
-
The duration for which monitoring history is stored (format '(NUMBER)d' eg '3d' for 3 days). NOTES: ('Corresponds to the parameter xpack.monitoring.history.duration' in 5.x, defaults to '7d')
-
-
An arbitrary JSON object allowing cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters arey are on the allowlist and not on the denylist. NOTES: (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Elasticsearch settings)
-
An arbitrary YAML object allowing cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters arey are on the allowlist and not on the denylist. NOTES: (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Elasticsearch settings)
-
An arbitrary JSON object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), ie in addition to the documented 'system_settings'. NOTES: (This field together with 'system_settings' and 'user_settings*' defines the total set of Elasticsearch settings)
-
An arbitrary YAML object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), ie in addition to the documented 'system_settings'. NOTES: (This field together with 'system_settings' and 'user_settings*' defines the total set of Elasticsearch settings)
-
A list of plugin names from the Elastic-supported subset that are bundled with the version images. NOTES: (Users should consult the Elastic stack objects to see what plugins are available, this is currently only available from the UI)
-
A list of admin-uploaded plugin objects that are available for this user.
A list of admin-uploaded plugin objects.
Hide user_plugins attributes Show user_plugins attributes object
-
A list of admin-uploaded bundle objects (eg scripts, synonym files) that are available for this user.
A list of admin-uploaded bundle objects, such as scripts and synonym files.
Hide user_bundles attributes Show user_bundles attributes object
-
The name of the bundle
-
The URL of the bundle, which must be accessible from the ECE infrastructure. This URL could be cached by platform, make sure to change it when updating the bundle
-
The supported Elasticsearch version (must match the version in the plan)
-
-
Defines the index curation routing for the cluster
-
Defines the Elasticsearch node attributes for the instances in the topology
-
-
Documents which deployment template was used in the creation of this plan
-
Defines the configuration parameters that control how the plan is applied. For example, the Elasticsearch cluster topology and Elasticsearch settings.
Hide transient attributes Show transient attributes object
-
The options for performing a plan change. Specify only one property each time. The default is
grow_and_shrink
.Hide strategy attributes Show strategy attributes object
-
Performs inline, rolling configuration changes that mutate existing containers. TIP: This is the fastest way to update a plan, but can fail for complex plan changes, such as topology changes. Also, this is less safe for configuration changes that leave a cluster in a non running state. NOTE: When you perform a major version upgrade, and 'group_by' is set to 'pass:macros[all]';, rolling is required.
Hide rolling attributes Show rolling attributes object
-
Specifies the grouping attribute to use when rolling several instances. Instances that share the same value for the provided attribute key are rolled together as a unit. Examples that make sense to use are '__all__' (roll all instances as a single unit), 'logical_zone_name' (roll instances by zone), '__name__' (roll one instance at a time, the default if not specified). Note that '__all__' is required when performing a major version upgrade
-
Whether we allow changing the capacity of instances (default false). This is currently implemented by stopping, re-creating then starting the affected instance on its associated allocator when performing the changes. NOTES: This requires a round-trip through the allocation infrastructure of the active constructor, as it has to reserve the target capacity without over-committing
-
Whether to skip attempting to do a synced flush on the filesystem of the container (default: false), which is less safe but may be required if the container is unhealthy
-
The time, in seconds, to wait for shards that show no progress of initializing before rolling the next group (default: 10 minutes)
-
-
A strategy that creates instances with the new plan, migrates data from the old instances, then shuts down the old instances.
GrowShrinkStrategyConfig
is safer than 'rolling' and ensures single node availability during a plan change, but can be a lot slower on larger clusters. -
A strategy that creates new Elasticsearch instances, Kibana instances, and APM Servers with the new plan, then migrates the node data to minimize the amount of spare capacity.
-
A strategy that lets constructor choose the most optimal way to execute the plan.
-
-
The configuration settings for the timeout and fallback parameters.
Hide plan_configuration attributes Show plan_configuration attributes object
-
The total timeout in seconds after which the plan is cancelled even if it is not complete. Defaults to 4x the max memory capacity per node (in MB). NOTES: A 3 zone cluster with 2 nodes of 2048 each would have a timeout of 4*2048=8192 seconds. Timeout does not include time required to run rollback actions.
-
This timeout determines how long to give a cluster after it responds to API calls before performing actual operations on it. It defaults to 5s
-
If true (default: false), does not take (or require) a successful snapshot to be taken before performing any potentially destructive changes to this cluster
-
If taking a snapshot (ie unless 'skip_snapshots': true) then will retry on failure at most this number of times (default: 5)
-
When you take a snapshot and 'skip_snapshots' is false, specifies the maximum age in seconds of the most recent snapshot before a new snapshot is created. Default is 300
-
If true (default false), does not clear the maintenance flag (which prevents its API from being accessed except by the constructor) on new instances added until after a snapshot has been restored, otherwise, the maintenance flag is cleared once the new instances successfully join the new cluster
-
Set to 'forced' to force a reboot as part of the upgrade plan. NOTES: (ie taking an existing plan and leaving it alone except for setting 'transient.plan_configuration.cluster_reboot': 'forced' will reboot the cluster)
Value is
forced
.
-
-
Restores a snapshot from a local or remote repository.
Hide restore_snapshot attributes Show restore_snapshot attributes object
-
If specified, contains the name of the snapshot repository - else will default to the Elastic Cloud system repo ('found-snapshots')
-
The name of the snapshot to restore. Use '__latest_success__' to get the most recent snapshot from the specified repository
-
Raw remote snapshot restore settings. Do not send this if you are sending source_cluster_id
-
The configuration for the restore command, such as which indices you want to restore.
Hide restore_payload attributes Show restore_payload attributes object
-
The list of indices to restore (supports +ve and -ve selection and wildcarding - see the default Elasticsearch index format documentation)
-
This JSON object (merged with the 'indices' field (if present) is passed untouched into the restore command - see the Elasticsearch '_snapshot' documentation for more details on supported formats
-
-
The restore strategy to use. Defaults to a full restore. Partial restore will attempt to restore unavailable indices only
Values are
partial
,full
, orrecovery
. -
If specified, contains the name of the source cluster id. Do not send this if you are sending repository_config
-
-
The list of resources that will be configured as remote clusters
Hide remote_clusters attribute Show remote_clusters attribute object
-
The remote resources
The Elasticsearch resource used as a Remote Cluster.
Hide resources attributes Show resources attributes object
-
The id of the deployment
-
The locally-unique user-specified id of an Elasticsearch Resource
-
The alias for this remote cluster. Aliases must only contain letters, digits, dashes and underscores
-
If true, skip this cluster during search if it is disconnected. Default: false
-
Information about a Remote Cluster.
Hide info attributes Show info attributes object
-
Whether or not the remote cluster is healthy
-
Whether or not there is at least one connection to the remote cluster.
-
Whether or not the remote cluster version is compatible with this cluster version.
-
Whether or not the remote cluster is trusted by this cluster.
-
Whether or not the remote cluster trusts this cluster back.
-
-
-
-
If specified, contains transient settings to be applied to an Elasticsearch cluster during changes,default values shown below applied. These can be overridden by specifying them in the map (or null to unset). Additional settings can also be set. Settings will be cleared after the plan has finished. If not specified, no settings will be applied. NOTE: These settings are only explicitly cleared for 5.x+ clusters, they must be hand-reset to their defaults in 2.x- (or a cluster reboot will clear them).
- indices.store.throttle.max_bytes_per_sec: 120Mb
- indices.recovery.max_bytes_per_sec: 120Mb
- cluster.routing.allocation.cluster_concurrent_rebalance: 5
- cluster.routing.allocation.node_initial_primaries_recoveries: 5
- cluster.routing.allocation.node_concurrent_incoming_recoveries: 5 For version 8.1 and later no defaults are provided through this mechanism, but instead hardware dependent settings are provided to each instance.
-
-
Enable autoscaling for this Elasticsearch cluster.
-
-
Information about a step in a plan.
Hide plan_attempt_log attributes Show plan_attempt_log attributes object
-
ID of current step
-
When the step started (ISO format in UTC)
-
When the step completed (ISO format in UTC)
-
The duration of the step in MS
-
The status of the step (success, warning, error - warning means something didn't go as expected but it was not serious enough to abort the plan)
Values are
success
,warning
,error
, orpending
. -
Current stage that the step is in
Values are
starting
,completed
, orin_progress
. -
Human readable summaries of the step, including messages for each stage of the step
The log message from a specified stage of an executed step in a plan.
Hide info_log attributes Show info_log attributes object
-
Timestamp marking on info log of step
-
Time in milliseconds since previous log message
-
Stage that info log message takes place in
Values are
starting
,completed
, orin_progress
. -
Human readable log message
-
A map with details for the log about what happened during the step execution. Keys and values for are always both strings, representing the name of the detail and its value, respectively.
-
The failure type, in case the step failed
-
-
-
Information describing the source that facilitated the plans current state
Hide source attributes Show source attributes object
-
The service where the change originated from
-
The type of plan change that was initiated
-
The time the change was initiated
-
The user that requested the change
-
The admin user that requested the change
-
The host addresses of the user that originated the change
-
-
Information about a warning from a plan.
-
Information about an error during a plan attempt.
Hide error attributes Show error attributes object
-
Timestamp marking on info log of step
-
Human readable error message
-
A map with details regarding the error. Both the keys and values are always strings, representing the name of the detail and its value, respectively.
-
The failure type
-
-
-
-
Information about the Elasticsearch cluster.
Hide elasticsearch attributes Show elasticsearch attributes object
-
Whether the Elasticsearch cluster is healthy (check the sub-objects for more details if not)
-
WARNING This endpoint is deprecated and scheduled to be removed in the next major version. Use
shards_status
instead.Elasticsearch shard info
Hide shard_info attributes Show shard_info attributes object
-
Whether the shard situation is healthy (any unavailable shards is unhealthy)
-
Information about the shards for each Elasticsearch instance container that hosts an Elasticsearch node. TIP: When the shard is unavailable, the cluster is unable to serve all of the data.
-
Information about the shards for each Elasticsearch instance container that hosts an Elasticsearch node. TIP: When the shard is unavailable, the cluster is unable to serve all of the data.
-
Information about the unavailable replicas. NOTE: Unlike shards, unavailable replicas indicate a loss of redundancy rather than a loss of availability.
-
-
Shards status represented as green, yellow, or red, as returned by the Elasticsearch cluster health API
-
Information about the master nodes in the Elasticsearch cluster.
Hide master_info attributes Show master_info attributes object
-
Whether the master situation in the cluster is healthy (ie is the number of masters != 1), or do any instances have no master
-
Information about the Elasticsearch instances. For split-brain cases, this also includes sub-clusters.
Hide masters attributes Show masters attributes object
-
The Elasticsearch node id of a master node
-
The corresponding instance name of the container hosting the Elasticsearch master node, if available
-
The names of the instance/container hosting the node belong to the cluster with the given master
-
-
A list of any instances with no master
-
-
WARNING This endpoint is deprecated and scheduled to be removed in the next major version. Use
cluster_blocking_issues
instead.cluster-wide and/or index blocks
Hide blocking_issues attributes Show blocking_issues attributes object
-
Whether the cluster has issues (false) or not (true)
-
A list of issues that affect availability of entire cluster
WARNING This endpoint is deprecated and scheduled to be removed in the next major version. Use
blocks
incluster_blocking_issues
insteadInformation about an issue and the Elasticsearch instance it affects.
-
A list of issues that affect availability of the cluster's indices
WARNING This endpoint is deprecated and scheduled to be removed in the next major version. Use
blocks
incluster_blocking_issues
insteadInformation about an issue and the Elasticsearch instance it affects.
-
-
Issues that prevent the Elasticsearch cluster or index from correctly operating.
Hide cluster_blocking_issues attributes Show cluster_blocking_issues attributes object
-
Whether the cluster has issues (false) or not (true)
-
A list of blocks that affect the availability of the cluster
Information about index or cluster blocks
-
-
-
Information about the public and internal state, and the configuration settings of an Elasticsearch cluster.
Hide metadata attributes Show metadata attributes object
-
The resource version number of the cluster metadata
-
The most recent time the cluster metadata was changed (ISO format in UTC)
-
The DNS name of the cluster endpoint, if available
-
The full URL to access this deployment resource
-
The DNS name of the cluster endpoint derived from the deployment alias, if available
-
The full aliased URL to access this deployment resource
-
The cloud ID, an encoded string that provides other Elastic services with the necessary information to connect to this Elasticsearch and Kibana (only present if both exist)
-
An unstructured JSON representation of the public and internal state (can be filtered out via URL parameter). The contents and structure of the
raw
field can change at any time. -
The ports that allow communication with the cluster using various protocols.
Hide ports attributes Show ports attributes object
-
A list of the URLs to access services that the resource provides at this time. Note that if the service is not running or has not started yet, the URL to access it won't be available
A URL to access the service of a resource
-
-
The topology for Elasticsearch clusters, multiple Kibana instances, or multiple APM Servers. The
ClusterTopologyInfo
also includes the instances and containers, and where they are located.Hide topology attributes Show topology attributes object
-
Whether the cluster topology is healthy (ie all instances are started and the services they run - ie elasticsearch - are available
-
Information about each Kibana instance and APM Server in the Elasticsearch cluster.
Hide instances attributes Show instances attributes object
-
The name of the instance in Elastic Cloud
-
Information about a configuration that creates a Kibana instance or APM Server.
Hide instance_configuration attributes Show instance_configuration attributes object
-
The id of the configuration used to create the instance
-
The name of the configuration used to create the instance
-
If the IC is configuration controlled, this field is the version either being read back (reads return the latest IC unless specified by the 'config_version' URL param), or the version to update. Cannot be used in creates. For unversioned IC reads it is left empty.
-
The resource type of the instance configuration
Values are
memory
orstorage
.
-
-
The version of the service that the instance is running (eg Elasticsearch or Kibana), if available
-
Whether the instance is healthy (ie started and running)
-
Whether the container has started (does not tell you anything about the service -ie Elasticsearch- running inside the container)
-
Whether the service launched inside the container -ie Elasticsearch- is actually running
-
Whether the service is is maintenance mode (meaning that the proxy is not routing external traffic to it)
-
The zone in which this instance is being allocated
-
The id of the allocator on which this instance is running (if the container is started or starting)
-
Information about the specific instances memory capacity and its usage
Hide memory attributes Show memory attributes object
-
The memory capacity in MB of the instance
-
The planned memory capacity in MB of the instance (only shown when an override is present)
-
The % memory pressure of Elasticsearch JVM heap space if available (60-75% consider increasing capacity, >75% can incur significant performance and stability issues)
-
The % memory pressure of the instance Docker container (if available)
-
-
Information about the use and storage capacity of a Kibana instance or APM Server.
Hide disk attributes Show disk attributes object
-
If known, the amount of total disk space available to the container in MB
-
The amount of disk space being used by the service in MB
-
The storage multiplier originally defined to calculate disk space.
-
-
List of roles assigned to the service running in the instance. Currently only populated for Elasticsearch, with possible values: master,data,ingest,ml
-
A list of the node roles assigned to the service running in the instance. Currently populated only for Elasticsearch.
Values are
master
,ingest
,ml
,data_hot
,data_content
,data_warm
,data_cold
,data_frozen
,remote_cluster_client
,transform
, orvoting_only
. -
Instance overrides
-
-
-
List of cluster system alerts
Information about a system alert on an Elasticsearch cluster.
Hide system_alerts attributes Show system_alerts attributes object
-
Timestamp marking the system alert
-
Instance that caused the system alert
-
Type of system alert
Values are
automatic_restart
,heap_dump
, orunknown_event
. -
The URL related to the event. Only applicable for alert_type: heap_dump
-
The exit_code related to the event. Only applicable for alert_type: slain
-
-
Information about the Kibana instances associated with the Elasticsearch cluster.
Hide associated_kibana_clusters attributes Show associated_kibana_clusters attributes object
-
The Kibana cluster Id
-
Whether the associated Kibana cluster is currently available
-
A map of application-specific operations (which map to 'operationId's in the Swagger API) to metadata about that operation
-
-
Information about the APM Servers associated with the Elasticsearch cluster.
Hide associated_apm_clusters attributes Show associated_apm_clusters attributes object
-
The APM cluster Id
-
Whether the associated APM cluster is currently available
-
A map of application-specific operations (which map to 'operationId's in the Swagger API) to metadata about that operation
-
-
Information about the APM Servers associated with the Elasticsearch cluster.
Hide associated_appsearch_clusters attributes Show associated_appsearch_clusters attributes object
-
The App Search Id
-
Whether the associated App Search is currently available
-
A map of application-specific operations (which map to 'operationId's in the Swagger API) to metadata about that operation
-
-
Information about the APM Servers associated with the Elasticsearch cluster.
Hide associated_enterprise_search_clusters attributes Show associated_enterprise_search_clusters attributes object
-
The Enterprise Search Id
-
Whether the associated Enterprise Search is currently available
-
A map of application-specific operations (which map to 'operationId's in the Swagger API) to metadata about that operation
-
-
For 2.x Elasticsearch clusters, specifies the information about the users and roles. For 5.x Elasticsearch clusters, use the Kibana management UI.
Hide security attributes Show security attributes object
-
The resource version number of the security settings
-
The most recent time the security settings were changed (ISO format in UTC)
-
The information about an Elasticsearch cluster user.
-
An arbitrarily nested JSON object mapping roles to sets of resources and permissions - see the Elasticsearch security documentation for more details on roles
-
The authorization information for an Elasticsearch cluster user.
-
-
Information about the monitoring status for the Elasticsearch cluster.
Hide elasticsearch_monitoring_info attributes Show elasticsearch_monitoring_info attributes object
-
Whether the Monitoring configuration has been successfully applied
-
The time the monitoring configuration was last changed
-
The status message from the last update (successful or not)
-
The list of clusters Ids from which this cluster is currently receiving monitoring data
-
The list of clusters Ids to which this cluster is currently sending monitoring data
-
-
Information about the snapshot status for the Elasticsearch cluster. For example, the health status.
Hide snapshots attributes Show snapshots attributes object
-
Health status of snapshots for this cluster
-
Number of snapshots stored for this cluster
-
Latest snapshot status
-
Status of the latest snapshot attempt, if any exist.
-
Scheduled time of next snapshot attempt
-
The end time of the most recently attempted snapshot
-
The end time of the most recently successful snapshot
-
Indicates whether the cluster has a relatively recent successful snapshot.
-
-
External resources related to the cluster
-
A map of application-specific operations (which map to 'operationId's in the Swagger API) to metadata about that operation
-
The settings for building this Elasticsearch cluster
Hide settings attributes Show settings attributes object
-
The snapshot settings for this deployment. When provided, snapshot settings are changed as specified. A
null
value reverts the field to the default value. Otherwise, all snapshot settings remain as they were set previously.Hide snapshot attributes Show snapshot attributes object
-
Interval between snapshots, with the format 'length unit' (space is optional), where unit can be one of: d (day), h (hour), min (minute). Default is 30 minutes
-
Cluster snapshot retention information
-
When set to true, the deployment will have SLM enabled. Default value is true.
-
Cron expression indicating when should snapshots be taken. This can be enabled only if SLM is enabled for the deployment and 'interval' is not present
-
-
The monitoring settings for this deployment. When provided, monitoring settings are changed as specified. A
null
value reverts the field to the default value. Otherwise, all monitoring settings remain as they were set previously. -
The top-level configuration settings for the Elasticsearch cluster.
-
The curation settings for this deployment. When provided, curation settings are changed as specified. A
null
value reverts the field to the default value. Otherwise, all curation settings remain as they were set previously.Hide curation attribute Show curation attribute object
-
Specifications for curation
Specifies the conditions to trigger an Elasticsearch cluster curation.
-
-
Threshold starting from which the number of instances in the cluster results in the introduction of dedicated masters. If the cluster is downscaled to a number of nodes below this one, dedicated masters will be removed. Limit is inclusive. When provided the threshold setting is updated. A
null
value removes the field. Otherwise, the setting remains as it was set previously. -
The rulesets to apply to all resources in this cluster. When specified, the set of rulesets is updated and the same rulesets will be applied to Kibana and APM clusters as well. If not specified, the rulesets remain as they were set previously.
-
Configuration of trust with other clusters. When provided, trust settings are changed as specified. A
null
value reverts the field to the default value. Otherwise, all trust settings remain as they were set previously.Hide trust attributes Show trust attributes object
-
The list of trust relationships with different accounts
The trust relationship with the clusters of one account.
Hide accounts attributes Show accounts attributes object
-
the ID of the Account
-
A human readable name of the trust relationship
-
If true, all clusters in this account will by default be trusted and the
trust_allowlist
is ignored. -
The list of clusters to trust. Only used when
trust_all
is false.
-
-
The list of trust relationships with external entities
The trust relationship with external entities (remote environments, remote accounts...).
Hide external attributes Show external attributes object
-
The ID of the external trust relationship
-
The name of the external trust relationship. Retrieved from the TrustRelationship and ignored on write.
-
If true, all clusters in this external entity will be trusted and the
trust_allowlist
is ignored. -
The list of clusters to trust. Only used when
trust_all
is false.
-
-
The list of trust relationships where the certificate is bundled with the trust setting. Allows configuring trust for clusters running outside of an Elastic Cloud managed environment or in an Elastic Cloud environment without an environment level trust established.
The trust relationship with entities trusted directly having their certificate bundled together with the trust settings.
Hide direct attributes Show direct attributes object
-
Auto generated identifier for this trust, allows distinguishing between update vs remove and add.
-
a human readable name of the trust relationship
-
The type can either be ESS, ECE, generic or proxy. If none is specified, then generic is assumed. If proxy is specified, trust_all should be false and trust_allowlist, scope_id and additional_node_names should be omitted.
Values are
ECE
,ESS
,generic
, orproxy
. -
If true, scope_id is required and the
trust_allowlist
is ignored and all clusters matching the scope id will be trusted. -
The list of clusters with matching scope to trust. Only used when
trust_all
is false. Providing one or more clusters makes scope_id mandatory. -
A lowercase alphanumerical string of max 32 characters. Usually an organization id or an environment id, but could really be any suitable suffix for clusters using the CA certificate of this trust. Required unless trust_all is false and trust_allowlist is empty.
-
A list of node names trusted in addition to those deducible from trust_allowlist and scope id. Allows trusting nodes that don't have a scoped name at the cost of maintaining the list. Mandatory if scope id is not defined. Wildcards are not allowed.
-
The public ca certificate(s) to trust. Only one is required, but it is possible to specify multiple certificates in order to facilitate key rotation.
An x509 certificate used by a DirectTrustRelationship
Hide certificates attributes Show certificates attributes object
-
The public ca certificate as string in PEM format.
-
Metadata about the certificate, including fingerprint and expiry date. Generated by the Cloud service and ignored on write.
Hide metadata attributes Show metadata attributes object
-
The fingerprint of the certificate
-
The expiry date of the certificate in UTC
-
The valid from date of the certificate in UTC
-
Other deployments also trusting this certificate
-
-
-
-
-
The contents of the Elasticsearch keystore. It's a write only field.
Hide keystore_contents attribute Show keystore_contents attribute object
-
List of secrets
Hide secrets attribute Show secrets attribute object
-
The value that you configure for the Elasticsearch keystore secret.
Hide * attributes Show * attributes object
-
Value of this setting. This can either be a string or a JSON object that is stored as a JSON string in the keystore. NOTE: When the keystore secret is unspecified, it is removed.
-
Stores the keystore secret as a file. The default is false, which stores the keystore secret as string when value is a plain string, or true when value is an object.
-
-
-
-
-
The region that this cluster belongs to. Only populated in SaaS or federated ECE.
-
-
-
The Deployment specified by {deployment_id} cannot be found. (code:
deployments.deployment_not_found
)Hide headers attribute Show headers attribute
Hide response attribute Show response attribute object
-
A list of errors that occurred in the failing request
Hide errors attributes Show errors attributes object
-
-
We have failed you. (code:
deployments.deployment_resource_no_longer_exists
)Hide headers attribute Show headers attribute
Hide response attribute Show response attribute object
-
A list of errors that occurred in the failing request
Hide errors attributes Show errors attributes object
-
curl \
--request GET 'http://api.elastic-cloud.com/api/v1/deployments/{deployment_id}/elasticsearch/{ref_id}'