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

## Using NVIDIA Run:ai GPU Fractioning on Amazon EKS

DevFeed: [Using NVIDIA Run:ai GPU Fractioning on Amazon EKS](<https://devfeed.tech/articles/using-nvidia-run-ai-gpu-fractioning-on-amazon-eks-143848.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/using-nvidia-runai-gpu-fractioning-on-amazon-eks/>)

Author: Muru Bhaskaran

Published: 2026-11-19T16:13:51Z

Content type: tutorial

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [gpu monitoring](<https://devfeed.tech/topics/gpu-monitoring.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [eks](<https://devfeed.tech/tags/eks.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [gpu-memory](<https://devfeed.tech/tags/gpu-memory.md>), [kai-scheduler](<https://devfeed.tech/tags/kai-scheduler.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [linux](<https://devfeed.tech/tags/linux.md>), [memory](<https://devfeed.tech/tags/memory.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [nvidia](<https://devfeed.tech/tags/nvidia.md>), [nvidia-run-ai](<https://devfeed.tech/tags/nvidia-run-ai.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [operator](<https://devfeed.tech/tags/operator.md>), [pod](<https://devfeed.tech/tags/pod.md>), [pods](<https://devfeed.tech/tags/pods.md>), [run-ai](<https://devfeed.tech/tags/run-ai.md>), [scheduler](<https://devfeed.tech/tags/scheduler.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

NVIDIA Run:ai GPU Fractioning lets two Kubernetes Pods share one NVIDIA A10G on Amazon EKS with enforced per-Pod GPU-memory contracts. In the validated setup, each Pod had an 8 GiB limit and successfully allocated 6 GiB; a 9 GiB allocation was rejected. The approach builds on MPS and adds Kubernetes scheduling, memory enforcement, and per-Pod metrics. The walkthrough uses a custom Amazon Linux 2023 image with an R615 driver, KAI Scheduler, and the GPU Fractioning Operator. It validates memory bounds and placement, not throughput, fault containment, or security isolation. Production use requires compatible hardware and software, capacity and runtime headroom, trusted workloads, and performance and rollback testing. It assumes pre-provisioned GPU capacity; GPU-fraction-aware autoscaling was not configured or validated.

### Source excerpt

Learn how to run two memory-bounded Kubernetes Pods on a single NVIDIA A10G GPU using open-source NVIDIA Run:ai GPU Fractioning on Amazon EKS. This walkthrough builds a custom Amazon Linux 2023 image, installs KAI Scheduler and the GPU Fractioning Operator, and validates per-Pod GPU-memory contracts with enforcement and metrics.

## Runtime security for Amazon EKS Auto Mode with Sysdig

DevFeed: [Runtime security for Amazon EKS Auto Mode with Sysdig](<https://devfeed.tech/articles/runtime-security-for-amazon-eks-auto-mode-with-sysdig-143966.md>)

Original publisher: [Read original article](<https://webflow.sysdig.com/blog/runtime-security-for-amazon-eks-auto-mode>)

Author: Eric Carter

Published: 2026-11-19T00:00:00Z

Content type: article

Language: en

Sources: [Sysdig](<https://devfeed.tech/sources/sysdig-blog.md>)

Topics: [workload protection](<https://devfeed.tech/topics/workload-protection.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Falco](<https://devfeed.tech/topics/falco.md>), [eBPF](<https://devfeed.tech/topics/ebpf.md>)

Tags: [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-eks-auto-mode](<https://devfeed.tech/tags/amazon-eks-auto-mode.md>), [cloud-workload-protection](<https://devfeed.tech/tags/cloud-workload-protection.md>), [detection](<https://devfeed.tech/tags/detection.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [falco](<https://devfeed.tech/tags/falco.md>), [filesystems](<https://devfeed.tech/tags/filesystems.md>), [host-shield](<https://devfeed.tech/tags/host-shield.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-security](<https://devfeed.tech/tags/kubernetes-security.md>), [loading](<https://devfeed.tech/tags/loading.md>), [node-management](<https://devfeed.tech/tags/node-management.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [runtime-security](<https://devfeed.tech/tags/runtime-security.md>), [security](<https://devfeed.tech/tags/security.md>), [shared-responsibility](<https://devfeed.tech/tags/shared-responsibility.md>), [shared-responsibility-model](<https://devfeed.tech/tags/shared-responsibility-model.md>), [sysdig](<https://devfeed.tech/tags/sysdig.md>), [sysdig-secure](<https://devfeed.tech/tags/sysdig-secure.md>), [threat-detection](<https://devfeed.tech/tags/threat-detection.md>), [universal-ebpf](<https://devfeed.tech/tags/universal-ebpf.md>)

### AI overview

EKS Auto Mode shifts node and core infrastructure management to AWS, but workload behavior at runtime remains the customer's responsibility. Since its Bottlerocket-based nodes do not allow kernel module loading, Sysdig uses an embedded Universal eBPF driver in Host Shield to monitor system calls without running anything on the host outside Kubernetes. Deployed as a Kubernetes workload, it follows nodes as AWS adds or replaces them. Sysdig Secure adds runtime policies, process and file monitoring, customizable Falco-based detections, and Kubernetes context for investigation alongside AWS controls such as GuardDuty, Security Hub, and network policies. The excerpt says runtime monitoring can catch suspicious behavior static scanning may miss; it recommends combining runtime security with posture management and vulnerability scanning. It suggests evaluating the setup on a small cluster by checking detections, context, and response workflows.

### Source excerpt

Amazon EKS Auto Mode hands node management to AWS, giving you immutable, Bottlerocket-based nodes with read-only root filesystems and no kernel module loading. But the shared responsibility model still applies: what happens inside your workloads at runtime is on you. This post explains how Sysdig Secure uses Universal eBPF and Falco-powered detection to deliver real-time runtime security on EKS Auto Mode. It covers deploying Host Shield, following nodes as AWS adds and replaces them, and catching threats with full Kubernetes context that static scanning alone can miss.

## How RiskSpan modernized its platform on AWS and cut processing time by 10x

DevFeed: [How RiskSpan modernized its platform on AWS and cut processing time by 10x](<https://devfeed.tech/articles/how-riskspan-modernized-its-platform-on-aws-and-cut-processing-time-by-10x-141898.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/migration-and-modernization/how-riskspan-modernized-its-platform-on-aws-and-cut-processing-time-by-10x/>)

Author: Pragya Purohit

Published: 2026-11-18T13:31:57Z

Content type: article

Language: en

Sources: [Migration & Modernization](<https://devfeed.tech/sources/migration-modernization.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [2027](<https://devfeed.tech/tags/2027.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-emr](<https://devfeed.tech/tags/amazon-emr.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [aws](<https://devfeed.tech/tags/aws.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-adoption](<https://devfeed.tech/tags/cloud-adoption.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [company](<https://devfeed.tech/tags/company.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [design](<https://devfeed.tech/tags/design.md>), [enterprise-governance-and-control](<https://devfeed.tech/tags/enterprise-governance-and-control.md>), [enterprise-strategy](<https://devfeed.tech/tags/enterprise-strategy.md>), [financial](<https://devfeed.tech/tags/financial.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [leader](<https://devfeed.tech/tags/leader.md>), [migration-solutions](<https://devfeed.tech/tags/migration-solutions.md>), [models](<https://devfeed.tech/tags/models.md>), [modernize](<https://devfeed.tech/tags/modernize.md>), [platform](<https://devfeed.tech/tags/platform.md>), [processing](<https://devfeed.tech/tags/processing.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [security-governance](<https://devfeed.tech/tags/security-governance.md>), [time](<https://devfeed.tech/tags/time.md>)

### AI overview

RiskSpan says its modernization removed architectural bottlenecks that horizontal scaling alone could not solve: workloads that once took up to 10 hours now finish in under an hour, and the article reports a 10x processing-time improvement. The team moved from a single-account monolith to isolated AWS accounts governed with Control Tower, then decomposed services onto Amazon EKS for independent scaling and deployment. It codified infrastructure and security controls, including scoped workload permissions and audit trails, and automated much of QA and release work. Reported results include 46% fewer client resource-support needs, 40% less manual QA, and more than double the feature throughput per release cycle. The article connects this foundation to faster AI-agent delivery and support for larger clients, while describing the figures and outcomes as RiskSpan's account of its journey.

### Source excerpt

This post is co-written with Praveen Vairavan and Anirudh Parmar from RiskSpan. RiskSpan, a financial analytics company, migrated to AWS but faced architectural design ceilings that horizontal scaling alone couldn't solve. As a recognized market leader, they felt the need to modernize their RiskSpan platform, which delivers cloud-native models for residential whole loans, MSRs, and [...]

## Yelp Migrates Cassandra to EKS by Moving EBS Volumes

DevFeed: [Yelp Migrates Cassandra to EKS by Moving EBS Volumes](<https://devfeed.tech/articles/yelp-migrates-cassandra-to-eks-by-moving-ebs-volumes-140160.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/kubernetes-cassandra-eks/>)

Author: Claudio Masolo

Published: 2026-11-18T09:00:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [migration](<https://devfeed.tech/topics/migration.md>), [cloud-migration](<https://devfeed.tech/topics/cloud-migration.md>), [Apache Cassandra](<https://devfeed.tech/topics/cassandra.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [data mobility](<https://devfeed.tech/topics/data-mobility.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [Amazon MSK](<https://devfeed.tech/topics/amazon-msk.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [cassandra](<https://devfeed.tech/tags/cassandra.md>), [cloud-migration](<https://devfeed.tech/tags/cloud-migration.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [ebs](<https://devfeed.tech/tags/ebs.md>), [eks](<https://devfeed.tech/tags/eks.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-cassandra-eks](<https://devfeed.tech/tags/kubernetes-cassandra-eks.md>), [moving](<https://devfeed.tech/tags/moving.md>), [news](<https://devfeed.tech/tags/news.md>), [volumes](<https://devfeed.tech/tags/volumes.md>), [yelp](<https://devfeed.tech/tags/yelp.md>)

### AI overview

Yelp moved about 90 Cassandra production clusters to Amazon EKS by reusing their existing EBS volumes instead of streaming data to new nodes. Its "Rolling PV Transplant" pre-created EKS volumes and claims pointing to the same volume IDs, then moved pods one at a time after each volume detached. Across roughly 1,000 pods and 1,000 TiB, the process avoided data transfer and extra compute; the largest cluster took about 12 hours, with no customer downtime or data loss. Because no nodes were decommissioned, rollback meant reversing the move. The method depends on EBS volumes being AZ-bound rather than cluster-bound, and a stale AWS CSI `VolumeAttachment` could leave an EKS pod Pending; Yelp recommends timeouts for stalled detach and attach operations. Monday.com's alternative added a new Cassandra datacenter, streamed data, and retired the old one afterward. That avoided relying on EBS volume portability and kept the old environment intact, but required both environments to run during a longer migration. Yelp also recommends checking repair state, backup IAM roles, and alert severity before migration.

### Source excerpt

Yelp has moved its Cassandra fleet from legacy self-managed Kubernetes clusters to Amazon EKS by re-pointing existing EBS volumes at new pods, rather than streaming data between nodes. By Claudio Masolo

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

## AWS Nitro Sandboxes Put Each EKS Pod in Its Own MicroVM with One RuntimeClass Field

DevFeed: [AWS Nitro Sandboxes Put Each EKS Pod in Its Own MicroVM with One RuntimeClass Field](<https://devfeed.tech/articles/aws-nitro-sandboxes-put-each-eks-pod-in-its-own-microvm-with-one-runtimeclass-field-134862.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/aws-nitro-sandboxes-eks/>)

Author: Steef-Jan Wiggers

Published: 2026-11-16T09:07:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Nitro System](<https://devfeed.tech/topics/nitro-system.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [attestation](<https://devfeed.tech/tags/attestation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-nitro-sandboxes-eks](<https://devfeed.tech/tags/aws-nitro-sandboxes-eks.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [containers](<https://devfeed.tech/tags/containers.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [eks](<https://devfeed.tech/tags/eks.md>), [field](<https://devfeed.tech/tags/field.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [half](<https://devfeed.tech/tags/half.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [key](<https://devfeed.tech/tags/key.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [microvm](<https://devfeed.tech/tags/microvm.md>), [news](<https://devfeed.tech/tags/news.md>), [nitro](<https://devfeed.tech/tags/nitro.md>), [one](<https://devfeed.tech/tags/one.md>), [passthrough](<https://devfeed.tech/tags/passthrough.md>), [pod](<https://devfeed.tech/tags/pod.md>), [release](<https://devfeed.tech/tags/release.md>), [sandboxes](<https://devfeed.tech/tags/sandboxes.md>), [security](<https://devfeed.tech/tags/security.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Nitro Sandboxes run opted-in EKS pods, ECS tasks, or EC2 workloads in separate Firecracker microVMs with their own guest kernels. On EKS, a RuntimeClass selects isolated or confidential mode; Auto Mode provisions capable nodes, while standard EKS requires a sandbox-enabled AMI. Isolated mode preserves tools such as exec and logs but trusts the parent instance. Confidential mode treats the parent as untrusted and can gate secret release on Nitro attestation measurements; those measurements must be checked by a KMS policy or external verifier for confidentiality guarantees to be complete. Network isolation removes the network device, including DNS, IMDS, and Pod Identity, and breaks HTTP/TCP probes. Constraints include no GPU passthrough, a limit of five sandboxes per node vCPU (halved on SMT instances), and no snapshot, restore, or live migration. The excerpt compares AWS's VM-based overhead, expressed through density and thread limits, with GKE's gVisor user-space kernel and its separate microVM option, which has stated per-pod resource costs and no GPU support.

### Source excerpt

AWS has launched Nitro Sandboxes, running each opted-in EKS pod, ECS task or EC2 workload in its own Firecracker microVM with a separate kernel, enabled by one runtimeClassName field at no extra charge. A confidential mode adds attestation-gated key release. The documentation lists the trade-offs: no GPU passthrough, at most five sandboxes per vCPU, and half the compute on SMT instances. By Steef-Jan Wiggers

## Remap Amazon EKS namespaces on restore with AWS Backup resource modifiers

DevFeed: [Remap Amazon EKS namespaces on restore with AWS Backup resource modifiers](<https://devfeed.tech/articles/remap-amazon-eks-namespaces-on-restore-with-aws-backup-resource-modifiers-131283.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/storage/remap-amazon-eks-namespaces-on-restore-with-aws-backup-resource-modifiers/>)

Author: Quinn Winter

Published: 2026-11-12T19:26:44Z

Content type: tutorial

Language: en

Sources: [AWS Storage Blog](<https://devfeed.tech/sources/aws-storage-blog.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [backups](<https://devfeed.tech/topics/backups.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.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-backup](<https://devfeed.tech/tags/aws-backup.md>), [backup](<https://devfeed.tech/tags/backup.md>), [data-protection](<https://devfeed.tech/tags/data-protection.md>), [modifiers](<https://devfeed.tech/tags/modifiers.md>), [namespaces](<https://devfeed.tech/tags/namespaces.md>), [restore](<https://devfeed.tech/tags/restore.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

AWS Backup resource modifiers let you restore an Amazon EKS namespace under a different name by applying ordered JSON Patch rules to each restored object. The walkthrough uses two rules: rename the cluster-scoped Namespace object and change `metadata.namespace` on namespaced objects, then restore into the same cluster. Modifiers are stored in S3, apply only to objects created during restore, and leave the recovery point unchanged; existing target objects are skipped. Namespace references embedded elsewhere--such as role bindings, DNS names, IRSA trust policies, and Pod Identity associations--are not rewritten automatically and may need separate updates. The article recommends testing rules before recovery and notes that EBS-backed claims follow their remapped volumes.

### Source excerpt

With AWS Backup resource modifiers, you can now remap an Amazon EKS namespace during a restore instead of recreating it in place. In this post, you back up a cluster and use a two-rule resource modifier to restore a namespace into a new namespace on the same cluster.

## Self-Service Namespace Onboarding on Amazon EKS: Automating Access Entries and RBAC with GitHub...

DevFeed: [Self-Service Namespace Onboarding on Amazon EKS: Automating Access Entries and RBAC with GitHub...](<https://devfeed.tech/articles/self-service-namespace-onboarding-on-amazon-eks-automating-access-entries-and-rbac-with-github-127576.md>)

Original publisher: [Read original article](<https://blog.devops.dev/self-service-namespace-onboarding-on-amazon-eks-automating-access-entries-and-rbac-with-github-74f0347e71e2?source=rss----33f8b2d9a328---4>)

Author: Oleh Adam Dubnytskyy

Published: 2026-11-10T09:42:12Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [admin](<https://devfeed.tech/tags/admin.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [api](<https://devfeed.tech/tags/api.md>), [api-server](<https://devfeed.tech/tags/api-server.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-eks](<https://devfeed.tech/tags/aws-eks.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [devops](<https://devfeed.tech/tags/devops.md>), [eks](<https://devfeed.tech/tags/eks.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [iam](<https://devfeed.tech/tags/iam.md>), [job](<https://devfeed.tech/tags/job.md>), [keys](<https://devfeed.tech/tags/keys.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [onboarding](<https://devfeed.tech/tags/onboarding.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [self-service](<https://devfeed.tech/tags/self-service.md>)

### AI overview

The excerpt describes namespace onboarding on Amazon EKS as two coordinated permission updates: an EKS access policy scope and Kubernetes RBAC. GitHub Actions authenticates through OIDC and temporary IAM role credentials. The EKS authorizer and RBAC authorizer can each allow a request, so effective permissions are their union; a restrictive custom RBAC role cannot narrow permissions already granted by a broader managed policy. The proposed setup uses separate workflows: one applies ClusterRoles and per-namespace RoleBindings, while another updates the access entry's namespace scope from files in a namespaces directory. The scripts validate namespace names, reject empty desired scopes, skip unchanged access-policy updates, and optionally prune stale managed RoleBindings. The excerpt notes that RBAC synchronization requires cluster-scoped rights and that missing namespaces are skipped with a warning before the workflow reports an error. The supplied text ends after describing this implementation and its pull request workflow.

### Source excerpt

Self-Service Namespace Onboarding on Amazon EKS: Automating Access Entries and RBAC with GitHub ActionsTwo authorization layers on Amazon EKS Every call my pipeline makes to the cluster's Kubernetes API server passes through two authorizers: Kubernetes RBAC and EKS access policies. Authentication: the access entry says who you are The pipeline never holds long-lived AWS keys. A GitHub Actions job gets an OIDC token, exchanges it for temporary credentials of an IAM role, and calls the cluster with them. More details on how it works can be seen here. Layer 1: Kubernetes RBAC RBAC is the standard Kubernetes model: Roles and ClusterRoles define rules, and RoleBindings attach them to a user or group. These objects live inside the cluster. You can write any rule you need, including rules for custom resources such as KEDA ScaledObject. Layer 2: EKS access policies Access policies are permission sets that AWS manages and that you attach to an access entry through the EKS API. They mirror the Kubernetes user-facing roles: AmazonEKSEditPolicy corresponds to edit, AmazonEKSAdminPolicy to admin, and so on. Each association has a scope: the whole cluster (type=cluster) or a list of namespaces (type=namespace). You can't modify an access policy or create your own. When the managed policies don't fit, more control can be configured by leveraging Kubernetes RBAC objects instead. How the two layers combine The API server chains its authorizers. The RBAC authorizer runs first and returns immediately if it allows the request. If RBAC has no opinion, the request goes to the EKS authorizer, which checks the access policies. If neither allows it, the request is denied. The access entry only establishes who the caller is; RBAC and access policies each get one chance to allow the request. Both authorizers can only allow or pass, so the effective permissions of ci-github-actions in a namespace are the union of both layers. That has two consequences for the automation: Onboarding a namespace

## LangSmith BYOC on AWS is generally available

DevFeed: [LangSmith BYOC on AWS is generally available](<https://devfeed.tech/articles/langsmith-byoc-on-aws-is-generally-available-123894.md>)

Original publisher: [Read original article](<https://www.langchain.com/blog/langsmith-byoc-is-now-generally-available-on-aws>)

Author: LangChain Accounts

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

Content type: release

Language: en

Sources: [LangChain Blog](<https://devfeed.tech/sources/langchain-blog.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Security, Identity, & Compliance](<https://devfeed.tech/topics/security-identity-compliance.md>), [observability](<https://devfeed.tech/topics/observability.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agents-in-production](<https://devfeed.tech/tags/agents-in-production.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bring-your-own-cloud](<https://devfeed.tech/tags/bring-your-own-cloud.md>), [byoc](<https://devfeed.tech/tags/byoc.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [inside](<https://devfeed.tech/tags/inside.md>), [langsmith](<https://devfeed.tech/tags/langsmith.md>), [managed](<https://devfeed.tech/tags/managed.md>), [observability](<https://devfeed.tech/tags/observability.md>), [teams](<https://devfeed.tech/tags/teams.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

LangSmith BYOC is generally available to Enterprise customers on AWS, placing sensitive LangSmith data and agent workloads in the customer's AWS account and VPC while LangChain operates the deployment. Its data plane includes a private EKS cluster, databases, and storage; a control plane in LangChain's cloud handles authentication, organization settings, billing metadata, and provisioning. The planes communicate through AWS PrivateLink. LangChain manages upgrades, scaling, patching, backups, and monitoring. Customers retain ownership of the AWS environment and data, and the provisioning role is scoped to infrastructure management without specified trace or database read permissions. BYOC is offered across 15 AWS regions in the US, EU, and APAC. Most core observability, evaluation, deployment, sandbox, and gateway capabilities are available; it requires the Enterprise plan and contacting LangChain to get started.

### Source excerpt

LangSmith Bring Your Own Cloud is now generally available on AWS, giving Enterprise teams managed observability, evaluation, and deployment inside their own VPC.

## Zero-Copy Migration: How Yelp Moved Its Cassandra Fleet Between Kubernetes Clusters

DevFeed: [Zero-Copy Migration: How Yelp Moved Its Cassandra Fleet Between Kubernetes Clusters](<https://devfeed.tech/articles/zero-copy-migration-how-yelp-moved-its-cassandra-fleet-between-kubernetes-clusters-127020.md>)

Original publisher: [Read original article](<https://engineeringblog.yelp.com/2026/11/zero-copy-cassandra-kubernetes-migration.html>)

Author: Ilkin Mammadzada and Max Falk, Site Reliability Engineers

Published: 2026-11-09T00:00:00Z

Content type: article

Language: en

Sources: [Yelp](<https://devfeed.tech/sources/yelp.md>)

Topics: [Apache Cassandra](<https://devfeed.tech/topics/cassandra.md>), [data migrations](<https://devfeed.tech/topics/data-migrations.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [observability](<https://devfeed.tech/topics/observability.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>)

Tags: [ads](<https://devfeed.tech/tags/ads.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-cassandra](<https://devfeed.tech/tags/apache-cassandra.md>), [blog](<https://devfeed.tech/tags/blog.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [but](<https://devfeed.tech/tags/but.md>), [cassandra](<https://devfeed.tech/tags/cassandra.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [control](<https://devfeed.tech/tags/control.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [copy](<https://devfeed.tech/tags/copy.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-clusters](<https://devfeed.tech/tags/kubernetes-clusters.md>), [migration](<https://devfeed.tech/tags/migration.md>), [yelp](<https://devfeed.tech/tags/yelp.md>), [zero](<https://devfeed.tech/tags/zero.md>), [zero-copy](<https://devfeed.tech/tags/zero-copy.md>)

### AI overview

Yelp moved about 90 Cassandra clusters, roughly 1,000 pods and 1,000 TiB of data from self-managed Kubernetes to EKS by transplanting EBS volumes instead of streaming data. Because the volumes were tied to Availability Zones rather than Kubernetes clusters, the team prepared matching PVs and PVCs in EKS, then moved pods one at a time: stop a legacy pod, let its volume detach, and start the waiting EKS pod with the same data and token range. Cassandra replication let the remaining ring serve traffic during each handoff; the team paused both operators' reconciliation to avoid conflicts and resumed the EKS operator after migration. Manual development runs informed an automated script, followed by a three-week production rollout. Yelp reports zero customer-facing downtime and no data loss; the largest cluster, with 54 pods, took about 12 hours. About 5% of pod moves encountered stale VolumeAttachment objects, which could leave pods waiting despite detached volumes. The migration also exposed backup IAM and alerting problems, disabled repairs, and other fleet issues. Rollback was the same volume handoff in reverse.

### Source excerpt

Introduction How do you move a large Cassandra fleet of around 1000 Kubernetes Pods and a petabyte of data across Kubernetes clusters without anyone noticing? Apache Cassandra powers many of Yelp's core features, from user profiles to ads and search. We run it on Kubernetes, orchestrated by a custom operator covered in our earlier blog post. When Yelp migrated its Kubernetes control plane to Amazon EKS, most workloads moved over seamlessly, but Cassandra was left behind on our legacy self-managed clusters alongside its persistent EBS-backed storage. The conventional way to move Cassandra between clusters is to stream the data: add...

## Addressing protocol security gaps in multi-tenant Kubernetes

DevFeed: [Addressing protocol security gaps in multi-tenant Kubernetes](<https://devfeed.tech/articles/addressing-protocol-security-gaps-in-multi-tenant-kubernetes-122100.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/security/addressing-protocol-security-gaps-in-multi-tenant-kubernetes/>)

Author: Ajinkya Patil

Published: 2026-11-06T21:08:50Z

Content type: article

Language: en

Sources: [AWS Security Blog](<https://devfeed.tech/sources/aws-security-blog.md>)

Topics: [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [adb](<https://devfeed.tech/topics/adb.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [WebRTC](<https://devfeed.tech/topics/webrtc.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [container-networking](<https://devfeed.tech/topics/container-networking.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>)

Tags: [active-directory](<https://devfeed.tech/tags/active-directory.md>), [adb](<https://devfeed.tech/tags/adb.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-kinesis-video-streams](<https://devfeed.tech/tags/amazon-kinesis-video-streams.md>), [android](<https://devfeed.tech/tags/android.md>), [android-debug-bridge](<https://devfeed.tech/tags/android-debug-bridge.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [audit](<https://devfeed.tech/tags/audit.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [network](<https://devfeed.tech/tags/network.md>), [pods](<https://devfeed.tech/tags/pods.md>), [policies](<https://devfeed.tech/tags/policies.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [protocol-security](<https://devfeed.tech/tags/protocol-security.md>), [protocols](<https://devfeed.tech/tags/protocols.md>), [security](<https://devfeed.tech/tags/security.md>), [security-blog](<https://devfeed.tech/tags/security-blog.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [webrtc](<https://devfeed.tech/tags/webrtc.md>)

### AI overview

The article describes a multi-tenant EKS design that adds security to unauthenticated protocols using namespace-scoped Envoy Gateway mTLS, short-lived certificates issued and rotated through cert-manager and AWS Private CA, and Kinesis Video Streams as managed TURN infrastructure for WebRTC. A custom API validates enterprise IdP JWTs, authorizes namespace access, returns connection details, and records identity, namespace, and time. The design depends on default-deny NetworkPolicies and namespace isolation; ADB traffic between Envoy and the pod is not encrypted, and immediate certificate revocation requires CRL or OCSP infrastructure. Compared with bastion forwarding through the Kubernetes API server, the reported Envoy path adds under 50 ms gateway latency, with ADB commands under 100 ms and installs under 30 seconds. Managed TURN removes the custom token-exchange service and, according to the article, kept WebRTC stable during peak use and removed manual routing updates after Availability Zone migrations. The post focuses on architecture and lessons, assumes existing EKS, IdP, and AWS Private CA setup, and notes that the JWT identity chain requires deployment-specific custom work

### Source excerpt

Protocols like Android Debug Bridge (ADB) and Web Real-Time Communication (WebRTC), by default, use unencrypted channels for network communications and don't support enterprise authentication mechanisms like JSON Web Tokens (JWTs). In a multi-tenant Kubernetes cluster--including Amazon Elastic Kubernetes Service (Amazon EKS)--pods can reach other tenants' open ports by default unless you configure network policies to [...]

## Are your Kubernetes CPU limits actually being enforced?

DevFeed: [Are your Kubernetes CPU limits actually being enforced?](<https://devfeed.tech/articles/are-your-kubernetes-cpu-limits-actually-being-enforced-121732.md>)

Original publisher: [Read original article](<https://www.gremlin.com/blog/are-your-kubernetes-cpu-limits-actually-being-enforced>)

Author: Andre Newman

Published: 2026-11-06T00:00:00Z

Content type: article

Language: en

Sources: [Gremlin Blog](<https://devfeed.tech/sources/gremlin-blog.md>)

Topics: [scheduling](<https://devfeed.tech/topics/scheduling.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Azure Kubernetes Service](<https://devfeed.tech/topics/azure-kubernetes-service.md>), [Gke](<https://devfeed.tech/topics/gke.md>), [health check](<https://devfeed.tech/topics/health-check.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [cfs](<https://devfeed.tech/tags/cfs.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [features](<https://devfeed.tech/tags/features.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [limits](<https://devfeed.tech/tags/limits.md>), [quotas](<https://devfeed.tech/tags/quotas.md>)

### AI overview

Kubernetes CPU limits are enforced through kubelet CFS quotas; if `cpuCFSQuota` is disabled, containers can exceed declared limits and use CPU beyond their request share. Check a container's cgroup v2 `cpu.max`: `20000 100000` indicates a 200m quota, while `max 100000` indicates no cap. The article describes checking kubelet configuration and matching affected nodes to pods with CPU limits. Disabling quotas can reduce throttling-related latency for multithreaded services, but leaves declared limits misleading; alternatives include raising limits, removing them for selected workloads while keeping requests, or using a dedicated node pool. Before re-enabling quotas, review and right-size limits to avoid new throttling. Set `cpuCFSQuota: true` using the configuration path for the cluster type, restart affected workloads so quotas take effect, then verify `cpu.max` again.

### Source excerpt

Kubernetes CPU limits only work if the kubelet enforces CFS quotas. Learn what happens when cpuCFSQuota is disabled, how to check your nodes, and how to fix it safely.

## What Happens When Your EKS Version Reaches End of Support?

DevFeed: [What Happens When Your EKS Version Reaches End of Support?](<https://devfeed.tech/articles/what-happens-when-your-eks-version-reaches-end-of-support-121145.md>)

Original publisher: [Read original article](<https://www.fairwinds.com/blog/what-happens-when-your-eks-version-reaches-end-of-support>)

Author: Husne Ozmen

Published: 2026-11-05T18:06:33Z

Content type: article

Language: en

Sources: [Fairwinds](<https://devfeed.tech/sources/fairwinds-blog.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [version](<https://devfeed.tech/topics/version.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [add-ons](<https://devfeed.tech/tags/add-ons.md>), [aks](<https://devfeed.tech/tags/aks.md>), [allows](<https://devfeed.tech/tags/allows.md>), [also](<https://devfeed.tech/tags/also.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [announce](<https://devfeed.tech/tags/announce.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [applying](<https://devfeed.tech/tags/applying.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [costs](<https://devfeed.tech/tags/costs.md>), [eks](<https://devfeed.tech/tags/eks.md>), [end-of-support](<https://devfeed.tech/tags/end-of-support.md>), [featured](<https://devfeed.tech/tags/featured.md>), [managed-kubernetes](<https://devfeed.tech/tags/managed-kubernetes.md>), [risks](<https://devfeed.tech/tags/risks.md>), [support](<https://devfeed.tech/tags/support.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

When EKS standard support ends, a cluster moves automatically to extended support, raising the control plane fee from $0.10 to $0.60 per hour--about $4,380 per year per cluster. Twelve months later, AWS upgrades the control plane on its schedule; node AMIs and add-ons remain the customer's responsibility except in EKS Auto Mode. The guide recommends upgrading before the deadline, one minor version at a time, after reviewing release notes and checking deprecated APIs, add-on compatibility, and node changes. It describes testing upgrades in dedicated provider-specific clusters, rolling through non-production first and letting changes bake for at least a week before production, with readiness and workload health monitored throughout. A standard-support-only policy avoids extended-support fees by triggering an AWS-scheduled control-plane upgrade at standard support's end, but the text cautions that this offers less control. Dates given are EKS 1.31 extended support ending November 26, 2026, and 1.34 standard support ending December 2, 2026.

### Source excerpt

Learn what happens when your Amazon EKS version reaches end of support, including costs, upgrade risks, and best practices for a smooth transition.

## How Regeneron built a multi-executor Omics platform with intelligent resource management on AWS

DevFeed: [How Regeneron built a multi-executor Omics platform with intelligent resource management on AWS](<https://devfeed.tech/articles/how-regeneron-built-a-multi-executor-omics-platform-with-intelligent-resource-management-on-aws-117620.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/hpc/how-regeneron-built-a-multi-executor-omics-platform-with-intelligent-resource-management-on-aws/>)

Author: Siddhesh Salunke

Published: 2026-11-03T20:34:05Z

Content type: article

Language: en

Sources: [AWS HPC Blog](<https://devfeed.tech/sources/aws-hpc-blog.md>)

Topics: [High-Performance Computing](<https://devfeed.tech/topics/high-performance-computing.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Security, Identity, & Compliance](<https://devfeed.tech/topics/security-identity-compliance.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>)

Tags: [accessible](<https://devfeed.tech/tags/accessible.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-fsx-for-lustre](<https://devfeed.tech/tags/amazon-fsx-for-lustre.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-batch](<https://devfeed.tech/tags/aws-batch.md>), [aws-parallel-computing-service](<https://devfeed.tech/tags/aws-parallel-computing-service.md>), [aws-parallelcluster](<https://devfeed.tech/tags/aws-parallelcluster.md>), [compute](<https://devfeed.tech/tags/compute.md>), [computing](<https://devfeed.tech/tags/computing.md>), [core](<https://devfeed.tech/tags/core.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [executor](<https://devfeed.tech/tags/executor.md>), [genomics](<https://devfeed.tech/tags/genomics.md>), [high-performance-computing](<https://devfeed.tech/tags/high-performance-computing.md>), [hpc](<https://devfeed.tech/tags/hpc.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [like](<https://devfeed.tech/tags/like.md>), [managed](<https://devfeed.tech/tags/managed.md>), [management](<https://devfeed.tech/tags/management.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [pharmaceuticals](<https://devfeed.tech/tags/pharmaceuticals.md>), [platform](<https://devfeed.tech/tags/platform.md>), [post](<https://devfeed.tech/tags/post.md>), [processes](<https://devfeed.tech/tags/processes.md>), [resource](<https://devfeed.tech/tags/resource.md>), [resource-management](<https://devfeed.tech/tags/resource-management.md>), [storage](<https://devfeed.tech/tags/storage.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Regeneron runs Nextflow genomics workflows from an AWS ParallelCluster head node and routes individual processes to SLURM, AWS Batch, or EKS using labels, letting workloads use different backends without pipeline code changes. The backends share FSx for Lustre; persistent container and reference caches sit there, while intermediate files use local NVMe. Regeneron's Haizi Bot scores each sample from FASTQ metrics, predicts resource needs from prior executions, and generates per-run Nextflow configurations according to cost, speed, and cluster conditions. Its cost mode favors Spot capacity and reports up to 60% lower cost; its time mode uses On-Demand resources and reports 30% faster completion, both against static allocation in internal benchmarks. The post also reports 95% pre-run cost-prediction accuracy. These figures are Regeneron-reported; the post is an architecture deep-dive, not a step-by-step tutorial.

### Source excerpt

This post references AWS ParallelCluster. Check out AWS Parallel Computing Service (AWS PCS), our new managed Slurm service for running HPC and AI workloads on AWS. Regeneron Pharmaceuticals processes thousands of genomic samples each week, using Nextflow as a core part of its scientific computing infrastructure. When its genomics workloads like ATAC-seq (Assay for Transposase-Accessible [...]

## When a Small Team Should (and Shouldn't) Adopt Kubernetes

DevFeed: [When a Small Team Should (and Shouldn't) Adopt Kubernetes](<https://devfeed.tech/articles/when-a-small-team-should-and-shouldn-t-adopt-kubernetes-109868.md>)

Original publisher: [Read original article](<https://hackernoon.com/when-a-small-team-should-and-shouldnt-adopt-kubernetes?source=rss>)

Author: Alana stefan

Published: 2026-10-31T00:39:43Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Azure Kubernetes Service](<https://devfeed.tech/topics/azure-kubernetes-service.md>), [Gke](<https://devfeed.tech/topics/gke.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [adopting](<https://devfeed.tech/tags/adopting.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [aks](<https://devfeed.tech/tags/aks.md>), [alerting](<https://devfeed.tech/tags/alerting.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [apps](<https://devfeed.tech/tags/apps.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automated](<https://devfeed.tech/tags/automated.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [benefits](<https://devfeed.tech/tags/benefits.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [costs](<https://devfeed.tech/tags/costs.md>), [decision](<https://devfeed.tech/tags/decision.md>), [devops](<https://devfeed.tech/tags/devops.md>), [do-small-teams-need-kubernetes](<https://devfeed.tech/tags/do-small-teams-need-kubernetes.md>), [is-kubernetes-right-for-me](<https://devfeed.tech/tags/is-kubernetes-right-for-me.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-adoption](<https://devfeed.tech/tags/kubernetes-adoption.md>), [learn](<https://devfeed.tech/tags/learn.md>), [right](<https://devfeed.tech/tags/right.md>), [small](<https://devfeed.tech/tags/small.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [team](<https://devfeed.tech/tags/team.md>), [when-to-adopt-kubernetes](<https://devfeed.tech/tags/when-to-adopt-kubernetes.md>)

### AI overview

Kubernetes can help small teams when many services need independent scaling, releases must be frequent and safe, workloads need portability, and someone can own the platform. Its orchestration benefits come with work to configure and maintain networking, storage, access controls, upgrades, monitoring, and costs. For a few services, predictable traffic, or a team still validating its product, a virtual machine or managed container or application platform may be simpler; Docker Compose is suggested for small tools. The article recommends assessing service count, scaling needs, release frequency, containerization, ownership, and maintenance capacity. If adopting, use a managed control plane, start with a non-critical workload, set resource limits, add monitoring, automate deployments, and plan upgrades.

### Source excerpt

Learn when a small team should or shouldn't adopt Kubernetes. Explore the benefits, challenges, costs, and simpler alternatives to make the right decision for y

## How BMW Group accelerated connected vehicle workloads on AWS Graviton

DevFeed: [How BMW Group accelerated connected vehicle workloads on AWS Graviton](<https://devfeed.tech/articles/how-bmw-group-accelerated-connected-vehicle-workloads-on-aws-graviton-107149.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/how-bmw-group-accelerated-connected-vehicle-workloads-on-aws-graviton/>)

Author: Tomislav Lozančić

Published: 2026-10-29T20:11:14Z

Content type: article

Language: en

Sources: [AWS Architecture Blog](<https://devfeed.tech/sources/aws-architecture-blog.md>)

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

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [automotive](<https://devfeed.tech/tags/automotive.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-graviton](<https://devfeed.tech/tags/aws-graviton.md>), [bmw](<https://devfeed.tech/tags/bmw.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [container](<https://devfeed.tech/tags/container.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [graviton](<https://devfeed.tech/tags/graviton.md>), [ingress](<https://devfeed.tech/tags/ingress.md>), [karpenter](<https://devfeed.tech/tags/karpenter.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [performance](<https://devfeed.tech/tags/performance.md>), [platform](<https://devfeed.tech/tags/platform.md>), [x86](<https://devfeed.tech/tags/x86.md>)

### AI overview

BMW Group migrated its Connected Vehicle platform from x86 to AWS Graviton incrementally, while keeping both architectures available and deployments uninterrupted. Karpenter replaced fixed node groups with dynamic provisioning; tainted Graviton node pools required workloads to opt in, and dual-architecture container images let one tag serve arm64 and amd64. For image builds, native architecture-specific runners avoid QEMU emulation overhead and surface compatibility issues earlier, but require dedicated runners; QEMU builds run from one machine but can be much slower for compute-heavy workloads. BMW supported both approaches and used native Graviton runners for platform-scale arm64 builds. The article reports about $600,000 in annualized infrastructure savings, around 57% lower CPU use for the NGINX ingress controller at the same ingress profile, and about 40% better price-performance. More than 65% of the platform now runs on Graviton in production.

### Source excerpt

Learn how BMW Group migrated its connected vehicle platform from x86 to AWS Graviton. Using Karpenter, multi-architecture container builds, and Graviton-based CI/CD runners, the team moved workloads without disruption, cutting NGINX ingress CPU by about 57 percent and delivering about 40 percent better price-performance.

## Unlocking full-stack observability for AWS Outposts

DevFeed: [Unlocking full-stack observability for AWS Outposts](<https://devfeed.tech/articles/unlocking-full-stack-observability-for-aws-outposts-108368.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/unlocking-full-stack-observability-for-aws-outposts/>)

Author: Aishwariya Khiani

Published: 2026-10-29T18:23:18Z

Content type: article

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [AWS Outposts](<https://devfeed.tech/topics/aws-outposts.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>)

Tags: [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automated-incident-response](<https://devfeed.tech/tags/automated-incident-response.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-outposts](<https://devfeed.tech/tags/aws-outposts.md>), [aws-systems-manager](<https://devfeed.tech/tags/aws-systems-manager.md>), [build](<https://devfeed.tech/tags/build.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [compute](<https://devfeed.tech/tags/compute.md>), [containers](<https://devfeed.tech/tags/containers.md>), [data](<https://devfeed.tech/tags/data.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [dimensions](<https://devfeed.tech/tags/dimensions.md>), [eventbridge](<https://devfeed.tech/tags/eventbridge.md>), [full](<https://devfeed.tech/tags/full.md>), [full-stack](<https://devfeed.tech/tags/full-stack.md>), [observability](<https://devfeed.tech/tags/observability.md>), [stack](<https://devfeed.tech/tags/stack.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The post outlines hybrid AWS Outposts monitoring across connectivity, storage, compute, and containers using Systems Manager, CloudWatch, and EventBridge. For Regional dependencies, it recommends pairing each service's CloudWatch metrics with the Outposts service-link ConnectedStatus to help distinguish dependency failures from connectivity drops. It lists S3 and EBS capacity and replication metrics, and Outposts instance capacity metrics for proactive planning because capacity is fixed. For EKS on Outposts, it describes self-managed worker nodes using AL2023 and nodeadm (managed node groups are unsupported in Outpost subnets), installing the CloudWatch Observability add-on, verifying Container Insights metrics, and combining infrastructure and workload metrics in a CloudWatch dashboard. EventBridge can create OpsCenter work items from health events; the text notes that Systems Manager Patch Manager depends on Regional endpoint connectivity through the service link.

### Source excerpt

Learn how to build end-to-end observability for AWS Outposts across four dimensions: network, storage, compute, and containers. This post uses AWS Systems Manager, Amazon CloudWatch, and Amazon EventBridge for unified visibility and automated incident response across hybrid infrastructure spanning your data center and an AWS Region.

## Preparing for large-scale live streaming events on AWS -- Part 2

DevFeed: [Preparing for large-scale live streaming events on AWS -- Part 2](<https://devfeed.tech/articles/preparing-for-large-scale-live-streaming-events-on-aws-part-2-107158.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/media/preparing-for-large-scale-live-streaming-events-on-aws-part-2/>)

Author: Manish Joshi

Published: 2026-10-29T14:36:46Z

Content type: article

Language: en

Sources: [AWS for M&E Blog](<https://devfeed.tech/sources/aws-for-m-e-blog.md>)

Topics: [Streaming](<https://devfeed.tech/topics/streaming.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Chaos Engineering](<https://devfeed.tech/topics/chaos-engineering.md>), [AWS Fault Injection Service (FIS)](<https://devfeed.tech/topics/aws-fault-injection-service-fis.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [amazon-cloudfront](<https://devfeed.tech/tags/amazon-cloudfront.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-support](<https://devfeed.tech/tags/aws-support.md>), [blog](<https://devfeed.tech/tags/blog.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [capacity-planning](<https://devfeed.tech/tags/capacity-planning.md>), [chaos](<https://devfeed.tech/tags/chaos.md>), [chaos-engineering](<https://devfeed.tech/tags/chaos-engineering.md>), [content](<https://devfeed.tech/tags/content.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [events](<https://devfeed.tech/tags/events.md>), [industries](<https://devfeed.tech/tags/industries.md>), [live](<https://devfeed.tech/tags/live.md>), [live-streaming](<https://devfeed.tech/tags/live-streaming.md>), [media-entertainment](<https://devfeed.tech/tags/media-entertainment.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The post recommends proving live-event readiness with realistic full-scale rehearsals, controlled failure injection, and edge delivery tuning. For CloudFront, it describes Origin Shield as a way to consolidate cache misses and protect origin capacity, alongside consistent origins, normalized cache keys, and short-segment cache efficiency. It distinguishes Lambda@Edge for compute-intensive Node.js or Python media customization from lower-cost CloudFront Functions for lightweight request-path operations. Testing proceeds from isolated components at twice expected peak, through integration at expected peak, to production rehearsal at 1.3-1.5 times peak and spike/failure tests; realistic profiles include a 60-minute ramp, sustained load, periodic spikes, and failover. The post also calls for separate signup/payment and ad-decisioning tests, viewer-based chaos thresholds with AWS Fault Injection Service, and early AWS support engagement: Unified Operations for Media or Countdown Premium, onboarded weeks before the event.

### Source excerpt

This post is part 2 in a two-part blog post series. Part 1 covers strategy, architecture evaluation, and capacity planning. Part 2 covers content delivery, nonfunctional testing, chaos engineering, and Amazon Web Services (AWS) support models.

## Preparing for large-scale live streaming events on AWS -- Part 1

DevFeed: [Preparing for large-scale live streaming events on AWS -- Part 1](<https://devfeed.tech/articles/preparing-for-large-scale-live-streaming-events-on-aws-part-1-107157.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/media/preparing-for-large-scale-live-streaming-events-on-aws-part-1/>)

Author: Manish Joshi

Published: 2026-10-29T14:36:20Z

Content type: article

Language: en

Sources: [AWS for M&E Blog](<https://devfeed.tech/sources/aws-for-m-e-blog.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon Route 53](<https://devfeed.tech/topics/amazon-route-53.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>)

Tags: [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-keyspaces-for-apache-cassandra](<https://devfeed.tech/tags/amazon-keyspaces-for-apache-cassandra.md>), [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-support](<https://devfeed.tech/tags/aws-support.md>), [aws-well-architected-framework](<https://devfeed.tech/tags/aws-well-architected-framework.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [capacity-planning](<https://devfeed.tech/tags/capacity-planning.md>), [chaos-engineering](<https://devfeed.tech/tags/chaos-engineering.md>), [content](<https://devfeed.tech/tags/content.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [events](<https://devfeed.tech/tags/events.md>), [industries](<https://devfeed.tech/tags/industries.md>), [large](<https://devfeed.tech/tags/large.md>), [live](<https://devfeed.tech/tags/live.md>), [live-streaming](<https://devfeed.tech/tags/live-streaming.md>), [media-entertainment](<https://devfeed.tech/tags/media-entertainment.md>), [planning](<https://devfeed.tech/tags/planning.md>), [series](<https://devfeed.tech/tags/series.md>), [strategy](<https://devfeed.tech/tags/strategy.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Large live streaming events can multiply baseline concurrency within minutes and also create separate surges in sign-ups, authentication, and payments; reactive auto scaling alone may lag. The article recommends treating readiness as a multimonth effort: review the full architecture across engineering, operations, and security; focus on scaling, identity, networking, and data bottlenecks; isolate critical viewer services and define graceful degradation. For capacity, combine instance diversification with On-Demand Capacity Reservations where assurance is needed, pre-provision EKS control plane capacity, keep warm compute, and reserve load balancer headroom based on load tests. Pre-scale databases and caches, check maintenance and quotas, and request network pre-warming when testing indicates limits may be approached. Business measures--early signup campaigns, pre-event programming, and loading secondary features after playback--can smooth demand. Part 1 covers strategy, architecture, and capacity planning; content delivery, testing, chaos engineering, and AWS support models are left to Part 2.

### Source excerpt

This post is part 1 in a two-part blog post series. Part 1 covers strategy, architecture evaluation, and capacity planning. Part 2 covers content delivery, nonfunctional testing, chaos engineering, and Amazon Web Services (AWS) support models.

## One pod, one node: The architecture behind serverless Kubernetes on AWS

DevFeed: [One pod, one node: The architecture behind serverless Kubernetes on AWS](<https://devfeed.tech/articles/one-pod-one-node-the-architecture-behind-serverless-kubernetes-on-aws-102145.md>)

Original publisher: [Read original article](<https://thenewstack.io/serverless-kubernetes-aws-fargate/>)

Author: Sri Saran Balaji Vellore Rajakumar

Published: 2026-10-27T12:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Overview, News and Trends | The New Stack](<https://devfeed.tech/sources/kubernetes-overview-news-and-trends-the-new-stack.md>), [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [AWS Fargate](<https://devfeed.tech/topics/aws-fargate.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [account](<https://devfeed.tech/tags/account.md>), [admission](<https://devfeed.tech/tags/admission.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-marketplace](<https://devfeed.tech/tags/aws-marketplace.md>), [changes](<https://devfeed.tech/tags/changes.md>), [containers](<https://devfeed.tech/tags/containers.md>), [first](<https://devfeed.tech/tags/first.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [network](<https://devfeed.tech/tags/network.md>), [node](<https://devfeed.tech/tags/node.md>), [one](<https://devfeed.tech/tags/one.md>), [pod](<https://devfeed.tech/tags/pod.md>), [post-contributed](<https://devfeed.tech/tags/post-contributed.md>), [required](<https://devfeed.tech/tags/required.md>), [routing](<https://devfeed.tech/tags/routing.md>), [scheduling](<https://devfeed.tech/tags/scheduling.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [sponsor-aws-marketplace](<https://devfeed.tech/tags/sponsor-aws-marketplace.md>), [sponsored-post-contributed](<https://devfeed.tech/tags/sponsored-post-contributed.md>), [worker](<https://devfeed.tech/tags/worker.md>)

### AI overview

EKS Fargate makes the pod the unit of infrastructure: it provisions a dedicated environment and VPC network interface for each selected pod, then removes the environment when the pod ends. An admission webhook matches pods to Fargate profiles and routes them to a dedicated scheduler, which requests capacity and waits for the runtime to register a ready node before binding the pod. The runtime supplies Kubernetes node components, while separate network namespaces isolate platform services, node functions, and workload traffic. Fargate periodically recycles pods for security patches using Kubernetes eviction and PodDisruptionBudgets, though a pod can eventually be deleted if disruption cannot proceed by its scheduled termination time. Each pod needs a matching profile, private subnet and ENI capacity; pods have no public IP. Workloads needing node access--such as DaemonSets, host networking, privileged operations, GPUs, or host-attached storage--do not fit this model; EFS is identified as the supported durable shared file storage pattern.

### Source excerpt

A pod-level walkthrough of admission routing, dedicated scheduling, and network isolation, no worker nodes required Serverless Kubernetes changes who manages The post One pod, one node: The architecture behind serverless Kubernetes on AWS appeared first on The New Stack.

## How We Run 250,000 Automated Tests a Day on Kubernetes

DevFeed: [How We Run 250,000 Automated Tests a Day on Kubernetes](<https://devfeed.tech/articles/how-we-run-250-000-automated-tests-a-day-on-kubernetes-102335.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-we-run-250000-automated-tests-a-day-on-kubernetes?source=rss>)

Author: lokeshsuri

Published: 2026-10-27T11:00:02Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Test automation](<https://devfeed.tech/topics/test-automation.md>), [kueue](<https://devfeed.tech/topics/kueue.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [dynamic test splitting](<https://devfeed.tech/topics/dynamic-test-splitting.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [audit](<https://devfeed.tech/tags/audit.md>), [automated](<https://devfeed.tech/tags/automated.md>), [certification](<https://devfeed.tech/tags/certification.md>), [cicd](<https://devfeed.tech/tags/cicd.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [devops](<https://devfeed.tech/tags/devops.md>), [eks](<https://devfeed.tech/tags/eks.md>), [financial-services](<https://devfeed.tech/tags/financial-services.md>), [flaky-tests](<https://devfeed.tech/tags/flaky-tests.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kueue](<https://devfeed.tech/tags/kueue.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [policy](<https://devfeed.tech/tags/policy.md>), [quotas](<https://devfeed.tech/tags/quotas.md>), [sharding](<https://devfeed.tech/tags/sharding.md>), [software-testing](<https://devfeed.tech/tags/software-testing.md>), [test-automation](<https://devfeed.tech/tags/test-automation.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### AI overview

The article describes a centralized platform running about 250,000 tests daily across four Amazon EKS clusters, using Kubernetes Indexed Jobs to shard suites and Kueue quotas and priorities to manage shared capacity. It recommends balancing shards by historical duration, retrying a failed shard once on a fresh pod, and recording whether failures come from tests, the environment, or infrastructure so reporting can distinguish flakes and support release certification. Multiple clusters reduce blast radius but add routing, upgrades, and configuration overhead. The authors frame quotas, failure policy, and trustworthy reporting as core platform responsibilities, while noting centralization creates a shared dependency and is a poor fit for small organizations or workloads needing specialized hardware.

### Source excerpt

How a financial-services firm runs 250,000 automated tests a day on 4 Amazon EKS clusters with Kueue quotas, sharding, flake policy, and certification.

## 20 AWS Cost Optimization Moves That Still Pay Off

DevFeed: [20 AWS Cost Optimization Moves That Still Pay Off](<https://devfeed.tech/articles/20-aws-cost-optimization-moves-that-still-pay-off-100572.md>)

Original publisher: [Read original article](<https://hackernoon.com/20-aws-cost-optimization-moves-that-still-pay-off?source=rss>)

Author: Fedir Kompaniiets

Published: 2026-10-26T15:58:42Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Graviton](<https://devfeed.tech/topics/graviton.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [AWS Fargate](<https://devfeed.tech/topics/aws-fargate.md>), [AWS consulting](<https://devfeed.tech/topics/aws-consulting.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2017](<https://devfeed.tech/tags/2017.md>), [2025](<https://devfeed.tech/tags/2025.md>), [amazon-s3-intelligent-tiering](<https://devfeed.tech/tags/amazon-s3-intelligent-tiering.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-compute-optimizer](<https://devfeed.tech/tags/aws-compute-optimizer.md>), [aws-cost-optimization](<https://devfeed.tech/tags/aws-cost-optimization.md>), [aws-graviton](<https://devfeed.tech/tags/aws-graviton.md>), [cloud-cost-optimization](<https://devfeed.tech/tags/cloud-cost-optimization.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cost-optimization](<https://devfeed.tech/tags/cost-optimization.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [eks](<https://devfeed.tech/tags/eks.md>), [examples](<https://devfeed.tech/tags/examples.md>), [finops](<https://devfeed.tech/tags/finops.md>), [finops-cloud-optimization](<https://devfeed.tech/tags/finops-cloud-optimization.md>), [net](<https://devfeed.tech/tags/net.md>), [networking](<https://devfeed.tech/tags/networking.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [plan](<https://devfeed.tech/tags/plan.md>), [practical](<https://devfeed.tech/tags/practical.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [rds](<https://devfeed.tech/tags/rds.md>), [s3](<https://devfeed.tech/tags/s3.md>), [strategies](<https://devfeed.tech/tags/strategies.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The article argues that routine AWS defaults can drive substantial waste and recommends measuring costs first, then targeting low-effort fixes. It compares commitment options: Compute Savings Plans trade discount depth for flexibility, while EC2 Instance Savings Plans and stable database Reserved Instances can discount more; Database Savings Plans add flexibility across listed data services at a lower ceiling. Other measures include Graviton migration, Spot for interruptible work, EKS node consolidation, rightsizing, S3 tiering and lifecycle rules, gp2-to-gp3 conversion, and VPC endpoints to reduce NAT processing. Each has limits: Spot can be reclaimed, Intelligent-Tiering charges to monitor objects and is less suited to tiny objects, and interface endpoints have per-AZ and data charges. The article also recommends reducing public IPv4 use, tuning RDS and connections, setting log retention, scoping AWS Config, and assigning cost ownership through tags, budgets, alerts, and review. It emphasizes checking business impact and current regional prices; quoted savings are estimates, not additive guarantees.

### Source excerpt

Discover 20 practical AWS cost optimization strategies for EC2, EKS, S3, RDS, and networking, with pricing examples and a 30-day action plan.

## Readyon Builds Four Layer Tenant Isolation for Multi Tenant Amazon EKS

DevFeed: [Readyon Builds Four Layer Tenant Isolation for Multi Tenant Amazon EKS](<https://devfeed.tech/articles/readyon-builds-four-layer-tenant-isolation-for-multi-tenant-amazon-eks-100607.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/readyon-four-layer-isolation/>)

Author: Leela Kumili

Published: 2026-10-26T14:07:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Per-user Database](<https://devfeed.tech/topics/per-user-database.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.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>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [argo-cd](<https://devfeed.tech/tags/argo-cd.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [eks](<https://devfeed.tech/tags/eks.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [isolates](<https://devfeed.tech/tags/isolates.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [layer](<https://devfeed.tech/tags/layer.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [multi-tenant-data](<https://devfeed.tech/tags/multi-tenant-data.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [news](<https://devfeed.tech/tags/news.md>), [observability](<https://devfeed.tech/tags/observability.md>), [policy](<https://devfeed.tech/tags/policy.md>), [readyon-four-layer-isolation](<https://devfeed.tech/tags/readyon-four-layer-isolation.md>), [security](<https://devfeed.tech/tags/security.md>), [tenant-isolation](<https://devfeed.tech/tags/tenant-isolation.md>), [threat-modeling](<https://devfeed.tech/tags/threat-modeling.md>), [virtual-pc](<https://devfeed.tech/tags/virtual-pc.md>)

### AI overview

ReadyOn describes four overlapping isolation layers for its Harmony platform on Amazon EKS: per-tenant Kubernetes namespaces with RBAC and default-deny policies; dedicated Karpenter node pools guarded by tenant and workload taints plus admission checks; VPC security groups that restrict database access to each tenant's node pool; and dedicated Aurora clusters instead of row-level filtering in a shared database. It also uses tenant-scoped Secrets Manager paths, short-lived IAM Roles for Service Accounts credentials, and dedicated observability backends. The excerpt says Kubernetes controls alone do not separate workloads on underlying nodes, and notes that observability should connect workload identity to database and network enforcement to reveal gaps. ReadyOn reports that adversarial exercises have not found a successful cross-tenant path to date; the excerpt does not provide independent verification.

### Source excerpt

ReadyOn has detailed a four-layer tenant isolation architecture for its Harmony platform on Amazon EKS. The design combines Kubernetes namespaces, dedicated Karpenter node pools, VPC security groups, and per-tenant Aurora databases, with controls evaluated against a 10-stage multi-tenant threat model focused on cross-tenant access and lateral movement. By Leela Kumili

## Is Kubernetes ready for AI agents?

DevFeed: [Is Kubernetes ready for AI agents?](<https://devfeed.tech/articles/is-kubernetes-ready-for-ai-agents-99192.md>)

Original publisher: [Read original article](<https://thenewstack.io/kubernetes-ready-ai-agents/>)

Author: Dan Ciruli

Published: 2026-10-25T14:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Overview, News and Trends | The New Stack](<https://devfeed.tech/sources/kubernetes-overview-news-and-trends-the-new-stack.md>), [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [OpenShell](<https://devfeed.tech/topics/openshell.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>)

Tags: [abstraction](<https://devfeed.tech/tags/abstraction.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-platforms](<https://devfeed.tech/tags/agentic-platforms.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-labs](<https://devfeed.tech/tags/ai-labs.md>), [ai-models](<https://devfeed.tech/tags/ai-models.md>), [ai-platform](<https://devfeed.tech/tags/ai-platform.md>), [ai-sandboxing](<https://devfeed.tech/tags/ai-sandboxing.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [cios](<https://devfeed.tech/tags/cios.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [developers](<https://devfeed.tech/tags/developers.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [post-contributed](<https://devfeed.tech/tags/post-contributed.md>), [software](<https://devfeed.tech/tags/software.md>), [sponsor-cncf](<https://devfeed.tech/tags/sponsor-cncf.md>), [sponsored-post-contributed](<https://devfeed.tech/tags/sponsored-post-contributed.md>)

### AI overview

Kubernetes can schedule, scale, and recover AI inference workloads, and the excerpt says two-thirds of organizations running inference use it. But agent behavior creates security and runtime demands beyond conventional services: the article calls for isolated sandboxes, explicit permissions for files, tools, network and system resources, and controls on code execution. It says CNCF work is underway, while open-source Kubernetes does not yet provide the full isolation needed, which may require virtual machines or host-level controls; some commercial distributions already offer such capabilities. Agents may run for seconds and need to start quickly, making fresh pod startup too slow for interactive use. An "agent substrate" warm pool is presented as one approach, keeping agents suspended so they can resume in milliseconds. The excerpt also identifies monitoring as an enterprise concern.

### Source excerpt

Kubernetes was built around a fairly simple assumption. It's that software does what its developers told it to do. AI The post Is Kubernetes ready for AI agents? appeared first on The New Stack.

[Next page](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md?cursor=WyIyMDI2LTEwLTI1VDE0OjAwOjAwKzAwOjAwIiwgIjExNDUwYTllLTE1ZjAtNGQ2OS04MGJhLWRmOTE3YWY3MDVhYSJd>)