aws-lambda-go-deployment

Diagnose and fix Go-based AWS Lambda deployment, packaging, runtime, and handler issues.

1|1|Updated May 3, 2026
One-click install
npx skills add https://github.com/matt-riley/agent-skills --skill aws-lambda-go-deployment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aws-lambda-go-deployment
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/aws-lambda-go-deployment
Command: npx skills add https://github.com/matt-riley/agent-skills --skill aws-lambda-go-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Deployments and debugging go-based AWS Lambda functions, focusing on packaging, bootstrap, runtime, and handler issues beyond SAM wiring or IAM/OIDC problems.

Core Features & Use Cases

  • Classifies failures into build-time, packaging, runtime-startup, or event-wiring categories.
  • Guides Linux cross-compilation, correct artifact layout, and runtime choices (provided.al2 or provided.al2023) to ensure Lambda boots.
  • Directs users to related skills for non-Go blocks, such as SAM template issues or IAM/OIDC troubleshooting.

Quick Start

Classify the failure, then follow the cross-compile and Linux build guidance to fix the Lambda artifact.

Frequently Asked Questions about aws-lambda-go-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Go Lambda function fail to start on AWS?▼

Go Lambda startup failures usually stem from incorrect runtime selection, missing Linux cross-compilation, or improper bootstrap artifact layout. Diagnosing these build-time and packaging issues ensures the provided.al2 or provided.al2023 runtime boots correctly.

How do I package a Go binary for AWS Lambda deployment?▼

Packaging a Go Lambda deployment requires a Linux-compatible binary and correct artifact layout so the bootstrap executes properly. Cross-compiling with the right environment variables ensures your Go function deploys without runtime startup errors.

What is the correct way to cross-compile Go for AWS Lambda Linux targets?▼

Cross-compiling Go for AWS Lambda requires setting GOOS=linux and GOARCH=amd64 or arm64 to produce a compatible binary. This ensures the artifact runs within the provided.al2 or provided.al2023 runtime environments without startup failures.

Does this fix SAM template wiring or IAM permission issues for Go Lambda?▼

It does not fix SAM template wiring or IAM permission issues. It focuses strictly on Go-based packaging, handler, and runtime startup problems, and routes you to related skills for non-Go infrastructure blockers.

How do I resolve handler and event-wiring errors in my Go Lambda function?▼

Resolving Go Lambda handler errors involves classifying the failure as event-wiring or runtime-startup and verifying the artifact layout. Correcting the Linux build and runtime configuration ensures the handler processes events correctly.

When should I use provided.al2 versus provided.al2023 for Go Lambda?▼

Choosing between provided.al2 and provided.al2023 depends on your required base Linux environment for the Go runtime. Both require a properly cross-compiled Linux binary and correct artifact layout to ensure successful Lambda startup.