Sheetal Joshi

Accelerated workloads make node provisioning challenging. Picking the wrong instance, scheduling constraint, or disruption policy impacts GPU utilization and drives up costs.

Amazon EKS continues to push the boundaries of what's possible. Join this session to understand the engineering principles and design decisions that drive Amazon EKS's evolution to support massive scale while maintaining simplicity and reliability.

Kubernetes makes building and running complex applications simpler, but using Kubernetes comes with a unique set of challenges, such as security, networking, interoperability, storage, and scaling.

In this builders’ session, explore the newly launched Amazon EKS Auto Mode and discover how it provides you integrated and ready-to-use Kubernetes capabilities for compute, networking, and storage.

With the flexibility of Kubernetes and its ecosystem, there are many ways to deploy to Kubernetes. Tooling is important, but deployment processes also need to be designed to support application teams.

As organizations expand their operations on Amazon EKS, they encounter the intricate task of managing diverse Kubernetes networking choices supported by Amazon VPC CNI. Establishing seamless networking within an Amazon EKS setup can be a complex endeavor.

GitOps simplifies both application deployments and operations tasks with Kubernetes. In this workshop, learn how to build a scalable, complete GitOps system that addresses the needs of both application teams and platform teams.

Kubernetes has become a standard way for organizations to innovate and modernize their application portfolio. AWS developed Amazon EKS to make Kubernetes more accessible to organizations of all sizes, allowing them to free up resources and focus on what matters most: their businesses.

In this workshop, learn how you can reliably deploy and manage your Kubernetes clusters and applications by adopting GitOps workflows. The workshop starts with a quick overview of what GitOps is and then moves to hands-on experience by building a reference environment using Amazon EKS.

Once you have containerized your application and broken your monolith down into a set of microservices, it becomes very critical on how these microservices interact with one another to satisfy your business logic. Do you embed the conditional logic or callback logic within the microservices, or do you abstract it?