aws / aws/serverless-java-container

Build and deploy native serverless app

Open
#1,082 1 comment 0 reactions 0 assignees View on GitHub
docs
Dominant language
Java
Stars
1.6k
Forks
574
PR merge metrics
No merged PRs in 30d

Description

*To help us debug your issue fill in the basic information below using the options provided*

*Serverless Java Container version*: `eg. 1.5`

*Implementations:* `Spring Boot 2 `

*Framework version:* `eg SpringBoot 3.3.4`

*Frontend service:* `REST API `

*Deployment method:* `eg SAM`

## Scenario
*I am tryin g to build native app and deploy, there are no instructions about how to build and deploy native app. I tried to use example pet-clinic native but I can only build it. Please provide typical way to build native app and deploy using architype*

## Expected behavior
*Describe how you would expect the application to behave*

## Actual behavior
*Describe what you are seeing instead*

## Steps to reproduce
*generate app and create CRUD rest service*

windows
```
mvn archetype:generate -DgroupId=dev -DartifactId=lambda -Dversion=1.0 ^
-DarchetypeGroupId=com.amazonaws.serverless.archetypes ^
-DarchetypeArtifactId=aws-serverless-springboot3-archetype ^
-DarchetypeVersion=2.0.1
```
linux
```
mvn archetype:generate -DgroupId=dev -DartifactId=lambda -Dversion=1.0 \
-DarchetypeGroupId=com.amazonaws.serverless.archetypes \
-DarchetypeArtifactId=aws-serverless-springboot3-archetype \
-DarchetypeVersion=2.0.1
```
*build native image*

*deploy to aws*
```sam deploy --guided --profile sv```

Contributor guide

Open the contributing guide

Research direction

Start with the Spring Boot 3 archetype commands in the issue and compare them with the pet-clinic native example. Document the typical native-image build and AWS deployment flow, including the `sam deploy --guided --profile sv` step; done means a generated CRUD REST service can be built natively and deployed using the archetype.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, java, spring-boot
Domain
api, build-system, cloud
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.