How guhan05/aws-honeypot works
This repository appears to implement an SSH honeypot that records attack activity and exposes it through a browser dashboard. The likely workflow runs a honeypot host, collects its logs, stores parsed attack records, and serves those records to the dashboard; Terraform files indicate AWS resources for this system. The Lambda excerpts confirm log parsing and database access, but the README is empty and Terraform, dashboard, and setup contents were not sampled, so their connections are shown as unverified.
Main entry points: cloudwatch.tf Attack logs · ec2.tf SSH honeypot host · alert_handler.py Log processor · api_handler.py Records API
Components 14
Honeypot Host
- Host setup
honeypot/setup.sh - SSH honeypot host
terraform/ec2.tf
Attack Data
- Attack logs
terraform/cloudwatch.tf - Log processor
lambda/alert_handler.py
AWS Services
- Attack records
terraform/dynamodb.tf - Records API
lambda/api_handler.py - API Gateway
terraform/apigateway.tf - GuardDuty
terraform/guardduty.tf - SNS alerts
terraform/sns.tf - IAM permissions
terraform/iam.tf - Lambda resources
terraform/lambda.tf - CloudWatch resources
terraform/cloudwatch.tf
Dashboard
- Attack dashboard
dashboard/index.html
Other components
- Dashboard user
Connections 11
- Log processor → Attack records: writes records
lambda/alert_handler.py - Records API → Attack records: scans records
lambda/api_handler.py - Dashboard user → Attack dashboard: views
- Attack dashboard → API Gateway: requests records
- API Gateway → Records API: invokes
- Host setup → SSH honeypot host: configures host
- SSH honeypot host → Attack logs: emits logs
- Attack logs → Log processor: triggers processing
- GuardDuty → SNS alerts: sends alerts
- IAM permissions → Lambda resources: grants access
- CloudWatch resources → Attack logs: configures logging