Software Artifact Mapping

Map your cloud accounts and cloud resources to Software Artifacts in your VSM workspace

Link Cloud Resources to Software Artifacts

Part of our recommended tagging policy is to associate your cloud resources to the Software Artifact they belong to. These tags can then be used to group the resulting Compute Environments in LeanIX Value Stream Management to the corresponding Software Artifact, e.g., one with category Microservice.

For example, if you added a tag microservice: MyService to all virtual machines that are used to run the microservice "MyService" in the cloud and provided a Software Artifact mapping "microservice": "microservice", LeanIX Value Stream Management can group these resources to a Software Artifact of category "Microservice" and name "MyService".

Map Cloud Tag Keys to Software Artifacts

  1. In your LeanIX Value Stream Management Workspace, go to Administration > Cloud Service Discovery.
  2. Map tag keys to Software Artifact categories in the configuration (where you also configured the Cloud Accounts) using the configuration snippet shown below.
{
  "artifactMappingPerTagGroup": {
    <tag key>: <software artifact category>,
    ...
  }
}

You can assign different tag keys to the same Software Artifact category, e.g., when different tag keys are used in different Cloud Providers or in different Business Units in your company.

📘

Tag keys and values are treated case-sensitive

The keys and values for the tags (AWS, Azure) respectively labels (GXP) are treated in a case-sensitive way. I.e., if you are using MicroService in AWS and microservice in GCP, please configure a mapping for both MicroService and microservice. Please also keep in mind that different artifacts will be created for tag/label values with different cases (e.g., invoice-management vs Invoice-Management).

The following categories are defined in the standard data model:

  • thirdParty
  • legacy
  • library
  • microfrontend
  • microservice
  • tooling

Using Self-service-configuration, additional categories can be added to your workspace, and referenced here thereafter.

📘

Use the categories' ids when defining the mapping

Please use the ids of the categories when defining the mapping, not their label. (I.e., microservice instead of Microservice.)

When omitting a category, or providing an invalid category (one not defined in the data model), saving the update configuration is disallowed. If custom categories are required, please add them to the data model first.

Here is an example for a configuration:

{
  "aws": {
    "accounts": [
      {
        "arn": "arn:aws:iam::123456789012:role/LeanIXCloudDiscovery",
        "extensions": [
          "organizations"
        ],
      },
      {
        "arn": "arn:aws:iam::210987654321:role/LeanIXCloudDiscovery"
      }
    ]
  },
  "artifactMappingPerTagGroup": {
    "microservice": "microservice",
    "microserviceId": "microservice",
    "tool": "tool",
  }
}

Note that in this example both cloud tag keys microservice and microserviceId are assigned to the same Software Artifact category "microservice".

  1. Click the button Overwrite all configurations to save your configuration.
  2. Click the button Scan now to start the discovery process. Wait until all scan runs show the status COMPLETED. (Refresh the browser page if necessary.)

Browse Software Artifacts in the Inventory

  1. In your LeanIX Value Stream Management Workspace, go to Inventory.
  2. Filter for Type: Software Artifact.
  3. Filter for Data Source Tag: Public Cloud.

Did this page help you?