Docs Home Pulumi IaC Pulumi ESC Pulumi Insights Pulumi Cloud Packages Tutorials
  1. Packages
  2. Lacework Provider
  3. API Docs
  4. AlertChannelJiraServer
lacework 2.0.6 published on Monday, Apr 14, 2025 by lacework
lacework/terraform-provider-lacework

lacework.AlertChannelJiraServer

Explore with Pulumi AI

lacework logo
lacework 2.0.6 published on Monday, Apr 14, 2025 by lacework
lacework/terraform-provider-lacework

    Configure Lacework to forward events to Jira. Lacework calls the Jira integration REST API and creates a new Jira open issue for each Lacework event that meets or exceeds the specified alert severity level. If there is a large volume of events that exceed the ability of Jira REST API to create new Jira issues, priority is given to those events with the highest severity.

    Jira + Lacework Integration Prerequisites

    Before creating the Jira alert channel, verify the following prerequisites:

    • Provide a Jira user name and password that is used to create new Jira issues. For management and security purposes, Lacework recommends creating a dedicated Lacework Jira user with appropriate permissions. For more information, refer to the Jira REST API Reference
    • The Jira user must have sufficient privileges to create new Jira issues in the specified Jira project
    • The Jira issue type must exist in the specified Jira project prior to creating the Lacework Jira alert channel. When Lacework creates new Jira issues, it creates new issues based on the specified Jira issue type
    • Whitelist the Lacework outbound IPs to allow Lacework to communicate with the Jira server. See Lacework Outbound IPs

    Example Usage

    import * as pulumi from "@pulumi/pulumi";
import * as lacework from "@pulumi/lacework";

const example = new lacework.AlertChannelJiraServer("example", {
    configuration: "Bidirectional",
    issueType: "Bug",
    jiraUrl: "mycompany.atlassian.net",
    password: "abcd1234",
    projectKey: "EXAMPLE",
    username: "my@username.com",
});

    import pulumi
import pulumi_lacework as lacework

example = lacework.AlertChannelJiraServer("example",
    configuration="Bidirectional",
    issue_type="Bug",
    jira_url="mycompany.atlassian.net",
    password="abcd1234",
    project_key="EXAMPLE",
    username="my@username.com")

    package main

import (
	"github.com/pulumi/pulumi-terraform-provider/sdks/go/lacework/v2/lacework"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := lacework.NewAlertChannelJiraServer(ctx, "example", &lacework.AlertChannelJiraServerArgs{
			Configuration: pulumi.String("Bidirectional"),
			IssueType:     pulumi.String("Bug"),
			JiraUrl:       pulumi.String("mycompany.atlassian.net"),
			Password:      pulumi.String("abcd1234"),
			ProjectKey:    pulumi.String("EXAMPLE"),
			Username:      pulumi.String("my@username.com"),
		})
		if err != nil {
			return err
		}
		return nil
	})
}

    using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Lacework = Pulumi.Lacework;

return await Deployment.RunAsync(() => 
{
    var example = new Lacework.AlertChannelJiraServer("example", new()
    {
        Configuration = "Bidirectional",
        IssueType = "Bug",
        JiraUrl = "mycompany.atlassian.net",
        Password = "abcd1234",
        ProjectKey = "EXAMPLE",
        Username = "my@username.com",
    });

});

    package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.lacework.AlertChannelJiraServer;
import com.pulumi.lacework.AlertChannelJiraServerArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        var example = new AlertChannelJiraServer("example", AlertChannelJiraServerArgs.builder()
            .configuration("Bidirectional")
            .issueType("Bug")
            .jiraUrl("mycompany.atlassian.net")
            .password("abcd1234")
            .projectKey("EXAMPLE")
            .username("my@username.com")
            .build());

    }
}

    resources:
  example:
    type: lacework:AlertChannelJiraServer
    properties:
      configuration: Bidirectional
      issueType: Bug
      jiraUrl: mycompany.atlassian.net
      password: abcd1234
      projectKey: EXAMPLE
      username: my@username.com

    Create AlertChannelJiraServer Resource

    Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.

    Constructor syntax

    new AlertChannelJiraServer(name: string, args: AlertChannelJiraServerArgs, opts?: CustomResourceOptions);
    @overload
def AlertChannelJiraServer(resource_name: str,
                           args: AlertChannelJiraServerArgs,
                           opts: Optional[ResourceOptions] = None)

@overload
def AlertChannelJiraServer(resource_name: str,
                           opts: Optional[ResourceOptions] = None,
                           issue_type: Optional[str] = None,
                           jira_url: Optional[str] = None,
                           password: Optional[str] = None,
                           project_key: Optional[str] = None,
                           username: Optional[str] = None,
                           alert_channel_jira_server_id: Optional[str] = None,
                           configuration: Optional[str] = None,
                           custom_template_file: Optional[str] = None,
                           enabled: Optional[bool] = None,
                           group_issues_by: Optional[str] = None,
                           name: Optional[str] = None,
                           test_integration: Optional[bool] = None)
    func NewAlertChannelJiraServer(ctx *Context, name string, args AlertChannelJiraServerArgs, opts ...ResourceOption) (*AlertChannelJiraServer, error)
    public AlertChannelJiraServer(string name, AlertChannelJiraServerArgs args, CustomResourceOptions? opts = null)
    public AlertChannelJiraServer(String name, AlertChannelJiraServerArgs args)
public AlertChannelJiraServer(String name, AlertChannelJiraServerArgs args, CustomResourceOptions options)

    type: lacework:AlertChannelJiraServer
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.

    Parameters

    name string
    The unique name of the resource.
    args AlertChannelJiraServerArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    resource_name str
    The unique name of the resource.
    args AlertChannelJiraServerArgs
    The arguments to resource properties.
    opts ResourceOptions
    Bag of options to control resource's behavior.
    ctx Context
    Context object for the current deployment.
    name string
    The unique name of the resource.
    args AlertChannelJiraServerArgs
    The arguments to resource properties.
    opts ResourceOption
    Bag of options to control resource's behavior.
    name string
    The unique name of the resource.
    args AlertChannelJiraServerArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    name String
    The unique name of the resource.
    args AlertChannelJiraServerArgs
    The arguments to resource properties.
    options CustomResourceOptions
    Bag of options to control resource's behavior.

    Constructor example

    The following reference example uses placeholder values for all input properties.

    var alertChannelJiraServerResource = new Lacework.AlertChannelJiraServer("alertChannelJiraServerResource", new()
{
    IssueType = "string",
    JiraUrl = "string",
    Password = "string",
    ProjectKey = "string",
    Username = "string",
    AlertChannelJiraServerId = "string",
    Configuration = "string",
    CustomTemplateFile = "string",
    Enabled = false,
    GroupIssuesBy = "string",
    Name = "string",
    TestIntegration = false,
});

    example, err := lacework.NewAlertChannelJiraServer(ctx, "alertChannelJiraServerResource", &lacework.AlertChannelJiraServerArgs{
	IssueType:                pulumi.String("string"),
	JiraUrl:                  pulumi.String("string"),
	Password:                 pulumi.String("string"),
	ProjectKey:               pulumi.String("string"),
	Username:                 pulumi.String("string"),
	AlertChannelJiraServerId: pulumi.String("string"),
	Configuration:            pulumi.String("string"),
	CustomTemplateFile:       pulumi.String("string"),
	Enabled:                  pulumi.Bool(false),
	GroupIssuesBy:            pulumi.String("string"),
	Name:                     pulumi.String("string"),
	TestIntegration:          pulumi.Bool(false),
})

    var alertChannelJiraServerResource = new AlertChannelJiraServer("alertChannelJiraServerResource", AlertChannelJiraServerArgs.builder()
    .issueType("string")
    .jiraUrl("string")
    .password("string")
    .projectKey("string")
    .username("string")
    .alertChannelJiraServerId("string")
    .configuration("string")
    .customTemplateFile("string")
    .enabled(false)
    .groupIssuesBy("string")
    .name("string")
    .testIntegration(false)
    .build());

    alert_channel_jira_server_resource = lacework.AlertChannelJiraServer("alertChannelJiraServerResource",
    issue_type="string",
    jira_url="string",
    password="string",
    project_key="string",
    username="string",
    alert_channel_jira_server_id="string",
    configuration="string",
    custom_template_file="string",
    enabled=False,
    group_issues_by="string",
    name="string",
    test_integration=False)

    const alertChannelJiraServerResource = new lacework.AlertChannelJiraServer("alertChannelJiraServerResource", {
    issueType: "string",
    jiraUrl: "string",
    password: "string",
    projectKey: "string",
    username: "string",
    alertChannelJiraServerId: "string",
    configuration: "string",
    customTemplateFile: "string",
    enabled: false,
    groupIssuesBy: "string",
    name: "string",
    testIntegration: false,
});

    type: lacework:AlertChannelJiraServer
properties:
    alertChannelJiraServerId: string
    configuration: string
    customTemplateFile: string
    enabled: false
    groupIssuesBy: string
    issueType: string
    jiraUrl: string
    name: string
    password: string
    projectKey: string
    testIntegration: false
    username: string

    AlertChannelJiraServer Resource Properties

    To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.

    Inputs

    In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.

    The AlertChannelJiraServer resource accepts the following input properties:

    IssueType string
    The Jira Issue type (such as a Bug) to create when a new Jira issue is created.
    JiraUrl string
    The URL of your Jira implementation without https protocol (https://). For example, mycompany.atlassian.net or mycompany.jira.com.
    Password string
    The password to the Jira user.
    ProjectKey string
    The project key for the Jira project where the new Jira issues should be created.
    Username string
    The Jira user name. Lacework recommends a dedicated Jira user. See above for more information.
    AlertChannelJiraServerId string
    Configuration string
    Defines whether the integration is Unidirectional or Bidirectional. For more information, see more about Bidirectional Jira integrations. Defaults to Unidirectional. The available options are:

    • Unidirectional: A unidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated.
    • Bidirectional: A bidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated, and vice-versa.
    CustomTemplateFile string
    A Custom Template JSON file to populate fields in the new Jira issues.
    Enabled bool
    The state of the external integration. Defaults to true.
    GroupIssuesBy string
    Defines how Lacework compliance events get grouped. Must be one of Events or Resources. Defaults to Events. The available options are:

    • Events: Single Jira issue will be created when compliance events of the same type but from different resources are detected by Lacework. For example, if three different S3 resources are generating the same compliance event, only one Jira ticket is created.
    • Resources: Multiple Jira issues will be created when multiple resources are generating the same compliance event. For example, if three different S3 resources are generating the same compliance event, three Jira issues are created.
    Name string
    The Alert Channel integration name.
    TestIntegration bool
    Whether to test the integration of an alert channel upon creation and modification
    IssueType string
    The Jira Issue type (such as a Bug) to create when a new Jira issue is created.
    JiraUrl string
    The URL of your Jira implementation without https protocol (https://). For example, mycompany.atlassian.net or mycompany.jira.com.
    Password string
    The password to the Jira user.
    ProjectKey string
    The project key for the Jira project where the new Jira issues should be created.
    Username string
    The Jira user name. Lacework recommends a dedicated Jira user. See above for more information.
    AlertChannelJiraServerId string
    Configuration string
    Defines whether the integration is Unidirectional or Bidirectional. For more information, see more about Bidirectional Jira integrations. Defaults to Unidirectional. The available options are:

    • Unidirectional: A unidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated.
    • Bidirectional: A bidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated, and vice-versa.
    CustomTemplateFile string
    A Custom Template JSON file to populate fields in the new Jira issues.
    Enabled bool
    The state of the external integration. Defaults to true.
    GroupIssuesBy string
    Defines how Lacework compliance events get grouped. Must be one of Events or Resources. Defaults to Events. The available options are:

    • Events: Single Jira issue will be created when compliance events of the same type but from different resources are detected by Lacework. For example, if three different S3 resources are generating the same compliance event, only one Jira ticket is created.
    • Resources: Multiple Jira issues will be created when multiple resources are generating the same compliance event. For example, if three different S3 resources are generating the same compliance event, three Jira issues are created.
    Name string
    The Alert Channel integration name.
    TestIntegration bool
    Whether to test the integration of an alert channel upon creation and modification
    issueType String
    The Jira Issue type (such as a Bug) to create when a new Jira issue is created.
    jiraUrl String
    The URL of your Jira implementation without https protocol (https://). For example, mycompany.atlassian.net or mycompany.jira.com.
    password String
    The password to the Jira user.
    projectKey String
    The project key for the Jira project where the new Jira issues should be created.
    username String
    The Jira user name. Lacework recommends a dedicated Jira user. See above for more information.
    alertChannelJiraServerId String
    configuration String
    Defines whether the integration is Unidirectional or Bidirectional. For more information, see more about Bidirectional Jira integrations. Defaults to Unidirectional. The available options are:

    • Unidirectional: A unidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated.
    • Bidirectional: A bidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated, and vice-versa.
    customTemplateFile String
    A Custom Template JSON file to populate fields in the new Jira issues.
    enabled Boolean
    The state of the external integration. Defaults to true.
    groupIssuesBy String
    Defines how Lacework compliance events get grouped. Must be one of Events or Resources. Defaults to Events. The available options are:

    • Events: Single Jira issue will be created when compliance events of the same type but from different resources are detected by Lacework. For example, if three different S3 resources are generating the same compliance event, only one Jira ticket is created.
    • Resources: Multiple Jira issues will be created when multiple resources are generating the same compliance event. For example, if three different S3 resources are generating the same compliance event, three Jira issues are created.
    name String
    The Alert Channel integration name.
    testIntegration Boolean
    Whether to test the integration of an alert channel upon creation and modification
    issueType string
    The Jira Issue type (such as a Bug) to create when a new Jira issue is created.
    jiraUrl string
    The URL of your Jira implementation without https protocol (https://). For example, mycompany.atlassian.net or mycompany.jira.com.
    password string
    The password to the Jira user.
    projectKey string
    The project key for the Jira project where the new Jira issues should be created.
    username string
    The Jira user name. Lacework recommends a dedicated Jira user. See above for more information.
    alertChannelJiraServerId string
    configuration string
    Defines whether the integration is Unidirectional or Bidirectional. For more information, see more about Bidirectional Jira integrations. Defaults to Unidirectional. The available options are:

    • Unidirectional: A unidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated.
    • Bidirectional: A bidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated, and vice-versa.
    customTemplateFile string
    A Custom Template JSON file to populate fields in the new Jira issues.
    enabled boolean
    The state of the external integration. Defaults to true.
    groupIssuesBy string
    Defines how Lacework compliance events get grouped. Must be one of Events or Resources. Defaults to Events. The available options are:

    • Events: Single Jira issue will be created when compliance events of the same type but from different resources are detected by Lacework. For example, if three different S3 resources are generating the same compliance event, only one Jira ticket is created.
    • Resources: Multiple Jira issues will be created when multiple resources are generating the same compliance event. For example, if three different S3 resources are generating the same compliance event, three Jira issues are created.
    name string
    The Alert Channel integration name.
    testIntegration boolean
    Whether to test the integration of an alert channel upon creation and modification
    issue_type str
    The Jira Issue type (such as a Bug) to create when a new Jira issue is created.
    jira_url str
    The URL of your Jira implementation without https protocol (https://). For example, mycompany.atlassian.net or mycompany.jira.com.
    password str
    The password to the Jira user.
    project_key str
    The project key for the Jira project where the new Jira issues should be created.
    username str
    The Jira user name. Lacework recommends a dedicated Jira user. See above for more information.
    alert_channel_jira_server_id str
    configuration str
    Defines whether the integration is Unidirectional or Bidirectional. For more information, see more about Bidirectional Jira integrations. Defaults to Unidirectional. The available options are:

    • Unidirectional: A unidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated.
    • Bidirectional: A bidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated, and vice-versa.
    custom_template_file str
    A Custom Template JSON file to populate fields in the new Jira issues.
    enabled bool
    The state of the external integration. Defaults to true.
    group_issues_by str
    Defines how Lacework compliance events get grouped. Must be one of Events or Resources. Defaults to Events. The available options are:

    • Events: Single Jira issue will be created when compliance events of the same type but from different resources are detected by Lacework. For example, if three different S3 resources are generating the same compliance event, only one Jira ticket is created.
    • Resources: Multiple Jira issues will be created when multiple resources are generating the same compliance event. For example, if three different S3 resources are generating the same compliance event, three Jira issues are created.
    name str
    The Alert Channel integration name.
    test_integration bool
    Whether to test the integration of an alert channel upon creation and modification
    issueType String
    The Jira Issue type (such as a Bug) to create when a new Jira issue is created.
    jiraUrl String
    The URL of your Jira implementation without https protocol (https://). For example, mycompany.atlassian.net or mycompany.jira.com.
    password String
    The password to the Jira user.
    projectKey String
    The project key for the Jira project where the new Jira issues should be created.
    username String
    The Jira user name. Lacework recommends a dedicated Jira user. See above for more information.
    alertChannelJiraServerId String
    configuration String
    Defines whether the integration is Unidirectional or Bidirectional. For more information, see more about Bidirectional Jira integrations. Defaults to Unidirectional. The available options are:

    • Unidirectional: A unidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated.
    • Bidirectional: A bidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated, and vice-versa.
    customTemplateFile String
    A Custom Template JSON file to populate fields in the new Jira issues.
    enabled Boolean
    The state of the external integration. Defaults to true.
    groupIssuesBy String
    Defines how Lacework compliance events get grouped. Must be one of Events or Resources. Defaults to Events. The available options are:

    • Events: Single Jira issue will be created when compliance events of the same type but from different resources are detected by Lacework. For example, if three different S3 resources are generating the same compliance event, only one Jira ticket is created.
    • Resources: Multiple Jira issues will be created when multiple resources are generating the same compliance event. For example, if three different S3 resources are generating the same compliance event, three Jira issues are created.
    name String
    The Alert Channel integration name.
    testIntegration Boolean
    Whether to test the integration of an alert channel upon creation and modification

    Outputs

    All input properties are implicitly available as output properties. Additionally, the AlertChannelJiraServer resource produces the following output properties:

    CreatedOrUpdatedBy string
    CreatedOrUpdatedTime string
    Id string
    The provider-assigned unique ID for this managed resource.
    IntgGuid string
    OrgLevel bool
    TypeName string
    CreatedOrUpdatedBy string
    CreatedOrUpdatedTime string
    Id string
    The provider-assigned unique ID for this managed resource.
    IntgGuid string
    OrgLevel bool
    TypeName string
    createdOrUpdatedBy String
    createdOrUpdatedTime String
    id String
    The provider-assigned unique ID for this managed resource.
    intgGuid String
    orgLevel Boolean
    typeName String
    createdOrUpdatedBy string
    createdOrUpdatedTime string
    id string
    The provider-assigned unique ID for this managed resource.
    intgGuid string
    orgLevel boolean
    typeName string
    created_or_updated_by str
    created_or_updated_time str
    id str
    The provider-assigned unique ID for this managed resource.
    intg_guid str
    org_level bool
    type_name str
    createdOrUpdatedBy String
    createdOrUpdatedTime String
    id String
    The provider-assigned unique ID for this managed resource.
    intgGuid String
    orgLevel Boolean
    typeName String

    Look up Existing AlertChannelJiraServer Resource

    Get an existing AlertChannelJiraServer resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.

    public static get(name: string, id: Input<ID>, state?: AlertChannelJiraServerState, opts?: CustomResourceOptions): AlertChannelJiraServer
    @staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        alert_channel_jira_server_id: Optional[str] = None,
        configuration: Optional[str] = None,
        created_or_updated_by: Optional[str] = None,
        created_or_updated_time: Optional[str] = None,
        custom_template_file: Optional[str] = None,
        enabled: Optional[bool] = None,
        group_issues_by: Optional[str] = None,
        intg_guid: Optional[str] = None,
        issue_type: Optional[str] = None,
        jira_url: Optional[str] = None,
        name: Optional[str] = None,
        org_level: Optional[bool] = None,
        password: Optional[str] = None,
        project_key: Optional[str] = None,
        test_integration: Optional[bool] = None,
        type_name: Optional[str] = None,
        username: Optional[str] = None) -> AlertChannelJiraServer
    func GetAlertChannelJiraServer(ctx *Context, name string, id IDInput, state *AlertChannelJiraServerState, opts ...ResourceOption) (*AlertChannelJiraServer, error)
    public static AlertChannelJiraServer Get(string name, Input<string> id, AlertChannelJiraServerState? state, CustomResourceOptions? opts = null)
    public static AlertChannelJiraServer get(String name, Output<String> id, AlertChannelJiraServerState state, CustomResourceOptions options)
    resources:  _:    type: lacework:AlertChannelJiraServer    get:      id: ${id}
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    resource_name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    The following state arguments are supported:
    AlertChannelJiraServerId string
    Configuration string
    Defines whether the integration is Unidirectional or Bidirectional. For more information, see more about Bidirectional Jira integrations. Defaults to Unidirectional. The available options are:

    • Unidirectional: A unidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated.
    • Bidirectional: A bidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated, and vice-versa.
    CreatedOrUpdatedBy string
    CreatedOrUpdatedTime string
    CustomTemplateFile string
    A Custom Template JSON file to populate fields in the new Jira issues.
    Enabled bool
    The state of the external integration. Defaults to true.
    GroupIssuesBy string
    Defines how Lacework compliance events get grouped. Must be one of Events or Resources. Defaults to Events. The available options are:

    • Events: Single Jira issue will be created when compliance events of the same type but from different resources are detected by Lacework. For example, if three different S3 resources are generating the same compliance event, only one Jira ticket is created.
    • Resources: Multiple Jira issues will be created when multiple resources are generating the same compliance event. For example, if three different S3 resources are generating the same compliance event, three Jira issues are created.
    IntgGuid string
    IssueType string
    The Jira Issue type (such as a Bug) to create when a new Jira issue is created.
    JiraUrl string
    The URL of your Jira implementation without https protocol (https://). For example, mycompany.atlassian.net or mycompany.jira.com.
    Name string
    The Alert Channel integration name.
    OrgLevel bool
    Password string
    The password to the Jira user.
    ProjectKey string
    The project key for the Jira project where the new Jira issues should be created.
    TestIntegration bool
    Whether to test the integration of an alert channel upon creation and modification
    TypeName string
    Username string
    The Jira user name. Lacework recommends a dedicated Jira user. See above for more information.
    AlertChannelJiraServerId string
    Configuration string
    Defines whether the integration is Unidirectional or Bidirectional. For more information, see more about Bidirectional Jira integrations. Defaults to Unidirectional. The available options are:

    • Unidirectional: A unidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated.
    • Bidirectional: A bidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated, and vice-versa.
    CreatedOrUpdatedBy string
    CreatedOrUpdatedTime string
    CustomTemplateFile string
    A Custom Template JSON file to populate fields in the new Jira issues.
    Enabled bool
    The state of the external integration. Defaults to true.
    GroupIssuesBy string
    Defines how Lacework compliance events get grouped. Must be one of Events or Resources. Defaults to Events. The available options are:

    • Events: Single Jira issue will be created when compliance events of the same type but from different resources are detected by Lacework. For example, if three different S3 resources are generating the same compliance event, only one Jira ticket is created.
    • Resources: Multiple Jira issues will be created when multiple resources are generating the same compliance event. For example, if three different S3 resources are generating the same compliance event, three Jira issues are created.
    IntgGuid string
    IssueType string
    The Jira Issue type (such as a Bug) to create when a new Jira issue is created.
    JiraUrl string
    The URL of your Jira implementation without https protocol (https://). For example, mycompany.atlassian.net or mycompany.jira.com.
    Name string
    The Alert Channel integration name.
    OrgLevel bool
    Password string
    The password to the Jira user.
    ProjectKey string
    The project key for the Jira project where the new Jira issues should be created.
    TestIntegration bool
    Whether to test the integration of an alert channel upon creation and modification
    TypeName string
    Username string
    The Jira user name. Lacework recommends a dedicated Jira user. See above for more information.
    alertChannelJiraServerId String
    configuration String
    Defines whether the integration is Unidirectional or Bidirectional. For more information, see more about Bidirectional Jira integrations. Defaults to Unidirectional. The available options are:

    • Unidirectional: A unidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated.
    • Bidirectional: A bidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated, and vice-versa.
    createdOrUpdatedBy String
    createdOrUpdatedTime String
    customTemplateFile String
    A Custom Template JSON file to populate fields in the new Jira issues.
    enabled Boolean
    The state of the external integration. Defaults to true.
    groupIssuesBy String
    Defines how Lacework compliance events get grouped. Must be one of Events or Resources. Defaults to Events. The available options are:

    • Events: Single Jira issue will be created when compliance events of the same type but from different resources are detected by Lacework. For example, if three different S3 resources are generating the same compliance event, only one Jira ticket is created.
    • Resources: Multiple Jira issues will be created when multiple resources are generating the same compliance event. For example, if three different S3 resources are generating the same compliance event, three Jira issues are created.
    intgGuid String
    issueType String
    The Jira Issue type (such as a Bug) to create when a new Jira issue is created.
    jiraUrl String
    The URL of your Jira implementation without https protocol (https://). For example, mycompany.atlassian.net or mycompany.jira.com.
    name String
    The Alert Channel integration name.
    orgLevel Boolean
    password String
    The password to the Jira user.
    projectKey String
    The project key for the Jira project where the new Jira issues should be created.
    testIntegration Boolean
    Whether to test the integration of an alert channel upon creation and modification
    typeName String
    username String
    The Jira user name. Lacework recommends a dedicated Jira user. See above for more information.
    alertChannelJiraServerId string
    configuration string
    Defines whether the integration is Unidirectional or Bidirectional. For more information, see more about Bidirectional Jira integrations. Defaults to Unidirectional. The available options are:

    • Unidirectional: A unidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated.
    • Bidirectional: A bidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated, and vice-versa.
    createdOrUpdatedBy string
    createdOrUpdatedTime string
    customTemplateFile string
    A Custom Template JSON file to populate fields in the new Jira issues.
    enabled boolean
    The state of the external integration. Defaults to true.
    groupIssuesBy string
    Defines how Lacework compliance events get grouped. Must be one of Events or Resources. Defaults to Events. The available options are:

    • Events: Single Jira issue will be created when compliance events of the same type but from different resources are detected by Lacework. For example, if three different S3 resources are generating the same compliance event, only one Jira ticket is created.
    • Resources: Multiple Jira issues will be created when multiple resources are generating the same compliance event. For example, if three different S3 resources are generating the same compliance event, three Jira issues are created.
    intgGuid string
    issueType string
    The Jira Issue type (such as a Bug) to create when a new Jira issue is created.
    jiraUrl string
    The URL of your Jira implementation without https protocol (https://). For example, mycompany.atlassian.net or mycompany.jira.com.
    name string
    The Alert Channel integration name.
    orgLevel boolean
    password string
    The password to the Jira user.
    projectKey string
    The project key for the Jira project where the new Jira issues should be created.
    testIntegration boolean
    Whether to test the integration of an alert channel upon creation and modification
    typeName string
    username string
    The Jira user name. Lacework recommends a dedicated Jira user. See above for more information.
    alert_channel_jira_server_id str
    configuration str
    Defines whether the integration is Unidirectional or Bidirectional. For more information, see more about Bidirectional Jira integrations. Defaults to Unidirectional. The available options are:

    • Unidirectional: A unidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated.
    • Bidirectional: A bidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated, and vice-versa.
    created_or_updated_by str
    created_or_updated_time str
    custom_template_file str
    A Custom Template JSON file to populate fields in the new Jira issues.
    enabled bool
    The state of the external integration. Defaults to true.
    group_issues_by str
    Defines how Lacework compliance events get grouped. Must be one of Events or Resources. Defaults to Events. The available options are:

    • Events: Single Jira issue will be created when compliance events of the same type but from different resources are detected by Lacework. For example, if three different S3 resources are generating the same compliance event, only one Jira ticket is created.
    • Resources: Multiple Jira issues will be created when multiple resources are generating the same compliance event. For example, if three different S3 resources are generating the same compliance event, three Jira issues are created.
    intg_guid str
    issue_type str
    The Jira Issue type (such as a Bug) to create when a new Jira issue is created.
    jira_url str
    The URL of your Jira implementation without https protocol (https://). For example, mycompany.atlassian.net or mycompany.jira.com.
    name str
    The Alert Channel integration name.
    org_level bool
    password str
    The password to the Jira user.
    project_key str
    The project key for the Jira project where the new Jira issues should be created.
    test_integration bool
    Whether to test the integration of an alert channel upon creation and modification
    type_name str
    username str
    The Jira user name. Lacework recommends a dedicated Jira user. See above for more information.
    alertChannelJiraServerId String
    configuration String
    Defines whether the integration is Unidirectional or Bidirectional. For more information, see more about Bidirectional Jira integrations. Defaults to Unidirectional. The available options are:

    • Unidirectional: A unidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated.
    • Bidirectional: A bidirectional integration with Jira allows you to programatically generate a corresponding Jira issue for an alert. When the alert status is updated, the Jira status is updated, and vice-versa.
    createdOrUpdatedBy String
    createdOrUpdatedTime String
    customTemplateFile String
    A Custom Template JSON file to populate fields in the new Jira issues.
    enabled Boolean
    The state of the external integration. Defaults to true.
    groupIssuesBy String
    Defines how Lacework compliance events get grouped. Must be one of Events or Resources. Defaults to Events. The available options are:

    • Events: Single Jira issue will be created when compliance events of the same type but from different resources are detected by Lacework. For example, if three different S3 resources are generating the same compliance event, only one Jira ticket is created.
    • Resources: Multiple Jira issues will be created when multiple resources are generating the same compliance event. For example, if three different S3 resources are generating the same compliance event, three Jira issues are created.
    intgGuid String
    issueType String
    The Jira Issue type (such as a Bug) to create when a new Jira issue is created.
    jiraUrl String
    The URL of your Jira implementation without https protocol (https://). For example, mycompany.atlassian.net or mycompany.jira.com.
    name String
    The Alert Channel integration name.
    orgLevel Boolean
    password String
    The password to the Jira user.
    projectKey String
    The project key for the Jira project where the new Jira issues should be created.
    testIntegration Boolean
    Whether to test the integration of an alert channel upon creation and modification
    typeName String
    username String
    The Jira user name. Lacework recommends a dedicated Jira user. See above for more information.

    Import

    A Lacework Jira Server Alert Channel integration can be imported using a INT_GUID, e.g.

    $ pulumi import lacework:index/alertChannelJiraServer:AlertChannelJiraServer example EXAMPLE_1234BAE1E42182964D23973F44CFEA3C4AB63B99E9A1EC5

    -> Note: To retrieve the INT_GUID from existing integrations in your account, use the Lacework CLI command lacework alert-channel list. To install this tool follow this documentation.

    To learn more about importing existing cloud resources, see Importing resources.

    Package Details

    Repository
    lacework lacework/terraform-provider-lacework
    License
    Notes
    This Pulumi package is based on the lacework Terraform Provider.
    lacework logo
    lacework 2.0.6 published on Monday, Apr 14, 2025 by lacework
    lacework/terraform-provider-lacework