How aleibl/cloudscanner4internet works
AWS Cloud Infrastructure
• Multiple AWS Regions (show at least 3 regions as examples)
• EC2 Instances running the custom AMI
• Region-specific AMI IDs
Control Flow Components
• Main Controller (aws-run-scan.py)
• Scan Executor (run_scan.py)
• Data Transformer (transform-ip2asn.py)
• Startup Service (run-scan-at-startup.service)
Cloud Infrastructure Layer (Middle)
• Inside each region, show:
• AMI deployment
• EC2 instances (multiple instances per region)
• Local scanning processes
Execution Layer (Bottom)
• Scanning components:
• masscan execution
• nmap processes
• Data collection flow
Use the following visual elements:
• Blue: Control components
• Orange: AWS infrastructure
• Green: Scanning processes
• Gray: Support services
Important Relationships to Show:
Control Flow
• aws-run-scan.py → AWS Regions → EC2 Instances → run_scan.py
Data Flow
• Scan Results → transform-ip2asn.py → Processed Data
Startup Process
• EC2 Instance → run-scan-at-startup.service → run_scan.py
Additional Considerations:
Scaling capabilities
• Instance replication
• Multi-region deployment
• Parallel scanning operations
Level of Detail:
• Configuration points like AMI IDs and region selection