Receber por email
← Voltar para o catálogo

aws-solution-architect

Expert AWS solution architecture for startups focusing on serverless, scalable, and cost-effective cloud infrastructure with modern DevOps practices and infrastructure-as-code

367estrelas
Atualizado há 4 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add aiskillstore/marketplace

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/aws-solution-architect-aiskillstore/svg)](https://www.skillteca.com.br/skills/aws-solution-architect-aiskillstore)

Skills relacionadas

Ver todas de DevOps e Infra →

Alerta por categoria

Receba novas skills de DevOps e Infra toda segunda

1 email curto, só com as skills novas de DevOps e Infra. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

AWS Solution Architect for Startups

This skill provides comprehensive AWS architecture design expertise for startup companies, emphasizing serverless technologies, scalability, cost optimization, and modern cloud-native patterns.

Capabilities

  • Serverless Architecture Design: Lambda, API Gateway, DynamoDB, EventBridge, Step Functions, AppSync
  • Infrastructure as Code: CloudFormation, CDK (Cloud Development Kit), Terraform templates
  • Scalable Application Architecture: Auto-scaling, load balancing, multi-region deployment
  • Data & Storage Solutions: S3, RDS Aurora Serverless, DynamoDB, ElastiCache, Neptune
  • Event-Driven Architecture: EventBridge, SNS, SQS, Kinesis, Lambda triggers
  • API Design: API Gateway (REST & WebSocket), AppSync (GraphQL), rate limiting, authentication
  • Authentication & Authorization: Cognito, IAM, fine-grained access control, federated identity
  • CI/CD Pipelines: CodePipeline, CodeBuild, CodeDeploy, GitHub Actions integration
  • Monitoring & Observability: CloudWatch, X-Ray, CloudTrail, alarms, dashboards
  • Cost Optimization: Reserved instances, Savings Plans, right-sizing, budget alerts
  • Security Best Practices: VPC design, security groups, WAF, Secrets Manager, encryption
  • Microservices Patterns: Service mesh, API composition, saga patterns, CQRS
  • Container Orchestration: ECS Fargate, EKS (Kubernetes), App Runner
  • Content Delivery: CloudFront, edge locations, origin shield, caching strategies
  • Database Migration: DMS, schema conversion, zero-downtime migrations

Input Requirements

Architecture design requires:

  • Application type: Web app, mobile backend, data pipeline, microservices, SaaS platform
  • Traffic expectations: Users/day, requests/second, geographic distribution
  • Data requirements: Storage needs, database type, backup/retention policies
  • Budget constraints: Monthly spend limits, cost optimization priorities
  • Team size & expertise: Developer count, AWS experience level, DevOps maturity
  • Compliance needs: GDPR, HIPAA, SOC 2, PCI-DSS, data residency
  • Availability requirements: SLA targets, uptime goals, disaster recovery RPO/RTO

Formats accepted:

  • Text description of application requirements
  • JSON with structured architecture specifications
  • Existing architecture diagrams or documentation
  • Current AWS resource inventory (for optimization)

Output Formats

Results include:

  • Architecture diagrams: Visual representations using draw.io or Lucidchart format
  • CloudFormation/CDK templates: Infrastructure as Code (IaC) ready to deploy
  • Terraform configurations: Multi-cloud compatible infrastructure definitions
  • Cost estimates: Detailed monthly cost breakdown with optimization suggestions
  • Security assessment: Best practices checklist, compliance validation
  • Deployment guides: Step-by-step implementation instructions
  • Runbooks: Operational procedures, troubleshooting guides, disaster recovery plans
  • Migration strategies: Phased migration plans, rollback procedures

How to Use

"Design a serverless API backend for a mobile app with 100k users using Lambda and DynamoDB" "Create a cost-optimized architecture for a SaaS platform with multi-tenancy" "Generate CloudFormation template for a three-tier web application with auto-scaling" "Design event-driven microservices architecture using EventBridge and Step Functions" "Optimize my current AWS setup to reduce costs by 30%"

Scripts

  • architecture_designer.py: Generates architecture patterns and service recommendations
  • serverless_stack.py: Creates serverless application stacks (Lambda, API Gateway, DynamoDB)
  • cost_optimizer.py: Analyzes AWS costs and provides optimization recommendations
  • iac_generator.py: Generates CloudFormation, CDK, or Terraform templates
  • security_auditor.py: AWS security best practices validation and compliance checks

Architecture Patterns

1. Serverless Web Application

Use Case: SaaS platforms, mobile backends, low-traffic websites

Stack:

  • Frontend: S3 + CloudFront (static hosting)
  • API: API Gateway + Lambda
  • Database: DynamoDB or Aurora Serverless
  • Auth: Cognito
  • CI/CD: Amplify or CodePipeline

Benefits: Zero server management, pay-per-use, auto-scaling, low operational overhead

Cost: $50-500/month for small to medium traffic

2. Event-Driven Microservices

Use Case: Complex business workflows, asynchronous processing, decoupled systems

Stack:

  • Events: EventBridge (event bus)
  • Processing: Lambda functions or ECS Fargate
  • Queue: SQS (dead letter queues for failures)
  • State Management: Step Functions
  • Storage: DynamoDB, S3

Benefits: Loose coupling, independent scaling, failure isolation, easy testing

Cost: $100-1000/month depending on event volume

3. Modern Three-Tier Application

Use Case: Traditional web apps with dynamic content, e-commerce, CMS

Stack:

  • Load Balancer: ALB (Application Load Balancer)
  • Compute: ECS Fargate or EC2 Auto Scaling
  • Database: RDS Aurora (MySQL/PostgreSQL)
  • Cache: ElastiCache (Redis)
  • CDN: CloudFront
  • Storage: S3

Benefits: Proven pattern, easy to understand, flexible scaling

Cost: $300-2000/month depending on traffic and instance sizes

4. Real-Time Data Processing

Use Case: Analytics, IoT data ingestion, log processing, streaming

Stack:

  • Ingestion: Kinesis Data Streams or Firehose
  • Processing: Lambda or Kinesis Analytics
  • Storage: S3 (data lake) + Athena (queries)
  • Visualization: QuickSight
  • Alerting: CloudWatch + SNS

Benefits: Handle millions of events, real-time insights, cost-effective storage

Cost: $200-1500/month depending on data volume

5. GraphQL API Backend

Use Case: Mobile apps, single-page applications, flexible data queries

Stack:

  • API: AppSync (managed GraphQL)
  • Resolvers: Lambda or direct DynamoDB integration
  • Database: DynamoDB
  • Real-time: AppSync subscriptions (WebSocket)
  • Auth: Cognito or API keys

Benefits: Single endpoint, reduce over/under-fetching, real-time subscriptions

Cost: $50-400/month for moderate usage

6. Multi-Region High Availability

Use Case: Global applications, disaster recovery, compliance requirements

Stack:

  • DNS: Route 53 (geolocation routing)
  • CDN: CloudFront with multiple origins
  • Compute: Multi-region Lambda or ECS
  • Database: DynamoDB Global Tables or Aurora Global Database
  • Replication: S3 cross-region replication

Benefits: Low latency globally, disaster recovery, data sovereignty

Cost: 1.5-2x single region costs

Best Practices

Serverless Design Principles

  1. Stateless functions - Store state in DynamoDB, S3, or ElastiCache
  2. Idempotency - Handle retries gracefully, use unique request IDs
  3. Cold start optimization - Use provisioned concurrency for critical paths, optimize package size
  4. Timeout management - Set appropriate timeouts, use Step Functions for long processes
  5. Error handling - Implement retry logic, dead letter queues, exponential backoff

Cost Optimization

  1. Right-sizing - Start small, monitor metrics, scale based on actual usage
  2. Reserved capacity - Use Savings Plans or Reserved Instances for predictable workloads
  3. S3 lifecycle policies - Transition to cheaper storage tiers (IA, Glacier)
  4. Lambda memory optimization - Test different memory settings for cost/performance balance
  5. CloudWatch log retention - Set appropriate retention periods (7-30 days for most)
  6. NAT Gateway alternatives - Use VPC endpoints, consider single NAT in dev environments

Security Hardening

  1. Principle of least privilege - IAM roles with minimal permissions
  2. Encryption everywhere - At rest (KMS) and in transit (TLS/SSL)
  3. Network isolation - Private
Compartilhar X LinkedIn