# 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.

## Use Amazon ECR global authentication token across AWS Regions

DevFeed: [Use Amazon ECR global authentication token across AWS Regions](<https://devfeed.tech/articles/use-amazon-ecr-global-authentication-token-across-aws-regions-146422.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/use-amazon-ecr-global-authentication-token-across-aws-regions/>)

Author: Sourav Kundu

Published: 2026-11-19T20:09:23Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-elastic-container-registry](<https://devfeed.tech/tags/amazon-elastic-container-registry.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-tokens](<https://devfeed.tech/tags/authentication-tokens.md>), [aws](<https://devfeed.tech/tags/aws.md>), [docker](<https://devfeed.tech/tags/docker.md>), [global](<https://devfeed.tech/tags/global.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [images](<https://devfeed.tech/tags/images.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [lifetime](<https://devfeed.tech/tags/lifetime.md>), [minutes](<https://devfeed.tech/tags/minutes.md>), [one](<https://devfeed.tech/tags/one.md>), [partition](<https://devfeed.tech/tags/partition.md>), [post](<https://devfeed.tech/tags/post.md>), [regions](<https://devfeed.tech/tags/regions.md>), [request](<https://devfeed.tech/tags/request.md>), [sign](<https://devfeed.tech/tags/sign.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [token](<https://devfeed.tech/tags/token.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

Amazon ECR global authentication tokens let one bearer token authenticate to ECR registry endpoints across AWS Regions within the same partition, simplifying multi-Region pushes and pulls. Request it through AWS Sign-In with `CreateBearerToken` for `ecr.amazonaws.com`; the caller needs `signin:CreateBearerToken`, and the token carries the caller's existing IAM permissions, which ECR checks for every operation. Its lifetime defaults to 12 hours and can be shortened to 5 minutes. AWS CLI 2.39.7 or later supports the command, and the ECR credential helper, Kubernetes credential provider, and GitHub Actions login action can opt in. CloudTrail records a shared sign-in session ARN on token issuance and authorized ECR events, supporting cross-Region tracing and session-specific denial. Registries and images remain Regional, existing regional tokens continue to work, and opt-in Regions require account enrollment. The walkthrough also cautions that credential tooling must accept variable-length tokens.

### Source excerpt

Amazon ECR now supports global authentication tokens: request one token from AWS Sign-In and use it to push and pull images across AWS Regions in the same partition, with a lifetime from 5 minutes to 12 hours. This post shows how to request a global token and use it with Docker in two Regions.

## High-quality cost-effective AI image generation on Amazon ECS

DevFeed: [High-quality cost-effective AI image generation on Amazon ECS](<https://devfeed.tech/articles/high-quality-cost-effective-ai-image-generation-on-amazon-ecs-136885.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/high-quality-cost-effective-ai-image-generation-on-amazon-ecs/>)

Author: Nick Biso

Published: 2026-11-17T00:19:06Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [diffusion-transformers](<https://devfeed.tech/topics/diffusion-transformers.md>), [ai-image-generator](<https://devfeed.tech/topics/ai-image-generator.md>), [AWS Inferentia](<https://devfeed.tech/topics/aws-inferentia.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai-image-generation](<https://devfeed.tech/tags/ai-image-generation.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [auto-scaling](<https://devfeed.tech/tags/auto-scaling.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cost](<https://devfeed.tech/tags/cost.md>), [diffusion](<https://devfeed.tech/tags/diffusion.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The described Amazon ECS service runs Z-Image-Turbo on AWS Inferentia2, with one service per image resolution and one request at a time per instance because inference saturates the accelerator. Its key deployment mechanism is compiling model artifacts once in CI/CD, caching them on Amazon EFS, and loading them into containers at startup; the post reports this cuts startup to about two minutes from over 30 minutes and avoids recompilation when changes do not affect the model graph. The excerpt estimates $0.003 per 512px image and $0.011 per 1024px image at $1.97/hour for an inf2.8xlarge in us-east-1, while noting costs vary with utilization and other AWS resources still incur charges. It also describes resolution-based routing and streaming intermediate image frames over WebSockets. Deployment requires AWS quotas for Inf2 instances, CDK bootstrap, and listed local tools; first deployment takes about 45 minutes, including compilation.

### Source excerpt

Learn how to run Z-Image-Turbo, a 6-billion-parameter diffusion transformer, on AWS Inferentia2 and Amazon ECS to generate high-quality images at a fraction of a cent each, with auto-scaling, arbitrary resolution support, and a complete CI/CD pipeline.

## How Salesforce efficiently right-sizes Kubernetes workloads at scale on Amazon EKS

DevFeed: [How Salesforce efficiently right-sizes Kubernetes workloads at scale on Amazon EKS](<https://devfeed.tech/articles/how-salesforce-efficiently-right-sizes-kubernetes-workloads-at-scale-on-amazon-eks-136886.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/how-salesforce-efficiently-right-sizes-kubernetes-workloads-at-scale-on-amazon-eks/>)

Author: Lei Liu

Published: 2026-11-16T20:40:26Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Performance Testing](<https://devfeed.tech/topics/performance-testing.md>)

Tags: [000](<https://devfeed.tech/tags/000.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [efficiently](<https://devfeed.tech/tags/efficiently.md>), [eks](<https://devfeed.tech/tags/eks.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [more](<https://devfeed.tech/tags/more.md>), [multi-tenant](<https://devfeed.tech/tags/multi-tenant.md>), [one](<https://devfeed.tech/tags/one.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [pod](<https://devfeed.tech/tags/pod.md>), [right](<https://devfeed.tech/tags/right.md>), [salesforce](<https://devfeed.tech/tags/salesforce.md>), [scale](<https://devfeed.tech/tags/scale.md>), [strategy](<https://devfeed.tech/tags/strategy.md>), [team](<https://devfeed.tech/tags/team.md>), [vertical](<https://devfeed.tech/tags/vertical.md>)

### AI overview

Salesforce reports more than $5 million in cumulative infrastructure savings after moving from static resource settings to workload-specific autoscaling across more than 1,400 Amazon EKS clusters. It uses VPA to adjust CPU and memory requests, HPA to change replica counts, or both when a workload needs independent vertical and horizontal scaling. For Istio, HPA tracks connected proxies while VPA adjusts each istiod pod's resources. The team describes staged, tested rollouts with rollback controls, monitoring, and safeguards such as eviction limits. Its guidance is to start VPA in Off mode, use RequestsOnly when adjusting resources, and keep VPA and HPA on distinct metrics. VPA recommendations use historical usage and are intended for steady-state optimization; sudden spikes need other protections. Planned expansions include in-place resizing and support for AI workloads.

### Source excerpt

Salesforce operates one of the largest multi-tenant Kubernetes platforms on Amazon EKS, spanning 1,400+ clusters. See how its team combined the Vertical Pod Autoscaler and Horizontal Pod Autoscaler into a multi-dimensional autoscaling strategy that right-sizes workloads at scale and drove more than $5 million in infrastructure savings.

## Automatically recover from GPU failures with Amazon ECS Managed Instances

DevFeed: [Automatically recover from GPU failures with Amazon ECS Managed Instances](<https://devfeed.tech/articles/automatically-recover-from-gpu-failures-with-amazon-ecs-managed-instances-131641.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/automatically-recover-from-gpu-failures-with-amazon-ecs-managed-instances/>)

Author: Piyush Mattoo

Published: 2026-11-12T21:24:16Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [gpu monitoring](<https://devfeed.tech/topics/gpu-monitoring.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [aws-sns](<https://devfeed.tech/topics/aws-sns.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-ecs](<https://devfeed.tech/tags/amazon-ecs.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [automatic](<https://devfeed.tech/tags/automatic.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [changes](<https://devfeed.tech/tags/changes.md>), [code](<https://devfeed.tech/tags/code.md>), [critical](<https://devfeed.tech/tags/critical.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [failures](<https://devfeed.tech/tags/failures.md>), [fault-injection](<https://devfeed.tech/tags/fault-injection.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [health](<https://devfeed.tech/tags/health.md>), [health-monitoring](<https://devfeed.tech/tags/health-monitoring.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [inference](<https://devfeed.tech/tags/inference.md>), [managed](<https://devfeed.tech/tags/managed.md>), [recover](<https://devfeed.tech/tags/recover.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Amazon ECS Managed Instances uses NVIDIA DCGM to monitor GPU hardware and automatically replace instances after critical GPU failures. It marks an affected instance IMPAIRED, drains it so no new tasks are scheduled, provisions replacement capacity, then terminates the old instance after its tasks stop. Repairs are limited to at most 20% of a capacity provider's instances at once, or one instance for providers with fewer than nine. Application-level faults such as XID 13 and 31 are surfaced through CloudWatch metrics rather than triggering instance replacement. Health and state changes are available through EventBridge; DCGM metrics require Container Insights with enhanced observability. The article demonstrates end-to-end validation by injecting a synthetic XID 79, which triggers the real repair workflow without damaging GPU hardware. The targeted host is still drained and terminated, so the test is intended for a dedicated cluster or maintenance window. In the sample, detection took about two minutes and replacement about eight; model startup added 7-20 minutes, depending on the tier. These timings are not service guarantees.

### Source excerpt

Amazon ECS Managed Instances provides built-in GPU health monitoring and automatic repair powered by NVIDIA DCGM. This post shows how GPU auto-repair detects critical GPU hardware failures and replaces impaired instances with no code changes, and how to observe and safely validate the workflow using DCGM fault injection on a dual-tier inference pipeline.

## Deep dive: Auto scaling response times on Amazon ECS

DevFeed: [Deep dive: Auto scaling response times on Amazon ECS](<https://devfeed.tech/articles/deep-dive-auto-scaling-response-times-on-amazon-ecs-116295.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/deep-dive-auto-scaling-response-times-on-amazon-ecs/>)

Author: Sai Kumar Samala

Published: 2026-11-03T16:37:37Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Elastic Container Service](<https://devfeed.tech/topics/amazon-elastic-container-service.md>), [Deployment & Scaling](<https://devfeed.tech/topics/deployment-scaling.md>), [AWS Fargate](<https://devfeed.tech/topics/aws-fargate.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [auto-scaling](<https://devfeed.tech/tags/auto-scaling.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-fargate](<https://devfeed.tech/tags/aws-fargate.md>), [benchmarking](<https://devfeed.tech/tags/benchmarking.md>), [changes](<https://devfeed.tech/tags/changes.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [deep](<https://devfeed.tech/tags/deep.md>), [deep-dive](<https://devfeed.tech/tags/deep-dive.md>), [dive](<https://devfeed.tech/tags/dive.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [faster](<https://devfeed.tech/tags/faster.md>), [feature](<https://devfeed.tech/tags/feature.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [load](<https://devfeed.tech/tags/load.md>), [managed](<https://devfeed.tech/tags/managed.md>), [memory](<https://devfeed.tech/tags/memory.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [times](<https://devfeed.tech/tags/times.md>)

### AI overview

Amazon ECS can use 20-second CPU and memory metrics with target tracking to react to load changes sooner; a lower-latency publishing path helps deliver each measurement promptly. In AWS benchmarks, scale-out decisions took 86 seconds versus 363 seconds with 60-second metrics, and new tasks were placed in 109 seconds versus 386. On a gradual-ramp workload, SLA breach time fell from 2,013 to 633 seconds on Fargate and from 1,692 to 30 seconds on ECS Managed Instances. Managed Instances gained more because tasks can use warm instances with spare capacity; Fargate provisions an isolated environment and pulls the image. Scale-down on the gradual-ramp profile dropped from over 30 minutes to under a minute. Results vary by workload, and abrupt-stop profiles improved less. To enable the feature, turn on 20-second CPU and memory metrics, let an existing service deployment finish, then attach target tracking with one of the high-resolution predefined metrics. It works across ECS compute options without Container Insights, but high-resolution metrics incur CloudWatch metric charges; the default 60-second metrics remain free. The post recommends reserving 20-second metrics for services where l

### Source excerpt

Amazon ECS now publishes high-resolution 20-second CPU and memory utilization metrics for target tracking, so service auto scaling detects and responds to load changes faster. This post shares AWS benchmarking results across AWS Fargate and ECS Managed Instances and shows how to turn the feature on.

## Measuring developer experience on an Amazon EKS developer platform

DevFeed: [Measuring developer experience on an Amazon EKS developer platform](<https://devfeed.tech/articles/measuring-developer-experience-on-an-amazon-eks-developer-platform-101932.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/measuring-developer-experience-on-an-amazon-eks-developer-platform/>)

Author: Zachary Jacobson

Published: 2026-10-26T17:32:58Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [dora metrics](<https://devfeed.tech/topics/dora-metrics.md>), [internal developer platform](<https://devfeed.tech/topics/internal-developer-platform.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [DORA change failure rate](<https://devfeed.tech/topics/dora-change-failure-rate.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Argo Rollouts](<https://devfeed.tech/topics/argo-rollouts.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [progressive delivery](<https://devfeed.tech/topics/progressive-delivery.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [apache](<https://devfeed.tech/tags/apache.md>), [argo](<https://devfeed.tech/tags/argo.md>), [argo-cd](<https://devfeed.tech/tags/argo-cd.md>), [argo-rollouts](<https://devfeed.tech/tags/argo-rollouts.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [can](<https://devfeed.tech/tags/can.md>), [cd](<https://devfeed.tech/tags/cd.md>), [change](<https://devfeed.tech/tags/change.md>), [changes](<https://devfeed.tech/tags/changes.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [developer-platform](<https://devfeed.tech/tags/developer-platform.md>), [eks](<https://devfeed.tech/tags/eks.md>), [experience](<https://devfeed.tech/tags/experience.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [measuring](<https://devfeed.tech/tags/measuring.md>), [platform](<https://devfeed.tech/tags/platform.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The article shows a demo for automatically tracking deployment frequency, lead time for changes, change failure rate, and failed deployment recovery time on Amazon EKS. Argo CD delivers releases, Argo Rollouts reports deployment outcomes, Argo Events and Workflows forward Git events, Apache DevLake calculates the metrics, and Grafana displays trends. The walkthrough records successful rollouts as deployments and links incidents to the most recent prior deployment; closing an incident represents recovery. Its Gitea setup lacks native DevLake integration, so pull requests are sent through a webhook and lead time starts at PR opening. With native GitHub, GitLab, or Bitbucket integration, the article says DevLake can measure from the first commit. In production, issue-based incident records should be filtered so only real incidents count. The demo creates EKS infrastructure and storage that can incur charges until cleaned up.

### Source excerpt

Most platform teams can't prove their internal developer platform is improving software delivery. This post shows how to automatically collect the four DORA metrics (deployment frequency, lead time for changes, change failure rate, and failed deployment recovery time) on an Amazon EKS platform using Argo CD, Argo Rollouts, Apache DevLake, and Grafana.

## Observability patterns for AI agents on Amazon EKS

DevFeed: [Observability patterns for AI agents on Amazon EKS](<https://devfeed.tech/articles/observability-patterns-for-ai-agents-on-amazon-eks-93981.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/observability-patterns-for-ai-agents-on-amazon-eks/>)

Author: Hari Muthusamy

Published: 2026-10-21T23:34:27Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent-observability](<https://devfeed.tech/tags/agent-observability.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agents-sdk](<https://devfeed.tech/tags/agents-sdk.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [alerting](<https://devfeed.tech/tags/alerting.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-elastic-kubernetes-service-amazon-eks](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service-amazon-eks.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [bifrost](<https://devfeed.tech/tags/bifrost.md>), [decentralized](<https://devfeed.tech/tags/decentralized.md>), [eks](<https://devfeed.tech/tags/eks.md>), [langfuse](<https://devfeed.tech/tags/langfuse.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The article implements two OpenTelemetry patterns for observing AI agents on Amazon EKS, using Strands Agents, Bifrost routing to Amazon Bedrock, and Langfuse for trace and cost views. Both capture agent steps and correlated model calls in a unified trace. In the decentralized pattern, each agent exports directly to Langfuse, reducing shared infrastructure and isolating exporter failures, while global pipeline changes require updating agents. In the centralized pattern, a shared OpenTelemetry Collector batches and processes telemetry and provides one place to add backends, sampling, or filtering; it also becomes a dependency that must be operated and monitored. The article recommends starting decentralized with a small fleet and considering centralization as fleet-wide control becomes more valuable. Its example traces show different workloads and costs, so they are not a direct performance comparison.

### Source excerpt

Traditional monitoring shows an AI agent's endpoint returned HTTP 200, but not why it picked the wrong tool, burned through your token budget, or looped. This post implements two OpenTelemetry observability patterns for AI agents on Amazon EKS, decentralized and centralized, using Bifrost, Amazon Bedrock, and Langfuse.

## Automating secure container registry management for air-gapped AWS workloads

DevFeed: [Automating secure container registry management for air-gapped AWS workloads](<https://devfeed.tech/articles/automating-secure-container-registry-management-for-air-gapped-aws-workloads-88876.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/automating-secure-container-registry-management-for-air-gapped-aws-workloads/>)

Author: Suneet Bhatnagar

Published: 2026-10-16T17:48:23Z

Content type: tutorial

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Security, Identity, & Compliance](<https://devfeed.tech/topics/security-identity-compliance.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Docker Hub](<https://devfeed.tech/topics/docker-hub.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-elastic-container-registry](<https://devfeed.tech/tags/amazon-elastic-container-registry.md>), [arm64](<https://devfeed.tech/tags/arm64.md>), [aws](<https://devfeed.tech/tags/aws.md>), [container](<https://devfeed.tech/tags/container.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [security](<https://devfeed.tech/tags/security.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

The article describes an architecture for managing container registries in air-gapped AWS environments. It combines Amazon ECR repository creation templates, Terraform, and an artifact migration tool to apply consistent security settings while preserving multi-architecture images and Helm chart dependencies. It also discusses trade-offs such as immutable tags, existing repositories, rate limits, and credential rotation.

### Source excerpt

Organizations in regulated industries run container workloads in air-gapped AWS environments, which means migrating hundreds of Helm charts and images into private Amazon ECR with consistent security controls. This post uses Amazon ECR repository creation templates, Terraform, and a migration tool to make secure-by-default the path of least resistance.

## Migrating from NGINX Ingress to ALB: Handling oauth2-proxy

DevFeed: [Migrating from NGINX Ingress to ALB: Handling oauth2-proxy](<https://devfeed.tech/articles/migrating-from-nginx-ingress-to-alb-handling-oauth2-proxy-65875.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/migrating-from-nginx-ingress-to-alb-handling-oauth2-proxy/>)

Author: Ali Sanhaji

Published: 2026-10-06T15:54:29Z

Content type: tutorial

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [ingress-nginx](<https://devfeed.tech/topics/ingress-nginx.md>), [nginx](<https://devfeed.tech/topics/nginx.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [backend](<https://devfeed.tech/tags/backend.md>), [elastic-load-balancing](<https://devfeed.tech/tags/elastic-load-balancing.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [nginx-ingress-controller](<https://devfeed.tech/tags/nginx-ingress-controller.md>), [oauth2](<https://devfeed.tech/tags/oauth2.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The article explains how teams migrating from NGINX Ingress to the AWS Load Balancer Controller can preserve OpenID Connect authentication when using oauth2-proxy. It compares keeping oauth2-proxy in reverse proxy mode with using ALB native OIDC, highlighting differences in backend authorization headers and outlining a staged migration and validation process.

### Source excerpt

The NGINX Ingress Controller is retired. If you run oauth2-proxy with NGINX for OpenID Connect authentication, switching to the AWS Load Balancer Controller can silently break your auth. This post shows two ways to keep OIDC working on an Application Load Balancer: run oauth2-proxy in reverse proxy mode, or use ALB native OIDC.

## Implementing feature flags in container environments with AWS AppConfig

DevFeed: [Implementing feature flags in container environments with AWS AppConfig](<https://devfeed.tech/articles/implementing-feature-flags-in-container-environments-with-aws-appconfig-63560.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/implementing-feature-flags-in-container-environments-with-aws-appconfig/>)

Author: Daniel Abib

Published: 2026-10-01T16:42:33Z

Content type: tutorial

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [blue-green deployment](<https://devfeed.tech/topics/blue-green-deployment.md>)

Tags: [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-fargate](<https://devfeed.tech/tags/aws-fargate.md>), [aws-systems-manager](<https://devfeed.tech/tags/aws-systems-manager.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [eks](<https://devfeed.tech/tags/eks.md>), [feature-flags](<https://devfeed.tech/tags/feature-flags.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [sidecar](<https://devfeed.tech/tags/sidecar.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

This tutorial explains how to implement runtime feature flags in Amazon ECS and Amazon EKS using AWS AppConfig and a sidecar agent. Applications query the local agent over HTTP for configuration, while it handles retrieval, caching, and refresh; gradual deployments, validation, and fallback defaults support safer configuration changes without rebuilding or redeploying containers.

### Source excerpt

Learn how to implement dynamic feature flags in Amazon ECS and Amazon EKS using AWS AppConfig with the sidecar pattern. You set up an AWS AppConfig feature flag, deploy the AWS AppConfig Agent as a sidecar container, and toggle application behavior at runtime without rebuilding or redeploying your containers.

## AI-powered EKS migration assessment with Amazon Bedrock AgentCore

DevFeed: [AI-powered EKS migration assessment with Amazon Bedrock AgentCore](<https://devfeed.tech/articles/ai-powered-eks-migration-assessment-with-amazon-bedrock-agentcore-62861.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/ai-powered-eks-migration-assessment-with-amazon-bedrock-agentcore/>)

Author: Pradip Kumar Pandey

Published: 2026-09-30T15:34:19Z

Content type: tutorial

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Linear](<https://devfeed.tech/topics/linear.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [strands-agents](<https://devfeed.tech/tags/strands-agents.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

This tutorial describes building an AI-powered agent with Amazon Bedrock AgentCore and the Strands Agents SDK to assess applications for migration to Amazon EKS. The agent analyzes source code and container artifacts, scores readiness, identifies migration blockers, and proposes a migration plan with architecture recommendations.

### Source excerpt

Learn how to build an AI-powered migration assessment agent using Amazon Bedrock AgentCore and the Strands Agents SDK. The agent reads application source code and container artifacts, scores Amazon EKS migration readiness, identifies blockers by severity, and generates an actionable migration plan with target architecture recommendations.

## How athenahealth modernized healthcare workloads with Amazon EKS Hybrid Nodes

DevFeed: [How athenahealth modernized healthcare workloads with Amazon EKS Hybrid Nodes](<https://devfeed.tech/articles/how-athenahealth-modernized-healthcare-workloads-with-amazon-eks-hybrid-nodes-62862.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/how-athenahealth-modernized-healthcare-workloads-with-amazon-eks-hybrid-nodes/>)

Author: Sai Charan Teja Gopaluni

Published: 2026-09-30T15:16:52Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [AWS Outposts](<https://devfeed.tech/topics/aws-outposts.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [costs](<https://devfeed.tech/tags/costs.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [data-residency](<https://devfeed.tech/tags/data-residency.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [latency](<https://devfeed.tech/tags/latency.md>)

### AI overview

athenahealth adopted Amazon EKS Hybrid Nodes to run latency-sensitive healthcare applications on premises while using a consistent Kubernetes operating model across its data center and the cloud. The post describes the architecture and reports that response times and hardware and operational costs each fell by 50%, while meeting data residency and compliance requirements.

### Source excerpt

Learn how athenahealth used Amazon EKS Hybrid Nodes to modernize latency-sensitive healthcare workloads on premises, cutting response times in half, reducing hardware and operational costs by 50%, and maintaining a single Kubernetes operating model across its data center and the cloud while meeting HITRUST and data residency requirements.

## Fix pod distribution drift in Amazon EKS with the Kubernetes descheduler

DevFeed: [Fix pod distribution drift in Amazon EKS with the Kubernetes descheduler](<https://devfeed.tech/articles/fix-pod-distribution-drift-in-amazon-eks-with-the-kubernetes-descheduler-61364.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/fix-pod-distribution-drift-in-amazon-eks-with-the-kubernetes-descheduler/>)

Author: Ramya D

Published: 2026-09-28T16:01:43Z

Content type: tutorial

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

Soft Kubernetes topology spread constraints may leave pods unevenly distributed after a node availability gap because the scheduler does not rebalance running pods. The post measures this drift on Amazon EKS and walks through using the Kubernetes descheduler to restore distribution.

### Source excerpt

A workload spread across three Availability Zones does not necessarily stay spread. This post explains why soft topology spread constraints drift after a node-availability gap, measures the cost, and shows how the Kubernetes descheduler restores even pod distribution on Amazon EKS without downtime and without forcing hard constraints.

## AWS named a Leader in the 2026 Gartner Magic Quadrant for Container Management

DevFeed: [AWS named a Leader in the 2026 Gartner Magic Quadrant for Container Management](<https://devfeed.tech/articles/aws-named-a-leader-in-the-2026-gartner-magic-quadrant-for-container-management-60173.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/aws-named-a-leader-in-the-2026-gartner-magic-quadrant-for-container-management/>)

Author: Aarti Patil

Published: 2026-09-25T21:18:33Z

Content type: release

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon Elastic Container Service](<https://devfeed.tech/topics/amazon-elastic-container-service.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [container](<https://devfeed.tech/topics/container.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [GitOps](<https://devfeed.tech/topics/gitops.md>), [Argo CD](<https://devfeed.tech/topics/argo-cd.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [GPU](<https://devfeed.tech/topics/gpu.md>)

Tags: [accelerators](<https://devfeed.tech/tags/accelerators.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [argo-cd](<https://devfeed.tech/tags/argo-cd.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-trainium](<https://devfeed.tech/tags/aws-trainium.md>), [container](<https://devfeed.tech/tags/container.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [eks](<https://devfeed.tech/tags/eks.md>), [gartner](<https://devfeed.tech/tags/gartner.md>), [gartner-magic-quadrant](<https://devfeed.tech/tags/gartner-magic-quadrant.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [leader](<https://devfeed.tech/tags/leader.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [scaling](<https://devfeed.tech/tags/scaling.md>)

### AI overview

AWS says Gartner recognized it as a Leader in the 2026 Magic Quadrant for Container Management for the fourth consecutive year. The announcement highlights container services, managed Kubernetes capabilities, GitOps tooling, and infrastructure for scaling AI workloads.

### Source excerpt

Gartner has recognized AWS as a Leader in the 2026 Gartner Magic Quadrant for Container Management for the fourth consecutive year. See what our latest container innovations across Amazon ECS and Amazon EKS mean for customers building and scaling on AWS.

## One Amazon EKS, many edges: How to choose your edge container strategy on AWS

DevFeed: [One Amazon EKS, many edges: How to choose your edge container strategy on AWS](<https://devfeed.tech/articles/one-amazon-eks-many-edges-how-to-choose-your-edge-container-strategy-on-aws-60174.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/one-amazon-eks-many-edges-how-to-choose-your-edge-container-strategy-on-aws/>)

Author: Sathish Kumar Prabakaran

Published: 2026-09-25T15:52:19Z

Content type: tutorial

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [container](<https://devfeed.tech/topics/container.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Cloud Native Ecosystem](<https://devfeed.tech/topics/cloud-native-ecosystem.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-elastic-kubernetes-service-amazon-eks](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service-amazon-eks.md>), [aws](<https://devfeed.tech/tags/aws.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [scaling](<https://devfeed.tech/tags/scaling.md>)

### AI overview

This tutorial explains how to standardize edge container deployments on Amazon EKS across sites with different connectivity, infrastructure, and scale. It recommends using one Kubernetes foundation while selecting the deployment model for each location.

### Source excerpt

Choosing the right edge container strategy across many locations can fragment your fleet into dozens of special cases. This post shows how to avoid that by standardizing on Amazon EKS, then choosing a deployment model per site: gate on connectivity, then match to existing infrastructure, so every edge runs the same Kubernetes standard.

## Building a single-pane NOC dashboard for Amazon EKS with Amazon CloudWatch

DevFeed: [Building a single-pane NOC dashboard for Amazon EKS with Amazon CloudWatch](<https://devfeed.tech/articles/building-a-single-pane-noc-dashboard-for-amazon-eks-with-amazon-cloudwatch-58911.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/building-a-single-pane-noc-dashboard-for-amazon-eks-with-amazon-cloudwatch/>)

Author: Sam Mukherjee

Published: 2026-09-23T18:30:21Z

Content type: tutorial

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Network Operations Center](<https://devfeed.tech/topics/network-operations-center.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [observability](<https://devfeed.tech/topics/observability.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [incident](<https://devfeed.tech/topics/incident.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [eks](<https://devfeed.tech/tags/eks.md>), [incident](<https://devfeed.tech/tags/incident.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [linux](<https://devfeed.tech/tags/linux.md>), [metric](<https://devfeed.tech/tags/metric.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [network-operations](<https://devfeed.tech/tags/network-operations.md>), [network-operations-center](<https://devfeed.tech/tags/network-operations-center.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

A tutorial for building a trustworthy single-pane Network Operations Center dashboard for Amazon EKS with Amazon CloudWatch. It combines Kubernetes and application telemetry, PromQL charts, CloudWatch metric widgets, drilldowns, alarms, and query validation before deployment.

### Source excerpt

An incident is the worst moment to discover you cannot trust your Amazon EKS dashboard. This post shows what a trustworthy single-pane NOC for Amazon EKS on Amazon CloudWatch looks like, why each design choice matters, and how to get one running in your account in about 15 minutes.

## The operations gap between deploying an application and running it forever

DevFeed: [The operations gap between deploying an application and running it forever](<https://devfeed.tech/articles/the-operations-gap-between-deploying-an-application-and-running-it-forever-58217.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/the-operations-gap-between-deploying-an-application-and-running-it-forever/>)

Author: Aritra Nag

Published: 2026-09-22T20:38:09Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Deployment](<https://devfeed.tech/topics/deployment.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [announcements](<https://devfeed.tech/tags/announcements.md>), [aws-elastic-beanstalk](<https://devfeed.tech/tags/aws-elastic-beanstalk.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>)

### AI overview

This post examines the operational gap between deploying container images and running applications reliably in production. It introduces AWS Elastic Beanstalk's Cluster Mode deployment model as a way to manage containerized application portfolios and their underlying infrastructure, networking, scaling, and monitoring.

### Source excerpt

This post features the new Cluster Mode deployment model in AWS Elastic Beanstalk that extends the operational promise of the service to containerized application portfolios. You bring your applications as source code, Dockerfiles, or container images, and Elastic Beanstalk takes ongoing operational responsibility for the production environment underneath.

## Implement per-pod image pull permissions with ECR repository policies on Amazon EKS

DevFeed: [Implement per-pod image pull permissions with ECR repository policies on Amazon EKS](<https://devfeed.tech/articles/implement-per-pod-image-pull-permissions-with-ecr-repository-policies-on-amazon-eks-58216.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/implement-per-pod-image-pull-permissions-with-ecr-repository-policies-on-amazon-eks/>)

Author: Asiel Bencomo Corona

Published: 2026-09-22T16:58:07Z

Content type: tutorial

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-container-registry](<https://devfeed.tech/tags/amazon-elastic-container-registry.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [eks](<https://devfeed.tech/tags/eks.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [namespaces](<https://devfeed.tech/tags/namespaces.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [policies](<https://devfeed.tech/tags/policies.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

This tutorial explains how to give individual Kubernetes pods scoped permission to pull container images from Amazon ECR in a multi-tenant Amazon EKS cluster. It covers per-pod credential support introduced by KEP 4412 and AWS-native ECR repository policies.

### Source excerpt

Learn how to scope Amazon ECR image pull permissions to individual Kubernetes pods on a multi-tenant Amazon EKS cluster using KEP 4412 credential providers and ECR repository deny policies, so teams sharing the same nodes can pull only their own container images.

## How Ramp runs GPU AI workloads at scale with ECS Managed Instances

DevFeed: [How Ramp runs GPU AI workloads at scale with ECS Managed Instances](<https://devfeed.tech/articles/how-ramp-runs-gpu-ai-workloads-at-scale-with-ecs-managed-instances-57597.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/how-ramp-runs-gpu-ai-workloads-at-scale-with-ecs-managed-instances/>)

Author: Raphaël Beamonte

Published: 2026-09-21T18:41:27Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Elastic Container Service](<https://devfeed.tech/topics/amazon-elastic-container-service.md>), [GPU](<https://devfeed.tech/topics/gpu.md>), [Inference](<https://devfeed.tech/topics/inference.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

Ramp describes moving continuously running GPU inference workloads onto Amazon ECS Managed Instances. The post covers the architecture pattern, Terraform implementation, and lessons from migrating its EC2-based infrastructure.

### Source excerpt

Ramp runs GPU-powered AI inference continuously on Amazon ECS. This post walks through how Ramp's infrastructure team moved those GPU workloads onto Amazon ECS Managed Instances: the architecture pattern, Terraform implementation, and the lessons learned migrating 50 to 60 EC2 instances.

## Automate proxy injection for Amazon EKS on AWS Fargate using Kyverno

DevFeed: [Automate proxy injection for Amazon EKS on AWS Fargate using Kyverno](<https://devfeed.tech/articles/automate-proxy-injection-for-amazon-eks-on-aws-fargate-using-kyverno-4624.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/automate-proxy-injection-for-amazon-eks-on-aws-fargate-using-kyverno/>)

Author: Himanshu Bansal

Published: 2026-09-01T15:59:57Z

Content type: tutorial

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [container](<https://devfeed.tech/topics/container.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [aws-fargate](<https://devfeed.tech/tags/aws-fargate.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [containers](<https://devfeed.tech/tags/containers.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [policy](<https://devfeed.tech/tags/policy.md>)

### 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](<https://devfeed.tech/articles/fast-model-loading-for-ai-inference-on-amazon-eks-4630.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/fast-model-loading-for-ai-inference-on-amazon-eks/>)

Author: Sajjan Gundapuneedi

Published: 2026-09-01T15:48:15Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Inference](<https://devfeed.tech/topics/inference.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Language models](<https://devfeed.tech/topics/language-models.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cuda](<https://devfeed.tech/tags/cuda.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [inference](<https://devfeed.tech/tags/inference.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [language-models](<https://devfeed.tech/tags/language-models.md>), [pytorch](<https://devfeed.tech/tags/pytorch.md>), [s3](<https://devfeed.tech/tags/s3.md>), [sglang](<https://devfeed.tech/tags/sglang.md>), [startup](<https://devfeed.tech/tags/startup.md>), [vllm](<https://devfeed.tech/tags/vllm.md>)

### 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](<https://devfeed.tech/articles/break-glass-access-for-amazon-eks-when-federated-identity-fails-4625.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/break-glass-access-for-amazon-eks-when-federated-identity-fails/>)

Author: Sam Mukherjee

Published: 2026-08-26T16:20:28Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Infrastructure as code](<https://devfeed.tech/topics/infrastructure-as-code.md>), [MFA](<https://devfeed.tech/topics/mfa.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [iac-security](<https://devfeed.tech/topics/iac-security.md>), [migration](<https://devfeed.tech/topics/migration.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [aws-iam](<https://devfeed.tech/tags/aws-iam.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [identity-and-access-management](<https://devfeed.tech/tags/identity-and-access-management.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [mfa](<https://devfeed.tech/tags/mfa.md>), [migration](<https://devfeed.tech/tags/migration.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### 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](<https://devfeed.tech/articles/deep-dive-into-amazon-eks-certificate-authority-rotation-4627.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/deep-dive-into-amazon-eks-certificate-authority-rotation/>)

Author: Micah Hausler

Published: 2026-08-19T20:55:49Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [AWS Fargate](<https://devfeed.tech/topics/aws-fargate.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-fargate](<https://devfeed.tech/tags/aws-fargate.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [deep-dive](<https://devfeed.tech/tags/deep-dive.md>), [security](<https://devfeed.tech/tags/security.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### 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](<https://devfeed.tech/articles/encrypt-amazon-ecs-traffic-vpc-encryption-controls-and-service-connect-tls-4628.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/encrypt-amazon-ecs-traffic-vpc-encryption-controls-and-service-connect-tls/>)

Author: Simone Tallevi-Diotallevi

Published: 2026-08-19T20:37:56Z

Content type: tutorial

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Cryptography](<https://devfeed.tech/topics/cryptography.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-fargate](<https://devfeed.tech/tags/aws-fargate.md>), [containers](<https://devfeed.tech/tags/containers.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [logs](<https://devfeed.tech/tags/logs.md>), [nitro-system](<https://devfeed.tech/tags/nitro-system.md>), [security](<https://devfeed.tech/tags/security.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [tls](<https://devfeed.tech/tags/tls.md>), [vpc](<https://devfeed.tech/tags/vpc.md>), [vpc-flow-logs](<https://devfeed.tech/tags/vpc-flow-logs.md>)

### 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.

[Next page](<https://devfeed.tech/sources/containers.md?cursor=WyIyMDI2LTA4LTE5VDIwOjM3OjU2KzAwOjAwIiwgImUxNTAyMDMyLTA5ZjktNGJmOS05OTMxLTVlNDVjMjZjNTFkOCJd>)