Cloud Platforms, Tools, and Technologies

The Lazsa Platform integrates with an array of tools and technologies for infrastructure provisioning, product development, data engineering and beyond, across various stages of product development and deployment. All you need to do is configure the connection details of these tools and technologies. You can then seamlessly access your preferred technologies from the single interface of the Lazsa Platform. This diverse tool support ensures flexibility and enhances productivity meeting the unique needs of every team and project.

Managing your saved connection configurations in Lazsa is easy. You can save multiple configurations for tool instances based on your requirements. You can modify connection details as needed, manage configuration access, select default configurations, and delete unwanted configurations.

  1. Sign in to the Lazsa Platform and click Configuration in the left navigation pane.
  2. On the Platform Setup screen, on the Cloud Platform, Tools & Technologies tile, click Configure.
  3. Configure the connection details of the following tools and technologies required in your product development life cycle. For detailed configuration steps, click each link in the Tool/Technology column.
    Tool/ TechnologyDescription
    Cloud Platforms

    The Lazsa Platform supports integration with the following cloud platforms:

    • Amazon Web Services (AWS)
    • Microsoft Azure
    Technologies and Testing Tools

    Select the type of application you are creating and accordingly select the required technology stack. The Lazsa Platform supports technologies grouped under the following categories:

    • API
    • Data Analytics
    • Data Integration
    • Data Quality
    • Data Transformation
    • Data Visualization
    • Data Management
    • Databases
    • Helm Repository
    • Web App
    • Workflow
    DevOps CI/CD Pipeline Configuration

    Currently, theLazsa Platform supports the following DevOps CI/CD pipeline tool:

    • Jenkins

    Kubernetes

    To access your Kubernetes cluster from within the Lazsa Platform, configure the cluster connection details.

    OpenShift Container PlatformTo access your OpenShift cluster from within the Lazsa Platform, configure the cluster connection details.
    Terraform ConfigurationConfigure the connection details of your Terraform Cloud workspaces and source code repositories to manage your Terraform runs from within the Lazsa Platform.
    Secret Management

    Currently, theLazsa Platform supports the following secret management tools:

    • AWS Secrets Manager

    • Azure Key Vault

    Source Code Repository

    Provide the connection details of your active accounts of source code repositories.

    Currently, theLazsa Platform supports the following source code repositories:

    • GitLab
    • Bitbucket Server
    • GitHub Enterprise Server
    • Bitbucket Cloud
    • GitHub Cloud
    Agile Planning Tools

    Currently, theLazsa Platform supports the following agile planning tool:

    • Jira

    Document Management Tools

    Currently, the Lazsa Platform supports the following document management tool:

    • Confluence
    Databases and Data Warehouses

    Currently, the Lazsa Platform supports the following databases:

    • Azure RDS
    • Amazon RDS
    • Amazon S3
    • Amazon AppFlow Connector
    • FTP
    • AWS Glue
    • Amazon Kinesis Data Streams
    • RDBMS
    • SFTP
    • Snowflake
    Data Integration

    Currently, the Lazsa Platform supports the following data integration tools:

    • Amazon AppFlow Connector
    • Databricks

    Data Visualization

    Currently, the Lazsa Platform supports the following data visualization tool:

    • QlikSense
    Systems Integration

    Currently, the Lazsa Platform supports the following systems integration tools:

    • Amazon SQS

    • Amazon SNS

    Artifacts Management Tools

    Currently, the Lazsa Platform supports the following artifacts management tools:

    • Amazon ECR

    • JFrog Artifactory

    • Azure ACR

    Security Assessment Tools

    Currently, the Lazsa Platform supports the following security assessment tools:

    • SonarQube
    • Qualys

Deleting a Connection Configuration

You may want to delete saved connection configurations that are no longer in use or required. The option to delete configurations is currently available for the following tools and technologies:

  • Cloud Platforms: AWS, Azure

  • DevOps CI/CD Tools: Jenkins

  • Container Orchestration: Kubernetes, OpenShift

  • Infrastructure as Code: Terraform

  • Source Code Repositories: Bitbucket, GitHub, GitLab

  • Agile Planning Tools: Jira

  • Document Management Tools: Confluence

  • Secret Management Tools: AWS Secrets Manager, Azure Key Vault

  • Artifact Management Tools: JFrog, Amazon ECR

  • Security Assessment Tools: Qualys, SonarQube

To delete a configuration of any of these tools or technologies, do the following:

On the configuration tile, click the ellipsis (...) in the upper right corner, and click Delete.

If the configuration is not set as the default or is not in use across any products, a confirmation dialog is displayed. Enter a mandatory comment explaining why you want to delete the configuration and then click Delete to confirm.

Confirm configuration deletion

The configuration is deleted and the details of this deletion are logged in the platform audit logs.

Default Configuration Restriction

If you try to delete a default configuration, you see the following informational dialog.

Deleting a defulat configuration is not allowed

In this case, do the following:

  1. Review the list of products and policy templates in which the configuration is currently used.

  2. Resolve dependencies associated with the configuration.

  3. Mark another configuration of the same tool as default and then try deleting this configuration.

In-Use Configuration Restriction

If you try to delete a configuration which is not a default one but is being used in products across the platform, you see the following informational dialog.

You cannot delete a configuration already in use.

In this case, do the following:

Review the list of products and policy templates in which the configuration is currently used.

Resolve dependencies associated with the configuration and then try deleting it.

After you configure the connection details of the required tools and technologies, you may want to create a portfolio, add products to it, and add releases and features to the product. See About Product Line, Product, Release, and Features.

Related Topics Link IconRecommended Topics What's next? Product Portfolio or Product Line