How cluedtke/discord-bot-once-human-codes works
AWS Services Layer
• AWS Lambda (Primary compute service)
• CloudWatch Events/EventBridge (Trigger mechanism)
• S3 (likely used for Lambda deployment)
External Services Layer
• Steam Discussions (Data source)
• Discord Webhook (Output destination)
Component Relationships
• CloudWatch Event → Lambda (triggering)
• Lambda → Steam Discussions (scraping)
• Lambda → Discord Webhook (posting)
Additional Details
Annotations for:
• CloudWatch cron schedule (daily trigger)
• Lambda function name and runtime (Python)
[CloudWatch Events] --triggers--> [Lambda Function]
• scrapes
• v
• [Steam Discussions]
• extracts codes
• v
• [Discord Webhook]
Important Considerations:
Infrastructure as Code
• A note that the infrastructure is managed via Terraform
• Configuration files (terraform/*.tf) influence on resource creation
Security and Access
• IAM roles and permissions if applicable
• Secure webhook communication
State Management
• If any state needs to be maintained between runs, indicate storage mechanism
Level of Detail:
• Timing indicators for the scheduled execution
Remember to:
• Use clear labels for all components
• A title and brief description
• Deployment method (Terraform)
• Document any environment variables or configuration requirements