eks cluster architecture diagram: TCP Three-Way Handshake

Tech architecture infographic titled "TCP Three-Way Handshake" using PROTOCOL HANDSHAKE archetype for a non-technical executive audience. Show a clean left-to-right sequence between two main labeled boxes: Client and Server, connected by large directional arrows across three numbered exchanges. Add supporting small contextual boxes around them in a simplified tech-diagram style: Client App, Network Path, Server App, and Connection State, each with an icon, a canonical English name, and a one-line English role description. Do not use browser/API/DB/cache/queue if not technically relevant; instead use protocol-accurate TCP components only.

Main boxes:
- Box 1: "Client" with laptop icon — "Initiates the TCP connection request"
- Box 2: "Server" with server rack icon — "Listens for incoming TCP connections"
- Supporting box: "Client App" with app window icon — "Requests a reliable transport session"
- Supporting box: "Network Path" with generic cloud/network icon — "Carries TCP segments between endpoints"
- Supporting box: "Server App" with service icon — "Accepts the established connection"
- Supporting box: "Connection State" with handshake/status icon — "Tracks SYN-SENT, SYN-RECEIVED, and ESTABLISHED states"

Arrows and protocol-accurate labels:
1. Arrow from Client to Server labeled "TCP SYN, Seq=x, dst port" 
2. Arrow from Server to Client labeled "TCP SYN-ACK, Seq=y, Ack=x+1" 
3. Arrow from Client to Server labeled "TCP ACK, Ack=y+1" 
4. Small final state arrow or badge between both sides labeled "Connection established"

Add concise callouts near the arrows explaining purpose in plain English:
- "Client asks to start a session"
- "Server acknowledges and agrees"
- "Client confirms receipt"

Add a numbered legend 1-7 in English at the bottom or side:
1. "The client wants to open a TCP connection to the server."
2. "The client sends a SYN segment with its initial sequence number."
3. "The server receives the SYN and reserves connection state."
4. "The server replies with SYN-ACK to acknowledge the client request."
5. "The client receives SYN-ACK and verifies the server response."
6. "The client sends the final ACK to complete the handshake."
7. "Both sides enter the ESTABLISHED state and application data can begin flowing."

Visual composition: executive-friendly infographic, minimal clutter, oversized numbered steps, clear spacing, bold box titles, short captions, strong directional flow, simple protocol annotations, subtle background grid, no claim of audited or production reference architecture. Include a small note box: "Illustrative TCP connection setup flow, not a security certification or cloud reference architecture."

Style and mood: cyberpunk neon fused with warm beige and navy palette; navy background base, warm beige panels, neon cyan/magenta edge glows used sparingly for arrows and highlights; polished editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use generic cloud/network icons only, no vendor branding, no AWS/GCP/Azure logos, no watermarks.

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).