role-architect:aws-architect

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.

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

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.

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.

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.

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