How easttimor/aws-incident-response works
The project is focused on AWS Incident Response—providing both documentation (via GitHub Pages using Jekyll _layouts and a detailed README) and deployable infrastructure (using Terraform) for investigating API activities and automating notifications when high‐risk AWS API events occur. In essence, it documents Athena SQL queries to analyze CloudTrail logs and deploys AWS EventBridge rules (with SNS notifications) to alert on suspicious or misconfiguration activities.
Main Components
• Documentation/UI Component:
– The root contains a README.md and _layouts directory which shows that the project has a web-based component (e.g. GitHub Pages) where users can review incident response documentation and query examples.
• Terraform Infrastructure-as-Code (IaC) Component:
– The “terraform” directory includes main.tf, terragrunt.hcl, and multiple modules (e.g., rules and sns_topic). These are responsible for deploying EventBridge event filters and SNS topics into AWS.
• AWS Services (Conceptual Components):
– AWS CloudTrail: Source of security-related event logs.
– Amazon Athena: Used for querying and analyzing CloudTrail logs with SQL.
– AWS EventBridge: Configured to catch high-risk API events based on rules defined by Terraform.
– Amazon SNS: Deployed for notifications triggered by EventBridge.
– Optional AWS Config, VPC Flow Logs, and Lambda are mentioned in the documentation as part of the observation and incident response ecosystem.
File Structure and Relationships
• Terraform Modules:
– The “terraform/modules/rules” directory contains several .tf files with eventbridge-rule configurations and CloudTrail investigation queries. This signals that EventBridge is a major trigger point.
– The “terraform/modules/sns_topic” directory provides configuration for SNS topics that receive notifications from the EventBridge rules.
• The main Terraform configuration (e.g., main.tf in terraform/) ties these modules together and deploys the necessary AWS resources.
• Configuration files like terragrunt.hcl indicate potential environment management for reusable Terraform configurations.
• The _layouts directory and GitHub Pages link in the README show that the deployment not only handles infrastructure but also serves as a browsable incident response playbook.