Hi PH Community! Infrastructure as code (IaC) often fails during deployment due to dynamic constraints such as name collisions, quota limits and other resource-specific constraints that devs run halfway into an IaC deployment. We witnessed this first hand at TinyStacks and built precloud - an open-source framework to define and run dynamic tests before IaC deployments. The precloud framework currently supports Terraform and AWS CDK with several default checks (unique names, service quota checks and more) and ability to define your own! Use Cases: 1. Harden your deployments. Ensure that you haven't defined resources that already exist so that you don't have to fail during deployments. 2. Enforce organizational resource patterns. Use resource checks to ensure resources are named and tagged correctly. 3. Maintain security standards. Use template check plugins to make sure that you're not launching things outside of VPCs, leaving public IPs open, or allowing global access to S3 buckets. Head to our GitHub repo and give it a try https://github.com/tinystacks/precloud!

precloud - Dynamic tests for infrastructure-as-code

Open source. No more mid-deployment IaC failures.

Open source. No more mid-deployment IaC failures.

precloud - Dynamic tests for infrastructure-as-code

Open source. No more mid-deployment IaC failures.

Open source. No more mid-deployment IaC failures.

Similar Products

Do you use precloud - Dynamic tests for infrastructure-as-code?

Do you use precloud - Dynamic tests for infrastructure-as-code?

You might also like