LogScale Self-Hosted Deployment
This manual covers the deployment of Falcon LogScale Self-Hosted versions 1.137.0-1.142.4. Self-hosted deployment means that you manage an your own installation of LogScale. This can be a bare metal, virtual server, private cloud, or a public cloud environment. This is different to using LogScale Cloud, where the infrastructure is managed by CrowdStrike.
In this documentation you will learn about planning for, and installing, your own self-hosted LogScale cluster. While you can install the requirements directly onto physical or virtual servers, the preferred method is to use containers and Kubernetes to deploy the cluster. You can run your Kubernetes cluster on your own servers, or using a public Kubernetes managed service such as Amazon Elastic Kubernetes Service (EKS).
LogScale also requires an Apache Kafka cluster. Again, this can be installed directly on to your own servers, or implemented using a public managed service such as Amazon Managed Streaming for Apache Kafka (MSK).
When running LogScale on your own infrastructure there are a number of different methods and considerations to take into account. For background on how LogScale is typically deployed, see LogScale Physical Architecture.
This section provides details of recommended planning to be carried out before the installation and deployment of LogScale. This covers subjects such as preferred deployment option, sizing guides, and system requirements.
This section provides details on how to install Falcon LogScale using containers. This is the preferred method of deploying your LogScale cluster.
Installing On Bare Metal or Cloud Instance
This section provides details on how to install Falcon LogScale on physical or virtual servers. While this method enables complete control of every facet of your installation, it requires considerably expertise to manage and scale this method of deployment.