{"id":89777,"date":"2021-02-02T20:08:09","date_gmt":"2021-02-02T20:08:09","guid":{"rendered":"https:\/\/www.red-gate.com\/simple-talk\/?p=89777"},"modified":"2021-02-02T20:08:09","modified_gmt":"2021-02-02T20:08:09","slug":"deploying-a-nodejs-application-from-github-to-aws-elastic-beanstalk-and-creating-a-ci-cd-aws-codepipeline","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/blogs\/deploying-a-nodejs-application-from-github-to-aws-elastic-beanstalk-and-creating-a-ci-cd-aws-codepipeline\/","title":{"rendered":"Deploying a NodeJS application from GitHub to AWS Elastic Beanstalk and creating a CI\/CD AWS CodePipeline."},"content":{"rendered":"

Goals<\/h2>\n

In this article I will assist you to deploy a NodeJS application from GitHub into AWS Elastic Beanstalk and Building a CI\/CD pipeline.<\/p>\n

What is Elastic Beanstalk ?<\/h2>\n

Using Elastic Beanstalk you will be able to deploy and manage applications within the AWS Cloud without having knowledge about the infrastructure that execute those applications. Elastic Beanstalk reduces management complexness without proscribing selection or control. You just transfer your application and Elastic Beanstalk mechanically handles the main points of capability provisioning, load equalization, scaling and application health observance.<\/p>\n

Elastic Beanstalk support applications developed in java, Go, PHP, NodeJS, Python and Ruby. Once you deploy your application, Elastic Beanstalk build the chosen supported platform version and provisions one or additional AWS resources like AmazonEC2 instances, to run your application. Elastic Beanstalk has a default security group, this security group acts as a firewall for the instances.<\/p>\n

Elastic Beanstalk console is used to interact with Elastic Beanstalk. You can also use AWS Command line interface or high-level designed interface.<\/p>\n

Once you create and deploy application, information about your application can be available on Elastic Beanstalk console.<\/p>\n

Why Elastic Beanstalk ?<\/h2>\n

AWS Elastic Beanstalk makes it easy for developers to share their application across different devices within less amount of time.<\/p>\n

Pre-Requisities<\/h2>\n

We will need pre-built sample of NodeJS application , you can download using this URL from GitHub https:\/\/github.com\/jspruance\/musician-app<\/a>. You should also have GitHub account and AWS account , you can create a free AWS account from https:\/\/aws.amazon.com\/<\/a>.<\/p>\n

Click here<\/a>, to Create AWS Account and enter AWS User name and Password and it will open AWS Management Console page. Click on All services and choose AWS Elastic Beanstalk.<\/p>\n

<\/p>\n

Figure 1: AWS Management console<\/strong><\/p>\n

When you click on Elastic Beanstalk , you will be directed to AWS Elastic Beanstalk Dashboard page and click \u201cCreate Application\u201d button and configure your NodeJS application.<\/p>\n

<\/p>\n

Figure 2: AWS Elastic Beanstalk Dashboard page<\/strong><\/p>\n

To create an Application<\/h2>\n

You can use \u201cCreate Web app\u201d console wizard to create your sample application.<\/p>\n

    \n
  1. Specify your Elastic Beanstalk application name information e.g: musician-sample<\/li>\n
  2. Click on Platform drop-down and select your platform e.g: node.js. Platform branch and platform version will be auto populated.<\/li>\n
  3. Select the Sample Application as application code and click on \u201cCreate Application \u201c button. It will take few minutes to launch your application.<\/li>\n<\/ol>\n

    <\/p>\n

    <\/p>\n

    Figure 3: Creating a Web App Information page<\/strong><\/p>\n

    This will deploy your application in specific environment and tracks the progress and display events.<\/p>\n

    <\/p>\n

    Once your Application is successfully launched , you will see Green check mark.<\/p>\n

    The environment Overview page will display high level of environment information such as Environment Health, Application running version and Application platform version where application is running on.<\/p>\n

    <\/p>\n

    <\/p>\n

    Figure 4: Environment overview page <\/strong><\/p>\n

    On top of the Overview Page you will see the environment\u2019s URL below the environment name, click on this URL to get to the sample application\u2019s Congratulations Page.<\/p>\n

    <\/p>\n

    <\/p>\n

    Once your application is successfully deploy, we will set up a Continuous Integration and Continuous Delivery (CI\/CD) AWS pipeline using AWS Code Pipeline Service. AWS Code pipeline services helps you to Build, Tests and Deploy code when there is any code changes in your source code.<\/p>\n

    We will learn how to create a simple pipeline that pulls code from GitHub repository and automatically deploy to AWS EC2 instances.<\/p>\n

    Click on \u201cService\u201d dropdown and Select \u201cCodePipeline\u201d as shown in below picture OR you can also search \u201cCodePipeline\u201d in search bar.<\/p>\n

    <\/p>\n

    Figure 5: AWS Service page<\/strong><\/p>\n

    On CodePipeline Dashboard page choose \u201cCreate Pipeline\u201d. Click on Get started for the first time user.<\/p>\n

    <\/p>\n

    <\/p>\n

    Figure 6: Create pipeline page<\/strong><\/p>\n

    Choose Pipeline settings<\/h2>\n

    AWS source resources you created must be in same region as your pipeline.<\/p>\n

      \n
    1. In Pipeline Name enter name of the pipeline. e.g: \u201cmusician-pipeline\u201d. You cannot edit pipeline name once it is created.<\/li>\n
    2. In Service Role default to \u2018New Service Role\u2019, it will help CodePipeline to create a new service role in IAM.<\/li>\n
    3. In Role Name default to \u2018AWSCodePipelineServiceRole-Region-pipeline name\u2019 .Example,this is the service role created for a pipeline named AWSCodePipelineServiceRole-us-west-2-musician-pipeline.<\/li>\n
    4. Click on Next Button as shown in figure.<\/li>\n<\/ol>\n

      Step 1: Add Source Stage<\/strong><\/p>\n

        \n
      1. On Source page, under Source Provider ,choose GitHub(Version 1).<\/li>\n
      2. If you have not created GitHub connection , click on \u201cConnect to GitHub\u201d button to grant permission to AWS Code pipeline to access your GitHub repository. This will help AWS Code Pipeline to upload your committed changes from GitHub to AWS Code Pipeline.<\/li>\n
      3. GitHub connection page will appear as shown below.<\/li>\n<\/ol>\n

        <\/p>\n

          \n
        1. Click on \u201cAuthorize aws-codesuite\u201d . It will grant permission to connect to GitHub<\/li>\n
        2. To connect to GitHub you need to click on \u201c Authorize AWS code-suite\u201d green button. Once you are successfully connected you will see the successful message in green box.<\/li>\n<\/ol>\n

          <\/p>\n

          Figure 7: Add source stage<\/strong><\/p>\n

          <\/p>\n

          Figure 7.1 : Add source stage<\/strong><\/p>\n

            \n
          1. In repository choose the name of your repository where you committed your code ,example : BinnyJoshi\/musician<\/li>\n
          2. In Branch select the branch name where you want your pipeline to detect source code. Example: Master<\/li>\n
          3. Choose GitHub webhooks, this will allow to trigger pipeline whenever there is any code changes to repository.<\/li>\n
          4. Click on NEXT button.<\/li>\n<\/ol>\n

            <\/p>\n

            Step 2 : Add Build stage<\/strong><\/p>\n

            1 ) Skip Build Stage, click on \u201cSkip\u201d button.<\/p>\n

            <\/p>\n

            <\/p>\n

            Figure 9: Add Build stage<\/strong><\/p>\n

            Step 3 : Add Deploy Stage details<\/strong><\/p>\n

              \n
            1. In Deploy provider , choose AWS Elastic Beanstalk.<\/li>\n
            2. In Region select the region where you have created your source code.<\/li>\n
            3. In Application name enter or choose the name that you have already created on AWS Elastic Beanstalk console.<\/li>\n
            4. In Environment name enter or choose the name that you already created on AWS Elastic Beanstalk console.<\/li>\n
            5. Click \u201cNext\u201d button<\/li>\n
            6. You will be directed to pipeline \u201cReview page\u201d.<\/li>\n<\/ol>\n

              <\/p>\n

              Figure 10: Add deploy stage<\/strong><\/p>\n

              Pipeline Review page details \u2013 as shown in below figure:<\/p>\n