cloudformation-to-pulumi

To convert an AWS CloudFormation template to Pulumi, this Skill automates resource conversion into a Pulumi program, prioritizing the aws-native provider for direct mapping. It guides you through mapping intrinsic functions and manual resource conversion.

Yes, you can import existing CloudFormation resources into Pulumi state without causing changes. The Skill guides you through automated resource import using cdk-importer and ensures zero-diff import validation for deployments.

The best way to migrate CloudFormation stacks to Pulumi infrastructure as code is using this conversion Skill. It translates templates into Pulumi TypeScript programs while ensuring critical requirements like resource name consistency are met.

Yes, the CloudFormation to Pulumi conversion supports intrinsic functions. The Skill explicitly guides users through intrinsic function mapping to ensure the translated Pulumi program accurately reflects the original template logic.

Your imported CloudFormation stack shows a diff in Pulumi because resource name consistency or zero-diff import validation requirements were not met. The Skill enforces these critical checks during the automated resource import process to prevent drift.

You need the aws-native provider because the Skill prioritizes it for direct resource mapping during CloudFormation conversion. This ensures the generated Pulumi program accurately maps to your existing AWS infrastructure components.