# Containers Just another Amazon Web Services site This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Automate proxy injection for Amazon EKS on AWS Fargate using Kyverno DevFeed: [Automate proxy injection for Amazon EKS on AWS Fargate using Kyverno]() Original publisher: [Read original article]() Author: Himanshu Bansal Published: 2026-09-01T15:59:57Z Content type: tutorial Language: en Sources: [Containers]() Topics: [Amazon EKS](), [Kubernetes](), [Containers](), [Amazon EC2]() Tags: [advanced-300](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [aws-fargate](), [compliance](), [containers](), [how-to](), [kubernetes](), [policy]() ### AI overview This tutorial shows how to use a Kyverno mutating admission policy to inject corporate HTTP/HTTPS proxy environment variables into Amazon EKS pods running on AWS Fargate. It targets labeled namespaces, avoids per-application manifest changes, and covers validation and proxy bypasses for Fluent Bit and AWS endpoints. ### Source excerpt Learn how to use a Kyverno mutating admission policy to automatically inject corporate proxy environment variables into Amazon EKS on AWS Fargate pods at admission time, delivering consistent egress compliance without modifying application deployment manifests. ## 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. ## Break-glass access for Amazon EKS when federated identity fails DevFeed: [Break-glass access for Amazon EKS when federated identity fails]() Original publisher: [Read original article]() Author: Sam Mukherjee Published: 2026-08-26T16:20:28Z Content type: article Language: en Sources: [Containers]() Topics: [Amazon EKS](), [AWS Identity and Access Management (IAM)](), [Infrastructure as code](), [MFA](), [Authorization](), [iac-security](), [migration]() Tags: [advanced-300](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [aws-iam](), [best-practices](), [identity-and-access-management](), [infrastructure-as-code](), [mfa](), [migration](), [technical-how-to]() ### AI overview This post presents a break-glass access pattern for Amazon EKS clusters when a federated identity provider fails. It describes a dedicated cross-account IAM role with enforced, recency-aware MFA, infrastructure-as-code templates, validation tests, and post-incident recovery procedures. ### Source excerpt Implementing break-glass access for Amazon EKS clusters removes the circular dependency where a federated identity provider outage locks you out of the clusters you need to reach to fix it. This post supplies a cross-account IAM role with enforced MFA, infrastructure-as-code templates, validation tests, and a post-incident recovery procedure. ## Deep dive into Amazon EKS certificate authority rotation DevFeed: [Deep dive into Amazon EKS certificate authority rotation]() Original publisher: [Read original article]() Author: Micah Hausler Published: 2026-08-19T20:55:49Z Content type: article Language: en Sources: [Containers]() Topics: [Amazon EKS](), [TLS (Transport Layer Security)](), [Availability](), [AWS Fargate](), [CI/CD](), [Security]() Tags: [advanced-300](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [announcements](), [availability](), [aws](), [aws-fargate](), [ci-cd](), [deep-dive](), [security](), [technical-how-to](), [tls]() ### AI overview This deep dive explains Amazon EKS certificate authority rotation. It describes the managed lifecycle, automated safeguards, rollback, AWS-managed components, and the customer responsibilities needed to preserve connectivity during the transition. ### Source excerpt Amazon EKS now provides a managed, non-disruptive lifecycle for rotating your cluster's certificate authority (CA), with automated safeguards and rollback. This deep dive explains how CA rotation works, what AWS handles versus what you must update, and how to walk through the rotation lifecycle on your own timeline. ## Encrypt Amazon ECS traffic: VPC encryption controls and Service Connect TLS DevFeed: [Encrypt Amazon ECS traffic: VPC encryption controls and Service Connect TLS]() Original publisher: [Read original article]() Author: Simone Tallevi-Diotallevi Published: 2026-08-19T20:37:56Z Content type: tutorial Language: en Sources: [Containers]() Topics: [Cryptography]() Tags: [advanced-300](), [amazon-elastic-container-service](), [amazon-vpc](), [aws](), [aws-fargate](), [containers](), [encryption](), [how-to](), [logs](), [nitro-system](), [security](), [technical-how-to](), [tls](), [vpc](), [vpc-flow-logs]() ### AI overview A hands-on guide to encrypting traffic between Amazon ECS workloads with VPC encryption controls or Service Connect TLS. It covers activation on AWS Fargate and verification through VPC Flow Logs. ### Source excerpt Learn how to encrypt traffic between Amazon ECS workloads using two native approaches: VPC encryption controls for network-layer encryption through the AWS Nitro System, and Service Connect TLS for application-layer encryption. A hands-on walkthrough shows how to activate encryption on AWS Fargate and verify it in VPC Flow Logs. ## Forensic container checkpointing on Amazon Elastic Kubernetes Service (Amazon EKS) DevFeed: [Forensic container checkpointing on Amazon Elastic Kubernetes Service (Amazon EKS)]() Original publisher: [Read original article]() Author: Varun DeviReddy Published: 2026-08-12T17:38:15Z Content type: tutorial Language: en Sources: [Containers]() Topics: [incident]() Tags: [advanced-300](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [api](), [container-security](), [containers](), [incident-response](), [kubernetes](), [memory](), [processes](), [security](), [technical-how-to]() ### AI overview This tutorial explains how to preserve volatile runtime evidence from suspicious containers on Amazon EKS by using the Kubelet Checkpoint API. It deploys a checkpoint agent that captures container state without stopping the workload, packages the result as an OCI image, and stores it in Amazon ECR for later forensic analysis. ### Source excerpt Amazon EKS 1.34 makes the Kubelet Checkpoint API functional, so you can capture a running container's full state (memory, processes, and network connections) without stopping the workload. This post shows how to deploy an unprivileged checkpoint agent that stores forensic checkpoints in Amazon ECR as OCI images for later analysis. ## Introducing advanced Kubernetes control plane configuration in Amazon EKS DevFeed: [Introducing advanced Kubernetes control plane configuration in Amazon EKS]() Original publisher: [Read original article]() Author: Ashok Srirama Published: 2026-08-12T17:23:45Z Content type: article Language: en Sources: [Containers]() Topics: [Amazon EKS](), [Kubernetes](), [configuration](), [API](), [Availability](), [Provisioning]() Tags: [advanced-300](), [ai-ml](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [announcements](), [api](), [availability](), [ci-cd](), [kubernetes](), [packing](), [retention](), [storage]() ### AI overview Amazon EKS introduces advanced Kubernetes control plane configuration, allowing users to set API server, scheduler, and controller manager parameters directly. The article covers pod placement scoring, event retention, and HPA synchronization settings through feature explanations and hands-on walkthroughs. ### Source excerpt With Amazon EKS, you can now configure Kubernetes control plane components (the API server, scheduler, and controller manager) directly through EKS APIs. This post explains what's configurable and includes two hands-on walkthroughs: enabling MostAllocated bin-packing to optimize pod placement, and tuning event retention duration. ## Centralize cross-account Amazon ECS telemetry with an ADOT gateway DevFeed: [Centralize cross-account Amazon ECS telemetry with an ADOT gateway]() Original publisher: [Read original article]() Author: Rahul Kumar Published: 2026-08-06T16:13:46Z Content type: tutorial Language: en Sources: [Containers]() Topics: [Amazon Elastic Container Service](), [telemetry](), [OpenTelemetry](), [SIEM, Security, Observability](), [Amazon CloudWatch](), [Amazon Web Services](), [Windows](), [.NET Framework](), [Traces](), [log management](), [Amazon Elastic Kubernetes Service]() Tags: [amazon-cloudwatch](), [amazon-eks](), [amazon-elastic-container-service](), [amazon-elastic-kubernetes-service](), [aws](), [intermediate-200](), [logs](), [metrics](), [net-framework](), [observability](), [opentelemetry](), [technical-how-to](), [telemetry](), [traces](), [windows]() ### AI overview This tutorial presents a centralized AWS Distro for OpenTelemetry gateway for collecting telemetry from Amazon ECS workloads across multiple AWS accounts. It replaces per-task sidecars, supports Windows .NET Framework tasks, receives OTLP over private connectivity, and exports traces to AWS X-Ray plus metrics and logs to Amazon CloudWatch. ### Source excerpt Running an OpenTelemetry collector as a sidecar in every Amazon ECS task does not scale across a multi-account estate, and it cannot run at all on Windows. Learn how to replace per-task sidecars with a single centralized ADOT gateway that ingests OTLP from workloads across accounts and exports traces to AWS X-Ray and metrics and logs to Amazon CloudWatch. ## Under the hood: how Amazon EKS Auto Mode detects, repairs, and diagnoses node failures DevFeed: [Under the hood: how Amazon EKS Auto Mode detects, repairs, and diagnoses node failures]() Original publisher: [Read original article]() Author: Sajjan Gundapuneedi Published: 2026-08-05T18:48:18Z Content type: article Language: en Sources: [Containers]() Topics: [Amazon EKS](), [Kubernetes](), [Monitoring](), [systemd](), [Cloud]() Tags: [advanced-300](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [cloud](), [diagnostics](), [kubernetes](), [monitoring](), [systemd](), [technical-how-to]() ### AI overview This article explains how Amazon EKS Auto Mode detects, diagnoses, drains, and replaces failed Kubernetes nodes. It describes the collaboration between the Node Monitoring Agent and Karpenter, including system-level fault detection, repair policies, safety thresholds, and node diagnostics without SSH. ### Source excerpt On Amazon EKS Auto Mode, node failures are detected, drained, and replaced automatically before anyone reaches for a laptop. This post shows how the Node Monitoring Agent and Karpenter form a detect-and-replace cycle that runs by default, why specific faults trigger node replacement, and how to collect node diagnostics without SSH. ## Extending Amazon ECS Express Mode to Build an Optimal Container Environment DevFeed: [Extending Amazon ECS Express Mode to Build an Optimal Container Environment]() Original publisher: [Read original article]() Author: Koichiro Okimura Published: 2026-08-04T15:57:59Z Content type: article Language: en Sources: [Containers]() Topics: [Amazon Elastic Container Service](), [Containers](), [Amazon Web Services](), [Deployment](), [log management](), [configuration](), [networking](), [Security]() Tags: [amazon-elastic-container-service](), [aws](), [containers](), [deployment](), [how-to](), [intermediate-200](), [logging](), [logs](), [network](), [security](), [technical-how-to]() ### AI overview This AWS article explains how to extend Amazon ECS Express Mode beyond its default container deployment configuration. It presents hands-on examples for enabling ECS Exec, adding scheduled scaling, and routing logs through a FireLens sidecar with a custom task definition. ### Source excerpt Amazon ECS Express Mode gives you load balancing, scaling, logging, and networking out of the box. Learn how to extend an Express Mode service beyond its defaults with three hands-on examples: turning on ECS Exec, adding a scheduled scaling policy, and adding a FireLens log router as a sidecar container.