LocalStack for Azure Enters Public Preview with Security Settings Stored but Not Enforced
LocalStack has opened its Azure emulator to a free public preview, running Azure services locally and accepting existing ARM, Bicep, and Terraform without rewrites. Its own documentation reports partial operation coverage per service and a consistent pattern: configuration is stored and returned, while enforcement of access restrictions, TLS, and network rules is not implemented. By Steef-Jan…
LocalStack, an open-source project led by former Microsoft engineer Paolo Salvatori, has entered public preview for Azure with its emulator offering a self-serve environment for developers to test applications without waiting for a dev subscription or paying for each iteration. The emulator runs Azure services on a developer machine, accepting existing ARM and Bicep templates, Terraform modules, Pulumi programs, and Azure CLI scripts without the need for rewrites.
The service list is broad, covering various Azure offerings such as AKS, Container Apps, Functions, App Service, Cosmos DB, Service Bus, Event Hubs, Key Vault, App Configuration, Managed Identity, API Management, and more. However, the fidelity of emulation varies across resources, with some resources like App Service not enforcing security settings such as keys, access restrictions, authentication settings, publishing credential policies, httpsOnly, custom host-name bindings, VNet integration, backup configuration, and more.
Networking components like Virtual Network, peering, VPN gateways, ExpressRoute circuits, Load Balancer, Application Gateway, and Network Watcher are also not implemented. Despite these limitations, LocalStack aims to provide an isolated sandbox for development and testing purposes, positioning itself as a tool for developers to identify potential issues early in the development cycle.
Brief written by urgent.news from InfoQ's own syndicated text. Machine-written — may contain errors; check the original before relying on it.
