Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
giuseppe-trisciuoglio avatar

Aws Lambda Java Integration

  • 1.4k installs
  • 311 repo stars
  • Updated June 22, 2026
  • giuseppe-trisciuoglio/developer-kit

aws-lambda-java-integration is an agent skill for provides aws lambda integration patterns for java with cold start optimization. use when deploying java functions to aws lambda, choosing between micronaut and raw java.

About

The aws-lambda-java-integration skill is designed for provides AWS Lambda integration patterns for Java with cold start optimization. Use when deploying Java functions to AWS Lambda, choosing between Micronaut and Raw Java. AWS Lambda Java Integration Patterns for creating high-performance AWS Lambda functions in Java with optimized cold starts. Overview This skill provides complete patterns for AWS Lambda Java development, covering two main approaches: 1. Invoke when the user deploying Java functions to AWS Lambda, choosing between Micronaut and Raw Java approaches, optimizing cold starts below 1 second, configuring API Gateway or ALB integration, or implementing serverless Java applications.

  • Deploying Java functions to AWS Lambda.
  • Optimizing cold starts below 1 second.
  • Choosing between Micronaut and Raw Java approaches.
  • Configuring API Gateway or ALB integration.
  • Setting up CI/CD pipelines for Java Lambda.

Aws Lambda Java Integration by the numbers

  • 1,446 all-time installs (skills.sh)
  • +55 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #326 of 4,386 Backend & APIs skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

aws-lambda-java-integration capabilities & compatibility

Capabilities
deploying java functions to aws lambda · optimizing cold starts below 1 second · choosing between micronaut and raw java approach · configuring api gateway or alb integration
From the docs

What aws-lambda-java-integration says it does

Provides AWS Lambda integration patterns for Java with cold start optimization. Use when deploying Java functions to AWS Lambda, choosing between Micronaut and Raw Java approaches,
SKILL.md
Provides AWS Lambda integration patterns for Java with cold start optimization. Use when deploying Java functions to AWS Lambda, choosing between Micronaut and
SKILL.md
npx skills add https://github.com/giuseppe-trisciuoglio/developer-kit --skill aws-lambda-java-integration

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.4k
repo stars311
Security audit3 / 3 scanners passed
Last updatedJune 22, 2026
Repositorygiuseppe-trisciuoglio/developer-kit

How do I provides aws lambda integration patterns for java with cold start optimization. use when deploying java functions to aws lambda, choosing between micronaut and raw java?

Provides AWS Lambda integration patterns for Java with cold start optimization. Use when deploying Java functions to AWS Lambda, choosing between Micronaut and Raw Java.

Who is it for?

Developers using aws lambda java integration workflows documented in SKILL.md.

Skip if: Skip when the task falls outside aws-lambda-java-integration scope or needs a different stack.

When should I use this skill?

User deploying Java functions to AWS Lambda, choosing between Micronaut and Raw Java approaches, optimizing cold starts below 1 second, configuring API Gateway or ALB integration, or implementing serverless Java applicat

What you get

Completed aws-lambda-java-integration workflow with documented commands, files, and expected deliverables.

  • Gradle build.gradle
  • Lambda handler classes
  • Shadow JAR deployment artifact

By the numbers

  • Micronaut application plugin version 4.7.6
  • Gradle shadow plugin version 8.1.1
  • 5 documented sections in Micronaut Lambda reference

Files

SKILL.mdMarkdownGitHub ↗

AWS Lambda Java Integration

Patterns for creating high-performance AWS Lambda functions in Java with optimized cold starts.

Overview

This skill provides complete patterns for AWS Lambda Java development, covering two main approaches:

1. Micronaut Framework - Full-featured framework with AOT compilation, dependency injection, and cold start < 1s 2. Raw Java - Minimal overhead approach with cold start < 500ms

Both approaches support API Gateway and ALB integration with production-ready configurations.

When to Use

  • Deploying Java functions to AWS Lambda
  • Optimizing cold starts below 1 second
  • Choosing between Micronaut and Raw Java approaches
  • Configuring API Gateway or ALB integration
  • Setting up CI/CD pipelines for Java Lambda

Instructions

1. Choose Your Approach

ApproachCold StartBest ForComplexity
Micronaut< 1sComplex apps, DI needed, enterpriseMedium
Raw Java< 500msSimple handlers, minimal overheadLow

Validate: Confirm the approach fits your use case before proceeding.

2. Project Structure

my-lambda-function/
├── build.gradle (or pom.xml)
├── src/main/java/com/example/Handler.java
└── serverless.yml (or template.yaml)

Validate: Verify project structure matches the template.

3. Implementation Examples

Micronaut Handler
@FunctionBean("my-function")
public class MyFunction implements Function<APIGatewayProxyRequestEvent, APIGatewayProxyResponseEvent> {

    private final MyService service;

    public MyFunction(MyService service) {
        this.service = service;
    }

    @Override
    public APIGatewayProxyResponseEvent apply(APIGatewayProxyRequestEvent request) {
        // Process request
        return new APIGatewayProxyResponseEvent()
            .withStatusCode(200)
            .withBody("{\"message\": \"Success\"}");
    }
}
Raw Java Handler
public class MyHandler implements RequestHandler<APIGatewayProxyRequestEvent, APIGatewayProxyResponseEvent> {

    private static final MyService service = new MyService();

    @Override
    public APIGatewayProxyResponseEvent handleRequest(APIGatewayProxyRequestEvent request, Context context) {
        return new APIGatewayProxyResponseEvent()
            .withStatusCode(200)
            .withBody("{\"message\": \"Success\"}");
    }
}

Validate: Run sam local invoke to verify handler works before deployment.

Core Patterns

Connection Management

// Initialize once, reuse across invocations
private static final DynamoDbClient dynamoDb = DynamoDbClient.builder()
    .region(Region.US_EAST_1)
    .build();

// Avoid: Creating clients in handler (slow on every invocation)

Error Handling

@Override
public APIGatewayProxyResponseEvent handleRequest(APIGatewayProxyRequestEvent request, Context context) {
    try {
        return successResponse(process(request));
    } catch (ValidationException e) {
        return errorResponse(400, e.getMessage());
    } catch (Exception e) {
        context.getLogger().log("Error: " + e.getMessage());
        return errorResponse(500, "Internal error");
    }
}

Best Practices

Configuration

  • Memory: Start with 512MB, adjust based on profiling
  • Timeout: Micronaut 10-30s, Raw Java 5-10s
  • Runtime: Java 17 or 21 for best performance

Packaging

  • Use Gradle Shadow Plugin or Maven Shade Plugin
  • Exclude unnecessary dependencies

Monitoring

  • Enable X-Ray tracing for performance analysis
  • Use CloudWatch Insights to track cold vs warm starts

Deployment Options

Serverless Framework

service: my-java-lambda
provider:
  name: aws
  runtime: java21
  memorySize: 512
  timeout: 10
package:
  artifact: build/libs/function.jar
functions:
  api:
    handler: com.example.Handler
    events:
      - http:
          path: /{proxy+}
          method: ANY

Validate: Run serverless deploy with --stage dev first.

AWS SAM

AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Resources:
  MyFunction:
    Type: AWS::Serverless::Function
    Properties:
      CodeUri: build/libs/function.jar
      Handler: com.example.Handler
      Runtime: java21
      MemorySize: 512
      Timeout: 10
      Events:
        ApiEvent:
          Type: Api
          Properties:
            Path: /{proxy+}
            Method: ANY

Validate: Run sam validate before deploying.

Constraints and Warnings

Java-Specific Constraints

  • Reflection: Minimize use; prefer AOT compilation (Micronaut)
  • Classpath scanning: Slows cold start; use explicit configuration
  • Large frameworks: Spring Boot adds significant cold start overhead

Common Pitfalls

1. Initialization in handler - Causes repeated work on warm invocations 2. Oversized JARs - Include only required dependencies 3. Insufficient memory - Java needs more memory than Node.js/Python 4. No timeout handling - Always set appropriate timeouts

References

For detailed guidance on specific topics:

  • [Micronaut Lambda](references/micronaut-lambda.md) - Complete Micronaut setup, AOT configuration, DI optimization
  • [Raw Java Lambda](references/raw-java-lambda.md) - Minimal handler patterns, singleton caching, JAR packaging
  • [Serverless Deployment](references/serverless-deployment.md) - Serverless Framework, SAM, CI/CD pipelines, provisioned concurrency
  • [Testing Lambda](references/testing-lambda.md) - JUnit 5, SAM Local, integration testing, performance measurement

Examples

Example 1: Create a Micronaut Lambda Function

Input:

Create a Java Lambda function using Micronaut to handle user REST API

Process: 1. Configure Gradle project with Micronaut plugin 2. Create Handler class extending MicronautRequestHandler 3. Implement methods for GET/POST/PUT/DELETE 4. Configure application.yml with AOT optimizations 5. Set up packaging with Shadow plugin 6. Validate: Test locally with SAM CLI before deploying

Output:

  • Complete project structure
  • Handler with dependency injection
  • serverless.yml deployment configuration

Example 2: Optimize Cold Start for Raw Java

Input:

My Java Lambda has 3 second cold start, how do I optimize it?

Process: 1. Analyze initialization code 2. Move AWS client creation to static fields 3. Reduce dependencies in build.gradle 4. Configure optimized JVM options 5. Consider provisioned concurrency 6. Validate: Measure cold start with CloudWatch metrics after changes

Output:

  • Refactored code with singleton pattern
  • Minimized JAR
  • Cold start < 500ms

Example 3: Deploy with GitHub Actions

Input:

Configure CI/CD for Java Lambda with SAM

Process: 1. Create GitHub Actions workflow 2. Configure Gradle build with Shadow 3. Set up SAM build and deploy 4. Add test stage before deployment 5. Configure environment protection for prod

Output:

  • Complete .github/workflows/deploy.yml
  • Multi-stage pipeline (dev/staging/prod)
  • Integrated test automation

Version

Version: 1.0.0

Related skills

How it compares

Pick aws-lambda-java-integration over generic AWS skills when the runtime is Java with Micronaut DI and shadow JAR Lambda packaging.

FAQ

What does aws-lambda-java-integration do?

Provides AWS Lambda integration patterns for Java with cold start optimization. Use when deploying Java functions to AWS Lambda, choosing between Micronaut and Raw Java.

When should I use aws-lambda-java-integration?

User deploying Java functions to AWS Lambda, choosing between Micronaut and Raw Java approaches, optimizing cold starts below 1 second, configuring API Gateway or ALB integration, or implementing serverless Java applications.

Is aws-lambda-java-integration safe to install?

Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.