Skill

role-architect:aws-architect

AWS architecture expertise including Well-Architected Framework, account strategy, VPC and networking design, compute and serverless patterns, data architecture, security architecture, and cost optimization strategies. Use proactively when designing systems on AWS, evaluating AWS services, planning AWS landing zones, or architecting for AWS-specific capabilities.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin role-architect

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash

Preview

- Designing or reviewing AWS multi-account strategy and Control Tower landing zones

Supporting Assets

references/aws-data-security-cost.mdreferences/aws-platform-and-compute.md

SKILL.md

Similar Skills

ui-ux-pro-max

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

57.6k

context7-mcp

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

51.8k

market-sizing-analysis

2 files

Calculates TAM/SAM/SOM using top-down, bottom-up, and value theory methodologies for market sizing, revenue estimation, and startup validation.

startup-business-analyst

32.9k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

role-architect:aws-architect

When to use

Designing or reviewing AWS multi-account strategy and Control Tower landing zones

Selecting between ECS Fargate, EKS, and Lambda for a workload

Architecting VPC design, Transit Gateway topology, or Direct Connect hybrid connectivity

Choosing between Aurora, DynamoDB, ElastiCache, Redshift, and Kinesis for data needs

Configuring GuardDuty, Security Hub, IAM Identity Center, or KMS for security posture

Designing multi-Region active-passive or active-active architectures

Optimizing AWS costs with Savings Plans, Spot Instances, Graviton, and data transfer strategies

Core principles

Multi-account by default — never mix production and non-production in the same account

SCPs as guardrails — enforce baseline security at the Organizations level

Roles over keys — IAM roles for everything; eliminate long-lived access keys

Tagging from day one — cost allocation and compliance require consistent tags before spend grows

Savings Plans before Reserved Instances — flexibility matters more than maximum discount for most workloads

Reference Files

references/aws-platform-and-compute.md — Well-Architected six pillars, multi-account architecture, Control Tower, Account Vending, VPC design, Transit Gateway, Direct Connect vs VPN, PrivateLink, ECS Fargate vs EKS, Lambda cold start mitigation, Step Functions, and EC2 Auto Scaling with Graviton

references/aws-data-security-cost.md — Aurora, DynamoDB, ElastiCache selection; Lake Formation, Redshift, Kinesis, Athena analytics stack; EventBridge, SQS/SNS, MSK event-driven patterns; IAM Identity Center, KMS encryption, Secrets Manager, GuardDuty, Security Hub, AWS Config; Compute Savings Plans, Spot strategy, Graviton migration, data transfer cost optimization, multi-Region patterns, and CloudWatch/X-Ray observability

AWS Architect

When to use

Designing or reviewing AWS multi-account strategy and Control Tower landing zones
Selecting between ECS Fargate, EKS, and Lambda for a workload
Architecting VPC design, Transit Gateway topology, or Direct Connect hybrid connectivity
Choosing between Aurora, DynamoDB, ElastiCache, Redshift, and Kinesis for data needs
Configuring GuardDuty, Security Hub, IAM Identity Center, or KMS for security posture
Designing multi-Region active-passive or active-active architectures
Optimizing AWS costs with Savings Plans, Spot Instances, Graviton, and data transfer strategies

Core principles

Multi-account by default — never mix production and non-production in the same account
SCPs as guardrails — enforce baseline security at the Organizations level
Roles over keys — IAM roles for everything; eliminate long-lived access keys
Tagging from day one — cost allocation and compliance require consistent tags before spend grows
Savings Plans before Reserved Instances — flexibility matters more than maximum discount for most workloads

Reference Files

references/aws-platform-and-compute.md — Well-Architected six pillars, multi-account architecture, Control Tower, Account Vending, VPC design, Transit Gateway, Direct Connect vs VPN, PrivateLink, ECS Fargate vs EKS, Lambda cold start mitigation, Step Functions, and EC2 Auto Scaling with Graviton
references/aws-data-security-cost.md — Aurora, DynamoDB, ElastiCache selection; Lake Formation, Redshift, Kinesis, Athena analytics stack; EventBridge, SQS/SNS, MSK event-driven patterns; IAM Identity Center, KMS encryption, Secrets Manager, GuardDuty, Security Hub, AWS Config; Compute Savings Plans, Spot strategy, Graviton migration, data transfer cost optimization, multi-Region patterns, and CloudWatch/X-Ray observability