Guidance for Streamlining Data Access with Jira Service Management and Amazon DataZone
Overview
This Guidance demonstrates how to streamline data access management through the integration of Amazon DataZone and Jira ticketing systems. The included code repository contains stacks that provision an event rule and the required identity and access management roles and policies to facilitate interaction with both Jira and Amazon DataZone. This foundational infrastructure allows you to integrate an Amazon DataZone subscription workflow with a Jira project, enabling data stewards to accept or reject access to data requested in Amazon DataZone directly from the Jira interface. With its extensible design, you can incorporate additional components for notifications on other Amazon DataZone events as well as integrate this Guidance with other ticketing systems as your workflows evolve.
How it works
This architecture diagram shows a comprehensive data streaming workflow for Jira ticketing systems running on AWS. This workflow encompasses the lifecycle of a data subscription, originating from an Amazon DataZone portal, and the subsequent status changes triggered within Jira, which are then reflected in the Amazon DataZone portal.
Deploy with confidence
Everything you need to launch this Guidance in your account is right here
We'll walk you through it
Dive deep into the implementation guide for additional customization options and service configurations to tailor to your specific needs.
Let's make it happen
Ready to deploy? Review the sample code on GitHub for detailed deployment instructions to deploy as-is or customize to fit your needs.
Well-Architected Pillars
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
Operational Excellence
Amazon DataZone simplifies data management for both end-users and operational teams. For example, Amazon DataZone offers a user interface for subscribing to data assets and emits EventBridge events for subscription requests, while Step Functions provides transparency into the current state of the subscription workflow. Additionally, AWS X-Ray assists in the troubleshooting of both the Lambda functions and the Step Functions.
Security
Amazon DataZone implements an authorization mechanism for data asset access, including subscription requests. In addition, IAM policies narrow access to the principle of least privilege. Finally, communication with the external Jira instance uses HTTPS and token authentication. By incorporating these security-centric services, this Guidance can help safeguard the confidentiality and availability of the data and the systems involved.
Reliability
EventBridge and Step Functions support the subscription workflow, with built-in retry mechanisms to help ensure a resilient architecture. Additionally, by decoupling the components, Amazon SQS is used to provide resilience for the communication between the Lambda functions and the Jira system. This approach focuses on building workloads that perform their intended functions correctly and consistently, while also enabling the ability to recover quickly from failures to meet demands.
Performance Efficiency
The capabilities of Amazon DataZone include the structured and streamlined allocation of IT and computing resources, addressing key areas such as the selection of optimized resource types and sizes, performance monitoring, and maintaining efficiency. The architecture further employs EventBridge, Step Functions, and Amazon SQS to support the subscription workflow with built-in retry mechanisms and decoupled components. This holistic approach focuses on workload performance, consistency, and the ability to quickly recover from failures, while also addressing distributed system design, recovery planning, and adaptability to changing requirements.
Cost Optimization
Amazon DataZone helps you establish a data mesh architecture within a significantly reduced timeframe compared to traditional methods. Moreover, instead of maintaining the subscription workflow state in databases, the state is managed within the Step Functions and Amazon SQS services, helping to avoid the operational overhead and costs associated with managing and scaling database infrastructure.
Furthermore, the use of serverless services, such as EventBridge, Step Functions, Lambda, and Amazon SQS, allows for a pay-per-use model and enables this Guidance to scale up or down based on demand without the need to provision and maintain dedicated infrastructure.
Sustainability
The Guidance helps you obtain a comprehensive understanding of the environmental impacts of the utilized services, quantifying these impacts throughout the entire workload lifecycle, and applying design principles and best practices to reduce these impacts. Specifically, it uses EventBridge, Step Functions, Amazon SQS, and Lambda, which eliminate the need for persistent storage or always-on Amazon Elastic Compute Cloud (Amazon EC2) instances. Instead, the compute resources are only used on demand, and the state is maintained within Step Functions and Amazon SQS, contributing to a more environmentally conscious and efficient cloud-based approach.
Disclaimer
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages