Back to search

Aws architect

Design workloads aligning with the six pillars of the AWS Well-Architected Framework, translating business needs into concrete AWS patterns, and ensuring availability, fault tolerance, security, and cost optimization.

  • Posted Nov 17, 2026
INDUSTRYSoftware & InternetSaaS & Enterprise Software

Responsibilities

  • Design workloads aligning with the six pillars of the AWS Well-Architected Framework
  • Translate Business to AWS Decisions
  • Choose Services, Not Collect Them
  • Design for Availability, Fault Tolerance, and Scale
  • Make Security a Default, Not a Phase
  • Own Cost and Sustainability Trade-offs

Requirements

  • Experience in a SaaS

Skills

AWS Well-Architected FrameworkMulti-AZ architecturesCloudFormationALBAuto ScalingAuroraCloudFrontRDSDynamoDBEC2LambdaECS/FargateS3EBSEFSFSxVPCsubnetsIGWNATRoute 53IAMKMSCloudTrailWAFCloudWatchSystems ManagerTrusted AdvisorSQSSNSEventBridgeAWS

Full description

Responsibility 1: Design for the Six Pillars Your primary responsibility is to design workloads that align with the six pillars of the AWS Well-Architected Framework: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability. aws.amazon+2 In practice, that means every architecture decision should be traceable to a pillar: Why Multi-AZ? Reliability. Why CloudFormation instead of point-and-click? Operational Excellence. Why S3 Intelligent-Tiering? Cost Optimization and Sustainability. antoniolofiego.github+1 Responsibility 2: Translate Business → AWS Decisions You are the translation layer between "We need a faster checkout” and "We'll use ALB + Auto Scaling + Aurora with read replicas behind CloudFront.” coursera+1 This translation includes clarifying non-functional requirements (RTO/RPO, latency expectations, compliance constraints) and mapping them to concrete AWS patterns: Multi-AZ vs Multi-Region, RDS vs DynamoDB, EC2 vs Lambda, S3 vs EFS vs FSx. tutorialsdojo+1 Responsibility 3: Choose Services, Not Collect Them AWS has 200+ services; an Associate Architect is expected to be fluent in the 40–60 core ones, not encyclopedic about everything. linkedin+1 That fluency centers around compute (EC2, Auto Scaling, ELB, Lambda, ECS/Fargate), storage (S3, EBS, EFS, FSx, Backup), databases (RDS, Aurora, DynamoDB, Redshift), networking (VPC, subnets, IGW, NAT, Route 53), security (IAM, KMS, CloudTrail, WAF), and operations (CloudWatch, CloudFormation, Systems Manager, Trusted Advisor). antoniolofiego.github+2 Responsibility 4: Design for Availability, Fault Tolerance, and Scale A solutions architect is judged by how systems behave on a bad day, not on a sunny demo. aws.amazon+1 You are expected to apply patterns like Multi-AZ architectures, health-checked load balancing, Auto Scaling, decoupling with SQS/SNS/EventBridge, and DR strategies (backup-and-restore, pilot light, warm standby, multi-site active-active) for each workload's risk profile. cbtnuggets+2 Responsibility 5: Make Security a Default, Not a Phase Security is not "later”; it is baked into IAM design, network boundaries, data protection, and observability from day zero. aws.amazon+1 That includes least-privilege IAM, KMS-backed encryption at rest, TLS in transit, Security Groups vs NACLs used correctly, and continuous visibility using CloudTrail, GuardDuty, AWS Config, and WAF where appropriate. stream+2 Responsibility 6: Own Cost and Sustainability Trade-offs There's a reason Well-Architected reviews always hit cost: most architectures bleed money quietly before they fail loudly. stormit+2 At Associate level, you're expected to think in pricing models (On-Demand vs Savings Plans vs Spot), right-sizing, storage classes, lifecycle policies, and autoscaling strategies that balance performance with spend—and increasingly to see sustainability (efficient, right-sized, idle-free workloads) as both a cost and environmental responsibility. trendmicro+2

Aws architect at Ova Technologies | Referso Jobs