AWS TO STACKIT

AWS to STACKIT migration

Replace service-name guesswork with an engineering plan. StackToIT reads your AWS Terraform, decides the treatment of every resource and writes the STACKIT target, the Terraform draft and the migration sequence.

Your AWS estate, resource by resource

AWS offers specialized services that rarely have a one-to-one counterpart. What decides the effort is how each resource is configured and what depends on it, so that is what StackToIT reads.

  1. Reads the whole estate

    Terraform and OpenTofu root modules, child modules and variables, with resources from both the AWS and the AWS Cloud Control providers.

  2. Maps by behavior

    Each resource gets a treatment and a stated reason. An S3 bucket can stay direct while one setting forces a reconfiguration, and the report tells you which one.

  3. Writes the package

    STACKIT Terraform draft, architecture diagrams, ordered execution plan, data movement and a decision list for your architects.

Where your services go

Typical outcomes from the StackToIT knowledge base. The treatment of each resource depends on its configuration, and the report states the reason.

AWSSTACKIT targetTreatment
Amazon EC2STACKIT Compute EngineReconfigure
Amazon EKS, Amazon ECSSTACKIT Kubernetes Engine (SKE)Replatform
Amazon RDS, AuroraPostgreSQL Flex, MariaDB, SQLServer FlexReplatform
Amazon S3STACKIT Object StorageDirect or Reconfigure
ElastiCacheKey Value Store (Valkey)Reconfigure or Replatform
OpenSearch ServiceSTACKIT OpenSearchReplatform
Amazon SQSSTACKIT RabbitMQReplatform
AWS LambdaSTACKIT Cloud FoundryContainerize
DynamoDBMongoDB Flex or PostgreSQL Flex (JSONB)Redesign

What it gives the business

  1. A budget based on real work

    See early which workloads only need configuration and which, like DynamoDB or Lambda, need a data model or runtime change. That split drives effort and timeline.

  2. Costs with no hidden gaps

    Priced lines come from the AWS Price List and the public STACKIT price list. A line with no price is named, with the reason.

  3. Evidence before a pilot

    Read the complete public AWS Retail Store run: 282 Terraform resources analyzed and 44 migration units identified, with the full report, diagrams and Terraform.

The Retail Store run shows what StackToIT produced for one public project. Your own run gives the result for your estate.

Planning a migration to STACKIT?

Let's explore how StackToIT can help assess your infrastructure and prepare a structured migration plan.