Skill

role-architect:aws-architect

Provides AWS architecture expertise on Well-Architected Framework, multi-account strategies, VPC networking, compute/serverless patterns, data services, security, and cost optimization. Use for designing AWS systems, evaluating services, and planning landing zones.

AWS

infrastructure

devops

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

Popularity

Parent stars

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/role-architect:aws-architect

User invocable

Model invocable

Inline context

Default effort

Tool Access

This skill is limited to the following tools:

ReadGrepGlobBash

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

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

Supporting Files

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

SKILL.md

33 lines · ~585 tokens

Similar Skills

role-devops:aws-expert

Provides deep AWS expertise for IAM policies, VPC networking, EKS/ECS/Lambda compute, RDS/DynamoDB/S3 storage, security hardening, monitoring, and multi-account production strategies.

3 files4 tools

role-devops

aws-solution-architect

Designs and stress-tests AWS cross-domain solution architectures. Use for multi-domain tradeoffs needing decision records, risk registers, or implementation roadmaps.

4 files3 tools

vanguard-frontier-agentic

cloud-architecture

Design cloud infrastructure for AWS, GCP, or Azure. Plan compute, storage, networking, and compliance. Use when architecting cloud systems or migrating to cloud.

infrastructure-design

Stats

LanguageShell

Parent stars13

Parent forks1

MaintenanceGood

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

role-architect:aws-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

role-architect:aws-architect

Popularity

Invocation

Tool Access

Context Preview

Supporting Files

SKILL.md

Similar Skills

Help us improve

Help us improve

Find plugins for your project

role-architect:aws-architect

Popularity

Invocation

Tool Access

Context Preview

Supporting Files

SKILL.md

AWS Architect

When to use

Core principles

Reference Files

Similar Skills

Help us improve

AWS Architect

When to use

Core principles

Reference Files