REVIEW 2 cited by
Statically Inferring Usage Bounds for Infrastructure as Code
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
Signed reviews
read the original abstract
Infrastructure as Code (IaC) has enabled cloud customers to have more agility in creating and modifying complex deployments of cloud-provisioned resources. By writing a configuration in IaC languages such as CloudFormation, users can declaratively specify their infrastructure and CloudFormation will handle the creation of the resources. However, understanding the complexity of IaC deployments has emerged as an unsolved issue. In particular, estimating the cost of an IaC deployment requires estimating the future usage and pricing models of every cloud resource in the deployment. Gaining transparency into predicted usage/costs is a leading challenge in cloud management. Existing work either relies on historical usage metrics to predict cost or on coarse-grain static analysis that ignores interactions between resources. Our key insight is that the topology of an IaC deployment imposes constraints on the usage of each resource, and we can formalize and automate the reasoning on constraints by using an SMT solver. This allows customers to have formal guarantees on the bounds of their cloud usage. We propose a tool for fine-grained static usage analysis that works by modeling the inter-resource interactions in an IaC deployment as a set of SMT constraints, and evaluate our tool on a benchmark of over 1000 real world IaC configurations.
Forward citations
Cited by 2 Pith papers
-
A Defect Taxonomy for Infrastructure as Code: A Replication Study
A replication of the 'Gang of Eight' defect taxonomy finds the same eight defect categories in code-based IaC tools and corporate repositories, with configuration-data mistakes most frequent.
-
Using a Feedback Loop for LLM-based Infrastructure as Code Generation
Feeding cfn-lint errors back to an LLM reduces CloudFormation template errors for a few rounds, but the improvement plateaus by roughly the fifth iteration.
Discussion (0). Continue with ORCID to comment.