> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/guides-and-examples/advanced-guides/infrastructure.md). # Infrastructure as code Release's infrastructure runner applies your infrastructure-as-code (IaC) plans as part of your application's workflows. ## Why use infrastructure as code with Release Release creates Kubernetes clusters in your cloud account (currently AWS or GCP) to host your application's development, staging, and production environments. By deploying your application with Kubernetes, you can start up most of the services you need when the environment is created. But your application may also rely on external services that aren't a good fit for Kubernetes. Stateful services such as databases, file storage, content delivery networks, and DNS configuration are typically provided by cloud providers such as AWS RDS, S3, CloudFront, and Route53. Configuring external services manually each time you create a new environment would slow down your workflow and likely cause your development, staging, and production environments to diverge should you start using different services for different environments. You can use an IaC tool alongside your Release environments to overcome this problem. With minimal configuration, an IaC tool can start, update, and destroy external cloud services for your environments. ## Terraform Terraform is the first IaC tool supported by Release's infrastructure runner, with Pulumi on the roadmap. See our [Terraform with Release](/guides-and-examples/advanced-guides/infrastructure/terraform.md) documentation to start using Terraform for your environments. ## Using Pulumi or other IaC tools If you use an IaC tool besides Terraform, please contact your technical account manager for help. Release's job runners can run any scripts, including IaC runners, during your application's workflows. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.release.com/guides-and-examples/advanced-guides/infrastructure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.