AWS, CloudFormation, devops, Elastic BeanStalk, H2 in-memory DB, Java, json, mac, S3, Spring Boot

Deploy Java Spring Boot Application in AWS Elastic BeanStalk using AWS CloudFormation Scripts

In this blog we are going to explore how to deploy a Java Spring Boot Application in AWS Elastic BeanStalk using AWS CloudFormation Scripts.

To start, we need a s3 bucket with the jar file.

Step 1 : Create a s3 bucket called “catalog_springboot” using AWS S3 console or using CloudFormation scripts from my previous blog.

Step 2 : Download catalog-springboot project from GitHub. catalog-spring-boot-0.0.1-SNAPSHOT.jar is found under /src/main/resources/jar.

Step 3 : Upload catalog-spring-boot-0.0.1-SNAPSHOT.jar to “catalog_springboot” s3 bucket. [ This can be done via AWS Console or AWS CLI  as below]

aws s3 cp /Users/home/catalog-spring-boot-0.0.1-SNAPSHOT.jar s3://catalog_springboot/catalog-spring-boot-0.0.1-SNAPSHOT.jar

Step 4 : We will be creating beanstalk-catalog-springboot-application.json. It has details regarding beanstalk environment and SolutionStackName which is “64bit Amazon Linux 2017.09 V2.6.8 running Java 8” . It also specifies autoscaling and load-balancing details.

  "AWSTemplateFormatVersion": "2010-09-09",
  "Parameters": {
    "S3BucketName": {
      "Description": "S3 BucketName",
      "Type": "String"
    "S3FileName": {
      "Description": "Name of the jar/war file",
      "Type": "String"
  "Resources": {
    "sampleApplication": {
      "Type": "AWS::ElasticBeanstalk::Application",
      "Properties": {
        "Description": "AWS Elastic Beanstalk Sample Java SpringBoot Application"
    "sampleApplicationVersion": {
      "Type": "AWS::ElasticBeanstalk::ApplicationVersion",
      "Properties": {
        "ApplicationName": { "Ref": "sampleApplication" },
        "Description": "AWS ElasticBeanstalk Sample Java SpringBoot Application Version",
        "SourceBundle": {
          "S3Bucket": { "Ref" : "S3BucketName"},
          "S3Key": {"Ref" : "S3FileName"}
    "sampleConfigurationTemplate": {
      "Type": "AWS::ElasticBeanstalk::ConfigurationTemplate",
      "Properties": {
        "ApplicationName": { "Ref": "sampleApplication" },
        "Description": "AWS ElasticBeanstalk Sample Java SpringBoot Configuration Template",
        "OptionSettings": [
            "Namespace": "aws:autoscaling:asg",
            "OptionName": "MinSize",
            "Value": "2"
            "Namespace": "aws:autoscaling:asg",
            "OptionName": "MaxSize",
            "Value": "6"
            "Namespace": "aws:elasticbeanstalk:environment",
            "OptionName": "EnvironmentType",
            "Value": "LoadBalanced"
        "SolutionStackName": "64bit Amazon Linux 2017.09 v2.6.8 running Java 8"
    "sampleEnvironment": {
      "Type": "AWS::ElasticBeanstalk::Environment",
      "Properties": {
        "ApplicationName": { "Ref": "sampleApplication" },
        "Description": "AWS ElasticBeanstalk Sample Java SpringBoot Environment",
        "TemplateName": { "Ref": "sampleConfigurationTemplate" },
        "VersionLabel": { "Ref": "sampleApplicationVersion" }
  "Outputs": {
    "DevURL": {
      "Description": "The URL of the DEV Elastic Beanstalk environment",
      "Value": {
        "Fn::Join": [
              "Fn::GetAtt": [
      "Export": {
        "Name": {
          "Fn::Sub": "${AWS::StackName}-EndpointURL"

Step 5 :  Create beanstalk-catalog-parameters.json which has details of s3 bucket and jar file name.

    "ParameterKey": "S3BucketName",
    "ParameterValue": "catalog-springboot"
    "ParameterKey": "S3FileName",
    "ParameterValue": "catalog-spring-boot-0.0.1-SNAPSHOT.jar"


Step 6 : Create beanstalk_creation_tags.json. It is a best practice to tag AWS resources for billing purposes.

    "Key": "owner",
    "Value": "xxxxx"
    "Key": "contact-email",
    "Value": ""


Step 7 : Now, run the command from AWS CLI

aws cloudformation create-stack –stack-name catalog-beanstalk –template-body file://beanstalk-catalog-springboot-application.json –parameters file://beanstalk-catalog-parameters.json –tags file://beanstalk_creation_tags.json

Screen Shot 2018-05-04 at 2.17.14 PM

AWS CloudFormation console is as follows.

Screen Shot 2018-05-04 at 2.14.36 PM

We can see Elastic BeanStalk creation as follows:

Screen Shot 2018-05-04 at 2.26.51 PM

Screen Shot 2018-05-04 at 2.27.04 PM

Step 8 : When complete, it will show the URL to access the application

Screen Shot 2018-05-04 at 2.26.25 PM

Step 9 : Hit the health check url [ URL/api/catalog/health ] from any browser.

Screen Shot 2018-05-04 at 2.18.17 PM

Step 10 : Hit the catalog url [ URL/api/catalog ] to get results stored in H2 in-memory database.

Screen Shot 2018-05-04 at 1.44.25 PM

Step 11 : To terminate beanstalk, run the below command from AWS CLI

aws cloudformation delete-stack –stack-name catalog-beanstalk


CaaS, container, devops, docker, mac, redis


Docker is a container platform provider to address every application across the hybrid cloud. Docker enables true independence between applications and infrastructure and developers and IT ops to unlock their potential and creates a model for better collaboration and innovation.

Get Started

Once Docker is installed , we’ll start by creating the Dockerfile. Then we’ll create the Docker image from the Dockerfile. We’ll run it as a containerized service. Then finally, we’ll learn how to use the Docker hub to share your Docker images.

Step 1: Install Docker CE

Step 2: Open ‘Docker QuickStart Terminal  (In MAC Spotlight, Search for ‘Docker QuickStart Terminal’ )

Scenario:  Say for example, we are creating a new application and need a Redis service. In a distributed environment, we want everyone to use the same set of configured services to prevent surprises during deployment. A simple solution is to create a Redis Docker image and distribute it across the teams.

Step 3: Create a Docker File

Create a new folder called “docker_image”. After creating the folder, create the empty Dockerfile:

$ mkdir docker_image

$ cd docker_image

$ sudo touch Dockerfile

Now that the Dockerfile is created, open it in a text editor and set the base image and maintainer information. Next, update application to have the latest version of Redis and Install the Redis Server. Finally, expose the default port for Redis using the EXPOSE instruction and then set the entrypoint for the image.

You can now save the file. Here’s how it should look:

# Set the base image
FROM ubuntu

# Dockerfile author / maintainer

# Update application repository list and install the Redis server.
RUN apt-get update && apt-get install -y redis-server

# Expose default port

# Set the default command
ENTRYPOINT [“/usr/bin/redis-server”]

Step 4: Build the Docker Image

Dockerfile is ready, let’s create the image. Run this command:

$ docker build -t redis-server .

Path is a mandatory argument for the build command. We use . as the path because we’re currently in the same directory.  -t flag is used to tag the image.

Step 5: Run a Redis-Server Instance

With the image we just created, we can now create a container running a Redis server instance inside. Run this command:

$ docker run –name redis_instance -t redis-server

Screen Shot 2018-05-01 at 5.43.56 PM

This creates a container with the name redis_instance. It is a good practice to assign the name for the container or else you will need to deal with complex alphanumeric container IDs.

Useful Docker Commands:

Command to list docker image

$ docker image ls

Command to list docker containers

$ docker ps

Command to kill Conatiner

$ docker kill redis_instance

Command to save docker image

$ docker save redis-server > redis-server-image.tar

Step 6: Upload to Docker Hub

Now that we’ve successfully built an image and created a container, let’s share the images using Docker Hub.

Create login credentials in Docker Hub 

$ docker login

$ docker tag b538350ff2a3 curtistechnologies/redis-server:version1.0

$ docker image push curtistechnologies/redis-server:version1.0

$ docker image pull curtistechnologies/redis-server:version1.0