PracHub
QuestionsLearningGuidesInterview Prep
|Home/System Design/Amazon

Design VPC, IP plan, management, storage, SSO

Last updated: Mar 29, 2026

Quick Overview

This interview question evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer for Design VPC, IP plan, management, storage, SSO states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

  • hard
  • Amazon
  • System Design
  • Software Engineer

Design VPC, IP plan, management, storage, SSO

Company: Amazon

Role: Software Engineer

Category: System Design

Difficulty: hard

Interview Round: Technical Screen

Design and deploy a multi-layer VPC architecture: how would you segment networks (public, private, management), route between layers, and enforce security with subnets, route tables, and security groups? For a fleet of 2,000 servers, plan the CIDR allocations and estimate how many IPs are required, accounting for per-subnet reserved addresses and future growth. Propose a centralized way to manage both Linux and Windows instances (e.g., configuration management, patching, access control, inventory). Recommend a shared storage solution for concurrent access by multiple servers (e.g., NFS/EFS, SMB/FSx, or alternatives) and compare performance, consistency, and cost trade-offs. Finally, design single sign-on so users authenticate once to access multiple services, including the identity provider choice, trust relationships, and token flows.

Quick Answer: This interview question evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer for Design VPC, IP plan, management, storage, SSO states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Related Interview Questions

  • Design a Scalable Metrics Monitoring System - Amazon (medium)
  • Design a Personalized Weekly Deals Service - Amazon (medium)
  • Design an Amazon Locker Service - Amazon (easy)
  • Architect an AI Chatbot for Enterprise Users - Amazon (medium)
  • Design a Scalable News Feed - Amazon (easy)
|Home/System Design/Amazon

Design VPC, IP plan, management, storage, SSO

Amazon logo
Amazon
Aug 10, 2025, 12:00 AM
hardSoftware EngineerTechnical ScreenSystem Design
5
0

Design VPC, IP plan, management, storage, SSO

System Design: Multi‑Layer VPC, IP Planning for 2,000 Servers, Fleet Management, Shared Storage, and SSO

Context

Design a production‑grade, multi‑AZ network and platform foundation in a major public cloud that uses VPC constructs (subnets, route tables, security groups). The environment will host a mixed Linux/Windows fleet (~2,000 servers) and multiple services requiring shared file storage and single sign‑on.

Requirements

  1. Network segmentation and routing
    • Segment networks into public, private (application), and management layers.
    • Define subnets, route tables, internet/NAT gateways, and inter‑tier routing.
    • Enforce security with security groups and (optionally) network ACLs.
  2. CIDR and IP planning for 2,000 servers
    • Plan VPC and subnet CIDR blocks across at least 3 Availability Zones.
    • Estimate required IPs (include per‑subnet reserved addresses) and future growth.
  3. Centralized fleet management (Linux and Windows)
    • Propose tools/processes for configuration management, patching, access control, and inventory.
  4. Shared storage for concurrent access
    • Recommend a solution (e.g., NFS/EFS, SMB/FSx variants) and compare performance, consistency, and cost.
  5. Single sign‑on (SSO)
    • Design SSO so users authenticate once to access multiple services.
    • Include identity provider choice, trust relationships, and token/assertion flows.

Constraints & Assumptions

  • Preserve the scope, facts, inputs, and requested outputs from the prompt above.
  • If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.
  • Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

Clarifying Questions to Ask Guidance

  • Clarify users, core use cases, read/write patterns, scale, latency, availability, and data retention.
  • State explicit assumptions before making sizing or architecture decisions.
  • Prioritize the functional path first, then address reliability, security, observability, and rollout.

What a Strong Answer Covers Guidance

  • A scoped requirements summary with concrete non-goals and success metrics.
  • API, data model, architecture, consistency, capacity, and operations.
  • Reasoned trade-offs among simple and scalable designs, including bottlenecks and failure modes.
  • A validation, monitoring, migration, and launch plan appropriate for the risk level.

Follow-up Questions Guidance

  • What breaks first at 10x traffic or data volume?
  • How would you degrade gracefully during dependency failures?
  • What metrics and alerts would prove the design is healthy after launch?

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Amazon•More Software Engineer•Amazon Software Engineer•Amazon System Design•Software Engineer System Design

Your design canvas — auto-saved

PracHub

Master your tech interviews with 9,000+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • AI Coding Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.