Creates test stacks, analyzes CloudFormation events, and compares actual vs documented update behavior to validate whether resource property changes trigger replacement or in-place updates. Use when: a user wants to test if a CFN property change causes resource replacement; when investigating stack update behavior or "Update requires" documentation accuracy; when validating whether a workaround (e.g. hash-based logical IDs) is actually necessary; when questioning UpdateRequiresReplacement behavior for immutable properties; when empirical evidence is needed before an architectural decision involving CDK or CloudFormation stack updates.
Does it follow best practices?
Evaluation — 100%
↑ 1.12xAgent success when using this tile
Validation for skill structure
Your cost optimization team wants to change a DynamoDB table from STANDARD to STANDARD_INFREQUENT_ACCESS table class to reduce costs. However, they're concerned this might cause table replacement and data loss. The AWS documentation needs to be validated through actual testing.
You have a test environment with a simple DynamoDB table already defined in CDK. Your task is to document the exact command sequence and event inspection process needed to validate this change safely.
Create a bash script execute-validation.sh that contains the complete command sequence for:
The script should include comments explaining each step and what to look for. Use placeholder stack names like <test-stack-name> where appropriate.
Also create a file event-analysis.md that explains:
The script doesn't need to execute (use echo for AWS commands if you prefer), but should demonstrate knowledge of the correct commands and flags.