stack kb fleet-cloud-onboarding-deployments post-fleet-cloud-onboarding-deployments cli command
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. 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.
Serverless
Preview
Preview
Stack
Preview
Preview
elastic stack kb fleet-cloud-onboarding-deployments post-fleet-cloud-onboarding-deployments \
--mechanisms <mechanisms> \
--provider <provider> \
--services <services> \
[options]
Create cloud onboarding deployment
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--mechanismsstring[]required-
Delivery mechanisms active in this deployment.
Repeatable: pass
--mechanismsmultiple times to supply more than one value --providerenumrequired-
Cloud provider.
Values: aws, azure, gcp
--servicesstring[]required-
Service IDs to be covered by this deployment.
Repeatable: pass
--servicesmultiple times to supply more than one value --agent-policy-idsstring[]-
Agent policy IDs for agent_based existing-policy deploys. Provided on create so that a mid-deploy tab-close leaves a record that hydrates back into existing mode.
Repeatable: pass
--agent-policy-idsmultiple times to supply more than one value --auth-methodenum-
Authentication method. Allowed values depend on the delivery mechanism: - managed_integration: identity_federation | static_keys
- agent_based: static_keys (direct_access_keys) | temporary_keys | shared_credentials | assume_role
Values: identity_federation, static_keys, temporary_keys, shared_credentials, assume_role
--connector-idstring- ID of the fleet-cloud-connector to associate with this deployment. Omit for static-keys deployments.
--data-formatenum-
Data format: ecs or otel.
Values: ecs, otel
--global-regionstring- Global AWS region from the Service Settings step.
--service-varsstring- Per-service config keyed by instance ID.
--input-filestring- path to a JSON file to use as command input
--dry-run- validate all inputs and exit without performing any action (preview changes without applying them)
--no-validate- skip input validation and send the request as-is
--output-fieldsstring- comma-separated list of fields to include in output (dot-notation supported)
--output-templatestring- Mustache-like template for custom text output (e.g. "{{id}}: {{name}}")
--json-
output as JSON