AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Aws Production Systems

skill-caiaffa-claude-code-ultimate-engineering-system-aws-production-systems · by caiaffa

Design and review AWS systems for IAM safety, resilience, scalability, durability, operability, and cost awareness.

No reviews yet
0 installs
38 views
0.0% view→install

Install

$ agentstack add skill-caiaffa-claude-code-ultimate-engineering-system-aws-production-systems

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-caiaffa-claude-code-ultimate-engineering-system-aws-production-systems)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Aws Production Systems? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Mission

Ensure AWS architectures are safe to run, understandable to operate, and justifiable in cost and complexity.

When to use

  • Designing or reviewing AWS-native systems.
  • Choosing managed services.
  • Reviewing IAM, queues, storage, networking, or secrets.
  • Planning resilience or disaster recovery.

Handoff

  • Receives from: principal-engineer (architecture decision) or backend-platform-engineer (infra needs).
  • Hands off to: security-review (IAM/trust), kubernetes-operability (if EKS), release-commander (infra rollout).

Before answering

Identify: workload type, traffic pattern, availability requirements, cost sensitivity, team ability to operate the chosen services, network and security constraints.

Service selection principles

| Need | Prefer | Avoid unless justified | |---|---|---| | Async jobs | SQS + Lambda or ECS | Step Functions for simple pipelines | | API backend | ECS/Fargate or EKS | Lambda if > 15s or stateful | | Storage | S3 (objects), RDS (relational), DynamoDB (key-value) | Aurora Serverless v1 (cold start) | | Caching | ElastiCache Redis | Self-managed Redis on EC2 | | Secrets | Secrets Manager or Parameter Store | Env vars in task definitions | | Events | EventBridge | SNS fan-out for complex routing |

Red flags

  • IAM policy with "Action": "*" or "Resource": "*".
  • S3 bucket without explicit public access block.
  • RDS without multi-AZ in production.
  • Lambda with 15-minute timeout on critical path.
  • No encryption at rest on any data store.
  • No CloudTrail or access logging.
  • Cost estimate missing from design doc.

Deep evaluation checklist

  1. Service decomposition and responsibilities.
  2. IAM — least privilege? trust boundaries explicit? cross-account?
  3. Networking — VPC, subnets, security groups, endpoints vs NAT.
  4. Queue/event semantics — at-least-once? ordering? DLQ?
  5. Data durability — backup, point-in-time recovery, cross-region?
  6. Availability — multi-AZ? failover tested? health checks meaningful?
  7. Secrets — rotation? scoped? auditable?
  8. Cost — top 3 cost drivers identified? reserved/spot where appropriate?
  9. Observability — CloudWatch, X-Ray, or OTel? alerts actionable?

Output format

  1. Architecture review (diagram or description)
  2. IAM assessment (overprivileged areas, trust boundary gaps)
  3. Risks by severity (critical / high / medium)
  4. Cost analysis (top 3 cost drivers, optimization opportunities)
  5. Recommendations (prioritized)
  6. Rollout notes (safe deployment order for infra changes)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.