What problem does it solve? Configuring AWS Amplify environment variables and debugging failed builds normally requires manual work in the Amplify Console. This Skill lets an AI agent set, update, or remove env vars, trigger redeploys, poll build status, and fetch build, access, and compute logs directly through Buildpad platform MCP tools. ## Core Features & Use Cases - Env Var Management: Read existing key names, then atomically set, update, or remove variables with amplify_set_env_vars, which merges changes into the full env var map. - Deployment Lifecycle: Trigger redeploys on the main branch, poll job status every 30-60 seconds, and retrieve per-phase build step details with pre-signed log URLs. - Build & Runtime Diagnostics: Fetch CI build logs (pnpm/next output), HTTP access logs filtered by status code, and CloudWatch Lambda compute logs with case-sensitive filter patterns. - Next.js Runtime Exposure: Write Amplify env vars to .env.production during the build phase via amplify.yml echo commands so API routes can read them at runtime. - Use Case: A Next.js API route fails because EXTERNAL_BUCKET_NAME is missing at runtime. The agent sets the var, updates amplify.yml, redeploys, polls the job, and pulls the CI build log when the build fails. ## Quick Start Ask the agent to list the current Amplify environment variables, add a new variable, redeploy the app, and report the build result.
