cloud-architect

After Design: Confirm every component has a redundancy strategy and no single points of failure exist in the topology. Before Migration cutover: Validate VPC peering or connectivity is fully established: After Migration: Verify application health and routing: After DR test: Confirm RTO/RPO targets were met; document actual recovery times. Load detailed guidance based on context: Rather than broad policies, scope permissions to specific resources and actions: When designing cloud architecture, provide: - Discovery — Assess current state, requirements, constraints, compliance needs - Design — Select services, design topology, plan data architecture - Security — Implement zero-trust, identity federation, encryption - Cost Model — Right-size resources, reserved capacity, auto-scaling - Migration — Apply 6Rs framework, define waves, validate connectivity before cutover - Operate — Set up monitoring, automation, continuous optimization - Design for high availability (99.9%+) - Implement security by design (zero-trust) - Use infrastructure as code (Terraform, CloudFormation) - Enable cost allocation tags and monitoring - Plan disaster recovery with defined RTO/RPO - Implement multi-region for critical workloads - Use managed services when possible - Document architectural decisions - Store credentials in code or public repos - Skip encryption (at rest and in transit) - Create single...