Overview
If you provision Azure resources with an Infrastructure as Code (IaC) tool today, you can keep using the same templates, modules and stacks with the LocalStack Azure emulator. These tools all create resources through Azure Resource Manager, and the emulator implements Resource Manager, so each tool only needs to be pointed at the emulator:
| Tool | How it targets the emulator |
|---|---|
| ARM templates and Bicep | The Azure CLI, after lstk az start-interception |
| Terraform | metadata_host in the azurerm provider, after lstk az start-interception |
| Pulumi | metadataHost and disableInstanceDiscovery in the azure-native provider |
| Azure Developer CLI | The azdlocal wrapper |
Terraform and Pulumi read the emulator’s endpoints from the metadata document that it serves at
/metadata/endpoints. For the endpoint values and the credentials that the emulator accepts, see
Credentials.
ARM Templates
Deploy Azure Resource Manager (ARM) templates to the LocalStack Azure emulator with the Azure CLI.
Azure Developer CLI
Deploy Bicep templates to the LocalStack Azure emulator with the Azure Developer CLI (azd).
Bicep
Deploy Bicep templates to the LocalStack Azure emulator with the Azure CLI.
Pulumi
Use the Pulumi Infrastructure as Code framework with LocalStack for Azure.
Terraform
Get started with the `terraform` tool on LocalStack.