The first step is to download the Repo from Kura Labs Github account in the form of a zip file.
The second step is to extract the zip file. After that, we will create a new repo and drag the contents of the extracted folder into the Github client.
The third step is to procure a Personal Access Token on Github and selecting the “repo” and “admin:repo_hook” parameters, securing the access token into a safe place for our Jenkins server.
The fourth step is to log into our Jenkins Server to build, test and deploy our build. In order to set up the build, we will create a pipeline using our Github credentials with Jenkins Credentials Provider verification with the proper authentication using our Github username and Personal Access Token as our password.
Following the fourth step, we will then go back to our Github repo and download said repo as a Zip file. We will extract the contents from the folder, and then go into the folder and compress the contents inside again to make sure the Local File is prepped for Elastic Beanstalk.
The sixth step is to set up our IAM roles on AWS according to our given parameters based on the service we need, choosing the “Use Case(s)”, and other specifications as outlined.
The seventh step is to set up our EC2 instance on AWS where we select the type of application that we are uploading, the raw file itself, picking out our selected service roles as outlined in the instructions given by instructors.
After we set up our EC2 instance we should have an application that launches, but we have come across an error. In order to mitigate the issue, I checked the Last 100 log entries. The error we received was “ModuleNotFoundError: No module named ‘application’.
Our next step will then be to go back into the Zip file we originally uploaded, extract it, and select the appropriate "module", and correct the issue. Then we will rezip the contents of our folder into a new Zip file, and reupload our Zip file into AWS.
Success! And our url_shortener has launched.
And our application is now live 🥳
