Category: *Post Types

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 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 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 explore patterns and practices for building and operating distributed Amazon Elastic Kubernetes Service (Amazon EKS)-based applications effectively. We examine three deployment models – SaaS Provider Hosted, Remote Application Plane, and Hybrid Nodes – each offering distinct advantages for specific use cases as companies scale their software as a service (SaaS) offerings.

In this post, Amazon ECS announces support for IPv6-only workloads, allowing users to run containerized applications in IPv6-only environments without IPv4 dependencies while maintaining compatibility with existing applications and AWS services. The new capability helps organizations address IPv4 address exhaustion challenges, streamline network architecture, improve security posture, and meet compliance requirements for IPv6 adoption.

In this post, we demonstrate how to configure Amazon Route 53 to enable unique failover behavior for each application within multi-tenant Amazon EKS environments across AWS Regions. This solution allows organizations to maintain the cost benefits of shared infrastructure while meeting diverse availability requirements by implementing application-specific health checks that provide granular control over failover scenarios.

In this post, we demonstrate how to use a Raspberry Pi 5 as an Amazon EKS hybrid node to process edge workloads while maintaining cloud connectivity. We show how to set up an EKS cluster that connects cloud and edge infrastructure, secure connectivity using WireGuard VPN, enable container networking with Cilium, and implement a real-world IoT application using an ultrasonic sensor that demonstrates edge-cloud integration.

In this post, we explore the migration path from AWS CodeDeploy to Amazon ECS for blue/green deployments, discussing key architectural differences and implementation considerations. We examine three different migration approaches – in-place update, new service with existing load balancer, and new service with new load balancer – along with their respective trade-offs in terms of complexity, risk, downtime, and cost.

In this post, we introduce an automated, GitOps-driven approach to resource optimization in Amazon EKS using AWS services such as Amazon Managed Service for Prometheus and Amazon Bedrock. The solution helps optimize Kubernetes resource allocation through metrics-driven analysis, pattern-aware optimization strategies, and automated pull request generation while maintaining GitOps principles of collaboration, version control, and auditability.

In this post, we explore how to build highly available Kubernetes applications using Amazon EKS Auto Mode by implementing critical features like Pod Disruption Budgets, Pod Readiness Gates, and Topology Spread Constraints. Through various test scenarios including pod failures, node failures, AZ failures, and cluster upgrades, we demonstrate how these implementations maintain service continuity and maximize uptime in EKS Auto Mode environments.