RepliMap Docs

Quick Start

Run your first scan and generate Terraform in 2 minutes

Get started with RepliMap in under 2 minutes.

Install RepliMap

pip install replimap

Scan Your Infrastructure

Run a scan to build the dependency graph of your AWS account:

replimap scan --profile prod --region us-east-1

You'll see output like:

Scanning: VPC, EC2, RDS, S3, IAM...
✓ Found 1,584 resources
✓ Mapped 1,470 dependencies

Generate Terraform

Turn that scan into Terraform plus an import scaffold — an adoption starting point you can terraform validate immediately:

# Preview what will be generated
replimap codify --profile prod --dry-run

# Generate Terraform files
replimap codify --profile prod --output-dir ./terraform

Review Generated Code

Resources are grouped into one file per service:

terraform/
├── vpc.tf / networking.tf / security_groups.tf
├── ec2.tf / compute.tf / alb.tf
├── rds.tf / elasticache.tf
├── s3.tf / storage.tf / messaging.tf
├── providers.tf / versions.tf
└── imports.tf        # import scaffold (Pro) — one block per resource,
                      # with the correct import ID format per type

Run terraform init && terraform validate to check the output against the real provider schema — the free tier includes every resource file, so you can judge the quality before paying for anything.

Common Scan Options

# Scan a specific VPC
replimap scan --profile prod --scope vpc:vpc-12345678

# Scan resources by tag
replimap scan --profile prod --entry tag:Application=MyApp

# Scan from an entry point (ALB)
replimap scan --profile prod --entry alb:my-app-alb

# Use cache for faster incremental scans
replimap scan --profile prod --cache

Check IaC Coverage

If part of the account is already under Terraform, find out exactly what isn't — the ClickOps inventory terraform plan structurally can't show you:

# Match live resources against one or more state files
replimap codify --profile prod \
  --coverage-state s3://tf-states/prod/terraform.tfstate

# Or a whole directory of local states
replimap codify --profile prod --coverage-state-dir ./states

Coverage is existence matching, not attribute comparison: every scanned resource is checked against every state you provide, and what's left is triaged into real ClickOps, embedded (e.g. EBS volumes owned by an instance), and likely auto-created (service-linked roles).

Visualize Your Infrastructure

Generate an interactive HTML graph — a single self-contained file that renders air-gapped:

replimap graph --profile prod --format html --output architecture.html
open architecture.html

Validate the Output

cd ./terraform

# Initialize and validate against the real provider schema
terraform init
terraform validate

# With the Pro import scaffold: import, then aim for "0 to change"
terraform plan

Next Steps

On this page