Proper planning of a deployment architecture is one of the critical factors in unlocking the Elastic Stack potential, leading to better operational efficiency and optimum performance.
Highlighted below are parameters that influence the architecture. Based on the organization’s needs, customers are encouraged to dive deeper into these aspects using the mentioned resources.
Depending on the use case, customers can select the hardware profiles and instance size for optimum performance. For example, a CPU optimized hardware profile provides high vCPU optimum for search-heavy use cases, and a Storage optimized hardware profile provides high I/O throughput for index-heavy use cases. Customers can resize their nodes anytime by editing their deployment.
A resilient and highly available cluster requires redundancy of each component and data. Customers should have deployment in more than one zone to have redundancy of components and data. For example, it is strongly recommended to deploy a data tier in more than one zone to ensure data availability in case of zonal loss.
Elastic Cloud provides an autoscaling feature that allows customers to configure the maximum size of data tier nodes and machine learning nodes for autoscaling. In the event of scaling, Elastic Cloud will scale up the node size in response to the increased load.
Elastic offers index lifecycle management (ILM) to manage both indices and data streams. Customers can manage their data lifecycle using ILM to roll over data to different tiers to save on storage costs and improve performance, or delete the data depending on retention policies.
Elastic Cloud is a managed offering from Elastic that operates under a shared responsibility model, where Elastic is responsible for the security and operation of Elastic Cloud and customers are responsible for their deployment.
Elastic Cloud provides several security features that customers can utilize to safeguard their deployments:
Customers can set up monitoring of their production deployment (by shipping logs and metrics to another deployment). This allows customers to view the deployment health dashboard and get alerts. Setting up monitoring is essential as it allows customers to understand and remediate issues within their deployment. For production, it is recommended to send monitoring data to a separate deployment.
The Elastic Cloud utilizes the snapshot feature to securely back up customer deployment data. These backups, also known as snapshots, are stored in a designated off-cluster location called a snapshot repository, which could be hosted on AWS S3, Google Cloud Storage, or Microsoft Azure.
By default, Elastic Cloud automatically backs up customer deployment data and settings. However, customers can specify their own custom repositories from any of the cloud providers and can schedule backups as per their disaster recovery plan.