Inventory of hand-built cloud resources
Before writing a line of infrastructure code, you need to know what already exists and who made it. Most teams find resources created in the console years ago, test buckets nobody remembers and security groups with no owner. A single inventory grouped by account, region and service tells you what to import first, what to delete and where the risk sits.
First tasks
- List every cloud account, subscription or project the team can sign in to
- Export a resource inventory for each account and active region
- Mark each resource as managed by code, hand-built or unknown
- Name an owner for every production resource and flag the ten riskiest