All news with #aws eks tag

🚀 AWS announces general availability of a new AWS Local Zone in Istanbul, Türkiye, bringing compute, storage, networking, and select services closer to end users. The Local Zone supports Amazon EC2 (C7i, M7i, R7i), Amazon S3 One Zone-Infrequent Access, Amazon EBS (local snapshots and gp3/gp2/io1/sc1/st1), Amazon ECS, Amazon EKS, VPC, AWS Direct Connect, and Application Load Balancer. To enable, turn on the zone (eu-central-1-ist-1a) in the EC2 console or use the ModifyAvailabilityZoneGroup API to reduce latency and meet data residency needs.

🔁 Amazon EKS now supports Amazon Application Recovery Controller (ARC) zonal shift and zonal autoshift when using the open-source Karpenter for compute provisioning. ARC automates redirecting in-cluster network traffic away from an impaired AZ and can perform practice runs to validate cluster behavior. During a zonal shift, Karpenter stops provisioning in the impacted AZ, halts voluntary disruptions there, and avoids scheduling actions that depend on that zone. Enable support by setting ENABLE_ZONAL_SHIFT.

📦 AWS Transform now automates replatforming to containers during migrations, extending its agentic AI to generate Dockerfiles, build images, and publish to Amazon ECR. It supports repositories from GitHub, Bitbucket, GitLab, or .zip sources and builds deployment artifacts for Amazon ECS and Amazon EKS. Integrated security scanning and Terraform and Helm outputs simplify operations. Available in all Regions where AWS Transform is offered.

🚀 AWS Backup now completes Amazon EKS cluster state backups up to 10x faster. This improvement reduces backup windows for clusters with large numbers of namespaces and Kubernetes resources from days to hours and is automatically enabled at no additional cost in supported Regions. AWS Backup is a policy-based, fully managed solution to centralize and automate protection across compute, storage, and databases.

☁️ Amazon Elastic Kubernetes Service (EKS) now offers one-click cluster access from the AWS Management Console via AWS CloudShell, eliminating the need to install or configure kubectl, AWS CLI, or kubeconfig files locally. From the EKS console, selecting Connect launches a CloudShell session with kubectl pre-configured for the chosen cluster so you can run commands immediately. The feature supports clusters with both public and private API server endpoints and each session also includes the AWS CLI and standard CloudShell utilities for troubleshooting and management.

🔗 Amazon Elastic Kubernetes Service (EKS) introduces the Amazon EKS Hybrid Nodes gateway to automate networking between an EKS cluster VPC and Kubernetes Pods running on EKS Hybrid Nodes. The gateway removes the need to make on‑premises pod networks routable and avoids extensive coordination with network teams by automatically maintaining VPC route tables as workloads scale. Deployed to Amazon EC2 instances via Helm, the gateway also enables control-plane-to-webhook, pod-to-pod, and AWS service connectivity (ALB, NLB, Amazon Managed Service for Prometheus). The codebase is open source and the feature is available in all Regions where EKS Hybrid Nodes is supported, excluding China Regions. AWS offers the gateway itself at no additional charge; customers pay for underlying EC2 and data transfer costs.

🔐 Amazon EKS now supports seven new IAM condition keys for cluster creation and configuration APIs, giving organizations finer-grained governance over cluster settings. Administrators can enforce private-only API endpoints, require customer-managed KMS keys for secret encryption, restrict approved Kubernetes versions, mandate deletion protection, set control plane scaling tiers, and enable zonal shift. The keys apply to CreateCluster, UpdateClusterConfig, UpdateClusterVersion, and AssociateEncryptionConfig APIs and integrate with Service Control Policies for centralized multi-account enforcement. They are available in all Regions where EKS is offered at no additional charge.

🚀 Amazon EKS managed node groups now support Auto Scaling warm pools, keeping pre-initialized EC2 instances ready for rapid scale-out. With warm pools enabled, instances complete OS initialization, user data execution, and software configuration before joining the cluster; you can choose Stopped (lower cost, longer transition) or Running (higher cost, faster transition). You can also enable reuse on scale-in to return instances to the pool instead of terminating them, and the feature works with Cluster Autoscaler without additional configuration. Enable via the EKS API, AWS CLI, Console, or CloudFormation by adding a warmPoolConfig to node group requests.

💽 Amazon ECS Managed Instances now supports using Amazon EC2 instance store volumes as a data volume option for container workloads. You can enable local storage by configuring a custom ECS Managed Instances capacity provider and selecting EC2 instance types that include instance store volumes; when an instance lacks instance store or local storage is disabled, Amazon ECS will automatically provision an Amazon EBS data volume. This reduces storage costs and can accelerate I/O for latency-sensitive workloads. Support is available in all commercial AWS Regions where ECS Managed Instances is offered.

🔒 Amazon EKS now offers a 99.99% Service Level Agreement for clusters running on the Provisioned Control Plane, up from the 99.95% SLA on the standard control plane. The upgraded SLA is measured in 1-minute intervals to deliver a more granular availability commitment for mission-critical workloads. At the same time, EKS introduces an 8XL scaling tier that doubles Kubernetes API server request processing capacity compared with the 4XL tier. Both the new SLA and the 8XL tier are available today in all regions where the Provisioned Control Plane is offered.

🔧 AWS announced the Neuron Dynamic Resource Allocation (DRA) driver for Amazon EKS, enabling Kubernetes-native, hardware-aware scheduling on Trainium-based instances. The driver publishes detailed device attributes — including hardware topology and Neuron-EFA PCIe co-location — directly to the Kubernetes scheduler, removing the need for custom scheduler extensions. Infrastructure teams can publish reusable ResourceClaimTemplates, while ML engineers reference them to deploy workloads without manual hardware tuning.

🔒 AWS Backup now supports protecting Amazon EKS clusters with logically air-gapped vaults. These vaults store immutable backup copies that are locked by default and encrypted with AWS-owned keys or customer-managed keys, and they can hold backups in the same account or across accounts and Regions. You can target a vault as the primary backup or copy destination via the console, API, or CLI, share recovery access through AWS Resource Access Manager (RAM) or multi-party approval, and initiate direct restore jobs from the recipient account without copying first to reduce recovery time.

🔔 Amazon CloudWatch Observability EKS add-on v5.0.0 now enables CloudWatch Application Signals (APM) by default for new installations and upgrades, removing the previous manual opt-in. The add-on automatically instruments services to collect traces, metrics, and logs, delivering an application-centric view without additional Kubernetes annotations. Users get immediate access to pre-built dashboards and enriched troubleshooting to detect latency, errors, and request traces out of the box.

🔓 Amazon EKS Node Monitoring Agent is now open source on GitHub, giving operators visibility into the agent's implementation and the ability to contribute or customize its behavior. The agent automatically monitors node-level system, storage, networking, and accelerator issues and publishes them as node conditions used by Amazon EKS for automatic node repair. It is included in Amazon EKS Auto Mode and available as an add-on in all AWS Regions. Cluster administrators can inspect, adapt, and participate in the agent's ongoing development to better fit their operational needs.

📥 Amazon Elastic Kubernetes Service (EKS) Auto Mode can now deliver logs via Amazon CloudWatch Vended Logs. Customers can configure each managed capability—compute autoscaling, block storage, load balancing, and pod networking—as a vended log source using the CloudWatch APIs or the AWS Console. Logs can be routed to CloudWatch Logs, Amazon S3, or Amazon Kinesis Data Firehose. This option uses built‑in AWS authentication and authorization and can reduce delivery cost versus standard CloudWatch Logs.

🚀 AWS Batch now supports unmanaged compute environments on Amazon EKS, extending Batch's job scheduling and orchestration to clusters you manage directly. You can create compute environments via the CreateComputeEnvironment API or the AWS Batch console by selecting an existing EKS cluster and specifying a Kubernetes namespace, then associate nodes using kubectl labels. This option preserves customer control over Kubernetes infrastructure for security, compliance, or operational requirements and is available today in all regions where AWS Batch operates.

🔐 Amazon EKS now directly integrates EKS add-ons with EKS Pod Identity in AWS GovCloud (US-East and US-West), simplifying lifecycle and IAM permission management for add-ons that need access to AWS services. You can manage Pod Identities via the EKS console, CLI, API, eksctl, and IaC tools like AWS CloudFormation. This GA expansion increases the set of Pod Identity–compatible add-ons available during cluster creation.

🚀 Amazon GameLift Servers now supports automatic scaling to and from zero instances, enabling game developers to eliminate charges for idle compute during inactive periods. This removes the need to keep instances running solely to preserve Fleet autoscaling, reducing infrastructure costs for titles with variable or unpredictable traffic. The capability is available in all supported regions and scales up automatically when game sessions are requested, simplifying operations and improving cost-efficiency.

🚀 Amazon EKS and EKS Distro now support Kubernetes 1.35, enabling creation of new clusters and upgrades of existing clusters via the EKS console, eksctl, or infrastructure-as-code tools. Kubernetes 1.35 introduces In-Place Pod Resource Updates to adjust CPU and memory without restarting pods, PreferSameNode traffic distribution to favor local endpoints, Node Topology Labels via the Downward API for region/zone awareness, and Image Volumes for delivering data artifacts such as AI models. EKS 1.35 is available in all AWS Regions where EKS is offered, including AWS GovCloud (US), and EKS Distro builds are published to the ECR Public Gallery and GitHub. Refer to the EKS documentation for available versions, upgrade guidance, lifecycle policies, and use EKS Cluster Insights to surface issues that could affect upgrades.

🕒 Amazon ECS now lets you define weekly event windows to control when AWS Fargate retires tasks for platform updates. Enable the account setting fargateEventWindows, create EC2 event windows with time ranges, and associate them to ECS tasks using managed tags like aws:ecs:clusterArn, aws:ecs:serviceArn, or aws:ecs:fargateTask. This allows precise timing (for example, weekend-only retirements) to avoid disruption during peak business hours and is available in all commercial AWS Regions.