Deploy on Elastic Cloudedit
To use Fleet for central management, a Fleet Server must be running and accessible to your hosts. Provisioning Fleet Server on Elastic Cloud as part of the hosted Elasticsearch Service is one of several approaches to setting up Fleet Server.
Elastic Cloud runs a hosted version of Integrations Server that includes Fleet Server. No extra setup is required unless you want to scale your deployment.
Compatibility and prerequisitesedit
Fleet Server is compatible with the following Elastic products:
-
Elastic Stack 7.13 or later.
- For version compatibility: Elasticsearch >= Fleet Server >= Elastic Agent (except for bugfix releases)
- Kibana should be on the same minor version as Elasticsearch.
-
Elastic Cloud Enterprise 2.10 or later
-
Requires additional wildcard domains and certificates (which normally only
cover
*.cname, not*.*.cname). This enables us to provide the URL for Fleet Server ofhttps://.fleet.. - The deployment template must contain an Integrations Server node.
For more information about hosting Fleet Server on Elastic Cloud Enterprise, refer to Manage your Integrations Server.
-
Requires additional wildcard domains and certificates (which normally only
cover
The TLS certificates used to secure connections between Elastic Agent and Fleet Server are managed by Elastic Cloud. You do not need to create a private key or generate certificates.
Setupedit
To confirm that an Integrations Server is available in your deployment:
- In Kibana, go to Management → Fleet.
- On the Agents tab, look for the Elastic Cloud agent policy. This policy is managed by Elastic Cloud, and contains a Fleet Server integration and an Elastic APM integration. You cannot modify the policy. Confirm that the agent status is Healthy.
Don’t see the agent? Make sure your deployment includes an Integrations Server instance. This instance is required to use Fleet.
Next stepsedit
Now you’re ready to add Elastic Agents to your host systems. To learn how, see Install Fleet-managed Elastic Agents.