role-architect:aws-architect

Designs AWS architectures including multi-account strategies, VPCs, and landing zones.

14|3|Updated Feb 22, 2026

Search Tags:#devops #serverless #aws #infrastructure #cost optimization #cloud architecture #vpc

Ready to run

npx skills add https://github.com/rnavarych/alpha-engineer --skill role-architect-aws-architect

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: role-architect:aws-architect
Source: https://github.com/rnavarych/alpha-engineer/tree/main/plugins/roles/role-architect/skills/aws-architect
Command: npx skills add https://github.com/rnavarych/alpha-engineer --skill role-architect-aws-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides expert guidance for designing, evaluating, and optimizing cloud architectures specifically on Amazon Web Services (AWS), ensuring best practices in security, reliability, performance, and cost-efficiency.

Core Features & Use Cases

AWS Architecture Design: Develop multi-account strategies, VPC designs, and landing zones.
Service Selection: Choose appropriate compute (ECS, EKS, Lambda) and data (Aurora, DynamoDB, Redshift) services.
Security & Cost Optimization: Implement security best practices and cost-saving measures.
Use Case: When planning a new microservices application on AWS, use this Skill to determine the optimal compute service (Fargate vs. EKS vs. Lambda) and database solution (Aurora vs. DynamoDB) based on performance, scalability, and cost requirements.

Quick Start

Use the aws-architect skill to design a multi-account strategy for a new AWS deployment.

Frequently Asked Questions about role-architect:aws-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design a multi-account AWS landing zone for a new microservices application?▼

To design a multi-account AWS landing zone, apply Well-Architected Framework principles to separate workloads, establish VPC network designs, and plan security boundaries for cloud-native applications.

What's the best way to choose between AWS compute services like Fargate, EKS, and Lambda?▼

Choosing AWS compute services requires evaluating service selection patterns based on performance, scalability, and cost optimization requirements for your specific serverless or containerized workloads.

When do I need a multi-account strategy for my AWS cloud architecture?▼

You need a multi-account strategy for AWS cloud architecture when isolating environments for security, managing billing boundaries, and enforcing distinct access controls across landing zones.

How do I optimize AWS infrastructure costs while maintaining security and reliability?▼

Optimize AWS infrastructure costs by implementing Well-Architected Framework principles, selecting appropriate compute and data services, and applying targeted cost-saving measures without compromising security.

Does this AWS architecture guidance cover VPC and network design for serverless workloads?▼

Yes, AWS architecture guidance covers VPC and network design for serverless workloads, detailing how to configure network patterns that support Lambda and compute services securely.

How do I select the right data architecture services like Aurora, DynamoDB, or Redshift on AWS?▼

Selecting the right AWS data architecture services involves comparing Aurora, DynamoDB, and Redshift against your specific performance, scalability, and data structure requirements.