BuildWithAI: What Broke, What I Learned, What's Next
Overview The architecture and the prompts are covered. Now for the part that usually gets left out: what actually broke, what could be better, and how to deploy the whole thing on your own AWS acco...

Source: DEV Community
Overview The architecture and the prompts are covered. Now for the part that usually gets left out: what actually broke, what could be better, and how to deploy the whole thing on your own AWS account. So far we've gone through the serverless stack and 5-layer cost guardrails, then the system prompt pattern and the prompt engineering behind all six tools. This final part is the practical side — the gotchas from development and a step-by-step guide so you can fork the repo and get it running yourself. Things that broke Bedrock model access First deploy went fine. Lambda functions created, API Gateway live, DynamoDB provisioned. Then the first endpoint returned access denied from Bedrock. No helpful error message, just a generic denial. The issue: when I first deployed this using Claude Sonnet & Haiku, model access had to be enabled manually before you could call the model. It's a one-time step. I initially assumed it was an IAM policy issue and spent time debugging the wrong thing.