Private Cloud Platforms comparison & reviews

3rd 4th 1st
User Reviews
Not Enabled Not Enabled Not Enabled
Analysis expand by Bhagyashri (Shri) Bhagvat by Bhagyashri (Shri) Bhagvat Luciano Taranto
Select All
General expand
  • Fully Supported
  • Limitation
  • Not Supported
  • Information Only
  • + Mature on-prem IaaS solution
  • + High-fidelity implementation of AWS APIs
  • + Proven at scale over years of operation
  • + Strong Storage Capability with Additional Compute and Networking Functionality
  • + Vendor Maturity and Market-share
  • + Simple and Straightforward Editions
  • + True Disconnected Offering of Cloud System
  • + IaaS and PaaS Solution
  • + Enterprise Solution
  • - Recent acquisition concerns
  • - No administrative GUI
  • - Missing features beyond API compatability
  • - Limited Capability
  • - Few Use Cases
  • - Temporary
  • - Disconnected Mode Only Billed as Capacity
  • - New to Market
  • - Closed Solution
Content Creator
Integrated software stack with AWS-compatible IaaS services.
The AWS Snowball Edge is a type of Snowball device with on-board storage and compute power for select AWS capabilities. (see details)
Azure Stack is Microsofts extension of Azure that provides a way to deliver Azure services in an on-premises environment. (see details)
Based on the Eucalyptus code-base that has been in production for over a decade, powering installations beyond 200K cores in size.
Snowball Edge was announced 2016 and builds on AWS which has been around since 2012
Azure Stack was made publicly available June of 2017 and builds off of Azure which has been available since February of 2010
Disconnected Offering
Can be deployed in a disconnected environment
Must connect back to AWS platform for full functionality
Azure Stack can be deployed in disconnected mode
Infrastructure Services expand
Virtual servers
Virtual servers are called cloud instances (equivalent to EC2 instances in AWS)
Virtual servers are called EC2 instances
Azure Stack allows for the deployment of virtual servers called virtual machines
VM Type - General Purpose
Virtual machine hardware can be configured to take full advantage of the underlying hosts hardware. A collection of instance types can be customized in terms of vCPUs, memory, and disk.
The SBE1 EC2 instance is the general purpose offering
General purpose VMs are Basic A, Standard A, Av2-series, D-series, DS-series, Dv2-series, DSv2-series
VM Type - Compute Optimized
Compute-optimized instance types can be customized by modifying the instance type
The SBE-C EC2 instance is the compute optimized offering
Computed optimized VMs are F-series, Fs-series, Fsv2-series
VM Type - Memory Optimized
Memory-optimized instance types can be customized by modifying the instance type
There is no memory optimized offering
Memory optimized VMs are D-series, DS-series, Dv2-series, DSv2-series
VM Type - Accelerated (GPU)
GPU instance types can be customized through advanced configuration only. No official documentation.
The SBE-G EC2 instance is the accelerated GPU offering
There are no accelerated VM offerings with a GPU
Metadata URL
Metadata URL, featuring EC2-compatible information and thus compatible with cloud-init, is reachable from instances.
You get access to a subset of metadata typically available to EC2 instances through an internal URL
While Azure has an Instance Metadata service, this functionality is not currently supported on Azure Stack
Rapid Provisioning
System components enable fast provisioning, particularly of EBS-backed instances.
You can specify the job and resources and Amazon will configure the device for you and ship it out to you
You can easily and quickly deploy virtual machines using the Azure Stack console
Resize existing VM
EBS-backed instances can be resized after stopping by modifying InstanceType attribute via ModifyInstanceAttribute request (in CLI or Console).
Typically resize an instance using CLI modify-instance-attribute on instanceType attribute but Snowball Edge only allows you to modify userdata
This functionality is supported in Azure Stack as well
Resource Management
Resources can be managed from either the Console or CLI/API
Resources such as EC2 instances cannot be managed through the console after the device is created and must instead be managed through the CLI/API adding a level of complexity
The Azure Resource Manager provides a platform to manage all resources deployed within the Azure Stack
AWS AutoScaling APIs are supported, with performance-based triggers for up- and down-scaling.
A cluster of 5-10 Snowball Edges can be created to offer increased durability and locally scale up or down storage on demand
Azure Stack includes scale sets which allow for automatic scaling of instances based on load
VM Imaging
Images (akin to AMIs and AKIs) can be created and shared with other cloud users. Existing instances can be saved into an image.
No mention in the developer guide
You can create and publish a custom marketplace item
VM Import/Export
Instances can be imported using raw disk or VHD formats. Exports done manually at hypervisor level. No API support for the operation exists.
No mention in the developer guide
You can import and export a disk used by a VM. In addition, you may be able to import/export a VM state but this is not confirmed (see details)
VM live migration
VMs can be live-migrated using CLI / API. In the event of a host failure instances to not automatically restart.
AWS does not support live VM migration and as such we shouldnt expect Snowball Edge to do this
Azure Stack supports live VM migration as a preventative measure to protect resources from failing hardware
VM to host affinity
Not supported. Can only be achieved by backend administration using instance migration.
When deploying a cluster, you can select which nodes an instance runs on
This capability is not supported by Azure Stack
VM to host anti-affinity
Not supported. Can only be achieved by backend administration using instance migration.
When deploying a cluster, you can select which nodes an instance runs on thus also choosing which nodes it does not run on
Azure Stack provides Availability Sets which replicate the VM across different hosts for high availability thus enforcing host anti-affinity
Cloud virtual networking
Overlays a virtual network on top of your existing network. Supports EDGE (EC2 Classic) and VPCMIDO (AWS VPC) modes.
The EC2 instances can have virtual network interfaces attached to them which allows them to communicate with each other and outside devices
The Network Resource Provider delivers a series of Software Defined Networking (SDN) and Network Function Virtualization (NFV) features
Cross-premises connectivity
Support for AWS VPN Gateway is available but only when using VPCMIDO network mode.
The Snowball Edge connects into the datacenter and allows for transfer of data between the datacenter and AWS albeit in a slow snail-mail fashion
Cross-premises connectivity can be established in Azure Stacks which are deployed in the connected mode
DNS hostname resolution
DNS names for VM instances is supported automatically
No mention in the developer guide
Azure Stack supports DNS hostname resolution
DNS zone management
No mention in the documentation
No mention in the developer guide
Azure Stack supports the creation and management of DNS zones and records using both the console and the API
IP reassignment
Elastic IP and Elastic Network Interface functionality enables flexible IP address assignment.
You can delete the virtual network interface attached to an EC2 instance and then create a new virtual network interface for that EC2 instance with a new static IP address
You can reassign an IP by modifying the virtual network interface or by deleting it and creating a new one (Experience)
Load balancing
Elastic Load Balancer is an included service.
No mention in the developer guide
The Azure Stack provides load balancing functionality
Network Interfaces
Elastic Network Interface functionality allows attaching and detaching of virtual NICs to instances
The device has a set of external network interfaces for connectivity into the customer datacenter (see details)
You can create and modify network interfaces attached to virtual machines (Experience)
Outbound Network Connectivity
Can be configured to connect to external networks with both EDGE (EC2 Classic) and VPCMIDO (Amazon VPC) networking modes.
The device has a set of external network interfaces for connectivity into the customer datacenter (see details)
The Azure Stack is integrated into the customers datacenter and has outbound network connectivity to the customers border
Public IP Address
Public IP addresses can be assigned to instances either automatically or from a pool of Elastic IP addresses.
Can attach a virtual network interface to your EC2 instance and specify a public IP address for use
Azure Stack supports IPv4 public addresses
SR-IOV support
Can be customized to use SR-IOV for instance networking by advanced configuration only. No official documentation.
No mention in the developer guide
No mention of this capability for Azure Stack
VM Security Groups
Instances can be added to a security group which has a specific network security policy applied to it.
Security groups exist and can be configured for EC2 instances similar to the way they work in AWS with limitations
VM Security groups are provided as network security groups
Virtual Network Peering
Ability to create a peering connection between two VPCs is supported.
Virtual Private Clouds (VPCs) are not supported in Snowball Edge and thus you cannot make virtual networks to peer
Not supported as of 20190124
Object storage
Supports S3-compatible object storage using its Object Storage Gateway (OSG)
The Snowball Edge supports S3 (object storage) as its primary purpose is downloading customer data from a remote datacenter which can then later be transferred to S3 in AWS
Azure Stack provides blob storage for object storage
Block storage
Elastic Block Storage (EBS) provides block-level storage volumes that you can attach to instances.
Block storage must exist as the Snowball Edge is capable of hosting EC2 instances but end-users have no access to block storage and cannot attach volumes themselves to EC2 instances
Azure Stack supports page blobs which are the equivalent of block storage
Shared file storage
Shared file storage is not supported.
Once connected to the datacenter, the S3 Adapter for Snowball or NFS mount point can be used to upload data from the datacenter into the Snowball Edge
Azure Stack does not provide a SMB or NFS solution
Procedures for backing up and restoring everything except root disks of instance-store (ephemeral) instances are documented.
By its nature, the device offers data backup for data stored within a datacenter albeit in a slower process
Microsoft Azure Backup Server can be used to back up data within Azure Stack (see details)
Local Data Protection
Relies on replication features of underlying software and hardware (RAID and Ceph) for local data protection from hardware failures.
The Snowball Edge employs defense-in-depth for data protection including a ruggedized tamper-reistant enclosure, 256-bit encrpytion, and a TPM
Local data is encrypted and replicated across nodes in case of hardware failure
Remote Replication
No special functionality for automatic remote replication are provided, but backup process can include transfer of backed up data offsite for disaster recovery.