Agent Plugins for AWSとは

Agent Plugins for AWSとは AWS が公開している,AI エージェント向けの拡張プラグインです.AI に単発でコードを書かせるのではなく「分析 → 構成提案 → コスト試算 → IaC生成 → デプロイ」というワークフローをスキルとして組み込めるのが特徴です.現在はClaude Code と Cursor に対応しています.この記事では Agent Plugins for AWS を Claude Code にインストールしました.

 /plugin marketplace add awslabs/agent-plugins
  ⎿  Successfully added marketplace: agent-plugins-for-aws

❯ /plugin install deploy-on-aws@agent-plugins-for-aw
  ⎿  (no content)

❯ /plugin install deploy-on-aws@agent-plugins-for-aws
  ⎿  ✓ Installed deploy-on-aws. Restart Claude Code to load new plugins.

検証

/deploy-on-aws:deploy を試してみます.デフォルトで用意されている Amplify Hosting で行う Nextjs にデプロイします.その際にかかるコストも出してくれました.AWS を利用するに当たって利用料の試算をしてくれるのは嬉しいですね.

 /deploy-on-aws:deploy

⏺ I'll help you deploy to AWS! Let me first analyze your codebase to understand what we're working with.

⏺ I see you're in your home directory. You have several project directories here. Which application would you like to deploy to AWS? I can see a
  few candidates:

  - blog-app - A blog application
  - my-app / my-react-app - React apps
  - next-market - Possibly a Next.js marketplace
  - go_todo_app - A Go todo application
  - flamboyant-lemur-200 - Unknown project

⏺ User answered Claude's questions:
  ⎿  · Which project would you like to deploy to AWS? → blog-app

⏺ Let me analyze the blog-app project.

⏺ Searched for 1 pattern, read 2 files (ctrl+o to expand)

⏺ Explore(Explore blog-app structure)
  ⎿  Done (15 tool uses · 53.7k tokens · 17s)
  (ctrl+o to expand)

⏺ Good. Here's what I found:

  Analysis: blog-app

  ┌───────────┬────────────────────────────┐
  │ Attribute │           Value            │
  ├───────────┼────────────────────────────┤
  │ Framework │ Next.js 16 (App Router)    │
  ├───────────┼────────────────────────────┤
  │ Language  │ TypeScript                 │
  ├───────────┼────────────────────────────┤
  │ Styling   │ Tailwind CSS               │
  ├───────────┼────────────────────────────┤
  │ API       │ Next.js API Routes (REST)  │
  ├───────────┼────────────────────────────┤
  │ Database  │ In-memory (no external DB) │
  ├───────────┼────────────────────────────┤
  │ Auth      │ None                       │
  └───────────┴────────────────────────────┘

  This is a straightforward Next.js app with server-side rendering and API routes, using in-memory storage.

  Recommended AWS Service: AWS Amplify Hosting

  Why Amplify:
  - Native Next.js SSR support (including API routes)
  - Zero infrastructure management - just connect and deploy
  - Built-in CI/CD, custom domains, HTTPS
  - Pay-per-request pricing is ideal for a dev/blog app
  - No need for containers, load balancers, or Lambda config

  Note: Since your app uses in-memory storage, data resets on each deployment/cold start. This is fine for dev. For persistence, you'd add
  DynamoDB later.

  Let me get you a cost estimate before proceeding.

⏺ plugin:deploy-on-aws:awspricing - get_pricing_service_codes (MCP)(filter: "amplify")
  ⎿  {
       "result": [
         "AWSAmplify"
     … +2 lines (ctrl+o to expand)

⏺ plugin:deploy-on-aws:awspricing - get_pricing (MCP)(service_code: "AWSAmplify", region: "us-east-1", output_options:
                                                     {"pricing_terms":["OnDemand","FlatRate"],"exclude_free_products":false})
  ⎿  {
       "result": {
         "status": "success",
     … +85 lines (ctrl+o to expand)

⏺ Cost Estimate (us-east-1, dev usage)

  ┌──────────────────┬───────────────────┬────────────────────────────┬──────────────┐
  │    Component     │    Unit Price     │      Estimated Usage       │ Monthly Cost │
  ├──────────────────┼───────────────────┼────────────────────────────┼──────────────┤
  │ Build            │ $0.01/min         │ ~15 min (5 builds × 3 min) │ $0.15        │
  ├──────────────────┼───────────────────┼────────────────────────────┼──────────────┤
  │ SSR Requests     │ $0.30/1M requests │ ~10K requests              │ $0.003       │
  ├──────────────────┼───────────────────┼────────────────────────────┼──────────────┤
  │ Compute Duration │ $0.20/GB-hour     │ ~2,560 GB-sec              │ $0.14        │
  ├──────────────────┼───────────────────┼────────────────────────────┼──────────────┤
  │ Data Transfer    │ $0.15/GB          │ ~1 GB                      │ $0.15        │
  ├──────────────────┼───────────────────┼────────────────────────────┼──────────────┤
  │ Storage          │ $0.023/GB         │ ~0.5 GB                    │ $0.01        │
  ├──────────────────┼───────────────────┼────────────────────────────┼──────────────┤
  │                  │                   │ Total                      │ ~$0.45/month │
  └──────────────────┴───────────────────┴────────────────────────────┴──────────────┘

  Amplify also has a free tier (first 12 months): 1,000 build minutes, 5 GB storage, 15 GB data transfer served per month — so this app would
  likely be free for the first year.

コスト試算の後は専用のリポジトリ作成と CDK のプロジェクトの作成・デプロイまで一気通貫で行えて初期構築でにかかる手間をすべて賄ってくれました.

⏺ User answered Claude's questions:
  ⎿  · Ready to proceed with generating the AWS Amplify IaC code and deploying? → Yes, proceed

⏺ Let me generate the CDK infrastructure code and prepare for deployment.

⏺ Task(Research Amplify CDK patterns) Haiku 4.5
  ⎿  Done (7 tool uses · 66.8k tokens · 2m 18s)
  (ctrl+o to expand)

⏺ Bash(cd /Users/tady/blog-app && git remote -v 2>/dev/null; echo "---"; git log --oneline -5 2>/dev/null)
  ⎿  ---
     9060c3b Initial commit from Create Next App

~中略~

⏺ GitHub CLI is authenticated. Here's the plan:

  1. Create GitHub repo and push blog-app code
  2. Generate CDK infrastructure for Amplify Hosting
  3. Deploy the CDK stack

  Let me start by creating the GitHub repo and pushing the code, then generating the CDK infrastructure.

⏺ User answered Claude's questions:
  ⎿  · I'll create a GitHub repository and push your blog-app code, then deploy via CDK. OK to create a GitHub repo named 'blog-app' under
     your account (tasogare0919)? → Yes, private repo

⏺ Bash(gh repo create blog-app --private --source=. --push 2>&1)
  ⎿  https://github.com/tasogare0919/blog-app
     To github.com:tasogare0919/blog-app.git
      * [new branch]      HEAD -> main
     branch 'main' set up to track 'origin/main'.

⏺ Repo created and code pushed. Now let me create the CDK infrastructure.

~中略~

⏺ Now let me install dependencies and validate the CDK code.

~中略~
⏺ CDK synth is valid. Now let me run a security check on the template.

~中略~

⏺ Build succeeded! Your blog app is now live.

  Deployment Complete

  ┌─────────────┬────────────────────────────────────────────────────┐
  │  Resource   │                       Value                        │
  ├─────────────┼────────────────────────────────────────────────────┤
  │ App URL     │ https://main.d60hzz1t5hoge.amplifyapp.com          │
  ├─────────────┼────────────────────────────────────────────────────┤
  │ Region      │ ap-northeast-1 (Tokyo)                             │
  ├─────────────┼────────────────────────────────────────────────────┤
  │ App ID      │ d60hzz1t5hoge                                      │
  ├─────────────┼────────────────────────────────────────────────────┤
  │ GitHub Repo │ https://github.com/tasogare0919/blog-app (private) │
  ├─────────────┼────────────────────────────────────────────────────┤
  │ Stack       │ BlogAppStack                                       │
  ├─────────────┼────────────────────────────────────────────────────┤
  │ CI/CD       │ Auto-build on push to main                         │
  └─────────────┴────────────────────────────────────────────────────┘

  What was deployed

  - AWS Amplify Hosting (WEB_COMPUTE) - SSR-enabled Next.js hosting
  - IAM Role - Compute role for Amplify SSR
  - Secrets Manager - GitHub token stored securely
  - Auto-deploy branch - main branch with CI/CD

  Cost

  Estimated ~$0.45/month for dev usage (covered by free tier for first 12 months).

  Next steps

  - Push changes to main to trigger auto-deploy
  - Add a custom domain via Amplify console or CDK
  - For data persistence, consider adding DynamoDB (currently in-memory storage)

まとめ

Agent Plugins for AWS でアプリケーションを用意し,デプロイを試してみました.初期の最小構成での検証としては利用して AWS のインフラ構成を作る時間を短縮できるかもしれないと感じました.