Originally published on moveinfra.eu .

To scan your Terraform setup for cloud lock-in before a migration, extract a full list of resource types from your .tf files or state file and group them into three categories: directly portable standards (like virtual machines, PostgreSQL databases, and S3-compatible buckets), managed services that need configuration changes (like message queues and serverless functions), and proprietary services that require application code rewrites (like DynamoDB, Firestore, or BigQuery). Pair this infrastructure audit with a scan of your application dependencies for provider-specific SDKs so you know exactly which engineering teams need to change code before you move to a European cloud provider.

Key takeaways

Terraform does not make your infrastructure portable by default. It standardizes how you write provisioning code, not the underlying cloud APIs.…