Deprecated: Update a managed integration
- Base URL
-
https://{kibana_url}
- PUT /api/fleet/agentless_policies/{policyId}
- PUT /s/{space_id}/api/fleet/agentless_policies/{policyId}
Deprecated. Use PUT /api/fleet/managed_integrations/{policyId} instead. Update a managed integration by ID. Uses full-replace semantics: the policy is rebuilt entirely from the request body, so any omitted optional field (for example, description, vars, global_data_tags, cloud_connector) is cleared or reset to its default. The integration package name is immutable and the runtime-managed cluster_id is preserved from the existing policy.
Path parameters
-
space_idstringoptional -
An identifier for the space. If
space_idis not provided in the URL, the default space is used. Refer to Spaces for more information.
Query parameters
-
onboarding_deployment_idstring · max length: 256The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Planned We plan to add this functionality in a future Elastic Stack update. Subject to changes. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. -
ID of the cloud onboarding instance that manages the package policies. Required to change package policies managed by a cloud onboarding instance; only the onboarding flow is expected to set it. Requests that change a managed package policy without a matching ID are rejected with a 400 error, and
forcedoes not bypass this check. A bulk delete that includes such a package policy is rejected as a whole.
Request body
-
additional_datastreams_permissionsstring[] · max items: 100nullable -
Additional data stream permissions that will be added to the agent policy.
-
cloud_connectorobjectnullable -
cloud_connector_idstring · max length: 256 -
ID of an existing cloud connector to reuse. If not provided, a new connector is created. Requires
enabled: trueand cannot be combined withname. -
enabledboolean · default: false -
Set to
trueto attach a cloud connector to this policy. Must betrueto set any ofcloud_connector_id,name, ortarget_csp. -
create_dataset_templatesboolean -
When true, install dedicated index templates for streams with a custom data_stream.dataset. Defaults to true for input packages, false for integration packages.
-
forceboolean -
Force package policy creation even if the package is not verified, or if the agent policy is managed.
-
inputsmap string to object -
Package policy inputs. Refer to the integration documentation to know which inputs are available.
-
<string>object -
conditionstring · max length: 10000nullable -
Agent condition expression to evaluate whether to apply this input.
-
streamsmap string to object -
Input streams. Refer to the integration documentation to know which streams are available.
-
namespacestring · max length: 100 -
Policy namespace. When not specified, it inherits the agent policy namespace.
-
policy_templatestring · max length: 256 -
The policy template to use for the managed integration. If not provided, the default policy template is used.
Responses
Indicates a successful response
-
itemobjectrequired -
additional_datastreams_permissionsstring[] · max items: 1000 -
Additional data stream permissions granted to the managed integration.
-
global_data_tagsobject[] · max items: 100 -
Custom data tags applied to all data produced by this policy.
-
inputsmap string to objectrequired -
Package policy inputs. Refer to the integration documentation to know which inputs are available.
-
<string>object -
conditionstring · max length: 10000nullable -
Agent condition expression to evaluate whether to apply this input.
-
streamsmap string to object -
Input streams. Refer to the integration documentation to know which streams are available.
-
onboarding_deployment_idstring · max length: 256The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Planned We plan to add this functionality in a future Elastic Stack update. Subject to changes. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. -
ID of the cloud onboarding instance that manages this managed integration. Set by Fleet, read-only.
Bad Request