Skip to content

Project

Amazon EKS

AWS's managed Kubernetes service, used as a control plane for containerised workloads on AWS infrastructure.

Known aliases

  • Amazon EKS
  • Amazon EKS 1.34
  • Amazon Elastic Kubernetes Service
  • EKS
  • EKS Standard
  • Elastic Kubernetes Service
  • managed EKS
  • prod-eks

Current stories

buildOne report1 publisher

One personal GitHub OAuth token carried 276 Terraform Enterprise workspaces until it was revoked

One revoked personal OAuth token stopped runs across 276 Terraform Enterprise workspaces, according to a dev.to write-up. Nobody was paged and the team needed two days to notice, so it moved the workspaces onto a GitHub App owned by the org.

Publishers:dev.to

Reality

Evidence55
Adoption
Not scored
Hype gap−10
Incentives
Not scored
Confidence50
buildOne report1 publisher

EKS, GKE and AKS each retire Kubernetes 1.34 on a different date with a different penalty

Kubernetes 1.34 loses upstream patches on October 27, but AKS stops patching it on November 30 and EKS starts billing it at six times the rate on December 2. Teams need an upgrade plan for each provider, because the managed dates decide what a 1.34 cluster costs and whether it still gets fixes.

Publishers:dev.to

Reality

Evidence55
Adoption
Not scored
Hype gap+10
Incentives
Not scored
Confidence60
buildOne report1 publisher

Three managed IAM policies decide who launches HyperPod Spaces from SageMaker Studio

AWS now lets SageMaker Studio users launch JupyterLab and Code Editor Spaces on HyperPod EKS clusters from the browser, with no kubectl step. On a shared GPU cluster, who may launch them comes down to three managed IAM policies and a per-user identity setting that older Studio domains must switch on.

Publishers:aws.amazon.com

Reality

Evidence55
Adoption
Not scored
Hype gap+10
Incentives70
Confidence60
buildOne report1 publisher

EKS lets teams switch its managed scheduler to MostAllocated bin-packing

Amazon EKS now lets customers set selected scheduler, controller-manager and API-server parameters, including MostAllocated bin-packing, through its API. Teams that self-host only for such tuning now need a parameter AWS has not exposed.

Publishers:dev.to

Reality

Evidence35
Adoption
Not scored
Hype gap+5
Incentives20
Confidence40
buildOne report1 publisher

Static pods led a hand-built Kubernetes controller to report the whole control plane at risk

One Karpenter operator wrote about 250 lines of plain client-go to flag pods that will not come back when a tainted node goes away. Doing it without controller-runtime or Kubebuilder put every piece of the watch, queue and reconcile loop on the page.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap0
Incentives
Not scored
Confidence55
buildOne report1 publisher

EKS Pod Identity swaps per-cluster OIDC trust for one service principal shared by every role

EKS Pod Identity, launched at re:Invent 2023, replaces IRSA's per-cluster OIDC trust with one pods.eks.amazonaws.com principal on every IAM role. A dev.to migration guide has each role trust both paths during cutover, so teams can move and verify one workload at a time.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+15
Incentives
Not scored
Confidence50
buildOne report1 publisher

AWS combines EKS, EFA and DeepEP to boost MoE reinforcement learning throughput by 40%

AWS says running DeepEP over its EFA network on EKS gives mixture-of-experts reinforcement learning 40% more throughput. Whether that reaches another cluster depends on how much of each training step goes to expert traffic between nodes.

Publishers:aws.amazon.com

Reality

Evidence30
Adoption
Not scored
Hype gap+30
Incentives80
Confidence35
buildOne report1 publisher

Two of WebRTC's three ICE candidate types depend on servers you operate

The spec's three JavaScript APIs handle codecs, encoding and transport once two peers have found each other. Finding them takes a signaling service, STUN and TURN, and all three are yours to run and budget for.

Publishers:dev.to

Reality

Evidence62
Adoption25
Hype gap+12
Incentives20
Confidence58
buildOne report1 publisher

A missing gp3 StorageClass made Storm's init containers blame Nimbus for two days

Apache Storm ships no maintained Helm chart and no migration guide, so one team wrote its own templates for EKS. The first thing that broke was a StorageClass name, and the only symptom was an init container log line.

Publishers:dev.to

Reality

Evidence58
Adoption18
Hype gap0
Incentives32
Confidence52
buildOne report1 publisher

Chromium's user-namespace sandbox survives the hardening that kills its setuid helper

PDFik dropped --no-sandbox from its Playwright workers and kept rendering customer-submitted HTML in non-root, capability-stripped pods. Its own security auditor later wrote that the flag was mandatory.

Publishers:dev.to

Reality

Evidence58
Adoption25
Hype gap−5
Incentives60
Confidence52
buildOne report1 publisher

HyperPod's inference gateway scores KV cache and LoRA residency before it picks a pod

Amazon's new EKS managed addon reads Prometheus metrics from every model pod and sends each request to the one with room in its KV cache. The advertised 82% cut in first-token latency rests on a single 4.4-second baseline.

Publishers:aws.amazon.com

Reality

Evidence46
Adoption14
Hype gap+38
Incentives88
Confidence52
buildOne report1 publisher

The default MCP deployment buys a Kubernetes operational surface for request/response traffic

A dev.to writeup makes the case for trying Bedrock Agents or AgentCore Runtime before containers, and for putting real limits on the gateway, because a looping agent spends money without ever raising an error.

Publishers:dev.to

Reality

Evidence28
Adoption
Not scored
Hype gap+18
Incentives32
Confidence36
buildOne report1 publisher

Elastic Beanstalk's Cluster Mode shares one EKS cluster across every app in a subnet set

AWS now says it takes full operational responsibility for Elastic Beanstalk production environments for the life of the application. Underneath, Cluster Mode puts multiple apps on one shared Amazon EKS cluster.

Publishers:aws.amazon.com

Reality

Evidence35
Adoption20
Hype gap+35
Incentives90
Confidence60
buildOne report1 publisher

Blocking checkpoint writes took up to 40 percent of wall time on AWS's H100 test runs

AWS's NVRx walkthrough puts synchronous checkpointing ahead of GPU faults as the source of idle time on its FSDP jobs, and pairs a background save with a restart that re-enters training without cycling the container.

Publishers:aws.amazon.com

Reality

Evidence54
Adoption20
Hype gap+18
Incentives76
Confidence56
buildOne report1 publisher

Karpenter moves the instance decision from config-authoring time to the moment pods go pending

A dev.to walkthrough of the provisioning loop shows Karpenter batching pending pods for up to ten seconds, packing them in memory against their own scheduling constraints, then letting EC2 Fleet price the candidates.

Publishers:dev.to

Reality

Evidence42
Adoption
Not scored
Hype gap+15
Incentives30
Confidence50
buildOne report1 publisher

Cilium 1.19 replaces the per-pod Envoy with one eBPF program per node

Cilium 1.19 puts routing, mTLS and observability in one eBPF program per node, with a single Envoy per node for Layer 7. The 100 GB of RAM the post says that frees assumes 1,000 pods at the top of the sidecar range.

Publishers:dev.to

Reality

Evidence24
Adoption38
Hype gap+45
Incentives
Not scored
Confidence34
buildOne report1 publisher

A governance tag push turned five EKS workers into Prometheus scrape targets

The environment and techteam tags that drive cost allocation also drive Prometheus EC2 service discovery, so an add-only tagging run in ap-south-1 enrolled Kubernetes nodes in a scrape job for a host agent they do not run.

Publishers:dev.to

Reality

Evidence58
Adoption30
Hype gap−10
Incentives25
Confidence55
buildOne report1 publisher

Datadog billed 5.6 times what the two servers replacing the AWS cluster cost

An audit of a post-Series A fintech serving 35 requests a second puts one observability line at $3,800 a month, more than five times the two bare-metal machines that replaced the whole AWS cluster.

Publishers:dev.to

Reality

Evidence22
Adoption12
Hype gap+55
Incentives68
Confidence26
buildOne report1 publisher

Locking the EKS API to one IP left the worker node with no route to the control plane

A k3s workload moved to Amazon EKS without an application code change, and the three things that had to be fixed were the control plane endpoint policy, the instance type AWS would allow, and the credential doing the work.

Publishers:dev.to

Reality

Evidence60
Adoption10
Hype gap−12
Incentives20
Confidence57

Earlier coverage