Build request to migrate deployment to a different template
Returns a deployment update request that would migrate this deployment to a different template.
Responses
-
The request was valid and the deployment can be migrated to the template with the provided ID.
Hide response attributes Show response attributes object
-
A new name for the deployment, otherwise stays the same.
-
Whether or not to prune orphan resources that are no longer mentioned in this request. Note that resourcesare tracked by ref_id, and if a resource's ref_id is changed, any previous running resources created with that previousref_id are considered to be orphaned as well.
-
New information about the Resources that will have this Deployment, otherwise they stay the same
Hide resources attributes Show resources attributes object
-
A list of payloads for Elasticsearch cluster updates
An alias for an Elasticsearch Cluster paired with a request for creating one
Hide elasticsearch attributes Show elasticsearch attributes object
-
A locally-unique user-specified id for this Elasticsearch cluster
-
The human readable name for the cluster (defaults to the generated cluster id if not specified)
-
The region where this resource exists
-
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.
-
-
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.
-
-
-
-
-
-
A list of payloads for Kibana updates
A Kibana creation request paired with the alias of the Elasticsearch cluster it should be paired with
Hide kibana attributes Show kibana attributes object
-
A locally-unique user-specified id for Kibana
-
Alias to the Elasticsearch Cluster to attach Kibana to
-
The human readable name for the Kibana cluster (default: takes the name of its Elasticsearch cluster)
-
The region where this resource exists
-
The plan for the Kibana instance.
Hide plan attributes Show plan attributes object
-
The topology of the Kibana nodes, including the number, capacity, and type of nodes, and where they can be allocated.
Hide cluster_topology attributes Show cluster_topology attributes object
-
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.
-
number of zones in which nodes will be placed
-
The Kibana instance settings. When specified at the top level, provides a field-by-field default. When specified at the topology level, provides the override settings.
Hide kibana attributes Show kibana attributes object
-
The version of the Kibana cluster (must be one of the ECE supported versions, and won't work unless it matches the Elasticsearch version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
A subset of Kibana settings. TIP: To define the complete set of Elasticsearch settings, use
KibanaSystemSettings
withuser_settings_override_
anduser_settings_
.Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within Elasticsearch - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within Elasticsearch - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Kibana settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of Kibana 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Kibana 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Kibana settings)
-
-
-
The Kibana instance settings. When specified at the top level, provides a field-by-field default. When specified at the topology level, provides the override settings.
Hide kibana attributes Show kibana attributes object
-
The version of the Kibana cluster (must be one of the ECE supported versions, and won't work unless it matches the Elasticsearch version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
A subset of Kibana settings. TIP: To define the complete set of Elasticsearch settings, use
KibanaSystemSettings
withuser_settings_override_
anduser_settings_
.Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within Elasticsearch - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within Elasticsearch - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Kibana settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of Kibana 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Kibana 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Kibana settings)
-
-
Defines the configuration parameters that control how the plan is applied. For example, the Elasticsearch cluster topology and Kibana instance 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)
-
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 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
Value is
forced
.
-
-
-
-
The settings for building this Kibana cluster
-
-
A list of payloads for APM updates
An APM creation request paired with the alias of the Elasticsearch cluster it should be paired with
Hide apm attributes Show apm attributes object
-
A locally-unique user-specified id for APM
-
Alias to the Elasticsearch Cluster to attach APM to
-
The human readable name for the APM cluster (default: takes the name of its Elasticsearch cluster)
-
The region where this resource exists
-
The plan for the APM Server.
Hide plan attributes Show plan attributes object
-
Defines the topology of the APM Server nodes. For example, the number or capacity of the nodes, and where you can allocate the nodes.
Hide cluster_topology attributes Show cluster_topology attributes object
-
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.
-
number of zones in which nodes will be placed
-
The configuration options for the APM Server.
Hide apm attributes Show apm attributes object
-
The version of the Apm cluster (must be one of the ECE supported versions, and won't work unless it matches the APM version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
A structure that defines a curated subset of the APM Server settings. TIP: To define the complete set of APM Server setting, use
ApmSystemSettings
withuser_settings_override_
anduser_settings_
.Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret token within APM - defaults to the previously existing secretToken
-
Optionally enable debug mode for APM servers - defaults false
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
-
-
The configuration options for the APM Server.
Hide apm attributes Show apm attributes object
-
The version of the Apm cluster (must be one of the ECE supported versions, and won't work unless it matches the APM version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
A structure that defines a curated subset of the APM Server settings. TIP: To define the complete set of APM Server setting, use
ApmSystemSettings
withuser_settings_override_
anduser_settings_
.Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret token within APM - defaults to the previously existing secretToken
-
Optionally enable debug mode for APM servers - defaults false
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
-
Defines the configuration parameters that control how the plan is applied. For example, the Elasticsearch cluster topology and APM Server 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 plan control configuration options for the APM Server.
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)
-
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 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
Value is
forced
.
-
-
-
-
The settings for building this APM cluster
-
-
A list of payloads for AppSearch updates. AppSearch has been replaced by Enterprise Search in the Elastic Stack 7.7 and higher
An AppSearch creation request paired with the alias of the Elasticsearch cluster it should be paired with
Hide appsearch attributes Show appsearch attributes object
-
A locally-unique user-specified id for AppSearch
-
Alias to the Elasticsearch Cluster to attach AppSearch to
-
The human readable name for the AppSearch cluster (default: takes the name of its Elasticsearch cluster)
-
The region where this resource exists
-
The plan for the App Search cluster.
Hide plan attributes Show plan attributes object
-
Defines the topology of the AppSearch nodes (eg number/capacity of nodes, and where they can be allocated)
Hide cluster_topology attributes Show cluster_topology attributes object
-
Defines the AppSearch node type
-
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.
-
number of zones in which nodes will be placed
-
Hide appsearch attributes Show appsearch attributes object
-
The version of the AppSearch cluster (must be one of the ECE supported versions, and won't work unless it matches the Elasticsearch version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
This structure defines a curated subset of the AppSearch settings. (This field together with 'user_settings_override*' and 'user_settings*' defines the total set of AppSearch settings)
Hide system_settings attributes Show system_settings attributes object
-
Optionally override the URL to which to send data (for advanced users only, if unspecified the system selects an internal URL)
-
Optionally override the account within App Search - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within App Search - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret session key within App Search - defaults to the previously existing secretSession. Note that this field is never returned from the API, it is write only.
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of AppSearch settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of AppSearch 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of AppSearch 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of AppSearch settings)
-
-
-
Hide appsearch attributes Show appsearch attributes object
-
The version of the AppSearch cluster (must be one of the ECE supported versions, and won't work unless it matches the Elasticsearch version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
This structure defines a curated subset of the AppSearch settings. (This field together with 'user_settings_override*' and 'user_settings*' defines the total set of AppSearch settings)
Hide system_settings attributes Show system_settings attributes object
-
Optionally override the URL to which to send data (for advanced users only, if unspecified the system selects an internal URL)
-
Optionally override the account within App Search - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within App Search - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret session key within App Search - defaults to the previously existing secretSession. Note that this field is never returned from the API, it is write only.
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of AppSearch settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of AppSearch 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of AppSearch 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of AppSearch settings)
-
-
Defines configuration parameters that control how the plan (ie consisting of the cluster topology and AppSearch settings) is applied
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.
-
-
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)
-
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
-
The request that specifies the Elasticsearch or stateless (eg Kibana) instances to move to allocators as part of the upgrade plan. When used in conjunction with '__all__' (roll all instances as a single unit) strategy, these instances are not restarted, which can sometimes enable recovery plans when these instances are boot-looping.
Hide move_instances attributes Show move_instances attributes object
-
The instance id that is going to be moved
-
An optional list of allocator ids to which the instance should be moved. If not specified then any available allocator can be used (including the current one if it is healthy)
-
Tells the infrastructure that the instance should be considered as permanently down when deciding how to migrate data to new nodes. If left blank then the system will automatically decide (currently: will treat the instances as up)
-
-
As part of the upgrade plan, identifies the move requests for the Kibana instances or APM Servers on the allocators.
Hide move_allocators attributes Show move_allocators attributes object
-
The allocator id off which all instances in the cluster should be moved
-
An optional list of allocator ids to which the instance(s) should be moved. If not specified then any available allocator can be used (including the current one if it is healthy)
-
Tells the infrastructure that all instances on the allocator should be considered as permanently down when deciding how to migrate data to new nodes. If left blank then the system will auto-decide (currently: will treat the allocator as up)
-
-
If true (default: false) does not allow re-using any existing instances currently in the cluster, ie even unchanged instances will be re-created
-
List of allocators on which instances are placed if possible (if not possible/not specified then any available allocator with space is used)
-
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
Value is
forced
.
-
-
-
-
The settings for building this AppSearch cluster
-
-
A list of payloads for Enterprise Search updates
An Enterprise Search creation request paired with the alias of the Elasticsearch cluster it should be paired with
Hide enterprise_search attributes Show enterprise_search attributes object
-
A locally-unique user-specified id for Enterprise Search
-
Alias to the Elasticsearch Cluster to attach Enterprise Search to
-
The human readable name for the Enterprise Search cluster (default: takes the name of its Elasticsearch cluster)
-
The region where this resource exists
-
The plan for the Enterprise Search cluster.
Hide plan attributes Show plan attributes object
-
Defines the topology of the Enterprise Search nodes (e.g. number/capacity of nodes, and where they can be allocated)
Hide cluster_topology attributes Show cluster_topology attributes object
-
Defines the EnterpriseSearch node type
Hide node_type attributes Show node_type attributes object
-
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.
-
number of zones in which nodes will be placed
-
Hide enterprise_search attributes Show enterprise_search attributes object
-
The version of the Enterprise Search cluster (must be one of the ECE supported versions, and won't work unless it matches the Elasticsearch version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
This structure defines a curated subset of the Enterprise Search settings. (This field together with 'user_settings_override*' and 'user_settings*' defines the total set of Enterprise Search settings)
Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within Enterprise Search - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within Enterprise Search - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret session key within Enterprise Search - defaults to the previously existing secretSession. Note that this field is never returned from the API, it is write only.
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Enterprise Search settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Enterprise Search settings)
-
An arbitrary JSON object allowing ECE admins to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), i.e. in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Enterprise Search settings)
-
An arbitrary YAML object allowing ECE admins to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), i.e. in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Enterprise Search settings)
-
-
-
Hide enterprise_search attributes Show enterprise_search attributes object
-
The version of the Enterprise Search cluster (must be one of the ECE supported versions, and won't work unless it matches the Elasticsearch version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
This structure defines a curated subset of the Enterprise Search settings. (This field together with 'user_settings_override*' and 'user_settings*' defines the total set of Enterprise Search settings)
Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within Enterprise Search - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within Enterprise Search - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret session key within Enterprise Search - defaults to the previously existing secretSession. Note that this field is never returned from the API, it is write only.
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Enterprise Search settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Enterprise Search settings)
-
An arbitrary JSON object allowing ECE admins to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), i.e. in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Enterprise Search settings)
-
An arbitrary YAML object allowing ECE admins to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), i.e. in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Enterprise Search settings)
-
-
Defines configuration parameters that control how the plan (i.e. consisting of the cluster topology and Enterprise Search settings) is applied
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.
-
-
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)
-
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
-
The request that specifies the Elasticsearch or stateless (eg Kibana) instances to move to allocators as part of the upgrade plan. When used in conjunction with '__all__' (roll all instances as a single unit) strategy, these instances are not restarted, which can sometimes enable recovery plans when these instances are boot-looping.
Hide move_instances attributes Show move_instances attributes object
-
The instance id that is going to be moved
-
An optional list of allocator ids to which the instance should be moved. If not specified then any available allocator can be used (including the current one if it is healthy)
-
Tells the infrastructure that the instance should be considered as permanently down when deciding how to migrate data to new nodes. If left blank then the system will automatically decide (currently: will treat the instances as up)
-
-
As part of the upgrade plan, identifies the move requests for the Kibana instances or APM Servers on the allocators.
Hide move_allocators attributes Show move_allocators attributes object
-
The allocator id off which all instances in the cluster should be moved
-
An optional list of allocator ids to which the instance(s) should be moved. If not specified then any available allocator can be used (including the current one if it is healthy)
-
Tells the infrastructure that all instances on the allocator should be considered as permanently down when deciding how to migrate data to new nodes. If left blank then the system will auto-decide (currently: will treat the allocator as up)
-
-
If true (default: false) does not allow re-using any existing instances currently in the cluster, i.e. even unchanged instances will be re-created
-
List of allocators on which instances are placed if possible (if not possible/not specified then any available allocator with space is used)
-
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
Value is
forced
.
-
-
-
-
The settings for building this Enterprise Search cluster
-
-
A list of payloads for Integrations Server updates
An Integrations Server creation request paired with the alias of the Elasticsearch cluster it should be paired with
Hide integrations_server attributes Show integrations_server attributes object
-
A locally-unique user-specified id for the Integrations Server
-
Alias to the Elasticsearch Cluster to attach the Integrations Server to
-
The human readable name for the Integrations Server cluster (default: takes the name of its Elasticsearch cluster)
-
The region where this resource exists
-
The plan for the Integrations Server.
Hide plan attributes Show plan attributes object
-
Defines the topology of the Integrations Server nodes. For example, the number or capacity of the nodes, and where you can allocate the nodes.
Hide cluster_topology attributes Show cluster_topology attributes object
-
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.
-
number of zones in which nodes will be placed
-
The configuration options for the Integrations Server.
Hide integrations_server attributes Show integrations_server attributes object
-
The version of the Integrations Server cluster (must be one of the ECE supported versions, and won't work unless it matches the Integrations Server version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
A structure that defines a curated subset of the Integrations Server settings. TIP: To define the complete set of Integrations Server setting, use
IntegrationsSystemSettings
withuser_settings_override_
anduser_settings_
.Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within Integrations Server - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within Integrations Server - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret token within Integrations Server - defaults to the previously existing secretToken
-
Optionally enable debug mode for Integrations Server - defaults false
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Integrations Server settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of Integrations Server 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Integrations Server 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Integrations Server settings)
-
The mode the Integrations Server is operating in.
Values are
standalone
ormanaged
.
-
-
-
The configuration options for the Integrations Server.
Hide integrations_server attributes Show integrations_server attributes object
-
The version of the Integrations Server cluster (must be one of the ECE supported versions, and won't work unless it matches the Integrations Server version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
A structure that defines a curated subset of the Integrations Server settings. TIP: To define the complete set of Integrations Server setting, use
IntegrationsSystemSettings
withuser_settings_override_
anduser_settings_
.Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within Integrations Server - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within Integrations Server - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret token within Integrations Server - defaults to the previously existing secretToken
-
Optionally enable debug mode for Integrations Server - defaults false
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Integrations Server settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of Integrations Server 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Integrations Server 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'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Integrations Server settings)
-
The mode the Integrations Server is operating in.
Values are
standalone
ormanaged
.
-
-
Defines the configuration parameters that control how the plan is applied. For example, the Elasticsearch cluster topology and Integrations Server 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 plan control configuration options for the Integrations Server.
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)
-
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 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
Value is
forced
.
-
-
-
-
The settings for building this Integrations Server cluster
-
-
-
Any new configuration for the current deployment object. If there is no new configuration the value is unchanged.
Hide settings attributes Show settings attributes object
-
Observability settings for this deployment
Hide observability attributes Show observability attributes object
-
The logging settings for the deployment
Hide logging attribute Show logging attribute object
-
The destination deployment that this deployment's logs will be sent to
Hide destination attributes Show destination attributes object
-
The deployment to send logs and/or metrics to. Contains either the deployment's ID or 'self'.
-
RefId of the Elasticsearch cluster to send logs and/or metrics to. If not specified, refId is resolved automatically as long as the destination deployment contains a single Elasticsearch resource.
-
-
-
The metrics settings for the deployment
Hide metrics attribute Show metrics attribute object
-
The destination deployment that this deployment's logs will be sent to
Hide destination attributes Show destination attributes object
-
The deployment to send logs and/or metrics to. Contains either the deployment's ID or 'self'.
-
RefId of the Elasticsearch cluster to send logs and/or metrics to. If not specified, refId is resolved automatically as long as the destination deployment contains a single Elasticsearch resource.
-
-
-
-
Enable autoscaling for this deployment.
-
See AutoOps integration status for this deployment.
-
-
Any new information about the current deployment object. If there is no new information the value is unchanged.
-
A user-defined alias to use in place of Cluster IDs for user-friendly URLs
-
-
The deployment cannot be successfully migrated to the template with the provided ID.
Hide response attribute Show response attribute object
-
A list of errors that occurred in the failing request
Hide errors attributes Show errors attributes object
-
-
You are not authorized to perform this action.
Hide response attribute Show response attribute object
-
A list of errors that occurred in the failing request
Hide errors attributes Show errors attributes object
-
-
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
-
curl \
--request GET 'http://api.elastic-cloud.com/api/v1/deployments/{deployment_id}/migrate_template?template_id=string'