This way, our app can be accessed from any IP. Sice our app will be running on port 8081, we will add an inbout rule with type Custom TCP on port 8081 to Anywhere.

This setup is only for demonstration purposes. You should really setup the security based on your need and use case. This is not recommended (see the AWS message). In my example I configured that anyone can SSH into the instance. In short, you define what IP addresses can access an instance on which port.

Step 4: I will choose 8 GiB of storage, which is default value. Step 3: I will be leaving everything as default. It is eligible for free tier of AWS so it is great for learning and testing purposes. Step 2: Choose the t2.micro instance type. You can really choose what ever you want here. I will be creating a t2.micro instance with 8 GiB of storage running Ubuntu 18.04. application.yml server.port : 8081 spring : application.name : spring-aws-gitlab : always datasource : url : jdbc:h2:mem:testdb driver-class-name : org.h2.Driver username : sa password : password h2.console : enabled : true path : /h2 Amazon Web Services Launcing an EC2 instance In the application.yml file, I’ve configured a server port to 8081.

I’m using H2 in-memory databse, but that can easily be sustituted by any other database management system. The app has 2 entities: Console and Game, where each Console has multiple Games, and one Game is only for one Console. I’ve already created a simple Spring Boot application with a couple of endpoints (shown bellow).

In this post I will show you how to launch an EC2 (Elastic Compute Cloud) instance on Amazon Web Services, setup a systemd service for out Spring Boot application and automate deployment procces with GitLab. Automating deployment process plays a big role in your development.

How to install gitlab on aws