awsiamPractitioner

Integrating AWS DevOps Agent with Jira: Event-Driven Automation

5 min read AWS DevOps BlogOct 2, 2026Reviewed for accuracy

Practitioner — Hands-on experience recommended

In today's fast-paced DevOps environment, integrating tools for better visibility and response is crucial. The integration of AWS DevOps Agent with Jira via Amazon EventBridge allows teams to automatically create and update issues based on operational investigations. This not only streamlines workflows but also ensures that critical issues are tracked and addressed promptly.

The integration works through an event-driven model. When the AWS DevOps Agent detects an operational issue, it emits an event to Amazon EventBridge with the source set to 'aws.aidevops'. An EventBridge rule then triggers an AWS Lambda function based on the event type. For instance, when an investigation is created, the Lambda function interacts with the Jira Cloud REST API to create a new issue. For subsequent investigation events, it updates the existing Jira issue by adding comments. To maintain the relationship between the investigation and the Jira issue, the integration uses Amazon DynamoDB to store mappings between the investigation task ID and the Jira issue key.

To implement this integration effectively, ensure you have an AWS account with the necessary permissions to create Lambda functions, EventBridge rules, DynamoDB tables, and manage secrets in AWS Secrets Manager. You’ll also need a local development environment set up with the AWS CLI, AWS CDK, and Node.js 18 or later. Be mindful that the integration relies on proper configuration of the Jira credentials stored in Secrets Manager, which is critical for the Lambda function to authenticate with the Jira Cloud REST API. Additionally, always verify that your EventBridge rules are correctly set to capture the right investigation events to avoid missing critical updates.

Key takeaways

→Automate issue creation in Jira by configuring AWS Lambda to respond to AWS DevOps Agent events.
→Store mappings between investigation task IDs and Jira issue keys in Amazon DynamoDB for easy tracking.
→Ensure your AWS environment has the necessary permissions for Lambda, EventBridge, and Secrets Manager.
→Use Node.js 18 or later to meet the runtime requirements for your Lambda functions.

Why it matters

This integration significantly reduces the manual overhead of tracking operational issues, allowing teams to focus on resolution rather than administration. It enhances responsiveness and accountability in incident management.

Code examples

Bash

1export JIRA_BASE_URL="https://your-domain.atlassian.net"
2export JIRA_USER_EMAIL="your-email@example.com"
3export JIRA_API_TOKEN="your-api-token"
4export JIRA_PROJECT_KEY="PROJ"
5export SECRET_NAME="devops-agent-jira-credentials"
6
7aws secretsmanager create-secret \
8  --name ${SECRET_NAME} \
9  --description "Jira credentials for DevOps Agent EventBridge integration" \
10  --secret-string "{\"jiraBaseUrl\":\"${JIRA_BASE_URL}\",\"jiraUserEmail\":\"${JIRA_USER_EMAIL}\",\"jiraApiToken\":\"${JIRA_API_TOKEN}\",\"jiraProjectKey\":\"${JIRA_PROJECT_KEY}\"}"