IaC status
IaC status compares your cloud assets to the IaC state file.
Last updated
IaC status compares your cloud assets to the IaC state file.
Last updated
IaC Status | Description |
---|---|
Unmanaged assets exist in an integrated provider (e.g., cloud account) but not in an available IaC state file. These assets were most likely created manually using ClickOps. | |
Codified assets are managed by IaC. Their configuration is in sync with the cloud and IaC state. | |
Drifted assets contain an asset configuration that deviated from the original IaC deployment, creating a discrepancy between the cloud and the IaC. Drift occurs when a user changes the configuration manually using ClickOps, or when a third party makes changes to the configuration in the cloud. | |
Ghost assets are a subset of drifted assets. Ghosts typically occur when the user is using IaC to provision infrastructure, but the user is manually removing the IaC stack without using the IaC destroy function. | |
Child assets are assets that are managed by their parent object. For example, EBS created by EC2. | |
Pending is a temporary status. Firefly is scanning this asset to determine its IaC status. | |
IaC-Ignored assets are not calculated in the IaC coverage metric. They are commonly used as default assets, such as default VPC and default subnet. | |
Firefly identified this asset in your IaC stack; however, we currently do not support cloud scanning for this resource type. The IaC status might be Codified, Drifted, or Ghost. |
Drifted and Codified assets are also called managed assets.