‹ 首页

aws-sam-bootstrap

@giuseppe-trisciuoglio · 收录于 1 周前

Provides AWS SAM bootstrap patterns: generates `template.yaml` and `samconfig.toml` for new projects via `sam init`, creates SAM templates for existing Lambda/CloudFormation code migration, validates build/package/deploy workflows, and configures local testing with `sam local invoke`. Use when the user asks about SAM projects, `sam init`, `sam deploy`, serverless deployments, or needs to bootstrap/migrate Lambda functions with SAM templates.

场景新项目初始化lambda迁移部署配置

适合你，如果要用 AWS SAM 搭建或迁移无服务器应用

/ 下载安装
aws-sam-bootstrap.skill双击,或拖进 Claude 桌面版 / Cowork,即完成安装↓ .skill↓ .zip
用别的 agent?下载 .zip 解压,把文件夹放进它的技能目录
Claude Code~/.claude/skills/(项目级 .claude/skills/)
Codex CLI~/.codex/skills/
Cursor自动读取上面两处目录
其他工具见其文档的「skills」目录;两个下载是同一份文件,只是名字不同
/ 通过 npx 安装 校验哈希
npx oh-my-skill add giuseppe-trisciuoglio/developer-kit/aws-sam-bootstrap
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- giuseppe-trisciuoglio/developer-kit/aws-sam-bootstrap
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify giuseppe-trisciuoglio/developer-kit/aws-sam-bootstrap
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
303GitHub stars
~784最小装载
~1.5K含声明引用
~1.5K文本包总量
镜像托管

怎么用

技能原文 SKILL.md作者撰写 · MIT · 306f428

AWS SAM Bootstrap

Overview

Generates SAM project artifacts for greenfield and migration scenarios. Creates the minimum required files (template.yaml, samconfig.toml, events/), validates with sam build, and configures sam deploy workflows following AWS SAM conventions.

When to Use
  • User needs to start a new AWS SAM project (sam init, sam deploy)
  • User wants to migrate existing Lambda functions or CloudFormation resources to SAM templates
  • User asks about SAM CLI commands (sam init, sam build, sam local invoke, sam deploy)
  • User needs to create or update template.yaml or samconfig.toml for serverless deployments
  • User wants to configure local testing with sam local invoke for Lambda functions
Instructions
1) Classify Scenario
  • New project: no Lambda structure exists. Run sam init to scaffold.
  • Existing project migration: Lambda/CloudFormation resources exist. Create template.yaml manually.
2) Select Runtime and Package Type

Use current non-deprecated runtimes. Package type: Zip (default) or Image (container/native deps).

3) Bootstrap New Projects
sam init
sam build
sam local invoke <LogicalFunctionId> -e events/event.json
sam deploy --guided
4) Bootstrap Existing Projects
  1. Inspect current Lambda handlers, runtime, and dependency layout
  2. Create template.yaml with Transform: AWS::Serverless-2016-10-31
  3. Map existing resources to AWS::Serverless::Function and related SAM resources
  4. Create samconfig.toml with deploy defaults and environment overrides
  5. Add events/event.json payload samples for local invocation
  6. Validate with sam validate and sam build before deploy
5) Required Artifacts
.
├── template.yaml
├── samconfig.toml
└── events/
    └── event.json

See reference templates: [examples.md](references/examples.md), [migration-checklist.md](references/migration-checklist.md)

6) Validation Checklist
  • sam validate succeeds
  • sam build succeeds
  • template.yaml has correct logical IDs and handlers
  • samconfig.toml contains deploy parameters for target environments
Examples
New SAM Project
sam init  # Interactive scaffold
sam build
sam local invoke HelloFunction -e events/event.json
sam deploy --guided
Migrate Existing Lambda
  1. Detect handler/runtime → create template.yaml with SAM transform
  2. Add samconfig.toml with stack_name, capabilities, resolve_s3
  3. Add events/event.json → validate with sam build

Full templates in [references/examples.md](references/examples.md).

Best Practices
  • One deployable function first, then expand; keep migration-first PRs minimal
  • Keep samconfig.toml committed for deterministic deployments
  • Use environment-specific sections ([default], [prod]) instead of CLI flags
  • Map existing handler paths to SAM conventions during migration
Constraints and Warnings
  • SAM CLI must be installed locally for command execution
  • CAPABILITY_IAM is required when IAM resources are created
  • Container image packaging requires Docker availability
  • Existing projects may require refactoring handler paths to match SAM conventions
  • sam deploy --guided writes local configuration; review before committing
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…