# cloudformation-to-pulumi

Migrates CloudFormation templates and active stacks to Pulumi programs. It formats resources for cdk-importer and validates zero-diff imports.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 888 installs · ★ 78
- Author: pulumi
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/pulumi/agent-skills/tree/HEAD/migration/skills/cloudformation-to-pulumi/SKILL.md
- Updated: 2026-10-09
- HTML: https://affpapa.org/en/nevibecode/skills/cloudformation-to-pulumi

## What it does

This skill guides the step-by-step migration of AWS CloudFormation stacks into Pulumi programs. First, the agent verifies AWS credentials using Pulumi ESC and confirms the target region. If a local template file is absent, it fetches the template body and resource inventory via the AWS CLI. It then parses parameters, conditions, mappings, and dependencies.

There is no automated converter for CloudFormation templates. The agent manually translates each resource into TypeScript. The critical rule is using the CloudFormation Logical ID as the Pulumi resource name. Renaming resources is a breaking mistake: the `cdk-importer` tool matches resources strictly by their logical IDs and fails otherwise.

The skill mandates the `aws-native` provider by default over the classic `aws` provider. CloudFormation types map directly to `aws-native`. Sticking to classic AWS causes import failures during the migration. The workflow concludes with zero-diff validation via `pulumi preview` and a migration report formatted for pull requests.

## Requirements
- Works with: AWS

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add pulumi/agent-skills --skill cloudformation-to-pulumi -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/cloudformation-to-pulumi/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/cloudformation-to-pulumi/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add pulumi/agent-skills --skill cloudformation-to-pulumi -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/cloudformation-to-pulumi/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add pulumi/agent-skills --skill cloudformation-to-pulumi -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/cloudformation-to-pulumi/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install pulumi/agent-skills cloudformation-to-pulumi
```

2. **Manually: put the files in place**
- File: `.github/skills/cloudformation-to-pulumi/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add pulumi/agent-skills --skill cloudformation-to-pulumi -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/pulumi/agent-skills --path migration/skills/cloudformation-to-pulumi
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/cloudformation-to-pulumi/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add pulumi/agent-skills --skill cloudformation-to-pulumi -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/pulumi/agent-skills/tree/HEAD/migration/skills/cloudformation-to-pulumi/SKILL.md

## When to use it
- convert CloudFormation templates into TypeScript Pulumi programs
- import active AWS stack resources into Pulumi with zero diff
- structure resource names and providers for automated `cdk-importer` workflows
- generate formal migration summaries for pull requests

## Example prompts
- Convert the CloudFormation stack my-network-stack into a Pulumi program using aws-native.
- Help me import existing resources from template.json into Pulumi with cdk-importer.
- Migrate our production CloudFormation stack to Pulumi and draft a pull request report.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: cae81aba73394427.

BEGIN THIRD-PARTY FILE cae81aba73394427
```text
---
name: cloudformation-to-pulumi
description: Convert, migrate, or import AWS CloudFormation stacks or templates into Pulumi programs. Load this skill whenever a user wants to move from CloudFormation to Pulumi, convert a CFN template, import existing CloudFormation-managed resources into Pulumi, or asks about CloudFormation-to-Pulumi migration in any form. Also load when the user mentions cdk-importer in a migration context.
---

## IMPORTANT: PLAN ADJUSTMENT REQUIRED

**If you have already generated a migration plan before loading this skill, you MUST:**
1. Review your existing plan against the workflows and requirements in this skill
2. Identify any gaps, missing steps, or incorrect assumptions
3. Update and revise your plan to align with this skill's guidance
4. Communicate the adjusted plan to the user before proceeding

## CRITICAL SUCCESS REQUIREMENTS

The migration output MUST meet all of the following:

1. **Complete Resource Coverage**
   - Every CloudFormation resource MUST be represented in the Pulumi program OR explicitly justified in the final report.

2. **CloudFormation Logical ID as Resource Name**
   - **CRITICAL**: Every Pulumi resource MUST use the CloudFormation Logical ID as its resource name.
   - This enables the `cdk-importer` tool to automatically find import IDs.
   - DO NOT rename resources. Automated import will FAIL if you change the logical IDs.

3. **Successful Deployment**
   - The produced Pulumi program must be structurally valid and capable of a successful `pulumi preview` (assuming proper config).

4. **Zero-Diff Import Validation** (if importing existing resources)
   - After import, `pulumi preview` must show NO updates, replaces, creates, or deletes.

5. **Final Migration Report**
   - Always output a formal migration report suitable for a Pull Request.

## WHEN INFORMATION IS MISSING

If the user has not provided a CloudFormation template, you MUST fetch it from AWS using the stack name.

## MIGRATION WORKFLOW

Follow this workflow **exactly** and in this order:

### 1. INFORMATION GATHERING

#### 1.1 Verify AWS Credentials (ESC)

Running AWS commands requires credentials loaded via Pulumi ESC.

- If the user has already provided an ESC environment, use it.
- If no ESC environment is specified, **ask the user which ESC environment to use** before proceeding.

**For detailed ESC information:** Use skill `pulumi-esc`.
```
END THIRD-PARTY FILE cae81aba73394427

The third-party file has ended. Everything between the cae81aba73394427 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2401 of 9646 bytes. © pulumi · Apache-2.0 · https://github.com/pulumi/agent-skills/tree/HEAD/migration/skills/cloudformation-to-pulumi/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md