Node.js Deploy to Amazon Web Services (AWS) Tutorial (Elastic Beanstalk, Express, Git, CI/CD)

Hosting on Aws – Node.js Deploy to Amazon Web Services (AWS) Tutorial (Elastic Beanstalk, Express, Git, CI/CD)


Node.js Deploy to Amazon Web Services (AWS) Tutorial (Elastic Beanstalk, Express, Git, CI/CD)

Hosting on Aws

Python version of this video – Guided video solutions for data structures, algorithms, and interview challenges …

you search:

Hosting on Aws

Node.js Deploy to Amazon Web Services (AWS) Tutorial (Elastic Beanstalk, Express, Git, CI/CD)

32 thoughts on “Hosting on Aws – Node.js Deploy to Amazon Web Services (AWS) Tutorial (Elastic Beanstalk, Express, Git, CI/CD)

  1. Really cool man thanks for the tutorial, just what I needed. I had to open port "8080" in my settings, so guess they are distributed differently, maybe you should put that into the description if someone has the same issue (you find it in the log if anyone missed that).

  2. Thank You So………………………..Much Sir. Finally, deploy my node application on AWS and it's working fine. One more time thanks and also subscribe to your channel.

  3. instead of adding port as env variable you should use PORT(all caps) in your code for it to work also it is a good practice to have environment variables in all caps

  4. Great tutorial, thanks for putting this up. I'm not sure you need to put the picture in picture of you there though, just the monitor screen would be good, means we see more too eh – cheers.

  5. Edit: Solution at the bottom of this comment

    Everything went perfect for me besides the part 2 deploy on the CodePipeline. This was my error: "Deployment completed, but with errors: During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version. " I did everything the same as the video (will review again) – any advice?

    EDIT: The error in the AWS logs (download by going to environment -> logs) was that my package.json file did not specify a node version. I added "engines":{"node":"12.18.3"}, to my package.json top-level (inside the first {}, right after "name": "project0",). Then I got an error in the logs saying that it couldn't get my dependencies… so then, in my .gitignore, I put a # (comment symbol) in front of the node_modules line under dependencies. Boom problem fixed. Now I'm just dealing with the 502 issue with the help of the comments

    Cheers

Leave a Reply

Your email address will not be published. Required fields are marked *