In Teleport 8, we introduced the TLS Routing feature that can multiplex all client connections on a single TLS/SSL port. Recently we've added support for TLS Routing for Database Access when Teleport is deployed behind an AWS Application Load Balancer (ALB). In this article, we will take a deep look at the problem with Teleport behind an ALB and how we solved it.
It’s the news everyone’s been waiting for: Teleport’s version 11 release! This release is packed with features from SFTP support all the way to GitHub Actions Machine ID compatibility. Let’s dive in!
Kubernetes is a very complex product where creating and managing clusters requires a great deal of knowledge on a wide range of topics. The introduction of managed clusters brought simplicity to the process allowing users to focus on extracting the most out of the system. One of the areas of most interest and different configurations is authentication and authorization. In authentication, the main objective, and most critical of all, is to ensure the identity and validity of users and machines.
As companies increasingly move to remote workforces, the need for secure and rapid offboarding has never been greater. Flywheel, a digital agency that specializes in healthcare and life sciences, has found great success using Teleport to streamline its offboarding process. Flywheel had been using a traditional VPN solution to grant access to customer environments, but found the process to be slow and cumbersome.
One of the most important features Teleport has to offer is that it centralizes all of your infrastructure’s audit logging into one central place, mapping every query, every command and every session to an individual user's identity. As you hire more engineers and resources scale, it can become increasingly difficult to manage all of this log data. Luckily Teleport’s extensibility makes this log data extremely easy to format, export and monitor all in a secure, event-driven way.
