How prdngr/red-sky works
Project Type and Purpose
• RedSky is a command-line utility (full CLI app), written in Go, for just-in-time offensive infrastructure provisioning on AWS.
• It embeds Terraform templates and invokes AWS APIs to create and destroy resources (EC2, networking, keys, etc.).
File Structure
• Top-level “cmd” directory: entry points for subcommands (create, destroy, list, version).
• “internal” directory: core services–AWS session management, Terraform orchestration, file handling, user-interface spinner/output, versioning, IP lookup (ifconfig).
• “static/terraform”: embedded Terraform code and modules (cdn, common), scripts (user-data).
• main.go ties everything together.
README Insights
• Describes supported deployment types (Nessus, Kali, Kali+Mythic C2).
• Installation via “go install”, usage via “red-sky create --type …”.
• Outputs AWS session details, deployment summary, SSH instructions.
Main Components
A. User (CLI)
B. RedSky Binary
1. CLI Parser & Command Dispatcher (cmd package)
2. Internal Services Layer:
– AWS Client (internal/aws.go)
– Terraform Orchestrator (internal/terraform.go)
– File Manager & Embedding (internal/files.go + static/embed.go)
– Network Info (internal/ifconfig.go)
– Spinner/UI & Output Formatter (internal/spinner.go + output.go)
– Versioning (internal/version.go)
3. Temporary Workspace (local filesystem) for Terraform files
C. Embedded Terraform Code (static/terraform & modules)
D. Terraform CLI (external binary invoked by orchestrator)
E. AWS API Endpoints (EC2, IAM, Networking, S3 for state)
F. (Optional) SSH Client for end-user connectivity
Relationships and Data Flows
• User issues “red-sky create” → CLI Parser dispatches to Create handler.
• Create handler:
– Initializes AWS session (calls AWS SDK).
– Extracts embedded Terraform assets into temp folder.
– Invokes Terraform init/plan/apply via Terraform orchestrator.
– Polls AWS APIs (e.g., describe-instances, elastic IP) until resource is live.
– Gathers output (instance IP, key material).
– Renders UI spinner and final summary.
• User then SSHs to the provisioned host.
• Similar flow for “destroy” and “list” commands.
Architectural Patterns & Principles
• Layered design: CLI layer → service layer → external dependencies (Terraform, AWS).
• Single binary embedding static assets for portability.
• Separation of concerns:
– cmd/* focuses on CLI/flags
– internal/* on business logic
– static/* on infrastructure-as-code templates
• Dependency injection via passing AWS session and paths into orchestrator.
Relevant Technologies / Libraries
• Go modules (go.mod)
• AWS SDK for Go
• Terraform CLI (external process)
• Go “embed” package (static/embed.go)
• Spinner library (internal/spinner.go)
• Standard libraries (os/exec, io/ioutil, net/http for ifconfig)
It Out
1. Leftmost lane: User & SSH Client.
2. Middle lane (Local Host):
– RedSky CLI binary
– Components: Parser → AWS Client → Terraform Orchestrator → Spinner/Output → Filesystem
– Embedded Terraform modules (static).
– Terraform CLI (external tool)
3. Rightmost lane (AWS Cloud):
– AWS API (EC2, IAM, Networking)
– Provisioned resources (EC2 instance, security groups, EIP)
– State backend (if S3 used in future)
– CLI→AWS SDK calls
– Orchestrator→Terraform CLI→AWS
– AWS→CLI (DescribeOutputs)
– CLI→User (SSH instructions)