Skip to content
Beta

AWS and Azure Target Service Mappings

Last updated on

Use these mappings to create an initial target design for workloads moving from AWS or Azure to STACKIT. The tables cover the full STACKIT service portfolio, not only the services typically used in a landing zone foundation, so they also apply to application, data, and platform migrations that go beyond the initial landing zone. Confirm the application architecture, data profile, availability needs, integration contracts, and operating model for every workload before approving a migration wave.

For AWS and Azure landing zones, STACKIT provides a structured migration path that maps account and subscription structures, network segmentation, identity and access controls, security policies, logging, monitoring, and governance guardrails into a STACKIT landing zone before application migration waves begin. The STACKIT Landing Zone Accelerator provides a reusable, automated foundation for establishing these target controls consistently and at scale.

Start with the Landing Zones overview to establish the platform baseline before workload migrations begin.

Developer platform and infrastructure tooling

Section titled “Developer platform and infrastructure tooling”
  1. Classify the workload with the Workload Migration Use Cases.
  2. Select the target services and record the required data, identity, network, security, and operations patterns.
  3. Choose the appropriate R-strategy and define the migration runbook.
  4. Validate the target design against the landing-zone baseline before scheduling the workload into a migration wave.