Spring boot-application

Spring-Boot Application with
MySQL RDS
2
▪ Spring Boot is often described as a quick and easy way of building
production-grade Spring Framework-based applications.To accomplish
this, Spring Boot comes prepackaged with auto configuration modules
for most libraries typically used with the Spring Framework.This is often
referred to as “convention over configuration.”
▪ AWS Elastic Beanstalk offers a similar approach to application
deployment. It provides convention over configuration while still giving
you the ability to dig under the hood to make adjustments, as needed.
This makes Elastic Beanstalk a perfect match for Spring Boot.
▪ The sample application used in this blog post is the gs-accessing-data-
rest sample project provided as part of the Accessing JPA Data with REST
topic in the Spring Getting Started Guide.The repository is located in
GitHub at https://github.com/spring-guides/gs-accessing-data-rest.

MySQL RDS
3
▪ Building and Bundling the SampleApplication
▪ The first step is to clone the repository from GitHub, add “mysql-connector” to
the build steps, compile it, and generate a “fat” JAR containing all of the
required library dependencies.To accomplish this, I will use Git (https://git-
scm.com/downloads) and Gradle (downloaded automatically through a wrapper
script).
– git clone https://github.com/spring-guides/gs-accessing-data-rest.git
– cd gs-accessing-data-rest/complete
▪ In the build.gradle file, replace “compile(“com.h2database:h2′′)” with
“compile(“mysql:mysql-connector- java:6.0.3′′)”.This step will replace the use of
H2 with the mysql-connector required for persisting data to MySQL using
Amazon RDS.
▪ Build the project using the Gradle wrapper.
– ./gradlew bootRepackage
▪ After Gradle finishes building the application, the JAR will be located in
build/libs/gs-accessing-data-rest- 0.1.0.jar.

MySQL RDS
4
▪ Setting Up an Elastic Beanstalk Application
– Sign in to the AWS ManagementConsole, and then open the Elastic
Beanstalk console. If this is your first time accessing this service, you will see a
Welcome to AWS Elastic Beanstalk page.Otherwise, you’ll land on the Elastic
Beanstalk dashboard, which lists all of your applications.
1. Choose Create New Application.This will open a wizard that will create
your application and launch an appropriate environment.

MySQL RDS
5
2. When you choose Create web server, the wizard will display additional steps for
setting up your new environment
3. When you choose Create web server, the wizard will display additional
steps for setting up your new environment. Don’t be overwhelmed!
4. Now choose an environment configuration and environment type. For
Predefined configuration, choose Java. For Environment type, choose
Load Balancing, auto scaling.

MySQL RDS
6
5. Now choose an environment configuration and environment
type. For Predefined configuration, choose Java. For
Environment type, choose Load Balancing, auto scaling.

MySQL RDS
7
6. Specify the source for the application. Choose Upload your own,
and then choose the JAR file built in a previous step. Leave the
deployment preferences at their defaults.

MySQL RDS
8
7. Next, on the Environment Information page, configure the environment
name and URL and provide an optional description.You can use any name
for the environment, but I recommend something descriptive (for example,
springbooteb-web-prod).You can use the same prefix as the environment
name for the URL, but the URL must be globally unique.When you specify a
URL, chooseCheck availability before you continue to the next step.

MySQL RDS
9
8. On the Additional Resources page, you’ll specify if you want to create an
RDS instance with the web application environment. Select Create an RDS
DB Instance with this environment and Create this environment inside a
VPC.

MySQL RDS
10
9. For Instance type, choose t2.small. If you have an Amazon EC2 key pair and
want to be able to remotely connect to the instance, choose your key pair
now; otherwise, leave this field blank.Also, set the Application health check
URL to “/”. Leave all of the other settings at their defaults.

MySQL RDS
11
10. On the EnvironmentTags page, you can specify up to seven environment
tags.Although this step is optional, specifying tags allows you to document
resources in your environment. For example, teams often use tags to
specify things like environment or application for tracking purposes.

MySQL RDS
12
11. On the RDS Configuration page, configure a MySQL database with an
Instance class of db.t2.small. Specify a Username and Password for
database access.Choose something easy to remember because you’ll need
them in a later step. Also, configure the Availability to Multiple availability
zones. Leave all of the other settings at their defaults.

MySQL RDS
13
12. The next step in the wizard is used to configure whichVPC and subnets to
use for environment resources. Specifying aVPC will give you full control
over the network where the application will be deployed, which, in turn,
gives you additional mechanisms for hardening your security posture.
13. For this deployment, specify the defaultVPC that comes with all recently
created AWS accounts. Select the subnets Elastic Beanstalk will use to
launch the Elastic Load Balancing load balancers and EC2 instances. Select
at least two Availability Zones (AZ) for each service category (ELB and EC2),
in order to achieve high-availability.
14. Select Associate Public IP Address so that compute instances will be created
in the public subnets of the selectedVPC and will be assigned a public IP
address.The defaultVPC created with most accounts contains only public
subnets. Also, for theVPC security group choose the default security group
already created for your defaultVPC.

MySQL RDS
14

MySQL RDS
15
15. On the Permissions page, configure the instance profile and
service role that the Elastic Beanstalk service will use to
deploy all of the resources required to create the
environment. If you have launched an environment with this
wizard before, then the instance profile and service role have
already been created and will be selected automatically; it
not, the wizard will create them for you.

MySQL RDS
16
16. The final step in the wizard allows you to review all of the settings.
Review the configuration and launch the environment! As your
application is being launched, you’ll see something similar to this on
the environment dashboard.
17. The final step in the wizard allows you to review all of the settings.
Review the configuration and launch the environment! As your
application is being launched, you’ll see something similar to this on
the environment dashboard.
18. During the launch process, Elastic Beanstalk coordinates the
creation and deployment of all AWS resources required to support
the environment.This includes, but is not limited to, launching two
EC2 instance, creating a Multi-AZ MySQL database using RDS,
creating a load balancer, and creating a security group.

MySQL RDS
17
19. Once the environment has been created and the resources have been deployed,
you’ll notice that the Health will be reported as Severe.This is because the Spring
application still needs some configuration.

MySQL RDS
18
▪ Configuring Spring BootThrough EnvironmentVariables
– By default, Spring Boot applications will listen on port 8080. Elastic
Beanstalk assumes that the application will listen on port 5000.There are
two ways to fix this discrepancy: change the port Elastic Beanstalk is
configured to use, or change the port the Spring Boot application listens
on. For this post, we will change the port the Spring Boot application
listens on.
– The easiest way to do this is to specify the SERVER_PORT environment
variable in the Elastic Beanstalk environment and set the value to 5000.
(The configuration property name is server.port, but Spring Boot allows
you to specify a more environment variable-friendly name).
– On the Configuration page in your environment, under Software
Configuration, click the settings icon.

MySQL RDS
19
• On the Software Configuration page, you’ll see that there are already some
environment variables set.They are set automatically by Elastic Beanstalk
when it is configured to use the Java platform.

MySQL RDS
20
• To change the port that Spring Boot listens on, add a new environment
variable, SERVER_PORT, with the value 5000.

MySQL RDS
21
• To change the port that Spring Boot listens on, add a new environment
variable, SERVER_PORT, with the value 5000.
• In addition to configuring the port the application listens on, you also need to
specify environment variables to configure the database that the Spring Boot
application will be using.

MySQL RDS
22
• Before the Spring Boot application can be configured to use the RDS
database, you’ll need to get the database endpoint URI. On the Environment
Configuration page, under the DataTier section, you’ll find the endpoint
under RDS.

MySQL RDS
23
▪ Spring Boot bundles a series of AutoConfiguration classes that
configure Spring resources automatically based on other classes
available in the class path. Many of these auto configuration
classes accept customizations through configuration, including
environment variables.To configure the Spring Boot application
to use the newly created MySQL database, specify the following
environment variables:
– SPRING_DATASOURCE_URL=jdbc:mysql://<url>/ebdb
– SPRING_DATASOURCE_USERNAME=<username>
– SPRING_DATASOURCE_PASSWORD=<password>
– SPRING_JPA_HIBERNATE_DDL_AUTO=update
– SPRING_JPA_DATABASE_PLATFORM=org.hibernate.dialect.MySQL5Dial
ect

MySQL RDS
24
• As soon as you click Apply, the configuration change will be propagated to the
application servers.The application will be restarted.

MySQL RDS
25
• When it restarts, it will pick up the new configuration
through the environment variables. In about a minute,
you’ll see a healthy application on the dashboard!

Testing Spring Boot in the
Cloud
26
• Now test the deployed REST API endpoint!
• Use the URL you configured on the environment to access the
service. For this example, the specified URL is
http://springbooteb-web-prod.us-east-1.elasticbeanstalk.com/.
• For our first test, we’ll do an HTTP GET on the root of the URL:
curl -X GET -i http://springbooteb-web-prod.us-east-1.elasticbeanstalk.com/

Cloud
27
• The service responded with a JSON HAL document.There’s a
“people” repository you can access. Next, create a person!

Cloud
28
• You’ve successfully added a person. Now get a list of people.
• There’s the person you added!The response from the server
is a HAL document with HATOAS and pagination.

Conclusion
29
• In just a few clicks you’ve deployed a simple, production-
ready Spring Boot application with a MySQL database on
AWS using Elastic Beanstalk.
• As part of the launch and configuration of the environment,
Elastic Beanstalk launched resources using otherAWS
services.These resources still remain under your control.
They can be accessed through other AWS service consoles
(for example, the EC2 console and the RDS console).
• This is not the only way to deploy and manage applications
onAWS, but it’s a powerful and easy way to deploy product-
grade applications and services.
• Most of the configuration options you set during the setup
process can be modified.There are many more options for
customizing the deployment.

Spring boot-application

Recommended

More Related Content

What's hot (14)

Similar to Spring boot-application (20)

More from Parag Patil (14)

Recently uploaded (20)

Spring boot-application

Editor's Notes