// CASE STUDY
AWS Incident Manager <-> Azure DevOps Integration
Integration of AWS SSM Incident Manager together with Azure DevOps with active synchronisation mechanism running in customer's production account.
- Year
- 2024
- Dev team
- 4 eng.
- Users
- 40
- Duration
- 3 to 6 months
// 01 Result
Integration of AWS SSM Incident Manager together with Azure DevOps with active synchronisation mechanism running in customer's production account.
// 02 Used technologies
- AWS-s3
- AWS-IAM
- AWS-SNS
- AWS-SQS
- AWS-SSM
- AWS-apiGateway
- AWS-cloudWatch
- AWS-eventBridge
- AWS-SSM-IM
- Python
- AWS
- GitHub
- Docker
// 03 Challenge
Handling various workflows and event types into one service.
Error events, such as alarms, vulnerability findings, or compliance reports, passing through AWS’scentral Event Bus are captured and analyzed. Content is then formatted, and an SSM incident is created. The service also implements active synchronization with Microsoft Azure DevOps. Example: An AWS Lambda function managing the business logic for Product Team A experiences a timeout due to system overload during Black Friday. This issue triggers a CloudWatch alarm, resulting in the automatic creation of an incident and an Azure DevOps ticket on Product Team A’s dashboard. The data is pre-analyzed and enriched, with detailed information included in the ticket descriptions and comments, aiding the development team in promptly identifying and resolving the problem.
EventIntegration
CloudWatchAlarm DevOpsGuru Dome9(a.k.a. CloudGuard) ActiveSync
IntegrationAzure DevOps Bridge IntegrationAzure DevOps Webhook Productteam subscription Ticket actions per team GrafanaDashboard
