Azure Data Box Gateway
On-premises virtual appliance exposing SMB and NFS shares whose contents are written through to Azure Storage.
- Provider
- azure
- Kind
- Edge appliance
- Category
- Compute
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| cloudManaged | boolean | — | no | true | ▸ true |
| connectivity | enum | connected | intermittent | disconnected | no | — | ▸ connected |
| encryptionInTransit | boolean | — | no | true | inherited |
| formFactor | enum | rack | ruggedized | virtual | no | — | ▸ virtual |
| localStorageGib | integer | — | no | — | ▸ 2048 |
| managed | boolean | — | no | false | ▸ false |
| minimumVirtualProcessors | integer | — | no | 4 | inherited |
| offlineMode | boolean | — | no | — | ▸ true |
| shareProtocols | enum | smb | nfs | both | no | both | inherited |
| singleNode | boolean | — | no | true | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
stateful-node-without-zone-redundancy
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "data-box-gateway", component: "azure-data-box-gateway" }Cloud Storage Gatewayalibaba-cloud-storage-gatewaySmart Access Gatewayalibaba-smart-access-gatewayAWS Backup gatewayaws-backup-gatewayAmazon EKS Anywhereaws-eks-anywhereAmazon FSx File Gatewayaws-fsx-file-gatewayAWS IoT Greengrassaws-iot-greengrassAWS IoT Greengrass Version 1aws-iot-greengrass-v1AWS Outposts rackaws-outpostsAWS Storage Gatewayaws-storage-gatewayAKS Edge Essentialsazure-aks-edge-essentialsAzure IoT Edgeazure-iot-edgeAzure IoT Operationsazure-iot-operationsAzure Localazure-localOn-premises data gatewayazure-on-premises-data-gatewayAzure Operator Nexusazure-operator-nexusAzure Stack Edgeazure-stack-edgeAzure Stack Hubazure-stack-hubCloudflare One Appliancecloudflare-one-appliancebalenabalenaGeneric edge applianceedge-applianceKubeEdgekubeedgeOpenYurtopenyurtGoogle Distributed Cloud air-gappedgoogle-distributed-cloud-air-gappedGoogle Distributed Cloud connectedgoogle-distributed-cloud-connectedGateway Applianceibm-gateway-applianceOracle Compute Cloud@Customeroci-compute-cloud-at-customerOracle Compute Cloud@Customer Isolatedoci-compute-cloud-at-customer-isolatedOracle Private Cloud Applianceoci-private-cloud-applianceOracle Roving Edge Infrastructureoci-roving-edgeOracle Roving Edge Classicoci-roving-edge-classic
# yaml-language-server: $schema=../../schema/component.schema.json # Azure Data Box Gateway: a virtual appliance you run on your own hypervisor that exposes SMB and NFS shares # and writes their contents through to Azure Storage ("Microsoft Azure Data Box Gateway overview"). The # specifications table on that page gives a single-node device with a minimum of 4 virtual processors, 8 GB # of RAM and a 2 TB data disk used as a local cache, data in flight encrypted with AES-256, day-to-day # management from the Azure portal, and a disconnected mode for offline upload. schemaVersion: "1" type: "component" id: "azure-data-box-gateway" kind: "edge-appliance" provider: "azure" docs: "https://learn.microsoft.com/en-us/azure/databox-gateway/data-box-gateway-overview" defaults: managed: false cloudManaged: true connectivity: "connected" offlineMode: true formFactor: "virtual" localStorageGib: 2048 properties: shareProtocols: type: "enum" values: ["smb", "nfs", "both"] default: "both" minimumVirtualProcessors: type: "integer" default: 4 encryptionInTransit: type: "boolean" default: true singleNode: type: "boolean" default: true