Skip to content
Beta

Provision an Application Landing Zone through Self-Service

Last updated on

Stackit LogoStackit Logo
STACKIT

Provision an Application Landing Zone through Self-Service

Guide Application Owners from a published Configurator template through project ordering, Plan review, deployment, and handover to workload migration.

PLAN

Identify the Workload Needs

Use discovery findings and the chosen migration strategy to identify the project environment, network relationships, service needs, and owning team.

Design and mobilizeLanding zonesApplication Landing Zone In 1 trail

Application landing zones are not designed in isolation. They require validated discovery input for dependencies, data sensitivity, runtime behavior, and operational constraints.

Typical discovery-driven design inputs:

  • Dependency profile: Inbound/outbound communication paths and trust boundaries.
  • Runtime profile: Resource behavior, availability expectations, and scaling characteristics.
  • Data and compliance profile: Classification, retention, and control obligations.
  • Migration strategy fit: Rehost, Replatform, or refactor constraints for each workload.
BASE

Open the Application Workspace

Open the hosted Configurator and establish the context for the work before choosing a configuration or project offering.

Ready to continue: The team knows where it is working, who owns the result, and which delivery workflow to follow.

Open the Configurator
OPS

Understand the Published Offering

Use a published project template as the reviewed platform offering. Identify its version, fixed settings, allowed parameters, and intended target before placing the order.

An immutable template version feeds separate application instances; later versions become explicit new catalog choices
An immutable template version feeds separate application instances; later versions become explicit new catalog choices
AUTO

Select the Offering and Set Project Parameters

An Application Owner selects a published template available in their working environment. They review its platform target and fixed settings, enter the exposed project parameters, and place an order. The order identifies the selected version and the intended application environment.

Decision: Select one offering and version for the intended application environment, then provide the project-specific values.

Use the parameters exposed by the selected template to describe this particular application environment. For example, a finance application may need a clearly named development project before its production environment is delivered.

Output: A complete set of project values reviewed against the selected template version. Use the same identity and environment description in the later workload runbook.

SAFE

Place and Approve the Order

An order turns a reusable catalog offering into a concrete application instance with a traceable delivery record.

  1. Confirm the selected template version and platform target.
  2. Review the project parameters and intended ownership together.
  3. Place the order and follow its configured approval policy.
  4. Continue with the order’s Plan and resource preview.

Output: An identifiable application order binding the selected version, project values, and delivery status. Use that order when following jobs and coordinating the handover.

OPS

Review the Plan and Start Deployment

Review and create the application environment

Section titled “Review and create the application environment”

Follow the order’s Plan and use its resource preview to review the intended application environment before starting Apply.

Decision: Explicitly start Apply of the reviewed saved Plan through the authorized execution path, then follow the job to its result.

Turn the reviewed resource preview into an explicit deployment decision.

  1. Confirm that the saved Plan represents the intended application environment.
  2. Explicitly start Apply through the authorized execution path.
  3. Follow the execution job and record its result against the application order.

Next checkpoint: Validate the project and agreed access, then pass the environment references to the workload delivery team.

SAFE

Validate the Delivered Environment

Accept the delivered environment against the order and the requirements for workload delivery. Application instances have their own lifecycle and state, separate from the shared platform.

Output: An accepted application environment and a handover record the workload team can use without rediscovering the platform decisions.

AUTO

Prepare the Workload Handover

Platform delivery and template publication lead to an application project, a readiness review, workload migration, and operational acceptance

The Application Landing Zone is the target environment for the next delivery stage. Bring its project, network, identity, and service references into the workload runbook. Review workload-specific access, connectivity, observability, and recovery arrangements with the migration team before starting the wave.

For VMware Relocate, connect the prepared environment to the existing VM landing-zone and migration-tool runbooks. For other workload types, use the relevant target architecture and delivery workflow. Keep the environment acceptance and workload acceptance as identifiable milestones with named owners.

VM Application Landing Zone for Relocate
STEP

Connect the Migration Use Case

The Platform Landing Zone supplies organization-wide governance, connectivity, identity, audit, and automation capabilities. The STACKIT Landing Zone Accelerator then creates one Application Landing Zone project for the workload and environment. Security Groups form an explicit manual approval gate before migration tooling or VMs enter that project.

Platform Landing ZoneVM Application Landing ZoneTool and workload contentGovernance and IAMShared connectivity and DNSAudit and automation baselineAccelerator baselineManual gateCoriolis or Hystax AcuraMigrated VMs and volumesGuest metrics, logs, and backupSTACKIT project and RBACRouted network and DNS zoneSecrets Manager and automation identityObject Storage and state bucketObservability endpointSecurity GroupsRule review and approval baseline readyinherit shared route policyinherit guardrailsapproved ingress and egress

The boundary is deliberate:

  • Landing Zone responsibility: Project, roles, routed network, DNS zone, Secrets Manager, Object Storage, automation identity, optional Observability instance, labels, and shared routing.
  • Manual security responsibility: Security Groups and their workload-specific ingress and egress rules are reviewed and created before tool deployment.
  • Workload responsibility: Migration appliances, migrated servers and volumes, guest configuration, application dependencies, backup policies, and telemetry agents.
GOAL

Own and Evolve the Instance

Use instance and job history to retain the relationship between configuration, selected template version, execution, and outcome. Review drift as a separate maintenance activity. Treat a version change as a reviewed delivery decision, and use an explicit deletion workflow when retiring an application environment.

Feed lessons from pilot workloads and migration waves into the next platform configuration and template versions. This closes the loop from platform standards to application delivery and back into continuous improvement.

Outcome: A repeatable lifecycle in which the current environment stays understandable and improvements become reusable for the next application team.

Trail historyAdded Nov 10, 2026LWUpdatedNo updates · 1 bar = 1 week i
Maintainer
LWLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updatesSTACKITwww.linkedin.com/in/lukas-weberruß-a360b081Contributed in STACKIT