aws-serverless-eda
AWS serverless/event-driven playbook for Lambda, API Gateway, EventBridge, SQS/SNS, Step Functions with IaC/observability/security.
- License 许可
- MIT
- 最近更新
- 2026-08-03
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- aws-serverless-eda
- description
- AWS serverless/event-driven playbook for Lambda, API Gateway, EventBridge, SQS/SNS, Step Functions with IaC/observability/security.
02 资源文件 8
- 参考文档references/deployment-best-practices.md19.2 KB
- 参考文档references/eda-patterns.md24.1 KB
- 参考文档references/observability-best-practices.md18.6 KB
- 参考文档references/performance-optimization.md16.4 KB
- 参考文档references/security-best-practices.md14.9 KB
- 参考文档references/serverless-patterns.md20.4 KB
- 参考文档SOURCE.md178 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
AWS Serverless & EDA (Concise)
Use for: designing or operating serverless APIs/EDA on AWS with Lambda + API GW + EventBridge/SQS/SNS + Step Functions.
Architecture
- Entry: API Gateway HTTP/REST; auth via Cognito/IAM/Lambda authorizers; request validation.
- Compute: Lambda with smallest perms; cold-start reduction (provisioned concurrency for hot paths); keep packages slim; use ARM/Graviton.
- Events: EventBridge for routing/schemas; SQS for buffering/retries; SNS for fanout; DLQs; idempotency keys.
- Orchestration: Step Functions for sagas/timeouts/circuit breakers; prefer service integrations.
- Data: DynamoDB single-table patterns; TTL; GSIs sized; use streams for CDC; S3 for blobs with presigned URLs.
IaC & release
- Use CDK/Terraform; versioned stages (dev/stage/prod); automated tests +
sam local/stepfunctions-localfor critical flows. - Deploy with canaries/gradual; feature flags; rollback via previous version/alias.
Observability
- OTel/Embedded metrics: request ids, correlation ids; structured logs to CloudWatch/OTel → OpenLIT; trace across API GW → Lambda → downstream.
- Alarms: 5xx, throttles, DLQ depth, iterator age, latency; synthetic canaries for key APIs.
Reliability & performance
- Concurrency limits per function; reserved concurrency for noisy neighbors; retries/backoff; idempotent handlers.
- API GW: caching for hot GETs; WAF; proper timeouts; binary/media settings.
Security
- Least-priv IAM per function; KMS for env vars and data; block public S3; WAF on APIs; secrets in SM/Parameter Store; audit logs on admin actions.
Cutover checklist
- Run load test on canary; verify DLQ empty; alarms green; trace sample end-to-end; cost check on provisioned concurrency.
References
- AWS Serverless Lens; Lambda Powertools; EventBridge/SQS/SNS best practices; Step Functions patterns.
04 同仓库更多 Skills
next-workflow-step
Use this skill when the user wants to transition to the next workflow step, wrap up a session cleanly, prepare a handoff, or says things like "next step", "continue the workflow", "wrap up", "hand off", "move to the next phase", "what's next in embrace", or "prepare for /clear". Also triggers when the current octo:embrace phase appears complete and no explicit next action is set.
source-discovery
This skill should be used when the user asks to "find sources", "discover URLs", "catalog a source", "classify a URL", "search for libraries", "check what exists", or mentions source discovery, URL cataloging, source classification, or research source management.
review-synthesis
This skill should be used when the user asks to "summarize review findings", "prioritize fixes", "rank review issues", "combine reviewer feedback", "create action items from review", or mentions review synthesis, finding prioritization, severity ranking, or review result summarization.
research-scoring
This skill should be used when the user asks to "score research", "check research quality", "evaluate coverage", "measure improvement", "assess research completeness", or mentions research scoring, quality metrics, coverage gaps, improvement baseline, or research pipeline status.
notebooklm-integration
This skill should be used when the user asks to "ingest into NotebookLM", "query NotebookLM", "add sources to notebook", "cross-source synthesis", "check stale sources", or mentions NotebookLM, notebook integration, source ingestion, or knowledge consolidation.
evidence-synthesis
This skill should be used when the user asks to "synthesize findings", "combine research", "cross-reference sources", "summarize evidence", "write a deep review", or mentions evidence synthesis, finding consolidation, cross-source analysis, or research summarization.