Before
Teams likely had to review AWS Config notifications, determine the alert type, switch between AWS and Jira, and perform the appropriate remediation manually. They also had to send verification messages, document completed actions, and archive Jira issues based on the response.
How it works
- Receive the AWS Config notification and create a Jira issue for qualifying alerts.
- Classify the notification and perform the corresponding EC2, security group, or verification action.
- Record the result in Jira and archive the issue when the expected response or closure path is reached.
Workflow details
- Notification intake and tracking: The workflow receives an SNS notification from AWS Config and evaluates whether it represents an initial subscription event. For qualifying alerts, it creates a Jira issue containing the notification details so the event has an operational record.
- Alert classification: The Jira issue is routed according to the notification type, including powered-off EC2 instances, non-compliant SSH security group rules, and deleted resources. This decision determines which infrastructure or verification action follows.
- Infrastructure remediation: For a powered-off instance, the workflow starts the EC2 instance. For a non-compliant SSH finding, it retrieves the relevant security group rules and submits a rule modification action.
- Verification and exception handling: For a resource-deleted notification, the workflow sends a verification message and evaluates the response. An expected response leads to issue archiving, while an unexpected response routes through an EC2 stop action before the process is documented.
- Audit trail and closure: The workflow adds comments to Jira describing the process performed and archives issues on the designated expected-response paths, keeping remediation activity connected to the original alert.
What changed
Each notification is automatically converted into a tracked Jira workflow and routed to a defined remediation or verification branch. Infrastructure actions, documentation, response checks, and selected issue-archiving steps now occur as part of the same automated handoff.
Work removed
Manually creating Jira issues, classifying notifications, checking EC2 and security group conditions, starting or stopping instances, modifying security group rules, sending verification messages, adding remediation comments, and archiving completed issues.
Expected outcome
Each qualifying notification is handled through one automated decision path, conservatively removing at least three recurring manual touchpoints for issue creation, remediation or verification, and documentation or closure.
