--- title: Concurrent Session Control for SSH and Kubernetes description: Teleport 4.4 introduces concurrent session control for SSH and Kubernetes, adding max_connections and max_sessions configuration values to limit how many... canonical: https://daily.dev/posts/concurrent-session-control-for-ssh-and-kubernetes-nt0dn6fdd twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Concurrent Session Control for SSH and Kubernetes | daily.dev og:description: Teleport 4.4 introduces concurrent session control for SSH and Kubernetes, adding max_connections and max_sessions configuration values to limit how many... og:url: https://daily.dev/posts/concurrent-session-control-for-ssh-and-kubernetes-nt0dn6fdd og:image: https://api.daily.dev/og/posts/NT0dn6FDd.png og:image:alt: Concurrent Session Control for SSH and Kubernetes og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Concurrent Session Control for SSH and Kubernetes **[Teleport](https://daily.dev/sources/teleport)** · 5 min read · 0 upvotes · 0 comments ## Summary Teleport 4.4 introduces concurrent session control for SSH and Kubernetes, adding max_connections and max_sessions configuration values to limit how many sessions a user can open, helping organizations meet AC-10 compliance controls such as FedRAMP requirements. Attempts to exceed limits generate new audit log events. The release also adds beta session streaming, letting session recordings stream directly to S3, GCS, or S3-compatible storage without touching local disk, improving performance and security. Additional fixes and improvements include SPDY ping support for Kubernetes connections, updated dependencies, and audit log enhancements. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I limit the number of concurrent SSH sessions a user can open in Teleport 4.4? Teleport 4.4 adds two configuration values, max_connections and max_sessions, set under a role's options. max_connections limits total concurrent connections to nodes per user across a cluster; max_sessions limits session channels per single SSH connection, matching the behavior of sshd's MaxSessions setting for OpenSSH clients. _Track access-control features like this as Teleport evolves by following updates on daily.dev._ ### What storage backends does Teleport support for streaming SSH session recordings? Teleport's beta session streaming feature, introduced in version 4.4, supports S3, Google Cloud Storage, S3-compatible backends like IBM Cloud Object Storage, and local file storage with multipart upload. Streaming sessions directly to storage avoids writing recordings to the host disk, improving both performance and security for long sessions. _Developers weighing session-recording backends can keep up with tooling changes on daily.dev._ ### What audit event does Teleport log when a user exceeds max_connections or max_sessions limits? Teleport logs a sessctl.limit event with code T1006W to the audit log when a user attempts to exceed the max_connections or max_sessions restraints. The event includes fields like max, proto, server_id, sessctl_kind, and the user who triggered it, supporting compliance tracking such as AC-10. _Security teams tracking compliance-driven audit logging can follow such changes on daily.dev._ ## Similar posts on daily.dev - [Updates to Kubernetes audit logging, network flow logs, and SSH records](https://daily.dev/posts/updates-to-kubernetes-audit-logging-network-flow-logs-and-ssh-records-p1hc5y2bj) · Tailscale · 3 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#ssh](https://daily.dev/tags/ssh) [View this post on daily.dev](https://daily.dev/posts/concurrent-session-control-for-ssh-and-kubernetes-nt0dn6fdd) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Concurrent Session Control for SSH and Kubernetes","url":"https://daily.dev/posts/concurrent-session-control-for-ssh-and-kubernetes-nt0dn6fdd","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/concurrent-session-control-for-ssh-and-kubernetes-nt0dn6fdd"},"datePublished":"2026-08-23T12:23:09.260Z","dateModified":"2026-08-23T12:58:15.600Z","description":"Teleport 4.4 introduces concurrent session control for SSH and Kubernetes, adding max_connections and max_sessions configuration values to limit how many...","image":"https://media.daily.dev/image/upload/s--OHB84bZF--/f_auto/v1722860399/public/Placeholder%2010","thumbnailUrl":"https://media.daily.dev/image/upload/s--OHB84bZF--/f_auto/v1722860399/public/Placeholder%2010","isAccessibleForFree":true,"articleSection":"Teleport","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Teleport","logo":"https://media.daily.dev/image/upload/s--Dw-Bbw6O--/c_limit,w_256/f_auto,q_auto/v1787487494/logos/teleport?_a=BAMAMicg0","url":"https://daily.dev/sources/teleport"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/concurrent-session-control-for-ssh-and-kubernetes-nt0dn6fdd","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,ssh","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Teleport","item":"https://daily.dev/sources/teleport"},{"@type":"ListItem","position":3,"name":"Concurrent Session Control for SSH and Kubernetes"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/concurrent-session-control-for-ssh-and-kubernetes-nt0dn6fdd#faq","mainEntity":[{"@type":"Question","name":"How do I limit the number of concurrent SSH sessions a user can open in Teleport 4.4?","acceptedAnswer":{"@type":"Answer","text":"Teleport 4.4 adds two configuration values, max_connections and max_sessions, set under a role's options. max_connections limits total concurrent connections to nodes per user across a cluster; max_sessions limits session channels per single SSH connection, matching the behavior of sshd's MaxSessions setting for OpenSSH clients. Track access-control features like this as Teleport evolves by following updates on daily.dev."}},{"@type":"Question","name":"What storage backends does Teleport support for streaming SSH session recordings?","acceptedAnswer":{"@type":"Answer","text":"Teleport's beta session streaming feature, introduced in version 4.4, supports S3, Google Cloud Storage, S3-compatible backends like IBM Cloud Object Storage, and local file storage with multipart upload. Streaming sessions directly to storage avoids writing recordings to the host disk, improving both performance and security for long sessions. Developers weighing session-recording backends can keep up with tooling changes on daily.dev."}},{"@type":"Question","name":"What audit event does Teleport log when a user exceeds max_connections or max_sessions limits?","acceptedAnswer":{"@type":"Answer","text":"Teleport logs a sessctl.limit event with code T1006W to the audit log when a user attempts to exceed the max_connections or max_sessions restraints. The event includes fields like max, proto, server_id, sessctl_kind, and the user who triggered it, supporting compliance tracking such as AC-10. Security teams tracking compliance-driven audit logging can follow such changes on daily.dev."}}]} ```