In this post, we explore how to manage EKS Pod Identity associations at scale using Argo CD and AWS Controllers for Kubernetes (ACK), addressing the critical challenge of the eventually consistent EKS Pod Identity API. The guide demonstrates automation techniques to ensure proper IAM role associations before application deployment, maintaining GitOps workflows while preventing permission-related failures.

In this post, we introduce the Slinky Project and explore how it enables organizations to run Slurm workload management within Amazon EKS, combining the deterministic scheduling capabilities of Slurm with Kubernetes' dynamic resource allocation for efficient hybrid workload management. This unified approach allows teams to maximize resource utilization across both batch processing jobs and cloud-native applications without maintaining separate infrastructure silos.

In this post, we explore the latest Amazon Elastic Kubernetes Service (Amazon EKS) Auto Mode features that enhance security, network control, and performance for enterprise Kubernetes deployments. These new capabilities address critical operational challenges including capacity management, network segmentation, enterprise PKI integration, and comprehensive encryption while maintaining the automated cluster management that makes EKS Auto Mode transformative for development teams.

In this post, we explore how to use AWS Identity and Access Management (IAM) Roles Anywhere, supported by HashiCorp Vault PKI, to facilitate joining EKS Hybrid Nodes to an Amazon EKS Cluster. This solution enables businesses to flexibly make use of compute resources outside of AWS by extending an Amazon Elastic Kubernetes Service (Amazon EKS) data plane beyond the AWS Cloud boundary, addressing use cases focused on data sovereignty, low latency communication, and regulatory compliance.

In this post, we explore how KubeArmor, an open source container-aware security enforcement system, enhances the security posture of containerized workloads running on EKS Auto Mode clusters. Although EKS Auto Mode significantly streamlines cluster management by automating control plane and node operations, securing the workloads running within the cluster remains a critical user responsibility.

In this post, we explore advanced traffic routing patterns with the Kubernetes Gateway API through a practical Calendar web application example, demonstrating how it streamlines and standardizes application connectivity and service mesh integration in Kubernetes. The post covers three key use cases: exposing applications to external clients through hostname-based routing, implementing canary deployments between microservices using gRPC traffic splitting, and controlling egress traffic to external services with security policies.

In this post, we explore how AWS and NVIDIA Run:ai are extending GPU fractionalization and orchestration capabilities beyond traditional cloud regions to edge environments, including AWS Local Zones, Outposts, and EKS Hybrid Nodes. The collaboration addresses the growing demand for distributed AI/ML workloads that require efficient GPU resource management across geographically separated locations while maintaining consistent performance, compliance, and cost optimization .

<p>Today, we’re announcing new network observability features in <a href="https://aws.amazon.com/eks/" target="_blank">Amazon Elastic Kubernetes Service (EKS)</a> that provide deeper insights into your container networking environment. These new capabilities help you better understand, monitor, and troubleshoot your Kubernetes network landscape in AWS.<br> <br> Customers are increasingly deploying microservices to expand and incrementally innovate with software in the AWS cloud, while using Amazon EKS as the underlying platform to run their applications. With enhanced container network observability, customers can leverage granular, network-related metrics for better proactive anomaly detection across cluster traffic, cross-AZ flows, and AWS services. Using these metrics, customers can better measure system performance and visualize the underlying metrics using their preferred observability stack.<br> <br> Additionally, EKS now provides network monitoring visualizations in the AWS console that accelerate and enhance precise troubleshooting for faster root cause analysis. Customers can also leverage these visual capabilities to pinpoint top-talkers and network flows causing retransmissions and retransmission timeouts, eliminating blind spots during incidents. These network monitoring features in EKS are powered by <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-NetworkFlowMonitor.html" target="_blank">Amazon CloudWatch Network Flow Monitor.</a><br> <br> Enhanced container network observability for EKS is available in all commercial AWS Regions where CloudWatch Network Flow Monitor is <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-NetworkFlowMonitor-Regions.html" target="_blank">available</a>. To learn more, visit the <a href="https://docs.aws.amazon.com/eks/latest/userguide/network-observability.html" target="_blank">Amazon EKS documentation</a> and AWS News Launch Blog.&nbsp;</p>

Snowflake Corporate IT Cloud Operations reached a critical juncture in its cloud infrastructure evolution. Managing large-scale containerized workloads on Amazon Elastic Kubernetes Service (Amazon EKS) demanded a modern, secure, and efficient operating system. The existing setup, running on Amazon Linux 2 (AL2), was functional but presented several challenges. Security hardening required frequent updates and patching, […]

Microservices and containers are revolutionizing how modern applications are built, deployed, and managed in the cloud. However, developing and operating microservices can introduce significant complexity, often requiring developers to spend valuable time on cross-cutting concerns like service discovery, state management, and observability. Dapr (Distributed Application Runtime) is an open source runtime for building microservices on […]

In this post, we show you how to implement comprehensive monitoring for Amazon Elastic Kubernetes Service (Amazon EKS) workloads using AWS managed services. This solution demonstrates building an EKS platform that combines flexible compute options with enterprise-grade observability using AWS native services and OpenTelemetry.

In this post, we demonstrate how to deploy the DeepSeek-R1-Distill-Qwen-32B model using AWS DLCs for vLLMs on Amazon EKS, showcasing how these purpose-built containers simplify deployment of this powerful open source inference engine. This solution can help you solve the complex infrastructure challenges of deploying LLMs while maintaining performance and cost-efficiency.

This post was co-written with Frederic Haase and Julian Blau with BASF Digital Farming GmbH. At xarvio – BASF Digital Farming, our mission is to empower farmers around the world with cutting-edge digital agronomic decision-making tools. Central to this mission is our crop optimization platform, xarvio FIELD MANAGER, which delivers actionable insights through a range […]

AWS Backup now supports Amazon EKS, providing a fully managed, centralized solution to back up and restore Kubernetes clusters and application data without requiring custom scripts or third-party tools.

Amazon EKS introduces Container Network Observability, providing enhanced visibility into Kubernetes workload traffic and performance insights to help teams monitor and troubleshoot microservice environments.

Commits • eac1f3c: (Backport v1.2.x)fix: prevent hash collisions while resolving subnets, security groups and AMIs from nodeclass selectors (#8660) (Amanuel Engeda) #8660

Chores • bump upstream karpenter version (#8593) #8593 (Jigisha Patil) Commits • 7f8a83d: (Backport v1.3.x)fix: prevent hash collisions while resolving subnets, security groups and AMIs from nodeclass selectors (#8659) (Amanuel Engeda) #8659

Chores • bump upstream karpenter version (#8594) #8594 (Jigisha Patil) Commits • f23af71: (Backport v1.4.x)fix: prevent hash collisions while resolving subnets, security groups and AMIs from nodeclass selectors (#8658) (Amanuel Engeda) #8658

Bug Fixes • make toolchain failing due to deletion of asciicheck for v1.5.x (#8652) #8652 (Amanuel Engeda) Commits • 0f47193: (Backport v1.5.x)fix: prevent hash collisions while resolving subnets, security groups and AMIs from nodeclass selectors (#8657) (Amanuel Engeda) #8657

Bug Fixes • make toolchain failing due to deletion of asciicheck for v1.6.x (#8653) #8653 (Amanuel Engeda) Chores • bump upstream karpenter version (#8595) #8595 (Jigisha Patil) Commits • 9e59a13: (Backport v1.6.x)fix: prevent hash collisions while resolving subnets, security groups and AMIs from nodeclass selectors (#8656) (Amanuel Engeda) #8656

Bug Fixes • ensure filtered offering is available for capacity blocks (#8518) #8518 (Jason Deal) Commits • bump sigs.k8s.io/karpenter to v1.7.1 (#8500) #8500 (Jason Deal) • 4abf673: (Backport v1.7.x)fix: prevent hash collisions while resolving subnets, security groups and AMIs from nodeclass selectors (#8655) (Amanuel Engeda) #8655