cloudcraft aws TCP Three-Way Handshake Infographic

Tech architecture infographic titled "TCP Three-Way Handshake" using archetype PROTOCOL HANDSHAKE, not a cloud reference architecture, designed for architect / staff audience. Show a technically accurate TCP connection setup as a clean isometric tech diagram in a green terminal palette, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Compose the scene with labeled boxes connected by directional arrows: Client Host box with terminal or laptop icon, name "Client Host", role "Initiates TCP connection"; Network Path box with generic cloud and router icon, name "IP Network", role "Transports TCP segments between hosts"; Server Host box with server rack icon, name "Server Host", role "Listens on TCP port and accepts connections"; Client TCP State box with chip icon, name "Client TCP Stack", role "Tracks SYN-SENT and ESTABLISHED states"; Server TCP State box with chip icon, name "Server TCP Stack", role "Tracks LISTEN, SYN-RECEIVED and ESTABLISHED states". Connect boxes with arrows showing exact exchange direction and labels in English: from Client Host / Client TCP Stack to Server Host / Server TCP Stack label "1. TCP SYN, Seq=x, dst port=443"; return arrow from Server Host / Server TCP Stack to Client Host / Client TCP Stack label "2. TCP SYN-ACK, Seq=y, Ack=x+1"; final arrow from Client Host / Client TCP Stack to Server Host / Server TCP Stack label "3. TCP ACK, Ack=y+1". Add supporting side arrows between hosts and Network Path labeled "IP packet carrying TCP segment", and subtle state-transition callouts labeled "LISTEN", "SYN-SENT", "SYN-RECEIVED", "ESTABLISHED". Include small port notation near endpoints such as "Ephemeral Source Port" and "Destination Port 443". Add packet-detail mini boxes or callouts for flags and sequence logic: "SYN flag set", "SYN+ACK flags set", "ACK flag set". Include a numbered legend 1-7 in English: 1. "Client opens a socket and sends a TCP SYN to the server port." 2. "The SYN advertises the client initial sequence number x." 3. "The server in LISTEN state receives SYN and allocates connection state." 4. "The server replies with SYN-ACK using its own initial sequence number y and Ack=x+1." 5. "The client validates the reply and moves toward ESTABLISHED state." 6. "The client sends ACK with Ack=y+1 to confirm the server sequence." 7. "Both endpoints enter ESTABLISHED state and application data can now flow." Add a small footer note in English: "Conceptual protocol diagram for explanation, not an audited production reference." Use crisp vector boxes, glowing green-on-dark terminal accents, black and deep charcoal background, neon green lines, muted emerald fills, subtle grid, precise arrowheads, clean typography, high contrast, structured spacing, professional systems-design mood. No browser, API, DB, cache, or queue unless represented only as generic non-primary placeholders outside the handshake flow; the main diagram must stay focused on the TCP protocol exchange and state transitions. 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).