ipa-destroy

Execute Makefile-driven teardown targets to delete composed CloudFormation stacks.

1|1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/aws-samples/sample-innovation-patterns --skill ipa-destroy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ipa-destroy
Source: https://github.com/aws-samples/sample-innovation-patterns/tree/main/.claude/skills/ipa-destroy
Command: npx skills add https://github.com/aws-samples/sample-innovation-patterns --skill ipa-destroy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the risk and complexity of cleaning up an already-deployed IPA full-stack pattern by turning “destroy my stacks” into a validated, status-aware, and repeatable teardown process.

Core Features & Use Cases

  • Validated prerequisites: Confirms .env, required variables, AWS credentials, and generated Makefiles are present before any destructive actions.
  • Status-aware teardown plan: Detects which CloudFormation stacks exist, shows what will be deleted vs. skipped, and highlights data-loss warnings.
  • Double confirmation safety: Requires an initial yes/no confirmation and a second typed namespace confirmation to reduce accidental destruction.
  • Idempotent deletion with verification: Executes the aggregate teardown target from generated Makefiles, then verifies stacks are fully deleted and reports remaining failures if any.
  • Preserves non-target infrastructure: Keeps the security stack and prepare stacks intact, focusing on the composed pattern teardown.

Quick Start

Run /ipa-destroy and follow the prompts to plan the teardown, confirm twice, and delete the composed infrastructure using the generated Makefile targets.

Frequently Asked Questions about ipa-destroy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely tear down AWS CloudFormation stacks for a serverless web app?

To safely tear down AWS CloudFormation stacks, you can execute a validated teardown process that checks stack statuses, requires double confirmation, and runs Makefile-driven AWS CLI delete-stack commands with post-deletion verification.

What is the best way to clean up IPA infrastructure after a partial deployment failure?

Cleaning up IPA infrastructure after a partial failure involves running an idempotent teardown process that detects existing stacks, skips missing ones, and safely re-runs deletion targets to recover from incomplete deployments.

Do I need a .env file and AWS credentials to delete composed infrastructure patterns?

Yes, deleting composed infrastructure patterns requires validated prerequisites including a .env file with required variables, active AWS credentials, and generated Makefiles to ensure authorized and targeted teardown.

Can I delete only the composed pattern stacks while preserving the security stack?

Yes, you can delete only the composed pattern stacks while preserving non-target infrastructure like the security and prepare stacks, ensuring the teardown focuses strictly on the serverless application composition.

How does double confirmation prevent accidental destruction of CloudFormation stacks?

Double confirmation prevents accidental destruction by requiring an initial yes/no prompt followed by a typed namespace confirmation, ensuring deliberate user consent before executing any irreversible AWS CLI delete-stack operations.

Why does my infrastructure teardown report remaining failures after stack deletion?

Infrastructure teardown reports remaining failures when post-verification detects CloudFormation stacks that are not fully deleted, indicating that the idempotent deletion process encountered issues requiring further investigation.