CloudForge - Jenkins on AWS in minutes
Deploy full-suite of Jenkins Directly to your AWS Account
4 followers
Deploy full-suite of Jenkins Directly to your AWS Account
4 followers
CloudForge makes deploying Jenkins on AWS effortless. Spin up a working setup in minutes, not weeks. Open foundation for contributors, with enterprise options for teams that need scale, security, and support.
🚀 CloudForge — Deploy Jenkins on AWS in Minutes
Hey Product Hunt!
I’m excited to introduce CloudForge, a project designed to take the pain out of standing up CI/CD infrastructure in the cloud.
For anyone who’s ever had to wrangle Jenkins or cloud automation before, you know the drill: it’s weeks of configuration, security groups, scaling, and networking before you even see a login screen. I wanted to change that.
So I built CloudForge, a set of AWS CDK (Java) modules that lets you deploy Jenkins to AWS in minutes instead of days.
👉 Try it out with the sample project: https://github.com/CloudForgeCI/...
💡 What it does
One-line deploy → everything you need wired up automatically
Open foundation → community-friendly modules you can extend and contribute to
Enterprise-ready path → optional advanced features (multi-AZ, WAF, SSO, PrivateLink, NAT gateways, etc.) for companies that need scale and security
🔑 Why it matters
For companies: Skip the endless setup. Get a proven CI/CD foundation and scale it with enterprise features when you’re ready. I’ll be offering guidance and setup help for teams that want to roll this out.
For contributors: The open repositories will be live for collaboration. Jump in, extend, and help shape where the project goes next.
🌍 The vision
CloudForge is about more than Jenkins—it’s about lowering the barrier to modern infrastructure. The plan is to expand beyond Jenkins to a broader set of automation tools, always balancing open collaboration with enterprise capabilities.
The foundation is here. The ecosystem is starting. And this is just the beginning.
✨ I’d love your feedback, contributions, and ideas. Let’s build the future of cloud automation together.
AWS CDK for Jenkins is exactly what's been missing. Love that it's open source. Does it handle auto-scaling for build agents?
Also launching today (ZenTrack) - upvoted!
@graino It currently is not directly wired for autoscaling, but is able to be configured for it. I do have plans of adding and testing it.
@phillip389 Hey Phillip! Makes sense to start with the core functionality first - autoscaling can definitely come later.
Building in public and iterating based on real needs is the way! We're taking the same approach with our AI features.
🚀 We just carved CloudForge into two focused, open-source projects—cleaner boundaries, faster builds, and a friendlier path for contributors.
What changed:
We split the big toolbox into two well-labeled kits. It’s easier to understand, test, and improve—whether you’re deep in CI/CD or just curious about how this stuff works.
New public repos:
Core (foundations & APIs) → https://github.com/CloudForgeCI/cfc-core
Modules: cloudforge-api, cloudforge-core
Community (turnkey Jenkins on AWS) → https://github.com/CloudForgeCI/cloudforge-community
Modules: cloudforge-jenkins-ec2, cloudforge-jenkins-fargate, cloudforge-jenkins-ec2-ssl, cloudforge-jenkins-fargate-ssl
Why this helps
Independent versioning and cleaner Git history
Streamlined CI/CD and Central-ready structure
Smaller mental load for new contributors
How you can jump in
Star the repos, skim the READMEs, and open an issue or PR
Tell me which examples or templates you’d like to see next
#OpenSource #DevOps #AWS #Jenkins #AWSCDK #Java #Maven #InfrastructureAsCode #CloudForgeCI
What’s new in CloudForge (modular + more guardrails)
Clean module split. Core is now two libs—cloudforge-api (models/contracts) and cloudforge-core (CDK builders). Community wrappers live in their own repo for clarity.
https://github.com/CloudForgeCI/cfc-core • https://github.com/CloudForgeCI/cloudforge-community
Pre-synth rule engine. New validation layer (RuleKit, RuntimeRules, TopologyRules) catches mis-configs before CDK synth.
Dedicated Jenkins builders. Separate EC2 and Fargate+EFS/ECS builders with a simple Jenkins façade—clearer responsibilities and easier testing.
Observability boost. Toggle VPC Flow Logs → CloudWatch via FlowLogFactory for quick network visibility.
Built-in testing app. New testing application with EC2/Fargate stacks + unit tests across factories—great for testing locally.
DevEx polish. Strategic move from Construct to Stack where it simplifies usage, plus version bumps and housekeeping.
Try it here: https://github.com/CloudForgeCI/cfc-core — and see the wrappers at https://github.com/CloudForgeCI/cloudforge-community
Footnote: For now, only the Fargate runtime is live; EC2 is in progress. A single unified entry point replaces four legacy paths and covers the full deployment surface—SSL, domain/subdomain wiring, VPC Flow Logs to CloudWatch, or a minimal no-domain/no-SSL mode. Existing legacy paths are still available.