Virtual Machines

This page describes how Virtual Machines maps to services in the environment where the application runs. Some profiles adapt origin API calls; others translate infrastructure or document target-native behavior.

​

Supported environments

API means the profile adapts origin API behavior. Infrastructure means the profile changes provisioned resources or documents a target-native alternative without promising an origin API endpoint. Check the operation and capability tables for the behavior your application depends on.

​

How the targets compare

Each row compares a capability of Virtual Machines with its adaptation on each target. A dash means this profile does not state the capability for that target.

​

Cloud Adapter

​

On AWS

​

EC2 Instances

An Azure virtual machine becomes an EC2 instance with a network interface, operating-system disk, mapped capacity and a target-compatible image. Boot settings are adapted for that image. For Azure client libraries using managed identity, the adapter serves the Azure metadata endpoint and identity token inside the guest.

​

Runtime management

Azure lifecycle requests go to the adapter, which saves the requested configuration and creates or updates the target VM and network resources. A request can be accepted while the cloud is still applying it. Poll the Azure-facing provisioning state before treating the machine as ready.

​

Guest startup and identity

The guest must boot an appropriate target image, run its startup configuration, and reach the expected identity endpoint. The in-guest adapter answers Azure managed-identity requests, while the adaptations for the services the application calls handle those credentials. Check disk contents and application startup separately from VM creation.

​

Compatibility differences

VM extensions become instance startup configuration, which requires acknowledgement at build time. Dynamically allocated public addresses are rejected because this mapping does not reproduce their allocation on start and release on stop.

​

On Google Cloud

​

Compute Engine

An Azure virtual machine becomes a Compute Engine instance with a network interface and boot disk. The adapter serves the Azure metadata endpoint and managed-identity token inside the guest for client libraries that use them.

​

Runtime management

Azure lifecycle requests go to the adapter, which saves the requested configuration and creates or updates the target VM and network resources. A request can be accepted while the cloud is still applying it. Poll the Azure-facing provisioning state before treating the machine as ready.

​

Guest startup and identity

The guest must boot an appropriate target image, run its startup configuration, and reach the expected identity endpoint. The in-guest adapter answers Azure managed-identity requests, while the adaptations for the services the application calls handle those credentials. Check disk contents and application startup separately from VM creation.

​

Compatibility differences

A reachable public address requires an access configuration on the target interface, which this mapping does not configure. The build flags VMs that need that public address. This exclusion concerns public addressing, not all outbound Internet traffic. Dynamically allocated addresses are also rejected: the mapping cannot reproduce their allocation on VM start and release on stop, and does not substitute a reserved address.

​

Existing data and credentials

Selecting a backend does not copy existing data, credentials or access policies. Plan and verify migration separately before changing an application’s endpoint. Do not assume an identifier, credential or encrypted value from the origin service works unchanged on the target.

​

Configure, tune and debug

Start with setup and configuration. Use tuning to understand supported request tags, debugging to investigate a request, and High Fidelity Cloud Emulators to validate a bounded reproduction.