Using EKS with Lambda on AWS

Hi, I'm Timur 👋

Forward Deployed Engineer · AI × Cloud. I build with LLMs, agents, and MCP servers on top of cloud infrastructure — sitting close to the problem, prototyping fast, hardening for production.

15+ years architecting cloud platforms across AWS, GCP, and Azure. Now putting most hands-on hours into AI tooling on top of cloud, with open source as the public surface area.

Background arc: DevOps Architect → Full Stack Developer → Cloud Architect → Head of IT / CTO → AI × Cloud / Forwa

Deploying Lambda functions to EKS

The main way to integrate EKS and Lambda is by deploying Lambda functions as Kubernetes deployments and services. This allows Kubernetes to manage and orchestrate the execution of Lambda code.

The steps to deploy a Lambda function to EKS are:

Create a Lambda function using the AWS CLI or SDK. This deploys the code and configuration to Lambda.

Create a Kubernetes Deployment and Service that points to the Lambda function ARN (Amazon Resource Name). The service exposes the function through a ClusterIP.

Kubernetes will trigger invocations of the Lambda function through the service endpoint. It handles load balancing, auto-scaling and orchestration of the function.

Benefits of using EKS and Lambda together

Leverage Kubernetes APIs and tools to deploy, manage and scale Lambda functions

Build serverless applications as Kubernetes workloads for portability across environments

Take advantage of Kubernetes features like auto-scaling, rolling updates, blue-green deployments etc. for Lambda code

Integrate Lambda functions into existing container-based applications on EKS

This allows building fully serverless applications that leverage the power of Kubernetes for orchestration along with AWS Lambda's ease of use.

Here is a sample Python code for deploying a Lambda function as a Kubernetes workload:

# Create Lambda function lambda_client.create_function( FunctionName='myfunction', Runtime='python3.8', Handler='index.handler', Code={ 'ZipFile': bytecode } ) # Create Kubernetes Deployment api.create_namespaced_deployment( namespace='default', body={ 'apiVersion': 'apps/v1', 'kind': 'Deployment', 'metadata': { 'name': 'lambda-deploy' }, 'spec': { 'replicas': 1, 'selector': { 'matchLabels': { 'app': 'lambda' } }, 'template': { 'metadata': { 'labels': { 'app': 'lambda' } }, 'spec': { 'containers': [ { 'name': 'lambda-container', 'image': 'public.ecr.aws/lambda/python:3.8', 'env': [ { 'name': 'AWS_LAMBDA_FUNCTION_NAME', 'value': 'myfunction' }, { 'name': 'AWS_REGION', 'value': 'us-east-1' } ] } ] } } } } ) # Expose Deployment as Kubernetes Service api.create_namespaced_service( namespace='default', body={ 'apiVersion': 'v1', 'kind': 'Service', 'metadata': { 'name': 'lambda-service' }, 'spec': { 'ports': [ { 'port': 8080, 'targetPort': 8080 } ], 'selector': { 'app': 'lambda' } } } )

This demonstrates how to deploy a Lambda function as a Kubernetes workload and expose it through a service for invocation. EKS and Lambda provide a powerful way to build serverless applications on Kubernetes.

Using EKS with Lambda on AWS

Comments

More from this blog

memex: training for the Forward Deployed Engineer era with a private memory brain on AWS

Building vibestack: how I stopped re-explaining myself to my AI

Working with AWS European Sovereign Cloud (ESC): Terraform, IaC, and what's different

ECS vs EKS: When You DON'T Need Kubernetes - A Practical Guide to Choosing AWS Container Services

AWS ECS Evolution: Managed Instances and Advanced Deployment Strategies

Deploying Lambda functions to EKS

Benefits of using EKS and Lambda together

Command Palette

Comments

More from this blog

Deploying Lambda functions to EKS

Benefits of using EKS and Lambda together