# Should I use Terraform, CloudFormation or Helm to install vendor software?

Canonical page: https://launchinyourcloud.com/questions/installation-tools/

Use the method documented and supported for your product, edition and platform: for example CloudFormation, Bicep, Terraform or Helm. Review the artifact and permissions, pin versions, and keep parameters in source control. A template’s existence does not establish support on every cloud.

Answer page: https://launchinyourcloud.com/questions/installation-tools/
Answer reviewed: 2026-11-21

- [Follow the production launch checklist](/guide/launch-checklist/)
- [Understand infrastructure as code](/glossary/#iac)
- [Browse documented install methods](/directory/)


## Match the artifact to the deployment

CloudFormation describes AWS resources, Bicep and ARM target Azure resources, Terraform can provision provider resources, and Helm packages Kubernetes applications. A product can combine tools at different layers. Use the documented combination for the exact edition and provider instead of substituting a tool merely because your team prefers it.

## Review the package as an input to operations

Record the official artifact location, version, required permissions and configurable values. Inspect what it creates and which external services it contacts. Keep reviewed parameters in version control while storing secret values through an appropriate secret-management mechanism.

Test the documented update, rollback or recovery procedure and ownership of changes made after deployment. An unofficial port, generic container image or publicly available template can be useful research material, but does not establish the vendor’s support entitlement or a new provider badge.

