{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/95de3b705786424c9540dce85799853b\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/95de3b705786424c9540dce85799853b-00c72f6db2b0bbb7.gif","duration":301.419,"title":"Deploying Portfolio Website on AWS","description":"This Loom provides a brief rundown of an AWS deployment for a simple HTML portfolio website using CloudFront, S3, Terraform, and GitHub Actions. The speaker explains the project’s Cloud.md setup for new team members, including architecture and CICD workflow, and describes using AWS and Terraform MCP servers for Terraform documentation and up-to-date AWS information. They also cover custom agent workflows for running tasks in parallel such as TF plan, TF plan queue launching, and security audits, along with safety layers like a user prompt submit hook that blocks destructive intent and command tooling and post-tool protections around Terraform plans. The Loom notes local settings.local behavior and that the scaffold terraform command generates Terraform files in the environment, with deploy logs available in dot-close/deploy log."}