Deploying a Single Page Application (SPA) on AWS: A Beginner's Guide. Part 8. Serverless

Deploying a Single Page Application (SPA) on AWS: A Beginner's Guide. Part 8. Serverless

Complete self-driving capabilities


Serverless architecture and AWS Lambda have brought a revolutionary change to how developers build and deploy applications. By eliminating the need to manage servers, developers can focus more on writing code and delivering features. This article explores the benefits of serverless, such as reduced operational overhead, cost-effectiveness, and scalability. Additionally, we delve into AWS Lambda, a popular serverless computing platform, and how it can streamline your application development process.

For theoretical insights into serverless, you can visit


AWS SAM (Serverless Application Model) is a framework that simplifies the development and deployment of serverless applications on AWS. It extends AWS CloudFormation to provide a simplified way of defining the resources and functions required for your application. To install AWS SAM, you can use the AWS SAM CLI, which is available through package managers like Homebrew, pip, or by downloading the installer from the official AWS SAM GitHub repository.

Java Code + SAM CloudFormation Template = Production Backend

The Price of Serverless

To fully benefit from serverless architecture, it's essential to refactor your code to be serverless-compatible with AWS Lambda. This process involves adapting your application's structure and codebase to work with Lambda functions, which are stateless, event-driven, and automatically managed by AWS. By doing so, you can take advantage of reduced operational overhead, cost-effectiveness, and improved scalability without the need to manage servers.

How Complex Is the Refactoring?

With Spring Boot 3 Application, making your code serverless-friendly is as simple as importing one library from AWS to wrap your Spring Boot App into an AWS Lambda handler:

public class GreetingLambdaHandler implements RequestStreamHandler {
    private static SpringBootLambdaContainerHandler<HttpApiV2ProxyRequest, AwsProxyResponse> handler;
    static {
        try {
            handler = SpringBootLambdaContainerHandler.getHttpApiV2ProxyHandler(RestServiceApplication.class);
        } catch (ContainerInitializationException e) {
            throw new RuntimeException("Could not initialize Spring Boot application", e);

    public void handleRequest(InputStream inputStream, OutputStream outputStream, Context context)
            throws IOException {
        handler.proxyStream(inputStream, outputStream, context);

That's all!

Deploying the App

Here's the CloudFormation template (CFN) for our Spring Rest API backend:

AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: Example Rest API Serverless for Spring Boot 3

    Type: AWS::Serverless::Function
      Handler: com.example.restservice.GreetingLambdaHandler::handleRequest
      Runtime: java17
      CodeUri: .
      MemorySize: 512
      Policies: AWSLambdaBasicExecutionRole
      Timeout: 60
          Type: HttpApi
            TimeoutInMillis: 20000
            PayloadFormatVersion: "2.0"

    Description: URL for application
    Value: !Sub "https://${ServerlessHttpApi}.execute-api.${AWS::Region}"

Now, let's build and deploy it:

sam build
sam deploy -g

And you can use the URL:

curl https://${ServerlessHttpApi}.execute-api.${AWS::Region}

So simple!

Let's Deep Dive into the CFN Template

The provided CloudFormation template is a description of AWS resources to be created or configured, focusing on a serverless architecture for hosting a REST API using Spring Boot 3 and Java 17.

Here's a breakdown of each part:

  1. AWSTemplateFormatVersion: Specifies the version of the CloudFormation template, in this case, '2010-09-09'.

  2. Transform: Indicates that the template uses the AWS Serverless Application Model (SAM) transformation named 'AWS::Serverless-2016-10-31'. This transformation provides a simplified syntax for describing serverless resources such as Lambda functions and APIs.

  3. Description: Provides a brief description of the template's purpose, specifically mentioning that it's an example REST API using serverless technology for Spring Boot 3.

  4. Resources: The main section, where all the resources to be created or configured are defined:

    • MyRestApiFunction: Describes a Lambda function that will handle the REST API requests.

      • Handler: Specifies the Java class and method that AWS Lambda will call to start executing your function.

      • Runtime: Specifies the runtime environment (Java 17).

      • CodeUri: The location of the code for the Lambda function (in this case, the current directory).

      • MemorySize: The amount of memory available to the function during execution (512 MB).

      • Policies: The permissions assigned to the function, here using a predefined basic execution role.

      • Timeout: The maximum amount of time the function is allowed to run (60 seconds).

      • Events: Defines an HTTP API event that triggers the Lambda function. It sets a specific timeout and payload format version for the event.

  5. Outputs: The section defines values that you can import into other stacks, return in response, or view in the AWS CloudFormation console.

    • RestApi: The output provides the URL for the REST API application, constructed dynamically using the region where the stack is launched.

Overall, this CloudFormation template represents a serverless application for a RESTful API using Spring Boot 3, capable of being deployed on AWS using Lambda and other serverless technologies. It includes configurations and properties that define how the API and Lambda functions should behave.


This article introduced the benefits of serverless architecture and AWS Lambda for application development, highlighting reduced operational overhead, cost-effectiveness, and scalability. We explored the AWS SAM framework, and the process of refactoring code for serverless compatibility, and provided an example of deploying a Spring Boot 3 REST API using a CloudFormation template.