Machine Configuration Settings

The Machine Configuration Settings screen helps you control the infrastructure used for deploying your applications or technology stack. With these settings, you can manage and optimize infrastructure costs by limiting the machine configurations and the number of cloud instances and load balancers that users can provision and use for their deployments.

The configuration options that you enable here will be available for selection to developers when they add cloud instances in the Deploy phase of feature development.

Note:

If you enforce a policy template, the machine configuration options enabled in the policy template supersede the options that you enable on this screen.

Configure Machine Configuration Settings

To enable the required machine configuration settings, do the following.

  1. Sign in to the Lazsa Platform and click Configuration in the left navigation pane.

  2. On the Platform Setup screen, on the Settings tile, click Configure.
  3. On the Machine Configuration Settings screen, do the following in each section.

    Enable or disable the predefined instance configuration options based on your application's needs and performance requirements. The following lighter and hence, cost-efficient configurations are available. They vary in terms of their memory (RAM) and the number of virtual Central Processing Units (vCPUs).

    • Large - 8 GB RAM 2 vCPU
    • Medium - 4 GB RAM 2 vCPU
    • Small - 2GB RAM 2 vCPU

     

    Custom Configuration

    In this section, we have predefined some heavy configuration options for you. You can add and enable these additional options as per your development requirements. You may require these instance types for various reasons, depending on the nature of your applications, development tasks, and performance requirements. The following are some common scenarios where developers might opt for such instances:

    • For building resource-intensive applications

    • To meet high traffic and scalability requirements

    • For big data processing tasks

    • In testing and staging environments that closely mimic production settings

    • In virtualization and containerization to ensure optimal performance for running multiple instances or containers on a single host

    Note:

    While heavy configuration instances provide significant computational power, they are cost-intensive, so you should carefully assess your specific requirements and workload demands to strike the right balance between performance and cost-effectiveness.

    Enable this option and define the maximum number of cloud instances that can be provisioned across products being developed from within the Lazsa Platform. By setting a maximum limit on the number of cloud instances, you can control and manage infrastructure costs more effectively. This prevents users from unintentionally provisioning excessive instances, which could lead to unexpected expenses.

    This is a setting used in your Docker deployments from within the Lazsa Platform. If you enable this option, users can choose between manual and automatic load balancer creation at a stage level in the Deploy phase of feature development.

    With automatic load balancer creation, users can offload the load balancer setup tasks to the Lazsa Platform, making it easier for users to deploy scalable and highly available applications.

  4. Save your changes.

Thus, the machine configuration settings enable you to optimize your infrastructure usage, adhere to budget constraints, and make efficient decisions when deploying your tech stack or applications from within the Lazsa Platform. With these settings, you can strike a balance between performance and cost-effectiveness.

Related Topics Link IconRecommended Topics What's next? Security Settings