AWS Lambda now supports GitHub Actions: Streamlining Serverless CI/CD

AWS Lambda now supports GitHub Actions

In August 2025, AWS made native support available to deploy AWS Lambda functions straight from GitHub Actions. With this integration, a lot of the complexity developers have had to undergo conventionally with serverless automatic deployment is eliminated.

As a valuable practical improvement, teams will now gain the ability to utilize declarative GitHub workflows with OIDC-secured authentication and auto-packaging of code for simpler CI/CD pipelines.

The news has prompted a good dose of enthusiasm, useful guidance, and healthy skepticism. Let’s unpack what it does for serverless devs, how it works, and how the community has responded.

What Changed?

Up until now, getting a function deployed from GitHub Actions to AWS Lambda took:

Writing custom scripts or AWS CLI commands
Handling everything manually, including packaging
IAM roles and error handling, reusing the same boilerplate in multiple repositories

This all leads to slow and error-prone onboarding.

Now with the new aws-lambda-deploy GitHub Action, developers can:

Deploy with a simple YAML workflow,
Package your code automatically (whether .zip or container images)
Use IAM OIDC auth (no long-lived AWS secrets),
Configure Lambda settings like runtime, memory, and environment variables,
Run deployments in dry-run mode before making changes

How does it Work?

A sample GitHub Actions workflow would look like:

name: Deploy Lambda Function
on:
  push:
    branches:
      - main
jobs:
  deploy:
    runs-on: ubuntu-latest
    permissions:
      id-token: write
      contents: read
    steps:
      - uses: actions/checkout@v4
      - name: Configure AWS credentials
        uses: aws-actions/configure-aws-credentials@v4
        with:
          role-to-assume: arn:aws:iam::123456789012:role/GitHubActionRole
          aws-region: us-east-1
      - name: Deploy Lambda Function
        uses: aws-actions/aws-lambda-deploy@v1
        with:
          function-name: my-lambda-function
          code-artifacts-dir: ./dist

This pipeline deploys a Lambda function automatically whenever code is pushed to the main branch.

AWS Position: A Major Simplification

In its official announcement (Aug 7, 2025), AWS presented the feature as a way to reduce preceding work and help developers be more productive. With the process of packaging automated and boilerplate removed, the company characterized GitHub Actions as the ‘natural entry point‘ for serverless CI/CD.

The emphasis was on:

Faster onboarding for new developers
Secure, secret-free IAM authentication with OIDC
Availability in all AWS commercial regions

Pros and Cons

Pros	Cons
Declarative YAML workflows simplify deployments	Still requires IAM role configuration
OIDC removes need for long-lived AWS secrets	Doesn’t build your code (must be pre-packaged)
Automatic packaging for .zip and container images	Trigger/event source setup still manual
Configurable runtime, memory, env variables	Functionality overlaps with existing CLI
Reduces onboarding time for teams	Incremental improvement, not revolutionary

Conclusion

AWS Lambda’s GitHub Actions integration is an important step for serverless CI/CD; it reduces manual work for developers, provides a better level of security, and provides pipelines for developers to consume.

That said, it is right for the community to recognize that it is an incremental improvement. It does give developers a process to make deployments easier, but it still requires users to manage IAM roles, triggers, and pre-build steps.

For developers using GitHub Actions, this new pattern will make them more productive. Hopefully, it gives them an enhanced ability to provide a developer-first CI/CD tool.

But again, as critics have pointed out, the company is left with the greater challenge – delivering the simple experience of ‘true container-first‘ serverless platforms, like Google Cloud Run.

Cloud Code Signing

Seamless Automated Code Signing Tasks without Need of Physical HSM or Token using Cloud Code Signing Certificate.

Code Signing as a Service

AWS Lambda GitHub Actions Integration: Streamlining Serverless CI/CD