Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
redStack — Terraform-deployed red team operator lab on AWS: Mythic, Sliver, and Adaptix C2 behind a production-style Apache redirector, with Kali/Windows hosts and a Guacamole portal. Built for authorized training and self-hosted cyber ranges. | Kitploit
Tools/GitHubGitHub/devzero-security/redstack
Cloud Infrastructure SecurityPenetration Testing FrameworksExploit FrameworksPost-ExploitationSecurity VirtualizationNetwork SecurityCommand and ControlLearning & EducationRed TeamingPayload DevelopmentLabs & Practice
286332427 days agoReviewed by Kitploit
GitHubdevzero-security/redstack

redStack

Terraform-deployed red team operator lab on AWS: Mythic, Sliver, and Adaptix C2 behind a production-style Apache redirector, with Kali/Windows hosts and a Guacamole portal. Built for authorized training and self-hosted cyber ranges.

View Repository

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

redStack

redStack Banner

Attending DEF CON 34? Click here to see presentation times and the prerequisites needed for the workshop.

DEF CON 34 Adversary Village Red Team Village Noob Village Session Docs & Prereqs

A red-team operator stack on AWS, up in ~45 minutes: three C2 frameworks (Mythic, Sliver, Adaptix), an Apache redirector, Kali and Windows workstations, and a Guacamole portal, across two peered VPCs with header + URI gating and scanner blocking. Run it two ways: Direct Access against your own self-hosted cyber range, or Tunneled Access over OpenVPN into a hosted training platform, Hack Smarter Labs, Hack The Box, OffSec Proving Grounds/Labs, VulnLab, or any platform that provides an .ovpn.

[!TIP] redStack now has a provider-agnostic successor: redStackPRO. It is a web canvas that composes red team infrastructure and cyber ranges as a provider-agnostic topology, then compiles that topology to a complete, runnable directory of Terraform and Ansible you run yourself. GCP and AWS are tested end to end; Azure, Proxmox, and ESXi are on the roadmap. Built and maintained under devZero Security. See redstackpro.com.

📖 Full documentation lives in the redStack Wiki →

The wiki is the de facto operator handbook. This README is a thin landing page so you can find your way in. Everything you need to deploy, verify, run the C2 walkthroughs, troubleshoot, or extend the lab lives there.


[!IMPORTANT] redStack is not a tutorial on how to use C2 frameworks. It's an environment that removes the infrastructure hurdle so you can focus on learning. This lab is strictly for authorized training and lab environments only (cyber ranges, self-hosted environments, personal lab VMs, etc.). Not intended for use in real-world engagements or against targets you do not own and have explicit written permission to test.

[!CAUTION] AWS TOS: use at your own risk. Hosting C2 infrastructure on AWS may raise concerns under the AWS Acceptable Use Policy. Before deploying, review the AUP and submit the AWS Penetration Testing / Simulated Events request form. As long as you're using redStack exclusively for personal lab work and authorized training platforms, you're generally in the clear. To be safe, run redStack from a dedicated, single-purpose throwaway AWS account.


Deploy in 5 Steps

#WhatWhere
1First-time AWS setup (account, IAM, CLI, SSH key, Kali Marketplace subscription)Prerequisites
2Pick open or closed environmentDeployment Modes
3Configure tfvars and terraform applyDeploy
4Confirm Guacamole + Windows + internal DNSVerify
5Land first beacon: pick a C2Mythic · Sliver · Adaptix

Total time: ~30-60 minutes on first deploy. Subsequent deploys: ~20-30 minutes.

Returning operator? Quick-Start is the abbreviated path.


What Gets Deployed

Seven EC2 instances across two peered VPCs. Two have public Elastic IPs (Guacamole portal + redirector); everything else is reachable only through Guacamole.

HostnameRolePublic IP
guacGuacamole portal (web SSH/RDP)Yes
redirectorApache reverse proxy + C2 frontendEIP exposes 80/443 only
mythicMythic C2 serverNo
sliverSliver C2 serverNo
adaptixAdaptix C2 teamserver (headless)No
windowsWindows Server 2022 workstationNo
kaliKali Linux workstation (AD enum + attack toolset)No

Full inventory and sizing details: Lab-Inventory. Architecture diagram: Lab-Architecture.


Cost

Roughly $0.27/hour of compute while running. With terraform destroy between sessions (recommended), expected monthly cost is ~$15-20/month for typical 5-10 hr/wk study cadence. Full breakdown including stop-vs-destroy tradeoffs: Cost-Management.

[!CAUTION] Forgetting a deployed lab is the #1 cause of unexpected AWS bills. Set a CloudWatch billing alarm before your first terraform apply.


When Something Breaks

Troubleshooting covers the failure modes that actually come up: Mythic SSL cert, Sliver missing, Adaptix build failed, agent not calling back, Marketplace OptInRequired, VPC limits, redirect.rules download issues, Kali user rename, ssh -R binding behavior, and more.


Wiki Page Map

Getting started: Home · Quick-Start · Prerequisites · Deployment Modes · Deploy · Verify · First-Run

Reference: Lab-Architecture · Lab-Inventory · Guacamole · Cost-Management

C2 backends: Mythic · Sliver · Adaptix

Workstations: Windows · Kali

Download Tool