Design secure multi-tier cloud infrastructure

Quick Overview

This question evaluates cloud systems design competencies including multi-tier network architecture, IP addressing and capacity planning, security controls, centralized server management, shared storage trade-offs, and identity and access integration within a production-scale virtual private cloud.

Design secure multi-tier cloud infrastructure

Company: Amazon

Role: Software Engineer

Category: System Design

Difficulty: hard

Interview Round: Technical Screen

Design and deploy a multi-tier VPC-based architecture for a large-scale application. Address: ( 1) Multi-layer segmentation (web/app/db) across multiple Availability Zones with subnets, route tables, NAT/bastion access, and security groups vs. network ACLs; ( 2) IP planning for at least 2,000 servers: choose VPC and subnet CIDR ranges, account for per-subnet reserved IPs, keep headroom for growth, distribute across at least three AZs, show calculations, and present one feasible plan; ( 3) Centralized management for Linux and Windows (patching, configuration, inventory, remote sessions): compare AWS Systems Manager, AD/Group Policy, and tools like Ansible/Salt; ( 4) Shared storage for concurrent access: compare NFS, Amazon EFS, SMB/FSx, and object-storage gateways, discussing consistency/locking, throughput/IOPS scaling, latency, and cost; ( 5) Single sign-on for administrators to "log in once" to servers and consoles using SSO (SAML/OIDC), MFA, short-lived credentials (e.g., SSM Session Manager/Kerberos), RBAC, auditing, and break-glass procedures.

Overview: This question evaluates cloud systems design competencies including multi-tier network architecture, IP addressing and capacity planning, security controls, centralized server management, shared storage trade-offs, and identity and access integration within a production-scale virtual private cloud.

|Home/System Design/Amazon
Amazon logo
Amazon
Sep 6, 2025
hardSoftware EngineerTechnical ScreenSystem Design
8
0

System Design: Multi-tier VPC Architecture for a Large-Scale Application

You are designing and deploying a production-ready, multi-tier network on AWS for an internet-facing application with thousands of servers. Assume three or more Availability Zones (AZs) in one Region and typical tiers: web, application, and database.

Address the following:

  1. Network Segmentation and Access
    • Design multi-layer segmentation (web/app/db) across multiple AZs using subnets and route tables.
    • Show how public vs. private subnets, NAT gateways, and optional bastion hosts are used.
    • Explain how you would use Security Groups vs. Network ACLs and why.
  2. IP Address Planning (≥ 2,000 servers)
    • Choose a VPC CIDR and per-subnet CIDRs.
    • Account for per-subnet reserved IPs, plan headroom for growth, and distribute across at least three AZs.
    • Show calculations and present one concrete, feasible plan with explicit CIDR blocks.
  3. Centralized Server Management (Linux and Windows)
    • Compare approaches for patching, configuration management, inventory, and remote sessions: AWS Systems Manager, Active Directory/Group Policy, and tools like Ansible/Salt.
    • Recommend a combined approach and justify it.
  4. Shared Storage for Concurrent Access
    • Compare NFS on EC2, Amazon EFS, SMB/FSx options, and object storage gateways.
    • Discuss consistency/locking semantics, throughput/IOPS scaling, latency, and cost trade-offs.
    • Recommend options for Linux and Windows workloads.
  5. Single Sign-On for Administrators
    • Design "log in once" for server and console access using SSO (SAML/OIDC), MFA, short-lived credentials (e.g., SSM Session Manager/Kerberos), RBAC, auditing, and break-glass procedures.
    • Provide concrete services and controls to implement this.

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...