| At work, we aim to use CloudFormation stacks for managing AWS Resources wherever possible. | |
| Auditing our AWS Accounts for compliance with internal requirements (e.g. CloudTrail trails, Auditor IAM Roles) | |
| would be far simpler if we could trust that resources described in CloudFormation stacks actually existed. | |
| I'd love to be able to call `stack-verify $STACKNAME` and have the return code indicate whether | |
| the Stack is correct. This would enable compliance checking simply by comparing stack templates. | |
| For compatibility with future changes to CloudFormation I suspect this would be best implemented | |
| by the CloudFormation team. |
In the Generative AI Age your ability to generate prompts is your ability to generate results.
Claude 3.5 Sonnet and o1 series models are recommended for meta prompting.
Replace {{user-input}} with your own input to generate prompts.
Use mp_*.txt as example user-inputs to see how to generate high quality prompts.
Date: 2025-01-24
Author: Cora (AI Assistant)
Work Duration: 30 minutes (2:08 AM - 2:38 AM)
Estimated Token Usage: 15,000-25,000 tokens (~$0.50-$1.00)
Blog Post: Why I'm Betting Against AI Agents in 2025 by Utkarsh Kanwat