| title | Only Cloud Single Node Cluster Blueprint | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| description | Deployment of cloud components required for Azure IoT Operations with single-node VM host, preparing cloud infrastructure without edge component installation | |||||||||
| author | Edge AI Team | |||||||||
| ms.date | 2025-06-07 | |||||||||
| ms.topic | reference | |||||||||
| keywords |
|
|||||||||
| estimated_reading_time | 2 |
This blueprint provides a deployment of the cloud components required for Azure IoT Operations (AIO) along with a single-node VM host. Unlike the full blueprint, this version only deploys the cloud resources and VM infrastructure, without installing the Kubernetes cluster or AIO components on the edge. This is ideal for scenarios where you want to prepare the cloud infrastructure first and handle the edge components separately or through a different process.
Please follow general blueprint recommendations from blueprints README.md.
This blueprint deploys:
- A Linux VM host in Azure
- Resource Group for all resources
- Security and Identity resources (Key Vault, Managed Identities)
- Data storage components
- All cloud prerequisites for later AIO installation
The resulting architecture provides the cloud infrastructure needed for an Azure IoT Operations deployment, ready for subsequent edge component installation.
This blueprint is currently available in:
- Bicep - Infrastructure as Code using Azure Bicep
Future implementations may include Terraform support.
This blueprint consists of the following key components:
- Main Template (
bicep/main.bicep): The primary deployment template that orchestrates the overall solution - Types Definition (
bicep/types.core.bicep): Defines core parameter types and structures used throughout the deployment
| Module | Purpose | Source Location |
|---|---|---|
cloudResourceGroup |
Creates the resource group | ../../../src/000-cloud/000-resource-group/bicep |
cloudSecurityIdentity |
Sets up security and identity resources | ../../../src/000-cloud/010-security-identity/bicep |
cloudData |
Creates data storage resources | ../../../src/000-cloud/030-data/bicep |
cloudVmHost |
Provisions the VM host | ../../../src/000-cloud/051-vm-host/bicep |
Beyond the basic required variables, this blueprint supports advanced customization:
| Variable | Description | Default | Notes |
|---|---|---|---|
common.environment |
Environment type | Required | "dev", "test", "prod", etc. |
useExistingResourceGroup |
Use existing resource group | false |
When true, looks up a resource group instead of creating it |
resourceGroupName |
Name of existing resource group | Generated | When empty, name is generated from common parameters |
common.resourcePrefix |
Prefix for resource naming | Required | Short unique alphanumeric string |
common.location |
Azure region location | Required | "eastus2", "westus3", etc. |
common.instance |
Deployment instance number | "001" |
For multiple deployments |
adminPassword |
A password for SSH to the VM | Required | Important: always pass this inline, never store in .bicepparam |
For additional configuration options, review the parameters in main.bicep.
Ensure you have the following prerequisites:
- Registered resource providers (see deployment instructions)
- Appropriate permissions to create resources
Follow detailed deployment instructions from the blueprints README.md, Detailed Deployment Workflow
- Full Single Cluster: Complete deployment including edge components
- Full Multi-node Cluster: Multi-node high-availability deployment
- Only Edge IoT Ops: Deploy only the edge components assuming cloud infrastructure exists
🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.