AWS Three-Tier Web App Topology Layout Infographic

Tech architecture infographic titled "AWS Three-Tier Web App" using archetype SYSTEM ARCHITECTURE (services + queues + storage). Show a classic three-tier topology layout for an architect / staff audience: Presentation Tier, Application Tier, and Data Tier, arranged left-to-right or top-to-bottom with clear grouped swimlanes. Render labeled boxes for each component, all connected by directional arrows: User Browser, CDN / Static Assets, Load Balancer, Web App / Frontend Servers, API Service, Auth Service, Cache, Message Queue, Worker Service, Relational Database, Object Storage, Monitoring / Logs. Include generic cloud boundary icons and network segments, but no real cloud-vendor logos. Each box must contain: a simple retro computing icon, the component name in canonical English-tech form, and a one-line English role description. Example role descriptions: "Renders UI and sends HTTPS requests", "Routes traffic to healthy app nodes", "Processes REST API business logic", "Stores session and hot query data", "Persists transactional records". Arrows must clearly show data direction and include short English labels such as: "HTTPS GET / HTML", "HTTPS REST JSON", "JWT token", "Cache read/write", "Enqueue job", "Async task", "SQL over TCP", "Object upload", "Metrics / logs". Make the flow technically accurate: Browser to Load Balancer over HTTPS, Load Balancer to Web App / Frontend Servers, Web App to API Service over REST/HTTPS, API Service to Auth Service for OAuth / JWT validation when needed, API Service to Cache for read-through caching, API Service to Relational Database over SQL over TCP, API Service to Message Queue for background jobs, Worker Service consumes queue messages and updates Database or Object Storage, Monitoring / Logs receives telemetry from app, API, worker, and database. Include optional response arrows back to Browser labeled "HTML/CSS/JS", "JSON response", and error path examples like "HTTP 200", "HTTP 401", "HTTP 500" where appropriate. Add a numbered legend (1-7) in English walking through the request lifecycle: 1 User opens app in browser over HTTPS, 2 Load balancer forwards request to web tier, 3 Frontend requests API data over REST, 4 API validates JWT / session and checks cache, 5 Cache miss triggers SQL query to relational database, 6 API may enqueue async work for worker processing and object storage, 7 Response returns to browser and telemetry is sent to monitoring. Visual style: retro 1980s computing, blueprint cyan palette, glowing cyan lines on deep navy background, technical drafting grid, vector wireframe boxes, CRT-inspired screen glow, subtle scanline texture, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Mood: precise, nostalgic, systems-engineering, schematic, professional but not marketing-like. Emphasize topology clarity, tier boundaries, and request/data lifecycle. Avoid any wording that implies audited security or official reference architecture. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real cloud-vendor logos (AWS, GCP, Azure) beyond generic cloud icons. Common protocol names (HTTPS, TCP, JWT, OAuth, REST, GraphQL) stay in canonical English form. No security-claim overstatements (do not present diagrams as audited reference architectures).