Does it document secrets?

No, the skill is designed to only list resource names and configuration patterns, and it explicitly avoids printing or storing actual secret values.

Does this skill support multi-cloud environments?

Yes, it includes specific investigation patterns and heuristics for AWS, Microsoft Azure, and various Kubernetes distributions including kOps.

What is Infrastructure Archaeology?

It is a systematic process of investigating and documenting undocumented cloud resources to understand their original purpose and current operational risks.

Can it help with EKS migrations?

Yes, it specifically maps kOps-managed clusters to identify configuration drift and architectural details necessary for a smooth EKS transition.

How does it handle company mergers?

It identifies 'merge artifacts' such as duplicate resources, overlapping CIDR ranges, and redundant logging pipelines that are common when companies consolidate.

Infra Archaeology

Name: Infra Archaeology
Author: simplycycling

bysimplycycling

0•

Cloud Infrastructure

Deciphers, maps, and documents legacy cloud infrastructure and inherited configurations to uncover intent and resolve technical debt.

This skill empowers engineers to navigate complex, undocumented cloud environments—particularly during company mergers or after personnel changes. It provides a systematic framework for investigating AWS, Azure, and Kubernetes resources, moving from evidence to hypothesis to identify hidden dependencies, redundant assets, and historical decision-making context. By automating the discovery of resource relationships and mapping configurations back to logical business needs, it simplifies the process of untangling technical debt and preparing for modern infrastructure migrations.

Key Features

01Systematic four-layer investigation framework to move from raw evidence to architectural hypothesis.

02Reverse-engineering of IAM roles, security groups, and database parameter groups to infer original design intent.

030 GitHub stars

04Automated documentation generation for infrastructure records (/infra-doc) and Architecture Decision Records (/adr).

05Intelligent tagging system to classify legacy assets, merge artifacts, and undocumented technical debt.

06Deep discovery patterns for AWS networking, Azure resource groups, and Kubernetes kOps-managed clusters.

Use Cases

01Reverse-engineering infrastructure after a company merger or acquisition to identify redundant resources.

02Onboarding to a legacy project with zero documentation or surviving contributors to map dependencies.

03Auditing kOps-managed Kubernetes clusters to prepare for a migration to Amazon EKS.

Key Features

01Systematic four-layer investigation framework to move from raw evidence to architectural hypothesis.

02Reverse-engineering of IAM roles, security groups, and database parameter groups to infer original design intent.

030 GitHub stars

04Automated documentation generation for infrastructure records (/infra-doc) and Architecture Decision Records (/adr).

05Intelligent tagging system to classify legacy assets, merge artifacts, and undocumented technical debt.

06Deep discovery patterns for AWS networking, Azure resource groups, and Kubernetes kOps-managed clusters.

Use Cases

01Reverse-engineering infrastructure after a company merger or acquisition to identify redundant resources.

02Onboarding to a legacy project with zero documentation or surviving contributors to map dependencies.

03Auditing kOps-managed Kubernetes clusters to prepare for a migration to Amazon EKS.