Cloud System Architecture Design Expert
Budget: $30 – $250 USD
I’m mapping out a full system design that must run seamlessly on both AWS and Azure, and I need a seasoned cloud architect to translate that vision into a clear, implementation-ready blueprint. The primary goal is system design itself—laying down the foundations that will later guide capacity planning, cost management, security hardening, and eventual migration tasks.
Here’s what I expect to walk away with:
• Editable high-level and low-level diagrams that detail compute, networking, storage, IAM boundaries, observability, CI/CD, and disaster-recovery layers.
• A brief but thorough design document (Markdown, PDF, or similar) explaining every service choice, expected throughput, scaling approach, and cost considerations across AWS and Azure.
• A rollout plan that includes landing-zone structure, recommended guardrails, and sample IaC snippets (Terraform or Bicep) my engineers can extend.
Acceptance criteria
• Diagrams delivered in a format I can modify (Draw.io, Lucidchart, or Visio).
• Design aligns with both the AWS Well-Architected Framework and Azure CAF; any intentional deviations are justified.
• All region, quota, and service-limit constraints are highlighted to prevent deployment surprises.
If multi-cloud architecture is your daily bread, let’s make this design rock-solid together.
Here’s what I expect to walk away with:
• Editable high-level and low-level diagrams that detail compute, networking, storage, IAM boundaries, observability, CI/CD, and disaster-recovery layers.
• A brief but thorough design document (Markdown, PDF, or similar) explaining every service choice, expected throughput, scaling approach, and cost considerations across AWS and Azure.
• A rollout plan that includes landing-zone structure, recommended guardrails, and sample IaC snippets (Terraform or Bicep) my engineers can extend.
Acceptance criteria
• Diagrams delivered in a format I can modify (Draw.io, Lucidchart, or Visio).
• Design aligns with both the AWS Well-Architected Framework and Azure CAF; any intentional deviations are justified.
• All region, quota, and service-limit constraints are highlighted to prevent deployment surprises.
If multi-cloud architecture is your daily bread, let’s make this design rock-solid together.