RepliMap Docs

Introduction

RepliMap - AWS Infrastructure Intelligence Engine

Welcome to RepliMap

RepliMap is an AWS Infrastructure Intelligence Engine that reverse-engineers your AWS infrastructure into Terraform code. Visualize dependencies and audit security in minutes.

100% Local Execution: RepliMap runs entirely on your machine. Your AWS credentials and infrastructure data never leave your environment.

The Problem

You inherited an AWS account. Or maybe you built it yourself over 3 years of "just one more click."

Now you have:

  • Hundreds of resources and no idea what connects to what
  • No Terraform — or a state file that covers half of what's really there
  • A hand-off (or an audit) coming — and no way to prove what exists

The Solution

RepliMap scans your AWS, builds a dependency graph, and gives you superpowers:

$ replimap -p prod scan

✓ Found 1,584 resources
✓ Mapped 1,470 dependencies
✓ Graph cached — next: replimap graph / codify

(That's real output from a 1,584-resource production account — the same account where we found the entire data layer, all 27 RDS instances, in no Terraform state at all.)

Key Features

Core Principles

PrincipleDescription
🔒 Read-OnlyWe only require read permissions. We never modify your resources.
📍 Local ProcessingAll data stays on your machine. No SaaS cloud to trust.
⚡ Resilient ScanningParallel scanners with per-item retries — 1,500+ resource accounts in minutes.
📦 Self-Contained OutputReports and graphs are single files that load nothing from the internet.

Supported Resources

Resources are listed here only if RepliMap scans them from the AWS API. Types marked graph only appear in the dependency graph, graph and deps, but codify does not emit them as Terraform (it would need data RepliMap refuses to read, such as function code or secret values, or the type is not generated yet). Everything else is generated as Terraform (scan → codify).

codify also skips resources owned by a CloudFormation stack (tagged aws:cloudformation:stack-id / stack-name): importing them would make Terraform and CloudFormation fight over the same resource. The summary shows how many were skipped; pass --include-cfn-managed to generate them anyway. They stay in the scan graph, and --coverage-state reports them as auto-created rather than actionable. AWS-reserved aws: tags are never written to the generated Terraform.

39 codified resource types plus 12 graph-only types:

CategoryResources
NetworkVPC, Subnet, Security Group, Route Table, Internet Gateway, NAT Gateway, VPC Endpoint, Network ACL, Elastic IP
Compute & Load BalancingEC2 Instance, Launch Template, Auto Scaling Group, Application/Network Load Balancer (+ target groups, listeners)
DatabaseRDS Instance, Aurora Cluster (+ Cluster Instance), DB Subnet Group, DB Parameter Group, ElastiCache Cluster, ElastiCache Subnet Group, DynamoDB Table
StorageS3 Bucket, S3 Bucket Policy, EBS Volume
Messaging & MonitoringSQS Queue, SNS Topic, CloudWatch Log Group, CloudWatch Metric Alarm
IAMIAM Role, IAM Instance Profile
DNS, CDN & CertificatesRoute53 Hosted Zone, Route53 Record (incl. alias, weighted and latency records), ACM Certificate, CloudFront Distribution
Containers (ECS / ECR)ECS Cluster, ECR Repository; graph only: ECS Service, ECS Task Definition (environment variable values are never stored)
ServerlessLambda Event Source Mapping; graph only: Lambda Function (no code download; environment variable values are never stored)
Secrets & EncryptionSecrets Manager Secret (metadata only, never the value), KMS Key (customer-managed, including its key policy), KMS Alias; graph only: SSM Parameter (never the value)
API Gateway (graph only)REST API, REST Stage, REST Custom Domain, REST VPC Link, HTTP/WebSocket API, HTTP/WebSocket Stage, HTTP/WebSocket Custom Domain, HTTP/WebSocket VPC Link

Not yet supported: EKS, EFS, CloudTrail, VPC Flow Logs.

New types are added based on what real scans encounter — if your account leans on something we don't cover yet, tell us.

Next Steps

On this page