Deploy Full Stack Application (Spring-Boot+MySQL+React) to AWS(EC2, RDS, S3) | new 2023 

I'm Happy to hear the success 👍

My friend. I'm happy it was of help to you. 👍🏽

Thanks for feedback. I'm happy tw's helpful

I'm glad it helped

Thanks Немања 🙏🏽 I appreciate this ❤

I'm happy it helped 👍

I'm happy your deployment was a success

Thanks, I appreciate 🙏🏽

Thanks for the comments 👍

Thanks. I'm glad it helped

I'm glad it helped ✌🏾

Thanks

🤗

👍👍

Thanks Chun for your Compliment. I appreciate 🙏🏽

I'm happy it helped

You're welcome!

👍🏽👍🏽👍🏽👍🏽

Glad it helped ❤️

For Elastin Bean I'll drop a video on that soon. But I want to know the functionilty in question you talking about? For Elastic Beanstalk vs Ec2, Ec2 is more scallable and you are responsible for managing and maintaining with wider range of customization. Elastic do better interms of auto scalling. Will be curious to know the specific functionality you want to acheive with Beanstalk

That's not a prob. it follows the same pattern. i'll do at free time

@@PhegonDev yes that would be helpful. Can you atleast tell me how can we connect to MongoDB

I'm happy it helped

That is because your server doesn't have an SSL/TLS certificate and haven't been configured yet.

@@PhegonDev Friend, I have the same problem. Would you help me.

🙏🏽

No. You can run your app in your server on a screen. So when you detached and exit your terminal, it'll still be up and running.

For EC2 It is around $0.0116 per hour for the t2.micro instance in the US East (N. Virginia) region. FOR RDS. Instance pricing: The hourly cost for a small DB.t2.micro instance, which includes a single vCPU and 1 GB of RAM, is approximately $0.017 per hour in the US East (N. Virginia) region. Storage pricing: The cost for General Purpose SSD (gp2) storage is approximately $0.115 per GB per month. From here you can do your calculation. OTHER ALTERNATIVES SOLUTIONS I think the major cut will be on AWS RDS. If you are on a budget and your database is still small, you can choose to set up and manage your own MySQL database on a virtual machine (VM) or bare metal server, or another platform with extremely low cost. You can research that. AWS RDS primarily favors big companies. Also, if your application isn’t large and doesn’t have many visitors at the moment, instead of hosting on EC2 you can consider using serverless aws lambda. By this, you pay for only when it’s been used. I may consider creating a tutorial on serverless.

If I get you clearly, what you mean is a link where you can connect to your service. You already have what you need. Your url is http//your_server_public_ip:port/any_other_thig e.g path variable or your deployed service. As long as you call it you can connect to your deployed service except you chose to add some additional security configuration

@@PhegonDev the url ip_adresse/... will work everyWhere even from another network because the ip adresse is related to network .

Okay. There are many reasons for these. We cannot tell now. I presume you are testing from your frontend after deployment. That information I am not aware. 1. To troubleshoot. After you deployed your backend to server first test your deployed app by using a client like Postman to manually send a login request to your server. This can help you isolate whether the issue is with your client-side code or with the server configuration. The error will determin if it is a server config or cient. Also login unto your server to see if the request is comming and to view the logs.

Hi Chloe, Yes, It ends at step 4, get your EC2-spring-boot endpoint, that’s all. You don’t need to deploy your webpages(thymeleaf) separately as they are coupled together with your spring-boot and they can be rendered together on a server.

@@PhegonDev Thank you so much for your answer!!

@@Chloe-si2hq 👍🏽👍🏽👍🏽👍🏽👍🏽👍🏽

I don't know what platform you are using. if you are to use your private server do the following. 1. Install the necessary dependencies required to run a jar file on your server. 2. Configure the server port you want to expose. 3. Do some security settings inorder to prevent unauthorised access to your server. 4. When you done, bundle your application put it there and run it.

Okay!. What error is showing on the frontend after deployment? This will give a trace of what the prob is

Get a domain from a domain provider, e.g namecheap or porkbun.com. You can then decide to host your services there or if you already have them hosted elsewhere e.g on aws ,you can use the DNS management to on your provider setting to route your domain url to the url of where your services are hosted

That's not a prob at all. AWS s3 bucket is used for storing static files. What you'll do is, "create a folder in the s3 bucket upload the images there manually and then reference it from your react app(each image/file on the s3 have a reference url/path)". If the image upload is dynamic i.e it's done by the end users using your application, you can use this link on how to upload image to s3 from react app. If I have a little bit of time, I'll do a video on that. dev.to/shadid12/how-to-upload-images-to-s3-in-a-react-application-4lm

@@PhegonDev OMG! Thank you so much! It's really help me.

First, After uploading to s3 , are you able to access your web pages via the s3 url? and are the necessary pages able to show? if yes you good to go if no then you didn't upload files correctly. 2, Where is your database?. Is your database hosted on RDS or is still on your local machine? If it’s on RDS then be sure your can access it via the rds url and password. Also always console log your errors when trying to perform operations on your database by so doing we’ll be able to see the error and know what to do.

SURE. You need to use screen to Acheive this. Run the below command on your server. screen --version ⇒ Check if you have screen install already. If not sudo yum install screen ⇒ Past this command to install screen screen ⇒ to create a screen with a random name or screen -S “prefered_screen_name” ⇒ to create a named screen else a random numeric name will be given screen -ls ⇒to list all available screen screen -r 123 ⇒ where 123 is the name a particular screen Run you application java on the server. E.g java jar app.jar or node index.js ctr + a + d ⇒ to detach from the running application and make the application run on a background screen screen -ls ⇒ to see list of running screen. Attached means not running Detached means it running at the background. If status is detached you can exit your server and you app will still be running. screen -r 123 ⇒ to enter your screen again.

awesome thank you for getting back to me! I also found a different solution in the meantime. At around 33:00 after copying the jar file, you can run ‘nohup java -jar ~jar file~ > output.log &’ instead of just running ‘java -jar ~jar file~’. This should keep the server up and running even after closing out the terminal as well!

*Keyword*: nohup Before running the jar file!

@@Prod3t Great. Thanks for sharing 👍

I can do that as well

@@PhegonDev thanks bro I have done but you will make video that should help people

Sure. Here it is: github.com/dennisiluma/employee-management

First debug and check if you able to connect to the database

If I get you correctly, when you say desktop you mean on your local machine? Because react is for web and react native can be used for building desktop apps. So I presume you mean on your local machine. If that's the case, check if other functionalities are working fine. If they are, then check your authenticator (firebase) if it requires some configurations. If other functionalities aren't working fine, then your frontend may have difficulty connection with your API, which you can easily resolve

@@PhegonDev Thank you, the problem was with firebase authorised domains. While we test, we have to enter the domain name in authorised domain section which will be in authentication.

@@_IT_Jason 👍👍 Nice. Good to hear it has been resolved

OK. First of all, Console log the cors error to check the exact type. If it’s server related you can add this to your controller to allow from all origin.@RestController @CrossOrigin(origins = "*") public class Controller {} Remember after setting SSL Certificate on your server, your api url should now be https If you follow this it should work fine.

now you have ssl certificate You can configure to use https

From your question, it seems your RDS only allows ip of your ec2 server. It doesn’t allow any other ips. WAY TO RESOLVE Check RDS Logs: Examine the Amazon RDS error logs for any issues or error messages that might provide clues about the problem. You can find these logs in the AWS Management Console. Check RDS Instance Availability: Ensure that your RDS instance is in the "available" state. If it's in a different state, it might not accept connections. Check Security Groups: Verify that your local IP address is whitelisted in the RDS security group. Update RDS Security Group: 1. Go to the AWS Management Console. 2. Navigate to the "Amazon RDS" service. 3. In the left sidebar, choose "Databases." 4. Select your RDS instance. 5. Scroll down to the "Security group rules" section and click on the associated security group. 6. In the security group settings, edit the inbound rules to allow traffic from the desired IP addresses or from anywhere (0.0.0.0/0 for all IPs). Add a new rule if necessary. WITH THESE, YOU GOOD TO GO

@@PhegonDev it's accessible everywhere, I mean I changed security group, but still can't connect

@@lunamore4077 If you cannot connect to you database how then is it accessible? I may not understand your exact question then. Check if your RDS instance if it is running and check your RDS logs. The logs will gives you all you need as to why it is not connecting(provided your credentials are correct) Again as i said it comes down to your security group configurations provided your login credentials are correct.

@@PhegonDev sir, I made it!!!! thank you. But right now I'm having another issue with refreshing the database in part 37:56, I deployed the build file on s3, and I followed all the steps except refreshing and setting the limit (I did it using cmd because my workbench is encountering some error). The page appeared however it became just static, I couldn't add new users and existing tables didn't appear. I guess it's because smth wrong with my database. Do you have any idea how to solve it?

@@lunamore4077 Good. I think you should follow these steps one at a time. 1. Set up your RDS database or platform you chose to use.. 2. Make sure you are able to connect to it first either using your cmd/shell as you said you did. 3. Connect your database to your backend application. 4. First Test on your local environment. 5. If it works fine, deploy each(backend & frontend) service to their respective platforms. 6. Test again after deploying. BONUS: As you are developing add loggings to your frontend and backend so you can easily view your errors for debugging sake. If you follow these steps correctly when you get stock on any step, you can easily know where the problem is. Doing everything at the same time will take extra time to know where exactly the prob is. In your current case, seems you able to access your database via the cmd which is good news. I still do not know why you are unable to use GUI e.g workbench. Ok, now you say existing tables didn’t appear? so you mean your table is not created in your database, so how can you add data to a table that doesn’t exist. Follow the above steps. If you are using the jpa @Entity database model on your spring boot project, your tables should auto persist and they'll be created once your backend application is run provided your app successfully makes a connection to your database. These are the little things you should check. I do not know the architecture you are using on your project. If you follow the listed steps above then you can easily resolve the issue

yes

1. Are you running your application as a screen. Remember if you aren't running your server as a screen when you quit/exist from shell it'll stop the service. I presume you deployed your java app on EC2 2. After you deployed your application try to test all component endpoints (that's the endpoints now running on your aws server) before integrating with your frontend app. 3. If 1 and 2 are done correctly then ass a console log to your react app to show the error when login or the implementation in question fails. This will give a hint a to what the problem is. 4. Take note of your environment variables make sure they are exported to your remote server so it can be easily accessible there. Remember you no longer on localhost.

hey did you find any solution for this im facing same

@@xash6917 Unfortunately, no.

If you close your cmd on ec2 your application will stop running because you are not detaching your cmd from the server. This can be solved by having screen sessions on your ec2 server. To do this; 1. Install a screen on your ec2 server using “sudo yum install screen” 2. Create a named screen using “screen -S your-screen-name” 3. Run your application on your screen using “java -jar your-applicationname.jar” 4. Detach from screen so your application can continue to run on background even when you exit by using “Ctr + a + a” This will solve your prob

@@PhegonDev thanh you very much

For Ec2. 1, Install Node environment on your server. 2, Ship in your node project and run it. That's all. For s3, Build your reach and upload to s3 as already done on the tuts.

​@@PhegonDevthank you I've deployed it!

From your error seems you still trying to connect to your local DB. Since you are now using your database hosted on aws, point the hostname to the url of the aws database[ not local host] also goes for the username and password.

@@PhegonDev still failed...should I move on next step first? spring boot & react, or this part should complete first? Thank you!

@@hou-chunlee5974 Either way is fine. But you should be able to connect to your database on aws and test to be sure it's successfully conneected so you can avoid arror along the way. I'll suggest you deal with that first.

@@PhegonDev thanks a lot! i will do the rest of the part first. i keep troubleshooting but still failed...

1 Free tier expiration The free tier for new AWS accounts is valid for 12 months from the date your account was created. If your account is more than 12 months old, you will no longer be eligible for the free tier and will be charged for all RDS resources used. 2 Check your AWS Billing and Cost Management console: This will provide you with a detailed breakdown of your charges, including the specific resources used and the associated costs. 3 Maybe you are exceeding the Free Tier limits: The AWS Free Tier for RDS includes 750 hours per month of usage for certain instance types (db.t2.micro, db.t3.micro, and db.t4g.micro). If you are using a different instance type or exceeding the 750 hours of usage per month limit, you will be charged for the additional usage. You may also be exceeding the free tier limits for storage, backups, or other resources associated with your RDS instance. Storage: The free tier includes 20 GB of storage per month. If your database exceeds this limit, you will be charged for the additional storage used. 4 The following RDS instance types are free for 12 months for new AWS accounts: db.t2.micro db.t3.micro db.t4g.micro 5 Please check if your RDS instance falls within such a category( i.e db.t2.micro, db.t3.micro, db.t44.micro). If you choose a different instance type, like t2.micro or m5.micro or t3.micro , you will be charged for the full cost.

yes it is

If your AWS account is new then it is free for a yr for micro instances but after a yr or if the account is more than a yr below are the pricing in U.S dollars. 1. EC2 (t2.micro instance in the US East (N. Virginia) ): Annual cost: $0.0116/hour * 24 hours/day * 365 days = approximately $101.62 per year. 2 RDS (db.t2.micro instance for MySQL in the US East (N. Virginia) ): Annual cost: $0.017/hour * 24 hours/day * 365 days = approximately $148.92 per year.

Thanks for quick reply, Channel subscribed. I have react and springboot and react application, this is the simple application and in this application i am uploading images through springboot and planning to stored in S3 and path storing in DB and some other other information. Please suggest if other way. And Database side which db i should use so for all 3 three aws services.. it should be cost around 125-180$.. bcz I don't have that much budget

Also I checked for vps hosting they are providing features for 1 year, linux, 3 core, 3gb ram, disk 90gb, bandwidth 3tb, ssl certificate, database space unlimited all this i am getting at 150$.. which one will be better aws cloud or vps hosting?

@@lalitk7057 Overall, vps is way cheaper. I don't know the size of your project. If it's a medium or small size use vps but if it's a very large aplication use AWS. you can also migrate anytime as well. For a start, i'll suggest you use VPS then you can migrate to aws when the need arises or when you start making enough. AWS can be very expensive. it's suitable for big companies. Alternatively, instead of ec2 you can use lambda functions, by this, you'll only pay when users make calls to your service while for idle time, you pay nothing.

nah, It's not. But you are allowed to test for 1 yr with some limitations if your account is new

Sure Noted!

come and teach us ...u try

@@davidosimiri7344 if you want me to teach you then you can visit New Delhi India!!

@@virusehwag9562 am ok with this lesson...

I'm happy tw's helpful. 👍