Skip to content

Getting Started with Config0

overview

Prerequisites

  • GitHub Account: Required for registration and login
  • AWS Account: Needed for IaC execution: secrets, logs, and federated workers
  • Forked Launch Repository: Working copy of Config0 examples

Step 1: Fork the Launch Repository

  • Visit the launch-config0 repository
  • Click the Fork button in the top right corner
  • Important: Uncheck the box that only copies the default (“main”) branch to ensure you get all sample branches

Step 2: Create Your Config0 Account

  • Sign up here
  • Authenticate with GitHub1
  • Authorize Config0’s application access2
  • Provide your AWS credentials temporarily:
    • AWS_ACCESS_KEY_ID
    • AWS_SECRET_ACCESS_KEY
  • Onboarding takes 5-10 minutes3
  • Security Note: Deactivate your AWS keys after onboarding completes!

Step 3: Understanding Sample Projects

The forked repository contains branches with pre-configured automation samples:

  • Each branch includes a sample config file at config0/config0.yml
  • For example
    • vars_set branch to used to create a variable set that is used to query and inject variable values
    • vpc branch to establish network foundations
    • select other infrastructure branch name samples

Step 4: Choose Your Implementation Path

Connect your existing running IaC codes and run them through CI/CD pipelines that will provide standard:

  • OpenTofu/Terraform init, validate, format
  • Automated security scanning (TfSec)
  • Cost estimation (Infracost)
  • Plan review in PR comments
  • GitOps-based approval workflow to execute plans

Option B (Test Drive Marketplace Solutions): Running Sample Config0 IAC

  • Start with vars_set branch to used to create a variable set that is used to query and inject variable values
  • Execute the vpc branch to build network foundations
  • Select additional infrastructure components (like MongoDB) as needed

Option C (Advance - Customization): Import Existing Infrastructure Code and Create Developer Solutions

Build developer solutions by importing your existing infrastructure code (not running) and leveraging Config0’s workflow layers to create developer solutions that can be used in an internal developer platform.

  1. Bitbucket support coming soon. ↩

  2. The GitHub application is registered under “Jiffy”. ↩

  3. Onboarding creates CodeBuild projects, Lambda functions, and secure networking for execution. All sensitive data remains in your AWS account. ↩