How ivanpetrushev/jira-issues-graph works
Key Components to Include:
Frontend Layer
• Static Web Hosting (S3 Bucket)
• HTML/JS files (index.html, graph.html, main.js, graph.js)
• This as the client-facing component
Backend Layer
• API Gateway
• Three Lambda Functions:
• generate-graph
• get-results
• -issues
• IAM Roles and Permissions
External Services
• Jira API (as an external dependency)
Connection Flows
• API Gateway to respective Lambda Functions
• Lambda Functions connecting to Jira API
Specific Elements
• S3 Bucket containing web assets
• API Gateway endpoints
• Three distinct Lambda Functions with their purposes
• IAM roles and policies
• Jira API integration point
Additional Details
• A note about future CloudFront/SSL integration (marked as planned)
• Configuration flow from terraform outputs to web config
• Public access points
Future expansion possibilities (CloudFront)
Remember to indicate that this is an AWS-native solution using terraform for infrastructure as code, with all components being managed through terraform configurations.