IaC Hub · Infrastructure automation
Evaluate, track and improve your IaC adoption.
Measure what Terraform and CloudFormation actually manage, detect infrastructure drift and uncover resources created outside code. IaC Hub turns these gaps into a prioritized plan to expand infrastructure automation safely.
Read-only analysis Daily and on-demand Team-controlled remediation
IaC Hub · Illustrative assessment Cloud2Gether
Environment baseline production · payments-platform
Analysis complete
73% IaC coverage
Resources linked to Terraform or CloudFormation definitions.
Latest findings Daily execution
aws_db_instance.customer backup_retention_period changed outside code Drifted
aws_s3_bucket.exports No Terraform or CloudFormation definition found Unmanaged
aws_ecs_service.api Live configuration matches declared state Codified
Read-only analysis Terraform + CloudFormation Daily and on-demand
How IaC Hub works
Turn your live infrastructure into an IaC adoption baseline
IaC Hub compares connected cloud resources with Terraform and CloudFormation definitions, classifies the gaps and prioritizes what your team should review.
- Discover Live cloud resources
- Match Terraform and CloudFormation
- Classify Codified, drifted or unmanaged
- Prioritize Risk and workload context
- Track Daily adoption baseline
IaC Hub · Coverage
Know what is managed as code and what escaped it
A console hotfix, an unmanaged resource or a stale definition can break the link between repositories and live infrastructure. IaC Hub measures coverage and classifies each resource as codified, drifted, unmanaged or ghost.
Codified resources
See which resources have a matching infrastructure definition.
Drifted and unmanaged
Find live changes and resources created outside approved code workflows.
Ghost references
Expose definitions that no longer match a resource in the environment.
IaC Hub · Coverage and drift Cloud2Gether
Coverage 73% 1,980 codified
Drifted 96 Needs review
Unmanaged 612 Outside code
ResourceDefinitionStatusSource
payments-api production Terraform Codified main.tf
customer-db production Terraform Drifted database.tf
exports-bucket production Not found Unmanaged Not applicable
legacy-queue production CloudFormation Ghost messaging.yml
customer-db drift 2 attributes changed outside the approved definition Review first
IaC Hub · Adoption
Focus IaC adoption where it reduces real operational risk
Coverage is not a vanity metric. Break it down by workload and environment to find where manual infrastructure creates the greatest recovery, audit and maintenance exposure.
Workload context
Compare coverage without treating every resource as equally important.
Prioritized gaps
Move production and shared infrastructure ahead of low-impact cleanup.
Progress over time
Refresh the baseline with recurring and on-demand executions.
IaC Hub · Adoption baseline Cloud2Gether
payments-platform Production 14% outside IaC
customer-data Production 39% outside IaC
analytics Data 52% outside IaC
internal-tools Development 22% outside IaC
Highest adoption gap Analytics has 52% of resources outside Terraform or CloudFormation. Start with production data stores and shared networking.
IaC Hub · Prioritized action plan Cloud2Gether
Recommended next actions
Guidance only Close the highest-risk IaC gaps first
01
Investigate Database drift
High priority Confirm whether retention and deletion-protection changes were intentional.
02
Codify Exports bucket
Medium priority Add the production bucket to the approved Terraform workflow.
03
Reconcile Legacy queue
Low priority Remove the obsolete CloudFormation reference after ownership review.
Your delivery workflow stays in control Cloud2Gether identifies and prioritizes the gap. Your team reviews, updates and applies the IaC through its existing process.
IaC Hub · Recommended actions
Turn IaC findings into a reviewable order of work
A useful finding ends with a decision. IaC Hub groups the gap, explains why it matters and recommends what the team should investigate, codify or reconcile first.
Clear next action
Separate investigation, codification and reconciliation work.
Risk-based priority
Start with the changes that can affect resilience, recovery or governance.
Human-controlled execution
Keep approvals and deployment inside the team's existing workflow.
Infrastructure as Code FAQ
IaC coverage and drift, explained
Answers about Terraform, CloudFormation, unmanaged resources, drift detection and Cloud2Gether's read-only operating model.
What is Infrastructure as Code?
Infrastructure as Code, or IaC, is the practice of defining and managing infrastructure through versioned configuration instead of relying on manual changes. It improves repeatability, reviewability and the ability to understand how an environment was created.
Which Infrastructure as Code tools does IaC Hub support?
IaC Hub works with Terraform and AWS CloudFormation. It uses the available infrastructure definitions and the connected cloud environment to show coverage, drift and resources that remain outside approved code workflows.
What is Terraform drift detection?
Terraform drift detection identifies differences between the infrastructure described in code and the resources currently running in the cloud. IaC Hub highlights the affected resource and the attributes that changed so the team can investigate the cause and decide how to reconcile it.
What is the difference between drifted, unmanaged and ghost resources?
A drifted resource exists in code and in the cloud, but its live configuration differs. An unmanaged resource exists in the cloud without an associated IaC definition. A ghost resource remains referenced by code but is no longer found in the connected environment.
Does Cloud2Gether automatically change or apply IaC?
No. Cloud2Gether analyzes the environment with read-only access and recommends what the team should review. Engineers remain responsible for updating, approving and applying changes through their existing repositories and delivery workflows.
How often is IaC coverage analyzed?
Cloud2Gether can analyze connected environments through recurring daily executions and on-demand runs. Each execution refreshes coverage, drift and unmanaged-resource signals using the latest available environment state.
IaC Hub
Make IaC coverage
visible and actionable
Measure what is codified. Find what drifted. Surface what remains unmanaged. Give the team a prioritized next step.
Read-only analysis. Your team controls every infrastructure change.