AWS Architecture Diagram of TCP Three-Way Handshake

Tech architecture infographic titled "TCP Three-Way Handshake" using the PROTOCOL HANDSHAKE archetype, adapted for a non-technical executive audience. Show a clean left-to-right network exchange with labeled boxes connected by directional arrows. Main boxes: Client Device icon + label "TCP Client" + one-line role "Initiates the connection request"; Network Cloud icon + label "IP Network" + one-line role "Transports TCP packets between endpoints"; Server Rack icon + label "TCP Server" + one-line role "Listens on a TCP port and accepts connections". Add supporting side boxes for context in simple generic form: Browser icon + label "Application Client" + one-line role "Uses the TCP connection to send app data"; API box icon + label "Application Service" + one-line role "Runs behind the established TCP session"; Database cylinder icon + label "Database" + one-line role "Stores application data after the session is established"; Cache box icon + label "Cache" + one-line role "Serves frequently requested data"; Queue icon + label "Message Queue" + one-line role "Buffers asynchronous work after requests arrive". Use arrows with technically accurate labels: arrow 1 from TCP Client to TCP Server through IP Network labeled "SYN, Seq=x"; arrow 2 from TCP Server back to TCP Client through IP Network labeled "SYN-ACK, Seq=y, Ack=x+1"; arrow 3 from TCP Client to TCP Server through IP Network labeled "ACK, Ack=y+1". Then show a lighter secondary arrow from Application Client to Application Service labeled "HTTP request over established TCP"; from Application Service to Database labeled "SQL query"; from Application Service to Cache labeled "Cache read/write"; from Application Service to Message Queue labeled "Async event"; return arrow back to Application Client labeled "HTTP 200 response". Include small port callouts near client and server such as "Ephemeral Port" and "Server Port 443 or 80". Make it clear that the TCP handshake happens before application data flows. Add numbered legend 1-7 in English: 1. "Client sends SYN to start a TCP connection." 2. "Network routes the packet to the listening server." 3. "Server replies with SYN-ACK to confirm and synchronize sequence numbers." 4. "Client sends ACK to complete the three-way handshake." 5. "TCP session is now established and ready for data transfer." 6. "Application traffic such as HTTP can now move across the connection." 7. "Backend services may then use cache, database, and queue as needed." Add a small note box labeled "Scope" with text "Conceptual protocol illustration, not an audited reference architecture." Visual style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use a green terminal palette with dark charcoal background, neon green accents, soft mint highlights, subtle grid lines, glowing packet arrows, crisp vector boxes, simple executive-friendly composition, modern technical mood, high contrast, minimal clutter. Include generic cloud icons only, no vendor branding. 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).