AWS HPC Blog
Category: Amazon Elastic Kubernetes Service
Introducing Riskthinking.AI Climate Earth Digital Twin on AWS
As climate change escalates, power infrastructure faces growing risks. Explore how the ClimateEarthDigitalTwin (CDT™) platform from riskthinking.AI leverages AWS HPC to assess these risks and enable resilience planning for the energy sector. Learn how this cutting-edge solution can safeguard your critical assets.
Adding configurable namespaces, persistent volume claims, and other features for AWS Batch on Amazon EKS
Exciting updates to AWS Batch on Amazon EKS! Configurable namespaces, persistent volume claims, and more. Check out our blog post to see how these features can help manage your complex containerized workloads.
How BAM supercharged large scale research with AWS Batch
Balyasny Asset Management (BAM), a $22B global investment firm, faced a unique challenge: how to empower 160 investment teams to conduct cutting-edge research across six strategies. Discover how they leveraged AWS Batch and Amazon EKS to supercharge their research capabilities.
Deploying Generative AI Applications with NVIDIA NIM Microservices on Amazon Elastic Kubernetes Service (Amazon EKS) – Part 2
Learn how to deploy AI models at scale with @AWS using NVIDIA’s NIM and Amazon EKS! This step-by-step guide shows you how to create a GPU cluster for inference in this second post of a two-part series!
Gang scheduling pods on Amazon EKS using AWS Batch multi-node processing jobs
AWS Batch multi-node parallel jobs can now run on Amazon EKS to provide gang scheduling of pods across nodes for large scale distributed computing like ML model training. More details here.
Explore costs of AWS Batch jobs run on Amazon EKS using pod labels and Kubecost
Today we show you how to get insights into the costs of running AWS Batch workloads on Amazon EKS using Kubernetes pod labels with Kubecost.
How AWS Batch developed support for Amazon Elastic Kubernetes Service
Today, we discuss AWS batch on Amazon EKS, and the initial motivation and design choices the team made when we developed the service, and some of the challenges to overcome.