# Amazon Elastic Kubernetes Service AWS managed service for deploying, operating, and scaling Kubernetes clusters. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Fault tolerant distributed training on Amazon EKS using NVRx DevFeed: [Fault tolerant distributed training on Amazon EKS using NVRx]() Original publisher: [Read original article]() Author: Aravind Neelakantan Published: 2026-09-16T18:59:25Z Content type: tutorial Language: en Sources: [Artificial Intelligence]() Topics: [NCCL](), [Amazon Elastic Kubernetes Service](), [PyTorch](), [distributed-training](), [Resilience](), [GPU]() Tags: [advanced-300](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [async](), [benchmarks](), [distributed-training](), [gpu](), [pytorch](), [resiliency](), [technical-how-to]() ### AI overview This tutorial integrates NVIDIA Resiliency Extension (NVRx) with PyTorch FSDP training on Amazon EKS. It covers asynchronous checkpointing, in-process restart, and in-job restart, and reports H100 benchmarks at 2- to 8-node scale with 99%+ training efficiency and recovery measured in seconds. ### Source excerpt Integrate NVIDIA Resiliency Extension (NVRx) into PyTorch FSDP training on Amazon EKS to overlap checkpoint I/O with training and recover from GPU faults in seconds. This post covers async checkpointing, in-process restart, and ft_launcher in-job restart, with H100 benchmarks at 2 to 8 nodes showing 99%+ training efficiency and second-scale recovery. ## Simplify and support your TorchServe workloads using Ray Serve Deep Learning Containers DevFeed: [Simplify and support your TorchServe workloads using Ray Serve Deep Learning Containers]() Original publisher: [Read original article]() Author: Ananth Raghavendra Published: 2026-09-09T15:51:29Z Content type: tutorial Language: en Sources: [Artificial Intelligence]() Topics: [Inference](), [model-deployment](), [Amazon Elastic Kubernetes Service](), [Containers](), [vlm](), [GPU](), [PyTorch]() Tags: [amazon-eks](), [containers](), [gpu](), [inference](), [intermediate-200](), [pytorch](), [technical-how-to](), [vulnerabilities]() ### AI overview The article introduces AWS Ray Serve Deep Learning Containers as a maintained, pre-tested inference option for teams moving from unmaintained TorchServe workloads. It demonstrates deploying a vision-language model on Amazon EKS using a single GPU node. ### Source excerpt TorchServe is no longer maintained, leaving teams to own the entire GPU inference stack. The AWS Ray Serve Deep Learning Container is a supported, pre-tested container with the framework, GPU drivers, and serving layer already assembled. This post walks through deploying a vision-language model on Amazon EKS using the Ray Serve DLC on a single GPU node. ## Cut GPU inference cold start from 8 minutes to less than a minute DevFeed: [Cut GPU inference cold start from 8 minutes to less than a minute]() Original publisher: [Read original article]() Author: Sajjan Gundapuneedi Published: 2026-09-03T18:30:00Z Content type: article Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [GPU](), [Inference](), [model-deployment](), [Amazon Elastic Kubernetes Service](), [CUDA](), [Optimization](), [Amazon S3](), [Kubernetes]() Tags: [ai-infrastructure](), [amazon-eks](), [aws-marketplace](), [cpu](), [cuda](), [gpu](), [inference](), [kubernetes](), [large-language-models](), [optimization](), [post-contributed](), [s3](), [sponsor-aws-marketplace](), [sponsored-post-contributed]() ### AI overview The article measures GPU model startup from pod creation to the first inference response and identifies six sequential phases. It reports that CUDA kernel recompilation dominates startup for a 64 GB model, while S3 weight downloads dominate for a 203 GB model. Configuration and platform changes reduced warm-node startup times by 80-93%, with additional cold-node improvements requiring Amazon EKS Auto Mode. ### Source excerpt We instrumented the full path from pod creation to first inference response on a GPU node running a 70B-class model. The post Cut GPU inference cold start from 8 minutes to less than a minute appeared first on The New Stack. ## Fast model loading for AI inference on Amazon EKS DevFeed: [Fast model loading for AI inference on Amazon EKS]() Original publisher: [Read original article]() Author: Sajjan Gundapuneedi Published: 2026-09-01T15:48:15Z Content type: article Language: en Sources: [Containers]() Topics: [Inference Performance](), [Amazon Elastic Kubernetes Service](), [Amazon S3](), [Language models]() Tags: [advanced-300](), [ai](), [ai-inference](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [best-practices](), [cuda](), [gpu](), [inference](), [kubernetes](), [language-models](), [pytorch](), [s3](), [sglang](), [startup](), [vllm]() ### AI overview The article analyzes cold-start delays for AI inference pods on Amazon EKS. It finds that startup bottlenecks vary by model size: torch.compile dominates for smaller models, while loading weights from S3 to GPU memory dominates for larger models. Configuration changes to Run:ai Model Streamer reduce model-loading time on repeat launches. ### Source excerpt When you scale AI inference on Amazon EKS, every new pod must load model weights into GPU memory before serving traffic. We investigated where cold-start time goes and found two configuration-only changes to Run:ai Model Streamer that cut model startup time by 80-93% on subsequent launches, with no code changes. ## Deploying IPv6-first EKS on AWS: What Still Doesn't Work, and What It Saves DevFeed: [Deploying IPv6-first EKS on AWS: What Still Doesn't Work, and What It Saves]() Original publisher: [Read original article]() Author: Spiro Stathakis Published: 2026-08-14T08:57:28Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Amazon Elastic Kubernetes Service](), [Amazon Web Services](), [VPC](), [networking](), [cloud-infrastructure](), [Kubernetes]() Tags: [2026](), [amazon](), [amazon-elastic-kubernetes-service](), [aws](), [cni](), [competition](), [cost](), [ip](), [ipv4](), [ipv6](), [kubernetes](), [nat](), [networking](), [networks](), [vpc]() ### AI overview A field report on deploying an IPv6-first Amazon Elastic Kubernetes Service platform on AWS. It explains how IPv6 pods, VPC networking, and an egress-only Internet gateway reduce dependence on NAT gateways and public IPv4 addresses, while legacy IPv4-only dependencies such as databases, payment APIs, and container registries still impose compatibility requirements and costs. ### Source excerpt In this field report on IPv6-first Amazon Elastic Kubernetes Service (EKS), the isp6 team shares which dependencies still drag IPv4 back in, what they learnt from /28s, and why the saving is large but not automatic. ## Pulling multi-gigabyte container images in seconds on Amazon EKS DevFeed: [Pulling multi-gigabyte container images in seconds on Amazon EKS]() Original publisher: [Read original article]() Author: Sri Saran Balaji Vellore Rajakumar Published: 2026-08-10T16:00:00Z Content type: article Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Amazon Elastic Kubernetes Service](), [container images](), [Machine learning](), [autoscaling](), [CUDA]() Tags: [ai-infrastructure](), [amazon-eks](), [autoscaling](), [aws-marketplace](), [container](), [container-images](), [containers](), [cuda](), [kubernetes](), [machine-learning](), [post-contributed](), [sponsor-aws-marketplace](), [sponsored-post-contributed]() ### AI overview This article explains how a production ML platform on Amazon EKS reduced multi-minute pulls of roughly 30 GB container images to seconds. Profiling found that software use of available hardware, rather than network bandwidth or the registry, was the main constraint; the resulting changes are available by default in EKS Auto Mode and were contributed upstream to containerd and the SOCI snapshotter. ### Source excerpt When the image is the bottleneck: Machine learning changed what a container image looks like. A typical application ships in The post Pulling multi-gigabyte container images in seconds on Amazon EKS appeared first on The New Stack. ## How EKS is simplifying Kubernetes cluster lifecycle management DevFeed: [How EKS is simplifying Kubernetes cluster lifecycle management]() Original publisher: [Read original article]() Author: Spyros Angelopoulos Published: 2026-08-01T15:00:00Z Content type: article Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Amazon Elastic Kubernetes Service](), [Kubernetes](), [Availability](), [Deployment]() Tags: [availability](), [aws-marketplace](), [cloud-services](), [deployment](), [devops](), [kubernetes](), [lifecycle](), [post-contributed](), [sponsor-aws-marketplace](), [sponsored-post-contributed](), [upgrades]() ### AI overview The article describes the operational challenges of Kubernetes upgrades and EKS efforts to make cluster lifecycle management easier. It highlights Extended Support, which broadens the availability of each Kubernetes version to 26 months, giving organizations more time to validate and schedule upgrades. ### Source excerpt Kubernetes moves at a pace of three minor version releases per year, and staying current is not optional if you The post Kubernetes upgrades don't have to break things: How EKS is making cluster lifecycle management simpler and safer appeared first on The New Stack. ## From intent to enforcement: Lessons from operating Kubernetes controllers at scale DevFeed: [From intent to enforcement: Lessons from operating Kubernetes controllers at scale]() Original publisher: [Read original article]() Author: Sri Saran Balaji Vellore Rajakumar Published: 2026-07-17T12:00:00Z Content type: article Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Kubernetes](), [Amazon Elastic Kubernetes Service](), [VPC]() Tags: [amazon-eks](), [aws-marketplace](), [clusters](), [controllers](), [declarative](), [kubernetes](), [networking](), [platform-engineering](), [policy-controller](), [post-contributed](), [reconciliation](), [scale](), [security](), [sponsor-aws-marketplace](), [sponsored-post-contributed](), [vpc]() ### AI overview This article explains lessons from operating Kubernetes controllers at scale in Amazon EKS. It focuses on how the Network Policy Controller and VPC Resource Controller reconcile declared intent with changing cluster state to enforce network traffic and AWS resource access policies. ### Source excerpt Kubernetes controllers are what make the platform's declarative model real. They observe the state, reconcile toward the intent, and keep The post From intent to enforcement: Lessons from operating Kubernetes controllers at scale appeared first on The New Stack. ## AWS Weekly Roundup: Claude Sonnet 5 on AWS, Amazon WorkSpaces for AI agents, AWS service availability updates, and more (July 6, 2026) DevFeed: [AWS Weekly Roundup: Claude Sonnet 5 on AWS, Amazon WorkSpaces for AI agents, AWS service availability updates, and more (July 6, 2026)]() Original publisher: [Read original article]() Author: Daniel Abib Published: 2026-07-06T15:46:43Z Content type: news Language: en Sources: [AWS News Blog]() Topics: [Amazon WorkSpaces](), [Amazon EC2](), [AWS CloudFormation](), [Amazon Elastic Kubernetes Service](), [Kubernetes]() Tags: [ai-agents](), [amazon-bedrock](), [amazon-cloudwatch](), [amazon-ec2](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [amazon-opensearch-service](), [amazon-sagemaker-ai](), [amazon-workspaces](), [aws](), [aws-certificate-manager](), [aws-cloudformation](), [claude](), [kubernetes](), [news](), [tls](), [week-in-review]() ### AI overview AWS weekly roundup covering Amazon WorkSpaces for AI agents, Claude Sonnet 5 availability, service availability updates, and recent launches including EC2 instances, CloudFormation Express mode, EKS Kubernetes rollbacks, and ACM ACME support. ### Source excerpt A couple of editions ago I wrote about what I find so energizing about working with startups. Last week I got a fresh dose of it: I spent a few days with the AWS Startups team, listening to stories of founders talking about the problems they're actually solving. One story that stayed with me came [...] ## Upgrade Amazon EKS clusters with confidence using Kubernetes version rollbacks DevFeed: [Upgrade Amazon EKS clusters with confidence using Kubernetes version rollbacks]() Original publisher: [Read original article]() Author: Micah Walter Published: 2026-07-01T17:20:30Z Content type: release Language: en Sources: [AWS News Blog]() Topics: [Amazon Elastic Kubernetes Service]() Tags: [amazon-eks](), [amazon-elastic-kubernetes-service](), [compute](), [feature](), [kubernetes](), [launch](), [news](), [safety]() ### AI overview Amazon EKS introduces Kubernetes version rollbacks, allowing administrators to reverse an upgrade to the prior version within seven days. The feature includes rollback-readiness checks for node compatibility and add-on dependencies. ### Source excerpt Learn how Kubernetes version rollbacks for Amazon EKS let you reverse cluster upgrades within seven days. This new feature provides a safety net for upgrade failures--no cluster rebuilds required--turning Kubernetes version upgrades into a reversible, low-risk operation. ## How AWS Powers Gradle's Open Source Build Tool DevFeed: [How AWS Powers Gradle's Open Source Build Tool]() Original publisher: [Read original article]() Author: Bo Zhang Published: 2026-06-09T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Amazon Web Services](), [ci](), [Testing](), [Open Source](), [Security](), [AWS IAM](), [Amazon EC2](), [Amazon Elastic Kubernetes Service](), [Amazon S3](), [OpenID connect (OIDC)]() Tags: [amazon-ec2](), [amazon-eks](), [amazon-rds](), [aws](), [aws-identity-and-access-management-iam](), [ci](), [gradle](), [oidc](), [open-source](), [security](), [testing]() ### AI overview The article explains how AWS supports Gradle's open source build tool, including plugin distribution through Amazon S3, large-scale builds and tests on Amazon EC2 and Amazon EKS, performance tracking with Amazon RDS, and layered security and observability services. ### Source excerpt The Gradle Build Tool runs a lot of the world's software. Millions of developers use it every day, and almost every Android app on your phone was built with it. So somebody, somewhere, is kicking off a Gradle build right now. And the next one. And a thousand more in the next minute. For all of them, it has to be fast, and it has to be there. That isn't free. Behind the open source project sits a plugin portal serving hundreds of millions of downloads a month, a CI fleet running millions of tests, a performance lab watching for regressions, and the security tooling that guards a supply chain a lot of the industry depends on. All of it runs on AWS. Here's how. Downloading plugins The Gradle Plugin Portal at plugins.gradle.org is where the community publishes the plugins that extend Gradle. Every plugin JAR it serves (thousands of them, downloaded around 200 million times a month) lives in Amazon S3. That's what lets us be the front door for the plugin ecosystem without running a fleet of file servers ourselves. Building and testing Gradle itself Most of our AWS bill goes here. Every commit to Gradle triggers hundreds of separate builds and tens of thousands of tests across our supported operating systems and architectures. That fleet runs on: Amazon EC2, with auto-scaling to match capacity to demand. Amazon EKS, which orchestrates our containerized Test Distribution agents. Amazon ECR, which stores the agent container images. Keeping Gradle fast A build tool only earns trust if it stays fast. Every commit runs through our performance test suite, and the results land in Amazon RDS, where we compare against history and catch regressions before they reach users. Securing the build Protecting a build tool means protecting a supply chain. Our CI authenticates to AWS through AWS Identity and Access Management (IAM) with GitHub OIDC. That gives us keyless, short-lived credentials, and any secrets we still need are pulled on demand from AWS Secrets Manager and AWS Systems Man ## Investigate Amazon EKS Audit Logs with Teleport Identity Security DevFeed: [Investigate Amazon EKS Audit Logs with Teleport Identity Security]() Original publisher: [Read original article]() Author: info@goteleport.com (Ben Arent) Published: 2025-11-11T00:00:00Z Content type: release Language: en Sources: [Teleport]() Topics: [Amazon Elastic Kubernetes Service](), [audit](), [Security](), [Kubernetes](), [Amazon Web Services]() Tags: [audit](), [cloudtrail](), [collection](), [kubectl](), [kubernetes](), [metrics](), [security]() ### AI overview Teleport 18 adds official support for importing Amazon EKS Audit Logs into Teleport Identity Security. The feature provides unified visibility into Kubernetes API activity, including actions performed outside Teleport, and supports correlating EKS activity with Teleport access and AWS audit data. ### Source excerpt Learn how Teleport 18 brings Amazon EKS Audit Logs into Identity Security, giving teams unified visibility into all Kubernetes API activity--including shadow access. ## Posts from the Past, October 2025 DevFeed: [Posts from the Past, October 2025]() Original publisher: [Read original article]() Author: Scott Lowe Published: 2025-10-22T18:00:00Z Content type: article Language: en Sources: [Scott's Weblog]() Topics: [Amazon Elastic Kubernetes Service](), [Kubernetes](), [Amazon Web Services](), [Infrastructure as code](), [Azure]() Tags: [2025](), [amazon-elastic-kubernetes-service](), [ansible](), [aws](), [azure](), [cilium](), [cli](), [cloud](), [cni](), [containers](), [cri-o](), [devops](), [docker](), [go](), [iac](), [japan](), [k8s](), [kubernetes](), [kubernetes-clusters](), [linux](), [networking](), [oci](), [openstack](), [security](), [vagrant]() ### AI overview A retrospective roundup revisiting the author's Kubernetes, cloud infrastructure, and container-related posts published in October across several years. It highlights work involving Pulumi, Amazon EKS, Bottlerocket OS, Azure Kubernetes Service, Cluster API, AWS, kubeadm, Ansible, Vagrant, and OpenStack. ### Source excerpt Every now and then, I publish one of these "Posts from the Past" articles that looks back on content I've created and posted over the life of this site. This year marks 20 years of content--I can hardly believe it! Don't worry, though; you won't have to go through 20 years of past posts. Here is a selection of posts from mid- to late October over the last decade or so. I hope you find something useful, informative, or at least entertaining! October 2024 Last year I shared information on how to use Pulumi to stand up an Amazon Elastic Kubernetes Service (EKS) cluster with Bottlerocket OS on the Kubernetes nodes--without using any higher-level Pulumi components. October 2022 In 2022, after getting irritated with what I felt was a poor user experience when accessing Azure Kubernetes Service (AKS) clusters created with Pulumi, I published this post on how to change the Kubeconfig file for a more streamlined user experience. October 2021 Cluster API is the name of the game for multiple posts in October 2021. First I wrote this article on kustomize transformer configurations for Cluster API v1beta1 (so that you can use kustomize to manipulate Cluster API manifests), followed up later that month with an article on influencing Cluster API AMI selection. I also touched upon using the external (out of tree) cloud provider for AWS that month, a topic I am revisiting soon as I explore integrating Talos Linux with AWS. October 2020 More Cluster API content--this time discussing IaC considerations for Cluster API (think things like integrating workload clusters with existing AWS workloads or services). October 2019 In October 2019 I explored using jk to programmatically create Kubernetes manifests, and discussed how to use kustomize with kubeadm configuration files. October 2018 Plenty of articles discuss the use of kubeadm to bootstrap Kubernetes clusters (including a few I wrote!), but what of talking about using kubeadm to stand up an etcd cluster? I've got you covered! October 2 ## 5 Ways to Keep AWS Fast with Just-in-Time Access DevFeed: [5 Ways to Keep AWS Fast with Just-in-Time Access]() Original publisher: [Read original article]() Author: jpitts@goteleport.com (Jack Pitts) Published: 2025-08-27T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Amazon Web Services](), [JIT](), [Amazon Elastic Kubernetes Service](), [AWS IAM](), [audit trail](), [Security](), [Amazon EC2](), [AI Agent](), [Amazon Bedrock](), [CI/CD](), [Amazon DocumentDB](), [PostgreSQL]() Tags: [ai-agent](), [amazon-bedrock](), [amazon-rds](), [audit-trail](), [aws](), [aws-iam](), [ci-cd](), [jit](), [least-privilege](), [postgresql](), [security]() ### AI overview This article explains how Teleport's just-in-time access model can help govern fast-moving AWS environments. It describes ephemeral, policy-defined privileges for humans, machines, and AI agents, with least-privilege controls, approvals, expirations, and audit visibility across use cases including EKS, EC2, AWS Console, CI/CD, and AI access. ### Source excerpt Learn how just-in-time access accelerates EKS, EC2, AWS Console, CI/CD, and AI access while eliminating standing privileges and ensuring full audit visibility. ## Building ClickHouse BYOC (Bring Your Own Cloud) on AWS DevFeed: [Building ClickHouse BYOC (Bring Your Own Cloud) on AWS]() Original publisher: [Read original article]() Author: Jianfei Hu; Yiyang Shao Published: 2025-03-12T15:09:23Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Amazon Web Services](), [cloud-infrastructure](), [Amazon VPC](), [Automation](), [Provisioning](), [Amazon Elastic Kubernetes Service](), [network security](), [Security](), [AWS IAM](), [Kubernetes]() Tags: [automation](), [aws](), [clickhouse](), [cloud](), [iam](), [infrastructure](), [kubernetes](), [network](), [network-security](), [provisioning](), [security](), [vpc]() ### AI overview This article explains how ClickHouse built a Bring Your Own Cloud (BYOC) offering on AWS. It covers deploying ClickHouse Cloud into customer-controlled VPCs and the engineering challenges of infrastructure automation, networking, security, compliance, resource management, auto-provisioning, scaling, and simplifying Kubernetes operations. ### Source excerpt Learn how we built ClickHouse BYOC (Bring Your Own Cloud) on AWS, tackling challenges like infrastructure automation, network security, and resource management to deliver a seamless, fully managed deployment within customer-controlled environments. ## Maximizing your reliability on AWS DevFeed: [Maximizing your reliability on AWS]() Original publisher: [Read original article]() Author: Andre Newman Published: 2025-01-13T00:00:00Z Content type: tutorial Language: en Sources: [Gremlin Blog]() Topics: [Amazon Web Services](), [Shared Responsibility Model](), [Amazon EC2](), [Availability](), [cloud-infrastructure](), [Amazon Elastic Kubernetes Service](), [App]() Tags: [amazon](), [amazon-ec2](), [availability](), [aws](), [cloud](), [compute](), [how-to](), [infrastructure](), [learn](), [shared-responsibility-model](), [use-cases]() ### AI overview This article explains how to improve workload reliability on AWS despite the cloud platform's limited visibility and shared responsibility model. It examines failure modes and mitigation options for services including Amazon EC2, Amazon EKS, and ECS, with emphasis on resilience, recoverability, fault tolerance, and EC2 auto-scaling groups. ### Source excerpt Learn how to maximize reliability when running workloads on Amazon EC2, EKS, ECS, and other services. ## New Chainguard Images July-September 2024: Hardened, minimal containers DevFeed: [New Chainguard Images July-September 2024: Hardened, minimal containers]() Original publisher: [Read original article]() Published: 2024-10-03T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [releases](), [Containers](), [GitLab](), [Amazon Elastic Kubernetes Service](), [PyTorch]() Tags: [amazon-eks](), [chainguard](), [chainguard-images](), [container-images](), [container-registry](), [containers](), [gitlab](), [images-directory](), [kubernetes](), [pytorch](), [releases]() ### AI overview Chainguard reports approximately 192 new hardened, minimal images released from July through September 2024, including FIPS-enabled images and images for GitLab, Amazon EKS, and PyTorch. ### Source excerpt Check out Chainguard's new image releases over summer 2024, including container images for GitLab, Amazon EKS, and PyTorch applications. ## Containers on AWS: Comparing ECS and EKS DevFeed: [Containers on AWS: Comparing ECS and EKS]() Original publisher: [Read original article]() Author: Guillermo Ojeda Published: 2024-04-22T23:24:13Z Content type: article Language: en Sources: [Guille Ojeda]() Topics: [Amazon Elastic Container Service](), [Amazon Elastic Kubernetes Service](), [Containers](), [Amazon Web Services](), [Orchestration]() Tags: [amazon-elastic-kubernetes-service](), [architecture](), [article](), [aws](), [container](), [containers](), [ecs](), [kubernetes](), [orchestration]() ### AI overview This article compares Amazon Elastic Container Service (ECS) and Amazon Elastic Kubernetes Service (EKS) for running and scaling containerized applications on AWS. It introduces container orchestration, explains ECS features, components, and EC2 and Fargate launch types, and discusses factors for choosing between the services. ### Source excerpt Containers offer a lightweight, portable, and scalable solution for running software consistently across different environments. But as the number of containers grows, managing them becomes increasingly complex. That's where container orchestration c... ## Teleport Community Edition license change, Kubecon EU and Teleport Product Updates DevFeed: [Teleport Community Edition license change, Kubecon EU and Teleport Product Updates]() Original publisher: [Read original article]() Author: ben@goteleport.com (Ben Arent) Published: 2024-03-15T00:00:00Z Content type: news Language: en Sources: [Teleport]() Topics: [Kubernetes](), [Kubernetes clusters](), [MFA](), [Amazon Elastic Kubernetes Service](), [Azure](), [Google]() Tags: [announcement](), [aws](), [azure](), [change](), [gke](), [google-cloud](), [kubecon](), [kubecon-eu](), [kubernetes](), [kubernetes-clusters](), [mfa](), [product-updates]() ### AI overview The March newsletter announces that Teleport Community Edition will move to a new commercial license with Teleport 16, including restrictions based on company size, revenue, and resale or embedding. It also covers KubeCon EU plans and recent Kubernetes-related product updates. ### Source excerpt March Newsletter ## Stitch Fix's Move to Kubernetes for More Agile Service Deployment DevFeed: [Stitch Fix's Move to Kubernetes for More Agile Service Deployment]() Original publisher: [Read original article]() Published: 2023-09-19T15:00:00Z Content type: article Language: en Sources: [Stitch Fix]() Topics: [Deployment](), [Kubernetes](), [Amazon Elastic Kubernetes Service](), [Microservice](), [autoscaling](), [Apache Spark]() Tags: [autoscaling](), [deployment](), [emr](), [golang](), [kubernetes](), [microservices](), [nodejs](), [python](), [scala](), [spark]() ### AI overview This article describes Stitch Fix's effort to improve service deployment agility. It explains the platform's self-service goals, its transition from EMR-based Spark infrastructure to EKS, and the deployment challenges that motivated consideration of Kubernetes for core platform services, including standardization across languages, autoscaling, rollback, and traffic segmentation. ### Source excerpt Introduction At Stitch Fix, our data platform is designed to be self-service, with our users taking ownership of their own ETL, models, and microservices. To support this approach, the platform team prioritizes user autonomy and end-to-end tooling in their tooling designs, minimizing the involvement of platform engineers in day-to-day engineering and data science workflows. We regularly evaluate our infrastructure against new frameworks to assess the costs and benefits of potential updates. Last year, we transitioned our EMR-based Spark infrastructure to EKS to take advantage of its benefits. The next logical step was to re-examine how our core platform services were deployed and updated, especially those still deployed directly to instances. We also recognized that Kubernetes, a popular open-source system for handling the deployment of containerized applications, could provide benefits for microservice orchestration beyond just batch compute infrastructure. Our existing instance-based service deployment framework was beginning to show its age in areas that were critical for Stitch Fix, such as the development lifecycle's velocity. As we saw an opportunity to leverage Kubernetes to address these issues, we identified pain points in our service deployment ecosystem. Pain Points Building and deploying services can be a time-consuming process, involving multiple steps and dependencies. We needed a solution that would streamline this process and enable us to deploy services more efficiently. Polyglot environments, where multiple programming languages are used within the same system, can present a challenge for deployment standardization. At Stitch Fix, we use a variety of languages, including Python, Golang, Nodejs, and JVM (Java and Scala), making it difficult to establish consistent deployment practices across the board. We needed a way to deploy polyglot environments in a standardized and efficient manner. Autoscaling and rollback capabilities are essential for manag ## Optimizing Trino using spot instances with Zillow DevFeed: [Optimizing Trino using spot instances with Zillow]() Original publisher: [Read original article]() Author: Santhosh Venkatraman, Rupesh Kumar Perugu, Brian Olsen Published: 2022-12-01T00:00:00Z Content type: article Language: en Sources: [Trino Blog]() Topics: [Amazon Elastic Kubernetes Service](), [AWS Local Zones](), [Amazon Web Services](), [data]() Tags: [amazon](), [amazon-eks](), [analytics](), [aws](), [compute](), [cost](), [summit](), [workflows]() ### AI overview This Trino Summit 2022 session recap describes how Zillow runs Trino on inexpensive but ephemeral spot instances to reduce compute costs. Zillow uses multiple Trino clusters on Amazon EKS, with dedicated on-demand coordinator nodes and a tuned mix of spot and on-demand worker nodes to balance savings and reliability. ### Source excerpt In this installment of the Trino Summit 2022 sessions posts, we jump into an exciting topic by folks from Zillow about running Trino on spot instances. Spot instances are cheap and ephemeral nodes that lead to reduced overall compute costs. Spot instances are cheaper as they are not guaranteed to remain available. In this session, Zillow engineers talk about how they use Trino on spots to take advantage of the cost savings while handling the transitory nature of spots. ## Tutorial: Set up an Identity-Aware Access Proxy as a Bastion Host in AWS DevFeed: [Tutorial: Set up an Identity-Aware Access Proxy as a Bastion Host in AWS]() Original publisher: [Read original article]() Author: info@goteleport.com (Janakiram MSV) Published: 2022-03-10T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Tutorial](), [Amazon Web Services](), [Zero Trust](), [Security](), [Amazon EC2](), [VPC](), [Amazon Elastic Kubernetes Service](), [Amazon RDS](), [DevOps](), [Open Source]() Tags: [amazon-ec2](), [amazon-eks](), [amazon-rds](), [amazon-web-services](), [authentication](), [aws](), [bastion](), [bastion-host](), [best-practices](), [devops](), [how-to](), [let](), [oidc](), [saml](), [security](), [tutorial](), [vpc]() ### AI overview This tutorial explains how to use Teleport, an open-source identity-aware access proxy, as a bastion host for securing AWS infrastructure. It focuses on replacing a traditional bastion host with a Teleport proxy and authentication server for SSH access to EC2 instances, while also describing access to services such as RDS and EKS. ### Source excerpt This post explains how to set-up AWS bastion host based on Teleport identity-aware access proxy. ## 10 Reasons You Need Teleport to Secure Your Apps on AWS DevFeed: [10 Reasons You Need Teleport to Secure Your Apps on AWS]() Original publisher: [Read original article]() Author: info@goteleport.com (Steven Martin) Published: 2021-11-29T00:00:00Z Content type: opinion Language: en Sources: [Teleport]() Topics: [Amazon Web Services](), [Security](), [AWS Management Console](), [Command-line interface](), [Provisioning](), [Amazon EC2](), [Amazon Elastic Kubernetes Service](), [Kubernetes](), [DevOps](), [GitLab](), [Jenkins](), [HashiCorp Vault]() Tags: [aws](), [aws-management-console](), [cli](), [devops](), [ec2](), [gitlab](), [hashicorp-vault](), [jenkins](), [kubernetes](), [provisioning](), [security](), [zero-trust-networking]() ### AI overview A promotional article presents ten reasons to use Teleport for securing applications and infrastructure access on AWS. The supplied sections describe identity-aware, role-based access controls for the AWS Management Console and CLI, temporary elevated access, access controls for EC2, databases, EKS clusters, and DevOps tools, plus zero-trust networking. ### Source excerpt Just in time for re:Invent 2021, here is the list of top 10 things you should know about AWS and Teleport.